yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sddfdds:
From http://www.cmxlog.com/12.1/maguro/ , i think that tiler revert in the pipeline for the next nightly was/is the problem so the 2/26 or 2/27 nightly might fix it completely
[Samsung Galaxy Nexus] chakme:
Hi guys!!

After something, that I could not figure out what is/was, one of my bank app (itaú mobile) stopped updating, it returned an "963 error, it was not possible to download the app (sometimes it returns the 907 error)"... Tried cleaning play store cache, uninstalling the app from play store and nothing solved the problem. Now, I can not even install it again.

Any thoughts ? Thanks in advance...
[Samsung Galaxy Nexus] Ziyan:
Yeah, I gave up on backporting the memory optimizations to CM12.1...
[Samsung Galaxy Nexus] phaleg:
If you have it available, what about uploading that build and share? XD
[Samsung Galaxy Nexus] playitlouder:
Will they reoccur in CM 13?

Me personally had zero issues with your first kernel with the reduced caveouts.

Do you know what's the exact problem when you open the camera, press home and open it again? This breaks the camera until a complete reboot for me.

Could you hack the memory allocation together with an userspace application? Basically an dummy app, that tells the system it needs X amount of ram, waits until it gets the memory freed up, exits and returns to the camera deamon?
[Samsung Galaxy Nexus] hgmichna:
Camera problem with cm-12.1-20160224-NIGHTLY

Both the CyanogenMod camera and the Google Camera still show some weird behavior or an error message, but sometimes they work.

Error message: Camera error - Can't connect to the camera. - REPORT DISMISS

Erroneous behavior: The camera opens with a black screen and a grey camera symbol in the middle, as usual, but then it stays like that for some time and never gets ready to take any photo. If you wait long enough, you may get an error message.

Workarounds are:

Just try to open the camera again. Sometimes it then works.

Press the recent apps button and swipe out the camera. Go back to the desktop and start the camera again.
[Samsung Galaxy Nexus] Markoz88:
I have the same problem at the camera.

Was it present on the previous nightly (20th of February)?

Or better, will it be fixed on the next nightly?

Thank you.
[Samsung Galaxy Nexus] hgmichna:
Camera problem with cm-12.1-20160224-NIGHTLY

Yes. This or a very similar problem was there before.

Everybody hopes that. :)
[Samsung Galaxy Nexus] a8a999:
I have copied it to google drive. It' the latest working build without any problem to me.

cm-12.1-20160210-NIGHTLY-maguro.zip
[Samsung Galaxy Nexus] pepexzz:
can we use the kernel from 24th january on the 10th? or will it cause the camera problem?
[Samsung Galaxy Nexus] kaberlis:
Hi all,

I have flashed the cm-12.1-20160227 version and after that operation, I installed Google Apps "open_gapps-arm-5.1-nano-20160227".

However, despite of the fact that it installs the apps successfully on recovery mode, after booting the phone and after it finishes the optimization step of all apps, it gives an error for all Google related apps such as: "Unfortunately Google Apps has stopped", or "Unfortunately Google X has stopped", and more than a dozen errors like this.

Therefore; I am not able to use my phone in any aspects right now, it is completely useless. If anyone have suggestion for me, I would very apprecciate.

Thanks a lot!
[Samsung Galaxy Nexus] sddfdds:
2/26 gapps
[Samsung Galaxy Nexus] Childe89:
Camera problem is still present on latest 20160227 nightly, have to try launching camera app multiple times till It runs :) Tried with stock and google camera, deleted their app data, wiped cache and dalvik again, but still same problem :)
[Samsung Galaxy Nexus] AndreiVolk:
Try with the micro package. I have read that nano and pico don't work very good on the galaxy nexus with LP and MM roms. Also, make sure to flash the gapps right after you flashed the rom. Don't flash the rom, boot the phone then restart in recovery to flash gapps.
[Samsung Galaxy Nexus] Ziyan:
What the hell. I guess I'll try re-enabling the camera hal debugging, maybe there's indeed a race condition going on somewhere...
[Samsung Galaxy Nexus] kaberlis:
Firstly, thanks for your answer.

