yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] baaabovka:
Hello guys.

I am thinking about upgrading my old buddy to the latest version of this rom. Currently I am running on the latest milestone of AOKP and start thinking that it's time for a change.

@diogofd8: What do you mean by "few apps" ? Just wondering whether the rom will work with my 20-30 apps correctly or not.

Anyway, is the rom stable for daily use?

Thank you.
[Samsung Galaxy Nexus] ed10vi:
I think this too, with more charge or an external battery I can do both things perfectly

My phone is 3 years old, and it says the battery is good. I've never measured it's capacity, but I should
[Samsung Galaxy Nexus] hgmichna:
After three years of daily or nightly charging and discharging the battery is bound to be very weak. I guess you might as well discard it and buy a new one.

Beware of fake Chinese batteries. Practically all "Oringinal Samsung" batteries offered on Amazon are fraudulent poor-quality fakes. Better buy from Anker or some other company that dares to put its own name on the battery. Or buy directly from Samsung, but those are really expensive.

We are drifting off-topic.
[Samsung Galaxy Nexus] nikodr:
My battery is three years old but with the phone overclocked and nephelim settings applied i can easily get 2 hours and 15 minutes of on screen time. And with not much use and data off i can get 48 to 72 hours of standby time.
[Samsung Galaxy Nexus] djkk16:
which overclocked kernel ?
[Samsung Galaxy Nexus] ed10vi:
Thank you! I'll take a look.

Today I was recording with Strava and when I took a look to the phone Strava wasn't recording, and it said there wasn't any SIM, so I rebooted. In the screenshot seems like it was off for some time (I forgot to see the on time before reboot)
[Samsung Galaxy Nexus] diogofd8:
I have 80 apps (including system and gapps) and it works nicely. Daily driver for sure.
[Samsung Galaxy Nexus] Noeljunior:
Does anyone suspect what's causing the incoming call lag?
[Samsung Galaxy Nexus] KarlusHTC:
It's memory or lack of memory related, i've uninstalled Facebook app, and since then it's much better.
[Samsung Galaxy Nexus] Noeljunior:
I have no app installed. Actually, I always remove a lot of CM's apps and I still have to wait 10-20 seconds...
[Samsung Galaxy Nexus] nikodr:
Btsmitty83 full auto kernel
[Samsung Galaxy Nexus] bamtan2:
IMO buy this ebay battery, it makes a big difference for me: http://xdaforums.com/showpost.php?p=61555946&postcount=141

This ROM is very stable! But the overall performance is likely not as good as your AOKP. For daily use, I recommend you stay with what works for you. Don't fix what isn't broken! ;)
[Samsung Galaxy Nexus] playitlouder:
Has anybody had luck with GPS?

Takes ages to fix, if at all.
[Samsung Galaxy Nexus] :
No problems, fast and reliable. Try the "GPS status" app.
[Samsung Galaxy Nexus] n76:
Two things could help.

First an app to force a reload of the agps data (basically a network download of the satellite position information so the phone does not have to listen to the GPS satellites for up to 12 minutes to get their location data). I use satstat (available on F-Droid) for that but there are others.

Second, if you are not using gapps or a substitute then network based location is not available. I have found that having a reasonable guess on your current location from a network based location (basically what WiFi APs or cell towers your phone detects) significantly speeds up the acquisition of the GPS signal on my old Maguro phone. If you don't want to load gapps, the microG project has a plug-in based "unified NLP" you can install (available on F-Droid) along with a number of backends (using Moxilla server based backend, using Apple server based backend or using on the phone database based backends). I use the on-the-phone based ones as I usually have cellular data turned off.

For what it is worth, I've noticed that my spouse's 2015 model Android phone has support for the Russian Glonass satellite navigation system in addition to the U.S. GPS system and it seems to acquire satellite based location much faster even with data turned off and no on-phone cell tower or WiFi database than my several year old GPS only phone.
[Samsung Galaxy Nexus] hgmichna:
A-GPS

