yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] YouKnowNothingJohn:
[MENTION=7046460]Regina Rainbow[/MENTION]

No I just installed it manually as this should result in the same behaviour, correct? The scripts in the addon.d. folder are executed automatically on a flash, correct? If not please correct me where I make wrong assumptions.

Could you help me with the script I posted as I would like to understand a bit better how I can make it work. Looking at it I feel that it should work as is but apparently there is something I'm missing.
[Samsung Galaxy Nexus] playitlouder:
Upstream Bug. :D
[Samsung Galaxy Nexus] devil_tear:
[MENTION=4038245]playitlouder[/MENTION] so it is a known bug?
[Samsung Galaxy Nexus] playitlouder:
This bug also happens on other devices.

It has nothing to do with the Galaxy Nexus, and it's not the maintainers job to fix it :)
[Samsung Galaxy Nexus] devil_tear:
Yup... I know what upstream bug means... :) didn't know that since this is the first time i try cm12, my nexus 6p crapped out and now it is on it's way to repairs... And in cm13 everything was perfect... I am actually surprised of how smooth cm12 on the nexus and I know that it is mostly because of the amazing kernel that Ziyan baked for this device... Another thing I noticed is that Skype really kills the battery, for some reason it keeps running in background and it is the main battery drainer on my phone... I uninstalled it and I gained 2 hours of up time and one hour of screen on time... I do not think that it is ROM related, I just wanted to tell people about my experience... :)
[Samsung Galaxy Nexus] nikodr:
Use greenify with root,i have skype plus many many other apps and never had deep sleep problems.
[Samsung Galaxy Nexus] devil_tear:
[MENTION=2744041]nikodr[/MENTION] it's not a deep sleep issue.. I checked with Trickster Mod, the phone deep sleeps... It's something else... And I just can't figure out what! I killed the app and regardless of how many times I would kill it I would still find it there killing my battery... Greenify works well, I know, but to be honest I didn't use it for a while on this device and it really doesn't make a big difference, at least for me...
[Samsung Galaxy Nexus] :
Skype in normal circumstances should be very battery friendly. The app itself is very heavy and bloated but also relies on GCM for notifications so should not use any battery in standby. It also does not run any background services by default (unless you specifically enable the constant notification option in its settings).
[Samsung Galaxy Nexus] devil_tear:
Well I didn't enable any strange settings and I didn't do anything that I usually don't do with it.. I will install it again and see how it goes, I'll check the settings and I will double check the deep sleep again... I might be missing something...
[Samsung Galaxy Nexus] eclipse6220:
Great Rom, incredible Job!!!

One question? It´s essential to install cyanogen recovery?

What is the best recovery and the best recovery configuration?
[Samsung Galaxy Nexus] hgmichna:
Cyanogen vs. TWRP recovery

Only with the Cyanogen recovery you can use the semi-automatic updater that is built into CyanogenMod. I use that for convenience.

When I need something else, like a complete backup, I install the TWRP recovery from TWRP Manager. Afterwards I install the Cyanogen recovery again, using the TWRP recovery, which can flash .IMG files directly.

The entire procedure can be done without a computer.
[Samsung Galaxy Nexus] :
That's not correct for me: I'm using twrp with all my devices together with the you called semi-automatic updater built in cm. No problems at all.
[Samsung Galaxy Nexus] hgmichna:
No automatic update with CyanogenMod updater through TWRP

Oops, this surprises me. Last I tried, it did not work.

Do you use the lastest TWRP version, twrp-2.8.7.0-maguro.img? I could bet I tried that too. Perhaps something has changed in CyanogenMod. Just a moment—I will try again.

No, it still does not work on this phone. After I start the automatic update, I get the following TWRP error:

E:Zip file is corrupt!

E:Error installing ZIP file '@/cache/recovery/block.map

Done processing script file

So I flash the Cyanogen recovery again, ask for the update, and the update process runs automatically, after choosing, downloading, and confirming the desired update, as it should be. The phone automatically boots into the recovery, does the update, and boots back into Android/CyanogenMod.

Just a moment again, perhaps this is only because I had the setting to auto-update the recovery enabled. I just tried again with that setting off, but the result is the same error message. On my phones (tested two) TWRP never works with the CM updater.
[Samsung Galaxy Nexus] :
Yep, 2.8.7.0 with maguro, 2.8.7.0 with manta and grouper too, 3.0 with mako and bacon - all are updating fine directly via built-in cm updater. I have no clue what's different and why they are working for me, sorry.