In the first page of this threat, it says: "Google Apps can be found at .... "beware that if you choose OpenGApps, only the nano version will fit!"

Therefore, I used nano version. But I still can't use my phone, I could not figure this out, Gapps still were not installed properly. Anyone gives me a hand? :(
[Samsung Galaxy Nexus] sanjed:
I've been checking the camera on 27th build, connection is erratic, worked on the 6th try and then the 3rd after that. [MENTION=2633638]Ziyan[/MENTION], what logs would be useful, I've just installed Andylog
[Samsung Galaxy Nexus] Ziyan:
Try it out with the 28th build, if it keeps breaking, give me a logcat :)
[Samsung Galaxy Nexus] kaberlis:
The problem still continues, I couldn't solve this... I flash the ROM first, reboot the phone, and get in the recovery mode again, flash the gapps, reboot the phone and I get dozens of errors about Google Apps.

But I use ClockWorkMod Recovery v5.5.0.2, is this something related to this? To install official CyanogenMod ROM, do I need to use CyanogenMod Revoery.img?
[Samsung Galaxy Nexus] r.albu:
You can try and flash TWRP recovery. Then reboot to recovery and flash latest ROM version and immediately the gapps file: the first reboot ONLY AFTER flashing GAPPS.
[Samsung Galaxy Nexus] n@vier:
[MENTION=2633638]Ziyan[/MENTION]

28th build seems to solve camera bug thanks ;)
[Samsung Galaxy Nexus] johnSpar:
With build cm-12.1-20160228-NIGHTLY-maguro.zip camera is working fine :) :) :)
[Samsung Galaxy Nexus] Childe89:
Camera is now working for me too, with new 20160228 build :) Problem fixed :)
[Samsung Galaxy Nexus] kaberlis:
I tried in this way, nope it is still not installing Gapps in any way :)

I am literally stuck in. Now I can go back to the beginning. I can uninstall and erase everything if necesarry. But I don't know how can I uninstall completely the cm-20160227 version and flash the cm-20160228 for the first time without any OS on the phone? I transferred my improtant data to my computer and I can delete everything if necessary:(
[Samsung Galaxy Nexus] n76:
Might not be a good thing. . . Checking the change at http://www.cmxlog.com/12.1/maguro/ it seems it was simply an enable of debugging. If that fixes it, then it could be a timing issue which can (probably will) come back to haunt. And timing issues can sometimes be difficult to chase down and really fix.
[Samsung Galaxy Nexus] Ziyan:
Now I don't know if I should I re-add the memory optimizations, since it seems like it wasn't them causing the problems...

Yeah... I hate this camera hal.
[Samsung Galaxy Nexus] hgmichna:
Wipe system before flashing CM and Gapps

Have you tried wiping system before flashing CM and Gapps? Your data would still be kept.

---------- Post added at 07:11 PM ---------- Previous post was at 06:17 PM ----------

Another confirmation. Both CM and Google cameras now seem to work reliably on cm-12.1-20160228-NIGHTLY-maguro. Tested on two phones.

You could issue an experimental version or two to a few testers here only to avoid confusing other unsuspecting users.
[Samsung Galaxy Nexus] kaberlis:
For my Galaxy Nexus;

Step 1- I wiped the system

Step 2- Got into recovery and flashed "cm-12.1-20160228-NIGHTLY-maguro" -- It says successfully completed

Step3- After flashing ROM is completed, I immediately flashed "open_gapps-arm-5.1-nano-20160228" -- It says successfully completed

Step 4- Rebooted the phone.

Step 5- It says Andoid is starting... Optimizing app x of 92

Result: After it finishes the Step 5, the phone starts but I still can't use Google Apps. By getting "Unfortunately, Google x sas stopped" errors in sequences.

I wonder what I am missing over here...
[Samsung Galaxy Nexus] hgmichna:
Google account missing

