yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ArnoldGarry256:
Cellular Network unstable after 2 weeks of usage

Thank You for the great work done on this rom.

l've been using this ROM for close to two weeks and my network reception started acting up. Network became very unstable. No network on 2G was available anywhere anymore. They were basically network drops all through whenever screen was turn on. 3G would hold a little network but also became unstable especially when phone was pulled from the charging dock.

Basically, I could only get cellular network when phone was plugged into the charger or power bank and when unplugged, network would drop. So no cellular data connection as well.

It only happened after a week and a half. I was running the new Official version of CM12.1. Tried to upgrade do the latest nightly by then released on January 25, 2016. Still no change. Also tried to flash back a recent unofficial build of CM12.1 released just before the first official build. Still no change.

This issue never happened on the unofficial build for the time I used it.

Long story short, I reverted to the Official CM11 and everything works normal and good. I'd like to know what could have caused the issue in CM12.1 and if there is a fix, I'll definitely move back to CM12.1. It was perfect before the issues began. Thank you.
[Samsung Galaxy Nexus] Injek:
[MENTION=7024484]blystad[/MENTION] you got us all hyped up mate! We keep fingers crossed for our gnex!
[Samsung Galaxy Nexus] hgmichna:
2016-01-29 nightly

The 2016-01-29 nightly is running nicely here on 3 Galaxy Nexus phones. No issues.

Thanks!
[Samsung Galaxy Nexus] cloud_strife84:
Is it possible to increase volume? It's too low...

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] blystad:
Working on it :) We're talking to the correct people, but these things take time (probably will take over a month). There's no guarantee that we'll get access.
[Samsung Galaxy Nexus] neuimnetz:
Hi [MENTION=535343]all[/MENTION],

thanx for this great work!

The only thing that doesn't work on my device is to play music in the dock (the dock with this 3 pins).

The audiovolume control button is grayed out and no sound over the 3,5 mm output. :(

... so I went back to CM 11 ... and playing music in the dock works.

Any ideas? ... and sorry for my rusty english. ;)

Best wishes, Klaus
[Samsung Galaxy Nexus] netreign:
with last update i have more lags... before its was better
[Samsung Galaxy Nexus] hgmichna:
More lags?

How have you measured that?
[Samsung Galaxy Nexus] vortex-5:
I find that the new upate is less laggy (zcache disabled) seems to run better than CM11.

We all know the DDK1.9 line bug is present and the audio snap is still present. Out of the two I think most people want their camera to work for the time being I'm holding onto CM11 but the performance increase is swaying me :)
[Samsung Galaxy Nexus] hemantv:
Is Lollipop really better than Kitkat on our device? All the Lollipop roms I've tried so far perform decently but performance, I have to switch back to Kitkat. Am I missing something? If yes, please provide me some info as I really want to use Lollipop as a daily driver.
[Samsung Galaxy Nexus] bamtan2:
I think most would agree that 4.x and 5.1 perform differently. But 5.1 has its charms! The latest CM is the state of the art. Try it and see how it goes! :)
[Samsung Galaxy Nexus] cloud_strife84:
Could you please give me instructions on how using f2fs with this rom?

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] bigflea:
Great work yet, but: since CM12.1 is official, USB-OTG doesn't work anymore. It was very useful simply to plug an usb-stick to backup photos and so on.

Is it possible to reactivate this feature?
[Samsung Galaxy Nexus] cloud_strife84:
It doesn't work for me too

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] breversa:
Thanks ! I had the same problem, and your solution worked : adding the MMS info to the main APN, then deleting the MMS*APN and switch airplane mode on/off allowed me to receive my MMSs ! :D

For the record, I had this king of stuff in my logcat (not my logcat, but messages were the same) :

09-13 12:10:39.658 E/MmsService( 3140): MmsRequest: MMS network acquiring failure
09-13 12:10:39.658 E/MmsService( 3140): com.android.mms.service.exception.MmsNetworkException: Acquiring network timed out
09-13 12:10:39.658 E/MmsService( 3140): at com.android.mms.service.MmsNetworkManager.acquireNetwork(MmsNetworkManager.java:130)
09-13 12:10:39.658 E/MmsService( 3140): at com.android.mms.service.MmsRequest.execute(MmsRequest.java:149)
09-13 12:10:39.658 E/MmsService( 3140): at com.android.mms.service.MmsService$RequestQueue.handleMessage(MmsService.java:124)
09-13 12:10:39.658 E/MmsService( 3140): at android.os.Handler.dispatchMessage(Handler.java:10 2)
09-13 12:10:39.658 E/MmsService( 3140): at android.os.Looper.loop(Looper.java:135)
09-13 12:10:39.658 E/MmsService( 3140): at android.os.HandlerThread.run(HandlerThread.java:61 )