This is not necessary. The phone gets the A-GPS data automatically at least once every three days. They are good for three days.

If you want to know, the app GPS Status shows you the age of your current A-GPS data ("AGPS age" on the left side) while it is acquiring a fix. Once it has the fix, the display changes to "Error" and shows the likely horizontal error, I think for the 95% confidence level (p < 0.05).

The GPS chip in the Galaxy Nexus has never been very good, unfortunately. It sometimes fails to function properly. In such a case a complete reboot helps.
[Samsung Galaxy Nexus] playitlouder:
I tried navigating with an offline Navigaion App while on holiday.

Without A-GPS Data it did not like it too much. Was pretty jumpy and took ages to fix.

I used GPSStatus in the past ;) But I did not think it was really necessary any more...
[Samsung Galaxy Nexus] silentz0r_:
I never flashed the LOWRAM ROM but went instead straight for the latest (31/08) ROM. I can finally see what everyone else was talking about, yesterday I missed my first call because the phone would just not cooperate (screen wouldn't come on, if I pressed the power button it just didn't show me the small circle to drag to the side and answer).

Overall I noticed way less redraws, but still the phone gets super hot on the smallest tasks (launching a simple puzzle game, browsing reddit).
[Samsung Galaxy Nexus] uji_sine:
Gps.

I had same problem before now, please try to change gapps. May be help.
[Samsung Galaxy Nexus] NerdySpam:
Also, if you use Greenfy sometimes it blocks GPS apps from searching satellites
[Samsung Galaxy Nexus] Phhoenyxx:
First of all, I would like to thank everyone who has worked on this ROM and provided feedback to make it better. One of the reasons I bought a GNEX 3 years ago was for its ability to use custom ROMs, and I finally installed my first one (this one) last week. It's really amazing. My phone is faster than ever. I'm not sure if it's the ROM or the fact that it needed a good wipe, but regardless, I'm loving it. I'm even going to install it on my wife's phone later today.

I haven't encountered any major issues so far. There was the no mobile data issue that I resolved by deleting all the Access Point Names and recreating the only one I needed. There's also the Google Camera bug where it crashes when trying to access the Settings. But both of these are well documented and non-issues really.

However, I did notice something odd last night. After taking a picture and reviewing it in the Gallery, I decided to edit it. I chose the default Photo Editor and started tweaking my picture. When I got to the Sharpness part, I noticed that it doesn't do anything. When I use the slider anywhere from 0 to 100, it does not apply any sharpening. Sharpening works fine in Snapseed and Instagram, but not in the stock Photo Editor. I haven't seen anyone mention this anywhere, but maybe I'm wrong.

Anyway, keep up the good work, and thanks again for a great ROM!
[Samsung Galaxy Nexus] hejaaa:
Transparent application in the multitask list (Bug)

Why? System or themes bug?

I have Galaxy Nexus with 12.1 cyanogen mod.
[Samsung Galaxy Nexus] Noeljunior:
Check if you disabled the Force high-end graphics under Developer options or if you enabled and then disabled the developer options.
[Samsung Galaxy Nexus] hejaaa:
I have not activate this features and after change various setting not have any change.
[Samsung Galaxy Nexus] Noeljunior:
Is the Force high-end graphics enabled? Anyway, I notice that some times some previews get transparent. Are all of yours transparent or just some sometimes?
[Samsung Galaxy Nexus] hejaaa:
Force 4x MSAA is disabled (force high-end graphics not found under developer menu)

Everything and always is transparent under mulitask list.
[Samsung Galaxy Nexus] 0s1ride:
This only happens with the 20150831 build (with lowram), rolled back to the 20150728 one and the issue disappeared.
[Samsung Galaxy Nexus] ed10vi:
Today it fast rebooted ramdomly and the SIM disappeared, but it still receives calls. After a manual normal reboot, the SIM came back.

