yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] otter34:
Thanks guys. I flashed the ROM, then booted up and back into recovery. Next I flashed FML-GApps-5.0.x-20150101-tuna.zip and booted up. BOOM IT WORKED!! The market didn't update and I had to go into accounts to manually add my google account but that's fine w/ me. I'll use titanium to restore my apps....too bad about lolipop's white background for everything. I'm not a fan of that.

Edit: So much for that idea. Any idea why the paid version of titanium doesn't show up in the market?
[Samsung Galaxy Nexus] demlv:
No clue why Titanium Backup is not showing up for you in the play store. But there is a way past the problem. Make a nandroid of your new Lollipop rom. Then restore your KK nandroid (you made one, right?) then boot into Android, go into Titanium Backup's options and look around. Titanium Backup can make a flashable zip of itself. Restore to the lollipop FML nandroid, then flash the zip made by titanium backup et voila! Good luck!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RW-1:
Before that, try the play store website as well, perhaps you can send it to the device ...
[Samsung Galaxy Nexus] bsmitty83:
I'm pretty sure if you didn't wipe your sdcard , the titanium pro licence should still be there , if you download the free version it should automatically unlock itself . turns itself into the pro version, so to speak . I haven't used tibu in a looong time tho .
[Samsung Galaxy Nexus] christianpeso:
Which version did you use? He had a beta that worked and it looks like he pushed it to the front page as of today. That has the keyboard FC issue fixed. Try that micro version labeled 1-16-2015.
[Samsung Galaxy Nexus] otter34:
Normally it shows as "purchased" in the store. Thanks it's worth a shot.

I'll try that first.

Well that's interesting. I never knew that. I made the zip. I'll let you know if it works, that is if the above suggestions don't work then I'll flash the zip I created
[Samsung Galaxy Nexus] otter34:
Lollipop is ugly...titanium showed as being purchased.

How do i turn off the battery charging light?

Gesture typing doesn't work although its enabled
[Samsung Galaxy Nexus] bsmitty83:
Charge light cannot be disabled yet , for gesture typing install the google keyboard
[Samsung Galaxy Nexus] KShion619:
Hello guys my GNex got fixed! And now I'm back! (Can even overclock better now with my new Motherboard!) Did the recent build fix Ambient Display not working?

Sent from my Verizon LG G3
[Samsung Galaxy Nexus] Nephilim:
Not yet, I'm still waiting on that as well. This build is amazing none the less though.
[Samsung Galaxy Nexus] otter34:
Looks like there isn't any customization available like long press to kill or the ability to change tiles, etc. Is that because it's early on or is this supposed to be a pure stock experience? I thought I remembered customization before but I could be wrong.

Regardless, this is an incredibly smooth ROM
[Samsung Galaxy Nexus] MWisBest:
Sorry for the lack of updates lately! I've been busy with a different project that has required my full attention. I'll try to set aside some time to go through the posts tomorrow and answer questions etc. As always, thank you for flying FML!
[Samsung Galaxy Nexus] otter34:
If I'm charging, When I turn the phone off it gets stuck and the only way to turn it on again is by pulling the battery first and then turning it on. I have it plugged into the charger and it shows that it is charging however if I unplug it then the charging icon still shows even three or four minutes later.
[Samsung Galaxy Nexus] Rushead:
That bug has existed since the dawn of 5.0
[Samsung Galaxy Nexus] otter34:
Is the alarm clock icon supposed to appear in next to 4g? Always did...important meeting in the morning. Using alarm clock plus...well I've added 2 more so something should work!

Edit: alarm clock plus didn't work but the other 2 did. Guess ACP isn't compatible with lollipop FYI
[Samsung Galaxy Nexus] fivefour:
After my phone dies I hold the keys to get into recovery, plug the phone in, boot from recovery.
[Samsung Galaxy Nexus] christianpeso:
[MENTION=3390093]MWisBest[/MENTION]

Will you incorporate the CM12 theme manager into your next build please?
[Samsung Galaxy Nexus] MWisBest:
NO. Just, NO.

The amount of problems it causes far outweighs its usefulness. I also am very distrustful of anything from Cyanogen Inc. In fact, not that long ago I heard multiple reports of Oppo Find 7's getting bricked by a CM nightly build (unrelated to the theme engine, but still, shows their level of testing).
[Samsung Galaxy Nexus] DBISGOD:
Any luck with adding a reboot menu option?
[Samsung Galaxy Nexus] PainFly23:
That really is the risk you take with nightly builds, but I know what you mean. Back when they were getting their new theme engine sorted out, there was a nasty bug that occasionally caused a mini bootloop when you pulled down the notification shade. The thing went unfixed for months, and almost every rom that was based on Cyanogenmod was affected as well.