(Taken from http://xdaforums.com/showpost.php?p=62801043&postcount=8018)

It appears that CyanogenMod 12.1 has trouble when dealing with a separate MMS APN…
[Samsung Galaxy Nexus] skyleth:
two bugs I found so far:

-Every time I try to update to a new build with the auto updater and TWRP, I have an error. It reboots into recovery but then nothing happens, I have to manually flash the update from the cmupdater folder. TWRP is the latest official from twrp, I think is 2.8.7 or smthg like that. I really don't want to use cwm as it is right now, because it saves the backups inside the data folder and not the sdcard, so if you aren't careful, you may lose your backup if you plan to do a fresh install.

- The other one I found is with facebook, probably is the old one with the big apps. I manage to install the facebook app, I don't know how, but now I'm trying to update it and every time the phone goes into bootloop, only bat pulling can stop it. Any ideas?
[Samsung Galaxy Nexus] playitlouder:
The Facebook app ist really bloated, and takes quite a while to get optimized for the Gnex. There is a timeout on how long an app can take to install (makes sense, to not drain your battery while an installation hangs). The Facebook app takes longer to optimize than the timeout is, because mobile cpu's have come a long way since 2011 and our CPU is just too slow.

I would suggest you to look at Facebook Lite or Tinfoil for Facebook. These should work fine.
[Samsung Galaxy Nexus] skyleth:
I know, I was using Facebook lite and now I'm with Metal. But I thought that maybe it has been fixed since I managed to install the app

Enviado desde mi GT-I9300 mediante Tapatalk
[Samsung Galaxy Nexus] hgmichna:
Cyanogen Updater and Recovery

I am under the impression that Cyanogen has designed things such that the Cyanogen Updater is incompatible with everything except the Cyanogen recovery. So you have to use that one. Bye bye Nandroid backups and most other TWRP functions.

For that I hate Cyanogen. This behavior reminds me of big, arrogant companies.
[Samsung Galaxy Nexus] skyleth:
Then, at least, they should change the way their recovery handles the nandroids. It's pretty useless like that.

Edit: it seems twrp is working fine flashing latest nightly [emoji1]

Enviado desde mi GT-I9300 mediante Tapatalk
[Samsung Galaxy Nexus] tmxda:
I moved from PA 4.4.4 to CM12 nightly, feel like battery life has reduced. What kind of battery life are others experiencing?
[Samsung Galaxy Nexus] Hydre:
Thanks a lot to Zian ! Amazing work - the phone is working even better than with the stock ROM so far.

On my side feel like same battery life than with the stock ROM.

One quick question : I have no names in the list of apps, just the icons and can't find the settings to display the names of apps - can anyone help?
[Samsung Galaxy Nexus] axlu:
I do agree. It will be very nice to have this feature enabled. The latest nightly is working perfect. I like the camera.
[Samsung Galaxy Nexus] zingzangripper:
Same battery? Totally not.

I flashed back cm11 because of the battery drain.
[Samsung Galaxy Nexus] stavpup:
Guys do you recommend 5.1.1 over the 6.0 for gnexus?
[Samsung Galaxy Nexus] playitlouder:
Android 6 uses too much ram and is not (yet) optimized for running on low memory.
[Samsung Galaxy Nexus] bakers:
Do a long press on the homescreen. Then some kind of menu should appear. You can draw the bottom bar to the top of the screen (by pressing the three dots). Then go to "Drawer Settings" -> "Icon Labels" and press on it so that is says "SHOW". Now go back to the app drawer and check the result. :)
[Samsung Galaxy Nexus] Nautilus74:
Try zzpianoman's ZZ Android 6 rom! ;)

It's significantly faster than any lollipop rom!
[Samsung Galaxy Nexus] playitlouder:
Well they are still using the old graphics drivers which will cause problems with apps.

Android 5 is far from unusable in fact it works pretty well with Z-RAM. Using the stock browser is not that fast but it's usable in general and I doubt multitasking will get much better (apps use way to much ram these days).

Zyan did a good job.

I hope he will look into an 6.0 ROM in the future (not that 5.1 is that bad).
[Samsung Galaxy Nexus] agw42:
Docking station with bogo pins causes reboots

I'm using the (horizontal) Samsung Desktop docking station that is using the pogo pins.

About 20 seconds after removing it (or removing the USB cable from the dock), my Galaxy Nexus reboots and comes back with no SIM card found.

This is reproduceable.

