yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Croc97:
It's because the system folder on this zip is an image and not a folder. Try with the v2 if you really want to try to get it booting (but if you have the VYL00M eMMC it won't boot).

Nexus 5 + Lollipop and Franco Kernel r66
[Samsung Galaxy Nexus] Ashutos1997:
Yea, atm there's no way to boot it on VYL00M eMMC chip based gnex's
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Sorry for the noob question but is the VYLOOM eMMC chip bootloop issue rom related or is due to some problem in android lollypop and will this issue ever be resolved. I'm desperate to get a taste of lollypop :'(
[Samsung Galaxy Nexus] Carlos_Manuel:
I 'm sure the EMMC VYL00M problem is kernel related..

This won't fix the problem:

http://git.omapzoom.org/?p=kernel/omap.git;a=commit;h=3550ccdb9d8d350e526b809bf3dd92b550a74fe1

but maybe some changes from newer kernels may help to fix the booting problems.

I've tried to find fixes, but I couldn't find anything else...

edit: I'm not sure if this is useful..:

https://android.googlesource.com/kernel/x86_64/+/836dc2fe89c968c10cada87e0dfae6626f8f9da3

[MENTION=3390093]MWisBest[/MENTION] is your ROM (LP 5.0) using newer DDK? that's why camera isn't working correctly?
[Samsung Galaxy Nexus] :
First of all: Good job!

Has anyone else issues with crashing webview? Applications like feedly (and even the AOSP browser) are crashing because there is something wrong with webview. I would have made some logcats if I had more time.

Besides that, it's working really good as a tablet (because of the broken RIL ;)). RAM usage is a bit high, but this won't be possible to fix (old device, new OS with higher RAM needs)...

If anyone is interested: Encryption is working flawlessly and it's nicely done in Android 5.0!

All in all: Nice build that is already useable if you don't rely on webview and mobile network. I'll keep it on my Galaxy Nexus.

Keep the great work up and I'm looking forward to a fully working, pure AOSP ROM on the last Nexus device with a removable battery. ;)
[Samsung Galaxy Nexus] MrJoas97:
I have the same problems concerning the webview. I found the time to make a logcat.
[Samsung Galaxy Nexus] Janzomaster:
Chromium is broken, says so in the first post
[Samsung Galaxy Nexus] virtual-metal:
I Flashed that 5.0 beta build but on boot it shows only google logo not going to next boot step :(
[Samsung Galaxy Nexus] coleburns:
Read the 1st post. I had to the same problem. It has to do with the type of chip in your device i believe.
[Samsung Galaxy Nexus] Master94ga:
Just wait next build, they are working on it :)
[Samsung Galaxy Nexus] jonathanpeter:
The new test zip for VYL00M is not working for me. I get the same boot loop I got with the earlier zip.
[Samsung Galaxy Nexus] cabalio83:
http://xdaforums.com/omni/general/omnirom-booting-android-5-0-friendly-t2933101

Thank god GNex has a REALLY active device maintainer :D:D
[Samsung Galaxy Nexus] pvkiniyan95:
Google Chrome works flawlessly for me, BTW that music shutter while locking is gone
[Samsung Galaxy Nexus] sasuketobi:
Facing the same issue

I'm facing the same issue, I installed the v2 zip and selected to reboot into system. I'll collect the logcat next time. The chip is V3U00M.
[Samsung Galaxy Nexus] santi1993:
are u using the last recovery cfg @ ext4? did u flashed from stock?
[Samsung Galaxy Nexus] eternal70:
[MENTION=3390093]MWisBest[/MENTION] so the google camera works. But after take one photo it FC. Here's the log. Hope that's help

https://docs.google.com/file/d/0B7SqITe__f5KN0dvbFYxUk1oOGc/edit?usp=docslist_api
[Samsung Galaxy Nexus] budhiprasttt:
I succes flash with cwm 6.0.45

Bug:

-Camera not work

- RIL

I cant see the google play store for the gapps ,

Sorry for bad english
[Samsung Galaxy Nexus] Ashutos1997:
I become sad eveytine I see V3000M users enjoying L :( . BTW as it's early build so bugs will be there . And u can download play store apk.
[Samsung Galaxy Nexus] Croc97:
Guys but if you try to port a kernel like the dirtyv or the fancy kernel? Won't it boot on VYL00M eMMC?

Nexus 5 + Lollipop and Franco Kernel r66
[Samsung Galaxy Nexus] ScardracS:
We are working on the new GPU drivers so kernel like Fancy, DirtyV and other can't help us right now.. We know we are able to boot it wirh older GPU but the eMMC bug still remain so we prefer to work on the new one
[Samsung Galaxy Nexus] sagara.sandaru:
Do you think this eMMC bug can be fixed? I couldn't resist but asking this sorry! [emoji24]
[Samsung Galaxy Nexus] ScardracS:
I hope yes
[Samsung Galaxy Nexus] sagara.sandaru:
Oh thanks! You made my day! :)
[Samsung Galaxy Nexus] Croc97:
So isn't the problem kernel related?
[Samsung Galaxy Nexus] Carlos_Manuel:
How can you be sure that Lollipop boots on Nexuses with older eMMC with older GPU? As if the new GPU drivers works on the Nexuses with VYL00M on KitKat, it should also work on Lollipop.

My guess is that the eMMC problem is in the kernel, drivers/mmc/.

I asked from Ice if he knows anything about this thing and the issue could be maybe a timing issue and the device may not have the proper timings set... I don't believe that GPU has something to do with this boot loop problem on Nexus...
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Does the eMMC bootloop issue mean that the updated gpu drivers wont work on these devices
[Samsung Galaxy Nexus] freshgiammi:
OH GOD PLEASE

GPU is not involved! We just can't boot with the older drivers because of modifications in the device tree. We should revert those to use the older GPU DDK, but we never will because we're trying to pull the switch on the older ones.

So please, we still don't know what's up with the EMMC bug. (Probably some secure erase thingy)

EDIT: Lollipop is able to boot with older DDK, but still a no go on that buggy EMMC.
[Samsung Galaxy Nexus] Ashutos1997:
Can anyone for just once build lollipop with older ddk which boots on VYL00M eMMC chip. Then all people will be quiet and won't ask same question again and again.

Just saying.
[Samsung Galaxy Nexus] Carlos_Manuel:
There nothing to do with the device tree. If there is then only fstab. I've already checked device trees for grouper, mako and n9 and I've updated my device tree for lollipop and MwisBest has similar changes, actally all the required Lp changes.

I've made research and I've found a few commits that may possibly fix the emmc boot loop thing. Easiest way would be to commit k3.4 emmc commits to 3.0 kernel. Or if someone can get any kind of logs like a kernel log. I can make tests myself later tonight or tomorrow as my nexus also has the old eMMC card VYL00M

The problem is in the kernel.
[Samsung Galaxy Nexus] Master94ga:
Is no sense, users have just to wait...
[Samsung Galaxy Nexus] freshgiammi:
Older DDK will NOT fix VYL00M. THIS IS NOT A DDK PROBLEM

There are modifications in the device tree for DDK1.9. If not, how the hell did we got camera working on KK?

And please, share the commits here and we will discuss them in the team hangout.
[Samsung Galaxy Nexus] Croc97:
Carlos why don't you help them with this port?
[Samsung Galaxy Nexus] Carlos_Manuel:
I am not talking about the camera!!

I was speaking about the emmc boot loop problem. and I meant that this bug, issue or whatever is not device tree related problem. It's a kernel problem

Read posts from a few pages back and you find a post with the commits that I posted which probably won't fix this but may help...

I've been trying to help and also I'm working on my own ROM..
[Samsung Galaxy Nexus] chall32:
Hey all, sorry if this has already been posted, but I found this excellent page that details the eMMC bug really well: http://wiki.cyanogenmod.org/w/EMMC_Bugs

Also goes on to discuss VYL00M and the version firmware we have: 0x25...

"Samsung has provided*a kernel patch*to Google which applies a firmware hotfix every time the chip is booted, fixing the problem." ...apparently...
[Samsung Galaxy Nexus] thagringo:
someone correct me if im wrong, but that has nothing to do with the mmc problems relevant here.

what you have posted is, as far as i know, known mmc bugs some chips had ( or have) that basically rendered the mmc storage useless after calling some erase instruction ( or whatever).

IOW, you ended up with a hardware bricked device or corrupted data.

These are known and have been adressed.

what has been discussed in this thread so far is a that VYL00M based mmcs simply do not boot the LP rom these guys have put together, which is a different story.

This is software related and it is not yet known if this is strictly kernel related or because of all the changes that were made in the devtree these guys are usning for the new pvr gpu drivers.

The app linked in the OP has only to be used to know if you have such hardware, not to detect any actual hardware problem relevant to the boot failure discussed here.

back on topic : can i ask if there are any kernel logs around to look at ?

I have no clue about linux in android world but im quite good ( i think...) when it comes to read logs and have developed myself for the linux kernel ( in x86 & arm world) previously.

thanks for your hard work guys !
[Samsung Galaxy Nexus] chall32:
Okey cokey cool
[Samsung Galaxy Nexus] theBlackEnd:
Check this post, [MENTION=5159369]grh35[/MENTION] attached a kmsg log.
[Samsung Galaxy Nexus] Carlos_Manuel:
EDIT: Deleted..

Maybe this is a fix for that:

https://github.com/Dreams-Lp/platfo...mmit/e9d02e32d4be35e15472eb7acfb526c0671cc379 I took this change from grouper. Mako has that same line.
[Samsung Galaxy Nexus] thagringo:
that refers to system ram i guess, would be very surprised if smartphones support that.

cheers
[Samsung Galaxy Nexus] Carlos_Manuel:
yeahm.. that line isn't the problem... I must read the log again.. :D
[Samsung Galaxy Nexus] MWisBest:
New build up, I haven't had time to check all the posts that've popped up in the thread recently, I'll do that later tonight!

I think the VYL00M eMMC issue should be resolved with this build, give it a try and let me know please!
[Samsung Galaxy Nexus] lo97:
News about phone,sms and mobile internet?
[Samsung Galaxy Nexus] alboz83:
Very thanks but i read that RIL is totally broken yet. I must wait when the sim works well
[Samsung Galaxy Nexus] Ashutos1997:
Sir, same process as before na ?
[Samsung Galaxy Nexus] MWisBest:
Just download the zip, and flash in recovery. The ROM might take a few minutes to flash however.
[Samsung Galaxy Nexus] Ashutos1997:
I mean the same process as previous ? Flash ROM ,unmount , flash gapps, remount ?
[Samsung Galaxy Nexus] jonathanpeter:
Yes Asutosh.
[Samsung Galaxy Nexus] the_f4b1:
Oh my god. It's really working. You're doing Duartes work here! Thank you so much!
[Samsung Galaxy Nexus] maxiv:
delete pls.
[Samsung Galaxy Nexus] Ashutos1997:
Booting ?
[Samsung Galaxy Nexus] the_f4b1:
Yes. Completely up and running.
[Samsung Galaxy Nexus] vangtsog:
I have VYL00M and lollipo works for me, thanks MWisBest!
[Samsung Galaxy Nexus] Ashutos1997:
What process u followed ?
[Samsung Galaxy Nexus] Carlos_Manuel:
[MENTION=3390093]MWisBest[/MENTION] could you please tell me what was the fix for the eMMC problem? :)

