yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] blystad:
Impressive!

Question though, how did you get to 993mb usable memory? Did you reserve the carveouts using CMA instead of memblock_remove? I've seen 1013MB on our kernel, but that was without any memblock's removed (except Ducati which reserved using CMA)...and that resulted in...eh...fancy graphical artifacts...to say the least :)

Regarding DDK, our TI guy is doing his best. We've put more pressure on them since we're down to very few CTS test failures now (from around 250 when we initially contacted TI, to 50-100 now).

EDIT: should've checked more thoroughly. Yep, I see you use CMA allocation instead of memblock_remove ( https://github.com/OMAP4-AOSP/andro...mmit/3ef8750203ba9c48dfea28928f20ee06eee49d47 ). Cool, I've had a similar idea for a while, just hasn't had time to implent it. I'm a bit curious if this create issues with the GPU though? (Since the GPU shares memory, if it just expects the memory to be available without explicitly requesting it I think that might create issues)
[Samsung Galaxy Nexus] ancelin:
Did you tried with this?

Nombre de usuario: wap@wap

Contraseña: wap125

MMSC: http://mms.pepephone.com/servlets/mms

Proxy MMS: 212.073.032.010:80
[Samsung Galaxy Nexus] johnSpar:
Those are old settings... You can check the latest ones here (expand the 5th question in the FAQ):

http://www.pepephone.com/movil/preguntas/configuracion
[Samsung Galaxy Nexus] nikodr:
[MENTION=2633638]Ziyan[/MENTION] do you plan to make a new thread for this kernel with 993mbyres?
[Samsung Galaxy Nexus] bamtan2:
I am really impressed by everyone involved. This is really professional work by everyone, including the anonymous developer(s). ;)

I think ANYONE would be impressed by how well Galaxy Nexus performs today. AND, I'm blown away that you think there's more performance to be found. Really impressive!

I hope everyone involved will get the credit and/or donations they deserve =)
[Samsung Galaxy Nexus] thagringo:
absolutely ! im learning a lot so pls. keep talking !!!

cheers guys
[Samsung Galaxy Nexus] ancelin:
Error 963 on play store

I can't download some 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)

Same thing to me, if an apps is not working with market (error 963), I cannot restore it with titanium backup or install apk.

Apps not working are the same for every one but I don't found a common thing.

I try every time with "guitar tuna" (a small app).

I recently wipe the phone to install another Gapps version but I don't found any working gapps exept the Pico Open gapps (I did it because on some others phones they solved this issue with 2015 gapps)

Does everyone get the same issue ? If someone do not have this issue, can you please give a link to the used gapps version?
[Samsung Galaxy Nexus] bamtan2:
I installed guitartuna and nimble quest and both worked. Although guitartuna seems 'resource intensive' ;) The gapps I installed with the ROM are the standard smallest size opengapps. I'm sorry I don't have more help to offer ;(
[Samsung Galaxy Nexus] ancelin:
Ok thank you very much for your help. May be it is because i have used the same google account from 4.4.4...?

Are you formated in F2FS or just simple intall (ext4)?
[Samsung Galaxy Nexus] bamtan2:
I am on ext4. I WISH I was on f2fs ;)

I have used my account with android versions before 4.4.
[Samsung Galaxy Nexus] skyleth:
latest nightly doesn't dirty flash when updating from cm updater. TWRP shows this error

The zip file is not corrupt since I downloaded 3 times from cm updater and one directly from the website and it's giving me the same error. I can flash it manually though.

I have this problem before, but I thought it was fixed
[Samsung Galaxy Nexus] garrymar:
Did you compare the MD5/SHA sum of the downloaded file with the CM's published sum? It is also a good practice to upload companion MD5 file with the firmware, as TWRP could check the sum just before the flashing.

For example I always do the following steps (Linux environment):

1. Download the firmware (cm-12.1-20160210-NIGHTLY-maguro.zip for instance)

