yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zzpianoman:
Found something interesting with the Camera.

Apparently starting with Lollipop, it is required that all binaries be compiled as PIE or Position Independent Executables and our fRom binary, which I believe is responsible for camera calibration, is not compiled as such and thus causes an error when the system tries to execute it.

root@toro:/ # fRom
error: only position independent executables (PIE) are supported.

So I decided to patch /bin/linker to ignore non-PIE compiled binaries and allow their execution so the fRom service is loaded at startup.

root@toro:/ # fRom
error: only position independent executables (PIE) are supported.

usage: fRom [ -v | --verbose ] -f file.bin -d /dev/mtd0
fRom -h | --help

-h | --help Show this help message
-v | --verbose Show progress reports
-w | --write Write file to the flash memory device
-c | --count Number bytes to read from device
-f | --filename File saved onto flash or copped from it, depends on --write option
-d | --device Flash device path (e.g. /dev/mtd0, /dev/mtd1, etc.)
-k | --calheader Add calibration dcc header when reading calibration
data from flash memory, valid only when reading
-o | --offset Start offset at flash device when writing
-x | --extract Extract DCC files from flash memory

Now when I try to record video with the camcorder, it is not perfect, but a LOT more of the video is in the frame and it definitely looks much better. Also, switching from the rear camera to the front camera is much faster. This does not however fix the issue of photos not saving - or any of the barcode scanner apps that use the camera API, but it's a start.

I'll include my patched linker so you can test for yourself:

make a backup of the original version first!

Extract linker from linker.tar

cp linker /system/bin/linker
chmod 755 /system/bin/linker
[Samsung Galaxy Nexus] joao7458:
what are the best gapps?
[Samsung Galaxy Nexus] demoniak1:
The new build -- cm-12-20141216-UNOFFICIAL-maguro.zip works very smooth.

But...

1. smart lock based on places does'nt work, while the previous build works.

It works at home , but at my office it doesn't work. I think it's maybe my network problem.

2. An android 5.0 feature "ambiet display" is missing.
[Samsung Galaxy Nexus] AllAboutTech:
the only probl with the lates build is that after screen is off you can't open the scree.

it only opens if you connect the charger..
[Samsung Galaxy Nexus] Hemidroids:
I used the one form the 5.0 AOSP wee stock ROM

http://xdaforums.com/galaxy-nexus/development/rom-aosp-lollipop-wee-stock-t2971379

Worked fine.
[Samsung Galaxy Nexus] revanmj:
Works fine here.
[Samsung Galaxy Nexus] fink42:
I am still having problems sending long SMS, so I don't think so ;)
[Samsung Galaxy Nexus] foosion:
Just dirty flash or is it better to wipe system & cache?
[Samsung Galaxy Nexus] XneofuX:
I think you just have to flash it ... when the phone doesn't start, you can still wipe and flash ^^ For my part, i usually wipe the cache ;)
[Samsung Galaxy Nexus] netreign:
insufficient storage space available in system partition, when i flash gapps! flashing other gapps, like a gapps-lp-20141109-signed.zip google account not able....
[Samsung Galaxy Nexus] foosion:
It works if you dirty flash. I was wondering if there's any advantage to wiping the cache or other.

---------- Post added at 11:19 AM ---------- Previous post was at 11:16 AM ----------

For my initial flash of CM12, I wiped system, cache and dalvik cache first,then flashed CM12 and the gapps in the OP. I didn't have a problem.
[Samsung Galaxy Nexus] supermax:
torch

Hello everybody

very good rom but I have a problem in activating torch.

Is only my problem?
[Samsung Galaxy Nexus] Reptilez_DK:
It is a known issue. :)
[Samsung Galaxy Nexus] danijaan:
I clean inatalled it yesterday. Flashing went smooth. However, apps randomly crashing as soon as I open them like AppGratis, Facebook, Messenger, Reddit Sync Any idea?
[Samsung Galaxy Nexus] Suxsem:
Great, thanks!
[Samsung Galaxy Nexus] Hemidroids:
I was really digging this ROM untill I came off wifi.

I had no data connection and everytime I tried to get to the section to change the APN it crashed.

Dec 16 version
[Samsung Galaxy Nexus] Reptilez_DK:
Logcat all the things. ;)
[Samsung Galaxy Nexus] rohit310:
Great

Great work done. I m using latest build and till now its smoothest than previous build till so far. Allover for me a daily driver. Thanks for the support.

Any body knows if any third party app for playing videos( i know [MENTION=2633638]Ziyan[/MENTION] is working hard for fix this), if not then also fine for me.