I din't find anything which would be the fix for that from your github page.

I can get myself ready to build LP for Nexus in 5 hours when I'm back in the dorm.
[Samsung Galaxy Nexus] Ashutos1997:
Booting. Thanks [MENTION=3390093]MWisBest[/MENTION] (y)
[Samsung Galaxy Nexus] the_f4b1:
OK. One problem for me though. Even though I flashed the gapps-package they are not installed. Nothing that bugs me because I'm not using this phone as daily driver just as an information.

//E:

Seems like the play store is installed. Taking everything back ;)
[Samsung Galaxy Nexus] freshgiammi:
4.7 GCC on kernel. 4.8 never played good on gnex.
[Samsung Galaxy Nexus] Carlos_Manuel:
Are you sure that was the problem? :D that just doesn't sound so right. It's funny if only the toolchain was causing this problem.
[Samsung Galaxy Nexus] freshgiammi:
It's that, probably. I don't think it's the old otapackage.
[Samsung Galaxy Nexus] MWisBest:
Oh, was about to say to make sure /system isn't mounted before flashing GApps. Not sure what's messing that up lately...
[Samsung Galaxy Nexus] NSD:
Oh man this is amazing, it works now! How does one go by acquiring root on 5.0? Flashing supersu zip in recovery will do it?
[Samsung Galaxy Nexus] Master94ga:
Very good work [MENTION=3390093]MWisBest[/MENTION]! :o
[Samsung Galaxy Nexus] pvkiniyan95:
Yes it does
[Samsung Galaxy Nexus] Ashutos1997:
Update : Not even getting flashed .