2. Compare the output hash from 'sha1sum cm-12.1-20160210-NIGHTLY-maguro.zip' with the published one.

3. If second step is successful, create an MD5 file for the zip archive. 'md5sum cm-12.1-20160210-NIGHTLY-maguro.zip > cm-12.1-20160210-NIGHTLY-maguro.zip.md5'

4. Upload both files in same target directory.
[Samsung Galaxy Nexus] skyleth:
No I didn't. The first time I just clicked on update, it rebooted into twrp, error, reboot into android, update, twrp and error, after that I downloaded the file from the browser on the phone, put it inside the cmupdater folder and went to cm updater and rebooted into twrp and got the same error, so I decided to take the risk and flashed it manually and it worked. No issues so far. Next nightly if I get the same error I'll compare the sums. Anyway to do this from android directly?
[Samsung Galaxy Nexus] garrymar:
Yes, you can use CM environment to do the above steps. Install any terminal emulator (ConnectBot, for example), enable root access for applications in dev. settings. Open the terminal and type 'su', then grant root permission for the terminal. Change directory, 'cd /sdcard/cmupdater'. Now, execute actions from the steps 2 and 3.
[Samsung Galaxy Nexus] Ziyan:
I know it sounds stupid, but I think CM updaters auto update feature doesn't really support TWRP - did you try using the CM recovery?
[Samsung Galaxy Nexus] atiartstudio:
latest twrp did auto update on yesterday's cm13 nightly for oneplusone.
[Samsung Galaxy Nexus] ancelin:
I have had the same error during my 2 last nightly update and i flash it as you did : manualy. No issue encountered

I was thinking it was twrp not compatible.
[Samsung Galaxy Nexus] hgmichna:
Hey, that's good news!

Had not ever seen that before.
[Samsung Galaxy Nexus] playitlouder:
I don't get, why CM want to do their own recovery?

TWRP is awesome. Why try to compete. Pointless.

TWRP FTW!
[Samsung Galaxy Nexus] skyleth:
Not yet. I'll try it when I'm at home, but I don't really like cm recovery since it doesn't backup to the sdcard, which I find quite useless for a recovery, but I give it a try again. [MENTION=2633638]Ziyan[/MENTION] is there any place we could add suggestions for the cm recovery?
[Samsung Galaxy Nexus] beatles1:
Hey all!

I'm a newbie here but I have been closely follwing Ziyan's work. Great job [MENTION=2633638]Ziyan[/MENTION] in keeping the Gnex alive. I'm planning to root it for the first time and dont really have a spare phone if it gets bricked. It would be great if this brilliant community could help me summarize the steps I should follow for installing the rom. What should I wipe and what should I keep?

Thanks a lot you guys! :)
[Samsung Galaxy Nexus] bamtan2:
To be honest, I think this is a fair question, because even as much as I know, I'm not confident I know enough to answer your question in the best way. I will say that you should backup what's important and expect to lose everything on the phone.

I can point to the tools I've tried:

http://xdaforums.com/galaxy-nexus/development/gnex-toolkit-v11-1-0-drivers-backup-t1392310

http://xdaforums.com/galaxy-nexus/development/toolkit-wugs-nexus-root-toolkit-v1-8-3-t2208863

Galaxy Nexus is the first "great" android phone, and many developers began with Galaxy Nexus, so many tools still support it well!
[Samsung Galaxy Nexus] beatles1:
Thanks a lot! Really appreciate it! :)

---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------

BTW.. I installed the rom and its working great. Only problem is that cellular internet does not work. Shows an exclamation mark. Any idea on how to solve this? Thanks :)
[Samsung Galaxy Nexus] AgentSmith:
To my knowledge there's no way rooting your phone is going to brick it. Then when you flash custom recovery (pref TWRP) you can always fall back on that when a ROM doesn't boot. So I think it's safe to say you'd have to do your best to brick your phone.
[Samsung Galaxy Nexus] skyleth:
I followed