Anyone has any fix for this?
[Samsung Galaxy Nexus] johnSpar:
Newbie here! :o

First of all, thank you to all those who made ​​possible this excellent ROM. This is the first time ever I use CyanogenMod and I have no plans to return to the official Google version (Jelly Bean 4.3) :good:

Everything seems to work fine except MMS. I can't make it work. These are my APN settings:

Name: Pepephone

APN: gprs.pepephone.com

Proxy: Not defined

Port: Not defined

User name: Not defined

Password: Not defined

Server: Not defined

MMSC: URL (I can't post outside links until the 11th message!)

MMS Proxy: 10.138.255.43

MMS Port: 8080

MCC: 214

MNC: 05

Authentication type: PAP

APN type: default,supl,mms

APN protocol: IPv4

APN itinerancy protocol: IPv4

Enable or disable APN: APN enabled

Connection type: Not specified

MVNO type: None

MVNO value: None

This is a logcat: pasted.co/2a3f050a

Can any expert help me out please?! Thanks in advance! :)
[Samsung Galaxy Nexus] Ziyan:
Attached is a boot.img suitable for any of the recent CM12.1 nightlies, with ~60mb more RAM freed up. Report back if all camera and video functions continue working correctly. More of this and more details later :)
[Samsung Galaxy Nexus] ovejota:
[MENTION=2633638]Ziyan[/MENTION] pictures seem to be working fine, video... not so much.

I can record videos just fine (when device is horizontal I can see the purple line), but when i play them, camera crashes afterwards and becomes unusable until you clear the app from memory and restart it.
[Samsung Galaxy Nexus] Fenvarien:
The test boot.img is working fine here, very stable and the additional RAM is great! No camera crashes here after playing videos, using the Google Camera app, just the well known purple line.
[Samsung Galaxy Nexus] garrymar:
Thank you, Ziyan! No problems with video using the updated kernel. Default camera and video player apps works as expected (and purple line is still here). Overall performance is very well. About ~300MB is free now (vs ~200MB before). Looking forward for details of such a great achievement. :)
[Samsung Galaxy Nexus] playitlouder:
Someone still uses mms? :P

Try deleting the separate mms APN and put the mms settings from your carrier into the data APN.

---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------

These docks are hard to find these days. I guess [MENTION=2633638]Ziyan[/MENTION] doesn't have one.

So please grab full logs and post it here (logcat, last kmsg etc.).

Andy Log works pretty good for that.
[Samsung Galaxy Nexus] agw42:
Thanks. Do you have a link for me that details how to collect these logs?
[Samsung Galaxy Nexus] playitlouder:
https://play.google.com/store/apps/details?id=com.bassel.andylog

After saving the logs, it will display the path in wich they are saved. Just zip it and upload it here.
[Samsung Galaxy Nexus] johnSpar:
That's exactly what I did...
[Samsung Galaxy Nexus] playitlouder:
Is zram enabled by default, or do I have to set it up using Kernel Auditor?

Hotplug is also not enabled in the latest "non nightly". I thought we were using that as out default govenour :silly:
[Samsung Galaxy Nexus] ASk4Net:
How to flash it?

fastboot flash boot boot.img

or

fastboot boot boot.img

to load and update the kernel?
[Samsung Galaxy Nexus] hgmichna:
How to flash boot.img

This looks correct:

fastboot flash boot boot.img

Another way is to flash TWRP 2.8.7.0 or newer with TWRP Manager, then use TWRP to flash boot.img. Then, if you like, you can immediately flash the Cyanogen Recovery.

TWRP has a button that chooses between ZIP and IMG files when selecting the file to flash. Nice treat.

The outstanding feature of this procedure is that you don't need a computer. The phone can do it all by itself.

You mentioned the kernel, but this has absolutely nothing to do with the kernel. The kernel is the Linux base on which Android runs.
[Samsung Galaxy Nexus] nikodr:
How much free ram in total?
[Samsung Galaxy Nexus] playitlouder:
About 300mb ;)
[Samsung Galaxy Nexus] ASk4Net:
It was 752M total memory and become 802 after last boot.img have been installed.
[Samsung Galaxy Nexus] Ziyan:
The next nightly should have the pink lines issue in video recordings worked around by modifying the default zoom value just so they aren't visible (the zoom can't be noticed at all - it's a very small zoom value). Honestly, I wouldn't be surprised if the old google camera hal used to do that... a bug fix which hopefully fixes all the remaining camera crashes also got merged. Thanks to an anonymous developer :)

