yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bhugh:
OK, here is a (somewhat kludgy] fix to this problem, that seems to work.

What I did was use the Tasker app to create a task that turns the camera apps off whenever the screen turns off. The Tasker recipe looks like this:

Profile: Display State Off (State/Display/Display State/Off)

Task: Kill app (I have 3 different camera apps installed, so I created tasks to "Kill app" for each of them (App/Kill App - then select the app you want killed). You can also add a little beep or vibration so that you know that the apps have been killed (Alert, then 'beep' or 'vibrate')

I'm using CameraZoom FX as the main camera app, and together with this Tasker auto-kill script, it seems to work OK, so far.

I'm not sure that this is the ultimate solution to this problem but it seems to help some.
[Samsung Galaxy Nexus] Kr4ft:
Problem with network

Ok guys! Got almost everything fixed but one thing:

I can upgrade to 5.1 and it works great... BUT and only BUT... probably because i'm in Brazil, there is no network connection, the airplane mode goes on... So, searching in this thread helped me find that the problem is with the kernel... but thats it... no more explanation whatsoever so... can someone explain to me what should i do? Like, explain why this happens and how do I fix it?

Please, my CM is beyond repairs now... I can't enter on internet anymore because it got so fat and buggy... :( :crying:
[Samsung Galaxy Nexus] harjifangki:
Hey, sorry if the question seems very newbish, but here goes nothing. So every time I flash the Gapps from MWisBest, This one to be exact, I got a status 6 error. I tried to download the full modular Gapps package from here, but it's giving me the same problem.

Is there a solution for this problem?
[Samsung Galaxy Nexus] SwimWithFire:
Duplicate Text Messages

Hello All,

I've been following this site for years and it's rare that I post as the answers are usually out there. I've seen a lot of questions around duplicate text messages and I have experienced this myself in the past (mostly on Jelly Bean) but the solution for me was a complete wipe back to factory and then going with my chosen ROM. Since I have done this I have not experienced these issues again. I have currently running the lastest 5.1 FML and my GNEX has not been this smooth in many many months! 5.0.2 was buggy/laggy as hell, but this update has been a night and day difference!
[Samsung Galaxy Nexus] bhugh:
After using LP 5.1 for about a week now, I would say it is definitely better than 5.0 but also definitely some of the lag and slowness is coming back. It's not as snappy as it was immediately after upgrade or as snappy as it feels this phone is/should be capable of.

FWIW.
[Samsung Galaxy Nexus] bhugh:
After another day with various camera problems, seems to be growing more laggy, and occasional/random loses network/cell connection problems, I'm going to try reverting to FML KitKat to see if that works better on this phone.
[Samsung Galaxy Nexus] bhugh:
After going through this, I can answer my own question from above, that you basically have to do a factory reset to downgrade from 5.x to 4.4.4 FML. So you will use all your installed apps, settings, etc. I think if you play it right you could keep your saved files etc on SDCARD, but I ended up reformatting the partitions to f2fs and a bunch of other stuff, which basically resulted in wiping all the internal storage space including SDCARD. So I was glad I had taken backups beforehand.

That also ended up wiping out the roms & gapps I had carefully uploaded for use in TWRP, so I had to use TWRP & adb sideload instead, to install the rom & gapps.

Two tips there:

The only way I could figure out to install the rom/gapps was via sideload. I couldn't figure out how to use 'adb push' as some instructions tell you.

Instead, I started, the 'sideload' option in TWRP and then used adb kill-server - adb usb - adb devices (a few times, unti lthe device actually shows up) - adb sideload my-rom.zip - then wait a while for it to install - then same process with adb sideload gapps-xxxxx-.zip - then wait a while - then reboot.

The only trick is: After getting into TWRP and starting the adb sideload option, and plugging the phone into the usb socket of the computer, etc, it still takes quite a while for the device to show up under 'adb devices', for some reason. Like maybe 5 minutes? But by waiting until adb devices actually shows the device in 'sideload' mode (not in 'recovery' mode) then it actually worked just fine.

FYI some instructions I read suggested using the 'adb push' command. This did not work for me in this situation. Instead what worked was (as outlined above):

* Phone (TWRP): Enter 'sideload mode'

* PC (command line, like cmd or similar):

- adb kill-server

- adb usb

- adb devices (a few times, until the device actually shows up)

- adb sideload my-rom.zip (then wait a while for it to install)

- adb sideload gapps-xxxxx-.zip (wait a while)

- reboot

The instructions here suggest using the gapps 'mini modular' package here: http://xdaforums.com/showthread.php?t=2397942

However twice now (in originally installing 5.0 and now in installing 4.4.4) I've found that TWRP gives an 'out of space' error with the mini modular gapps package. So instead I've just installed the 'micro modular' package--the next smaller available package--from the same page--and it seems to work just fine.
[Samsung Galaxy Nexus] bhugh:
After using the 4.4.4 FML build (from July) for a day, I can pretty well say that it is solid and ready for prime time/regular use. Whereas the 5.0 build definitely was not, and the 5.1 build (from early March 2015)--while far better than the 5.0 build--is, IMHO, more ready for experimenters/testers/people who like the cutting edge and not quite ready for solid, day-to-day use.

A few specifics:

Mic mute on phone calls - didn't work in 5.1, works fine in 4.4.4

Camera - many problems in 5.1, works fine (so far) in 4.4.4.

Lagginess - worst in 5.0, better in 5.1, but 4.4.4 is downright snappy by comparison. I'm sure that you could get better performance out of a brand-new top end phone, but with 4.4.4 the GN is a perfectly serviceable phone again. I'll report again after I've used it for about a week, but so far it is light years ahead of 5.0 and 5.1, performance-wise.

With previous versions, it took about a week before I was certain about issues/performance. So I'll report back then. But the one-day evaluation is clearly all in favor of 4.4.4 vs 5.1 for my phone.

FYI besides simply installing the 4.4.4 rom with micro GAPPS package, here are the main things I have done to optimize the phone:

Reformatted all partitions to F2FS file system (in TWRP). Note that this ERASES all internal memory including SDCARD, so make a full backup before attempting.

Switched to ACT (under settings/developer)

Turned off all animations (settings/developer)

Increased CPU maximum speed to maximum allowable (under settings/performance). Presumably this will hurt battery life a bit but improve performance a bit.

Turned auto-update off. The objective here is to keep Google apps from updating--my impression is that the latest versions of these are quite laggy on the GN. http://www.reddit.com/r/GalaxyNexus/comments/31iua3/the_galaxy_nexus_isnt_slow_the_new_google_apps/
[Samsung Galaxy Nexus] mosgjig:
Gapps install errored out

ROM: FML-AOSP-5.1-20150311-maguro.zip (196.39 MB) installed fine and works pretty good, didn't delv too much into it because...

FML-PA-GApps-Micro-5.1-20150310-UNOFFICIAL.zip (149.31 MB) could not be installed and received an errror (status 6) followed by Installation aborted using clockworkmod recovery v6.0.4.7 where CM11 was previously installed.
[Samsung Galaxy Nexus] mosgjig:
Logs

cwm/advanced/show log ->

Installing update...
W:Using fallback updater for downgrade...
installing samsung updater extensions
line 2 col 1: syntax error, unexpected $end, expecting IF or STRING or '!' or '('
1 parse errors

Reading up online, looks like a common issue caused by devs using non-linux/unix env when editing these files. Gotta cross those Ts and dot those Is my friend... i can relate ;)