Also, I've been meaning to ask this, but has anybody else had problems with hardware video decoding on the 1/08 build? I haven't seen hardly anyone mention this. I noticed it stopped working for me when I dirty flashed a while back. I've been back on 1/04 ever since then and it's now working fine.
[Samsung Galaxy Nexus] dj-bilbo:
Getting stuck in bootlooop when I try bsmitty's wicked awesome r5 or r6 kernel. So frustrating!
[Samsung Galaxy Nexus] bsmitty83:
Who's kernels ?? Lol [emoji12]

#iamnotkoush
[Samsung Galaxy Nexus] dj-bilbo:
Mouhahahahha yours!!! Of course. Sorry for the typo. Any thoughts on why bootloop? [emoji6]
[Samsung Galaxy Nexus] bsmitty83:
Figured it was that ducking awesome autocorrect feature .......[emoji6]

Not sure , maybe try a fresh FML install . I haven't had too many people report non-booting situations on the last releases . wish I could help more , but if it continues , while in a bootloop if you are by a computer , hook up your phone , type "adb shell " , then "busybox dmesg" , copy n paste the output and I'll take a look. If you can't get a shell , try to just grab a logcat with " adb logcat " won't be as helpful but better than nothing. [emoji2]
[Samsung Galaxy Nexus] dj-bilbo:
Ya I was thinking abt a fresh install too. Will try. Thanks for ur help

Edit: fresh install did the trick! ;)
[Samsung Galaxy Nexus] otter34:
My phone turned off for some unknown reason. I can't remember the last thing I was doing before I set it down (fully charged) on my desk. Is there any way to retrieve an error log so I can post it here for you or are you aware of this? It's been 4 days of stock and this is the first time it happened
[Samsung Galaxy Nexus] alfick3:
I have a question: I bought my son one of these for Christmas and he's installed this ROM. He's trying to get a USB OTG cable to connect. He has played around and gotten a USB - ethernet cable to work, but for some reason he can't get a USB stick to mount. He's tried stick mount from the play store, and it shows that it's mounted, but when he uses a file explorer he can't see anything there. He knows that there are files on the stick, but the phone doesn't properly mount it for him to see them.

Thanks in advance.
[Samsung Galaxy Nexus] PainFly23:
What file explorer is he using? Give FX File Explorer a try if you can't get it to work. I've been using it for a while and have had no trouble getting my thumb drive to show up with Stickmount.
[Samsung Galaxy Nexus] alfick3:
I believe that he's using EsFile explorer. I'll suggest that to him, thank you.
[Samsung Galaxy Nexus] xlabscat:
Firefox Crash

removed.
[Samsung Galaxy Nexus] Rushead:
I doubt the file explorer is the issue. Phones are very finicky about otg cables. You need to get one that's made for the specific model device you have. My GNex cable does not work on my wife's gs3. And there's no guarantee that it'll work even if it says made for GNex (it should but you never know).
[Samsung Galaxy Nexus] JoeSyr:
Are FML builds synced with the latest Omni changes when they're built? I'm still happy to wait on 4.4. while bugs are getting ironed out but I'm pretty curious to see the Material Browser update that was just merged into Omni 5.0. Always had a soft spot for the AOSP browser but eventually gave it up because it was getting so neglected.
[Samsung Galaxy Nexus] Rushead:
AFAIK, this is still AOSP based.
[Samsung Galaxy Nexus] bryantjopplin:
Is it a fat32 format or ntfs? Are you looking under SDcard/usbstorage.
[Samsung Galaxy Nexus] alfick3:
I believe that the stick is formatted to fat32. As far as where he's looking, I'm not sure. I'll have to check with him on that later when I get home.
[Samsung Galaxy Nexus] bryantjopplin:
Hmm this is interesting
[Samsung Galaxy Nexus] bryantjopplin:
Everything is working great for me, just one little thing. When using the phone, little pop sounds sometimes comes out of the speaker
[Samsung Galaxy Nexus] jcpowell:
Hahaha, same here... Thought it was just my phone
[Samsung Galaxy Nexus] Nephilim:
That's the touch sound, I thought it was a bug too but go into settings/sound & notifications/other sounds and turn them off. ;)
[Samsung Galaxy Nexus] jcpowell:
No, I use it with the touch sound, but this is different it's a little weird pop lol

His might be the touch sound and my phone is still haunted like I originally thought lol
[Samsung Galaxy Nexus] bryantjopplin:
Yeah its a little pop randomly. Weird
[Samsung Galaxy Nexus] oman0123:
I know what you guys are talking about. It's like when (in my experience) OC the phone too much it will freeze and makes that little pop noise when it reboots.