Btw Happy Easter to all of you!
[Samsung Galaxy Nexus] devil_tear:
I can confirm that TWRP is working fine with the Cyanogen Updater... Never had problems
[Samsung Galaxy Nexus] st.Antony:
There is an error in camera app.

Anybody got the same? (Start camera app, switch to video record, make a shot, press home, then open camera app again. On latest builds i can hear a sound from phone like "tick".)
[Samsung Galaxy Nexus] YouKnowNothingJohn:
You are correct, I can recreate the error with the steps you mentioned!
[Samsung Galaxy Nexus] bamtan2:
The good news is: I cannot reproduce this on March 10 build! :)
[Samsung Galaxy Nexus] mrcdipauli:
Hi, I'm using it daily and it is good. No crashes, no reboots,quite smooth. I have only a problem a big problem, I cannot calibrate battery. The batteryis new, I rootedthe phone, I used battery calibration but I can't do anything, it goes from 100% to 55% then immediately to 15% and then it dies. Anyone else has this problem?

Cheers

Marco
[Samsung Galaxy Nexus] YouKnowNothingJohn:
[MENTION=6925607]mrcdipauli[/MENTION]

I don't have the exact same problem but my Nexus sometimes shuts down when it's at 10~15% but this usually happens under load so it probably has to do with a lower voltage due to the load.
[Samsung Galaxy Nexus] hgmichna:
Bad batteries

Looks like a bad battery to me. Most "original" batteries you buy on Amazon or elsewhere are Chinese fakes with a very short life span.

Buy Anker or some other branded battery, just not Samsung.
[Samsung Galaxy Nexus] YouKnowNothingJohn:
I'm still trying to get my addon.d script working :(

I want to use the script posted below. Made some adjustments and tried flashing the latest nightly to see if the apps were removed. They weren't. I did not see any echos during flashing so I can't say for sure if it's run properly. I do know that my SU backup script works properly so the bash scripts are run.

Can anybody with some bash knowledge help me so people can use this script for their own Nexus device?

File 80-autoclean.sh placed in /system/addon.d/ with permission set -rwxr-xr-x

#!/sbin/sh
#
# /system/addon.d/80-autoclean.sh
#

. /tmp/backuptool.functions

list_files() {
cat <<EOF
AudioFX
BackupRestoreConfirmation
BasicDreams
Browser
CMAccount
CMBugReport
Calendar
CyanogenSetupWizard
DeskClock
Eleven
Email
Exchange2
Galaxy4
HTMLViewer
HoloSpiralWallpaper
LatinIME
LiveWallpapers
LiveWallpapersPicker
LockClock
NoiseField
PhaseBeam
PhotoPhase
PhotoTable
Tag
Terminal
ThemeChooser
ThemesProvider
UserDictionaryProvider
VisualizationWallpapers
VpnDialogs
EOF
}

