yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] skyleth:
No problems here. Check the led settings and/or reinstall the ROM again doing a full wipe. Maybe there's something interfering

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] breversa:
There ! I think I managed to get both catlog and dmesg logs when it happened ! :)

PS :

I don't know how to add tags, so I hope this works :
[MENTION=2633638]Ziyan[/MENTION]
[Samsung Galaxy Nexus] skyleth:
I'm having a problem with the default browser. Every time I try to open a link to the Google play or any YouTube video, it opens them directly in the browser instead of asking with which app or using their respective ones. I've tried resetting the default settings without luck. With chrome it works flawlessly, but chrome it's too slow in my phone

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] skyleth:
Screenshots feature broken in latest nightly

Log included http://cloud.tapatalk.com/s/573055911556e/2016-05-09_11.13.zip

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] vortex-5:
Seems to work for me.
[Samsung Galaxy Nexus] skyleth:
I'll wipe system and try again
[Samsung Galaxy Nexus] vortex-5:
Are you triggering the screenshot with vol down and power? I'm getting a flash and a notification that the screenshot is taken.
[Samsung Galaxy Nexus] vitalero:
Having issues installing Gapps, Insufficient storage space availalble

installed normally like in the OP, did wipe, flashed ROM, trying to flash gapps but cant, wiped cashe/dalvik and still fail at gapps

Trying to install the Nano version

ALSO, dont we need to flash some SuperSU or something?
[Samsung Galaxy Nexus] bamtan2:
try to install the very smallest opengapps available, just to make sure

cm12 has root built in via the developer options

if you must resize your system partition, try flashing the appropriate REPIT for your device https://github.com/Lanchon/REPIT
[Samsung Galaxy Nexus] skyleth:
Yes, but somehow it was giving an error. I wiped everything and reflashed the ROM for a clean start and now is working again.

Any way to make the navbar match the status bar color when it changes?

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] norton75:
cm-12.1-20160508-NIGHTLY-maguro.zip broken wifi

With release cm-12.1-20160508-NIGHTLY-maguro.zip WiFi seems to not work properly (wifi switch greyed out)

Reverted to cm-12.1-20160501-NIGHTLY-maguro.zip and WiFi returned to work correctly
[Samsung Galaxy Nexus] natzy85:
while using Google Fit to keep track of my bike ride the app keeps reminding me to turn the high precision of the GPS on but it's already on. Is this a CM bug? I switched to Google because runtastic always loses track of the ride if I'm biking more then 2 hours (think because of the low memory). Any way does anyone suggest a fix for this?
[Samsung Galaxy Nexus] breversa:
Sorry to read about this.

I flashed cm-12.1-20160508-NIGHTLY-maguro.zip just now and did not encounter your bug though.
[Samsung Galaxy Nexus] kerpert:
I don't understand how to flash gapps without having space problem.

I format partitions in F2FS, then install cm-12.1-20160105-UNOFFICIAL-maguro-BFQ-ZCACHE-LZ4-ZRAM.zip without mounting system, at this point if I flash open_gapps-arm-5.1-pico-20160521.zip I receive the no space error.

If I mount system I can flash it correctly but file system return to ext4.

Shell I download older pico gapps version?
[Samsung Galaxy Nexus] n76:
EXT4 on /system is not really a problem as it is mounted read only when the phone is in normal operation. The advantage for F2FS is when you are doing write operations. So the real need and benefit for using F2FS is on /data and /cache.
[Samsung Galaxy Nexus] bamtan2:
It is supposed to return to ext4!

That said, if anyone wants to change the size of /system, they may flash the appropriate REPIT for their device, by Lanchon: https://github.com/Lanchon/REPIT
[Samsung Galaxy Nexus] kerpert:
I just had the same issue, solved by reflashing all another time without change TWRP version (2.8.6.0 f2fs).
[Samsung Galaxy Nexus] gabrielex:
I'm trying to flash it but I get an error saying not enough space available when flashing the nano gapps from OpenGApps.