I followed your steps and the sums are exactly the same. Probably Ziyan is right and cm doesn't support twrp and sometimes it update without errors and other time it doesn't. I guess we'll have to update manually until they decide to support twrp or change the path for the backups in cm recovery
[Samsung Galaxy Nexus] hgmichna:
TWRP vs Cyanogen recovery

There is at least one other way to handle this. I usually do it this way.

When I want to do something that only TWRP can do, like a Nandroid backup, I flash TWRP, using the TWRP Manager app.

When I am finished, I use TWRP to re-flash the Cyanogen recovery. Note that TWRP can flash .IMG files directly. You just have to have a reasonably current Cyanogen recovery .IMG file on your phone before you leave TWRP.

One characteristic of this procedure is that you do not need a computer.

If you use this method, always have this setting enabled: Settings, Developer options, Update Cyanogen recovery. To my knowledge this setting has no effect on TWRP, but when you later update your Cyanogen ROM, using the Cyanogen recovery, you get the Cyanogen recovery updated as well.
[Samsung Galaxy Nexus] skyleth:
That's a good workaround. Thanks!
[Samsung Galaxy Nexus] momojuro:
Did you try first to set your APN settings manually ? :) (Settings => More => Cellular Networks settings => Access Points Name).

If it doesn't help, I'm having an idea. Using Cyanogenmod 12.1 on my friend's S3, I had too an exclamation mark even that his cellular internet was working normally. I done some researches and I found the following :

Best regards.
[Samsung Galaxy Nexus] Codename89:
Hi Zyian,

I noticed that, starting from 20160212 nightly, cam is totally broken, both with cyanogen or google app.

It shows "unable to connect to camera". Could it be due to the latest related commit, "disable camera hal debugging"?

As usual, thanks for your amazing work :)
[Samsung Galaxy Nexus] Ziyan:
Odd, can you try flashing the boot.img from an earlier nightly? Report back if it fixes the issue.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
[MENTION=2633638]Ziyan[/MENTION] I see this rom has the nightly tag. I use my Gnex as a daily driver as such I need a stable and smooth device so according to you should I flash your rom or not
[Samsung Galaxy Nexus] bandelenth:
I am using this rom as a daily driver and I would say it is pretty stable. I have no crashes or such things, but my phone is mainly a phone, so messenger, calls etc... I haven't tried games or other really intense activities. If you want a rock solid system, go with an old stock version, I would say. But if you can bear with updating every few days and want to use newer features of android I would go with the nightlies.
[Samsung Galaxy Nexus] ancelin:
@ CoDe LaZaRuS this rom is really good and can be used as daily but for my side i have an 963 error while downloading some play store app.

Do not use the last 12/02/16 build because flash and camera aren't working.

I try now to boot last 12/02/16 build with 10/02/016 boot.img --> reply soon --> It Worked!! Flashlight and camera is back

No more APN issue

But still this crazy 963 error market... --> Solved! with 20160120 opengapps

---------- Post added at 06:07 PM ---------- Previous post was at 05:47 PM ----------

If someone interested I bought this battery : Akku-King-Batterie-Samsung-Galaxy-GT-i9250 with NFC support and now my phone can run at least 3 days long !!! I won't change my gnex now.
[Samsung Galaxy Nexus] beatles1:
I added a new APN for my AT&T and now it works like a charm! Thanks a lton :)
[Samsung Galaxy Nexus] Codename89:
Tried the solution, it works! Can you fix the issue on next releases? :)
[Samsung Galaxy Nexus] ancelin:
Error 963 on some google play store apps --> Solved!!

HAHA now phone running like a charme!

So if you encournter like me this 963 play store error on cm12.1, you need to flash those pico opengapps :

20160120