E : Error executing updater binary in zip.
[Samsung Galaxy Nexus] freshgiammi:
Unmounted /system ?
[Samsung Galaxy Nexus] AbhishekS:
Still not working. Be patient!
[Samsung Galaxy Nexus] Ashutos1997:
Yes
[Samsung Galaxy Nexus] lukappaseidue:
One silly question? WIll be released a stable version of 4.4.4 kitkat rom with latest stable GPU Drivers?
[Samsung Galaxy Nexus] Ashutos1997:
OK so it booted. The error was that recovery was corrupt I mean not working correctly.

Thanks [MENTION=3390093]MWisBest[/MENTION] (y)
[Samsung Galaxy Nexus] pvkiniyan95:
Being a Linux user I just found that certain Linux communities are moving to Clang compiler, will that do anything good [MENTION=3390093]MWisBest[/MENTION]
[Samsung Galaxy Nexus] qtoo941:
As far as i know you cannot kill settings :D So this feature should work correctly. Anyway, no problem for other features. Maybe in some of next builds (maybe next?!) we will feel the new features :)
[Samsung Galaxy Nexus] Alkemix:
Can You compile this rom by Sabermod 4.9.1 toolchain or Linaro 4.9.1 by Christopher83?
[Samsung Galaxy Nexus] pablomoreno:
I'm trying the rom and I find it very good, responsive and fast.