I tried a manual fast reboot and the SIM disappeared again
[Samsung Galaxy Nexus] musical_chairs:
[MENTION=4608636]bsmitty83[/MENTION] has been saying that this is caused by an SELinux denial. If anybody who can reproduce this sim card issue wants to help fix it, here's how:

Let's see the SELinux audit log from a 'no sim card' situation, it should be a fairly simple fix.
[Samsung Galaxy Nexus] garrymar:
I've reproduced the situation using soft reboot, but the audit.log is clean:

root@maguro:/ # cat /data/misc/audit/audit.log
type=2000 msg=audit(0.882:1): initialized
type=1403 msg=audit(1442838279.726:2): policy loaded auid=4294967295 ses=4294967295
type=1404 msg=audit(1442838279.742:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
[Samsung Galaxy Nexus] Ziyan:
New build up:

- Switched to BFQ-v7r8 I/O scheduler (generally, it seems like a better scheduler for us - most importantly, it should help with the lags after switching on wifi, when every app begins to sync)

- Synced with CM repos (09/26)

Let me know how that scheduler works :) I experienced a soft reboot with the previous build too - while I wasn't able to get a log, let's hope that it was a CM bug which is fixed since then.
[Samsung Galaxy Nexus] garrymar:
Thank you, Ziyan! Black screen problem during incoming call solved for me after dirty update.
[Samsung Galaxy Nexus] moe61:
/

Hi there,

I just dirty upgraded to 09/26 and it is the snappiest experience till now. The changed scheduler seems to work wonders.

I didn't receive any calls yet so I can neither confirm nor deny the black screen lag still exists :D

Thanks again ziyan for your great work!
[Samsung Galaxy Nexus] :
+1

[MENTION=2633638]Ziyan[/MENTION]

Fantastic work, thx ziyan!

Any status news regarding migrating our "unofficial" cm maguro builds to official cm nightly builds (like tuna)?

Have a great week
[Samsung Galaxy Nexus] KarlusHTC:
1th day of daily use of the new built 09/26. It's great thanks [MENTION=2633638]Ziyan[/MENTION]

Enviado do meu Galaxy Nexus através de Tapatalk
[Samsung Galaxy Nexus] sddfdds:
Has anyone tried encryption with the latest builds?
[Samsung Galaxy Nexus] canetinhas:
Thank you!
[Samsung Galaxy Nexus] chakme:
Guys, one doubt: everytime when flashing a new build, you flash a GApp again?? Or it's not necessary?? I mean, not formating data partition, only cache and system...
[Samsung Galaxy Nexus] Childe89:
It´s not necessary, when dirty flashing/updating same rom. You don´t have to wipe system either, just cache and dalvik cache. :)
[Samsung Galaxy Nexus] tauvan16:
i feel sound is late just a little bit , anyone confirm that bug ?
[Samsung Galaxy Nexus] zieruchan:
I am ?
[Samsung Galaxy Nexus] Fenvarien:
Thanks [MENTION=2633638]Ziyan[/MENTION] for the new build! The added BFQ scheduler works just great for me and has reduced lags quite noticeable. :good: :)
[Samsung Galaxy Nexus] ASHURiCAN:
File temporarily unavailable? Another link please?
[Samsung Galaxy Nexus] redcrash:
Which file are you trying to download? I've just downloaded the last package and I had no problems at all. Since you indicate that you got a "temporarily" message, could you retry?
[Samsung Galaxy Nexus] ASHURiCAN:
It's ok now. Worked with PC.

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Samsung Galaxy Nexus] sddfdds:
Had a chance to try out encryption...the following is still the case

Any word on that being a viable solution?
[Samsung Galaxy Nexus] uncholowapo:
Hey is panorama and Photosphere missing for anyone else in the Google Camera app? I can open the app and see the image but after maybe a few seconds it force closes which was enough to see what was missing.
[Samsung Galaxy Nexus] hgmichna:
Panorama and Photosphere

To the best of my knowledge these functions are not there when the low_ram flag is set, which it probably should be on the Galaxy Nexus. If this is so then you have to do without these functions if you want to have the newer, bigger Android version on the meanwhile a little old phone.