Have you checked in Settings, Accounts whether your Google account is there? If not, add it.
[Samsung Galaxy Nexus] sddfdds:
Maybe you could do what I already said and install the 2/26 gapps since the same thing happened to me when I tried the 2/27 ones and then downgraded to 2/26
[Samsung Galaxy Nexus] SimonD1:
I have been doing the same as kaberlis for the past day with multiple version of Cyanogen and Gapps

My last attempt:

Step 1- I wiped the system (wipe system + dalvic + cache + factory reset but not "SD")

Step 2- flashed "cm-12.1-20160210-NIGHTLY-maguro.zip" -- It says successfully completed

Step3- without any rebot, flashed "open_gapps-arm-5.1-nano-20160227" -- It says successfully completed

Step 4- Rebooted the phone.

Step 5- It says Andoid is starting... Optimizing app x of 92

Step 6- first google play services happen during the walk-through, just after connecting to the wifi.

Before that I tried with open_gapps micro (does not fit) and pico (same result)

I also tried more recent version of the nightlies.

Would removing all data from the internal memory help?

I am using TWRP 2.8.7.0. I read somewhere to use an update version because of permission issues with older one.
[Samsung Galaxy Nexus] kaberlis:
Hi sddfdds;

Tried 2/26 but still have the same problem. Guys please what can I do anymore... You can see my screenshot through this link: http://i68.tinypic.com/23mkmyp.jpg
[Samsung Galaxy Nexus] Nautilus74:
Wipe DATA , cache , dalvik , system

and....

use OpenGapps nano !
[Samsung Galaxy Nexus] kaberlis:
My steps are exaclty same as you wrote. But still got this in the beginning: http://i68.tinypic.com/23mkmyp.jpg

I am not able to reach any kinds of Google applications, because they are not installed properly but I really don't know what I am missing.
[Samsung Galaxy Nexus] cloud_strife84:
Wipe all, flash rom and try aaroma version. In aaroma gapps don't select a thing and let's see if it works

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] SimonD1:
Wiping *ALL* did the trick : it seems something remains in data/data that prevented clean configuration of the app.

Dont forget to backup your pictures...
[Samsung Galaxy Nexus] playitlouder:
Testbuild?
[Samsung Galaxy Nexus] kaberlis:
Hi SimonD1;

Have you successfully installed the apps? If so, could you please help me with the step on how to wipe *ALL*. Because I am still stuck in and I couldn't install the apps. Your help is needed I guess.

Thanks in advance.
[Samsung Galaxy Nexus] defy_owner:
Yes, of course you should! I never experienced any problem with those, optimizations provided an extraordinary improvement.

And [MENTION=2633638]Ziyan[/MENTION] please consider this issue, it would be a great deal also for those who have problems flashing gapps.
[Samsung Galaxy Nexus] SimonD1:
In TWRP, select wipe->Advanced Wipe then I selected:

Dalvik Cache

Cache

System

Data

Internal Storage

External SD (?)

The regular factory reset keep the internal storage untouched... (pictures + download and other).

After I immediately flashed cyanogen + gapps pico and it worked.
[Samsung Galaxy Nexus] sddfdds:
heh, is that not the essence of nightly
[Samsung Galaxy Nexus] spryka:
i think we should give a try
[Samsung Galaxy Nexus] blystad:
There might be a small possibility that the Camera HAL was outsourced to a external consultancy company that had a business model where they would write horrible, semi obfuscated code, and charge outrageous prices for assisting with modifications to it... :)

Yeah...It's pretty terrible...Lots of code duplication, bad naming practice, race conditions etc...

