[ROM][DEV]CM 7.2.0 (Android 2.3.7) - Viewsonic ViewPad 7 & Variants

CM 7.2.0 Android 2.3.7:
CyanogenMod 7.2.0 port for FIH FM6 varaints.
Working:
USB
Sensors(partially)
GPS
Audio
Camera(partialy)
Wifi
OpenGL/graphics
Video Playback
Bluetooth
RIL
Bugs:
1) Front Camera is not working
2} Main Camera Zoom is not working for higher resolutions.Works upto some extent for QCIF
3)Portrait orientation is not proper.Some apps run upside down
4)Device suffers from very rare reboot due to kernel panic
Download Link:
ROM:
Code:
http://goo.im/devs/mb-14/viewpad7/cm-7-viewpad7.zip
GAPPS Package:
Code:
http://goo.im/gapps/gapps-gb-20110828-signed.zip
Installation:
Boot into CWM 5.0.2.8 recovery
Wipe DATA and Dalvik Cache
Flash ROM
Flash GAPPS package
For DEVS:
Here is my device config:
Code:
https://github.com/mb-14/android_device_viewsonic_viewpad7
Any help will be appreciated.
BUG REPORTING:
You must follow these instructions exactly, or I will ignore your requests. Provide the following information:
Report any customizations you have made to the ROM (themes, system apps, etc.)
Describe the problem clearly, including steps on how I can reproduce the issue.
Provide a logcat from your system taken just after the issue has occurred. To take a logcat, you enter this command from your PC: adb shell logcat -d >c:\logcat.txt.
Alternatively, if I ask for a radio logcat, this is the command: adb shell logcat -b radio -d >c:\logcat-radio.txt. Copy and paste this log to pastebin.com, and provide the link.
Send all this information to my email ID:[email protected] with subject as CMBUG
Credits:
CyanogenMod Team for their awesome ROM.
Goo-inside Team for providing their build server
Please donate to these people
Plea for help:
This project would not have been possible without the help of Goo-inside Me Team.
Now they require financial help for upgrading their servers.Please donate to them!!!
For more info check out their website: http://goo.im/

I am eager to test this beta build, and in anything i can help you with... im using a viewpad 7

Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?

WOw!!! I'm waiting.

s2k7 said:
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
Click to expand...
Click to collapse
Non-working functions are due improper implementation of hardware drivers(working on it)
Right now ill be commiting changes to the device config but due to hardware limitations
it takes lot of time to compile a build.
If you have sufficient hardware resources(RAM,space,cores)
you can clone my repo ,download and build the Cyanogenmod source and test it on your phone
PM me for any queries

s2k7 said:
Happy to be a beta tester.
I will settle up a ubuntu system to follow you. Please let me know what I can do.
All non-working functions are related with kernel?
Click to expand...
Click to collapse
+1, same here, can help debug the issues and work with adb.
Maybe an Irc channel for quicker contact?

cant wait for this. very willing to test

slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards

sirgawain123 said:
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
Click to expand...
Click to collapse
I'm think cause 2.3 and 2.2 have most possibility to use in stable. Viewpad 7 is to old to play around. And if this device have rom that can use maximum hardware's can do and stable. I think maybe we can see Viewpad7's ICS ROM in real life.
Sorry for my weak english.

sirgawain123 said:
slightly off topic from an android-noob: Why still Android 2.x.x?
Any hope of Android 4.x.x (ICS) in viewpad7?
Best regards
Click to expand...
Click to collapse
Tnie device seems too weak for ics, its a single core 600mhz armv6 CPU.

ics think it wil work on oure device it`s been ported too the x8 to and that`s a arm v6 600 mhz to,
but im happy with 2.3.7

Well, as long as I get 7.1 I'm happy. I still think having it ported is one thing but having it work flawlessly for everyday use is another.

Is wifi working yet? I've seen some commits on github but haven't seen any updates to the update.zip file in the first post.
*edit* where is the update.zip, exactly? Can't seem to find it on the first post anymore
Also, the sensors readout for screen orientation should be somehow flipped or mangled, for by default the device seems to be in landscape mode and if turned to portrait, it flips upside down for me.

