NOTE: THIS ROM IS NOT CURRENTLY USABLE! DO NOT FLASH IF YOU DO NOT KNOW WHAT YOU ARE DOING
Ladies and gentlemen of XDA, I present to you ICS on the TF101! This ROM is currently very much still in development, and is not usable in it's current state, but it boots! This is more or less a proof of concept at the moment.
What's not working:
Display has a green overlay most of the time
Touchscreen
Wifi
Camera
HW Acceleration
Pretty much everything else
What does work:
adb
Boots to launcher
Touchpad on the dock (currently only method of input)
To install:
Download the system blob from http://mirror.mostoftheinternet.com/android/ROM/tf101/system-AOSP-20111230.blob.bz2
Boot into recovery
Do factory reset
Mount /sdcard using the menu
Use adb to transfer the blob to the device
Code:
adb push system-AOSP-20111230.blob.bz2 /sdcard/blob.bz2
Enter device shell
Code:
adb shell
Decompress blob and apply
Code:
bzcat /sdcard/blob.bz2 | dd of=/dev/block/mmcblk0p4
Reboot and wait for it to install
Done!
If you are able to contribute at all, please let me know. The Git repo for this is at https://github.com/Deathisfatal/android_device_asus_tf101/tree/cm9.
Dev notes:
Most of the random crashes (and the green colour) seem to be caused by an issue with the graphics
Eventually, I plan to move to CM9 once they move closer to release
Screenshot! (yay, green...)
http://mirror.mostoftheinternet.com/images/ics.png
this
is
sex
Congrats
Sent from my MyTouch_4G_Slide using xda premium
Are you going to setup a repository for this? I was actually planning on starting a port of my own but I would love the opportunity to jump in and work with you.
Already have, forgot to add it to the post
Thanks for the support, guys.
Nice to finally see even an early build as this, well done i`ll be keeping an eye on this thread
Deathisfatal said:
Eventually, I plan to move to CM9 once they move closer to release
Click to expand...
Click to collapse
This would make my day! If we manage to get CM9 to start working, I would love to help try or try to be the main man behind porting MIUI (English Site). I've helped a decent bit with porting it to my phone (Samsung Epic 4G). From everything i've seen so far the kernels of CM7 and MIUI are pretty much interchangeable, so it should be a fairly easy transition if CM9 functions. I don't know squat about kernels, so i wouldn't be of any help there though.
UH i had this like 3 weeks ago, but didn't post cuz it sucked so much.
Here's mine, no green stuff either.
I also didn't post it because it's a straight up kang of the Iconia guys' but whatever.
LOL
Thanks to OP for your hard work...
www.scienceprousa.com/jcarrz1/icstest.zip just flash in clockwork but don't expect much...........
Mind sharing your vendor files, jcarrz1?
Deathisfatal said:
Mind sharing your vendor files, jcarrz1?
Click to expand...
Click to collapse
Nope cause it's a straight-up kang of the iconia guys'. And they took their source down because n00bs b crazy.
I really admire that you actually have a device tree and stuff, I'm too inexperienced to do that.
Nice!
jcarrz1
Maybe this may help? https://github.com/CyanogenMod/android_device_asus_tf101
Was going to start an ICS port today as well so I'll be forking your branch and hopefully helping out. Glad we are going to get some progress on this!
arayray said:
Maybe this may help? https://github.com/CyanogenMod/android_device_asus_tf101
Click to expand...
Click to collapse
My original code is a fork of that. Their repo is pretty incomplete.
Was going to start an ICS port today as well so I'll be forking your branch and hopefully helping out. Glad we are going to get some progress on this!
Click to expand...
Click to collapse
Excellent!
Deathisfatal said:
My original code is a fork of that. Their repo is pretty incomplete.
Click to expand...
Click to collapse
Yeah its pretty outdated... Lets get a community effort here..
Good to see a start on this, a bit later than expected!
Sent from my Transformer TF101 using xda premium
For the graphics drivers, as the tf101 uses the same SOC as the xoom, it might be possible to pull the tegra2 drivers from google's wingray aosp sources (found here)
First of all for your work
You know what i dont get is this
http://phandroid.com/2011/11/27/asus-transformer-not-prime-gets-early-ics-port/
where is bumbledroids work?(this was november still)
i am a total retard when it comest od developing but if you ever need any beta tester i have loads of experience on rooting/romming devices an am in possesion of a SBK1 asus transformer with keyboard.
looking forward to giving it a go
Sent from my Lumia 800 using XDA Windows Phone 7 App
Are you compiling against AOSP or CM9?
telsk said:
First of all for your work
You know what i dont get is this
http://phandroid.com/2011/11/27/asus-transformer-not-prime-gets-early-ics-port/
where is bumbledroids work?(this was november still)
i am a total retard when it comest od developing but if you ever need any beta tester i have loads of experience on rooting/romming devices an am in possesion of a SBK1 asus transformer with keyboard.
Click to expand...
Click to collapse
Right, and if the cyanogenMod device tree for tf101 is by bumbledroid then why doesn't touch work yet?
jcarrz1
Related
This is a little port I made that came from this thread on the HTC Desire: Here
Most of the work goes to coolexe for the Desire ROM I ported this from and bypass23 for the original Honeycomb ROM on the Nexus One. Also credit goes to s0be for his AP4 kernel I am using with this ROM and arodey for his Honeycomb Boot Animation. In this port I also KANGED modules and various other files for our little Hero from CM Nightly #62 by Cyanogen and the CyanogenMod team. I've taken this as far as I could for personally I have no dev skills as well as that the Honeycomb source code has yet to be released. Once it is, much more will be able to be completed.
What Works:
-Honeycomb UI when I changed lcd density to half of original
-Touchscreen (If you seem to lose press search button then back button)
-USB Connection
-LED's
-Settings
-Rotation (Have to enter camera app in landscape and exit to go to landscape [Stuck in Landscape until reboot])
What Doesn't Work:
-Audio
-Wifi
-Camera
-SD Mounting
-Data Connection
-SMS
-Calls
-Gallery (FC's when selecting)
-And many more.
Download here: http://www.mediafire.com/?e8etyxuein8vme2
whoa! No kidding! I'm down to test.
AND FIRST!
etstanger said:
whoa! No kidding! I'm down to test.
AND FIRST!
Click to expand...
Click to collapse
This ROM is NOWHERE near being used as a daily because so much doesn't work, more of a proof of concept.
etstanger said:
whoa! No kidding! I'm down to test.
AND FIRST!
Click to expand...
Click to collapse
I JUST ASKED ABOUT THIS LITERALLY LIKE 10 SECONDS AGO AND YET HERE IT IS!!!!!
I am truly in love with xda now because the response to questions and wishes are so fast....THANK YOU! Downloading now.....its a race to the first tester boot hehehe
dastin1015 said:
This ROM is NOWHERE near being used as a daily because so much doesn't work, more of a proof of concept.
Click to expand...
Click to collapse
Yeah I know, but i wanna see it on my hero.
etstanger said:
Yeah I know, but i wanna see it on my hero.
Click to expand...
Click to collapse
Same here....i don't care what doesn't work...i just want it to boot so i can jump for joy
edit: booting it now although 2 minutes have passes already.....
htckid07 said:
Same here....i don't care what doesn't work...i just want it to boot so i can jump for joy
edit: booting it now although 2 minutes have passes already.....
Click to expand...
Click to collapse
Yeah it takes a bit to boot up the very first time. After that it gets faster. I'm going to reflash to see the boot time for first boot.
dastin1015 said:
Yeah it takes a bit to boot up the very first time. After that it gets faster. I'm going to reflash to see the boot time for first boot.
Click to expand...
Click to collapse
timed it on stock hero phone hardware (i just got it today)...its 2 minute 23 seconds for me
and yes it is slow.....but hey i just p!ssed in my pants thanks to this rom
....now i'll be going to change my pamper again so i can reboot and do it all over again
htckid07 said:
timed it on stock hero phone hardware (i just got it today)...its 2 minute 23 seconds for me
and yes it is slow.....but hey i just p!ssed in my pants thanks to this rom
....now i'll be going to change my pamper again so i can reboot and do it all over again
Click to expand...
Click to collapse
I have 1 min 10 sec to boot animation and 2 min 37 sec to lockscreen. I've had my Hero since October of 2009. Results may vary.
i was just asking about this today but what could i do to help the development of this? i know what porting a rom is but what could i do to help you out? and what is kanging?
htckid07 said:
i was just asking about this today but what could i do to help the development of this? i know what porting a rom is but what could i do to help you out? and what is kanging?
Click to expand...
Click to collapse
Development wise we would need to get the apps to work on here and various other changes and get files specifically build for Honeycomb rather than the Gingerbread Cyanogen files. Also get things like Calls, SMS, MMS, Data working.
KANGED - To have one's developer code and work taken, manipulated, rebranded, and re-released by someone else with no credit.
But here I gave credit to the author of those files which is Cyanogen and the CyanogenMod Team and I got those files from the heroc CM Nightly #62.
dastin1015 said:
Development wise we would need to get the apps to work on here and various other changes and get files specifically build for Honeycomb rather than the Gingerbread Cyanogen files. Also get things like Calls, SMS, MMS, Data working.
KANGED - To have one's developer code and work taken, manipulated, rebranded, and re-released by someone else with no credit.
But here I gave credit to the author of those files which is Cyanogen and I got those files from the heroc CM Nightly #62.
Click to expand...
Click to collapse
im still new to this a bit and after a bit of googling "port rom android" it seems to me that .so files for the lib folder are somehow involved in this....so i guess i could around town on the forums and gather a lot of .so files, take names for who they came from, and just play the guess and check game....would that work for fixing something? or is porting much more complicated?
i don't know if i said this but thanks
htckid07 said:
im still new to this a bit and after a bit of googling "port rom android" it seems to me that .so files for the lib folder are somehow involved in this....so i guess i could around town on the forums and gather a lot of .so files, take names for who they came from, and just play the guess and check game....would that work for fixing something? or is porting much more complicated?
i don't know if i said this but thanks
Click to expand...
Click to collapse
We would actually have to build files for our phone. Copying and pasting lib files is not going to get things working on our Hero. Much more complicated process. As I have no dev skills, I wouldn't know the process do such work. Various .so files work for the version they were built/complied for and are not specifically going to work for another.
Edit: Also much of this cannot be fixed until the source code is released. This is more of a tease before source code comes out.
dastin1015 said:
We would actually have to build files for our phone. Copying and pasting lib files is not going to get things working on our Hero. Much more complicated process. As I have no dev skills, I wouldn't know the process do such work. Various .so files work for the version they were built/complied for and are not specifically going to work for another.
Click to expand...
Click to collapse
hmm so this is beyond what i've read up as far as porting a rom then....okay i guess i'll just be a tester for this rom and i can confirm that your first post is correct as to what is and isn't working. now back to google search and xda search to figure out how are all the people on xda doing this rom/theme/mod stuff. i'm going back to aosp now but i had to try this and i'll test if you need a tester
OMG
*.* this is unbelieveable
;; Not Booting.
First a GingerSense port then a AOSP OMGB port and now a Honeycomb port?! Man im definitely have to test this!
cant wait to try this
This weekend freakin rocks!!!!! So many ROMs to try out. I feel like a kid in a candy shop.
Ohmyfudgelickngod :O I'm so down to test
Sent from my HERO200 using XDA App
this is awesome! What a way to end a perfect weekend can't wait to flash this
Sent from my HERO200 using XDA App
This is AOSP-4.0.1-R1, compiled and built for the HTC Sensation 4G (should work on the regular HTC Sensation too).
You can follow progress on Twitter.
Update (11/30/2011): We're not dead! New builds incoming soonish. For now look to the latest pages and grab stoneyjonez' build.
This is a REALLY early build - almost nothing works properly yet.
Huge props and thanks to stoneyjonez for providing and modifying the device configuration for pyramid. Also for continued help/assistance - we're basically working on this together.
This is the *development thread* - please go here for discussion and help flashing it. If you are about to tell us "X device has ICS, you should use their ROM!", put it in the god damn discussion thread. DO NOT post it here.
Credits:
- CM7.1-SELFKANG-Alphafied 10 for HTC Sensation, for providing some libs, device configuration and a clean AOSP-ish ROM
- AOSP, obviously
- stoneyjonez for device config
- Practically everyone in this thread (the SDK port for the Sensation)
- dsixda's kitchen, for making the packaging easier.
Working:
- Boots
- Displays some graphics (though they are torn diagonally and basically unusable)
- Hardware controls (volume up/down)
- TOUCHSCREEN, as of this post (Touches won't release yet, though)
Not working:
- Almost everything else
DO NOT FLASH THE RECOVERY IMAGE. We don't know what it does just yet.
Proper downloads:
test1 (AOSP, booting!): http://www.mediafire.com/?my054essk6g0le6
test3 (AOSP): http://www.mediafire.com/?8ynyror6mnkk5x1
test3.1 (AOSP kernel, rooted + busybox): http://www.mediafire.com/?e86zfv4avaxlo26
TEST3 won't boot or output to adb... cookies to anyone who can figure out why. I'm going to try and fix the touchscreen in test1, uploadable zip of test1 coming soon.
Click to expand...
Click to collapse
Pastebin from boot (test2): http://pastebin.com/HMQsNnNw
Oh yeah, lets get this started!
I would have hit thanks but I am limited to 5 per day lol. Can't wait for a stable release
System image with the changes is just about to finish - stay tuned for an updated build + flashable zip.
Very nice. How many Devs do you have working on this?
Knucklessg1 said:
Very nice. How many Devs do you have working on this?
Click to expand...
Click to collapse
So far two directly working on it, though probably like 8 if you count everyone in the SDK port thread.
Just got the stats for how long a full build takes for me:
real 72m53.054s
user 224m22.581s
sys 11m14.934s
This is with 8GB of RAM, though I probably have to downgrade to 6GB of RAM soon (someone else needs one of my 4GB sticks )
Nice job, its good to see more development happening here, it may be worth keeping an eye on the touchpad devs progress too due to their similar chipset
Jack E said:
Nice job, its good to see more development happening here, it may be worth keeping an eye on the touchpad devs progress too due to their similar chipset
Click to expand...
Click to collapse
I have a TouchPad, I might make a build for it once I'm happy here
Congrats Zorlin & team
Hopefully Nobody asks ETAs
Hopefully Nobody asks How to Install
Hopefully Nobody asks why their phone doesn't work after installing recovery
Thanks for the works, at-least we can start playing with it...
\Regards,
Nice to see a quick start on this, looking forward to observing development.
I know someone got the touchscreen working on the nexus one using this post Idk if its any help here
http://forum.xda-developers.com/showpost.php?p=18711543&postcount=55
Sent from my Nexus One using XDA App
zorlin said:
I have a TouchPad, I might make a build for it once I'm happy here
Click to expand...
Click to collapse
Oh, I love the sound of that offer.
My TouchPad w/ GB is still good but ICS could be even better.
Here's test3.
http://www.mediafire.com/?e86zfv4avaxlo26
It won't boot or output to adb... cookies to anyone who can figure out why. I'm going to try and fix the touchscreen in test1, uploadable zip of test1 coming soon.
If you flash the CM7.1-SKA10 kernel it will output to adb but still not boot.
zorlin said:
Here's test3.
http://www.mediafire.com/?e86zfv4avaxlo26
It won't boot or output to adb... cookies to anyone who can figure out why. I'm going to try and fix the touchscreen in test1, uploadable zip of test1 coming soon.
If you flash the CM7.1-SKA10 kernel it will output to adb but still not boot.
Click to expand...
Click to collapse
I have logcat working.
http://code.google.com/p/ics-sdk-port-sensation/downloads/list
Sent from my Sensation using XDA App
---------- Post added at 04:30 PM ---------- Previous post was at 04:18 PM ----------
xm0is3sx said:
I know someone got the touchscreen working on the nexus one using this post Idk if its any help here
http://forum.xda-developers.com/showpost.php?p=18711543&postcount=55
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Won´t work. HTC makes it really hard with all the changes they make for Sense, so most things will take more work than the Nexus line.
jassycliq said:
I have logcat working.
Sent from my Sensation using XDA App
Click to expand...
Click to collapse
Neat, how?
this is making me excited! Can't wait til more features are working so I can test it out!
Its in the update script. Sorry I think you´ll notice though, but right now I feel like crap :´( all of a sudden Im sick now :/
Great work zorlin.. Any way we can get the device config for pyramid... Would love to compile and give it a try.
Thanks !
So i can use this as daily driver?
I'm kidding
See page 19 for the seventh build.
Good job! Nice and clean in a new topic. KUTGW!
Sent from my HTC Desire using XDA App
Freaging sweet!
(sorry for spam but this is exciting)
Excellent stuff.
So will that mean close to full HWA?
If we're running any of the ICS builds which have the hardware hacks, this applies, right?
texasice said:
@ those who flashed Chaosz-X new kernel you need to remove this line from build.prop
Code:
ro.config.disable_hw_accel=true
Click to expand...
Click to collapse
@rootSU: I think it does, because it scores almost the same as GB Sense ROMs, and it gets pretty decent FPS at Quadrant (certainly smooth enough), so I think it works fine.
@pnw: haven't tested that, but you can give it a try, it seems pretty logical that it would help
Can't wait for the 3.0 kernel
Sent from my HTC Desire using XDA App
I flashed this on the p2 build, but my wifi would not turn on... I reverted back to my nandroid right before the flash...
sent from my HTC desire using xda premium
mattmanwrx said:
I flashed this on the p2 build, but my wifi would not turn on... I reverted back to my nandroid right before the flash...
sent from my HTC desire using xda premium
Click to expand...
Click to collapse
chaoz tried including the wifi module you use in the kernel in the system/lib folder? can't find it there on the newest kernel. This messed things up for tristan earlier
Oh crap, forgot to supply the bcr4329.ko indeed.
I'm going to try to get a running 3.0 by tonight, if I don't have it finished this evening, I'll upload the WiFi module from the build (using 2 different OS's to work on, Linux for compiling, and Windows for everything else, and working in Win is much easier for me ;p)
Edit: beginning with the really lame methods of getting 3.0 to run, first attempt is done I think, just copied over files, and modified some of them, nothing really special, starting compiling in 5 minutes.
I flashed over p2 with the camera fix and the camera no longer works. Should I reapply the camera fix?
*child said:
I flashed over p2 with the camera fix and the camera no longer works. Should I reapply the camera fix?
Click to expand...
Click to collapse
But does your wifi work? It didn't work for me...
Not too sure about the camera... it should work... as the added is just libs... the kernel does look at the libs, but doubt it would make a difference... just my guess...
sent from my HTC desire using xda premium
Wifi did not for me. Camera worked but I didn't test it extensively.
Sent from HTC Desire
Camera and wifi doesnt work But HW ac. is fine more speed
Wi-Fi also does not work
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
texasice said:
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
Click to expand...
Click to collapse
cant wait 3.0 kernel for n1
texasice said:
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
Click to expand...
Click to collapse
How could he even develop a linux kernel if he is better in using windows? Dont you have to be a kernel dev to do those things?
Some devs are crossing strange lines - 4 sure . Hope you get it done for our Nexus ONE my friend
cheers
sweet..kernel 3.0!!
waiting ..waiting..
bunnahabhain said:
How could he even develop a linux kernel if he is better in using windows? Dont you have to be a kernel dev to do those things?
Some devs are crossing strange lines - 4 sure . Hope you get it done for our Nexus ONE my friend
cheers
Click to expand...
Click to collapse
People start with windows at a young age
Sent from my HTC Desire using xda premium
Hi,
Nvidia has just release binary and tools to build ICS ROM for Tegar2 plateforme...
http://developer.nvidia.com/tegra-resources
Bye
looks like (a lot of) the stuff needed to get our own built AOSP image running properly on the TF101.
Who knows, we might see a proper ICS rom before Asus releases their own .
I cant wait to see a ics-rom on my TF101!
Sent from my Galaxy Nexus using xda premium
Ohhhh... Nice.... I'm new around here does the transformer have a dev that build aosp roms from source (not kanged)
That page has been around forever and doesn't have what is necessary to get AOSP on pretty much anything.
There's been a few accounts posting that all around the same time frame the last few days all over the Tegra based device forums.....hmmmmmm.
thanks for this!reading ics 3ad it seems that it isn't so usefull...(http://forum.xda-developers.com/showpost.php?p=21768082&postcount=361)what are you think about that?
They posted an ICS device image for ventana. We can pull the required binaries from there as a starting point rather than trying to get ICS to work with the binaries pulled from honeycomb.
I'm downloading it now.
Thanks for the post!
daoist said:
They posted an ICS device image for ventana. We can pull the required binaries from there as a starting point rather than trying to get ICS to work with the binaries pulled from honeycomb.
I'm downloading it now.
Thanks for the post!
Click to expand...
Click to collapse
...we already have binaries that work with ICS, I've had builds in the public with working (and very smooth) graphics for weeks. If these ones are comparable then it'll be a nice source to pull them from, build a ROM without having to pull from a device etc. but they don't make anything any easier as you suggest.
paulburton said:
...we already have binaries that work with ICS, I've had builds in the public with working (and very smooth) graphics for weeks. If these ones are comparable then it'll be a nice source to pull them from, build a ROM without having to pull from a device etc. but they don't make anything any easier as you suggest.
Click to expand...
Click to collapse
But isn't there a new kernel in there or something to help with the (deep) sleep problems? Or is the reference board too diferent from our TF101 board?
It's all quite helpful. Cribbing stuff from a working compile is going to be easier than doing it from scratch.
dipje said:
But isn't there a new kernel in there or something to help with the (deep) sleep problems? Or is the reference board too diferent from our TF101 board?
Click to expand...
Click to collapse
There's a kernel binary, sure. It won't run on the TF101 though because as you mention it's not the same board. Ok, maybe it would run, but if it does then it'll have all the wrong peripheral setup etc. The source for the kernel is (presumably) the same nvidia source that's been available for a while and is the basis of the TF101 kernel I've been working on, so it shouldn't be significantly different.
daoist said:
It's all quite helpful. Cribbing stuff from a working compile is going to be easier than doing it from scratch.
Click to expand...
Click to collapse
'Cribbing' what exactly? I'm not sure what you think you can usefully take from this.
paulburton said:
There's a kernel binary, sure. It won't run on the TF101 though because as you mention it's not the same board. Ok, maybe it would run, but if it does then it'll have all the wrong peripheral setup etc. The source for the kernel is (presumably) the same nvidia source that's been available for a while and is the basis of the TF101 kernel I've been working on, so it shouldn't be significantly different.
'Cribbing' what exactly? I'm not sure what you think you can usefully take from this.
Click to expand...
Click to collapse
All the proprietary binaries/configs/etc. The sort of stuff we'd pull via extract-files.sh. Right now you've done an excellent job building it up from what we had in honeycomb. Now we have known-good files from ICS.
daoist said:
All the proprietary binaries/configs/etc. The sort of stuff we'd pull via extract-files.sh. Right now you've done an excellent job building it up from what we had in honeycomb. Now we have known-good files from ICS.
Click to expand...
Click to collapse
Well, no. The _only_ things that I intend to use binaries for are the graphics drivers and bluetooth firmware. Bluetooth firmware doesn't care at all which version of android you're running, so we can ignore that. Which just leaves graphics drivers, which are already taken from an ICS ROM (fortunately the TF101 isn't the only tegra 2 tablet!).
This thread is no longer active. Jomeister plans to continue work on Evervolv. He will open a new thread for that purpose.
Introduction
The purpose of this thread is to coordinate work on the AOSP-based Evervolv 2.2 ROM for Skyrocket (and its sister, T989).
Skyrocket is not an officially supported ROM by Evervolv, but we have fully integrated device and vendor directories in their tree. Therefore we get fixes from the main tree and also have the ability to push fixes to Evervolv's tree. This is something we could never do when we worked directly off the Code Aurora source.
Our desire is to give the dev community a single codebase to coalesce around. Hopefully, with more devs working on the same project, we can progress faster towards AOSP.
To build, follow the instructions here (choose ev_skyrocket-eng at the lunch menu):
https://github.com/Evervolv/android
Or, the short, short version:
Run "repo status" and make sure you have no local mods.
Run "repo sync" and make sure it completes without error.
Run "rm -rf out" to remove any old compiled stuff
Run ". build/envsetup.sh" to set up your environment
Run "lunch ev_skyrocket-eng" to select the target
Run "make -j4 otapackage" (adjust -j option to match your # of processors)
What works:
2D/3D graphics, hw accel of gui, bluetooth, gps, nfc, wifi, sdcard (int+ext), MTP/PTP over USB
What doesn't work:
audio, calls, camera, cell data, sms, anything else you can think of
Issues are being managed on Github:
https://github.com/Evervolv/android_device_samsung_skyrocket/issues
Want a ROM link?
Then follow the instructions to build a ROM! The point, at this time, is to get devs involved in the process. The ROM is not ready for anyone to try out or use at this point. There are many problems left to solve.
Want to help?
Are you a dev with a Skyrocket and a burning desire to get AOSP for your phone? Please, check out Evervolv and start debugging! The Github Issues link above is a great starting point.
Jomeister and RaverX3X graciously agreed to join forces here. We hope other devs join too!
Current Dev Contributors:
jomeister15
RaverX3X
topprospect
Credit and Thanks:
Xboarder56 for the original Evervolv Skyrocket device tree
romracer for the unsecure mods to the ICS kernel
Changes Log:
04/11/12: Posted succint build instructions
04/11/12: Fixed unstable-ness of GUI (link)
04/06/12: Build now boots on its own boot.img (link)
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
BaconStep said:
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
yes because google has released 4.0.4 sources and ota updates to nexus.
wali01x said:
yes because google has released 4.0.4 sources and ota updates to nexus.
Click to expand...
Click to collapse
Sweet!
Sent from my GT-P7510 using XDA Premium HD app
Looks great, will try building/debugging when I get my Ubuntu box up again!
Sent from my SAMSUNG-SGH-I727 using XDA
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
giant420 said:
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
Click to expand...
Click to collapse
No stupid questions here. A fully compiled ROM like the ICS leak obscures a lot of the details about how to build the ROM from scratch. You have to reverse engineer a lot of what Samsung did to compile AOSP, plus how to avoid pulling in too much Samsung bloat code. Hope that helps.
more or less were going to keep as much samsung out of it as we possibly can . Yes u can kang in stuff from the leak but then that actually causes more issues in the long run then doing it right the first time ;P.
bsbachert said:
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
Click to expand...
Click to collapse
I think we as a community should still continue working on things such as CM9 and AOKP in addition to Evervolv, just to give people as many options as possible. The good thing that Evervolv device trees are very similar to those required by CM9 and AOKP, so with a few hacks here and there I'm sure we can get those building as well. I don't know about the other devs, but I definitely have enough time to collaborate on multiple projects, as long as I'm not the sole carrier.
ur killing me. I finally managed to get media server to stay up for msm8660 audio pulled from the leak with jos isotope a4 with some other libs and bins. acdb pulling audio policy was still a problem though.
This is definitely for the better though. I was uncomfortable with all those Samsung libs bins and blobs, especially after staring at them under IDA. like raver said it woulda been a nightmare later on.
This is great though, everyone on the same pile should make this go a lot faster.
im very excited for this.
What's IDA?
Sent from my SGH-T989 using XDA
Wow. This build is going to b epic! Can't wait guys. Nice work so far
LawStud3nt said:
What's IDA?
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Interactive_Disassembler
crazy what u can find in those blobs. helps a lot for debugging though
all I know is I love evervolv on my nexus one its super baller... Thanks to all 3 of you guys
Sent from my SAMSUNG-SGH-I727 using xda premium
Any updates? Got ants in my pants waiting for this one!
softballjunkee13 said:
Any updates? Got ants in my pants waiting for this one!
Click to expand...
Click to collapse
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
topprospect said:
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
OK...enjoy the holiday as well!