I get it too.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] bsmitty83:
If you turn touch sounds off , it won't happen , as [MENTION=2853378]Nephilim[/MENTION] stated. Its not an actual touch sound , but a bug or glitch associated with touch sounds
[Samsung Galaxy Nexus] Nephilim:
Exactly.
[Samsung Galaxy Nexus] bryantjopplin:
Wasn't sure if the phone would blow up lol
[Samsung Galaxy Nexus] Christopher8989:
This never happen to me after many flashed and re-flashed, but one time after restore it did, then I wiped everything and re-flashed anew and it's went away.
[Samsung Galaxy Nexus] Christopher8989:
over heating

I have a bad experience last weekend (still do). The phone overheated and auto turned off, and again even after cooled.

I left Waze on for a 2 hours drive and it got really hot after about an our and turned itself off. I turned it right back on and it booted fine but after a minute or so would shut off again. I used the car A/C to cool it until I can't feel any heat and it booted fine again but after about 5 minutes would shut off again. Since this is my only phone that I fear I might damaged it.

I didn't know whether any of you would want some files so I backed it up and wiped everything and restored from an earlier backup and it was fine through the night. This morning when I started the browser it shut off. I wiped everything and re-flashed anew. Everything went fine but after an hour or so but it shut off again.

I just backup to LS KK now and wait and see. Hope it's still OK...

---------- Post added at 09:52 PM ---------- Previous post was at 09:28 PM ----------

uh-ooh LS KK shut itself off too.
[Samsung Galaxy Nexus] bryantjopplin:
Turn down you frequency on the cpu
[Samsung Galaxy Nexus] Christopher8989:
I don't remember what settings LS KK or the backed up L were but the newly re-flashed L is stock setting, even the kernel.
[Samsung Galaxy Nexus] Christopher8989:
The backed up L was with bsmitty's R6 for L and Neph's V4 setting. All fine except for the long running of Waze or google map navigation.
[Samsung Galaxy Nexus] bryantjopplin:
Hmm maybe some other settings then.
[Samsung Galaxy Nexus] Nephilim:
My settings have a v5 that I updated when R6 hit. ;)
[Samsung Galaxy Nexus] Christopher8989:
Well so far so good with a clean re-flash. If tonight and tomorrow will be same then I think the over heating damage the battery. I went to a store and paid $40 for a Rayovac battery because I need it right away.

I noticed wildly different battery life reported from bootloader, TWR and within android. Anything from 9% to 53% to 99% all within the time I was trying to flash or restore and I thought that can't be right. It also crashed receiving phone calls. Just a loud buzz and froze up the screen.

I now lower CPU speed to 1200MHz. All other settings are still same as Neph's V4.

If it's just the battery then I'll buy another one online (which was about $10 last time) and will try running Waze for hours again on this weekend or the next once I have it.

---------- Post added at 03:12 AM ---------- Previous post was at 03:10 AM ----------

OK. I don't see it when clicking on your signature...

---------- Post added at 03:23 AM ---------- Previous post was at 03:12 AM ----------

Found it.
[Samsung Galaxy Nexus] bsmitty83:
Definitely sounds like a bad battery , I'd be surprised if a new battery didn't fix your troubles. Most of the heat is probably from the battery . and when my battery was going bad , it would do what you described for any high power use function like data, calls , WiFi .
[Samsung Galaxy Nexus] Christopher8989:
I tried to charge the bad battery outside of the phone and it indicates that it's full, and it's 4 volts when measure with a volt meter. I have 14 days to return the new battery so I'm thinking of trying the old one again. Not a good idea? A waste of time?

Would the heat just damaged the NFC part of the battery which is why the phone had different reading of battery life? What's NFC used for?
[Samsung Galaxy Nexus] dalvear88:
Hola! I'm trying to set up your settings, and I'm using the R7 Kernel, and I see you were using 'Illinois' for the TCP Congestion Control, however I only get the options for westwood, cubic, reno, bic, and htcp. Are the settings you have posted strictly for R6?
[Samsung Galaxy Nexus] Christopher8989:
R7? Downloading now thanks

---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------