Now, gotta find a way to convert the script into unix format and strip away all the wincrap out of there.
[Samsung Galaxy Nexus] bhugh:
The next thing I would try is installing the nano or pico GApps. Not sure what status 6 is, though, or whether the smaller GApps packages will help.
[Samsung Galaxy Nexus] bhugh:
Well, within a DAY the lagginess was back.

I'm not sure at all what is causing it. I know this phone is a few years old, and it will never be as snappy as the latest & greatest. But at times (like immediately after the fresh install of 5.0, and 5.1, and 4.4.4) it is just fine--reasonably responsive. It's a phone I could easily keep using for another year--because why switch from something that is working perfectly well.

But when I picked up the phone to show my SO how beautifully it was 'fixed'--it was back to its worst. Like 15 seconds to start up gmail, over 30 seconds to start maps, etc etc etc. This is multiple times longer than it takes when well behaved.

I am not certain what the cause of this is. It is using just a fraction of the total 16gb memory available now (over 10gb free). I switched all file systems to f2fs. The apps tab shows something like 1/3 of total working memory free (434mb used, 313 mb free right now--this is about typical).

So I took some more drastic measures:

Installed an app to auto-reboot the phone every morning at 4am

Installed Greenify and greenified a bunch of apps; all options enabled and basically greenified every possible thing it would let me (bought the app and also installed Xposed so all options available)

DS Battery Saver app in "balance" mode - seems to really help battery lifetime

Deleted/removed/disabled everything that seems unnecessary such as Google Now and the 'OK Google" voice recognition

Turned off location services in Google maps

Installed Xposed/Amplify which is supposed to stop some ongoing memory/wakeup calls that are unnecessary