Force-close is not good though. I have not seen that on mine. I suspect bad Google Apps. Try these:

http://winhlp.com/files/tk_gapps-modular-pico-5.1.1-20150816-signed.zip
[Samsung Galaxy Nexus] musical_chairs:
Hi [MENTION=2633638]Ziyan[/MENTION]! the new scheduler does seem to be really snappy. I had my phone on the charger and happened to glance at it and see the Google logo. Looking at /proc/last_kmsg, it looks like several bad things happen, and in the end it is the bfq scheduler that is complaining as it dies. It also looks like we are hotplugging CPU1? I thought hotplugging isn't reliable on the GNex? Anyway, this kmsg is from a toro running my build of CM12.1, built with stock cm kernel source. Here's the log:
[Samsung Galaxy Nexus] channaq4:
Im having issues playing streaming video audio and video not sync correctly.did any one having this issue?
[Samsung Galaxy Nexus] Ziyan:
Thanks for the logs, I'll investigate the issue. About hotplugging, it was unreliable on the ancient Google kernel, but it's way more reliable on the new kernel ;) I actually used the hotplug governor for some time, and it was working perfectly. Anyways, we're only hotplugging in suspend/deep sleep mode.
[Samsung Galaxy Nexus] garrymar:
Hello [MENTION=2633638]Ziyan[/MENTION]! I caught some selinux denials in dmesg and last_kmsg (attached), but /data/misc/audit/audit.log is clean. Also I noticed reduced battery life (~ -50%) compared to 8-31 build.
[Samsung Galaxy Nexus] moe61:
Hi there,

while the new scheduler is really fast and it brings back the speedy feeling a new galaxy nexus had when it was first released it seems to have some issues.

After my dirty flash and cache clean (including dalvik) I got random reboots and then reeboots after reebots. Also a cleaninstall didn't solve that so I'm now reverting to build 8/31.

Sadly I can't provide a last_kmsg because of too fast reboots...

Also I sort of found out why I had to format system partition prior to every new build. It seems that ClockWorkMod cwm can't handle the builds an breaks the installs.

Using twrp everything flashing works like charm.
[Samsung Galaxy Nexus] Ziyan:
Could you (and everyone who ever experienced a reboot) please try flashing the attached boot.img on top of the 09/27 build? You could also use an appropriate kernel settings app to switch back to CFQ if this isn't solving your issue, so you won't have to use an old build :)
[Samsung Galaxy Nexus] uncholowapo:
I doubt it since I downloaded the camera app from the play store. I flashed the latest build so no lowram to my knowledge. Weird...
[Samsung Galaxy Nexus] moe61:
where do I change the kernel settings.

What's changed in the boot.img?
[Samsung Galaxy Nexus] tofublock:
I flashed the latest update and was REALLY happy with it - fast and responsive to the point where I thought "maybe I don't need a new phone just yet?".

Today the phone wouldn't wake up from sleep and after pulling the battery it boots and instantly shuts off again. The boot.img did nothing.

I went back to 0831 now, but I still get reboots before Android is done optimising apps. I don't really know what to do about it at the moment and to be honest, I'm getting tired of this. Don't get me wrong, I love tinkering with my gadgets as much as the next guy and more, but resurrecting a dead screen on a primary phone every other week is slowly getting to me. ;)

Not to say it isn't awesome work you do here, of course!

edit.

Phone is alive again after I restored a nandroid backup of the 0831 image (the dance continues... ;) ). What happened with the latest, though? Any ideas?
[Samsung Galaxy Nexus] 0s1ride:
Yes, since the 20150831 build: http://xdaforums.com/showpost.php?p=62975215&postcount=3255.
[Samsung Galaxy Nexus] ftrack:
I am Also facing the same issue, after flashing with latest build my phone work fine, but movement i shutdown and start, after few second its getting hang and restart auto, again its happened, its happen till i again re-flashed with latest build but on another day same issue getting hand and restarting, Then i totally format my system everything wipe and again flash with latest build and gapps, but today morning same issue whats the problem with new build i am just tried of flashing doesn't understand why its happening. Now again flash and its seems to be working but i dought, it again start issue when i shutdown and restart.