What should I do?

EDIT: Sorry wrong thread, I was supposed to post this in the CM 13 thread!
[Samsung Galaxy Nexus] kerpert:
After having many apps crashes and data lost (e.g. WhatsApp history), I reformat the data and cache partition to EXT4, without change the TWRP (2.8.6.0 F2FS).

Now all is fine, but no idea why those errors in F2FS, could be a bad recovery version?
[Samsung Galaxy Nexus] nu pogadi:
increased battery drain with latest nightly

After flashing the latest nightly "cm-12.1-20160605-NIGHTLY" I noticed a strong increase in battery drain in stand by.

With my normal, everyday use my GNex will last 1,5 days with one charge and will still have about 35 - 40% capacity left. In standby it easily reached 3-4 days with previous nightlies.

After flashing the latest nightly the battery drain increased - its about 25 - 30 % in standby during the night.

Besides, I noticed one issue when flashing this version. Normally the device reboots into TWRP and I can normally chose to wipe cache and dalvik, then flash the new nightly and reboot system afterwards. With the latest nightly and its previous version it went all in full-auto mode, e.g. I choose to flash the new version, my GNex then rebooted into TWRP and with out any interaction from my side TWRP started to flash the nightly and then rebooted into system. I did not even have the chance to interfere or interact.
[Samsung Galaxy Nexus] breversa:
Reporting battery drain as percentage can be highly misleading, because not only are batteries not made equal, but they also wear off with time.

To work around that, you may want to use an app like Battery Monitor Widget that can display battery consumption in mA, which is much more objective. Also, you'll be able to monitor what processes/apps use the most battery.
[Samsung Galaxy Nexus] hgmichna:
Don't worry, be happy. It does exactly the same automatically. That's how Android is meant to work.

If you want to do something different, like wiping data, flashing something else on top, or whatever you like to do, you can still easily do it by not starting the automatic update, but instead booting into TWRP and doing whatever you want to do. So, no problem there.
[Samsung Galaxy Nexus] cloud_strife84:
Is there a way to get OTG working with this rom?
[Samsung Galaxy Nexus] musical_chairs:
Does OTG work on the latest unofficial cm13 build? I don't have an OTG cable to test with, but if it works there, I may know what is wrong.
[Samsung Galaxy Nexus] werty100:
Any changelog for cm12.1 19/06/2016?
[Samsung Galaxy Nexus] bamtan2:
https://www.cmxlog.com/12.1/maguro/ ?

---------- Post added at 10:11 AM ---------- Previous post was at 10:04 AM ----------

I have been using CM12.1 and Android 5 Lollipop for over 6 months, and the performance has been great. The phone performance is smooth and the bugs are minimal if any. I have zero complaints. You have done such a good job, I just donated to you for all your past work done. Thank you!
[Samsung Galaxy Nexus] werty100:
Updating whatsapp from play sotre makes my phone soft reboot and then loose GSM, only happen with Whatsapp at the moment
[Samsung Galaxy Nexus] LeoHart:
Since the latest Update I noticed a small bug with the battery.

If the battery is empty and the gnex shutting down, the gnex can't be charged. I must swap the battery and all is working again.

Maybe someone had noticed similar too.
[Samsung Galaxy Nexus] nobbi123:
Hello, I've been using my Nexus with the last CM12.1 and wanted to access a USB Stick via a OTG Adapter.

But the USB Stick is not getting recognized, under Options -> Storage/Memory. I can only see internal Storage.

A USB mouse is being recognized, the cursos however is missing.

Is the GNex not functioning with OTG under CM12.1?

IN TWRP 2.8.7.0 I can access the USB Stick via OTG. So it does seem to be an issue with CM12.1

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] varadparulekarofficial:
I send messages which contain upto 25-30 words and there isn't any problem..