A very annoying bug: when trying to customize the colors of the LED notification of the application must be in error and closes automatically, I hope that this bug will be fixed soon.

For the rest there is to complain about, really a great job.
[Samsung Galaxy Nexus] rkwhyte2:
I'm pulling down the new build as we speak and hope it fixes the problem I have now seen twice. I lose the ability to adjust my volume via the rocker bar. I have to restart or power down the phone to get it back. Anyone else seeing this issue.
[Samsung Galaxy Nexus] Alkemix:
I've just found issues by supersu 1.99r3 ... supersu doesn't work well into this release (4.4.3) ..maybe chainfire must update supersu again ...

root lost .. supeuser seems work solid

Yes ... I confirm bug ...
[Samsung Galaxy Nexus] Suo.Eno:
[MENTION=3390093]MWisBest[/MENTION] got his own special sauces going on for this gig so best let him handle the mix. Plus are these 4.9.1s toolchains 4.4.3/KTU84M ready? I must have missed the links.
[Samsung Galaxy Nexus] Alkemix:
Kernel compiled by those toolchains works very very fine into 4.4.3 ROMS... Why ROMS should have issues ?
[Samsung Galaxy Nexus] Suo.Eno:
Said I missed the links and I haven't ran SmittyV's latest yet if that's not obvious.
[Samsung Galaxy Nexus] AllAboutTech:
Hi,

This ROM is AOSP or it have customizations?

If yes, what are them?

Thank you.
[Samsung Galaxy Nexus] qtoo941:
Man, you must be more high than me.. or just d**b -.-
[Samsung Galaxy Nexus] AllAboutTech:
Hi,

Can someone post some print screens with the 4.4.3 build?