Please help because i have installed after dirty flash but then also i m facing same issue.
[Samsung Galaxy Nexus] Ziyan:
Try flashing the kernel from post #3282. If that doesn't solve your issue, switch back to CFQ using your favorite kernel settings app (eg. Kernel Adiutor), and report back that only that worked.

I'm yet to investigate why BFQ seems to cause issues for some people, but doesn't effect others :rolleyes:

It has a BFQ-related change.
[Samsung Galaxy Nexus] musical_chairs:
[MENTION=2633638]Ziyan[/MENTION], for what it's worth I flashed the updated boot.img on my toro, but unfortunately it breaks radio. I'm thinking SELinux? Anyway, I know supporting Toro or Toroplus is outside the scope of this thread, but for what it's worth I pushed a commit to the tuna device tree that adds SELinux permissions for Toro and Toroplus proprietary apps.
[Samsung Galaxy Nexus] ftrack:
Thanks Ziyan :good:, I did as you suggested, flashed with boot.img and now everything seems to be normal and working smooth. Hope it will be as smooth as now after ill restart.

Really, one question actually i didn;t understand this eg. Kernel Adiutor pls let me know what if it won't work
[Samsung Galaxy Nexus] bamtan2:
Kernel Adiutor is a tweaking program by [MENTION=4443334]Grarak[/MENTION]! With it, you can change your IO scheduler from BFQ to CFQ, or sioplus, or whatever is available. :)

Here is the forum thread: http://xdaforums.com/android/apps-games/app-kernel-adiutor-t2986129

Download on google play store: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor

Download on f-droid store: https://f-droid.org/repository/browse/?fdid=com.grarak.kerneladiutor
[Samsung Galaxy Nexus] generalprobe:
[MENTION=2633638]Ziyan[/MENTION] i did a clean flash since im coming from a different rom and the os hang after i shot some test fotos when i left the camera app. i have not installed the boot image you posted.
[Samsung Galaxy Nexus] ftrack:
Hi Ziyan,

Thanks for your help, but unfortunately, none of your suggestion work for me, again today's morning my Gnx start with issue keep on hanging did lots of steps as suggested but anyway...

Now i am again back to Cm11 nightly seems everything is working smooth and stable... :cowboy:

I Hope i shall join you back but after 4 to 5 month later , till then keep up your good work :good:
[Samsung Galaxy Nexus] skyleth:
Hi Ziyan, it's the same for Hotplug. I had two galaxy nexus, and one supported the hotplug governor, and the other just didn't (it worked until the phone went to sleep, then I had to pull the battery). Probably it's the same for BFQ, some processors are more "resistant" than others

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] matorola:
just my 2c, latest build (09/26) works great for me.
[Samsung Galaxy Nexus] Ziyan:
BFQ shouldn't work like this, it should work for everyone - it seems like it's causing lockups for some people on <3.4, which is odd, since 3.0 is officially supported by the BFQ devs... so I'm changing back the default governor to CFQ in the next build, but I'll keep BFQ in the kernel, so we'll have the ability to switch to it anytime.

About hotplug, did you ever try it with the new kernel? Various improvements were made, it might be working for everyone now :)
[Samsung Galaxy Nexus] skyleth:
I'm on 4.4 now, but I'll try it during the weekend :)

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] siealex:
Galaxy Nexus has at least two (if not three) completely different hardware revisions. Different CPU versions, EMMC and radio chips.
[Samsung Galaxy Nexus] norton75:
Hello all

For my experience CM12.1 build 09/26 is the best till now

Unexpected reboot happened only one time, but with this scheduler (and F2FS partition) EMMC I/O lag (which was one of the biggest issue on this phone) completely gone away. Also with internal disk almost full I have no lag at all (previously if the disk was over 70% full, the phone became completely unusable)