Sent from my CyanogenMod powered Galaxy Nexus
[Samsung Galaxy Nexus] aliesz:
Which version of CM12 do you use!? I have installed 5.01 version and there was that problem.
[Samsung Galaxy Nexus] varadparulekarofficial:
I have the 20/12 build which runs on Android 5.0.2

Sent from my CyanogenMod powered Galaxy Nexus
[Samsung Galaxy Nexus] tlwhitec:
Easy with those emotions, [MENTION=5421988]aliesz[/MENTION] :) SMS size is not defined by words, right? It's defined by single characters and 1 SMS is supposed to contain 160 of them(not using Unicode). The problem is obviously in splitting larger messages. It's quite likely that a message with 30 words can easily fit into that limit without any splitting. Unless Mr. "Wordcount" tells us how many characters his message had, he can't be taken seriously.
[Samsung Galaxy Nexus] xergio24:
Indeed.

The SMSs problem shows up when you write an SMS with more than 1 "page"... that's more than 160 GSM characters or more than 70 if you use UNICODE characters (like á, é, í, ó, ñ...).
[Samsung Galaxy Nexus] sohailazam:
Casting not working

Had flash this ROM works FINE :good:

but its not casting to my chromecast im talking about the inbuild casting option in 5.0 , btw i hav try'd third party apps like all cast and local cast its heck of a delay , :( i have try casting from my MOTOE AND MOTO G its cast really good no delay compare to my gnex from the third party apps, Please fix:fingers -crossed: { NO DEMAND JUST REQUEST }
[Samsung Galaxy Nexus] xXrawrXx:
Has anyone else been unable to boot 12/20 build after a clean install? I'm assuming my phone can't handle booting the GPU at 512mhz is there any work around?
[Samsung Galaxy Nexus] XneofuX:
Wipe \System before installing? Not entirely sure, but could help ^^
[Samsung Galaxy Nexus] kekko986:
[MENTION=2633638]Ziyan[/MENTION] thx a lot for lollipopping maguro! You rules!
[Samsung Galaxy Nexus] varadparulekarofficial:
[MENTION=2633638]Ziyan[/MENTION] First of all HATS-OFF to your awesome work you have done to lollipopify our maguro.. Increasing the GPU frequency to 512 MHz resulted in an impressive boost in performance. Why don't you consider overclocking even the CPU frequency? The 1.2 GHz frequency isn't too slow to run Lollipop but its not even that fast. Hope you consider this.. [emoji6]

Sent from my CyanogenMod powered Galaxy Nexus
[Samsung Galaxy Nexus] XneofuX:
The problem with that is the increased heat output. When you stress the cpu over a long time, the phone is getting pretty warm, even without an overclock. So i don't think, that it's such a great idea. Also i think that it's locked in the Kernel and not in the ROM ^^
[Samsung Galaxy Nexus] n76:
More to the point, the manufacturing process is such that there is some variation in how well each individual chip performs. The spec'd clock rate is picked so that they have reasonable yield of chips that actually work. You can over clock lots of chips out of a production run but not all. And maybe not even most. If a distribution automatically just over clocks things then there will be chips (or in our case phones) that fail to run correctly.

Over clocking should be an user option, the default build should use the manufacturer's specific clock rate.
[Samsung Galaxy Nexus] XneofuX:
Yep ... PC CPUs as an example ... the newest i5/i7 can easily be overclocked to 4.2 Ghz ... when you're unlucky then there is the end. If you get lucky, you can overclock it stable to 4.7-4.8 Ghz (mine is at 4.6 ^^).
[Samsung Galaxy Nexus] xXrawrXx:
I've done a complete wipe using twrp and cwm and neither works along with trying various gapps and it'll boot but the screen is pixelated is there any way to change the defualt clock of the rom?
[Samsung Galaxy Nexus] XneofuX:
Why do you want to change the default clock of the rom? ^^ with cmw 6.0.5.1 it works perfectly for me ... Before install i wiped \System and \cache ... not more and it works flawlessly ... ;)
[Samsung Galaxy Nexus] xXrawrXx:
Because my GPU is unstable at 512mhz so I get a pixelated screen and no video and yes I've done a complete wipe and in the end reverted to the previous build with the GPU clocked at 384mhz
[Samsung Galaxy Nexus] nikodr:
Did you try to use trickster mod to change the frequency?I think it allows it to be lowered
[Samsung Galaxy Nexus] fearlessaryan:
Awesome!!

