Develop Bugs

Gingerbread [Alpha2] by Neopeek!

Original thread here! >>http://www.neopeek.com/forum/Android-ROMs/5764-Ooops-WE-did-it-again!-Gingerbread-Alpha2-available <<
EDIT: Not for Sony Xperia X1. Works on my HTC Diamond so I can't say what other devices will do...Thanx everyone for testing the Pre-Alpha! I could fix several bugs! Now we are officially Alpha and it's quite usable on my HTC Diamond!
Ooops WE did it again...
My wife's still knocking my brain saying I am an idiot B) (while writing this she stands behind me). I spent some hours yesterday and several hours during the night cause I know everyone wanna try this out. I want especially say thanx to Chann who always is inspiring me with his ideas while I am doing some nice conversations with him on dev-section of this forum. It's really helpful to have such kind of member here.
More details later -> as always: I don't have time to test anything out on my own -> so I didn't! It's up to you to come back and report your experiences.
Alpha-release 26-12-2010
Before continuing be aware of: This is an Alpha release and now it seems usable (on my HTC Diamond it is!)! So before you do anything I suggest you to make a backup of your data / files! So read everything careful now :
What's inside ?? :
[ul]
[li]Gingerbread 2.3[/li]
[li]Working: Wifi, Data, Phone, SD-Card, Compcache 25%, automatic lcd-density settings and maybe more[/li]
[li]BT activating produces reboot (needs fix)[/li]
[/ul]
Important now!!!!!! Read:
[ul]
[li]First boot takes quite some time! [/li]
[li]I suggest you to open all apps and sync your account with google. Then reboot your device![/li]
For Download, click above link!
As always: Use this on your own risk!
Thanx go to: Balsat, XDAndroid-Project, Martin DZO and everyone else whom I forgot!
Download is a 1-file-download, again! Including everything you need!
EDIT: I need your experiences / feedback in this thread!
Installation:
[ul]
[li]Installation Instructions (Link) thanx to chase21[/li]
[li]Test-Kernels to try out (Link) thanx to hayabusa94[/li]
[/ul]
Please update your signature! It's always hard to find out which device / smartphone you use and which kernel(s) you are referring to!
Click to expand...
Click to collapse
-Neopeek!
Don't thank me! Thank Vatoloco/Neopeek!!

HTC raphael 800 can run but wifi not working (status: error) and battery drain fast.
I still waiting for Neopeek Team.

I am just instaling it... I can not wait for the final fully functioning version.
Cheers

Not stable enough for me at least (Fuze/RAPH110)... Guess I'll just have to deal with FRX03/FRX02 for now... ^_^
Kernel package: htc-msm-linux @ 20101204_005141

I have a Fuze and it works fine for me, but it is just a bit laggy (kernel does not support so well).
Remember he just hacked gingerbread to work with froyo settings but I can promise that future builds will be much better once every one else has started the development of gingebread on our devices

I kind of figured, just wanted to report my experience since it seems most of the newer kernels seems to half work on my Fuze with FRX03. Might just be something I'm looking over About to try again with newest kernel from Glemsom's site and see if the FCs are any less frequent.

Yeah, i'm using the latest glemsom kernel and it is slightly laggy but stability is much better. I have not tried any other kernels yet..

I'm using the old kernel & module 01238 from FRG83 R5 build in this Raph100 & it works just fine except for the known Android issues that we still have.
Some minor glitches in Gmail & root access rights reported by SetCPU, but overall a good build (stable) considering that it's still in Alpha stage. Anyway, we get to test run Gingerbread while most native Android devices are still running Eclair or Froyo!

hello, it runs fine with kernel 1190 from camera thread, for the keyboard use jap input. Reboot you can, do with the dev tools-bad behavior-crash system server. keep going man very good!

UPDATE
Gingerbread is working nicely! I have not tested everything but at least there are less FCs! I am using kernel package from Dec 26, 2010:
zImage & modules
NOTE: Check out F22's note about this specific kernel package from THIS post.

