yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] wbedard:
Thanks for the tips. I assume you are referring specifically to issues affecting this ROM+device as I haven't had any trouble connecting to 5GHz WiFi with a variety of other ROMs and devices. That said, my maguro device configured with either FML or CM12 continues to refuse to make said connections. In my case, my device doesn't even see my router when it's using channels 149-161. While it does see the router when it's on channels 36-48, it simply won't connect no matter what changes I've made to the router and while my other devices have no trouble connecting to the very same router interface. While I have to admit that I'm stumped for the moment, I would love to provide whatever logcats might be requested if someone would like to help me troubleshoot this issue and beta-test any possible fixes!

(@Ziyan)

R/

wbedard
[Samsung Galaxy Nexus] AgentSmith:
Have you checked if it isn't a CM12 issue? Maybe the CM team has already fixed the issue.
[Samsung Galaxy Nexus] Ziyan:
Try getting logcat, as I don't really see an error that would prevent the device from booting :rolleyes:
[Samsung Galaxy Nexus] vit0m:
Hi guys! Nice work on this unofficial release!

I have some noob to unofficial question:

- I have to come here for updates or the built-in sistem is working?

- eventually when a official CM release comes out can i upgrade from this?

It's working pretty well, only thing broken seems to be the camera, have some working stock-like options to suggest?
[Samsung Galaxy Nexus] revanmj:
How is it supposed to work when this is not an official CM12 build. Of course you have to come here for updates until release of official nightlies.
[Samsung Galaxy Nexus] Reptilez_DK:
Actually, it could work, since it is open source, and configurable to update from whatever source. But most people are too busy, telling other people off, to realize that. ;)
[Samsung Galaxy Nexus] revanmj:
But its open source for quite some time and I didn't see any developer using it besides CM team. So being realistic, it won't work in unofficial builds :)
[Samsung Galaxy Nexus] Reptilez_DK:
I can't remember which device, but I did see it, being used by other than CM. But never mind. The point was, that it could work. :)
[Samsung Galaxy Nexus] :
Since [MENTION=2633638]Ziyan[/MENTION] is cm's official maintainer of this device you could see this as official cm, all we are testing here is coming on cm github, ,so a very big thanks to Ziyan
[Samsung Galaxy Nexus] poo706:
Here's about 4200 lines worth of the logcat. http://pastebin.com/W5CrdtpR I can do more if needed. Thanks again for looking.

[poo]
[Samsung Galaxy Nexus] Reptilez_DK:
[MENTION=2633638]Ziyan[/MENTION] any idea, as to when, you will push your changes upstream ? :) THIS IS NOT AN ETA REQUEST ! :)
[Samsung Galaxy Nexus] Ziyan:
New build up.

Most notable changes:

- added support for CMHW (color, gamma, cab, vibrator settings)

- Minor kernel improvements

- synced with CM12 sources (lots of misc changes, like the ability to display battery percentage, etc...)

I'd like to fix the stock camera before that :) I may push the kernel and maguro's repo today or tomorrow, but tuna has to wait a bit more :/
[Samsung Galaxy Nexus] Reptilez_DK:
Awesome ! A huge thank you, for all the work, you put into this, in Koush's words, "ancient device" ! ;)
[Samsung Galaxy Nexus] rajputrajat:
Hi ziyan

Does it have f2fs support?

Thanks
[Samsung Galaxy Nexus] aliesz:
Thanks a lot Ziyan, are there any fixes on RIL(especially for sending long SMS) and google account issues in new build?
[Samsung Galaxy Nexus] n76:
Wouldn't any Google account issues be associated with gapps rather than the kernel work Ziyan is doing?

Along that line, I run with out gapps using components from the microG/nogapps project. That runs to my satisfaction on CM11. Has anyone tried it on CM12?
[Samsung Galaxy Nexus] Igazine:
I gotta say that this ROM compared to others (even KK and JB ROMs) is fast and snappy. I always had issues lately with KK ROMs, a lot of lag after a day of use etc.

This ROM is surprisingly fast.

Thank you, keep up the good work
[Samsung Galaxy Nexus] Childe89:
Never encountered SMS or calling problems, and I´m using this rom and Zmod and basically CM11 from early stages of development, and those functions were always rock solid for me. (except the issue with black screen for few seconds when receiving call, but that seems like lollipop GUI issue not call itself).

Maybe your operator has some unusual SMS settings, which require some configuration - like changing SMS center number.

If you think MMS, that is somewhat broken in all AOSP roms as far as i know - for operators who use multiple APNs, switching between MMS and INTERNET APN is very unreliable