On another note, we're still working on getting access to the GPU drivers. Our contacts has been on vacation, so communication lately has been lacking. We still don't know if we'll actually get access, but we're pushing. We're down now to 36 CTS test failures (we were at 150 or so when we initiated contact), and at least 8 of them depend on new GPU drivers.
[Samsung Galaxy Nexus] sanjed:
Has anyone else had a problem with the phone not connecting to saved networks? If I tell it to forget the network and then set it up again, it will work, but if I go airplane mode and back then it no longer connects
[Samsung Galaxy Nexus] spryka:
i've got a new problem.. i was experimenting with other rom and made nandroid backup in TWRP (twrp-2.8.6.0-maguro-f2fs.img from this thread)

after this i tried to restore and stuck on restoring 3gb /data.

System cache all went well but data stuck on ~20% (600-700mb). no errors. just huge performance degradation. i got 1-3mb restored for an hour

tried lot of things and one helped me. i formated /data to ext4 instead f2fs and succesfully restored my backup

Can anybody confirm this bug? (don't forget to save TWRP backup to PC before /data reformating) Tried new TWRP 3.0.0.0 f2fs as well and got same result

sorry for my English.
[Samsung Galaxy Nexus] phaleg:
I feel that you can hardly backup if your total is around 4GB or more...

It is not just a matter of file system, I would consider also the effect of warming up your phone too much and hardware stress

Try to do it after the phone has been off for hours in a cool and fresh spot
[Samsung Galaxy Nexus] hgmichna:
This differs from phone to phone.

If it is indeed overheating then disabling compression in TWRP could help.
[Samsung Galaxy Nexus] :
I had this problem before. It happens only when /data is F2FS. Never had issues with EXT4 partitions. This bug is not related to this particular ROM, just TWRP and the F2FS filesystem.
[Samsung Galaxy Nexus] zzpianoman:
If this happens, try extracting the backups manually from a command prompt. The backup archives (*.winxxx) are actually just tar archives so you can extract them manually from the root filesystem by typing "# tar -xvf /path-to-backup/backupname.winxxx"
[Samsung Galaxy Nexus] norton75:
I had this problem too.

Complete restore from a backup on F2FS filesystem took all night long to complete, but in the end it was successful. I think it is related to F2FS implementation in TWRP, since restoring on EXT4 filesystem with the same version of TWRP is very fast
[Samsung Galaxy Nexus] phaleg:
True... I don't like compression either ^^
[Samsung Galaxy Nexus] spryka:
i made backup with and without compression same result. it's not an overheating because same performed to ext4 works flawlessly

looks like it's associated with ram if partition less than available ram then no problem
[Samsung Galaxy Nexus] BadSanta_07:
In nightly build from 28.02 camera don't crashes anymore, it is good. But when Wi-Fi is turn on, the battery is discharged very quickly. If I turn off Wi-Fi battery lasts for a long time. And sometimes lost mobile signal
[Samsung Galaxy Nexus] davispuh:
I can confirm that camera freezing bug have been present in every version (I use camera every day and update nightly every few days) since first cm-12.1 release (but worked perfectly fine with cm-11), it still happens even with latest cm-12.1-20160228-NIGHTLY-maguro

it can be easily reproduced with Snapchat by quickly turning on/off flashlight and taking photos. Note that I didn't managed to reproduce it with regular camera app which no matter how I tried didn't hung.

Also even with regular camera app videos have green/purple sides.

from logcat when it freezes

D/CameraHal( 141): (42e83b60) device/samsung/tuna/camera/CameraHal.cpp:1261 setParameters - Positive bracketing range 1
D/CameraHal( 141): (42e83b60) device/samsung/tuna/camera/CameraHal.cpp:1272 setParameters - Negative bracketing range 1
D/CameraHal( 141): (42e83b60) device/samsung/tuna/camera/CameraHal.cpp:1356 setParameters - Restarting Preview
D/CameraHal( 141): (41118008) device/samsung/tuna/camera/ANativeWindowDisplayAdapter.cpp:956 processHalMsg - Display thread received DISPLAY_STOP command from Camera HAL
D/CameraHal( 141): (41118008) device/samsung/tuna/camera/ANativeWindowDisplayAdapter.cpp:990 processHalMsg - +Signalling display semaphore
D/CameraHal( 141): (41118008) device/samsung/tuna/camera/ANativeWindowDisplayAdapter.cpp:995 processHalMsg - -Signalling display semaphore
D/CameraHal( 141): (417bfce8) device/samsung/tuna/camera/BaseCameraAdapter.cpp:1370 __sendFrameToSubscribers - Empty Frame Queue
// CameraHal freezes here and doesn't respond anymore

dumpsys media.camera

still shows

Client[0] (0x41643d50) PID: 15289

even if that process was killed and no app will be able to use it

does anyone know how to restart it from adb without rebooting whole phone?

actually I just found it myself, need to just kill /system/bin/mediaserver and then camera works again yey :)
[Samsung Galaxy Nexus] rijalMuh:
Usb otg not work on CM 12.1, can anyone give the solution, please?
[Samsung Galaxy Nexus] bamtan2:
OR the camera debugging itself is broken =) and we're saved! ;)
[Samsung Galaxy Nexus] Ziyan:
The latest nightly should be available really soon, and has one of the RAM optimizations added back. Report back if it affected camera at all - it shouldn't have :)
[Samsung Galaxy Nexus] Childe89:
Camera is working correctly on 20160302 :)
[Samsung Galaxy Nexus] Fenvarien:
+1