Better performance ?
Gingerbread is supposed to be faster than Froyo. I wonder whether this will translate into a better performance on the Diamond. The Diamond is a slow device (compared to the HD2) and there's not much that can be done about it, except overclocking.

HD2_addict said:
Gingerbread is supposed to be faster than Froyo. I wonder whether this will translate into a better performance on the Diamond.
(post trim)
Click to expand...
Click to collapse
Anyway we could interest you into test driving and giving it a once-over with your diamond?

I would love to try it myself on my touch pro cdma (raph800), but i can't afford to mess around with creating the separate partition to try this. Is there yet an alternative way, as i would love to test this out also?

I suppose I could try to make it into a .sqsh file so you can just boot off of it on sd card but no garuantee it will work...

I wouldn't mind trying it if you don't mind doing that. I keep my android2.2 in "setpath=android2.2" directory, and assume i could also do the same with this "setpath=android2.3" to keep them separate.

here it is: http://www.multiupload.com/6QEW8OFBMJ
*may or may not work*

Thank you much sir. I just unzip the sqsh file from that archive file into the main SD stick directory, correct? So far i followed the instructions and (at the time of writing this) was at the "run the install from the subdirectory, after it's done, it will reboot back into WM" part, and continuing.

Yes, that is correct. You don't need to run "install.exe" or need the npkinstall folder. It should be fully compatible with xdandroid and you don't need the files from neopeek.com.
Just boot it as if it were an xdandroid build and hopefully, it should display android logo. Ext2 is much faster.. give it a try when you can.

I might have to do that. All i get is the following (last 2 lines of the screen at boot)
"mmc1: error -22 whilst initialising SDIO card"
"Waiting for root device /dev/mmcblk0p2..."
and then just sits there for ever.

Are you using an xdandroid startup.txt or neopeek?

[TESTING] XDAndroid GBX0C 2.3.7 Build

Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!​
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install​
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download

Caveat List​​
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from my RHOD400 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog​​
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...

Just to get people going on some of the newer kernels.
2.6.35 is currently auto-built at:
https://code.google.com/p/zimages/downloads/list
Emwe has been maintaining this tree, and he is most qualified to speak about it, but pretty much everything is functional barring camera.
Head over to this testing thread for more information on 2.6.39/3.0/3.1 kernels for Rhodium.

arrrghhh said:
Pre-Install Prep REQUIRED!!!​
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Download
Click to expand...
Click to collapse
You probably saw this problem coming but I have just the stock windows rom, how would i go about doing this? (or do i have to go and find each and every CSV file )
I googled and downloaded total commander on my laptop, and i got it to show my phone, but it only shows up with my SD card stuff, not my phone itself (unless thats whats supposed to happen )
Will keep trying! -determined-

A cool username said:
You probably saw this problem coming but I have just the stock windows rom, how would i go about doing this? (or do i have to go and find each and every CSV file )
I googled and downloaded total commander on my laptop, and i got it to show my phone, but it only shows up with my SD card stuff, not my phone itself (unless thats whats supposed to happen )
Will keep trying! -determined-
Click to expand...
Click to collapse
Sigh, are you freakin serious? I even link to Total Commander's website in my instructions.... Not sure how much easier I could've made it.
I also just attached the CSV's for the lazy... .
It does say TESTING in the title, no? Yea. It does..

Hehehe I know, I know, i guess i just don't have very much knowledge with this kinda stuff (obviously) Thanks!

A cool username said:
Hehehe I know, I know, i guess i just don't have very much knowledge with this kinda stuff (obviously) Thanks!
Click to expand...
Click to collapse
Testing/development threads usually mean "please pitch in and help test if you can. If not, please wait until the final stable release".
Make sense?

Okay, i'll be glad to help test it if someone could post the CSV files for a rhod300 (if its not too much trouble). If not, I will wait for the stable release. Thanks arrrghhh!
Yes, makes sense

Installed the rom but i've got a problem with the fact that the screen dissapaers after about 5 seconds, so i can't even put in my pin.
also i'll put in the csv files from my rhodium100.
Edit: Works good on second boot, had to change the calibration file and it's works good and fast. Only thing i have is that i now have got 919 contacts instead of the (normal) 135.
A lot of text messages for tonight
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Camera works when you don't move a lot, otherwise it's blocked.
bleutooth doesn't work for me it connects to my parrot but i can't make a phone call.