New app startup very slow. Facebook even crashed 1st time up. I returned back to stock and OK now.
[Samsung Galaxy Nexus] zzpianoman:
A fully charged battery should measure 4.16-4.2 volts. If your battery that is "fully charged" is only measuring 4 volts, then it is defective.
[Samsung Galaxy Nexus] dalvear88:
Maybe I'm just not sure on what settings we should be using. For the Full Auto Kernels, should I be using the DirtyV/SmittyV Kernel: Settings?
[Samsung Galaxy Nexus] Nephilim:
My lollipop settings are still in test phase, don't use the OP settings on my thread, the ones you should use are linked in a post I made on the last page of my thread. ;)
[Samsung Galaxy Nexus] dalvear88:
Thanks so much! I was driving myself mad looking round and round haha.
[Samsung Galaxy Nexus] MWisBest:
Here's an update on how things are going!

I have been very busy with work and college; those have to come before things like FML. It's certainly not fair to my umm.. employer, if I'm not giving all the focus and time I can on my work, and it's not fair to me if I don't do the best I can in school. However, it's also not fair for me to not take a little break from these things and do fun stuff like working on FML! It's hard to find a balance, and last semester in school I slipped up a bit when I worked on the whole updated GPU drivers thing and the initial Lollipop builds; my grades were still good, but I know I can do better than I did, so I'm trying to avoid a repeat of that this semester (which means FML work is slowing down, as you may have noticed).

Last week I had a hard drive failure; thankfully, because of all the kind donations I've received from so many people which has helped cover some of my college costs (as well as gasoline dropping to less than $2.00 a gallon!), I had just enough money stashed away to splurge a bit on a replacement: a 500GB Samsung EVO 850 SSD. After some difficulties with installing Windows (which involved me screaming at my laptop a bit), I've got Linux and the majority of my Android dev stuff up and running. Thanks to the SSD, Android compiles two times faster now, which means I'll have more time to spend on FML.

Thank you to EVERYBODY who has donated to me!

Here's a little list of some of the changes that should be in the next FML build:

- More improvements to the camera:

--- Enhanced stability and some minor bug fixes.

--- Fixed Flashlight toggle ( thanks to [MENTION=3457922]stargo[/MENTION] ).

--- Proper calibration data used ( should fix color and white balance issues, thanks to [MENTION=2633638]Ziyan[/MENTION] )

- Kernel improvements:

--- Synced up with some updates from [MENTION=2633638]Ziyan[/MENTION], the most important of which will let [MENTION=4608636]bsmitty83[/MENTION] build just one kernel now.

--- Added screen color control finally.

--- Fixed an issue that may have prevented the compiler from optimizing things better.

- Removed charging LED, as it is annoying without being able to configure it in the settings properly.

If you have any questions that other users haven't been able to answer, please mention me with "@MWisBest" in your post!
[Samsung Galaxy Nexus] jguerdat:
[MENTION=3390093]MWisBest[/MENTION] - Good drive - have one myself. And just sent you a donation. Anything to remove the charging LED at night!
[Samsung Galaxy Nexus] RW-1:
MW, looking forward to the next build...

Off top, but computer related, anyone else on the Win 10 tech preview?

I'm liking it, though too many complainers on the start menu changes in 9926, they said we would lose re-sizing and get it back later, but complainers don't read the win blog ...

Ok, back to FML ...
[Samsung Galaxy Nexus] bsmitty83:
Kubuntu 15.04 here [emoji6]

I still have win7 ultimate activation codes lmao , I haven't had the need for windows in ages , especially since Ubuntu now supports Netflix natively in chrome .

Also have Kali Linux dual booted , but that's just for messing with the IT guy at my work lol , I keep him on his toes
[Samsung Galaxy Nexus] Christopher8989:
This doesn't have CM12 theme engine right? What does it use?

I'd like to make some minor changes. I set dpi to 240 and the nav buttons are smaller so there's now big gap between them and icons on the dock. I'd like to lower the dock a bit.

That and maybe make all icons bigger. Any suggestion as to where to look would be great thanks
[Samsung Galaxy Nexus] bothgoodandbad:
sweet

[MENTION=3390093]MWisBest[/MENTION], make sure you back that new HD up because once a ssd drive crashes, it's 99.9% over and no turning back. just sayin;)
[Samsung Galaxy Nexus] Rushead:
XDA rule #2

Read, read, read.

FML is pretty much the anti-CM

P.S. I've always run @ 290 dpi
[Samsung Galaxy Nexus] MWisBest:
Kubuntu 15.04 here too :good: how are ya liking Plasma 5? :cool:

BTW, thanks to OEM:SLP keys there's practically an infinite amount of Windows 7 activations...

I've always backed up the important stuff :)

Anti-CM... I like the sound of that :D
[Samsung Galaxy Nexus] bsmitty83:
Plasma 5 was the reason I installed 15. Its awesome imho , I don't think I'll be using anything else for a while. I'm surprised how smooth it is too , I installed the latest beta , beta2 I believe . its not like I have a powerhouse laptop , but it runs good .