You probably wiped cache and dalvik in recovery, if not try so.

If nothing helps, try to reflash with google factory image: https://developers.google.com/android/nexus/images

which is complete wipe and rebuild of all partitions, and then try flashing from scratch again - recovery, rom, etc.
[Samsung Galaxy Nexus] hgmichna:
No SMS Reception

Thanks for your assistance!

I am not aware of that SMS center number setting. Where is it?

Let me note that SMS reception works without that setting on my oldest as well as on my newest phones. Just not on the Galaxy Nexus since this upgrade.
[Samsung Galaxy Nexus] Childe89:
Well to be honest I never changed it on this ROM so I´m not sure where to find that setting, it should be in sms app under some advanced settings. :)

If not, dial this code *#*#4636#*#* and you will find SMSC number there, in phone info. Click refresh, type correct one, and click apply (or actualise, depenfing on translations) :)

Edit:

Totally forgot, MMSC should also be in APN settings, edit your default APN in network settings (the one selected with dot) and dont forget to save changes
[Samsung Galaxy Nexus] moe61:
The new build is way faster and much more stable.

The lag for turning on the screen for a call is a little faster but still takes some seconds.

Another problem I have is while flashing an image. I always have to format the system partition. Otherwise I'll get the "can't install this package on top of incompatible data" error message. After flashing the new image I'll have to flash the gapps as well though they woun't crash on boot.

Any idea why I have to format system-partition every time?

Thanks

moe
[Samsung Galaxy Nexus] ASHURiCAN:
Guess what? I have the same problem but with my GTab2 :D. Glad haven't this problem with my GNex! Would be nice to know what cause this problem...

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] ftrack:
Hi,

Do i need to first total wipe data, cache, delv again before flashing new build i.e cm-12.1-20150831-UNOFFICIAL-maguro.zip?

I knew most of them recomend that but how can restore my old software etc is there any backup software.?

Thanks
[Samsung Galaxy Nexus] hgmichna:
Updating, Backup

The first post in this thread describes it:

There is anyway no harm in trying, because you can still wipe and flash differently if it does not work.

There are some backup apps: Helium (formerly Carbon) is pretty good, but backs up only the data of those apps that allow it and has a tendency to choke on a few apps.

Titanium Backup is more rigorous and backs up pretty much everything, but its user interface is not very well thought out. It requires some discovery and learning.

But in your case your best bet may be the good old Nandroid backup that every good recovery can do. It backs up everything including the system itself. The downside is that you can restore only on a phone of exactly the same type.
[Samsung Galaxy Nexus] ftrack:
Thank for the answer..! :good:

I am on the way of flashing new build, just one more help can i go for auto kernel 22. will that help me or should i stay with stock kernel.

Thanks
[Samsung Galaxy Nexus] Pee_kee:
Can i dirty flash it on zmod.?

:confused:
[Samsung Galaxy Nexus] zieruchan:
when playing some games eg : clash of clans, I found, 'audio lags /unsync'. with latest build 30/8

sorry my bad english
[Samsung Galaxy Nexus] jnns:
Here's what I wrote down after using this ROM and the Galaxy Nexus after 5 days of usage. Due to me never having used the Galaxy Nexus with other ROMs besides this, I cannot say if my problems are tied to the ROM, the device or CyanogenMod 12.1. I'm using 12.1-20150831-UNOFFICIAL-maguro with the f2fs filesystem.

Notification bar unusable (i.e. graphical glitches, black lock screen background).

To get rid of graphical glitches, go into the developer settings and activate "Improved graphic effects".

Reboots.

The phone reboots sometimes and afterwards no SIM card is recognized (I guess this is a soft reboot then). It especially occurs during heavy usage (i. e. having navigation and VLC active simultaneously).

GPS problems.

Getting a GPS fixation takes sometimes minutes. Navigation is unusable because the signal is dropped every few minutes and the position is jumping a lot afterwards resulting in false routing advice.

Speed.

In general, the speed is very good and that makes it usable as a daily driver. But you can't help but notice that the phone is very dated. A small lag here and there is not very problematic but there are situations where lags are annoying (for instance, it takes several seconds for the display to wake up when there's an incoming call).
[Samsung Galaxy Nexus] matorola:
flashed back to cm-12.1-20150728-UNOFFICIAL-maguro.zip , since last release is quite slow on some operations, like answering a call (black screen)