About yesterday's kernel with more free ram enabled, I'm still searching for the safe values, so it won't be merged yet (another one that frees 3mb got merged though).
[Samsung Galaxy Nexus] playitlouder:
Can we combine the newest nightly and the "experimental kernel"?

Where did you shave off 63mb RAM? Graphics buffer or camera buffer or is that ram an general IO buffer thing?

Looks like quite a bit of work (according to that many changes in your github ;) )

I am asking, because after I flashed the kernel, I decided to clean up my internal storage, so I plugged the phone into usb and deleted a bunch of stuff. But when I tried to move a folder into an other one an error popped up telling me the device is currently busy (although I had no apps open on the phone and did nothing else on the computer).

[But this could be completely unrelated, I had bad luck with MTP in the past on other devices, I just thought I'd mention it :p]
[Samsung Galaxy Nexus] johnSpar:
Any ideas? MMS is one of the main features that should work on any CM version.
[Samsung Galaxy Nexus] skyleth:
Try deleting the apn and creating a new one with the pepephone website values. I had to do that last time I used the mms with pepephone

Enviado desde mi GT-I9300 mediante Tapatalk
[Samsung Galaxy Nexus] opticyclic:
Is it possible to re-size the system partition using fdisk or frankly, any other way?

I installed the Blackberry Apps and now I can't install even the PA Pico GApps!
[Samsung Galaxy Nexus] johnSpar:
I have already applied the configuration provided by the carrier (and I can't delete the APN because it is the main one).
[Samsung Galaxy Nexus] skyleth:
What about creating two new apns, one for internet and the other for mms, and then, delete the old one? Just an idea, i don't know if you've tried already

Enviado desde mi GT-I9300 mediante Tapatalk
[Samsung Galaxy Nexus] musical_chairs:
It is possible using this method: (requires odin)

http://xdaforums.com/showpost.php?p=64482777&postcount=28

Please note that after flashing most ROMs (except zzpianoman's), you'll need to use the 'resize FS' optino in TWRP to 'correct' system to your new partition size. See this post for explanation:

http://xdaforums.com/showpost.php?p=64675566&postcount=35
[Samsung Galaxy Nexus] agw42:
Attaching logs for this crash.
[Samsung Galaxy Nexus] nikodr:
Is there a way to overclock?without installing other kernel?i want to use it because of more ram this kernel has.but i always had my nexus running with 1.65 ghz so 1.2 is too little for me.
[Samsung Galaxy Nexus] a8a999:
No Weather above quick setting

I didn't see the weather above the quick setting. I have selected that option.
[Samsung Galaxy Nexus] bamtan2:
This is amazing work by all involved. Thank you [MENTION=2633638]Ziyan[/MENTION] and anonymous developer(s)!!!
[Samsung Galaxy Nexus] johnSpar:
That was the initial configuration but it didn't work. Some other people suggested to delete the mms APN and put the mms settings supplied by the carrier into the data APN. That's what I did but it also didn't work. I thought that it could be related to the default Cyanogen MMS client and installed Hangouts but the result is the same, no luck so far :(
[Samsung Galaxy Nexus] cloud_strife84:
Great job ziyan!!! Now that line on video disappeared, camera is perfect! By the way adding chance to overclock would be great. I used Franco kernel and more speed makes phone faster

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] vortex-5:
Anyone else still getting a speaker pop every now and then (even with screen touch sounds disabled).

Seems to happen whenever you either launch or close an app. Or when the phone is doing otherwise heavy processing.
[Samsung Galaxy Nexus] johnSpar:
Yes, this is an issue already reported.
[Samsung Galaxy Nexus] bamtan2:
I don't remember getting it ever since I was told to dig deep into the settings and disable touch sounds. I don't remember the exact name of the setting I changed, or even how to find it o_0
[Samsung Galaxy Nexus] ancelin:
Issues

Hello all,

Thank you for this super work, my phone in working really fine now!

But I have had 2 issues with this rom :

1) [Solved] I couldn't receive MMS.

Solution :

Add MMSC field in the data APN

and in type add ",mms" at the end

(default,supl,mms)

+ delete MMS APN

2) I can't download all play store apps because on some application I have an 963 error

- I tried to delete data and cache on the play store app (but not working)

- I tried to force app to be installed on internal sd with adb (pm set-install-location 1) with 0 = auto, 1 = internal, 2 = ext sd (but not working)

For information I used pico Open gapps from january 2016, I tried 01/28, 01/29 ... but nothing correct the issue

--> Do someone have same issue and solved it? Or can you provide me a link to working gapps?