case "$1" in
backup)
# Stub
;;
restore)
# Stub
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
list_files | while read FILE; do
rm -rf /system/app/$FILE.apk
rm -rf /system/priv-app/$FILE.apk
rm -rf /system/app/$FILE
rm -rf /system/priv-app/$FILE
echo "Removed $FILE"
done
;;
esac
[Samsung Galaxy Nexus] skyleth:
Not working here :(
[Samsung Galaxy Nexus] YouKnowNothingJohn:
Try downloading the update through the official updater but manually go into recovery and manually flash the update.
[Samsung Galaxy Nexus] skyleth:
I've done that, but then it's not working as it was (with autoupdating).

I'd rather stick with cm recovery and flash twrp whenever I need it
[Samsung Galaxy Nexus] hgmichna:
CM-Updater vs. TWRP

That has usually worked, but it does not match the simplicity of the CyanogenMod updater with the Cyanogen recovery.

No problem for us here, but I provide phones for non-technical users. I don't want to teach them all to use TWRP.

Currently I also install the CM recovery and change to TWRP when needed. It remains a bit awkward though. The multiple boot processes take time.
[Samsung Galaxy Nexus] AV8ing:
Hello all. I have only just recently put CM 12.1 on my GNEX. I was previously running stock up until then. Everything seems to be running great (actually much smoother) with 2 exceptions. First one which is relatively minor, is that the phone drops and re-establishes wifi constantly at home, even when I'm in the same room as the router. The other problem, which is a big deal for me, is one particular app that I need for work (a scheduling type for aviation) will not connect to its server when using cellular data but works fine when using wifi. If I do not have wifi connectivity, it says that I don not have a connection to the internet and goes into offline mode (I am connected as I can browse the web, make skype calls, play my Simpsons Tapped out, etc). Typical response from our IT, "We do not support custom ROMs".

Just a shot in the dark here, but does anyone have any suggestions that might give me the connectivity I need on cellular data?

Thanks in advance for the help.
[Samsung Galaxy Nexus] :
Set your WiFi frequency to 2.4GHz only and see if it still disconnects.

You may want to try using this Xposed module as a workaround: http://xdaforums.com/xposed/modules/app-fake-wifi-connection-t2800416
[Samsung Galaxy Nexus] AV8ing:
awesome....thanks. I'll give them both a try. Thanks tomasz86
[Samsung Galaxy Nexus] michitux:
Crashes/reboots when using LiveDisplay-feature

My Galaxy Nexus reboots from time to time. Sometimes it's after a few days, sometimes more often. It always happens a few seconds after I turn the screen off and it's always a full reboot (i.e. with Google logo etc.). This has happened with all builds of CM 12.1 that I've been using since they became official nightlies. I didn't have this problem with CM11 with the official kernel but I had similar reboots with the "Fancy Kernel" that I tried for some time before switching back to the regular kernel.

I have an idea why this happens. I like to have a more reddish screen during the night. That's why I configured some automation app to change the screen colors using the color control interface in the "Fancy Kernel" for CM11. When I switched back to the stock kernel I wrote a simple app to do same thing with the "samoled_color" interface. As CM 12 has this feature built-in (named "LiveDisplay") I started using this feature. Now CM12.1 has the color control interface included and not the "samoled_color"-interface anymore. Always when the phone reboots, /proc/last_kmsg ends with messages from colorcontrol and the suspend. That's why a bit more than a week ago I decided to turn "LiveDisplay" off. The phone hasn't rebooted since then with now over 200 hours of uptime, therefore I suspect that this is the cause of the crashes.

When I developed my app, I noticed that while you could change the values in the files in /sys/class/misc/samoled_color/ while the display was off, the values were not applied (even though the files reported the new values). The colorcontrol interface in /sys/class/misc/colorcontrol/ doesn't have this restriction. The values are applied regardless if the screen is on or off. In manual tests this works and doesn't cause any crashes but maybe during suspend there is some race condition that sometimes triggers the crash? Is there any reason for the switch from "samoled_color" to color control? I'm just wondering because in CM11 you could also change the screen colors so apparently CM11 worked just fine with the "samoled_color"-interface.

I've attached two of the logs after crashes with screen off as described above and another log of a crash (also with full reboot) with screen on where I don't know if it is in any way related. The crash with screen on happened in Trebuchet during the opening animation of the app drawer, i.e. while this circle around the app drawer button was expanding. I can't remember that this has ever happened before and it hasn't repeated yet but maybe it is still useful as it is the only log after a crash that contained a backtrace, all the other logs always end with the suspend and always contain messages from color control directly or almost directly before it.
[Samsung Galaxy Nexus] breversa:
Would you know why this battery : https://www.anker.com/products/70SMT989-W22A is listed as NOT compatible with the Galaxy Nexus I9250 ?
[Samsung Galaxy Nexus] hgmichna:
Different battery for different phone

Different size. Different position of contacts. That battery is for the Samsung Galaxy S II.
[Samsung Galaxy Nexus] breversa:
Check the compatible models : the Samsung Galaxy Nexus SPH-L700 (Sprint) is listed as compatible. Is the SPH-L700 different (battery-wise) than the GT-I9250 ? Or is it maybe a matter of NFC compatibility ?
[Samsung Galaxy Nexus] :
The dimensions of the two are different. The battery will not fit into GT-I9250.
[Samsung Galaxy Nexus] breversa:
That's what I feared. Thank you for confirming. :)
[Samsung Galaxy Nexus] breversa:
No mobile data after soft reboot

I'm having a weird issue for quite some time now : after a soft reboot, I have the "no SIM" icon in the notification bar, and mobile data does not work. I can however phone and send SMSs (not sure about receiving though).

Going to Settings/Mobile network/APNs (or whatever it's called in english) shows that no SIM card is recognized.

Switch to airplane mode and back changes nothing.

I need to do a normal reboot or shutdown/start.

Also, when my phone randomly (soft) reboots (it happens sometimes, though infrequently), mobile data works fine.

Current CM version 12.1-20160320-NIGHTLY-maguro (but started several versions ago !) on Galaxy Nexus I9250.
[Samsung Galaxy Nexus] :
Old problem. It occurs in all Lollipop ROMs. I do not think there is any fix :(

Just do not use soft reboot...
[Samsung Galaxy Nexus] Suhayb803:
I encountered a problem

I installed everything properly, i reinstalled all my apps and they all work. When I installed Google Play Games, it gave the error 505, and I cannot install it. Every time it finishes download, then it says "installing," the error comes up..........can you please help me with this?
[Samsung Galaxy Nexus] hrico2002:
Hello

After i make a call i lose phone signal for a couple of seconds and after that it reconnects. How do i deal with this issue?

Also after some time my sim card is not detected anymore.
[Samsung Galaxy Nexus] Nautilus74:
you must delete manually

\DATA\APP\(application)

by a file manager

Then you can install it normally
[Samsung Galaxy Nexus] MayuraDeSilva:
Cool!

Snappier! Only complaint is some apps are not working - but they are working on Marshmallow (CM 13.0) though. Guess it's something to do with Lollipop itself.

Hope CM 13 will be snappier as this soon.

[MENTION=2633638]Ziyan[/MENTION] rocks!:cool:
[Samsung Galaxy Nexus] ancelin:
Did you tried to use those Gapps : cf my post 3813.

If i don´t use those 20160120 opengapps, I have so many play store issue...
[Samsung Galaxy Nexus] mstyle3244:
It will not be able to flash the latest Open Gapps.
[Samsung Galaxy Nexus] vortex-5:
As of build 2016410 I believe the headset button is now unresponsive.
[Samsung Galaxy Nexus] ILA:
MHL?

Does MHL work on this ROM? I have read somewhere in the thread that you've managed to get it working, but now that I've gotten the MHL cable, when I plug it to my monitor, nothing happens... Just trying to figure out if it's a problem with my cable or the ROM, without flashing a stock ROM...

Maybe I'm missing a step somewhere? Do I need to set something up?
[Samsung Galaxy Nexus] Skylined:
I am just here to say that this build 12.1-20160410-NIGHTLY is the best experience I had with my Nexus since Minco
[Samsung Galaxy Nexus] breversa:
Network silently stops working at night

Hi,

Anyone having this weird bug ?

I'm running

CM12.1-20160320-NIGHTLY-maguro

(but the bug started earlier), and several times a week, my network would silently stop working, starting between 23:00 and 01:00.

When I say silently, I mean that both wifi and data/network icons look like they have service, but pretty much any browsing/downloading fails, as if addresses could not be resolved (e.g. with Firefox, I instantly get "host unknown", as if it wasn't even trying).

I'm using AFWall+ as my firewall, but disabling or restarting it has no effect.

The only reliable solution I've found is to switch airplane mode on/off.

I believe I can still send/receive SMSs (plain old unencrypted "phone" SMSs, not encrypted "network" SMSs like Signal) and make/receive phone calls, though it's awkward to test as it happens in the middle of the night… I'm also pretty certain that it happens on both my home wifi and phone networks.

It's quite troublesome, as I end up missing many Signal messages (or email sync) until I think "Hum… that's weird : why has my friend not replied yet ?" and switch airplane mode on/off… and then sure enough receive a boatload of panicky messages asking why I wouldn't answer (I'm exaggerating a bit but you get the picture).

Additional info :

My phone provider normally supplies two APNs : one for data, and one for MMS. Since I've had MMS problems, I fused both APN info into a single APN, as CM reportedly has trouble using several APNs at the same time.
[Samsung Galaxy Nexus] Zenroid:
Agreed thanks [MENTION=2633638]Ziyan[/MENTION]
[Samsung Galaxy Nexus] vortex-5:
Anyone know what happened to the cyanogen changelogs?

Are there changes in these new builds or are we just increment the date? We just got a new build 4-17-2016 for those that are keeping track.
[Samsung Galaxy Nexus] Skylined:
Changelogs: https://www.cmxlog.com/12.1/maguro/

But info on newest builds are null

I'm afraid to flash new build...it's sooo stable right now...maybe later
[Samsung Galaxy Nexus] playitlouder:
No logs, no problem.

Post a logcat and dmesg when the issue happened, tag Ziyan in the post.

Something like this is hard to recreate.
[Samsung Galaxy Nexus] breversa:
Yeah, I've been waiting for the problem to pop up again to try and get a log, but since I can't tell exactly when it'll happen again, I probably won't be able to get a dmesg then. logcat is doable but will be huge, I fear.

Anyway, thanks for your instructions, [MENTION=4038245]playitlouder[/MENTION] :)
[Samsung Galaxy Nexus] AntonyBIG:
Sorry guys, I have a problem. I can't change scheduler I/O, that is stock on bfq. You think bfq is good, or you think I have to change it? And how can I change? If I do my cell dies and I have to remove battery and restart. I install the rom in this order: Wipe data, cache, dalvik and system, then I install 04/10/2016 nightly, gapps pico and update 2.67 supersu.
[Samsung Galaxy Nexus] playitlouder:
You could probably change it with the Kernel Auditor app.

But why would you bother? My Gnex runs perfectly smooth (for a an Android device from 2011 that is ;)) and it's stable.
[Samsung Galaxy Nexus] musical_chairs:
Changing the scheduler away from bfq causes the phone to freeze and reboot. This bug has been present for some time. Other than than, bfq is an excellent scheduler which is why it's the default in spite of this bug. You certainly don't need to change it.

Of course, if you want to, that's your privilege. The default scheduler is set in build.prop, change it to cfq or whatever you prefer, and reboot. Then, you can use Kernel Aduitor to change the scheduler to other schedulers. Just remember that changing it away from bfq while the system is running will cause a reboot.
[Samsung Galaxy Nexus] frusso3:
Hi guys , I currently use the latest cm11 and I feel good . I would like to move to 12.1 and I wanted to know : in the daily use is better than cm11 ? It works USB OTG ? Thanks
[Samsung Galaxy Nexus] Regina Rainbow:
I'm trying to build CM 12.1 for maguro on my arch linux machine. I double checked the build environment, all dependencies are met. But nevertheless, it always stops at the same point - when building libvpx stuff:

/home/regina/android/system/out/target/product/maguro/obj/STATIC_LIBRARIES/libvpx_asm_offsets_vpx_scale_intermediates/libvpx_asm_offsets_vpx_scale.a)
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: /home/regina/android/system/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/third_party/libvpx/source/libvpx/build/make/obj_int_extract.o: unsupported reloc 43 against global symbol stderr
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: /home/regina/android/system/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/third_party/libvpx/source/libvpx/build/make/obj_int_extract.o: unsupported reloc 43 against global symbol stderr
external/chromium_org/third_party/libvpx/source/libvpx/build/make/obj_int_extract.c:31: error: unsupported reloc 43
external/chromium_org/third_party/libvpx/source/libvpx/build/make/obj_int_extract.c:787: error: unsupported reloc 43
clang: error: linker command failed with exit code 1

It seems to be the same problem, this guy had back in december: Post 1, Post 2. On my arch linux machine none of the suggested/linked "fixes" help.

Yesterday I synced the repo on my ubuntu machine and started to build. Absolutely no problem there, building process works flawlessly, spitting out working ROMs. My guess is, that there's something wrong or rather "ubuntu specific" about the prebuilds? Has anyone managed to build CM 12.1 for maguro in Arch Linux lately?
[Samsung Galaxy Nexus] thepasto:
On arch the easy way to fix your problem is to

ln -sf /usr/bin/ld.gold prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/bin/ld

From your sources root
[Samsung Galaxy Nexus] frusso3:
I installed the last of 17/04 but does not work usb host . Is this normal?
[Samsung Galaxy Nexus] Regina Rainbow:
Thanks for your help! After manually linking the corresponding libs, the build ran without any further problems.
[MENTION=2633638]Ziyan[/MENTION]: Is this intended or accidental behavior? Because if it's intended, it might be covered in maguros build wiki; if it's accidental, it might have to be fixed?
[Samsung Galaxy Nexus] thepasto:
It's not android related issue, it's binutils archlinux package doesn't fit MM prebuilt version of ld.

Maybe it should be added in archwiki's android page.
[Samsung Galaxy Nexus] frusso3:
I also noticed that the browser is slower than cm11 , especially in desktop mode . Someone confirmation?
[Samsung Galaxy Nexus] skyleth:
I'm wondering why there's no snapshot version for the gnex. I think it's pretty stable right now, but maybe there's something I don't get

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] Heart1010:
Is it possible with CM12.1 to enable the old usb mass storage function instead of mtp?

I've read to use these command to enable them

su
setprop persist.sys.usb.config mass_storage,adb
reboot

But that doesn't work.

update: ok, forget about usb mass storage... I asked because I need a full image of my nexus because I reformated my f2fs /data partition back to ext4 (and forgot to backup all files). But I found http://xdaforums.com/showthread.php?t=1818321 which is the better/correct way of making a raw image of the userdata partition.
[Samsung Galaxy Nexus] johnSpar:
+1
[Samsung Galaxy Nexus] Md Helal:
about notification!

the cyanogenmod 12.1 for nexus i9250 is good, but after installing it, i noticed that the notification LED system don't work properly. And when I plug in for charging the LED goes on.
[Samsung Galaxy Nexus] tlwhitec:
Check the LED settings, this is a new feature (at least) in CM12 and can be easily turned off.