For those of you that want to get in on early GB development but don't have the skill to compile it from source, I compiled the new source code that dropped for the gingerbread build for the Sprint Tab. This is NOT an installable rom. This is a zip containing the compiled AOSP kernel and system, purely for research/development purposes. Download, unzip and play. I doubt this will boot on a CDMA device without the proper bootloaders, but you're welcome to try. You can even develop AOSP roms from it that will probably run on your tab after the update on the 5th. Enjoy.
Download​
Hope someone comes up with a great rom be it asop or other. Im truly looking for great things to come out of this.
Sent from my GT-P1000 using XDA Premium App
im expecting alot from these files!!!
a working 2.3 rom means the following for cdma tabs:
1.working skype video calls!
2.Working hulu!
3. Last but not least, Working Netflix!
it would make the tablet experience so much better for us CDMA owners.
i want to be the first to make a bug list on the first dev to release a rom
it would be a honor
and glad to see you finally posting something space. you have been in hiding so long, you rival osama lol
Argh, I wish I knew how to build roms >:|
kabuk1 said:
Argh, I wish I knew how to build roms >:|
Click to expand...
Click to collapse
im going to start reading this ebook i got.
its called:
learn android application development in 24 hours.
hopefully that would at least wet my feet.
man if I had broadband id have atempted to merge these into my cyanogen repo and make a build
Sent from my SCH-I800 using XDA App
wolfie083188 said:
im going to start reading this ebook i got.
its called:
learn android application development in 24 hours.
hopefully that would at least wet my feet.
Click to expand...
Click to collapse
For real? If so where can I get it.!?!?
EDIT : found it
Sent From My Evo using nanotechnology and incense!
has anyone tried just installing the kernel? anyone tried overwriting the last cdma cm7 build's system with this? anyone tried both? I'm going to see if I can get my hands on some internet soon but I might have me a date
Sent from my SCH-I800 using XDA App
Obama's>god said:
has anyone tried just installing the kernel? anyone tried overwriting the last cdma cm7 build's system with this? anyone tried both? I'm going to see if I can get my hands on some internet soon but I might have me a date
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
I guess I should add: you'll need the driver libs to get this running... you'll have to gank what you can from the gsm GB build. Stuff in /system/lib/hw and /system/lib/egl and so on. Just compare and you will get the idea.
spacemoose1 said:
For those of you that want to get in on early GB development but don't have the skill to compile it from source, I compiled the new source code that dropped for the gingerbread build for the Sprint Tab. This is NOT an installable rom. This is a zip containing the compiled AOSP kernel and system, purely for research/development purposes. Download, unzip and play. I doubt this will boot on a CDMA device without the proper bootloaders, but you're welcome to try. You can even develop AOSP roms from it that will probably run on your tab after the update on the 5th. Enjoy.
Download​
Click to expand...
Click to collapse
Thanks! This is useful. I am merging the CDMA kernel sources with GSM right now and the PowerVR module is updated so it looks like I will have to switch to newer OpenGL driver from this archive.
Technomancer said:
Thanks! This is useful. I am merging the CDMA kernel sources with GSM right now and the PowerVR module is updated so it looks like I will have to switch to newer OpenGL driver from this archive.
Click to expand...
Click to collapse
I hope it's useful. Sadly, the proprietary files weren't included in the source, so of course you'll have to patchwork from other builds or wait until the official release for some of those.
You're welcome though, glad to be of service.
spacemoose1 said:
I hope it's useful. Sadly, the proprietary files weren't included in the source, so of course you'll have to patchwork from other builds or wait until the official release for some of those.
You're welcome though, glad to be of service.
Click to expand...
Click to collapse
Yeah, I just noticed that, no EGL, etc. Maybe they put this stuff in /vendor now?
I just redid my Tab. I'm ready for Gingerbread on this *****.
It seems OTA may be pushed to some users now. Anyone care to rip all the files in /system and post them?
-d
technomancer
as soon as I get my update i'll help you out, just let me know how to rip my system, hell if i could dump my whole g-tab into an installable rom i would... still waiting on the push update, 7:02 PM EST, still no update! might be tomorrow!
x4gvnferdy said:
as soon as I get my update i'll help you out, just let me know how to rip my system, hell if i could dump my whole g-tab into an installable rom i would... still waiting on the push update, 7:02 PM EST, still no update! might be tomorrow!
Click to expand...
Click to collapse
Open adb shell and run this:
tar -czvf /mnt/sdcard/system_dump.tar.gz /system/
it will create file system_dump.tar.gz in on your sdcard with the contents of your factoryfs (system) partition.
alright! So when my update comes i will do just that and put it on my dropbox, providing you a download link!
Technomancer said:
Open adb shell and run this:
tar -czvf /mnt/sdcard/system_dump.tar.gz /system/
it will create file system_dump.tar.gz in on your sdcard with the contents of your factoryfs (system) partition.
Click to expand...
Click to collapse
Would the .zip update file help? I've got that posted on mediafire (as i just a little bit ago got the notice for an update. If it'll help, here's the link.
http://www.mediafire.com/?cngx5e67dgbq04y
Otherwise i'll get the update installed and see about running the sys dump as well.
pvtjoker42 said:
Would the .zip update file help? I've got that posted on mediafire (as i just a little bit ago got the notice for an update. If it'll help, here's the link.
http://www.mediafire.com/?cngx5e67dgbq04y
Otherwise i'll get the update installed and see about running the sys dump as well.
Click to expand...
Click to collapse
has anyone tested this? i don't wanna brick my tab!
I've got it up and running on my tab and there's at least 1 other person from this thread http://forum.xda-developers.com/showthread.php?t=1148447 that has it up and running as well.. Odin'd back to stock EA24, did the OTA EB28, and then ran the update.zip from stock recovery. All is happy on my tab. Now I just have to wait till i'm at work tomorrow to get ADB to work, and I'll dump /system.
Related
Hey guys!
i am very new at this but i have ported a build from fascinate over to our continuum and am looking for some devs to jump in and start helping me fix stuff.
this is very early but you can grab my first port here.
it is very much not ready for every day use.
Please flash if you are going to help me fix this for everyone
Code:
[B]
Rap sheet of things to fix will be here:
Screen placement overlaps the ticket screen, i was thinking we could
somehow code this thing so it will ignore the ticker
screen and only use the top.
Also we need to enable the soft keys.
Keyboard is non existent.
phone is not functional yet.[/B]
Well since this phone is virtually Unbrickable.... why not try our best.
Sent from my SCH-I400 using xda premium
Porting what build? Please tell me it's MIUI!
Sent from my SCH-I400 using XDA App
I've tried this before, and didn't get anywhere xP so, good luck
Sent from my SCH-I400 using xda premium
thanks for the well wishes... anyone know where to go in the rom to edit the screen dimentions yknow so it uses the top screen only? i think this is kernal
yea the problem with ports on the continuum is u cant flash mtd files in recovery a friend and i tried to port the fascinate miui 2.3.2 rom to the continuum we got everything resised and made it flashable but it just said installation aborted. the fascinate can flash mtd files straight from recovery and the continuum can not.
i still have all the files for miui if someone wants them pm me the problem is converting it to a .tar file so we can install via odin.
Bierce22 said:
yea the problem with ports on the continuum is u cant flash mtd files in recovery a friend and i tried to port the fascinate miui 2.3.2 rom to the continuum we got everything resised and made it flashable but it just said installation aborted. the fascinate can flash mtd files straight from recovery and the continuum can not.
i still have all the files for miui if someone wants them pm me the problem is converting it to a .tar file so we can install via odin.
Click to expand...
Click to collapse
mtd files? what's those for? the above build was ported from a fascinate rom. very asop
most roms use mtd sum to install everything im not going to go into detail about everything because i would just sound like an idiot lol.
Bierce22 said:
most roms use mtd sum to install everything im not going to go into detail about everything because i would just sound like an idiot lol.
Click to expand...
Click to collapse
lol i hear you, nah the above build ported fine.... no errors installing, i had to adjust scripting and also include imnut's kernal but it works. just need to fix stuff inside the rom
can u shed some more light on the rom such as is it froyo and aosp more information would be nice.
Bierce22 said:
can u shed some more light on the rom such as is it froyo and aosp more information would be nice.
Click to expand...
Click to collapse
sure, gimme a few and i'll update post 1, last night late i posted it with minimal info then went to bed...
alright here goes nothin im going to see what happens lol
The demensions seem to be within the framework, or at least the call to the kernel for the screen size..
So porting it is pointless, because you'll have to modify the framework back to the continuum's which would defeat the point...
As far as I think/know
That is actually why I stopped
But, feel free to prove/show me up
Sent from my SCH-I400 using xda premium
it does boot but i couldnt even get to settings and about phone to tell what it was and he still hasnt updated the op yet.
Yeah, i know it boots, haha.. I did this like two months ago
But the screen isn't divided properly for the ticker/softkeys... And won't be unless you can find the right part to edit
What language are we talking about? If it's Java I'm happy to help.
Sent from my SCH-I400 using XDA App
trailblazer101 said:
Yeah, i know it boots, haha.. I did this like two months ago
But the screen isn't divided properly for the ticker/softkeys... And won't be unless you can find the right part to edit
Click to expand...
Click to collapse
From what I have seen, in other posts about other phones, the screen size is written into the kernel. So, to do this, we need the source code for the kernel.
joshkoss: Great effort, but to do any serious mods, we must have the kernel source code. Without that, there is no way to compile the fixes/changes into the kernel. I have been able to use modprobe to do a few things, but, generally, the modules must be compiled against the source code of the kernel to work properly.
If someone can get us the kernel source code, we will be golden... Up until then, porting anything is not going to be fun.
If one was REALLY interested in doing this, one would take the generic Gingerbread kernel and ROM and work a build from the ground up that way. Especially since I don't think Samsung, nor Verizon will be handing out the kernel source code.
There is an off chance that Samsung might give the Continuum kernel source code to a developer AFTER Verizon sunsets this phone... (It's a very remote chance...)
Verizon gave me this number for the Samsung Mobile Helpline: (888) 987-4357. I haven't called them yet, but if enough of us call, someone MIGHT be able to knock something loose... Who knows. Let me know if I can help... This phone is my only phone, so I can't go flashing it every night to try things, but, over the weekend, I can try things.
Ciao!
I agree...collectively we should be capable of anything...even gettn sammy source...sumhow
sent from my XDA phone - its more than a continuum
I for one think y'all can do anything. Y'all have already done so much and I really think y'all are on to something huge!
Put a thread on cyanogen.com asking for assistance with this topic. What do you guys think of doing a donation pool to get a build working on our device?
Contents:
Android 4.0.4/IMM76D deodexed ROM in flashable ZIP format. Will not produce errors when decompiling APK/JAR files.
Includes Superuser and boot.img root-level access. Does not include radio or recovery.
Changelog:
[R1/02APR2012]: ROM base changed from 4.0.4/IMM26 to 4.0.4/IMM76D. Files updated from stock IMM76D listed below.
Updated File List:
system/app/GoogleEarth.apk (v.6.2.1.6363 :: Earth)
system/app/googlevoice.apk (v.0.4.2.54 :: Voice)
system/app/Maps.apk (v.6.5.0 :: Maps)
system/app/Phonesky.apk (v.3.5.15 :: Play Store)
system/app/Wallet.apk (v.1.1-R57v4 :: Wallet)
system/lib/libearthmobile.so
Notes:
The need to wipe data beforehand is dependent on which ROM you're already using, but is advisable when possible for the sake of simplicity.
[R1] http://www.mediafire.com/file/48w84r8v3qbb8bw/NS4G-4.0.4-IMM76D-DEODEX-R1.zip
So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.
ssconceptz said:
So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.
Click to expand...
Click to collapse
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.
So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium
Killasmoke said:
So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
The procedures are the same as for other ZIP-based ROMs: download, transfer to phone, and flash through recovery. You may or may not need to erase your data (depending on which ROM you're coming from), but backing up your data beforehand is advisable and never hurts.
I haven't received any feedback regarding this specific ROM yet (I don't know if that's a good or bad sign). The main difference is that it's deodexed and will decompile without errors. I'm sure there are other threads with more in-depth information on IMM26 changes/improvements/issues.
SuperUser
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.
mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.
I went to nexusshacks.com and downloaded the nexussrootICS.zip file (I think that's what its called). There's a SuperUser.zip file within that zip file. I moved the file to my phone and flashed it in recovery (wipe cache and dalvik cache of course). And its working well.
Sent from my Nexus S 4G using XDA App
mvilla8 said:
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.
Click to expand...
Click to collapse
Thanks for bringing that to my attention. Uploaded an updated version in the OP that addresses the Superuser issue. Sorry for the inconvenience.
satuday said:
mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.
Click to expand...
Click to collapse
This update is from ChainsDD's site and has the latest Superuser app and binary. Should accomplish the same thing.
XK72 said:
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.
Click to expand...
Click to collapse
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?
I guess the Google Apps are included?
Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.
Been using this since the 9th and I have to say it's very smooth. Very stock too, which obviously is what it's supposed to be. Just saying that for anyone who comes in looking for something customized. This is basically pure vanilla ICS.
Sorry for the delayed replies. I've been hammered by other obligations lately.
sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
mabry said:
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?
Click to expand...
Click to collapse
I'll try my best to post the steps later today or tomorrow. Sorry to keep you waiting.
akabadnews said:
I guess the Google Apps are included?
Click to expand...
Click to collapse
The stock Google apps are included. There are now two choices: One has the apps that were included in the IMM26 release (R3) and I have also included the latest app updates and related binary files as (R4).
The Batman said:
Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.
Click to expand...
Click to collapse
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.
I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium
xamadeix said:
I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Sorry about that. I don't know what happened there. Link fixed.
XK72 said:
Sorry about that. I don't know what happened there. Link fixed.
Click to expand...
Click to collapse
Thank you
Sent from my Nexus S 4G using xda premium
Does anyone have problems turning Bluetooth on?
Sent from my Nexus S 4G using Tapatalk
XK72 said:
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.
Click to expand...
Click to collapse
I would rather have the straight vanilla experience. Thanks for responding.
Edit: Also, touch to focus would be nice for the camera if at all possible. Thanks.
Please keep in mind this is a work in progress and is currently intended for devs only. Do not flash if you don't know what you're doing.
Ok, after making some progress towards getting this thing ready for user-space, I've decided to finally start a thread on it just to see if I can get anyone interested or willing to help... This ROM is currently in below Alpha status (if there is such a thing) and does not boot, but I believe I can get it booting in about a week barring a system crash or a zombie apocalypse. Again, this is only meant for a jumping off point towards getting AOSP ICS on our I957s, so don't blame me if you flash this and your tab becomes bricked...
Source
Link to source ------> Here
Github
Link to Github ------> Here
Want to Help?
Code:
Downloading and Building from Source
Edit
Follow the Repo instructions to download and install Repo.
Download the Android source tree by specifying the branch and manifest for a specific Code Aurora release. In this example the download the carrot.cupcake branch using manifest ''M7201JSDCBALYA6380.xml''
$ repo init -u git://codeaurora.org/platform/manifest.git -b ics -m M8260AAABQNLZA30120.xml --repo-url=git://codeaurora.org/tools/repo.git
$ repo sync
Build the source tree
$ source build/envsetup.sh
$ choosecombo 1 1 msm8660_surf eng
$ make -j4
Running choosecombo with no arguments will prompt for Android build options and target.
Downloads
Link to ROM------> Here
Thanks to Da_g for the kernel base, and thanks to the people at Code Aurora for the msm8660 source.
Great stuff jo
Sent from my SAMSUNG-SGH-I727 using xda premium
Sweet, Thank you for start a build for i957 and Finally about time!
great start, thank you!!!!
MaX
Great news, keep up the good work.
Yes thank you very much for this start!
ICS for i957?
I'm ready to test when you have a bootable ROM! Where are you getting ICS-compatible hardware drivers for the i957?
Thanks
phil_white99 said:
I'm ready to test when you have a bootable ROM! Where are you getting ICS-compatible hardware drivers for the i957?
Thanks
Click to expand...
Click to collapse
Base drivers can be used from the msm8660 ics source code provided by Code Aurora, and proprietary can be used from the stock Honeycomb firmware. Hopefully.
1. THANKS JO!
2. In order to boot, what is needed?
I'm assuming this is a CWM zip, not an odin package, right>
With ics for the skyrocket leak hopefully things will get easier
Sent from my SAMSUNG-SGH-I727 using xda premium
Thank You. Hell yeah! You guys rock. I'll help out if I can.
I'm willing to test too.
hey Jo there are some ICS CWM roms starting to come out for the skyrocket (ICSMOD5 is what I was looking at). Do you think with some script edits this could be flashed to the i957?
thanks to OP for attempting this. there are enough of us i957 users out there I think !
orlandoxpolice said:
hey Jo there are some ICS CWM roms starting to come out for the skyrocket (ICSMOD5 is what I was looking at). Do you think with some script edits this could be flashed to the i957?
Click to expand...
Click to collapse
Yes, but the problem is we would probably need our own ICS kernel to get most of the stuff working. I'll try my hand at ICSMOD5, but I'm not sure if anything will work without a dedicated kernel.
jomeister15 said:
Yes, but the problem is we would probably need our own ICS kernel to get most of the stuff working. I'll try my hand at ICSMOD5, but I'm not sure if anything will work without a dedicated kernel.
Click to expand...
Click to collapse
yes you are right about that, but i think the tmobile guys got ics running with the skyrocket kernel but they are having issues with data.
orlandoxpolice said:
yes you are right about that, but i think the tmobile guys got ics running with the skyrocket kernel but they are having issues with data.
Click to expand...
Click to collapse
Ok, I'm not really going to be able to use my tab for dev purposes this weekends, but if you want to try a port here's what you need to do.
1) Setup a build enviornment in dsixda's kitchen with ICSMOD5.
2) You'll need to look at the updater-script and change the partition blocks according to the Tab (e.g system needs to be 25 instead of 24).
3) Two ways to do 3. One: grab the kernel from this thread and put it in ICSMOD, or Two: You could just leave the kernel as is. I'm wary of option Two.
4) Flash it. If it doesn't boot, try to get a logcat and send it my way. If it does, then yay ICS.
jomeister15 said:
Ok, I'm not really going to be able to use my tab for dev purposes this weekends, but if you want to try a port here's what you need to do.
1) Setup a build enviornment in dsixda's kitchen with ICSMOD5.
2) You'll need to look at the updater-script and change the partition blocks according to the Tab (e.g system needs to be 25 instead of 24).
3) Two ways to do 3. One: grab the kernel from this thread and put it in ICSMOD, or Two: You could just leave the kernel as is. I'm wary of option Two.
4) Flash it. If it doesn't boot, try to get a logcat and send it my way. If it does, then yay ICS.
Click to expand...
Click to collapse
OK I have followed these instructions; downloaded ICSMOD5, set up the kitchen, grabbed the kernel (assuming that's boot.img) from your zipfile in the first post of this thread and copied it to the working folder, overwriting the Skyrocket kernel.
Then I looked at the updater script to see if partitions need changing. Per this post the layout looks OK. Example: /system is p24 and /boot is p08 already.
So far so good? Planning a test for later today.
Exciting let me know how it goes
Sent from my SAMSUNG-SGH-I727 using xda premium
Also don't use the default generated kitchen updater script
Sent from my SAMSUNG-SGH-I727 using xda premium
In case anyone is having trouble finding toro as a device target when trying to build from the list of targets from the 'lunch' command... Toro didn't show up in the list but I was able to manually specify it rather than selecting a numeric option.
Devs probably know that works, but amateurs like myself might benefit from that tidbit. Jellybean seems to be building OK for me now.
EDIT: I was asked what I did, more specifically, so I'll put that here in op:
Rather than enter a numeric choice, I entered 'full_toro-userdebug'. Apparently this was a valid response and the build proceeded.
Mind explaining how you manually selected it?
keith.mcintyre26 said:
Mind explaining how you manually selected it?
Click to expand...
Click to collapse
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.
question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?
spunks3 said:
question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?
Click to expand...
Click to collapse
It's not as 'polished'. There are no gapps, the dictionary is not complete (need a version from a factory image/rom), there are extra keyboards (Japanese?), maybe a couple other oddities as compared to a stock ROM. It will certainly be more capable that porting a gsm rom to toro, that's for sure .
mmuzzy said:
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.
Click to expand...
Click to collapse
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium
keith.mcintyre26 said:
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You're very welcome. Happy flashing.
I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
mmuzzy said:
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
Click to expand...
Click to collapse
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was actually trying to pull it before Google was finished so it hasn't been that long.
Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?
anton2009 said:
Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?
Click to expand...
Click to collapse
Lol!
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
Lol!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this
Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?
cdrshm said:
Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?
Click to expand...
Click to collapse
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!
CPCookieMan said:
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!
Click to expand...
Click to collapse
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.
i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
mwalt2 said:
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.
Click to expand...
Click to collapse
cdrshm said:
i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
Click to expand...
Click to collapse
For future reference, what he's referring to is the extract-files.sh script included in the CM source. If you cannot find the proprietary binaries for a certain device you wanna build for, plug in the phone via usb, cd to the directory with the script and execute the command.
anton2009 said:
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this
Click to expand...
Click to collapse
I also got version 4.0.9.99.999.9999.99999 when I synced to the master branch. Thanks for mentioning the workaround to sync with 4.1.1_r1 .
Did you figure out if it's a problem to sync 4.1.1 into a directory that's already synced with master (4.0.9.99...)?
--------------------------------
Update: I think I can answer this question based on JBQ's response:
https://groups.google.com/d/msg/android-building/rtH5ZbJC7qU/-N1lr9MqexYJ
"You can also switch in place: just run "repo init -b <new_manifest_branch>; repo sync" in your existing client."
Sounds like syncing to a new branch in the same working directory should work just fine.
For those who prefer open source builds, rather than "Factory Images", here is a zip which is a stock, AOSP 4.3 build, straight from source. Why post this when anyone could make it? Well, it seems Google messed up their binary drivers, so it took me a little while to fix them, and fix the problems and get the ROM booting (they put the wrong mali GLES driver in their blob package).
Anyway, I have fixed that, and made it build successfully, so without futher ado, an AOSP (no google proprietary apps etc) build of 4.3 for the Nexus 10. The fixed vendor blobs are available at https://github.com/pulser/vendor_samsung_manta for anyone wanting to build themselves, and all can be verified, as they came from the "Factory Image" of 4.3 for the Nexus 10.
This is a pure AOSP build, there is no boot animation or any other "Google" things - just a plain, pure, AOSP build.
Enjoy, and this can be rooted using Chainfire's current 4.3 root method using SuperSU, which is detailed at https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Feel free to use, share, re-use, distribute, copy, paste, mirror, ignore, root, tweak, patch or mod. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this
Tested:
Wi-Fi
Bluetooth
GPS
Auto rotation
Accelermeter
Magnetic Field Sensor
Brightness Sensor (and Autobrightness)
Barometer
Seemingly not working:
Proximity sensor (not detected, but apparently has one)
Download:
http://goo.im/devs/pulser/Nexus10
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
duarian said:
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Stock image isn't the AOSP?
I am not worrying.
Thanks OP.
duarian said:
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Nothing to worry about. I took the RIGHT driver from the factory image (stock image).
The AOSP release they made had wrong blobs, I rectified it with the correct files from the stock image.
I missed a blob:
https://github.com/pulser/vendor_samsung_manta/commit/4c534c24407a163bc16bfa24cb769aef7ab9ebd3
Push to /system/vendor/lib/
pulser_g2 said:
I missed a blob:
https://github.com/pulser/vendor_samsung_manta/commit/4c534c24407a163bc16bfa24cb769aef7ab9ebd3
Push to /system/vendor/lib/
Click to expand...
Click to collapse
How do we download the file/blob please?
Never downloaded anything from Github before...
pulser_g2 said:
For those who prefer open source builds, rather than "Factory Images", here is a zip which is a stock, AOSP 4.3 build, straight from source. Why post this when anyone could make it? Well, it seems Google messed up their binary drivers, so it took me a little while to fix them, and fix the problems and get the ROM booting (they put the wrong mali GLES driver in their blob package).
Anyway, I have fixed that, and made it build successfully, so without futher ado, an AOSP (no google proprietary apps etc) build of 4.3 for the Nexus 10. The fixed vendor blobs are available at https://github.com/pulser/vendor_samsung_manta for anyone wanting to build themselves, and all can be verified, as they came from the "Factory Image" of 4.3 for the Nexus 10.
This is a pure AOSP build, there is no boot animation or any other "Google" things - just a plain, pure, AOSP build.
Enjoy, and this can be rooted using Chainfire's current 4.3 root method using SuperSU, which is detailed at https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Feel free to use, share, re-use, distribute, copy, paste, mirror, ignore, root, tweak, patch or mod. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this
Tested:
Wi-Fi
Bluetooth
GPS
Auto rotation
Accelermeter
Magnetic Field Sensor
Brightness Sensor (and Autobrightness)
Barometer
Seemingly not working:
Proximity sensor (not detected, but apparently has one)
Download:
http://goo.im/devs/pulser/Nexus10
Click to expand...
Click to collapse
Is this why the latest version supported for manta is 4.2.2r1 (according to this) while everything else is 4.3xx?
Explains why I can't get a flashable build.
This is why I stick to factory images.
ridobe said:
Is this why the latest version supported for manta is 4.2.2r1 (according to this) while everything else is 4.3xx?
Explains why I can't get a flashable build.
Click to expand...
Click to collapse
It may well be, but the factory image is available.
But some of us don't want GApps, and don't want binary parts (save for the necessary evil of drivers), which is where AOSP builds come in.
pulser_g2 said:
It may well be, but the factory image is available.
But some of us don't want GApps, and don't want binary parts (save for the necessary evil of drivers), which is where AOSP builds come in.
Click to expand...
Click to collapse
Thanks. I like to build for myself but couldn't figure out why I couldn't flash successfully. Upon further investigation it appears that it is not supported (yet) in aosp. I'm running the factory images for now instead. However, this evening I'm going to flash this.
I just want to make sure. This wont wipe my internal hard drive. First time i flashed the new 4.2 i lost everything and cant backup anything as of now because i am outta town the whole summer.. Plz if anybody can confirm
Sent from my Nexus 10 using Tapatalk HD
BabyHuey said:
I just want to make sure. This wont wipe my internal hard drive. First time i flashed the new 4.2 i lost everything and cant backup anything as of now because i am outta town the whole summer.. Plz if anybody can confirm
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am not aware of anything to deliberately wipe /data, but I strongly suggest you don't flash this, unless you are willing to lose things? Why? because I didn't test every possible situation that could come up. I also didn't CHECK that /data remained...
So perhaps take the OTA (if you're on stock)? Or just hang off? It's nothing hugely special in my opinion.
pulser_g2 said:
I also didn't CHECK that /data remained...
Click to expand...
Click to collapse
It does, I flashed it.
Would still like to know how to get those missing blobs...
stonebear said:
It does, I flashed it.
Would still like to know how to get those missing blobs...
Click to expand...
Click to collapse
So nothing will be wiped?
Sent from my Nexus 10 using Tapatalk HD
BabyHuey said:
So nothing will be wiped?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
My data remained, but I would be concerned if you took a chance on my say so and something went wrong. I was ok but maybe you wouldn't be for some reason.
Sent from my Nexus 7 using Tapatalk 4 Beta
stonebear said:
It does, I flashed it.
Would still like to know how to get those missing blobs...
Click to expand...
Click to collapse
Which ones? The blobs are in the github link and came from the factory image. I'm not aware of any missing ones.
pulser_g2 said:
Which ones? The blobs are in the github link and came from the factory image. I'm not aware of any missing ones.
Click to expand...
Click to collapse
I don't know how to download them. Are they downloadable?
I suppose if I could understand the page I would know which ones to take from the factory image...noob, sorry.
Is it just "libRSDriverArm.so"?
http://d-h.st/aPi
4.3 gapps
Sent from my AOSP on Manta using Tapatalk HD
Thanks pulser_g2 for adding the correct binary blobs! Glad I'm not completely insane like I thought I was, I too noticed that Google had forgotten to provide the correct graphics driver binaries so I tried building 4.3 with the 4.2.2 graphics binaries and it not surprisingly didn't boot past the Google logo. Glad we could get this fixed :good:.
stonebear said:
I don't know how to download them. Are they downloadable?
I suppose if I could understand the page I would know which ones to take from the factory image...noob, sorry.
Is it just "libRSDriverArm.so"?
Click to expand...
Click to collapse
Sure, that is the only "blob" I am aware I forgot. The N10 supposedly supports Bluetooth 4 (LE), but I have no idea how to test it, as I don't have any Bluetooth 4 LE devices. Can anyone test that? I will update the system.img today for you to make it easier It was only one blob I missed, and it only affects using front facing camera I believe.