Thank you for your help
[Samsung Galaxy Nexus] sddfdds:
ive had the 963 error, but only for bad piggies hd and lyft, not all apps...not really a solution for every app, but if theres a specific app you need updated, you can grab the apk from apkmirror and install it with adb (which i was able to do for lyft so adb is somehow able to transcend whatever the issue is)
[Samsung Galaxy Nexus] vortex-5:
Yeah like I said I've disabled it but overall it only reduces the likely hood that you'll get a pop but you still get it.

Try listening to music / podcasts when you close that program / start it you tend to get a pop.
[Samsung Galaxy Nexus] ovejota:
This is happening to me too. Strangely, only with some games (I now only remember Nimble Quest, which is not a big sized game). I even tried to download the apk and install it, but it also failed. There are no leftover files from the app, so I don't know what else to do...
[Samsung Galaxy Nexus] johnSpar:
It did not work for me :( Again... if some expert could take a look at this logcat to see what's going on with the MMS on my phone...:

pasted.co/2a3f050a

Thanks in advance
[Samsung Galaxy Nexus] nikodr:
Ziyan it is excellent rom. I used your boot. Img and have 802 mbytes of ram. Would you be willing to enable overclockibg in the stock kernel somehow?
[Samsung Galaxy Nexus] Tromzy:
There is one issue on my girlfriend's Gnex with this (awesome) Rom : there is always a notification saying "The SMS could not be sent" but there seems to be no SMS associated with that. Is there a way to disable this notification ?
[Samsung Galaxy Nexus] Hydre:
I have the same notification. Didn't find a way to disable it though.
[Samsung Galaxy Nexus] ancelin:
What is your sim card operator?
[Samsung Galaxy Nexus] johnSpar:
It is Pepephone, a MVNO that uses Movistar (Telefonica) network. I posted the values of the APN I am using on page 369 of this thread (btw, the MVNO fields are empty but those are the settings recommended by the operator and they were valid in Jelly Bean 4.3).
[Samsung Galaxy Nexus] blystad:
The main improvements I can see is reducing the size of the Ducati IO Buffer (which takes 90MB by default, atleast on our device), and removing SMC (TrustZone, which wasn't used anyways, because of a power management hardware bug on OMAP4).

See:

https://github.com/Ziyann/omap/commit/7c07453808bf0adba2465fb624c350172a8647cf

https://github.com/Ziyann/omap/commit/ac6398129acb0aa7801e69617d0ddd1b8248fe76

This _could_ be dangerous, since the size is hardcoded in Ducati and passed onto the kernel for the memory allocation. I think the best test is 1080p video encoding & decoding at the same time, while using the camera. A video calling application with 1080p video should do the trick. Also, try the Android CTS mediastress tests...those can be devastating to the buffers. Otherwise, video record, playback, record, playback could also show issues if they exist.

There's also some experiments with converting the Ducati driver to use CMA instead of memblock_remove. This will make the memory Ducati reserves visible, but not usable...Except, there's also another experiment being done where the `rpmsg` module (which deals with communcation between Ducati and Android) will be disabled/enabled at runtime. If this experiment succeeds then the memory used by Ducati _could_ be available when the Camera/Video encoder/Decoder is not in use - by disk and application cache. However, this could also result in longer time needed to start camera and do video encoding/decoding.

PS Ziyan, you'll want vmalloc=496MB if you're going to use CMA+Ducati :) That's the recommended value from TI on 4AJ2.5 kernel release. The default vmalloc of 128mb can result in heavily fragmented memory regions over long-term use on Android based devices (or so I've atleast heard).

All in all, pretty fascinating experiments :)
[Samsung Galaxy Nexus] Ziyan:
We already have an experimental kernel with the ducati reserved memory freed up when it's not being used (see: https://github.com/OMAP4-AOSP/android_hardware_ti_omap4/commit/4c1bd2b33150ede41e1f1483c67c1f52e862408c#diff-9323a7bafc55285b530dd018c84fbdaaR127) - it is working very well, the memory is actually freed up when ducati isn't being used (not just visible for the system - there's actually ~993mb usable memory). There are some hiccups with cma on kernel 3.0 though (allocations failing sometimes), but I'm sure this will get fixed up in the future. This is very experimental, so I'm not publishing any builds with this yet (the latest kernel commits aren't pushed anyways) :) my tests indicate that loading ducati and allocating the required memory always finishes below 1 seconds.

You're right about the ducati io buffer size reduction - I was able to create a camera crash with some 1080p video recording and playback situations, so this will probably get skipped. Not a problem once the CMA implementation goes live.

Thanks about the vmalloc notice, I'll try it out - don't forget to keep us updated if there are any news regarding a newer ddk version ;)