Schumi_wk said:
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Camera works when you don't move a lot, otherwise it's blocked.
bleutooth doesn't work for me it connects to my parrot but i can't make a phone call.
Click to expand...
Click to collapse
Sounds like a proximity sensor issue - not sure if some of the GSM rhod proximity related adjustments made it into the acoustic .27 kernel. You should try one of the newer kernels (not sure what's the status with .35 and GSM-proximity, but on 39+ I expect you won't have this issue).
This GB build, and these new kernels are kexec enabled. Meaning if you are on .35 or newer, and would like to interchange the kernel on-the-go, without re-booting to WinMo you can do the following:
1. While in Android, copy the new kernel and modules to the same location (over-writing the zImage) as your current kernel (adb push).
2. Go to the shutdown menu in GB, and select "Kexec".
3. Phone will reboot within Android, using the new kernel.
Again, this feature only works with the new kernels.
---------- Post added at 06:20 PM ---------- Previous post was at 05:38 PM ----------
Schumi_wk said:
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Click to expand...
Click to collapse
Let me know if you are willing to test a prox support for rhod 100. I'll pm you a kernel pack.

Just tried the .39 kernel and bluetooth didn't work with that one. The phone did work with this one.
Than did the 3.0 kernel and bluetooth works but there i don't have wifi.
The 3.1 kernel doesn't load it stops at
3.711395 mmcblk0:mmc1:1234 SA0BG 7.42gb
3.728118 mmcblk0: p1
Than did the .35 kernel and bluetooth worked but no wifi.
No more testing for me today, i'm getting ready for the last hours of 2011.
For all of you enjoy the last moments of 2011 and start 2012 with a lot of fun!!

Schumi_wk said:
Just tried the .39 kernel and bluetooth didn't work with that one. Than did the 3.0 kernel and bluetooth works but there i don't have wifi. The 3.1 kernel doesn't load it stops at 3.711395 mmcblk0:mmc1:1234 SA0BG 7.42gb
3.728118 mmcblk0: p1
Than did the .35 kernel and bluetooth worked but no wifi.
No more testing for me today, i'm getting ready for the last hours of 2011.
For all of you enjoy the last moments of 2011 and start 2012 with a lot of fun!!
Click to expand...
Click to collapse
You must understand that BT is only functional in 3.0 and .35 (well, and .27). I don't know about the state of wifi in any of 'em... Should work in .39, I thought it worked in .35 as well. Haven't booted .35 in quite some time myself. Logs are really going to be necessary to triage any of your problems tho. Thanks, enjoy New Years.

arrrghhh said:
Caveat List​​
The CSV files from my RHOD400 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
Click to expand...
Click to collapse
Here are my .csv files for the Tilt2 (Rhod300). Have not compared to the RHOD400 yet.

Here's my CSV files from my RHOD500
BTW, I can't use the Wi-Fi
I'm using the default kernel and settings that came in the bundle...I will try using a new data.img
Logcat says: "E/WifiService< 1328>: Failed to load Wi-Fi driver."

nickleby said:
Here's my CSV files from my RHOD500
BTW, I can't use the Wi-Fi
I'm using the default kernel and settings that came in the bundle...I will try using a new data.img
Logcat says: "E/WifiService< 1328>: Failed to load Wi-Fi driver."
Click to expand...
Click to collapse
You didn't start on a new data.img...?
This makes me think the modules didn't copy, but I force them to every time. Perhaps I should rm them all first... bleh.
You're not mixing and matching anything are you...?

arrrghhh said:
You didn't start on a new data.img...?
This makes me think the modules didn't copy, but I force them to every time. Perhaps I should rm them all first... bleh.
You're not mixing and matching anything are you...?
Click to expand...
Click to collapse
I'm using a new data.img, but the wifi still not work...I'm using the rootfs, zimage, kernel, initrd, startup.txt and system.ext2 that came in the bundle, I just added my ts-calibration