Hi Ziyan,

The Rom is awesome and does not lagg much though there are many issues still I am using it as my daily driver.

Thanks a lot for ur efforts.

Thanks & Regards,

fearlessaryan
[Samsung Galaxy Nexus] girkev:
[J
[Samsung Galaxy Nexus] fearlessaryan:
update cwm on maguro

Can You please tell the steps to manually install cmw 6.0.5.1 on maguro.
[Samsung Galaxy Nexus] playitlouder:
[MENTION=2633638]Ziyan[/MENTION]

Who would've thought the mighty Gnex can run Pokemon Go? :P

Works fairly well considering it's using 300mb RAM ;P

Catching Pokemons is sometimes pretty laggy with the virtual reality mode turned on (using the camera), but with it turned off its fairly close to fluid :D

Thanks for your work again ;)

PS: Might try CM13, as some more RAM might help performance ;)
[Samsung Galaxy Nexus] abo we2am:
Please help me, can any one upload the last version of cm12.1 for me? I can't open the official site of cyanogen.

Thanks a lot.
[Samsung Galaxy Nexus] rahimali:
Here: http://pc.cd/ceUctalK
[Samsung Galaxy Nexus] bamtan2:
From http://get.cm/?device=maguro the link is http://get.cm/get/jenkins/169285/cm-12.1-20160710-NIGHTLY-maguro.zip and the hash is sha1: 9fdc26746e605c31cc07fae5993c72fe3c0a5262
[Samsung Galaxy Nexus] abo we2am:
Thanks bro. :)

---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------

Thanks bro, that helped :)
[Samsung Galaxy Nexus] vitalero:
Any chance to get tap-to-wake on the gnexus?