Everything working nice and stable with the latest nightly.
[Samsung Galaxy Nexus] bamtan2:
It seems that all of our TWRP builds have a bug with backup/restore of F2FS partitions. and since F2FS is an important feature for some users, this bug needs to be fixed. BUT there's a big problem: no one is actively developing TWRP for Galaxy Nexus right now.

The solution I see is a bounty. I will donate $10 USD via paypal to the volunteer(s) who fix this TWRP bug. the three people who just reported it can decide when it's fixed, and then tell the rest of us who (or how many people) they think deserve the bounty. Will anyone else contribute to this bounty?

CC to TWRP contributors: [MENTION=912474]Dees_Troy[/MENTION] [MENTION=4831205]vocoderism[/MENTION] [MENTION=4240105]werty100[/MENTION]
[Samsung Galaxy Nexus] r.albu:
Hi,

When I need it, I reboot to recovery and copy/move/del with the file manager it has (I have TWRP recovery).

Yeah, not the best, but when in need...
[Samsung Galaxy Nexus] davispuh:
maybe just a coincidence, but previously I didn't managed to get "Failed to connect to camera" with regular camera app, but now it did happen few times with cm-12.1-20160302-NIGHTLY-maguro, but it doesn't actually hang and just closing it and opening it again it works fine so it's very very minor issue and might not be related.
[Samsung Galaxy Nexus] rijalMuh:
Thank you r.albu. is the bug? because in CM 11, usb otg was detected and can open in filemanager. And i try in CM 12 it's not work.
[Samsung Galaxy Nexus] a8a999:
I did a dirty installation. Camera works fine. Thanks!
[Samsung Galaxy Nexus] vocoderism:
What kind of bug you have?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Samsung Galaxy Nexus] bamtan2:
http://xdaforums.com/galaxy-nexus/d...eta-builds-t2958865/post65581918#post65581918 :)
[Samsung Galaxy Nexus] netreign:
someone will tell you how much RAM do I need total after last update!
[Samsung Galaxy Nexus] n@vier:
CPU-Z shows 794mb of ram.
[Samsung Galaxy Nexus] zingzangripper:
how is the battery drainage? still heavy?
[Samsung Galaxy Nexus] pepexzz:
mine is good, but a bit fast sometimes
[Samsung Galaxy Nexus] vocoderism:
try this experimental build only for test f2fs and report back

https://www.wetransfer.com/download...fcf7588d840d2d63450dbfa320160303175740/debd4c
[Samsung Galaxy Nexus] natzy85:
Is it me or the phone takes a lot longer to charge with cm12.1 then using stock?

Trimis de pe al meu Galaxy Nexus folosind Tapatalk
[Samsung Galaxy Nexus] vocoderism:
Someone try experimental twrp posted ?