Autorun manager & disabled some very active Google Play Services receivers

Tried 'lagfix free' and some other similar utilities to take care of the 'trim' problem, though this doesn't seem necessary (or even possible--lagfix wouldn't even run the trim utility) with F2FS

IMPORTANT: Disabled auto-update for all apps. The intention here is to keep all google apps at the 4.4.4 stage and prevent them from continuously updating to newer versions that (may?/seem to?) be a major cause of lag on the GN.

So far it seems better. We'll see if it lasts.

If anyone has any bright ideas about what is causing these interminable / intermittent lag problems with the Galaxy Nexus over multiple roms/Android versions, I would be very, very interested to know what the causes are, and what solutions might help.
[Samsung Galaxy Nexus] mosgjig:
Do you have any links to those? can't seem to find them.
[Samsung Galaxy Nexus] rom_quizzer:
Headset Control

Hi MWisBEst,

Could you please check and add the headset control functionality to the ROM.

I have noticed that no lollipop rom has the working head set control.
[Samsung Galaxy Nexus] mosgjig:
FIgured out my problem. Was using CWM which is apparently not supported anymore. Switched to TWRP by flashing CM11 and accompanying GApps and downloading TWRP from play store. Was able to flawlessly flash and overcome error 6 when installing gApps.
[Samsung Galaxy Nexus] bhugh:
Continuing quest to get a rom going that is functional in all needed ways.

1. FML 4.4.4 (from 2014/07) works ALMOST perfectly, but has a very, very long delay in establishing the cell data connection after it is turned off (ie, if wifi is on, then loses signal). Like many minutes. This is pretty much no-go. It shows "mobile data state: connecting" for an interminable amount of time. AFter 5-10-15 minutes or so it will finally connect.

2 I tried updating to the FML 4.4.4 version from 2014/10, in hopes it would solve some problems. Without the updated boot.img it booted up fine, but--as advertised--no radio. When I flashed the updated boot.img ( a couple of different ways) it gets stuck at the 'google' boot-up screen and never moves on.

I think this **might** be because I've re-formatted data & cache in to f2fs. at any rate, I couldn't get the 2014/10 FML to work at all with the radio. Otherwise it looked fine . . .

3. So I tried FML 5.1 again (nandroid backup). I was immediately struck by how incredibly laggy it is vs 4.4.4. But, the mobile data works quite perfectly.

4. Now trying CM 11 (4.4.4) and it seems to have the exact same (or similar) "mobile network state: disconnected" issue as FML 4.4.4.

Anyone have any ideas about how to fix that mobile network connection issue?

UPDATE: It looks like all I had to do to fix the mobile network connection issue, was go into the APN settings (under settings/mobile networks/access point names) and then select the right one. There were several APNs listed and the wrong one was selected. I'm using Straight Talk so something like this is needed: http://www.droid-life.com/2014/03/04/straight-talk-apn-settings/

UPDATE: Actually the APN info listed in that link is the exact APN that was flakey/super-slow to connect. So if you happen to be on Straight Talk, don't use the info in that link! However, in general the issue was getting the correct APN info entered and selected, so depending on your provider you'll probably have to look that up and enter and/or just experiment with the various APN settings that you will (probably?) find in your settings under APN, and you may find one that works.

This worked on the CM11 rom and I'm assuming it will work on the FML 4.4.4 ROM as well. UPDATE: It did indeed work on FML 4.4.4 from 07/2014, problem solved.

I didn't realize APN was likely to get messed up when moving from on ROM to another.

This was actually easier to troubleshoot under CM11 because mobile data just stopped working entirely. Under FM 4.4.4 it was intermittently working. I don't know that this is a feature/bug of the ROMs per se--just a quirky side-effect of the particular strange thing each was doing to the APNs. One ROM selected a completely non-working APN and the other selected a partly-working APN. Regardless, 'partly working, sometimes' makes it hard to debug.
[Samsung Galaxy Nexus] alirexaa:
Configurable wake on charge

Does the Lolipop version for maguro have the "no wake on charge" option? My Gnex has the USB port bug and I need this feature.
[Samsung Galaxy Nexus] ComradeF:
Ok Google

I searched this thread and the official FML thread for "Ok Google" and didn't find anything, so...

With a fresh flash of FML-AOSP-5.1-20150311v2-toro, saying "Ok Google" doesn't work. Has anyone else experienced this?
[Samsung Galaxy Nexus] mike_kostop:
noob question but will this build u mention will be compatible for the maguro devices or not???
[Samsung Galaxy Nexus] asheenlevrai:
The GNex (Tuna) exists in several variants: GSM (Maguro) and CDMA (Toro and ToroPlus). My best guess is that a "Tuna" build would work for all variants... Otherwise it wouldn't make much sense obviously.