My power button is not working very well anymore
[Samsung Galaxy Nexus] playitlouder:
Isn't there a Volume Button wake option somewhere? :cyclops:
[Samsung Galaxy Nexus] suniz:
After properly installed the latest version of 12.1, when I press Reboot now after, I have a google screen (with google logos and an unlocked padlock), then it's totally black, any tips ?
[Samsung Galaxy Nexus] vitalero:
Yeah but its either waking up the device or changing music tracks, cant have both :[

And we already have a "tap notification" action to turn off the screen, im sure a double tap to wake isnt such of a big issue
[Samsung Galaxy Nexus] bamtan2:
double tap to wake was tested in a galaxy nexus kernel by [MENTION=4608636]bsmitty83[/MENTION]. it did not operate consistently for me, and apparently it uses even more battery life than normal! I would not recommend it to anyone.
[Samsung Galaxy Nexus] hgmichna:
I agree. To the best of my knowledge, the phones that have it use a special hardware capability to avoid using any noticeable amount of electricity. Phones that do not have such hardware have to power up the entire touch screen to make it possible, which certainly uses some energy. It can be done, but may not be wise.

I don't know the finer details. If anyone does, please educate us.
[Samsung Galaxy Nexus] playitlouder:
Wasn't there swipe to wake in the original Google kernel?
[Samsung Galaxy Nexus] [.::MDT::.]:
Hello, thanks a lot for this Rom.

I've been trying it for about a week, but noticed that the phone keeps rebooting sometimes (e.g. during sygic maps download it rebooted 3 times)...

Does anyone have the same problem?

What could the issue be?

Thanks a lot
[Samsung Galaxy Nexus] breversa:
You might want to try this : https://fossdroid.com/a/waveup.html
[Samsung Galaxy Nexus] Ziyan:
As of today, the nightlies have been switched over to CM13.0 A new CM12.1 snapshot has been uploaded, which won't disappear from get.cm, so anyone can decide to revert back to 12.1 anytime :) I've been using 13.0 for a while now, and I think it more or less reached the stability and performance of 12.1.
[Samsung Galaxy Nexus] hgmichna:
Great! Thanks.

Do you expect that the update from CM 12.1 to 13 can keep the users' apps and their data (i.e. dirty flash works)?
[Samsung Galaxy Nexus] Ziyan:
Theoretically, yes, as long as you flash a CM13 compatible gapps before booting into it first. However, I never tried it...
[Samsung Galaxy Nexus] bamtan2:
I think I will volunteer to test this for you. The last 12.1 build I've been using for many months has been quite stable. I think now that I should upgrade to your last 12.1 milestone, test it for regressions for a couple weeks, and then use it as an opportunity to test upgrading to CM13. I will of course dirty flash CM13 and new CM13 google apps simultaneously. Then we will see if it works. I hope for my sake it does ;) ;)
[Samsung Galaxy Nexus] mstyle3244:
Do not be improved to be able to flash the open gapps nano?

now on tap I want to use.
[Samsung Galaxy Nexus] bamtan2:
see:
[Samsung Galaxy Nexus] axlu:
cm-13

it doesn't work with capps-13.0-20160707-signed.zip
[Samsung Galaxy Nexus] bamtan2:
I'm sorry I don't know what that is ;( I use the smallest one at http://opengapps.org/
[Samsung Galaxy Nexus] mstyle3244:
Lanchon REPIT did not work if an error occurs.

"/ Tmp" Directory to put error to flash occurs.
[Samsung Galaxy Nexus] bamtan2:
Maybe this is a TWRP error? I think REPIT requires a certain version of TWRP which is not mentioned in [MENTION=2633638]Ziyan[/MENTION]'s OP.

I apologize. You should not be expected to hunt for this file. Please try this TWRP: http://xdaforums.com/showpost.php?p=66467639&postcount=1971 (you will need to "flash image to recovery partition" instead of normal "flash zip". example: reboot to TWRP -> enter install -> flash image -> select twrp img -> select "recovery.

Edit: I think I may know the cause of your problem. [MENTION=4141005]Lanchon[/MENTION]'s REPIT needs to unmount all partitions. The error messages imply it is trying to unmount /system, but cannot. So it copies itself to memory (in /tmp). This means you must manually unmount /system. Unplug your phone from your computer, and click Mount in TWRP. Unmount /system. Go back to flash the REPIT zip from /tmp. My REPIT took 10-30 minutes to run (I didn't see exactly). It checked and TRIM'd all the file systems, even /data which it doesn't change. So, please have your battery charged and phone plugged into the wall before attempting REPIT.
[Samsung Galaxy Nexus] musical_chairs:
capps (cyanogen OS apps) are different than gapps (Google apps). I never tried with capps, there's nothing in there that I want.
[Samsung Galaxy Nexus] hgmichna:
I have a spare Galaxy Nexus here, my backup phone, fully installed with lots of apps. I think that would be an ideal test case. What exactly should I do?

I think I will first update to the last CM 12.1 version, to have a well-defined starting point.

I suppose I cannot use the built-in updater to update to CM 13, because it would boot into Android immediately after the update. But I can at least use it to download the new CM versions to the cmupdate folder.

I assume that, to keep data, I would have to download CM 13 and OpenGapps for Android 6 pico, then flash both with the current CyanogenMod recovery before booting into Android.

Is there no way to prevent that many users destroy their phones by using the recommended update method? They are even encouraged to update by notification. This just happened to one friend of mine. I think it is not good style. I have no idea how users could be protected, but it would be great if a way could be found. Some kind of warning perhaps.
[Samsung Galaxy Nexus] playitlouder:
Have accidentally updated with CMUpdater before.

Would be as simple as prompt the user to download the latest opengapps and flash the gapps with the updates if they are either in the cmupdater or downloads folder.

A few simple lines of code...
[Samsung Galaxy Nexus] hgmichna:
Sounds simple, but if the user uses the updater, she will not get a chance to flash Gapps, because the updater automatically reboots after flashing CyanogenMod.

Since our maintainers do not program or modify the updater and since this is a general CyanogenMod problem, what you propose is to generally modify the updater. The updater would then have to know whether a suitable Gapps package is present on the phone. This may be a bit more involved than just a few lines of code. The updater may have to ask the user which Gapps file to install.

But what would be really simple is to add a user instruction to the updater when the main version changes, like from 12.1 to 13. It could read like this:

"You are going to update to a new major version. This cannot be done with this updater. You have to find, and download the matching Google apps for this version of Android, then start the recovery to manually flash the new CyanogenMod version and immediately afterwards the Google apps."

Since it is certain that the updater would destroy the phone, it should never actually start the automatic updating with a major version change.

I must say, I find it outrageous that a semi-automatic system like the updater entices the user by means of notifications to destroy her phone.

Is there anybody here who is in contact with the people who maintain the updater? This change request is so obvious and so useful that I find it hard to believe that nobody has ever thought of it.
[Samsung Galaxy Nexus] playitlouder:
I'd report it on the official CM issue tracker. Here: https://jira.cyanogenmod.org/secure/Dashboard.jspa
[Samsung Galaxy Nexus] hgmichna:
Jira issue CYAN-2049: Updater breaks phone due to non-matching Google apps

I went there, searched for related issues, and found one:

https://jira.cyanogenmod.org/browse/CYAN-2049?jql=component = Updater

In this issue the exact same sentiments were written that I uttered here.

It bears these dates.

Created:

30/Aug/13 5:15 PM

Updated:

09/Feb/16 7:40 PM

Resolved:

23/Jul/15 11:13 PM

The resolution was to do nothing.

At this point my idiot bells begin to ring, and I withdraw. I do not deal with idiots. Have better things to do.
[Samsung Galaxy Nexus] playitlouder:
The issue has been closed due to old age. I created a new one.

Lets see ;)