Thanks.
[Samsung Galaxy Nexus] MWisBest:
The last time I tried to use GCC 4.9 (which wasn't very long ago), the ROM wouldn't boot. The thing about Linaro's toolchains is that they will generally have many of the improvements from the next-up GCC version, so for example, Linaro GCC 4.8 will contain many of the ARM speed improvements you'll find in a stock GCC 4.9, and with GCC 4.9 being so new right now it's not that big of a deal.

I will be looking into that, thank you for the bug report!!

I've had this happen with a couple intense games, what I've found fixes it is pressing the Recents button. Give that a try next time.

This ROM already contains Superuser out of the box, there's no need to flash SuperSU!

There are differences in the toolchain between the ROM and the kernel, that's why the kernel is compiled with a different toolchain when you build a ROM (for an ARM CPU that is).

Go have a look into OmniROM. It's what this ROM is based on. It has just about every customization you can think of in my opinion.

Hey hey hey, be nice!! This is a mean-free zone!
[Samsung Galaxy Nexus] Alkemix:
Sure .. but superSu is better ;)

[MENTION=3390093]MWisBest[/MENTION] Can You solve a bug on dialer?

Bug is:

If You disabled into "developer options" all animations ... and after You open (for the first time) the dialer (keyboard to compose a number) keypad doesn't appear .. You must enter on It again !

By animations (also 0,25x) It doesn't happen... Why ? Can You fix It ?
[Samsung Galaxy Nexus] MWisBest:
Holy crap that is quite an oddball bug you found there! I'll see what I can do about it but it probably won't be fixed in this next build.

As for SuperSU being better... how is that?
[Samsung Galaxy Nexus] pianistaPL:
Good question, i really don't know what is better in SuperSu, personally when i run an app which needs root, i grant permissions and that's all :P

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] Alkemix:
SuperSu is faster than superuser to bestow root permissions; moreover some apps like Titanium backup, flashify for example work better by superSU. Metalspring into his Omnimetal rom include supersu into menu settings preferences.
[Samsung Galaxy Nexus] MWisBest:
There aren't any issues with an app working better with one superuser over another anymore, that was just an issue with the initial transition from Android 4.3 to 4.4 which has been worked out for months now and TiBu really needs to get rid of that stupid warning as there are absolutely no issues with this superuser.

I used SuperSU just recently for when I was still on the stock OS for my Kindle Fire HD 7", and I don't see how you can call it faster, in fact the UI of it when asking for root permissions was sluggish for me.

The Superuser with this ROM is open-source. SuperSU is not open-source. I will be sticking with open-source software as much as I can.

If you truly have a complaint with the Superuser in this ROM, let me know what it is and maybe I can fix it. That's the beauty of it being open-source.
[Samsung Galaxy Nexus] iHeadhunterz:
- I sleep through the vibration too haha, I literally have like 3 alarms on my phone set up with different tones and I still have my alarm clock ringing. I'm just a heavy sleeper :/.

- But regarding the lower sound, that's the step I was leaning on, I use V4A, so I got it to work. It's definitely louder. But thanks for that info, ill make sure not to go over the 6 db mark just be on the safe side.

- Got all the quirks fixed up and I am enjoying this ROM! Thanks again Man!
[Samsung Galaxy Nexus] NSD:
Doesn't seem to work. SuperSU icon appears but does not launch.
[Samsung Galaxy Nexus] cqloveqc:
[MENTION=3390093]MWisBest[/MENTION]

Hi, thx, for the great job, i want to make a donate, i've lot of google play credit, so want to know if you have paid app, so that i can buy one to help, or maybe you create one, and then, i buy it

thanks again
[Samsung Galaxy Nexus] shahrukhraza:
Thank you for your hard work [MENTION=3390093]MWisBest[/MENTION]

Is anybody having trouble with swyping using the stock keyboard?
[Samsung Galaxy Nexus] Oxirane:
Correct me if I'm wrong, but RIL being broken means this currently doesn't have telephony services, right?

Either way, really nicely done for making this much progress already.
[Samsung Galaxy Nexus] marcovittori:
yes,you can't phone,send sms,use data or other telephone service
[Samsung Galaxy Nexus] ScardracS:
So, in the last build there are 2 things that don't work: ril (the most important and the thing we are focused in that moment) and the camera (you can replace it with another camera app and it should be work enought).. The RIL, for the noobs who don't know it, is the radio interface layer, the thing wich provide radio connection on telephony (ceck wikipedia for more accurate information)
[Samsung Galaxy Nexus] bankov:
Just trying the 11/09 build, location is not working, youtube videos not working too. Camera 360 from playstore is working perfect also flashlight is working too. NO lag in recents.
[Samsung Galaxy Nexus] flip360:
Latest build working good on the buggy eMMC, overall very satisfactory speed, thanks MWisBest and everyone involved, cant wait to see what optimizations do to the ROM. Would kill for a working RIL in this state though :) GNex Lives On!

