yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] christianpeso:
A few people have had that issue including myself and Bsmitty himself. With you saying that you were charging offline, might give some insight on why this is happening. If I recall correctly., I was plugged in when I restarted and got that password screen. So far from what I can tell, the most common factors when getting that screen is running BSMittys kernel. I had my device on F2FS but others were on ext4. If we can get others to chime in whether they had their device plugged in when they restarted it and got that message that will help narrow down this problem.

For me I reformatted my device and used ADB sideload to reinstall a ROM. Lost data that was there, but nothing was on it in the 1st place.
[Samsung Galaxy Nexus] bsmitty83:
I'm still at a loss for why this seems to randomly happen on f2fs and my kernel , I experienced it once and have been back on f2fs for at least a week on the latest FML with no issues . I haven't touched anything filesystem related in a long time . again , I agree the issue seems to be my kernel and f2fs , but I have no idea why . maybe its something to do with going from 5.0 to 5.1 , cause after I wiped my phone completely , including sdcard , its been fine . The only commit I could see even remotely having a chance of being responsible would be the offmode charging workaround , but I still don't see it .

I apologize for the inconvenience of a wiped device , its been bothering me immensely that this has been happening to people besides myself .

So if you want to be safe , use ext4 on 5.1 for now , f2fs should be fine on 5.0 , hopefully I can figure this out soon and correct it .
[Samsung Galaxy Nexus] Christopher8989:
What about with R11 or a few revision back?
[Samsung Galaxy Nexus] bsmitty83:
AFAIK they are fine .