If I flash up i have the error. It may be a google issue and they have to fixe it (No issue on CM13 opemgapps)
[Samsung Galaxy Nexus] Ziyan:
Hopefully it'll be fixed in the next nightly, as I found a safe combination of carveout sizes. This should result in about 50 mb ram freed up, with all camera functionality working (no crashes - report back if a crash happens, and I'll try to reproduce it). Note that this will result in a garbled screen during the transition from the google logo to the boot animation for a second or two, which I'll fix later if the reports about camera are positive.
[Samsung Galaxy Nexus] sddfdds:
nice catch...fixed it for me as well
[Samsung Galaxy Nexus] djkk16:
for those who are using the latest nightlies, how is the battery life for you guys ? for me the performance of the nightlies is pretty great but battery life isnt much good. am sing powernap, greenify and amplify and there still seems to be idle battery loss and screen on time is quite less compared to my stock jb battery timing.
[Samsung Galaxy Nexus] AgusL:
I am having random soft reboots here. It happens when I am just using the phone with basic things like Instagram or Whatsapp or when using the camera. The ROM runs amazingly fast and I have not found slowdowns at all but I am experiencing this random soft reboots out of nowhere. This never happened on ZMoD.

And always that this happens, the SIM card is not detected and I have to manually reboot in order to get it working. Have you been having trouble with SIM not being detected? This never happened on ZMoD either.
[Samsung Galaxy Nexus] Roman_Likhachev:
Camera line fix http://xdaforums.com/oneplus-one/themes-apps/app-cameranext-modded-t2999275
[Samsung Galaxy Nexus] n76:
I have been running the 20150906 build of ZMOD since it was released. I have had several occasions when the SIM stopped being detected and a reboot was required to get it working again. It does not happen often, maybe once a month or so. But I have seen it happen.

I really hope that at least one more ZMOD build is released, I have really been enjoying it and would like the latest fixes described for CM12.1 in this thread.
[Samsung Galaxy Nexus] goblin999:
Hi everybody,

First, thanks to the developers for their hard work. Much appreciated!

I've only noticed a significante decrease in battery life in this last ROM. So much that I'm thinking of reverting to the previous release date... And the soft-reboots became obvious in this last ROM also...
[Samsung Galaxy Nexus] playitlouder:
I think the best test for the camera would be to install a Dashcam app and a Time-lapse app.

Then let the phone record a few hours with the Dashcam app and afterwords take a long timelapse.

If you want to test the decode just start a slideshow in the gallery app and let it think for a couple of hours.
[Samsung Galaxy Nexus] pluk64:
Me too. I am always charging my battery to 100% before night. During night I put the phone to airplane mode. I always had around 94-96% battery in the morning (after ~8 hours). Now (since around cm-12.1-20160207-NIGHTLY?) it's just 77-80%.

Battery usage statistics are not very helpful, as you can see in following screenshots: https://goo.gl/photos/4pdoJjdP8s95c7A98

So I thought my battery is dying, but if you have similar problem it's perhaps something else.

Also, I thought about buying new original 1750mAh battery, but I'm not sure whether it would have a better battery life than my current battery (stock, 4.5 years old, charged once a day, now at least twice)

I have no soft-reboots.
[Samsung Galaxy Nexus] playitlouder:
Try installing GSam Battery Monitor. It will show more detailed stats.
[Samsung Galaxy Nexus] michitux:
I have observed something very similar after upgrading from 2016-01-29 to 2016-02-07. I charge my phone during the night and during the day I don't use it a lot so after 8 to 10 hours I usually still had around 70%, now it's just around 60%.

I had a look at the statistics that are provided by Better Battery Stats and I found nothing unusual, i.e. only few wake locks, alarms mostly for Play Services (and not too many) and most of the time the phone was in deep sleep. I hadn't checked that on earlier CM12.1 nighties but I remember that on CM11 I had a bit less deep sleep. Therefore I'm relatively sure that this is not on the software side.