hi
really appreciate you looking into porting this to the viewpad/variants etc
hope it goes well, looking forward to a little added ooompf,
(though [ROM]EUViewpad7 v1.7b has been great too)

@googlehome how's the progress?
@anyone I'm a programmer but i'm new to this android build compilation etc. Could anyone point me to tutorial or manual on how to these and those? Thx.

Yes, viewpad 7 seems to weak for ICS... We didn't even get honeycomb (3.X)

Dear Santa...
I'll be happy just with 2.3 and using my front camera with skype or gtalk...
Happy Holidays

Thank for hardwork

Hi
I think Gingerbread is perhaps as far as this device will go - in terms of functionality and "useablilty" - sure I'm sure ICS will "go on" if attempted but i'm pretty sure will fail to be useful (and if someone proves me wrong then I still win as I'll use it)
anyway keep up the good work with this gingerbread attempt - I'm hoping it goes well

Any news for the new year?

Related

VegaComb 3.2 Available For Adam.

Found post about VegaComb being released for Adam on TabletRoms.com. Due to the similarities and the fact that there exists ROMs for G-Tab based on Adam. Do we know if there is an effort to port this ROM to G-Tab? Any info would be appreciated as this looks to be THE ROM, with the possibility of fixing camera and hardware acceleration.
A kernel is being worked on ; on the slatedroid forum. The hardware is different so a kernel has to be made for it to work
[email protected]: Posted Today, 09:31 AM
Unfortunately the Vega is not a hardware match for our beloved g-tab, they are very similar however they are not the same hardware exactly, little things like the wireless controller and the camera are different. They also have a different mainboard in their system. I'm pretty sure that the rom that works on theirs is not going to work on ours until we have a working kernel to work from. They have worked very hard on rewriting the drivers to get their tablet to work as well as it is in 3.2 and they don't seem to be slowing down now that it is working. I know that the group that is working on the kernel is working very hard to get it running as quickly as we can, I don't think that most of us have much experience in kernel coding and so it is taking some time to even get it to boot. However I can tell you that we are working diligently to get through the problems and get a kernel out to the community so that we can join the ranks of the Vega in making Google cry by hacking our way to victory. On a side note I want to say how impressed I am by the level of assistance that everyone in this community has for the new members and old members alike. I don't know of another rom that has this level of support from it's users out there. Thanks to all of you that are helping people overcome their issues and enjoy this fantastic rom.
Click to expand...
Click to collapse
.
[email protected] Posted 14 August 2011 - 09:01 PM
Hello all, Ch3vr0n5 here
The GTab Kernel Dev Team would like to chronicle our kernel development process for everyone to enjoy. The Gtablet 2.6.36 kernel project is based on the work done by Eduardo/RaYmAn on the Adam kernel. The biggest thanks goes out to them and anyone else who works on that project because it has made our work possible.
The Dev team is currently: Myself, Icewyng, Mayday_Jay, WayneMasta, Treznorx
[8/25/2011]
We know that we are hanging on init.rc and have a few ideas one how to proceed. Mayday_Jay (Give him and Icewyng a big thank you because they have made this project viable) is working on getting all the developers a proper update.zip that will help those with out a usb to serial converter get some useful debug information.
Don't fret when it takes a couple days for us to update. If you want bleeding edge news, join us on the kernel dev irc channel which is found further on in the thread. We are still working! =)
[8/23/2011]
Linux (BT5) will boot without Touchscreen working. Work is progressing slowly to get this working with Android. Mayday_Jay, with the use of USB -> serial converter has been able to get some useful dmesg output as well as some other debug information that is giving us new ideas on how to proceed.
[8/19/2011]
Starting to modify the adam files to mach the correct values for our device. Our current config gets us passed the birds and to the second boot image and the usb device registers. Trying to get it connected to adb to get some dmesg output.
[8/14/2011]
The resulting kernel did not boot and this is more than likely due to the fact that there are quite a few new config options that need to be set. I have run a diff to find differences between Pershoot's and Rayman's kernel and will be trying a new config either tonight or tomorrow hopefully. Gotta sift through new and deprecated options as well as any they both have but are set differently (and why)
Part 2
The kernel compiled with the additions from rayman's config in pershoots got it past the birds to the "Android 3.0" screen. Tomorrow I will be able to hookup adb and see where it is crashing from there.
[8/15/2011]
Still running through different configurations. Need to ask pershoot what modifications he made to make the .32 kernel boot on the 1.2 bootloader. IE Which files use the NEWBL config option and what the changes are.
[8/16/2011]
I received the source for the Vega kernel from rebel1. I may not update for a few days as I try out different configs and such but I will still be here.
[8/17/2011]
Decided to go with the Adam kernel because of hardware compatibility. Put up the github repo.
GitHub.com Repo
git://github.com/ch3vr0n5/android-tegra-2.6.36-gtablet.git
-----------------------
All thoughts, idea, comments and criticisms are welcome (Please be kind). Just remember, most of us are not programmers or software engineers by trade. I got my degree in network security so I generally play with routers, firewalls and the like and do this as a hobby. If you find anything wrong with what I or any of the Dev team have written please tell me... just don't point and laugh. LOL
Cheers
Click to expand...
Click to collapse

[DEV] ICS Android 4.0 Porting and Development | es209ra (X10) | alpha1 | 21/11/2011

This is a dev thread. Do not install this release unless you know what you're doing. Do not post if you have nothing to contribute.
This is very early build, we're behind other qsd8k devices but will eventually catch up
Big thanks to all qsd8k developers working on this (N1, Desire, HD2, X10).
[KERNEL]
- ol' good 2.6.29-SEMC
- fixed touchscreen driver (now backward-compatibile with Gingerbread)
[ROM]
- partially based on drewis release (thanks!) - currently I don't have access to PC that could handle compilation of the whole thing
If someone could compile clean es209ra build and upload it would be awesome.
[WORKING]
- it boots
- radio, calls, txt (sms)
- audio partially working (in-call is fine, playing mp3/ringtones leads to WLOD)
- bluetooth, GPS seem to work
- wifi almost working ("can't find wlan0 device")
- mobile data (it gets IP but disconects afterwards, needs investiagtion)
[NOT WORKING]
- most of the stuff does not work
- quite unstable
[SOURCES]
Will upload all of the useful code/fixes here.
- ICS + GB compatibile touch driver: es209ra_touch_mt.c
- compatibile ramdisk (props FXP): http://www.mediafire.com/?1n51pn1upwv79ur
[DOWNLOAD]
Alpha1 ROM (for CWM5) + corresponding kernel (flashtool) is here:
http://www.mediafire.com/?ht6p6tbpj2988d4
Cheers,
z
Just did a major clean up on this thread mates....no more "thanks" posts please. If thankful... click the thanks button.
Regards,
M_T_M
Finally we get it. aZuZu is working on ASOP ICS 4.0.1. This may help him work easier. So with locked bootloader, can we flash cause' you wrote there CWM5?
VIDEO
here's a video for ics on x10 alpha build 1
http://www.youtube.com/watch?v=bsOFn4YLvZU
@frosty666 please kindly include this on your ics discussion thread.
thankz
hi zdzihu, its great to see you back! is this only temporary or, are you going to be more active, like before?
mmmkay, I'm not dev, but I want to ask if you're compiling this from ground up (like Jerpelea's CM7), or you're like just mashup of current SE and ICS sources. if its a mashup, I can help. but I do very little design from ground up things.
Sent from my X10i using xda premium
if you have fixed audio hw sources i could recompile..
altho i have complete es209ra compile with ics hw, old cm gralloc / copybit sources and generic audio..
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
I help if u want
Hello guys, I'm new to the forum and I hope to see well with you.
I would be willing to help compile the source since EXCLUSIVELY use only Linux operating system and is much easier to work on programming because most of the libraries are already installed by default, I hope I was clear.
greetings
Joseph
zdzihu said:
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
Click to expand...
Click to collapse
yaay Z!!!
glad to see back!
now i feel so bad & depressed that i dont have a working x10 with me
hope that service center guy is able to repair it again...
@aZuZu
can u please upload ur work-in-progress sources to git... i know how much fixing u have done... it might help other too
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
so good
I will try to build ICS this weekend!
I have no time this weekday
Zdzihu, if the wifi still reports the same error (can't find wlan0 device), it probably means that the kernel refers to wlan interface as eth0. Try changing the wifi.interface entry in build.prop to eth0.
little help for folks that compile ICS on weak pc
make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Killed << if processes during compile get killed try this script > Fix Swap
Well to me helped so maybe it helps other ppl.
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
WHAT IS IT WITH SOME OF YOU GUYS, IT IS DEV ONLY THREAD AT THE REQUEST OF THE DEVELOPER, IF YOU CAN'T FOLLOW SIMPLE RULES THEN INFRACTIONS WILL BE HANDED OUT, YOU HAVE NOW BEEN WARNED!
wbbigdave said:
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
Click to expand...
Click to collapse
gunzip -c <ramdisk.gz> | cpio -i
Cheers,
z
The next member who disregards a developers request and posts in a non helpful way will be banned for a week.
i encourage any dev or helpful member to pm me or any other mod with the offending post and the user will be dealt with
Please don't reply tp them to tell them they are breaking th rules as you post will then also be rule break worthy
Hugs and kisses
PiLoT
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_frameworks_base,n,z
sorry for posting here. but is for development. for ICS, can we used modified 2.6.29, and modify, like what zdzihu did, it so it 100% or do we have to use 3.x (or whatever) becuase I'm starting to do kernel mods and I want to see what I can contribution.
so in all, does the newest kernel have to be ported? or can we continue using good old 2.6.29 and keep Modding it? (hopefully camera will work, drivers have to be rewritten for kernel. and no one likr to write drivers)
Sent from my X10i using xda premium
In case, we can see here how they get the SD Card working
http://forum.xda-developers.com/showthread.php?p=19774268#post19774268

[DISCONTINUED] CM9/ICS Nightly Builds

As of 8/25/12, this project is officially discontinued. All information below is for archival purposes only and will not be supported henceforth.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
INTRODUCTION
Now that Fattire has lifted his request that everyone build their own zips, I've decided to make available the nightly builds I've been generating. I've got an OS X system cranking out a new build every night at midnight, so there will always be an up to date zip available!
Credit for this rom goes to Fattire, Dalingrin, keyodi, nemith, arcee and the the other hard working people over in the development thread, as well as the the CyanogenMod developers and anyone who's done work on the Nook Color. I wish I could list everyone by name but there's so many great people who've made contributions I can't even begin to do so. I'm just building zips from the source; we'd be nowhere without the contributions these great developers have made to this community.
As nighty builds, these zips may not always work. I'll try to remove any zip found to be broken, but you know the drill: All files provided here are to be installed at your own risk. I'm making built zips available, but no warranty is expressed or implied by the hosting of said zips. I'll provide what support I'm able to, but that doesn't mean that there aren't potentially unknown bugs. If you have questions, you should check the development thread or try the #NookColor IRC channnel on irc.freenode.net.
As posted by Fattire slightly further down, anyone feeling adventurous should definitely consider building from source rather than downloading the built zips. Here's his two cents:
fattire said:
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
Click to expand...
Click to collapse
However, if you're not quite sold on setting up a development environment but you still want to try the goodness that is Ice Cream Sandwich, proceeed on down to the...
DOWNLOADS
Without further ado: The Ice Cream Sandwich zips!
Ice Cream Sandwich Nightly Builds.
The rom does not include the google apps, so you can/should flash the lastest version of those, which is available here.
Finally, I've hosted a few flashable zip files to make small tweaks to the rom. These are all located in the misc. folder on my server. Below is an explanation of each zip and its purpose.
MISC FOLDER INFO
If you notice that some apps are missing from the market, this may be due to the fact that these ICS builds for the nook do not include support for apps which request phone permissions. Although this ideally would be fixed by developers not requesting phone permissions for their app unless it absolutely needs to be phone-specific, you can also fix it by flashing the telephony-permissions-fix.zip file located in the misc folder. You will likely want to flash this file immediately after flashing your rom.
Secondly, if you prefer the old bootanimation from the galaxy nexus, you can also flash the fix-bootanimation.zip located in the Misc. folder, which replace the new CM9 animation it with Homer_S_xda's fixed version. Thanks to Homer for the fix!
NOTES ON INSTALLING TO SD
I've fixed Verygreen's sd installer image to work with ICS -- you should no longer have to flash SP1 first, or rename the gapps to gapps-gb. If you test out this image, please let me know how it works for you! More recently, Leapinlar has stepped up in helping to fix the image further, increasing its size to allow for the larger size of the new nightlies. Thanks to him for his help -- It's available for download here. Huge thanks to Verygreen for helping me to figure out what needed to be fixed -- in the words of HacDan, "He's not just super helpful, he's a genius". Once you've got the new image, you can use Verygreen's original instructions from his thread on SD Installs, replacing "cm7" with "cm9" where necessary.
IN CONCLUSION
Please remember to thank the developers working on this project, as they've done seriously awesome things for us in an amazingly short amount of time. If you have questions/comments specifically regarding my zips, please post them here, but if you have more general questions regarding Ice Cream Sandwich on the NC you may want to head on over to the development thread. Finally, if you're really enjoying the rom I'd strongly recommend that you try setting up a build environment and building your own zips -- even though I'm making prebuilt ones available they're no substitute for the experience gained by getting familiar with the build process yourself, and Fattire has done a great job of making it an extremely accessible and rewarding project.
Thank you!!!!
What bugs can we expect as far YouTube, flash player. Boot loop . A breakdown of what to expect and not to expect. I don't expect anything but like to know for flashing
And you can build too!
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
So awesome!
Youtube missing in latest gapps ?
I installed the latest nightly with the gapps and found youtube app is missing ?
Thanks for sharing! I love nook color devs community! You did an awesome job!
Brilliant work! I upgraded from CM7 and all my existing apps that ive checked worked no problem, it kept all my settings too! Speed-wise I would say its very close to CM7, i use ADW EX in preference to trebuchet, and it just flies!
One thing ive noticed is that NFS shift doesnt behave properly when using the tilt sensor to steer, its axis sensor wants the tablet to be in portrait orientation when the screen is in landscape. Hard to know if its the games fault or the sensor. If thats all there is to complain about this early in the development then the future looks promising
rajazeeshan said:
I installed the latest nightly with the gapps and found youtube app is missing ?
Click to expand...
Click to collapse
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Dual boot ?
I currently have a dual boot environment setup so I can boot into stock (primary boot partition is currently CM7). Does anyone know if this still supports that ? Anything specific I'd have to do with the install then ?
TIA
Thanks a bunch for hosting these nightlies.....let the fun begin!
I just want to point out for the sd-card users using verigreens 1.3 boot image to setup cm7 to run off of sd card and retain stock for various reasons.
That process will also work for ICS/cm9. Currently, you need to flash update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip first. It's found in the ics/cm9 dev. thread: http://forum.xda-developers.com/showthread.php?t=1370873
Then, flash Samiam's nightly builds otherwise you will get stuck in a boot loop right now.
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
I'm gonna stay on cm7 for a while. But I love the progress were seeing with ics.. thanks guys
pavlos46 said:
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
Click to expand...
Click to collapse
What version of the gapps did you have where the wifi location worked? If you link me to that I can see if there's something missing from my gapps zip.
YouTube is incompatible from the market. Actually, it appears any device I have that runs ICS is listed as incompatible.
youtube app missing in gapps
Samiam303 said:
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Click to expand...
Click to collapse
Unfortunately thats not the case when I search market it doesn't list YouTube app and when I
Google it takes me to mobile YouTube app in market that is not compatible with this device.
I salute you all dev. gurus.
Hat off and thanks for the ICS
Awesome thanks so much!
Hey,
awesome awesome work, thank you very much!
I have a slight problem with the GApps, though: I came from update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs and just updated over that with some ics-apps installed. Unfortunately, I do not remember which ones.
Now after the update all my apps are there, but the home screen wiped (not so bad), but my Google Account vanished and I cannot add a new one. Neither in the Settings, nor by opening GMail, Talk, whatever. These will just crash.
Any suggestions?
Thanks again for all your work and energy, I really appreciate that.
Greetz,
Felix
ZenoGia said:
Awesome thanks so much!
Click to expand...
Click to collapse
+1 .

[DEV][DEPRECATED][4.0]ICS 4.0.4 for the 4.0 (Build #3.5 up)

THIS THREAD IS DEPRECATED.
This project has move down, out of the alpha stage, to here:
http://forum.xda-developers.com/showthread.php?t=1950453
This thread is here for documentation purposes only! There are better builds at the new link, more detailed instructions, and support. Please direct your attention there! Thank you.
Warning! Flashing this may/will delete your /efs, which will causes major issues if you ever decide to return back to stock, so make sure you make a backup! If you don't know how, frankly you shouldn't flash this, as you need at least some experience just in case something goes wrong.
Team SuperNOva:
Oisis (helped us get over the final issue)
Zaclimon (first kernel dev, did a LOT of the preliminary work)
Neyodmium (helped us sort out that SGS sources that CAN be used for the 4.0, and helped pinpoint what needed to be replaced/fixed)
Me, hanthesolo (Rom dev, I will be providing updates, support, and other smaller things, so they can concentrate on the kernel, while I fix up the ROM)
The Back Story:
Firstly, excuse my cheesy biblical writing, I just have always wanted to write something in that format .
In the beginning (march 2012), there was hanthesolo. He saw the Galaxy Player forums, and all that he saw was good. This man started creating new work for the Gplayer forums, a and gained a small following. There was just one issue that concerned him: NO ICS!
In light of this, this man created a thread, to collect all ICS development, into one easy-to-read forum. Other began to follow him, zaclimon, Ijimaniac, and several others. Ideas flew fast and furious, but hope was waning quickly. A kernel would have to be created from scratch, a monumental task that had not been undertaken by any man so far.
All was quiet for awhile, and people began to slowly fade out, until only hanthesolo and zaclimon remained, slowly trading ideas and guesses over several weeks. Then a new disciple arrived: neyodmium. This korean (?) developer brought a different kind of kernel experience to the trio, and development began in earnest, with zaclimon and neyodmium trading work, while hanthesolo contributed where he could. One unsurmountable issue arose: this magnificient kernel, the likes of which had never lit up these forums before, would merely boot into recovery, not into Android.
Then Oisis came around, hearing our desperate cries for help. Like a moses, he guided his flock in the right direction, squashing issue after issue, until a monumental day arrived: August 13, 2012. On this day, ICS was finally created in Cyanogen's own image, and it was good.
Then increased development began, with hanthesolo squashing CM9 bugs, while zaclimon, neyodmium, and Oisis working feverishly on the kernel.
But an issue occurred, a wrench in the works. Thine enemy's name is GL, SuperNOva. GL would not cooperate, acting as a barrier between usable ICS, and frustrated efforts to fix it. But one day, the magical variable was flipped, and the builds booted! About this time there was a github mishap involving a bad I9000 push that stopped things for about a week, but that's another story.
What happens next? I dunno, but I will update this story when it happens .
NOTE: This does NOT represent anyone's political or religious standpoint, or the way anyone is viewed. It was created as a humorous way to explain our situation to users.
The fix list:
ROM:
Bluetooth (should be easy)
HW acceleration (easy, just neds to be implemented)
Camera (will take awhile)
Kernel:
HW acceleration (Oisis is working on it)
Drm manager (needs to be fixed before market can be used!)
US home button
Boot to recovery (very annoying when trying to flash builds)
Camera (?)
Changelog:
Build#1:
Initial release, basically everything is broken.
Build#2 changelog:
Finally fixed bootlooping that was plaguing our github
fixed ALL GL crashing and oddness
Fixed/improved sound (if it was broken)
Fixed Browser (slow, but usable)
Waiting on a new kernel to readd GL and/or HW acceleration.
FM radio! Just download the spirit FM app, you can find it for free on XDA
Build#3 changelog:
Fixed av codecs (videos should play just fine now, as well as youtube)
General code cleanup and optimizations
Build #3.5:
Performance improvements and some code cleanup.
Download links:
Build#1:
CM9: http://www.broken-arrow.pl/oisis/aokp/YPG1-CM9-OiSiS-build-02.zip
Kernel: http://zhshibenzhu.host22.com/tuchuang/cm9_kernel.tar
Build#2:
CM9: http://www.mediafire.com/download.php?lu33uubm6der2j9
Kernel: Flash the one above.
Build#3:
http://www.mediafire.com/download.php?96yk0e3y8cqzj1b
New kernel: http://forum.xda-developers.com/attachment.php?attachmentid=1298676&d=1346633739
Build #3.5: http://www.mediafire.com/download.php?oscyfde4w364dj6
Install instructions:
Special thanks to daniel644 for the video and his high praises of me .
If you get stuck in recovery, flash a GB kernel, it will boot into recovery, simply hit "reboot". When it bootloops, boot into download and flash the CM9 kernel.
Resources:
Manifest.xml (so you can just simple "repo sync" instead of git pulling every time we have a new commit):http://forum.xda-developers.com/attachment.php?attachmentid=1278615&d=1345762041
Wiki link (please help improve it!): http://forum.xda-developers.com/wiki/YP-G1
Github repo: https://github.com/TeamSupernovaSGP
NOTE: this is just the modded files. You need to full CM9 source before you can compile!
Contact us at: [email protected]
Please only emails us with valid questions or useful support!
port kernel 3.x from Galaxy S to SGP4.0 should be easy, coz hardware parts are almost the same, but SGP5.0 conpoments arent the same, the way for SGP5.0's 3.x kernel should be harder.
tdmcode actually has a booting CM9 build. I believe that wifi and sound work, but nothing else. His vendor tree and device tree are here:
https://github.com/tdm/android_vendor_samsung_ypg1/tree/ics-cm
https://github.com/tdm/android_device_samsung_ypg1/tree/ics-cm
He just never released it as it is still not very functional.
Maybe it would be easier to just take his source and try and fix the issues and make it fully working. Because getting an AOSP bringup to boot is most of the work; the rest should be easier to do.
Would it not be easier to port over a rom, as the hardware is the same? It would at least be more helpful, because if we could create a guide, we could port other roms over very quickly!
Sent From my Galaxy Player running StratusRom using XDA
klin1344 said:
tdmcode actually has a booting CM9 build. I believe that wifi and sound work, but nothing else. His vendor tree and device tree are here:
https://github.com/tdm/android_vendor_samsung_ypg1/tree/ics-cm
https://github.com/tdm/android_device_samsung_ypg1/tree/ics-cm
He just never released it as it is still not very functional.
Maybe it would be easier to just take his source and try and fix the issues and make it fully working. Because getting an AOSP bringup to boot is most of the work; the rest should be easier to do.
Click to expand...
Click to collapse
I built it and I will test to see if it works (I'll use the newest kernel from cm7)
I am going out on a limb here...could we use the cm7 kerbel to help port a workable ics kernel for a galaxy s port? Once thats done cooking up a working rom should be easy and quick.
Sent From my Galaxy Player running StratusRom using XDA
One thing
Ambitious project hanthesolo
one thing: could i suggest that the title of this thread should be Operation: ICS for Galaxy Player 4.0 or something?
Okay, I may rename it. ICS is far more feasible than you think. Once we get a working kernel running (which will be soon) we can port ics over from the galaxy s (which would be best, as once it boots most features would work). I hope by the time school starts up ics will be functional as a daily driver. I may not be able to help a ton, as most of this revolves around making a working kernel, but I will try to help where I can.
Sent From my Galaxy Player running StratusRom using XDA
I can't get it to boot. (stuck at samsung logo) I think it would be better to build it from source instead of porting over.
Its stuck at the samsung logo because the kernel probably didnt work. It has happened to me before, we need to compile an ics kernel. The galaxy s one almost works, we just need to find out what makes it fail to boot.
Sent From my Galaxy Player running StratusRom using XDA
We can use the BML/STL partition layout in waiting for yaffs2. We can use entrophy's device tree as base for it(we can ask for help from him too)
https://github.com/Entropy512/android_device_samsung_infuse4g
Thanks for looking into that zaclimon! I will pm him and see if he would be interested. I willxupdate the opxwoth info from various people/sies as I get it.
Sent From my Galaxy Player running StratusRom using XDA
Would a tablet kernel made from scratch to run ICS do anything or does it need to be more kosher with Samsung and their device tree?
rozelle25 said:
Would a tablet kernel made from scratch to run ICS do anything or does it need to be more kosher with Samsung and their device tree?
Click to expand...
Click to collapse
I dont quite understand what you mean. Can you elaborate please?
Sent From my Galaxy Player running StratusRom using XDA
Hey I've been looking at this situation too and science coming back after q long time in the Xperia play forum I decided I wanted to help I found this guide about compelling ics http://www.freeyourandroid.com/guide/compile-ics but 1 problem I need to find the device and vendor tree on github but I've never used githubn before so need some help with that so if I can help please let me know
minipot said:
Hey I've been looking at this situation too and science coming back after q long time in the Xperia play forum I decided I wanted to help I found this guide about compelling ics http://www.freeyourandroid.com/guide/compile-ics but 1 problem I need to find the device and vendor tree on github but I've never used githubn before so need some help with that so if I can help please let me know
Click to expand...
Click to collapse
If it was that easy, webwould have ics today on our devices. The reason its been so difficult is that we need to combine/port githubs to create a working kerbel, which is a lot harder than it sounds. Thanks for the link! I will put it in the op.
Sent From my Galaxy Player running StratusRom using XDA
Im guessing u mean we could make a rom using that but first we need a kernel that qill work with it
Yeah. Porting a rom is easy, but getting a working kernel is not. Once we get a working kernel we can port as many roms as we please.
Sent From my Galaxy Player running StratusRom using XDA
Well I don't think it is that hard if we base ourselves from other devices trees like entrophy's one. I think he removed RFS from his initramfs which leaves him only ext4. Then he used a script that would convert the partitions to ext4 when installing CM9. I think it is the same things than with the mmc partitions (I think this is a part of why the 5.0 got ICS sonner than 4.0)
EDIT: And I think it's better to build it from source the first time. (instead of porting for the case of CM9 for example.)
Yeah, I was just talking comparatively. Has anyone begun working on this yet? I have been researching a LOT (the best thing I can do to help right now), but since my knowledge is limited on kernels, i cant help with that riht now
Sent From my Galaxy Player running StratusRom using XDA

Want to start with AOSP JB 4.2 - experienced developers are welcome :)

Hi all,
i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me?
I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do
some nice things
I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2
### EDIT
As long as no one has found to help, here a short description of current progress:
- Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio)
- Device is bootable (no other boot.img required anymore)
- Bootanimation is working
- Mount of partitions is working
- Deodexing is working
- adb, debuggerd and root access is working
Not working: a lot
- Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM)
- Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver)
- Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs)
- USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process)
- RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony)
Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting
Sent from my GT-I9300 using xda premium
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
hop3l3ss1990 said:
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
Click to expand...
Click to collapse
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
andy572 said:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
Click to expand...
Click to collapse
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?
I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it
Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool
Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom
PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.
They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.
Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
slaphead20 said:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
Click to expand...
Click to collapse
Thank you, it would be nice if you can contact him
andy572 said:
Thank you, it would be nice if you can contact him
Click to expand...
Click to collapse
Ok, will mention it to him
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Good Luck Dude~
I haven't tried AOSP yet.
Hope someday i can give it a go.:silly:
hop3l3ss1990 said:
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Click to expand...
Click to collapse
current state:
- patched android/build so we can compile the kernel within the main compile process
- patched android/build main.mk file so we can use OpenJDK or Oracle JDK
- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)
- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP
- modified android/frameworks/native/include so a OMX Plugin header can be found
- modified android/libhardware and patched gralloc module
currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem
to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like
a bug in android/build too.
For only 2 days trying to compile to the end without errors its a very good cut
here we go: it compiles to the end and a flashable "JOP40" zip could be created
tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.
do we need a new or patched kernel instead the CM10 smdk421x one?
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
b-eock said:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor
is red blinking (the one to the right of the speaker.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
Sent from my GT-I9300 using xda premium

Categories

Resources