Only issue I have is I haven't gotten chome to open yet. Tried both stable and beta versions. It installs fine , but it starts to open , then just disappears .

Edit : I was missing a few libs for chrome , had to force install them , now its all good .
[Samsung Galaxy Nexus] RW-1:
Hey, have a few questions on build.prop:

on shiny I have an additional line for RIL:

persist.radio.apn_delay=5000

and online i was reading how some N6 users were getting better results on VZW by adding:

ro.telephony.get_imsi_from_sim=true

Of course, I wanted to check with someone before I start playing around with build.prop, lest I make my phone unusable (back up in twrp first, but think this would just affect data not crash it)

thoughts?
[Samsung Galaxy Nexus] zzpianoman:
I have found that adding "ro.telephony.get_imsi_from_sim=true" causes the phone to pull the correct MCC/MNC pair from the SIM card (311/480 for Verizon). Without that line, MNC comes up as 00 causing only one APN to be recognized from the table. As a result, I use this entry in my ROM (CM12) and experience better data connectivity as a result. I am not sure if this is a CyanogenMod specific system prop, or if this is in AOSP - one way to check is to search the repos "for ro.telephony.get_imsi_from_sim" and see if it exists. It should be in frameworks_opt_telephony (possibly in RIL.java, but I don't know off the top of my head).

You can try adding it - worst that will happen is that it won't do anything. It's not going to cause your phone to crash or anything. After you apply the setting, open up APN editor and see if you have more APNs listed. Also, check your MCC/MNC and see if it matches 311/480.

As for persist.radio.apn_delay, that entry is used only for testing purposes as noted in the source code and might actually cause more harm than good (battery drain).

EDIT: I just confirmed that this entry is not present in AOSP, so it will not do any good for you to add this line to build.prop. And for future reference, ro.telephony.get_imsi_from_sim is located in RuimRecords.java and not RIL.java.
[Samsung Galaxy Nexus] RW-1:
Hey, thanks for checking that out. I feel that I'm getting the same data connectivity transitions since KK, but overall I like 5.0 better than 4.
[Samsung Galaxy Nexus] zzpianoman:
Yeah, there are a whole bunch of addition system prop entries that CyanogenMod added to the telephony framework to achieve better compatibility with older RILs and for the most part, I can say that they work pretty well. The one major improvement I have noticed over KitKat ROMs I have used in the past, is that handoffs seem to be much more stable. In KitKat whenever there was a 3G-4G handoff, there would be a HUGE spike in CPU usage, particularly the rild process (I tend to keep the cpu usage overlay on at all times when I am testing things) and it would last for a good bit of time before tapering off. This would cause music apps to stutter, and overall performance would drop significantly. I can't vouch for the other Lollipop ROMs, as I am using exclusively the ROM I am currently developing (CM12).
[Samsung Galaxy Nexus] MWisBest:
The MCC/MNC fetching is something that I will be addressing soon; this is partly because I'm making a serious push to, at the very least, get toro and toroplus builds unified. I've been slowly making progress towards this since Lollipop's release.

EDIT: By the way, I think I figured out the MMS sending issue.
[Samsung Galaxy Nexus] Nephilim:
Any luck on ambient display? Only asking about progress, no rush.
[Samsung Galaxy Nexus] Rushead:
Hey!?
[Samsung Galaxy Nexus] MWisBest:
Not yet :/
[Samsung Galaxy Nexus] Nephilim:
No big deal, just checking. :)
[Samsung Galaxy Nexus] The Race To Die:
Running fantastic on my Wi-Fi only nexus, thanks man! Crazy how my Galaxy Nexus has lollipop before my Moto X (2013)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dbt816:
I was trying to figure out my adb issues...no luck.. and decided to re-flash the latest FML and R9 kernel. I was watching logcat as the device booted and noticed that the screen locked on the boot animation, but the system was actually still running. It went through the whole cache build process and started all the apps...eventually the screen locked, but it was still stuck on the frozen boot animation when unlocked. Eventually it just rebooted itself and I had consecutive boot animation lockups thereafter when rebooting via adb. I had to pull the battery to get a clean boot.

One thing I noticed is that during the lockup, if you touch the screen, you get a bunch of these in the logcat output:

I/InputDispatcher( 522): Dropped event because input dispatch is disabled.

Maybe a clue to what's going on with the boot animation lockup?
[Samsung Galaxy Nexus] jguerdat:
I had thought the boot process was still going although I wasn't connected to anything to check progress (charge LED coming on after the lockup was my indication). Good to know you had better confirmation.