yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] skyleth:
anybody using the cm recovery (cwm based)? I've tried it, but it still saves the backups in /data/media/clockworkmod instead of the sdcard so if you wipe to install a new rom or fresh install you lose your backups. Anyway to fix it?

I know TWRP is working, but as CWM is included in CM I guess it should be working out of the box

---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------

CM12.1 or Zmod are fine. Also, if you really need it to record videos, try the unofficial cm12.1 with DDK1.8, you won't have the green/purple line
[Samsung Galaxy Nexus] papei:
Since when does CM recovery make backups? I only have it on my galaxy s2 because I am forced to. It is tied in with the kernel. As far a I have seen there is no option for backups.

On my galaxy nexus I am using TWRP.
[Samsung Galaxy Nexus] skyleth:
I don't know in the S2, but in our gnex is a CWM based recovery, if I remember correctly it has the regular ui, but is touch. in the menu there is a "backup and restore" option, or something similar and there you can select to do a backup or restore a previous one
[Samsung Galaxy Nexus] papei:
Interesting. I didn't realize CM recovery differed from model to model. One of the main reasons I don't like it is because there is no possibility for a backup, at least on the S2. If it is different for the g-nexus I might give it a second chance.

Cheers.

P
[Samsung Galaxy Nexus] defy_owner:
I hope it's not stuck in a rut.

Can we have an updated build by the way?

Thanks again for your work. ;)
[Samsung Galaxy Nexus] breversa:
Thanks for pointing that out ! I found the solution myself, but I'm glad I'm not the only one affected.

Is there anyway to integrate that command in future builds ?
[Samsung Galaxy Nexus] djflexlive:
First, thanks for this ROM.

Btw I have an issue with my phone network, the signals goes up and down with some losts.

I have Rogers Canada as Carrier, the radio ROM is : 1.25.21331147A1.06G_20.69.4196.01_F

Where can I find another radio rom more compatible with this CyanogenMod version ?

Thanks.
[Samsung Galaxy Nexus] playitlouder:
Is there a fix for the camera with the RAM optimizations on the way?

Ram usage on modern Android is just crazy (CM13 on the Nexus 5 has a bug, if the ram fills up completely, the radio crashes and the phone performs a hot reboot. It crashes every other day. On kitkat 2gb was awesome, nowdays it's just 'okay'. Older background apps are closed pretty often).

But Motorola is updating their 1gb RAM Moto G to Marshmallow, so it has to be possible to not run out of memory.
[Samsung Galaxy Nexus] hgmichna:
Lack of RAM

My wife just reported that she keeps having problems to run Google Navigation on her Galaxy Nexus with the 2015-11-02 version.

My guess is that Android got bigger, the Google apps got even bigger, and particularly Maps and Navigation got a lot bigger, perhaps due to the new off-line navigation.
[Samsung Galaxy Nexus] breversa:
<off-topic>

Offline navigation is a new feature in Google Maps ? That's cute : OsmAnd has been doing it for age. :P

</off-topic>
[Samsung Galaxy Nexus] hgmichna:
Kernel with swap or zram

Does anybody know of a replacement kernel that is capable of swapping or at least zram? The shortage of RAM in the Galaxy Nexus makes its use increasingly difficult. Problems with Google Maps/Navigation are one example.

Of course the kernel would have to work with CyanogenMod 12.1, as described in this thread, and, I hope, with 13 soon.

If you have tried swap or zram on the Galaxy Nexus with CyanogenMod 12.1, what is your experience?
[Samsung Galaxy Nexus] bamtan2:
[MENTION=4608636]bsmitty83[/MENTION] is who you're looking for. Unfortunately there's a bug in the current kernels that have ZRAM enabled by default: they do not allow you to change the size. Maybe the older one there, R21, doesn't have it on by default. I'm using 17 or 19 I think, but those downloads were taken down. http://xdaforums.com/devdb/project/?id=7544#downloads
[Samsung Galaxy Nexus] Tromzy:
Hi, I flashed my Gnex with this Rom and it's pretty awesome ! I have just one (big) problem : the data network keeps disconnecting, every 30 seconds or less. I have to retick the "Mobile Network" option all the time and after a few seconds it unticks itself. Calls and SMS work fine. I tried upgrading the radio Rom but it did not solve the problem. Any idea ?
[Samsung Galaxy Nexus] hgmichna:
Does manually entering the APN settings help? You may be able to get them from your mobile phone service provider's web site.
[Samsung Galaxy Nexus] Tromzy:
I tried but it didn't help. :/
[Samsung Galaxy Nexus] defy_owner:
Hey [MENTION=2633638]Ziyan[/MENTION], may we have and updated build?
[Samsung Galaxy Nexus] playitlouder:
Try Sygic. Should run well.

They are on sale at the moment.

The folks over at the S3 camp are enjoying a nearly bugfree CM13 with 3.0 kernel. Funny if you look back at codewokx swearing while getting CM9 to work (camera was a pain).
[Samsung Galaxy Nexus] Tromzy:
I reintalled everything and it seems to work now. Maybe it was a configuration error due to Titanium backups or something. :)
[Samsung Galaxy Nexus] hanschke:
will 13 come :fingers-crossed:
[Samsung Galaxy Nexus] Ziyan:
New build up. Changes:

- reclaimed ~6 megabytes of userspace RAM

- enabled video stabilization, exposure and whitebalance lock in the camera HAL (our ducati supports these, but it's not advertising it! what a *****...)

- disabled dex2oat watchdog (this should make the optimizing apps dialog on every boot disappear, and hopefully fixes installing large apps)

- synced with CM repos (01/01)

I also switched back the default I/O scheduler to BFQ - I hope that the lockups some of you experienced were caused by an older CM bug (they made some BFQ-related platform changes).

If anyone encounters another one, and wants to switch back, simply change sys.io.scheduler to cfq in /system/build.prop. Alternatively, use your favorite kernel settings app to change to CFQ on boot (but I'd recommend changing build.prop instead - I think Kernel Adiutor has a nice interface for editing it). And remember: if it locks up again, no need to remove the battery: just hold down the power button for at least 10 seconds, and the device will turn itself off.

As soon as I'm satisfied with the results (currently, I'm not - looking at you, memory management).

Facts:

- they received official KitKat update with proper drivers and stuff, tuna only got 4.3 (Samsung updated their EGL blobs for KitKat, meaning they didn't have to port over to a new kernel like we did, and didn't have to switch to a newer camera and domx hal)

- there's at least 10 people actively maintaining it over CM

- their user and developer community is at least 10x bigger

I can't express how hard and time-consuming it is to maintain tuna with only two active developers :(
[Samsung Galaxy Nexus] Roman_Likhachev:
In new realise : Camera dont have photosphere ;(
[Samsung Galaxy Nexus] sddfdds:
you can get it back by switching lowram in build.prop to false (though having said that, i dont know what/if other problems this may create)

thanks for the new build, ziyan
[Samsung Galaxy Nexus] Childe89:
Thanks for the new build, nice after-christmas present for surviving Galaxy Nexus users :) Though I´m experiencing one crash in this build - everytime I run Dolphin Browser, phone freezes and restarts after few seconds... I´m using Dolphin for a long time, never happened before... no problem in other apps, what might cause such freeze/reboot?

Seems it was BFQ problem, switched to CFQ in build.prop and Dolphin works again :)
[Samsung Galaxy Nexus] Ziyan:
That's a shame - sounds like we have something conflicting with BFQ then (it can't be BFQ itself, since it has an "official" 3.0 release which we are using, and it's being upstreamed post-4.0).
[Samsung Galaxy Nexus] sddfdds:
not sure about other large apps, but for facebook this results in a soft reboot after a while trying to update...also, not sure what this means in terms of it almost being successful, but it leaves extra facebook folders in data/app for each attempt, so theres com.facebook.katana-1, com.facebook.katana-2, com.facebook.katana-3, etc...