nickleby said:
I'm using a new data.img, but the wifi still not work...I'm using the rootfs, zimage, kernel, initrd, startup.txt and system.ext2 that came in the bundle, I just added my ts-calibration
Click to expand...
Click to collapse
Hrm. Can you pull some logs? I tested wifi every which way and it was always working. I did make some rootfs tweaks, so I guess it's possible it's using the wrong firmware...?
Someone had a wifi issue, rebooted and it went away. I hate wifi .

Yay! Merry Christmas and Happy New Year guys. Can't wait to try this and get back on .39. And sort-of hot-swapping kernels? Sweet.

arrrghhh said:
Hrm. Can you pull some logs? I tested wifi every which way and it was always working. I did make some rootfs tweaks, so I guess it's possible it's using the wrong firmware...?
Someone had a wifi issue, rebooted and it went away. I hate wifi .
Click to expand...
Click to collapse
I rebooted the phone, but it doesn't work...Here's a logcat, if you need another type of logs, please tell me...

nickleby said:
I rebooted the phone, but it doesn't work...Here's a logcat, if you need another type of logs, please tell me...
Click to expand...
Click to collapse
I just see a lot of this
E/WifiService( 1320): Failed to load Wi-Fi driver.
So uh... I think that indicates a modules mismatch? rm -rf /lib/modules and rebootski. I guess I need to make that change in init... copying and extracting every time doesn't work.

AOKP ICS preprepre alpha

This is a very pre-alpa build of AOKP ROM.Known serious issue are h/w buttons,not all are working correctly,use onscreen ones.More functional update will be very soon
Credits
Goes to everybody working on ICS for hero and heroc
P.S I took updater-script from HeroICS ROM,hope guys wouldn't shot me
http://www.mediafire.com/?2qb7fk2w8dyiibw

:/
ported from where? more details..

1ceb0x said:
:/
ported from where? more details..
Click to expand...
Click to collapse
This one is ported from WFS,now compiling new wersion from sources

not bad few issues\recommendations after installing:
Max speed of 710 is a bit keen (default of 691 ?)
Recommend latest Nova Launcher (1.2 - lots of bug fixes)
SuperSU rather than SuperUser
Remove pointer following boot-up
Updater script saying installing CM 4.0.3 needs edit as 4.0.4 is installed ...
Advise that gapps are not included
Please dont take this as criticism, I certainly couldn't do this (tho i might have a bash somepoint)
I'd be happy to be guinea pig for testing further builds if you'd to pm me.

awesome! glad to see you guys have an aokp port now.
about the hardware buttons, wouldnt that have to do with the /usr folder? try to replace key layout related stuff with ones from heroics, and it should work.
if you need any help let me know

Download link not work correct..and one question if i understand good this is new port from new HTC Desire C ROM....ICS 4.0.4?
Thanks
P.S.Good will be to make your tread with more exact info like ROM version images from phone,change log and e.g

What works and what not?