Sent from Tapatalk for Windows Mobile OS
[Samsung Galaxy Nexus] spryka:
same result

~650mb restoring fast.

then huge performance degradation 20mb per 1 hour

restoring this backup to ext4 works with no any freezes
[Samsung Galaxy Nexus] phaleg:
Were you restoring a f2fs backup on "unofficial" TWRP 3?

(I don't see the official version of it)
[Samsung Galaxy Nexus] spryka:
official doesn't support f2fs

1st try was on 2.x one from Zyans thread

2nd on 3.x

3rd today on new compilations with some tweaks.. same result for all
[Samsung Galaxy Nexus] phaleg:
And for what I have seen, "official" TWRP 3.0 does not exist yet for maguro...

I guess you really need f2f2 support on your recovery
[Samsung Galaxy Nexus] vocoderism:
QUOTE=phaleg;65651285]And for what I have seen, "official" TWRP 3.0 does not exist yet for maguro...

I guess you really need f2f2 support on your recovery[/QUOTE]

Please try this

View attachment recovery.zip

unzip and flash img file with fastboot or twrp or flashify and report back
[Samsung Galaxy Nexus] vocoderism:
Simeone tried last zip with new experimental build?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Samsung Galaxy Nexus] spryka:
same :(
[Samsung Galaxy Nexus] vocoderism:
OK can you send me recovery log ?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Samsung Galaxy Nexus] spryka:
i don't know how to get it. i can't cancel restoration. that's why i should pull out the battery to cancel this. i guess there is no log after restart
[Samsung Galaxy Nexus] AgusL:
I am still having the SIM Card not being detected. Now I have found a new problem: When the SD Card is detected and working, if someone calls me, the phone reboots instantly, and then the SD Card it is not detected, and I have to reboot manually in order to get it working.

If I am the one making calls, the phone works perfect. The problem is when someone calls me.

This happens in both CM12.1 official and CM13 unofficial. This doesn't happen in ZMoD.

The phoen runs amazingly fast, no problem with camera at all, I am using Open Camera and it works perfect.
[Samsung Galaxy Nexus] vocoderism:
During restore send me output of dmesg and recovery.log on /cache

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Samsung Galaxy Nexus] agw42:
Any chance of getting this crash fixed? Can the issue be determined from the logs?

re-cap: removing th Gnex from the Samsung dock with pogo pins almost certainly results in a reboot after a few seconds and it comes up with no SIM found.
[Samsung Galaxy Nexus] Codename89:
Tried 20160302 nightly for a couple of days, camera has been completely fixed up.

No more "can't connect" issue, purple line on videos, or out-of-sync audio (using Google Cam app).

Thanks Zyian for your hard work ;)
[Samsung Galaxy Nexus] playitlouder:
It has something to do with Audio. Something complains about not being the right sampling rate.

There were some changes to improve the audio during the early 5.0 days. Something probably got broken while fiddling with it. [MENTION=2633638]Ziyan[/MENTION] could probably fix this.
[Samsung Galaxy Nexus] bamtan2:
Maybe agw42 could test a different distro, like maybe android 6.0, to see if the bug persists there?
[Samsung Galaxy Nexus] vocoderism:
please try this another experimental build and report back feed

View attachment recovery.zip
[Samsung Galaxy Nexus] bamtan2:
I'm not sure your testers know how to do this part. Maybe you can include instructions! ;)

Thank you for your work! :)
[Samsung Galaxy Nexus] vocoderism:
Try and report

Sent from Tapatalk for Windows Mobile OS
[Samsung Galaxy Nexus] Ziyan:
Are you sure you set up the build environment correctly (by following the wiki pages linked in the OP)? The nightly builds build exactly the same way, and as you see, they indeed build, otherwise there would be no recent nightlies :)
[Samsung Galaxy Nexus] vocoderism:
Simeone tried last twrp during f2fs restore?

Inviato dal mio Nexus 4 utilizzando Tapatalk