Looking forward to it :)

Best,

-a-
[Samsung Galaxy Nexus] horeabeni:
GNex maguro - FML-AOSP-5.1-20150405v2-tuna.zip

Tested FML-AOSP-5.1-20150405v2-tuna.zip on my GNex (maguro) and it flashed and booted without any issue.

Note: all ext4
[Samsung Galaxy Nexus] HSC_Jake:
Just flashed FML-AOSP-5.1-20150311v2-toro today with FML-PA-GApps-Micro-5.1-20150310-UNOFFICIAL (Both from here, followed flashing instructions start to finish), everything (Data, camera, video, etc.) works great, however MMS is not working for some reason. Tried flashing the previous Verizon fix from the development thread to no avail, but have not since had time to try a reflash or anything.

I'd hate to have to go back down to 4.4 since 5.1 is really nice from what I've seen so far, but I may have to unless there is a known fix since I use MMS quite a lot on a daily basis.
[Samsung Galaxy Nexus] FaBjE:
Did you get any reply on your bugreport? http://xdaforums.com/showthread.php?p=60010121#post60010121

Or do we all need to bump that thread ;)
[Samsung Galaxy Nexus] mlazowik:
FML-AOSP-5.1-20150405v2 testing

Hi,

I've been using that build as my daily driver since you published it. Everything works great (if RAM usage does not kill the whole UI… but that happened to me on every rom).

There was only one issue: one day the call/notification audio just stopped working. Rebooting helped. In case that happened again what logs would be of interest to you?

Thanks for the great work ;) I could try to help if if find some time during summer.
[Samsung Galaxy Nexus] Doskos:
Is this threat alive??
[Samsung Galaxy Nexus] Neotil:
FML 5.0.2

Hi, keep up the good work!

Everything is as smooth on Lollipop as on Jelly Bean and Kitkat!

My only problem is, which will probably make me return to FML Kitkat, that a lot of apps 'unfortunately stopped', Google Play services stops most often. Also when i try to log into my Google account, it says 'Checking info...' and then it stops. This prevents me from accessing my music, email, and contacts. Sucks!

I hope I'm just too stupid and someone knows how to fix this, or if it's my phone.

Thanks!!

I forgot to mention that when I charge the phone when it is powered off, the charging icon appears, but doesn't go away until you disconnect the charging cable and take out the battery.

EDIT: I just did a factory reset and flashed other Gapps than the ones that are suggested by [MENTION=3390093]MWisBest[/MENTION], because they don't work, and now Lollipop works flawlessly!

Lollipop is so fluid even with a mild overclock of 300MHz, which leaves my phone relatively cool at 1.5GHz. It might even be a bit faster than the stable FML 4.4.4 KitKat build!

Awesome, keep it up [MENTION=3390093]MWisBest[/MENTION]!!!
[Samsung Galaxy Nexus] Bruno3589:
Good morning [MENTION=3390093]MWisBest[/MENTION],

first of all thanks for bringing Lollipop to the GNex.

To test your latest changes, I decided to make my first-ever attempt at building a ROM myself.

So this week I synced your GitHub repo source and managed somehow to build an almost-fully working ROM.

I don't know if you can make use of it, but here's what happened.

Please bear in mind I'm not very experienced with Android ROMs (and also GitHub) but I followed your thread for a while and I did learn some things.

First build did not complete, due to "libdomx" not complying to "strict aliasing rules".

Looking at your recent commits, I found out a workaround by adding this:

FML_NO_STRICT_ALIASING_MODULES += \
libdomx

at the end of core/fml_config.mk

After that, the build did complete, but I looked at the zip otapackage and there were some apks missing from priv-app (AFAIK at least one is critical):

MusicFX

OneTimeInitalizer

SystemUI

WallpaperCropper

So I searched online and found a way to build them standalone, then I merged them into the package.

Then I clean flashed it (wiped everything), along with latest TK GApps, and I was almost sure it couldn't work. Surprisingly enough it boots and works!

After initial setup, I can say almost everything works, but there are some issues:

- After a while, Geolocation makes Google Play Services crash every time it tries to get current location. Clearing Play Services data and rebooting solves the problem temporary, until it starts to crash again

- In Settings -> Backup and restore -> Backup Account, I can't select anything, there is a greyed-out text "Backing up to debug-only private cache". I know there is a solution for this, but I thought it was useful to report anyway.

Some details about the build process:

- All the work was done in a VirtualBox VM running Debian 8.1 64 bit