jogai said:
What works and what not?
Click to expand...
Click to collapse
Hardware buttons except for menu, home and back (correct me if I'm wrong) don't work. However Keynrtracker (or check here for more information and keynrtracker.apk) resolves all the buttons. The problem doesn't seem to rely in /system/usr/keylayouts, but somewhere else.
Haven't had time to try this ROM out any further.

Build now maintained under:
http://forum.xda-developers.com/showthread.php?t=1795990

AOSP 4.1.1 R4 (JRO03L) for Wingray

I've started a project building an AOSP ROM for wingray for my own amusement, and I thought I'd share, just in case someone wanted a nearly pure AOSP ROM with some carefully chosen tweaks.
As far as I am aware this is a fully functional ROM, but I am unable to test exhaustively so treat it as a pre-release beta, use at your own risk, blah, blah, blah.
I don't make any promises to continue development or fix bugs.
Features:
Built from pure AOSP 4.1.1 R4 (JRO03L) source with the following tweaks:
Fixed Guava compilation errors (thanks to CM10)
Added Busybox binary (thanks to ChainsDD)
Added Superuser package (thanks to ChainsDD)
Removed cellular and tethering references from wingray build (thanks to Peter Alfonso)
Disabled inclusion of AOSP recovery in the build (thanks to Peter Alfonso)
Fixed init.d support (thanks to CM10)
Working Camera
Bigger thumbnail size in recent apps menu
To do:
Horizontal recent apps menu
Reboot menu
T-Mobile Theme Chooser
More ...
Known Issues:
May encounter an issue with Superuser forgetting app permissions. Workaround: install SuperSU.

To install this ROM, I recommend wiping System, and Dalvik Cache, and performing a Factory Reset, but feel free to try it your way.
Make a Nandroid backup first!
Use standard Jellybean gapps.
http://goo.im/devs/zigackly/roms/wingray/AOSP_JRO03L
All feedback/bug reports welcome!

Well this is pretty neat, Thanks!

Glad you like it. I'm finding it quite snappy to use, even though it's not overclocked. I'll try to build in some more features as I get the time, if I can do it without losing the butteriness.

Hey thanx for your work.:good:
I wonder how this would run with a Tiamat/Eos Kernel ? Anyone tried?

Only one way to find out
Development is going a bit slowly in the last two days as I have been having trouble with corruption in my git repository.

i was just wondering if someone might ever do an aosp build for my xoom. thank you so much for your efforts, and for sharing the fruits with us!

cool deal man, i'll give this a spin and report back. so good to see others dev'ing for the Xoom! thank you thank you thank you

when looking in TB there is a system app listed with Chinese characters followed by 4.1.1-eng.zigackly.20120914.083408. What is this and can it be removed?
just like to add that first impressions go a long way and i dont normally look at the boot animation, but i did this time and it was way smoother than any other ive seen on my tablet, dont know what the diff is, but i like it
so far so good

Getting build.prop error 7 on install. Looking for Wingray in the build.prop line.
Might be a bad download? I am trying to update from CM10 and the stock update Stachre provides.

dodgefan67 said:
when looking in TB there is a system app listed with Chinese characters followed by 4.1.1-eng.zigackly.20120914.083408. What is this and can it be removed?
Click to expand...
Click to collapse
That will be the AOSP Chinese keyboard. There's a Japanese one too. Look in Settings->Language and input and you will see them as options. I believe you can safely remove them.
tincbtrar said:
Getting build.prop error 7 on install. Looking for Wingray in the build.prop line.
Might be a bad download? I am trying to update from CM10 and the stock update Stachre provides.
Click to expand...
Click to collapse
Could you try the download again? Build.prop should be replaced in system when you install, so it doesn't sound like a problem with where you are coming from.
MD5 checksum is 8cfdb670d42b5486f07f816f0e9a4791. You can check with MD5 checker from the play store.
If it's not a download problem, try a factory reset and wipe system before installing. Make sure you back up first.
In other news, I have fixed my git repositories although I had to redo all my work, but I am now working on a new build with improvements to the recents menu to take advantage of the Xoom's screen size. Hoping to implement bigger app thumbnails tonight and possibly a horizontal menu tomorrow.
The addition of a reboot menu is challenging. I made some changes based on the way Peter Alfonso does it and that didn't work, so I looked at the way CM10 do it and that didn't work either! I don't give up easily though. I'll take another stab at it this week. I'm learning this as I go along. Best way to learn, I think.
I'm also hoping to look at adding Theme Chooser this week.

Thank you for the md5, it matches, but still doesnt install.

z1gackly said:
That will be the AOSP Chinese keyboard. There's a Japanese one too. Look in Settings->Language and input and you will see them as options. I believe you can safely remove them.
Click to expand...
Click to collapse
thanks and looking forward to the updates!
may i suggest one or two? i like the options for things like setting quiet hours or profiles, being able to change toggles, etc. not sure how easy those would be to add in. i'm more than willing to help out and test things.
tincbtrar said:
Thank you for the md5, it matches, but still doesnt install.
Click to expand...
Click to collapse
what recovery are you using and are you sure you have done a complete wipe? (factory reset/wipe data, format cache, format system, wipe dalvik)?

Im using Rogue Recovery...did full wipe, dalvik, cache and system.
Perhaps its the recovery - but that doesnt make sense as every other rom ive installed worked well.
I modified the build.prop with some more operators to see if it will accept the model name or similar instead and I get a error 6 instead.
Maybe its just my Xoom? Nonetheless, ill wait for now, and stick with CM10 - its been pretty stable for me with no reboots.

tincbtrar said:
Im using Rogue Recovery...did full wipe, dalvik, cache and system.
Perhaps its the recovery - but that doesnt make sense as every other rom ive installed worked well.
I modified the build.prop with some more operators to see if it will accept the model name or similar instead and I get a error 6 instead.
Maybe its just my Xoom? Nonetheless, ill wait for now, and stick with CM10 - its been pretty stable for me with no reboots.
Click to expand...
Click to collapse
understandable. maybe try TWRP recovery just to make sure? if you have the time or are up to it?

I guess I could try TWRP, but I dont like how I always have issues with mounting sd with it...its why I stick to Rogue.
Ill give it a shot later on with TWRP to try and pinpoint the cause.
Edit: Tried TWRP and it flashed. Interesting! Thanks a bunch!

Build 7 added with larger app thumbnails in the recent apps menu. Available for download in post 2.
I'll look at what it might take to add those features, dodgefan67. I'm looking to implement the ones in my wish list in the OP first though.
I also need to get my head around merging in some improvements from the AOSP code base from after 4.1.1 r4.

The build.prop error is caused by an assert in the updater-script which checks you're installing the ROM on the correct device.
You could extract the updater-script and remove the assert, then replace the updater-script in the ROM.
It's in /META-INF/com/google/android in the zip.
I'm trying to get hold of a build.prop from a wingray which exhibits this problem, so I can correct for it in the script, but I expect yours will be fine now.
Worst case I can just remove the assert, then if someone flashes it on the wrong device it's their lookout, but I'd rather add the variant which is causing the problem to the assert.

I'm going to have to halt development on this for a time whilst I work on some stuff for my Nexus 7. I've updated build 7 so it will work with Rogue recovery. Back in a little while.

thanks for the update!

[ROM][WIP][5.0]Android L System Dump Port

Hey Peeps, I've been tinkering with the system dump and would like to cooperate on bringing Android L to the Galaxy Nexus, hopefully before code release we could have at least an operational/booting port/build
It Currently
--------------------
Reboots Back to Recovery, Kernel Boots, Build.prop is valid enough, fits currently in the GNex's System Partition fine
It Does Not
--------------------
Do Anything Else, last_kmsg and dmsg attatched
ROM Will State ShinyROM, i only used the binaries and installer zip from that
ROM is/Will be here! https://drive.google.com/folderview?id=0B9Wl2sHjHmR1SmlneHF0RGxVVE0&usp=drive_web
Mods, if this is too early/not enough to be in development threads, please go ahead and move me

+1 For quick start on this! I currently use toro so it is much appreciated. Just say if you need anything. :highfive:

KShion619 said:
Hey Peeps, I've been tinkering with the system dump and would like to cooperate on bringing Android L to the Galaxy Nexus, hopefully before code release we could have at least an operational/booting port/build
It Currently
--------------------
Reboots Back to Recovery, Kernel Boots, Build.prop is valid enough, fits currently in the GNex's System Partition fine
It Does Not
--------------------
Do Anything Else, last_kmsg and dmsg attatched
ROM Will State ShinyROM, i only used the binaries and installer zip from that
ROM is/Will be here! https://drive.google.com/folderview?id=0B9Wl2sHjHmR1SmlneHF0RGxVVE0&usp=drive_web
Mods, if this is too early/not enough to be in development threads, please go ahead and move me
Click to expand...
Click to collapse
hello can we flash this now?plus it says in build prop that its for maguro

hutchjim said:
hello can we flash this now?plus it says in build prop that its for maguro
Click to expand...
Click to collapse
I'm sorry, but did you even READ the post you quoted? it says "currently will reboot back to recovery"
so it's not really USABLE, but it's a START towards logs and figuring out what needs to be changed IF it can get to the point of boot& run

its awesome that you got it this far i tried to but it did what you said it rebooted into recovery thank you

hutchjim said:
hello can we flash this now?plus it says in build prop that its for maguro
Click to expand...
Click to collapse
Its stated as maguro for comparability with apps Verizon blocks, forgot I did that until now technically you can test it til it boots really on any Galaxy Nexus, you just won't gave data

What I've Deducted as of far
Kernel Needs Compiling, without source I dunno how to manage that
Init is trying to load KitKat based Binaries and not finding them due to renaming in L
Assuming theres a lot of Qualcomm Specific code here, as the CPU halts first before rebooting

^its possible but you need a skilled kernel dev. What I'm thinking (but I'm no dev) would be to decompile the n5 (android L) kernel, compare it to the n5 (kk) kernel, and apply similar changes to the gnex source and compile the kernel.
Just my 2 cents.