Here is how R12/f2fs/FML 5.1 is running for me anyways , still no encryption issues .
[Samsung Galaxy Nexus] welcomebob:
[GAPPS][CLOSED][5.x] PA-GOOGLE APPS (All ROM's) [CLOSED]

Copied From PA-Google Apps Thread :( :( :( :( :(

"Thread Closing Announcement

After spending some time away from XDA, I have decided to take an extended break from providing and maintaining PA GApps. While I am leaving the door open to a possible return, I will be closing down my threads here on XDA at this time. And, although I won't be closing my XDA account, I probably won't be responding to PM's either.

While I had considered a move to Google+, it became apparent that even though I would have more control over things on G+, more work would also be requried to maintain things to the standard I had previously set here on XDA. Clearly, this is not a valid option for me at this time.

I'd like to thank the regular participants of my threads here on XDA. It was your participation and support that kept me motivated the past two years I've provided this free service and it's my interaction with you folks I'll miss most. Best of luck to y'all and perhaps our paths will cross again.

[ RETIRED PA GAPPS PROVIDER ]"

:( :( :( :( :(
[Samsung Galaxy Nexus] erk1725:
+1 on being plugged in when I had this experience

Been running great on ext4 for probably close to two weeks now

Thanks
[Samsung Galaxy Nexus] Christopher8989:
Oh my those numbers... I'll try again thanks
[Samsung Galaxy Nexus] traco1:
slow pull down

Still some issues .. Pull down from top of screen hard to get all the way down. Flash light tile disappears when you tap it.

Wish you could get the app drawer to show the background wall paper. (minor) Haven't tried all items yet. It's nice so far The other item that the last 2 Roms have also done is just as the screen is shut off the graphics go to grey scale.

Keep up the good work.
[Samsung Galaxy Nexus] Christopher8989:
I got it that way too but then unpluged and pull the battery and reboot but got the password screen too.
[Samsung Galaxy Nexus] jley22:
I know this may be old, but I wanted to let you know that you are the most amazing person alive. Thanks.
[Samsung Galaxy Nexus] DBISGOD:
Is there a newer build than 3.11?
[Samsung Galaxy Nexus] MWisBest:
What if I may have just fixed it now so that workaround won't be needed anymore? :)
[Samsung Galaxy Nexus] bryantjopplin:
Your the most amazing?
[Samsung Galaxy Nexus] cujo6801:
You should see him with his shirt off.... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Rushead:
You don't have a pic?
[Samsung Galaxy Nexus] cujo6801:
:confused::eek::thumbup:;):p:D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] MWisBest:
:D

wat. I'm a scrawny little... you know what. 5'8" 140lbs. Nobody wants to see that.

I do have a nice head of hair though!
[Samsung Galaxy Nexus] Rushead:
STOP.... You're making me hot!
[Samsung Galaxy Nexus] bryantjopplin:
Lol 6,4 200 with not such a good head of hair lol
[Samsung Galaxy Nexus] cujo6801:
Don't you guys know how the internet works

let me show you I'm 6 foot 2

200 pounds

flowing blonde hair

ripped abs and buns of steel

:D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bryantjopplin:
I believe you ha ha. Nerds don't look like that lol
[Samsung Galaxy Nexus] Rushead:
He meant flowing blonde pubic hair.
[Samsung Galaxy Nexus] ramosroger:
Does that toro build work on maguro? I scrolled back like 20 post and it seems this is for toro but I heard maguro users using this ROM and the newest build post said there would be a maguro build
[Samsung Galaxy Nexus] zzpianoman:
You could force flash it, but you wouldn't have any phone capabilities - and some other things might be broken too.
[Samsung Galaxy Nexus] cujo6801:
http://xdaforums.com/showthread.php?p=52945415

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bryantjopplin:
Try the other thread lol
[Samsung Galaxy Nexus] arigr:
an 8 day tease?? yer killin me :P
[Samsung Galaxy Nexus] Christopher8989:
Nothing to flash lately so I flashed KK and JB :p

Went back to sweet L ha!
[Samsung Galaxy Nexus] past_pluto:
Flashed just the rom and gapps and turned off ambient display but still can't get the phone to deep sleep. Weird.
[Samsung Galaxy Nexus] otter34:
Can someone please post a link to banks 4.4.2 gapps? I had it bookmarked and now tapatalk updated and erased my bookmarks and I'll be dammed if I can find it searching the site or googling it. Thanks very much
[Samsung Galaxy Nexus] Christopher8989:
http://xdaforums.com/showthread.php?t=2348100

http://xdaforums.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842

http://xdaforums.com/showthread.php?t=2779598
[Samsung Galaxy Nexus] MWisBest:
Sorry about the delay (as always)!

One last surprise for the next build, but you have to guess it... here's a hint: "FML-AOSP-5.1-20150405-tuna.zip"
[Samsung Galaxy Nexus] opssemnik:
5.1, AOSP rather than omni and unified builds? did i got it right ? :p
[Samsung Galaxy Nexus] MWisBest:
Just the unified part. There's a 5.1 AOSP build here already, and I haven't done OmniROM since 4.4.
[Samsung Galaxy Nexus] Nephilim:
Finally updated to the 5.1 build along with Smitty's latest kernel. All the lag and issues I was having are gone. This build is soooo smooth. Also, I dirty flashed over the 5.0.2 build only wiping dalvik/cache with no problems at all. Great work MW.
[Samsung Galaxy Nexus] welcomebob:
Links to Official PA Gapps and Unofficial PA Gapps

For those of you that use and are interested In PA GAPPS, here is a Forum I found that has links to all of the last version of Official PA Gapps, also in link is, so far two different people making Unofficial PA Gapps to try to continue [MENTION=2777334]TKruzze[/MENTION] Work (PA Gapps by [MENTION=4344925]hellowasif[/MENTION], and PA Gapps by [MENTION=680750]sir*mez[/MENTION]). I have not tried either one of these Gapps packages, so I do not know of there condition, but that they are using TKruzze scripts to try and get things working. Reading through the forum it looks like there still learning the script and that there seems to be some issues for some people, but that a lot of people are having good luck with them so far. But hopefully something to keep our eye on if TKruzze doesn't end up coming back. But again for those who don't have them, this site has all of the last Official PA packages that TKruzze made (Pico | Nano | Micro | Mini | Full | Stock) of each of the three listed below.

http://xdaforums.com/showpost.php?p=59691711&postcount=5

5.1.x Lollipop Packages: Package date: 15th March, 2015

5.0.x Lollipop Packages: Package date: 15th March, 2015

4.4.4 Kitkat Packages: Package date: 8th March, 2015
[Samsung Galaxy Nexus] arigr:
any major changes in 0405v2tuna vs 0311v2toro ?
[Samsung Galaxy Nexus] KShion619:
1. A MMS Fix for Verizon was added, no workaround needed anymore https://github.com/MWisBest/android...mmit/073dc2726c15b7d7b446302e264c625df4792dd4

2. Unification of Maguro/Toro/Toroplus builds https://github.com/MWisBest/android...mmit/ce50f19f241324fa4bcdabc343ff3f23aae13ba4.

3. 5.1.0_r3 Build of Android, the build number is LMY47I for those keeping track at home https://github.com/MWisBest/android_manifest/commit/3399eea624de860b826c6ef28d82c326de026789

4. # Superuser settings menu re-added https://github.com/MWisBest/android_manifest/commit/d87bc83c24d9a89583a8382cb54a8e37faf37328

5. Audio Resampler Changes -put lots of commit links here-

6. If you want to watch the project continue liveish look at the commits on each repo at https://github.com/MWisBest
[Samsung Galaxy Nexus] cowsquad:
Where did you get 5.1 lol?
[Samsung Galaxy Nexus] KShion619:
I'm sure he's talking about the one in the downloads section (Not in the OP because potentially unstable) wait til he brings the next build to OP, it probably wont be long
[Samsung Galaxy Nexus] cowsquad:
Thank you. I am on KitKat because I think lollipop is not for the gnex. My Gnex gets laggy
[Samsung Galaxy Nexus] KShion619:
Give a bit more time, KitKat had that issue on mine, might be the odd amount of RAM avalible making it not being a LowMem device or a normal mem device (neither 512MB (LowMem) or 1GB+ (NormalMem))or its just devices aging oddly, have you tried using F2FS on data and cache and not using facebook on it? runs amazing when i try that
[Samsung Galaxy Nexus] cowsquad:
I don't use Facebook or Pandora. I just use whatsapp and sometimes spotify
[Samsung Galaxy Nexus] KShion619:
Did you try Nephilims (old but still relevant) settings? they translate pretty well to 5.1 considering a few of the Memory leaks has been cleaned up in the newest builds of Android, memory allocation is not really a huge issue anymore, try out the new build when it comes its looking nice ;)
[Samsung Galaxy Nexus] Root Wizard:
Will it flash Directly From 4.0?

Can i flash the 4.4.4 stable onto a nexus with 4.0?
[Samsung Galaxy Nexus] sonic147862:
So what exactly will the ART compiler help with? I was trying to read up on it but it was very confusing, Thanks!

Edit: Also i have been running logcat but i haven't got a freeze when its been recording the logs so i will keep trying to get that to freeze and help fix the issue.
[Samsung Galaxy Nexus] Sik-1:
ART is like installing a game to your xbox360, makes things load faster and leaving a smaller foot print, gaining more memory and smoother operation, hope that helps
[Samsung Galaxy Nexus] sonic147862:
CatLog

Hey not sure if this will help at all but I got a freeze while running CatLog and I have the files so im just going to leave them here :P

Edit: also the error is at the very end of the file I had CatLog running for about 2 hours and had over 1000 lines of code
[Samsung Galaxy Nexus] MWisBest:
THANK YOU! I've gotten some good info from that, but could you also let me know what you were doing when it froze? It does look like it's related to the GPU drivers.
[Samsung Galaxy Nexus] sonic147862:
If I remember right I was in the Facebook app then closed it then dropped down my notification bar and clicked the quick-settings icon, then i clicked on wifi to change the network i was on and it froze.
[Samsung Galaxy Nexus] Rushead:
From my experience with various KK roms, my freezes / reboots seem to all be related to something similar to yours: closing one app & quickly trying to do something else.

Sent from a frequent flasher.
[Samsung Galaxy Nexus] sonic147862:
Hey I was running CatLog again and got another freeze (I unlocked my phone then went to the quick-settings and clicked the battery stats and it locked up) the log looks a bit different than last time but I have no clue how to read them, I just hope this helps!
[Samsung Galaxy Nexus] MWisBest:
Thank you guys, this info was extremely helpful and I've posted it up here for other developers to take a look at it as well: http://xdaforums.com/showthread.php?t=2530132
[Samsung Galaxy Nexus] 7175:
I think you've convinced me to get on the 4.4 train just so I can load up an adb terminal and crash the **** out of this *****, hopefully contribute something. It's really cool to see a dedicated developer and the people so far who have joined the fix-the-gpu-drivers cause. 4.4 AOSP is the way to go. :good:
[Samsung Galaxy Nexus] MWisBest:
Well, CM's repos seemed to have finally calmed down enough for me to be comfortable enough to switch back over to CM as FML's base like I had for 4.3.x. Check out the changelog, flash away, make bacon, whatevs. I'm going to get some sleep finally!
[Samsung Galaxy Nexus] 7175:
Thanks for the update, flashing after this post! Man glad I waited a day though making preparations for my no-data-wipe, 4.3-to-4.4 surgery. Also had to explain to Vanir how my Nexus isn't a slut for flashing other roms, it's just "polyamorous"... [/roflcopter-flyby]
[Samsung Galaxy Nexus] ironfisted:
If you press 3g it won't toggle back to LTE.
[Samsung Galaxy Nexus] stebomurkn420:
No reboots so far but I'm experiencing over all laggy performance... Maybe I had a bad DL.. I did a clean install.
[Samsung Galaxy Nexus] MBQ_:
A bad download would atypically result in an initial failure during flashing of the actual ROM in your recovery.

Regarding your bad performance, mind telling me a little more about your setup, and situation? :)

Like, which kernel are you using, if you're getting lag with certain apps, functions, etc.
[Samsung Galaxy Nexus] dx1881:
This ROM has been excellent thus far, with art enabled it flies! Future looks very bright!
[Samsung Galaxy Nexus] MWisBest:
I was juuuuust about to post about this. Looks like an issue with the overlay... I'm going to be out of town until later tonight so it'll be a while before I can fix it unfortunately. If not tonight it'll be tomorrow night. In the mean time, don't toggle it!! :P
[Samsung Galaxy Nexus] oman0123:
Gallery force closes with ART running.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] jonstrong:
oops -- wrong thread! sorry...
[Samsung Galaxy Nexus] rester555:
Titanium backup keeps force closing on me.... I think I read this somewhere else with CM. Can someone confirm?
[Samsung Galaxy Nexus] Nephilim:
Using my custom settings with Smitty's latest kernel on 5.1 I've had no issues with multitasking or lag, home screen redraws are completely gone as well. I have a few minor changes my latest batch of settings that differ from the latest posted on my thread but nothing drastic. I'll update them as soon as I'm at my home PC.
[Samsung Galaxy Nexus] KShion619:
Nope, grab and flash all the radios from 4.2.2 and bootloader update from Maguro 4.3 and the 2.8 TWRP mentioned a few pages back in fastboot, if you need help i can explain further in a PM/Q&A thread Which is here!
[Samsung Galaxy Nexus] zzpianoman:
There is a build.prop key that you can use to force the device as a low RAM device, but it makes everything super laggy and performance seems to actually be a lot worse.
[Samsung Galaxy Nexus] KShion619:
In KitKat, it works well for multitasking, I used this primarily but it kinda limits you in terms of features of the camera and some apps

On Lollipop 5.0.x (Havent Tested 5.1) the UI looks a bit odd when on the lock screen and on the notification pulldown
[Samsung Galaxy Nexus] zzpianoman:
As far as I can tell, all it does is turn off graphics acceleration and give lower minfree values - but having minfree values too low doesn't leave much room for cache so performance is going to suffer.

EDIT: You can check out the source code here.
[Samsung Galaxy Nexus] KShion619:
Might be the graphics acceleration that does that wierd stuff I'm getting my new battery in a week or so (dont use a 2.9A charger on a GNex, it destroys batteries to death) and ill run up that to try it out on 5.1 and 5.0 to give screenshots if no one else does
[Samsung Galaxy Nexus] zzpianoman:
Wow, I wouldn't think that the Galaxy Nexus would allow itself to draw that much current? Or perhaps the protection is in the charger itself (or it SHOULD be). I believe that the charger is supposed to look for a special proprietary voltage across the D+ and D- pins of the USB connector, and only applies the full 2+ AMPS if it sees that voltage, to protect devices that aren't equipped to handle it, from overheating. I believe this is how Apple does it, but you probably run a great risk if you use no name brand chargers.

Chargers are ONE area I never skimp on, simply because so much can go catastrophically wrong with a switchmode power supply. I usually spend more for my chargers, and less for cables and other stuff (like the phone itself..haha how cheap is Galaxy Nexus now? 30 bucks?)
[Samsung Galaxy Nexus] KShion619:
Well both the official Nexus Charger from Google Play (took 6 months about) and Limefuel's Dual Slot Charger (about 3) did it, on two different motherboards, at least it seems that the GNex is the only thing effected by this, as i use it on my G3, Droid Incredible, and Nexus 7 (2012) constantly with their original batteries
[Samsung Galaxy Nexus] zzpianoman:
Interesting...I have always found the charging circuitry in the Galaxy Nexus to be somewhat questionable and considering the main achilles heel of this device appears to be the battery life, it wouldn't surprise me. Perhaps some revisiting of the max17040 fuel gauge driver code is in order? I know there are a few different versions of it out there....maybe it can be tweaked to further optimize the charging circuitry?
[Samsung Galaxy Nexus] KShion619:
That and maybe smartreflex, just to see how agressive we can make it without hindering anything, would lower power draw a bit :P (almost literally, but better than it being primarily a stability tool)
[Samsung Galaxy Nexus] zzpianoman:
I actually did try to drain the battery beyond the limits acceptable to the system, by disabling the auto-shutdown procedure in the kernel. I was able to get it down to around 3.4 volts before the system would no longer run. It really only translated to an additional hour or so of usage time - but the damage that repeated deep cycling would do to the battery is probably not worth the extra few minutes.
[Samsung Galaxy Nexus] vladimirhtg:
That's super cool. I cycle through multiple batteries (like...4) and would actually be interested in trying that out.
[Samsung Galaxy Nexus] zzpianoman:
Oh, it's a rush, that's for sure!

But it is really terrible for the battery. I don't have exact figures, but I believe it significantly diminishes its long-term capacity, and could also have untold effects on the internal circuitry of the phone itself. I have only done it once, and will probably never do it again. I do, however, want to see if there is a more efficient way of cycling the battery, in particular, to adapt to the subtle differences one would find across different batteries.

Also, if you are using an extended battery, that extra hour or so I was able to squeeze out of the stock battery might translate to even more time!

It should also be noted that since the discharge curve of a lithium ion battery is logarithmic, after the voltage drops below a certain threshold, the discharge rate increases significantly. There is also the danger that discharging the battery too much would make it vulnerable to falling below the absolute critical threshold at which point it would be rendered completely unusable.
[Samsung Galaxy Nexus] vladimirhtg:
Hard to get exact figures for batteries, even for OE equipment--I worked with a team doing Li Ion batteries for a weather balloon camera (read: high altitude & very cold). Batteries are way more finnicky that I ever would've believed previously.

Looks like I need to jump into kernel development...:fingers-crossed:
[Samsung Galaxy Nexus] zzpianoman:
Definitely. Take a look at the max17040 fuel gauge driver code. It appears as if the SOC (state of charge, i.e. percent) is actually read directly from the chip itself and NOT calculated in the driver code as a function of voltage. This leads me to believe that all of the relevant calculations are done via a proprietary method within the max17040 IC. There is one adjustable parameter called RCOMP, but I have not managed to find any documentation on what this value is or how it is calculated. It appears to be some some sort of compensation factor that is most likely specific to each individual lithium ion battery. I'm guessing the RCOMP value for our Galaxy Nexus was calculated based on the OEM battery, which might explain why there is so much variation among all of the aftermarket batteries in terms of reported capacity and longevity.

It would be fun to revisit the fuel gauge driver, as this was actually what led me into trying my hand at kernel development.
[Samsung Galaxy Nexus] KShion619:
It may be caused by the device being incapable to reading voltage directly from the battery, but who knows? maybe this is also the reason the reported battery capacity is always 1750 on the miscellaneous (if it appears) under battery settings in 5.0+
[Samsung Galaxy Nexus] RW-1:
Looks like a sprightly discussion on Batt charging going on, how's everyone? I've been on my N6 and been away secretly enjoying myself :)

The GNex may go to my daughter and onto our family plan, so I'll be lurking, however because of the data drops I've had with it, I may just reflash a JB rom for her and go from there....
[Samsung Galaxy Nexus] KShion619:
How's the Nexus 6 doing on Verizon? hows the reception v. GNex?
[Samsung Galaxy Nexus] RW-1:
Absolutely perfect - I've only had two instances where it dropped over to 3G and back, handoffs are instantaneous, couple of times the handoff from wifi to mobile took 5 sec (by count) but all good.

Call quality just as perfect IMO. Havent activated VoiP (adv calling 1.0) yet though to try out.

It just confirms what we knew - ever since KK we just don't have a good radio driver interfacing with the OS IMO.

I know not everyone had the issues, but I pushed it for over 1.5 years with sometimes 30 sec handoffs, areas that would just drop out where another VZ phone would remain in 4G with great signal (-50 to -60Db) ...

I don't blame anyone on this, we pushed the GNex to its limit with no additional support from google or TI, who left the scene ... Dev's have always rocked this device.
[Samsung Galaxy Nexus] RW-1:
Jeez, what dirty minds! :)
[Samsung Galaxy Nexus] Christopher8989:
My mind is not dirty. It's full of wonderful stuff :D
[Samsung Galaxy Nexus] xkegsx:
Any link for the 0405tunav2?
[Samsung Galaxy Nexus] amd_h4x0r:
I have a copy, but [MENTION=3390093]MWisBest[/MENTION] locked down the original link. Not sure if he wants that build shared anymore.
[Samsung Galaxy Nexus] xkegsx:
Here's the thing. Between this build and pianomans build I haven't had usable MMS since going to Lollipop. I use google messenger. Every time MMS fail to download and until I click the recipient and manually download them I won;t even get a notification for it. I can apply the MMS fix 100 times and it still does nothing. I do a full wipe for every iteration of either ROM. And yes, auto retrieve is on. WHen I click the sender it says failed to download message click to manually retry.
[Samsung Galaxy Nexus] past_pluto:
I have same mms issue too. A reboot normally makes them all come flooding in. Luckily I don't do group messaging too much.