a rather clunky workaround if anyone wants (for facebook, presumably other large apps? but im not sure) is to tell the play store to update, wait for the dl to finish and the play store to say installing, then check /data/app for when it creates a new facebook folder, pull the base.apk from the new folder, then update with adb install -r base.apk
[Samsung Galaxy Nexus] SuperGoober:
Hi , is this a unified build for all 3 variants ? If not do you ever foresee it being unified ? thanks
[Samsung Galaxy Nexus] supermario3:
Buttons on my maguro are not working :(

Is there any way to enable double tap to wake or something similar on this build?

I don't mind installing new kernel or app, I just want continue using my galaxy nexus

Thanks
[Samsung Galaxy Nexus] hgmichna:
Buttons, double-tap to wake

Which buttons are not working?

To the best of my knowledge double-tap to wake requires suitable hardware, which the Galaxy Nexus does not have. So that will never work, unless I am overlooking something.
[Samsung Galaxy Nexus] eternal70:
Old ROMs have TouchControl support. Cm12.1 from zzpianoman support that to if i remember
[Samsung Galaxy Nexus] norton75:
Successfully installed version cm-12.1-20160102-UNOFFICIAL-maguro, no problem so far, no reboot at all with BFQ scheduler.

For all that have spontaneous reboot, i noticed that this happens often when the SD free space is below 3Gb. It seems that the EMMC suffer very high access delay that cause self reboot if free space is below this value; freeing some space (currently i have about 8Gb free, F2FS data partition) the phone literally fly!

It worths a try
[Samsung Galaxy Nexus] bandelenth:
So I am using this rom for some time now and decided I wanted to encrypt my /data partition in mid November. I now wanted to update my phone to the 20160102 build, but I have not been able to flash it, because /data cannot be mounted. At first I was surprised by that, because I thought the flash would not need to touch the /data partition, but it seems like it does.

I tried several things including trying to mount it manually via vdc and mount, but it turns out TWRP seems to have no vdc. I am not really familiar with the way android handles system encryption, so maybe I am missing something here. Do you guys have any experience with an encrypted Galaxy Nexus and flashing it? I am stuck.
[Samsung Galaxy Nexus] breversa:
With Android 4.4.4/CM11, my phone would get unusably slow/unresponsive proportionally to the filling of the /data partition (ext4). Using Trimmer/fstrim helped (sometimes greatly !), but never totally corrected.

Switching to F2FS solves the problem though (using this tool http://xdaforums.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702).

Could there be a link between those phenomenons ?
[Samsung Galaxy Nexus] sddfdds:
you can sideload it
[Samsung Galaxy Nexus] bandelenth:
Oh, yes, thank you. I totally forgot about that. Looks good so far.
[Samsung Galaxy Nexus] bamtan2:
This is an interesting observation. To the best of my knowledge, if the EMMC performs better with more free space, we can simply partition /data to be smaller, thus FORCING free space. I would do this if we can prove it helps...
[Samsung Galaxy Nexus] hgmichna:
Free space in data partition

Did you mean bigger?

Oh, now I understand what you mean. Took me a moment. You want to leave some space completely unused, so the hardware has guaranteed space for remapping.

But for now it would be good enough just to tell people not to fill it up.

Is it possible that the behavior varies from phone to phone, depending on EMMC wear or on past use, fragmentation, or anything like that?
[Samsung Galaxy Nexus] norton75:
Yes obvioulsy this could be related to EMMC wear, but i think all GNEX currently in circulation are not so new.

This is my direct experience: when /data free space is low phone suffers heavy lags and sometimes completely freeze for about a second, then brightness go to the maximum for 1/10 sec. and then reboot. In one case, when /data was nearly full, the phone didn't even completed the boot, going into bootloop with the same symptoms (1 sec of freeze and then 1/10 sec max bright and then reboot).

F2FS simply reduce this behaviour respect to EXT4 because with EXT4, also with good free space, after some weeks the phone become very slow (I suppose due to fragmentation) and this don't happen with F2FS, but F2FS don't solve the problem when /sdata is near full.

I assume kernel go in panic due to impossibility to access EMMC in this particular condition; i don't know in detail android kernel but i think one workaround could be to work on I/O EMMC timeout in order to allow more time to wait for access before to reboot, but i'm not sure if this could be possible.

In general in my opinion the only big limit of this phone is a very poor implementation of EMMC management or very low quality EMMC chip, the real source of all problems. I know several people who suffered complete bricking of the phone due to EMMC death.
[Samsung Galaxy Nexus] playitlouder:
These EMMCs don't really die I don't think.

They get corrupted and go read only, or shredd the file system table though.

There is an official fix from Google implemented in the stock Gnex Kernel. It overwrites some sectors on boot, if they get damaged.

But this happens while the kernel starts up, I don't think this is thats really ideal, because the phone could crash, the battery can get pulled etc. It is also probably not executed, while you do critical writes to the chip (in recovery mode).

I messaged [MENTION=4141005]Lanchon[/MENTION] who worked on fixing trim and the Superbrick bug on the S2/S3. Our Gnex the same chip. He tried to save a Gnex a while back, but was not successful.
[Samsung Galaxy Nexus] norton75:
Yes I know about this google fix, that was applied only on specific revision ID of the EMMCs. Anyway I think it is not directly related with the increasing access delay of the EMMC when the partition is nearly full. I remember this happened to me also with stock kernel and also when the phone was some months old (now it is near 4 year old on all days usage) so I suppose not directly related with wear rather than specific implementation of the EMMC internal management or something that relies under the filesystem partition level; for this reason I think it cannot be solved on kernel level and only workarounds can be applied.

I have another readonly locked gnex (with brocken screen and stuck on "Google" start screen) can could be used for "experiments" on EMMC; it can be turned on in recovery and accessed via usb adb, but all writing commands return ok and nothing is actually wrote
[Samsung Galaxy Nexus] playitlouder:
I think we should open a new Thread for this, but after some digging I found that desoldering the Chips, and updating their firmwares will bring them back to life. http://forum.gsmhosting.com/vbb/f67...ead-emmc-kmvyl000lm-b503-first-world-1939201/

The question is: Can we update the Firmware, while the chip is still soldered to the board? Is there anything for firmware updating in the Kernel [MENTION=2633638]Ziyan[/MENTION]?
[Samsung Galaxy Nexus] norton75:
Yes I agree, anyway I think is important that people are aware of this because many of the problems that someone often reports as rom issue are related to EMMC issue instead.

Returning to version cm-12.1-20160102, the only issue I noticed till now was a single soft reset (uptime was not reset) while on and connected to USB; after the soft reset it was reported no sim inserted and only emergency call available but trying to call the phone it regularly rings and make calls. Already happened with previous versions; the only way to recover the wrong indication is to reboot the phone
[Samsung Galaxy Nexus] hgmichna:
Writing Flash

I have never heard of flash memory that does not have internal spare memory over and above its nominal size, for the reason you describe.

If it were not like that, it would be a suicide design.
[Samsung Galaxy Nexus] Lanchon:
i dont understand that link. i cant access attachments. is the software available or is it a for-sell thing? is the source available? can you repost the stuff here if you have access?

---------- Post added at 01:13 PM ---------- Previous post was at 01:06 PM ----------

btw, they might not be able to do it because they probably use JTAG to flash firmware. but yes, fixes and firmware upgrades CAN be done just by booting software of the phone. samsung has such software as confirmed by google engineers, but they won't release it. (there are complications with wiped phones and signed bootloaders and EFS partition, i wont deny it.) so all those dead S2s and Gnexes are dead courtesy of samsung that made ****ty emmcs and then didnt release the fixes. what to do about this? boycott samsung of course. forever if possible.
[Samsung Galaxy Nexus] playitlouder:
I've been to this site multiple times, they seem to have a lot of fixes, hacks and such for numerous devices.

Somehow they often obtain schematics and such (found fixes there for not working iPhone backlights etc.).

But I never created an account on that site.

The software described on the thread is for a JTAG phone flash box. They stuff they used to sim unlock old nokias etc. (I don't own one of these).

The Software for this box however is publicly available on their website here http://easy-jtag.com/?page_id=1349
[Samsung Galaxy Nexus] norton75:
Thank you Lanchon for the detailed explanation, very useful to better understand.

The issue was related to some application that won't start, causing autonomous selfreboot of the rom if tried to launch. Me and other users suffered this kind of behaviour and I found seemed to be related to nearly full /data partition. (F2FS filesystem) It seems that the access to EMMC in this particular situation is extremely slow or even denied, causing a kernel panic, probably for the reason you explained.

What do you think about F2FS filesystem? Can be helpful to keep under control WA effect in your opinion?

Regarding the other Gnex I own (locked in "readonly EMMC" on the "Google" startscreen) I tried to let it some hours on but nothing happened except one time when the bootanimation appeared but no further progress. We can continue the discussion on this specific issue in separated thread if you agree
[Samsung Galaxy Nexus] Lanchon:
you should ALWAYS have min 20% free space. that's it. if you don't bad things happen.

F2FS provides less guaranties than ext4. some programs will corrupt data if the phone hangs on F2FS but not on ext4. this is mostly a bug in those programs, not F2FS, but it bites all the same. F2FS is in its infancy and not as safe as ext4 IMHO. F2FS is performance-wise a better FS to run on your emmcs if performance is your goal. F2FS properly trims the emmc of course (if running a capable kernel).

locked emmc: put it in the trash bin.

---------- Post added at 03:14 PM ---------- Previous post was at 03:13 PM ----------

yep. its proprietary software for a proprietary OS that i certainly don't run. no source code. there is nothing to be learned there, so i wont look into that any further.
[Samsung Galaxy Nexus] Ziyan:
New build up with ZCache and LZ4-backed zRAM enabled and set up according to Google's guide. I also enabled WITH_DEXPREOPT_BOOT_IMG_ONLY - this increases the initial boot and update time by ~2 mins, but saves ~45 mb on /system, resulting in enough free space to install the nano gapps, to which the CM wiki point to by default. Report back if memory management is worse, the same, or better than on the previous build :)

One thing I'm not sure about is swappiness - those who want to experiment can change it from 60 to 40 using an app like Kernel Adiutor, but only after checking how it works with 60, to see if it's any better with 40 ;)

EDIT: also experiment with the i/o read ahead value - the default 128 kb might be a bit low, I'm experimenting to see if 256 kb is any better.

EDIT 2: lastly, feel free to experiment with the zram size as well - the ideal size is somewhere between 160 and 350 megabytes, the values aren't final yet.
[Samsung Galaxy Nexus] blystad:
To what extent would updated EGL blobs help?

My company is working on trying to get access to PVR SGX sources from TI, since were failing virtual display related CTS tests (due to the display being in BGRA instead of RGBA, or something), and our main priority (should we get access to the sources) is getting that fixed. It should be fixed in DDK 1.12 and newer.

Getting access to the sources is easier said then done though...Even though we have a CDDS agreement, the OMAP4 team is disbanded, and the contract with Imgtec might've expired...but we're using our TI contacts for what they're worth.

If we get that working I might be able to share the blobs from our device.
[Samsung Galaxy Nexus] Ziyan:
With DDK 1.12, we wouldn't need to patch the platform to add back support the old CPU screenshot path (to avoid artifacts on screenshots, rotation animation and screen off animation), add back the workaround for BUG_10194508 on Marshmallow (the display surface format workaround you're talking about, which got removed from M), and we wouldn't have to hack up gralloc to support cursor layers (which isn't only used for cursors, but also for 'show touches', and possibly some other minor things in dev settings). And quite possibly it would give us a nice graphics performance boost, since the old DDK 1.9 we're all using was designed for Android 4.1 (we noticed a slight boost after switching from DDK 1.8 to 1.9 as well). So yeah, you'd pretty much save the future of OMAP4.

TI released DDK 1.12 for their jacinto6 platform (source) - sadly, that uses an SGX544, not an SGX540 like us, but I'm quite sure it wouldn't take much time for them to compile it for SGX540 (they should share the same source, it's just a matter of build option).