http://forum.xda-developers.com/galaxy-nexus/general/porting-android-l-lpv81b-to-tuna-help-t2796203/page3

wouldn't it be possible to just port the systemui and some other stuff and get the material ui, lockscreen, notification pulldown and basically everything else you actually see, even if the performance tweaks and such aren't changed?

KShion619 said:
Kernel Needs Compiling, without source I dunno how to manage that
Init is trying to load KitKat based Binaries and not finding them due to renaming in L
Assuming theres a lot of Qualcomm Specific code here, as the CPU halts first before rebooting
Click to expand...
Click to collapse
Why not just copy over some of the apps that make up the ui of L and edit the build prop so they act as if they are in an actual l installation?

dreamwave said:
wouldn't it be possible to just port the systemui and some other stuff and get the material ui, lockscreen, notification pulldown and basically everything else you actually see, even if the performance tweaks and such aren't changed?
Click to expand...
Click to collapse
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.

shwise said:
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.
Click to expand...
Click to collapse
good luck, it would be fantastic to at least get a bit of a port before the official launch so we know what to expect kind of. and are you sure you mean July? That's like a week
---------- Post added at 05:13 PM ---------- Previous post was at 04:56 PM ----------
shwise said:
I am actually currently working on this, and have run into a roadblock deciding which l libs to include. I hope to have it working by the end of July.
Click to expand...
Click to collapse
also if you tell me what the libs are I can try and make a couple decisions for you

Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise

shwise said:
Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise
Click to expand...
Click to collapse
I could at least beta test so long as I am allowed to show it off to my friends
also, how is it coming so far? BTW I have the sprint galaxy nexus, so how hard is it to change it from verizon or gsm to sprint after you port them?

shwise said:
Yes, I do mean July (setting high goals), and thanks for the offer to help. When saying "libs," I an reffering to the files in /system/lib.
Thanks for the support,
Shwise
Click to expand...
Click to collapse
approximately how far are you two days of?

dreamwave said:
approximately how far are you two days of?
Click to expand...
Click to collapse
Thanks for keeping an interest. I have gotten it to boot he kernel, and the actual OS immediately crashes due to the all apks crashing at once I assume. I will continue working on the libraries, but I may give up and wait for the actual release to build a ROM if it continues to fail.

I've been working on this as well, from what I can tell, there are unmet dependencies in libc.so, and there are some additional libraries that were added in KK AOSP that don't seem to be in any of the roms I've checked so far, libunwind.so is the major one.

shwise said:
Thanks for keeping an interest. I have gotten it to boot he kernel, and the actual OS immediately crashes due to the all apks crashing at once I assume. I will continue working on the libraries, but I may give up and wait for the actual release to build a ROM if it continues to fail.
Click to expand...
Click to collapse
are they recognizing it is not a valid android l installation? can you send me what you have so far so I can take a look?

dreamwave said:
are they recognizing it is not a valid android l installation? can you send me what you have so far so I can take a look?
Click to expand...
Click to collapse
Any progress on this guys?