My guess is therefore that disabling SMC caused this. The 2016-02-07 nightly is the first nightly where SMC was disabled. In case you are wondering why disabling hardware could cause a higher battery consumption: sometimes a component needs a software in order to activate power saving. So no driver/firmware could mean more battery consumption. Maybe [MENTION=2633638]Ziyan[/MENTION] could provide us a kernel with SMC re-enabled to test this?
[Samsung Galaxy Nexus] spryka:
i have battery drain too

a couple of nightlies before, i had < 2-4% battery consume per deep sleep at night.. today i had 65% through the night 10h 9h of deep sleep. wakelock detect nothing unusual
[Samsung Galaxy Nexus] erOzeOz:
Same problem with the battery drain for me.

Otherwise works great.

Thanks Ziyan, please bring MM to life now :)
[Samsung Galaxy Nexus] blystad:
Do:

adb bugreport > bugreport.txt

and post that here, or diagnose yourself at: http://battery-historian.dev.hostedmobiles.com/ (it's a server running the same tool Google uses for battery analysis).

If it's a wakelock then it will show up there. If not then it might be that a power domain is unable to enter suspend. We've seen this happen with dss (Display Subsystem) on 3.4. That will not show up on battery-historian, but the kernel log will show it, and the kernel log is part of the bugreport.
[Samsung Galaxy Nexus] Codename89:
Hi Zyan, I flashed latest nightly with carveout changes (20160214) but unfortunately it doesn't solve the problem. Camera works a few times, but most of times it returns to me the usual warning (cannot connect to camera). Help :(
[Samsung Galaxy Nexus] pluk64:
I tried "bugreport > bugreport.txt" through Terminal Emulator for Android and I'm getting "Failed to connect to dumpstate service"
[Samsung Galaxy Nexus] mstyle3244:
cm-12.1-20160214-NIGHTLY-maguro.zip I installed it, Google camera did not work.

Also , Scroll of Google+ App and Google App is not smooth.
[Samsung Galaxy Nexus] Ashutos1997:
Carrier name got fixed in CM12 20th December nightly / Android 5.0.2 build i.e. carrier name now on top left side of screen.
[Samsung Galaxy Nexus] aliesz:
Has the long sms sending issue been solved in new build?!
[Samsung Galaxy Nexus] Nabbolo:
You mean build 20 Dec?
[Samsung Galaxy Nexus] aliesz:
Yes certainly I mean the latest version, thanks bro..
[Samsung Galaxy Nexus] Suxsem:
It sounds very interesting!

Edit: check also this: http://xdaforums.com/showpost.php?p=57550984&postcount=2924
[Samsung Galaxy Nexus] xergio24:
Hi guys! 2 things:

1. Is there a workaround for the off-line charge? I have a battery that run out of energy and now I cannot charge it (I don't have a battery charger), so I'm now using an old battery (that luckily had some energy).

2. What Camera app are you using? I read that stock camera don't work but if we download another camera app it would work... I have already tried "Camera 2" and "HD Camera" and they also crash.

I'm on 2014-12-20 build

(Nice job Ziyan!!!)
[Samsung Galaxy Nexus] foosion:
2. http://xdaforums.com/showpost.php?p=57271342&postcount=164
[Samsung Galaxy Nexus] Reptilez_DK:
1. Make a backup.

2. Flash a kitkat ROM.

3. Recharge battery.

4. Restore backup.

5. ???

6. Profit.
[Samsung Galaxy Nexus] foosion:
It does seem to improve responsiveness and doesn't seem to have had any effect on battery life.
[Samsung Galaxy Nexus] xergio24:
thanks! =)

+ 7. Don't let the battery goes below 1% until the bug is fixed xD haha

thanks!
[Samsung Galaxy Nexus] zzpianoman:
If you can get it to boot into recovery mode, you can charge it from there. I know the low power cutoff in the kernel is set at a lower threshold than it is in the OS so when Android reports that you have 0%, recovery will still show you as having 4%.
[Samsung Galaxy Nexus] AllAboutTech:
where is the download link?