PS: later edit, actually 0728 seems to be slow in showing who is calling as well, so it could give last release one more try....
[Samsung Galaxy Nexus] nikodr:
Regarding speed the only way to fix is with a custom kernel settings or to apply overclock both cpu and gpu.

I have mine at 1.650 max and 250 min,the gpu is to 512.

Speed is top.
[Samsung Galaxy Nexus] KarlusHTC:
I've been using as daily driver on my Gnex since 2015-09-01 this rom cm-12.1-20150831-UNOFFICIAL-maguro.zip, the issues I have with it, is the lang to answer incoming calls (already know issue), and the other is that it cant install the latest update of Facebook. Thanks for the great work made in this excellent ROM.

P.S. how can I overclock with this ROM, to solve the lag problems?
[Samsung Galaxy Nexus] Childe89:
Well, few posts back I was telling I never had problems with SMS, and today I noticed I can´t send them... receiving works, but can´t send nothing.

Tried wipe cache and dalvik, reset APNs, create APN manually, configuring SMSC number, using alternative sms apps, custom kernel (Lucky) but still same - I can receive but can´t send... so latest build 08/31 really has some SMS bug
[Samsung Galaxy Nexus] siealex:
Do you configure SMSC correctly? Our phone requires transcoding of the number.
[Samsung Galaxy Nexus] Childe89:
I believe I do it correctly, what do you mean by transcoding the number?

Btw. I never had any issue with this, APNs were automatically there after any flash, any rom, if I was experimenting and broke something I just did reset APNs to defaults and all worked again... until this build.. so I´m assuming there is no mistake on my side, probably just some bug...
[Samsung Galaxy Nexus] chakme:
Hi again!!

Today it happened again!! I was using the phone and my battery indicator was showing 26%. I opened an app and it just turned off. No way to turn it on. Only when I put it to charge, I could turn it on. Then when it loaded for complete, (waited only the normal time to load), it was showing 0%. I'm wondering what is happening, once it turned off with 26%. Sorry, no catlog this time.

Anyone has this experience?
[Samsung Galaxy Nexus] mfg81:
Happens to my wife periodically. I thought it was because the phone was kinda beat up
[Samsung Galaxy Nexus] hgmichna:
I have a few very simple hints. They may or may not fit, but better check for these first.

1. One possible cause could be loose or dirty battery contacts.

2. Another could be that the battery is old and worn. To check for that, dial *#*#INFO#*#* or *#*#4636#*#* , tap "Battery information" and check "Battery health".

3. Yet another cause could be that the battery has not been charged from totally empty non-stop to totally full in a long time, like several weeks. This looks to me like a fundamental Android defect, but we cannot change it, so we have to do it occasionally to recalibrate the battery charge display.

If these three do not hit home, then please ignore this message and look for some other cause.
[Samsung Galaxy Nexus] Childe89:
That´s the sign of faulty battery in most cases. Try calibrate the battery with some battery calibrator from google play (they work almost same, wait till its charged to 100%, then click calibrate to delete battery stats).

It´s also common problem with low quality replacement batteries, which do it from the first use.
[Samsung Galaxy Nexus] garrymar:
[MENTION=2633638]Ziyan[/MENTION], thank you for the build 8-31. I noticed following details using the build for week: applications became more responsive then in build 8-6; black screen bug during incoming call became 100% reproducible (have to wait 5-7 seconds every call), absolutely no problems with SMS, 3G. Update was completed using dirty method. Thanks!
[Samsung Galaxy Nexus] bamtan2:
Every Galaxy Nexus owner owes themselves a new battery anyway ;) "Calibrating" won't do anything because Android apparently does that when it starts up. Here's the battery I bought: http://xdaforums.com/galaxy-nexus/general/rom-kernel-using-t2738831/post61555946#post61555946
[Samsung Galaxy Nexus] Childe89:
I managed to repair my SMS sending problem, following instructions in this topic:

http://xdaforums.com/showthread.php?t=1916507

Long story short: SMSC number needed to be converted in correct PDU format, and then changed in *#*#4636#*#* menu.

Instructions from topic (credit goes to ryu-x)

1.) Open up PDU Encoder

2.) Insert your desired SMSC Number in the SMSC Field

Leave the receiver field blank

Alphabet Size should be 7

Delete the "how are you?" so that it is blank

Convert it

3.) On the hexadecimal PDU Message dont use the first field (AT+CMGW=x)

We will use the PDU Message on the second field

In my Case (Hutchison 3G Austria) 06913466006006110000910000AA00

4.) On your phone enter the phone number *#*#4636#*#*