Again thanks [MENTION=2633638]Ziyan[/MENTION].
[Samsung Galaxy Nexus] sagara.sandaru:
Playing videos? Then you can use MXPlayer.
[Samsung Galaxy Nexus] Childe89:
Everything ok with latest 11/01 build, flashed over previous one, with cache and dalvik wipe. Encountered no problems so far.

I have CPU Max Screen Off at 350MHz, checked through Trickster Mod, it might be bug in your kernel managing app...

By the way, little offtopic question - friend wants his Gnex flashed, but he uses video a lot - LP has purple band, KK video is choppy, which CM for maguro has no problems with video/camera? Latest 10.2.1 Stable?
[Samsung Galaxy Nexus] skyleth:
Half an hour installing Facebook is quite a lot :eek: so I've checked in the Play Store, it didn't give any error, but for the Play Store it was not installed. Rebooted the phone into TWRP and wipe dalvik + cache, and Facebook is now installed :victory:

I've noticed a bug, I have LiveDisplay activated, in automatic mode, and every time it has to change from day to night (around 18:00) the phone reboots itself. If I turn the automatic off and change it manually, it doesn't reboot.
[Samsung Galaxy Nexus] jassim007:
OmniROM KK with fancy kernel (not franco), has no problems at all even for video recording. One thing, you also need to flash that old version of ducati for better video playback.
[Samsung Galaxy Nexus] ed10vi:
[MENTION=2633638]Ziyan[/MENTION] What about this bug?

it happends when you decrease the green gamma
[Samsung Galaxy Nexus] opticyclic:
Is Ducati a codec?

Do you have a link to the one you are talking about?
[Samsung Galaxy Nexus] jassim007:
http://xdaforums.com/galaxy-nexus/general/how-to-to-solve-hw-video-playback-t2559138
[Samsung Galaxy Nexus] sddfdds:
Tried this...for me, it just sits on installing... for like 10-15 minutes and then soft reboots.
[Samsung Galaxy Nexus] netreign:
me too...
[Samsung Galaxy Nexus] breversa:
Hi all,

I installed CM12.1 (cm-12.1-20151101-UNOFFICIAL-maguro.zip), but I couldn't restore (using Titanium Backup) or install some apk, that would fail with a laconic "Installed failed" message.

Digging deeper, I tried the following :

su
pm install app.apk
Failure : [INSTALL_FAILED_INVALID_URI]

I searched the web and found this : https://jira.cyanogenmod.org/browse/NIGHTLIES-1803

so I did :

su
pm set-install-location 1
1[internal]

… and TADA, I can now install those apps.

Hope this helps !

I then tried to revert to the automatic install location, but got the following :

su
pm set-install-location 0
Error: java.lang.SecurityException: Package android does not belong to 2000

pm set-install-location 1
1[internal]
[Samsung Galaxy Nexus] Baletka:
I can't find anything about this, is there a reason ambient display is not available in these builds?
[Samsung Galaxy Nexus] breversa:
Anyone else experiencing heavy battery drain ?

Here are some of my findings :