Cheers!
[Samsung Galaxy Nexus] santi1993:
Rawwwwwwwr i'll love you, ill buy a i9250 vyl000m only to help u test :D
[Samsung Galaxy Nexus] objaa:
Work nice on my gnexus vyl00m chip. Now wait RIL and SuperSU ;)

thanks, [MENTION=3390093]MWisBest[/MENTION]!
[Samsung Galaxy Nexus] cqloveqc:
I think you need to flash the latest SuperU zip, i check, it's 2.17

I first flashed 2.01, not worked very well
[Samsung Galaxy Nexus] ScardracS:
Superuser have some probs working because it was use a "bug" in the android's ramdisk codes wich is fixes on android 5.0, so it's better expect for a stable release for the superuser... You can ceck G+'s post by chainfire for more informations
[Samsung Galaxy Nexus] flip360:
Is there some place where we can check for progress, apart from this thread like github, G+ or else?
[Samsung Galaxy Nexus] jhonnyx:
Hmmmm I think you can check in the first page, unless you want to pay for a premuim service to e-mail you when a new build is out.

Picture in your mind that you're the developer and you have physically behind a glass wall and there are a bunch of guys at the other side looking at how the developer progresses, however they get bored and start punching at the glass wall.... well.... this is that kind of the situation.... how would you feel if you're the dev?

Sorry, once again, not trying to be rude, but keep that in mind. I'm pretty sure this fantastic group of developers will get your device refreshed with Android 5.0, so, stay tuned and keep calm. If not, visit this website: http://www.wikihow.com/Be-Patient
[Samsung Galaxy Nexus] Master94ga:
Just go with your browser here and press 5 every 5 min ;)
[Samsung Galaxy Nexus] dpunx:
Works really fast and really good. It's amazing the way of this project.
[Samsung Galaxy Nexus] musical_chairs:
You could always click on MWisBest's xda profile, find on there the link to his github, click on the 'public activity' tab and wear out your F5 key there...
[Samsung Galaxy Nexus] Driver007:
Yeah it's booting :D

First impression:

Installed Facebook and all phone just hangs :D

YouTube is not working

Tried few other apps and it feels pretty snappy.

Just needs mobile network to be working and it could be daily driver for me.

Congrats to developers.
[Samsung Galaxy Nexus] Sain Choe:
Yeah...really...really thanks! :)
[Samsung Galaxy Nexus] Kewyang:
Hi All,

Currently I am on Kitkat FML beta version with 1008 kernel... Quite smooth but i notice it wasnt big mem.(or I dunno). Can you share me the latest kernel for kitkat?

Thanks
[Samsung Galaxy Nexus] garyngkt:
Flashed 11/09 version and booted fine. Now playing around L. Thanks for the effort
[Samsung Galaxy Nexus] pvkiniyan95:
that was an amazing build, no aosp browser issues, smooth recents. About to check imap issue.
[Samsung Galaxy Nexus] AbhishekS:
Well such wonderful compliments for the builds are making me jealous now! Feeling so unfortunate that I cannot try it as the GNex is my daily driver and I cannot survive without my phone calls! :P
[Samsung Galaxy Nexus] vivekbalan:
Well, I could not resist too. So I put my sim card into old Samsung galaxy Fit phone and started using lollipop in my

primary nexus phone. Thanks [MENTION=3390093]MWisBest[/MENTION] and the team for bringing lollipop into our phone.
[Samsung Galaxy Nexus] flip360:
Thanks man was looking for that kind of updates, no thanks to jhonnyx and his creative answer on how devs work
[Samsung Galaxy Nexus] dezful:
Just installed lollipop on my maguro. wow, its snappy! well done mate! camera does not work. screen shot works through pressing down+power
[Samsung Galaxy Nexus] FreddyFernando_:
Just tested the Lollipop ROM. It is smooth. Cellular and camera doesn't work though. Pretty much everything else is bearable.