Go to telephone info and click on the SMSC Tab (which is blank at the moment)

Enter your PDU Message from above

Click on the First Refresh Button (it should display update error, this is normal)

Click on the second Refresh Button (in this case it could display the number or still give you an error - but should work nonetheless)
[Samsung Galaxy Nexus] siealex:
DO NOT enter the whole message. Enter the first byte (06) and the corresponding number (6) of following bytes: 06913466006006.
[Samsung Galaxy Nexus] erOzeOz:
Hello everyone,

Has anyone tried lollipop kernel full_auto with this ROM?

I get terrible lags when using it (I didn't try it with Nephilim v5 settings) and wonder what could be the reason.

I'm on f2fs on cache and data in case this has an impact.

Thanks!
[Samsung Galaxy Nexus] zieruchan:
Same here, don't post here, because this is just fullauto, because using lucky k with cm 12 is really smooth.
[Samsung Galaxy Nexus] diogofd8:
[MENTION=2633638]Ziyan[/MENTION]

Everything works great in the latest release, I've noticed that if we keep the device with few apps it is smooth and stays smooth for weeks! Congrats!

Still, I'm using Google Launcher and Google Keyboard because Nova Launcher and Swiftkey were redrawing or force closing because of the ram too much, rendering the device pretty slow... Is there a way to prioritize their behavior in the ram management so they are kept open for more time rather than other apps opened after those? Lancher and Keyboard from Google don't behave agressively like that so there must be a way ^^
[Samsung Galaxy Nexus] christianpeso:
Once you go into Nova settings and scroll to the bottom and hit Advanced. Their is an option that says "Aggressive Desktop". Supposed to keep the launcher in memory. Never used that option myself. Turn it on and give it a try.
[Samsung Galaxy Nexus] hgmichna:
I use the same build also, but do not have the delay on incoming calls problem. The call sound and the screen come simultaneously. Just experienced this two times.

I had used the phone for other things a couple of minutes ago though. Perhaps the problem occurs only when the phone has been sleeping for a long time?
[Samsung Galaxy Nexus] diogofd8:
I already tried that. I don't know if it's placebo effect but I think it got a little bit better. Still, there are too many redraws.
[Samsung Galaxy Nexus] ftrack:
Hi,

I have issued whenever i try to update facebook apps i am not able to complete it successfully, though it download properly but after that stuck on installing "facebook".. and its never end sometime apps auto deleted, now i again trying then its restating phone and again stuck on same message.

After 3 to 4 times installing attempt my phone is become slow and i need to restart again. Is that kind of Bug? but why its on creating issue with facebook apps?

Please anyone suggest?
[Samsung Galaxy Nexus] hgmichna:
Bad Google apps?

Could something perhaps be wrong with the Google apps you used? Just a hunch, because on some phones Facebook is a system app, which it should not be. You could try reflashing everything with these Google apps: tk_gapps-modular-pico-5.1.1-20150816-signed.zip
[Samsung Galaxy Nexus] garrymar:
Hi hgmichna,

Thank you for comments. I actively use my phone (hangout, telegram, very often incoming/outgoing calls). Even in woken up state it takes 2-3 seconds to display 'answer' button. Have you done data/cache wipe for build 8-31?

Hi [MENTION=2633638]Ziyan[/MENTION], I attached collected log during incoming call in sleep mode (black screen lasted 5-6 seconds).

Thanks!
[Samsung Galaxy Nexus] Rd. Vortex:
Am I the only one who is getting absolutely ridiculous amounts of wakelocks on this rom?

For example today I had over 1h 30min wakelock from kernel during my work day. RILJ seems to be causing some serious wakelock for my Nexus. I've limited RILJ wakelock to be allowed every 800s in Amplify and it shows 21:51 wakelock time allowed and 03:02:59:35 wakelock time blocked.

I've recently halved the time to 400s since I've been getting issues where the phone suddenly states that there's no sim card and I'm testing if blocking the RILJ wakelocks causes this. If I have the RILJ wakelock unblocked though the battery life is absolutely horrible and even now its quite damn bad (especially as I downgraded from OnePlus One since it broke down).
[Samsung Galaxy Nexus] 0s1ride:
[MENTION=2633638]Ziyan[/MENTION] I think I found the cause (and possibily the fix) about "App not installed" happening with some apks.

It was not easily reproducible because it happens only with apps that set installLocation to 2 (preferExternal) in the manifest.

You can find a detailed explanation here, along with the fix and a link to an apk to reproduce the issue (be sure to use version 1.3.3).

In the meantime, as a workaround, people who want to install said apps can force the install location to internal storage via a terminal:

su
pm set-install-location 1

(it only solves this this particular install bug, check if your log is similar to [MENTION=6890844]biglouis87[/MENTION]'s)
[Samsung Galaxy Nexus] playitlouder:
I got problems with big apps from Amazon App store (app of the day). Some of them just will not install, it tries for a while and then "install failed".

Happens on Monument Valley for example.

-->Support the idea with external storage.

Have to check on wakelocks. Battery life is not too great. Probably Ril related for me as well.
[Samsung Galaxy Nexus] ftrack:
Hi,

Can i have a link of tk_gapps-modular-pico-5.1.1-20150816-signed.zip ?

One more request can u help me which call record.. will work in? becoz mine prv one wasn't working.

Thanks
[Samsung Galaxy Nexus] hgmichna:
TK Google apps pico

The link is in this article and also again at the bottom of it:

http://winhlp.com/node/919

I don't understand what you mean by call record.
[Samsung Galaxy Nexus] scorpeeon:
Hi there!

I'm using this ROM since a while and generally I'm very pleased with it, but recently a strange thing has happened.

So my phone started to show randomly being charged while not really charging and that causes the display to turn on very regularly, killing battery life. It's probably a hardware related issue so not really related.

Anyway I tried to fix it by cleaning the port, removing the battery, etc, and after turning it back on, I see very strange things. The status and nav bar are totally black all the time (like in the Jelly Bean times), in all the apps where it should be translucent. Also, lock screen is totally black (not showing the background image), pulling down the status bar, all below gets totally black, in recent apps list all the preview images are missing (the background is in their place), and generally performance seems to be heavily degraded. It almost feels like generally hw acceleration on the UI is totally broken (though I can still see effects I don't think would be possibly without it...), but I'm not sure if that's possible.

Any ideas what can I check to find out what's wrong?
[Samsung Galaxy Nexus] 0s1ride:
Is anybody else experiencing audio out of sync with any video?

Under developer options, make sure Force high-end graphics is set to on.
[Samsung Galaxy Nexus] scorpeeon:
It worked, thanks!

So this is on by default and somehow I managed to turned it off accidentally? :)
[Samsung Galaxy Nexus] hgmichna:
It was on by default on my phone.
[Samsung Galaxy Nexus] :
[MENTION=2633638]Ziyan[/MENTION]

Thx Ziyan for this great cm12.1 maguro rom. I'm really enjoying our maguro with cm12.1. This combo makes much more fun than the Nexus 7 (2012 - grouper) with cm12.1, unbelievable ! :)

Keep us updated with fresh maguro updates, please!

Thx again for your great work!
[Samsung Galaxy Nexus] shishimaru1000:
How's general stability and performance compared to cm 11 snapshots?
[Samsung Galaxy Nexus] loryevolution:
Bug Report

When I share a video with whatsapp, the video is corrupted and becomes all green and moved. Thanks for the support
[Samsung Galaxy Nexus] ed10vi:
Hello and tanks for this great ROM [MENTION=2633638]Ziyan[/MENTION].

I've had some problems

I've disabled lowram in build.prop because I use a lot the Google Camera Photosphere:

This happened to me with cm-12.1-20150805-UNOFFICIAL-LOWRAM-maguro.zip. I was recording a GPS track with Strava and shoting a Photosphere when the phone turned off (Battery stats screenshot)

With the latest build I can't cut a video with the galery app or Telegram

When I decrease the green gamma the whole screen goes green. I attach a photo because this doesn't appear in the screenshots
[Samsung Galaxy Nexus] hgmichna:
I'm not an expert and cannot be sure, but I would be surprised if you could run two RAM-hungry apps at the same time on the Galaxy Nexus on a big operating system like Android 5.1.1. People have voted for the low_ram flag for a reason.

This may or may not cause the phone to shut down. Actually, the shutdown looks to me like the old Android defect that it cannot keep track of the charge level, particularly when you have not charged it continuously from 0 to 100% recently.

Your battery may be old on top of that, and the high processor load during photo processing may have increased the current drawn from the battery, causing its voltage to drop below the battery electronics emergency level, leading to an immediate cut-off, i.e. not an oderly shutdown.

This is speculation, but the circumstances fit this scenario very well. How old is your battery? Have you measured its capacity? Does the phone still recognize the battery as good? (Dial *#*#INFO#*#* or *#*#4636#*#* to find out.)

In any case this is not a ROM problem.