* After a battery calibration (full/overcharge, full deplete 'til phone won't start again, full/overcharge again) and using Battery Monitor Widget (BMW), I noticed that my 1750mAh battery has aged to about about 1050 to 1450mAh (I'll try and recalibrate to achieve a more precise result). That's just to compare with a new battery.

* Battery stats show that screen-on gobbles battery like crazy, around -1% every 2 minutes ! I use dark/black themes UI whenever I can, though my wallpaper had lots of blue. I have since switched to a black/dark grey wallpaper instead to see if that changes anything.

* Other than screen-on (about 50% of battery consumption), BMW tells me that the next culprit is the "Android System" (around ¼ of screen-on = 9%). OS Monitor tells me that even when idle (but with screen on, of course), Android System uses about 7% of CPU work, and the process itself is system_server (next one is ksmd).

* Setting the governor to "hotplug" (using Kernel Aduitor, for example) spams logcat with "E: Tuna PowerHAL : Error writing to /sys/devices/system/cpu/cpufreq" (but from what I know, that's an expected behavior), but seems to reduce battery consumption with screen-on.

Any idea on what could be wrong with system_server, or what further tests I could do to pintpoint the issue ?
[Samsung Galaxy Nexus] siealex:
It's normal for 5.1, downgrade to 4.4 and you won't see this drain.
[Samsung Galaxy Nexus] breversa:
Why is it "normal" ?

I flashed Full_Auto_R25v2_Ak2.zip (from http://xdaforums.com/galaxy-nexus/development/lollipop-kernel-fullauto-r1-aosp-cm-t2994371), and said battery drain seems to be much lower (need more testing though).

This kernel also lowers the system_server "idle" CPU load to 3-4% rather than 7-8%.
[Samsung Galaxy Nexus] Childe89:
Well it might be the famous Lollipop "Mobile radio active" bug:

"When mobile data (2G or 3G) is switched on, all the internet apps continue to consume battery and keep the mobile data active unless they are force stopped. On kitkat, this didn't happen because apps stopped using mobile data whenever their transaction was over. But here in lollipop, they don't seem to stop ever and cause a huge battery drain.

Please look into this.. It's still present in 5.1 (aosp and all custom roms)."

Citated from here: https://code.google.com/p/android/issues/detail?id=165558
[Samsung Galaxy Nexus] Hoodahottie:
I updated to the latest release from Kitkat. I have an error with internet connection. Only Browser connects to websites.

All other apps keep loading forever. Firefox, Opera, Dolphin browsers + all network apps never complete connections. Is this a known bug?

Should I flash this ROM again?
[Samsung Galaxy Nexus] Childe89:
Updated from KitKat - dirty flashed without wipe? That might be the problem. Try at least wiping cache and Dalvik cache in recovery.

If problem stays, do your backups, wipe everything and do a clean flash.
[Samsung Galaxy Nexus] Hoodahottie:
I wiped everything in the recovery before flashing. There was no OS, cache or Dalvik cache when I flashed.
[Samsung Galaxy Nexus] Childe89:
In that case you should try to create your internet access points manually - deleting current ones, and create custom according to your network operator.
[Samsung Galaxy Nexus] breversa:
You might want to check your date and time.

If they are too much off, download might be severly impaired.

---------- Post added at 01:31 ---------- Previous post was at 01:24 ----------

Thank you for that info ; I was not aware of it (but flashing Full_Auto_R25v2_Ak2.zip did reduce the battery drain by a bit).

At first, I thought I was not affected, as it's "Android system" and not "Cell data" that took most of the CPU. What's more, screen-on is still superior.

However, by checking a bit more carefully in the processes' details, I can see very long times of "Active GSM cell", so I might be affected anyway.

I installed that Xposed module (http://repo.xposed.info/module/com.pyler.mobileradioactivefix) that supposedly fixes that problem. Let's see what it does…
[Samsung Galaxy Nexus] A_A_M_I_R:
Updated to 5.1.1, things seem to be working fine. I miss the network and location modes in KitKat CyanogenMod :(

Also, I noticed this bug when you turn off the 'force high end graphics' in dev options the notification bar starts acting up and only shows 1 notification (the top one).

Update: So just like everyone else, I'm also being subjected to this mobile radio bug so hopefully there's a somewhat stable M build soon I can move to! :D
[Samsung Galaxy Nexus] Polooo2:
A total noob question. When switching from stock to this ROM I did a full wipe with eveything.

Now if I want to switch to the most recent version of this ROM I have to wipe cache and dalvik and install the ROM from recovery. Will this rest my device and delete my apps/data/...?
[Samsung Galaxy Nexus] Childe89:
Don´t worry, just flash new version from recovery and wipe cache and dalvik, your apps/ personal data will not disappear.
[Samsung Galaxy Nexus] BenG7:
Hi kenshin33

I renamed /system/lib/libjni_latinime.so -> /system/lib/libjni_latinimegoogle.so

but for this step /system/addon.d/*-gapps.sh

I have 2 files, 30-gapps.sh and 70-gapps.sh, and in both of them, latinime.so is already replaced with latinimegoogle.so

yet when I reboot, AOSP gestures still don't work: AOSP keyboard crashes

can you please clarify the edits that need to be made?

[EDIT] Found fix (thanks MZO!) here http://xdaforums.com/android/development/fix-cm-aosp-keyboard-swipe-fix-zip-t3182789

for those this may help.

Thanks

beng
[Samsung Galaxy Nexus] norton75:
Tried new 11/01 release for some days: i found it a bit slower than 09/27, with some sporadic lags not only on graphical effects but also on audio, for example listening mp3s. Tested both CFQ and BFQ schedulers but no significant differences. I also confirm sometimes videos with audio out of sync.

Switched back to 09/27 release, till now the best for me
[Samsung Galaxy Nexus] Saberfang:
It's really nice to see continued development for this phone. I tried out of curiosity to see what would happen if I installed CM 12.1 and in my opinion is still not here yet. The animation are pretty fluid and the system seem to handle itself quite well with a clean install but as soon as I tried to get back my apps I got problems. The great monster app, nightmare of all batteries, facebook couldn't install. Sure its not that big of a deal but if I got a problem there I'm incline to think there could issue with more apps of the play store.

I roll back to cm 11 still keep the good work, I hope you can figure out this and more problems. Cheers.
[Samsung Galaxy Nexus] skyleth:
Facebook app is a great pile of s**t. Too bad optimized. If you need Facebook notifications you should stick with the lite version. Otherwise, the webpage is way better

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] Saberfang:
I agree with you still the point is not that. It just get stuck in the installation process and crash to an unknown error code. I don't think its an app issue at this point but a problem between the play store and the build, its just happened to be that app.
[Samsung Galaxy Nexus] mimox:
Did anyone notice any problems with video playback on latest 12.1 build? Recorded video plays but looks distorted.
[Samsung Galaxy Nexus] RaduOv:
How can I modify the SMS center number in this ROM ? Thanks !
[Samsung Galaxy Nexus] matorola:
http://wiki.cyanogenmod.org/w/SMSC_Updates
[Samsung Galaxy Nexus] janstetka:
Was on 29/08/15 gone back to 4.4.4. Main problems:

- Slow downs, due to low memory? Not fair to blame the ROM for all of this, as some is down to resource hungry apps, as some are still slow on 4.4.4.

- Black screen when receiving calls

- Rendering of web pages incomplete, particularly meetup.com, in default browser

- The straw that broke the camels back, was that the lock screen stopped showing notifications correctly & lost background image

Will miss the extra screen space on lollipop
[Samsung Galaxy Nexus] VBTheory:
So lately I had my Galaxy Nexus i9250 plugged in my PC just charging, then when I received a message on it and tried to unlock it, it took a little more time. Usually when it does that, it shuts off and restarts, only this time it stayed on the Google logo for hours.

The natural thing I would do was to boot into recovery and clean cache and dalvik, so I restarted my phone into recovery and it gave me the twrp logo but stayed there for hours again.

Here are the other things I tried:

- I tried flashing stock using Odin3, it always aborts on system.img

- I tried booting into fastboot and cleaned cache and data

- I tried using fastboot to flash cwm and twrp but it didn't work

Please help me get my phone back to life
[Samsung Galaxy Nexus] nikodr:
Most probably your nand chip is dead or dying.You could temporarly install an os and could in some time boot,but if it fails on odin i would smell a dying nand.
[Samsung Galaxy Nexus] ardeus_ua:
First CM13 builds started to rolling out for some devices. Anticipating new CM13 build from [MENTION=2633638]Ziyan[/MENTION]
[Samsung Galaxy Nexus] hgmichna:
Not enough RAM

Since Android and the Google apps keep growing, the problem with too little RAM on the Galaxy Nexus will also grow. With CM 12.1 it is already problematic to run Google Maps Navigation alone or, I hear, Facebook. It can only get worse with CM 13.

A way out could be some swap space, if you accept a little slowness, but the kernel does not support swapping.

It would be nice to see Android 6 run on the GNex, but what use would it be if you could only run one small app at a time?
[Samsung Galaxy Nexus] ardeus_ua:
I don't use FB app. It's too big and uses just enormous amount of RAM to be just a website shell. And GMaps navigation replaced with Sygic and iGo. So, basically, I'm satisfied with current builds of CM by [MENTION=2633638]Ziyan[/MENTION].

I have tried zMod 6.0 but on that early stage I miss some features from CM and thats why reverted to CM.

Anyway, I think all GNex CM users would be glad to use a newer version.
[Samsung Galaxy Nexus] skyleth:
There are new phones with even lower ram (I found yesterday a crappy zte with only 512mb). The problem probably is not only the amount, but the speed and optimizations

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] Noeljunior:
I had two maguros that died. One of them become some kind of ROM - literally read-only memory. I used all kinds of flashing (more than the ones said in this topic) and still the same state (Zyian had a similar problem). The other one can be flashed but it reboots some seconds after boot. I found out that if I remove the back camera (removed the flat cable) it can be booted for a bit more but eventually it reboots. Logs shows nothing as it reboots before writing or output anything.

My primary maguro is running since 10/2011 full time, a lot of flashes, some swap file used, etc. I don't know how much time it can still be with us but as these devices are too sensitive to nand I would recommend not to use swap or any other nand intensive things. And don't forget that the nand of this phone is a bit more fast than the old 3.1/2 floppy disk. Running swap in this nand can be worst than not using...

Obviously it depend in many factor. The best is to try and see. Still, I would not recommend trying it.
[Samsung Galaxy Nexus] scorpeeon:
Seeing how much problem low RAM can mean, and considering growing app and OS sizes (though Android itself is constantly optimized for lower-end devices as well, so no real complaints there) and no option on mobile to use swap - I pretty much decided long time ago that my next phone will have at least 4GB RAM. There's no Nexus phone with that, so I'm still waiting. Meanwhile powerful 14 nm socs like Snapdragon 820 appearing won't hurt as well, so most likely next year will be the year to upgrade for me :)
[Samsung Galaxy Nexus] hgmichna:
I feel with you. However, you might well be happy with less than 4 GB. Consider that Android and the Google apps occupy the better part of one Gigabyte, so the remaining bit is too little for very big apps. 2 GB already at least triple the free RAM space for apps. I have a few phones with 2 GB in my vicinity and can say that currently 2 GB is plenty.

I see though that RAM demand may well grow rapidly. My primary phone, a OnePlus One, has 3 GB RAM, and I am very happy with that. I have high hopes that 3 GB will still be enough when this phone bites the dust or gets relegated to a secondary role. The one after that will probably have at least 4 GB, maybe 6 GB, and must be a 64 bit system. But currently I still think that 2 GB are plenty.
[Samsung Galaxy Nexus] scorpeeon:
Yeah i know, at this level when the RAM is full all the time, even a few 100 MBs of RAM can make a huge difference. I had a device with 1GB available RAM (not ~700MB we have with GN) and even there I hardly saw any memory issues. I agree that 2GB is enough for most usage now, I have an N7 2013 and never really had any RAM issues with it, it's still extremely snappy, maybe even snappier than when it came out 2 years ago due to Android optimizations through 6.0. >=4GB is really mostly just a way to make it more future-proof. So while 2GBs of RAM would really be enough right now, I wouldn't buy a phone like that because I know in a few years it wouldn't be always enough.

Phones quickly got from 512MB (2010 era) of RAM through 1GB to 2GB (back in 2012), and then they just stopped at 2GB for many years and It's only recently that phones with 3 or 4 GB RAM started to appear. One could say technology's progression slowed down (which is true) but demand for performance has also slowed down after reaching a certain level, once things got "good enough". So point is because of this slowing down, I expect a phone with 4GB RAM not to have many RAM issues for at least like 5 years or so.
[Samsung Galaxy Nexus] RossPierreDaLaThor:
build 11/01 -- microphone and speaker muted while trying to call

ROM is pretty nice except it's (at least for me) impossible to call / receive calls. No mic and no speaker. Complete silence on both ends.
[Samsung Galaxy Nexus] :
It seems something is wrong in your installation. I haven't never problems in doing calls with this rom. Please check.
[Samsung Galaxy Nexus] RossPierreDaLaThor:
I've rebooted my phone and mic / speaker are working again. I will check how it goes and report if that problem appears again.
[Samsung Galaxy Nexus] m4heshd:
Happy with everything

This rom is just amazing. Thank you so much for doing this for us. First i was so scared of flashing this but after this is rocking.

Few notes:

You only can install the pico package of gapps. Else it'll say insufficient space on system partition.

And there's a slight bug. I hear a cracking noise from the main speaker once in a while. Usually when i press the home button. Nothing more.

Also, Can i have all the features of google camera back? Pano, Sphere & Lens Blur.

Thank you so much again for this.
[Samsung Galaxy Nexus] VBTheory:
Do you think there is any way I can mend it or get it replaced?
[Samsung Galaxy Nexus] skyleth:
Hey can we expect this one to make it to the official builds? I know it's just a matter of naming, but would be great if we could get the updates directly by ota

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] konnarides:
Ziyan,, will we be seeing 6.0 on gnexus that can run without maxing out ram ?
[Samsung Galaxy Nexus] Ziyan:
Yes, we're just waiting for Hashcode to get this fixed and merged to CM's repos - for some reason, this is breaking a Kindle device, but all others work fine with it.

We're working on it - it's getting harder and harder to keep the RAM usage controlled :mad:
[Samsung Galaxy Nexus] hgmichna:
I think you want a swapfile of a couple hundred Megabytes. Without it, you will keep running into problems.
[Samsung Galaxy Nexus] konnarides:
Ziyan,, in your opinion which is the lollipop Rom to go with on the gnexus ?
[Samsung Galaxy Nexus] bamtan2:
I don't think swap helps when it is stored on slow old NAND. But I can confirm from using [MENTION=4608636]bsmitty83[/MENTION] older kernels that ZRAM works! It trades your battery life (CPU time spend encoding/decoding RAM) for more free RAM. If I remember correctly from testing, my zram swap was set to ~180MB and used ~80MB of RAM, thus saving ~100MB of RAM.

Note that if you try his latest kernel, it has ZRAM enabled by default, and a bug prevents you from changing the settings from the default size he chose. So you need to use an older kernel where ZRAM is off by default.