https://jira.cyanogenmod.org/browse/CYAN-7886
[Samsung Galaxy Nexus] hgmichna:
How to update from CyanogenMod 12.1 to 13

I went ahead and did it. I had already set the auto-update option of the CyanogenMod recovery in the developer options and subsequently updated to the latest CyanogenMod 12.1 nightly: cm-12.1-20160710-NIGHTLY.

First I downloaded the first CyanogenMod 13 nightly, using the downloader, but did not install it. Then I downloaded OpenGapps ARM, Android 6, pico to the phone.

I booted into the current (automatically updated) Cyanogen recovery, wiped cache, flashed CyanogenMod 13, then immediately flashed the Google apps and rebooted.

I feared that the CyanogenMod recovery's inability to format the system partition might spoil the process, but a little bit to my surprise it worked on the spot. No need to flash TWRP, although I am pretty sure TWRP would have worked at least as well.

Finally the phone booted into the new CyanogenMod 13 without a hitch and "optimized" only 86 apps instead of the usual 156 with CM 12.1 updates.

It is a miracle. 2 years ago I would have lost any bet that Android 6 would ever come to this phone, mainly because of its limited RAM. Thanks a lot to all who contributed and particularly [MENTION=2633638]Ziyan[/MENTION].

Addendum: Much more detailed instructions, suitable for beginners, can be found at http://winhlp.com/node/928 .
[Samsung Galaxy Nexus] bamtan2:
So far so good running the latest cm-12.1-20160719-SNAPSHOT-YOG7DAO8DL-maguro.zip ! Some settings were lost in the dirty flash from the older version I was using, including the launcher icon settings. But the ROM is fast and good. Thanks [MENTION=2633638]Ziyan[/MENTION]!
[Samsung Galaxy Nexus] catteneo:
Changelog

Is there any difference between the last nightly (20160710) and the snapshot? Can't see it on the changelog :S