A big thank to Ziyan for his great work, not all people who use this rom write on the forum, but I assure that we are so many people!
[Samsung Galaxy Nexus] garrymar:
Earlier, I reported my battery life reduced to 1 day (usually I charge battery once in two days). I decided to inspect the problem using BetterBatteryStat (BBS). After the app has been installed and the device has been rebooted I noticed that battery life actually increased to 3 days. :good:

I think, several days required to recalibrate the battery after update. As already been said, 9-27 build is the best for maguro at the moment!
[Samsung Galaxy Nexus] biglouis87:
I confirm, latest version is a lot better than the older ones... nice work! :)

Now the phone it's faster on app opening and answering phone calls, but in 10 days of use I still experience some reboots (not the soft ones, 2-3 times) and last night the phone completely froze (the back was hot), the alarm didn't ring and I had been late for work :p

Despite this, nice release.

I will buy an alarm clock for next mornings :D
[Samsung Galaxy Nexus] redcrash:
I completely agree with Norton75, garrymar and biglouis87.

I upgraded from cm-12.1-20150728-UNOFFICIAL-maguro.zip to cm-12.1-20150927-UNOFFICIAL-maguro.zip last week and the experience has improved a lot! It is much responsive!

Big bravo & thank you, Ziyan!!
[Samsung Galaxy Nexus] natzy85:
Notifications are shown at the top on lockscreen and I can't swipe them. Is this a bug?

Solved! It was because I disabled transparency in dev options :)
[Samsung Galaxy Nexus] musafercom:
gentlemen,

I AM ON the 28/7 RELEASE.

WHEN I FLASH ALL RELEASE THEREAFTER I GET STUCK ON BOOTLOOP.BUT WHEN I DIRTY FLASHED THE 28/7 RELEASE I DID NOT GET STUCK ON BOOTLOOP.

WHEN I FATORY RESET I DO NOT GET THE BOOTLOOP.

ANY IDEA WHAT IS THE PROBLEM.

I DO NOT MIND FACTORY RESET BUT I NEED ONLY WHATSAPP BACK UP BECUASE I DO NOT HAVE THE SIM CARD TO REGISTER AGAIN.

HOW CAN I BACK WHATSAPP WITH ITS DATA AND REGISTRATION AND GET BACK AFER FACTORY RESET AND FLASH OF LATEST RELEASE.

THANKS & BEST REGARDS
[Samsung Galaxy Nexus] ASHURiCAN:
Too big, makes pain to eyes, sorry, can't READ... [emoji29]
[Samsung Galaxy Nexus] musafercom:
Sorry I forget the caplock.

I stock into bootloop when ever I flash dirty any release after 28/7 release.

When I factory reset its OK.

The broblem I do not want to lose my whatsapp registration.I cannot register because I do not have the sim card.

How I solve the bootloop without factory reset or how can I back my whatsapp with its data and registration.

Thanks & bestregards
[Samsung Galaxy Nexus] natzy85:
Finally on the latest nightly we have instant caller showing when ringing. I even dirty flash over CM11 and everything just works. This is the best release so far
[Samsung Galaxy Nexus] WoolTomb:
Will you bring Android M (CM13) on Galaxy Nexus?

Pleaseee I need it :p [MENTION=2633638]Ziyan[/MENTION]
[Samsung Galaxy Nexus] skyleth:
Guys, relax and chill about the new Android 6.0

It's been released just now. Let the latest nexus to check if there are bugs, and sooner or later we'll get it

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] biglouis87:
LOL CM12 maguro is still bleeding edge, full of bug, and people think about CM13...

I think all our GN will die before Android M will be ported on this device :D
[Samsung Galaxy Nexus] AgentSmith:
^ Join the huge line of people that keeps underestimating the devs here. Lots of folks claimed we wouldn't get Lollipop either. ;)

Sure the hardware is falling light years behind but the devs are doing what they can. :)