- PC's hardware specs are: Intel Core i7 950, 6GB RAM, 120GB SSD + 1 TB HDD, GeForce GTX 570 GPU. Build took ~4hrs 30min (with ccache on)

- Target is fml_tuna-userdebug

- The build command was "make -j8 otapackage"

So to sum it up, ROM works, is pretty fast, and I'm quite satisfied as this is my first build ever.

But I don't understand why it did not build those missing APKs, and why Google Play Services crashes with Geolocation (could be a GApps issue, but I doubt it).
[Samsung Galaxy Nexus] Bruno3589:
Hello, just a quick update on how the test's going.

The Play Services crash related to geolocation seems to happen only in "High accuracy" and "Battery saving" modes (in other terms, when WiFi-based location is on). Setting "Device only" mode works without issues and doesn't crash Play Services.

Meanwhile I also solved the backup issue by following a guide.

Will try to get a logcat when Play Services crashes to futher investigate the issue.
[Samsung Galaxy Nexus] uji_sine:
Waiting new build.

I hope to see new build.
[Samsung Galaxy Nexus] enotbay:
USB Connectivity Issues

I'm using your Lollipop ROM on my unlocked Verizon Galaxy Nexus and I have been pleased with how it has been operating. :good:

My only complaint is that my computer will no longer recognize my device. I am running Windows 10 on a Dell Inspiron 5000 Series 15634. I have tried everything short of resetting my computer to try to get my phone to connect.

Is there any device driver I should use or any fix that would work?

Any and all help would be greatly appreciated.
[Samsung Galaxy Nexus] girkev:
Connect your device, go in Recovery mode and your Windows machine recognizes it. Hope it helps.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] enotbay:
Thanks, I found out the real problem was the usb cable.
[Samsung Galaxy Nexus] logicalien:
Google Play services not working

Is anyone else having problems with Google Play Services? After I flash the ROM and gapps the ROM works beautifully until I reboot or after 24 hours or so the message starts popping up saying Google play services has stopped. It doesn't stop and just comee every 5 seconds. Clearing the cache, data, and restoring to factory version only solves the problem for a few hours. I've tried flashing different gapps packages but to no avail. Any help would be appreciated.
[Samsung Galaxy Nexus] jjrojo:
V3U00M is my emmc chip working with a modified v1 version.
[Samsung Galaxy Nexus] Schlachtbank:
I'm posting the log here because I'm not authorized to post in the main thread

https://drive.google.com/open?id=0BwDQXhnD7h3LMndycDRSMHpTZGM&authuser=0
[Samsung Galaxy Nexus] okanfb:
RESPECT guys ! good job i wanna try it does it good for daily driver ?
[Samsung Galaxy Nexus] uuxy:
which you need

please remove .txt

I use origal ver
[Samsung Galaxy Nexus] okanfb:
Signal sim card not working on maguro i cant call or write sms
[Samsung Galaxy Nexus] Ken Chan:
Has been running for ~1 day now. A good early-bird ROM I must say.
[Samsung Galaxy Nexus] chuckycrx:
Has anyone tried the V3?

http://xdaforums.com/devdb/project/dl/?id=9486
[Samsung Galaxy Nexus] quertz:
I had no problems with flashing the lollipop ROM, but my systemUI seems to crash --> I don't have buttons, notifications nor a lock screen. Any ideas?
[Samsung Galaxy Nexus] ch4mi:
Thanks for bring Lollipop to our GNex! and so fast! You really are doing a amazing work :)

Waiting for a stable version!
[Samsung Galaxy Nexus] okanfb:
Does the RIL solved for maguro with the new build?
[Samsung Galaxy Nexus] alexsander.xs:
Great job

Great job, flashed well, but still not working camera and cellphone. Using maguro with bugged emmc.
[Samsung Galaxy Nexus] okanfb:
Plz fix the RIL problem i want to use this rom as my daily driver :)
[Samsung Galaxy Nexus] sungamagnus:
Android 5.0 FML works on VYL00M eMMC maguro

Thanks MWisBest for the 1109 update.

It's booting up on my magnuro.

Just tested for a short time, it's very snappy.
[Samsung Galaxy Nexus] sohailazam:
Is the network working ? And what about WiFi and camera ?
[Samsung Galaxy Nexus] alexsander.xs:
Nope, mno camera no cellphone, the developers told us to wait :)
[Samsung Galaxy Nexus] sudeepbaral:
Camera on Lollipop build

I've tried Camera Zoom Fx and many other camera apps but all of them didn't work. Can you name some other camera app that have been tested to work on Latest Lollipop build?