thank you in advance..
[Samsung Galaxy Nexus] madhavs:
http://build-server.com/daniel/cm-12-20141220-UNOFFICIAL-maguro.zip
[Samsung Galaxy Nexus] AgentSmith:
What I would try first is to quickly swap batteries while the phone is on. I think the device stays on when it's connected to the charger, at least for a bit.
[Samsung Galaxy Nexus] xergio24:
Battery issue workaround! (extra battery needed)

Thanks! It didn't work that way... because the battery wouldn't even get to Recovery, but you gave me an idea that worked!

Here is my workaround (simpler than having to flash CM11 ROM, but you need an extra battery with some energy).

1. With the phone off, plug in the battery with energy.

2. Boot to Recovery.

3. Plug the charger.

4. Put off the battery (the phone will stay ON).

5. Plug in the empty battery.

6. Done! that will charge the empty battery... after some minutes you can reboot to system and keep charging it with phone turned on =)

--- EDIT:

Indeed! It will stay on, but only on Recovery mode... not with the phone tuned on into android.
[Samsung Galaxy Nexus] betizad:
I installed the ROM yesterday and I am amazed how stable it is for a beta release. I only have one issue (apart from camera which is known and using camera zoom fx it is resolved) which I don't know if it is known:

When I open an app and after a while that I work with it, I wanna go back or switch to another app but it takes quite some time to switch.

Even if I switch to home launcher by pressing back or home , it seems that it is restarting launcher kind of it has been closed and redraws everythin. I noticed in the memory vaialble that I have more that 250MB free memory, so I don't understand the behaviour.

Thanks for this great work,
[Samsung Galaxy Nexus] foosion:
Same here, although sometimes going back home is quick. When it's not, it can be very slow. Increasing the clock speed as Ziyan suggested helps somewhat. The 20141201 version continues to be the smoothest for me.

The camera not working means many related apps don't work, such as Authenticator (can't scan QR code), google goggles and flashlight.
[Samsung Galaxy Nexus] XneofuX:
Seems to work just fine. I noticed no change in battery life but the responsiveness is better. Even if you don't change it by default, I'll change it after every update if i have to! :D
[Samsung Galaxy Nexus] md1008:
I am confused about the charging bug. I am able to charge this phone. What instance does this phone not charge? I am on 12/20 CM11
[Samsung Galaxy Nexus] basf:
from first post

- charging text stuck on the lockscreen, offmode charging broken
[Samsung Galaxy Nexus] AgusL:
Scrolling of Google App is working fine on my device. Smooth as expected.

I use Open Camera, sometimes the camera doesn't connect or I have FC but I open it again and works.

I have not experienced soft reboots with 20160214 yet.
[Samsung Galaxy Nexus] Regina Rainbow:
Just wanted to report/confirm, that after flashing cm-12.1-20160214-NIGHTLY-maguro.zip Camera can connect a few times, then fails to do so consistently.
[Samsung Galaxy Nexus] blystad:
You need to do it from a computer. Alternatively you can do "dumpstate > something.txt" on the device as root, it's equivelent.
[Samsung Galaxy Nexus] mukesh:
Same here. Also, GPS not locking.
[Samsung Galaxy Nexus] alexradium:
Me too,camera not working.

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pluk64:
Thanks. Here it is: https://drive.google.com/file/d/0B2v1e-TCSUpIajc1UE55dGhjdzQ/view?usp=sharing

And some screenshots: https://goo.gl/photos/rRDRET8gekpDHuni8

Uhm... so it looks like Play services?

Now I remember I enabled some play services feature a few days ago, but I cannot remember what was it.
[Samsung Galaxy Nexus] Sesme:
My camera run's great on 0214

:D 0212 no run's camera

Please clear data on camera app
[Samsung Galaxy Nexus] erOzeOz:
I'm having a lot of soft reboots on 0214 build.

SuperSU 2.46;

eXtremeBeats 5.0, Viper4Android 2.4.0.1;

Xposed v80;

Greenify 2.8.0.1, Power Nap 0.7a