yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] :
I did not dirty flash, this was a clean install of 01/02 with squid kernel r14b, and open gapps mini.

And I only have one theme, its a cm13 theme, and I'm puzzled as its been installed since 01/02, and these strange display errors just started yesterday.

Now done full wipes, reflashed and everything is fine, music player working as is wifi, and the theme is still installed, if I use it, setting and sub menus opens as normal.

Edit

After 24 hours, the problems has persisted, I uninstalled the theme a couple of you suspected was the culprit, unfortunately, this hasn't resolved the issue.

I've just done another clean install, and still I'm seeing these strange display or graphical errors, especially pressing the back button........

No themes installed at this time.

Setting menus just display alot of unreadable garbage at times.

I'll keep my eye on things, but I have no desire to move to another ROM, this was fine until yesterday.
[E 2015 Original Android Development] spiked_mistborn:
Things seem to be working pretty good except for a couple of issues. I've noticed that sometimes after Ambient Display activates it fails to turn off the backlight. You have to be in a dark environment to notice it since it's just showing a black screen. Pressing power to turn the screen on and then back off turns the backlight off, but it doesn't happen all the time, so if it happens and you don't catch it you could be looking at high battery drain.

Another problem is the phone app message "Invalid Number" that it shows in a dialog box if somebody hangs up the phone before you do. Here's a logcat.

I have had these issues in both the 12/25 and 2/01 builds on my xt1527.
[E 2015 Original Android Development] blacksh4dow:
I noticed the same problem with Ambient Display.
[E 2015 Original Android Development] xukashi:
me too
[E 2015 Original Android Development] Sher1234:
Ya facing same problem here and also facing 4g & 3g network issues also

On CM13 01/Feb/2016 Build

XT1521 - India
[E 2015 Original Android Development] TheDarkAhead:
AudioFX

Is it me or does the equalizer only work intermittently, like really, really rarely.
[E 2015 Original Android Development] sirhc:
Ambient display has had this issue for awhile and it does result in high battery drain, that's a Cyanogen issue, something with their code when they made Ambient Display
[E 2015 Original Android Development] :
I've not noticed any difference in the equalizer, whatever settings I have, I don't think it's working, but that's just my opinion......

Still having these very strange display issues, but only in the setting menu, is anyone else experiencing this?

BTW clean install with wipes of 01/02 build, squid kernel r14b and open gapps pico.

I did flash resurrection remix earlier but that crashed on the welcome/start screen and I've reflashed this again.
[E 2015 Original Android Development] sirhc:
Equalizer is trash, working or not working. No offense, but it screws up the audio worse than before. Even Motorola's stock equalizer works more effectively
[E 2015 Original Android Development] squid2:
I've known of this issue for quite a while. It's been happening ever since the start of CM12.1, and it affects the entire Motorola MSM8916 family of devices (surnia, osprey, and lux). It usually turns off the backlight, but sometimes it doesn't, and as you say, when it doesn't turn off the backlight, it drains the battery quickly. I've turned off Ambient Display on my lux because of this bug (turning it off prevents this issue from happening).

It has been on my radar for quite some time, but the nature of the bug makes it non-trivial to debug, and I haven't found time to more seriously attempt fixing it. I consider the bug to be the largest family-wide issue for MSM8916 CyanogenMod for Motorola devices.

I have found that ambient display and MotoDoze work fine on otus (no backlight staying on bugs there). This means that the bug is either:

In our MSM8916 family kernel

In our CMActions implementation

In a MSM8916-specific CM HAL

---------- Post added at 09:41 PM ---------- Previous post was at 09:32 PM ----------

From my experience, it seems to only work for software playback but not in compress offload. For CM12.1 on lux, I had ended up disabling hardware offloading of audio effects to avoid this issue, though I'm not sure what the others in our group's view on this is. Forcing software playback increases battery drain compared to offloaded decode, but flaky AudioFX is annoying and more of a bug.
[E 2015 Original Android Development] sirhc:
Ive studied the entire code for CMActions in attempt to fully integrate it into CM. I'm assuming it could be their Pickup or Wave gestures causing the backlight issue
[E 2015 Original Android Development] Prithvi Raj Singh:
Any new builds?
[E 2015 Original Android Development] Thexmastermind:
You're the worst.
[E 2015 Original Android Development] Kenny13554:
http://xdaforums.com/search.php?searchid=404465766

I just love reading through your "contributions" :D

Patience is the key. But seriously, this rom works fine for 99,9% of the cases...
[E 2015 Original Android Development] GeorgePr:
Bug on the 20160220 build: when I turn off the wifi, the device hangs for a second and then hard reboots (though it doesn't ask for pin).
[E 2015 Original Android Development] sirhc:
A build isn't needed everyday man, I feel like the nightlies get the best of people. The ROM is pretty solid as is right now. Be patient ??
[E 2015 Original Android Development] bigblueshock:
I saw some posts mentioned regarding Waze here...

I do see it unresponsive shortly after starting up too. I can put my destination in, it will start my routing, I will be driving, but the direction texts is frozen for a while and I can't move the map around on the screen.

I can still see my car moving though, which is odd. After a while it starts working and is responsive again. This is on multiple CM13 based Roms, so I am unsure what the root cause is.
[E 2015 Original Android Development] spiked_mistborn:
I have the same problem. They are supposed to have a new version number of Waze coming out soon, so hopefully it will be fixed then.
[E 2015 Original Android Development] bigblueshock:
I am part of the Waze 4.0 beta, and unfortunately it is not fixed in the Waze 4.0 beta yet. It has the exact same issue; will freeze for about a half a minute or so, and then work flawlessly afterwards.

My co-worker with a Nexus 6P does not have this issue (he is on 6.0.1 like we are).

It also doesn't seem to be memory related, as I have around 250mb free RAM at any given time, even while waze is running. Unless android is somehow compressing the memory and that's whats causing the problem. The 6P has 3GB RAM, my HTC m8 has 2GB RAM, this Moto E with the problem has 1GB RAM
[E 2015 Original Android Development] spiked_mistborn:
It could be a permission error. I think Waze uses webview to draw some user interface items. The "draw over other apps" permission is greyed out also.
[E 2015 Original Android Development] ctenc001:
Can anyone confirm if this build supports band 12 for model XT1527?

Do all Cyanogen builds support band 12?
[E 2015 Original Android Development] spiked_mistborn:
As far as I can tell it depends on your baseband. I have only seen band 12 working with the original 5.0.2 baseband, which I am currently using myself for that very reason.
[E 2015 Original Android Development] sirhc:
Band support isn't Software specific, but baseband specific. You can block the option via Software but as long as the baseband/hardware supports it, it'll always be there
[E 2015 Original Android Development] bigblueshock:
I think you're getting somewhere with that. I don't have webview installed, and I wonder how/if that affects anything. I did install it at one point and it still was freezing, but I wonder if I have to change permissions to Waze once webview is reinstalled.
[E 2015 Original Android Development] sirhc:
Webview should already be preinstalled unless things have changed? Granted it's most likely a different version (AOSP)
[E 2015 Original Android Development] cm4M&o:
Decryption Unsuccessful...

Since today I use CM 12.1 and now I want to give CM13 a try. After flashing the ROM from 10-jan to a clean system (wipe system, data, cache, dalvik) I rebooted and was ask as for my encryption password. I entered it but I got a message "Decryption Unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. ...". What do I need todo more ?

System details: XT1514, recovery: TWRP 3.4.5-r1, encrypted within CM12.1
[E 2015 Original Android Development] Thexmastermind:
I got that message once. You have to do a full wipe via adb. Type in help on the terminal and it gives a list of accepted commands, it should be something like -s
[E 2015 Original Android Development] cm4M&o:
Thanks, I tried the Format data in TWRP and it works too
[E 2015 Original Android Development] Thexmastermind:
That's good. But it still just wiped it right?
[E 2015 Original Android Development] cm4M&o:
No, I would assume its a real format, because type changed from f2fs to ext4
[E 2015 Original Android Development] switcher:
[MENTION=4919084]vivekspanicker[/MENTION]

same here, but how did you go into settings ?

My device is already getting dark in the setup (when asking for language), after choosing language there is not return :crying:
[E 2015 Original Android Development] DSchwarz47:
Im on xt1527, i installed the gapps and everything boot ok but when i select the language the screen turns black and i can only hear the lock/unlock tone, the screen doesnt turn on , only if i reboot, but is the same thing.

Returning to 12.1 until its solved. Thanks
[E 2015 Original Android Development] openhacker:
Guys, I think the issue is related to init. I will fix it soon enough. But please do give me a logcat. I have the same build working flawless on my phone. :/
[E 2015 Original Android Development] debojyotidey:
did u clean flashed the build or dirty flashed over cm12.1?
[E 2015 Original Android Development] switcher:
[MENTION=6999328]openhacker[/MENTION]

Where do i find the logcat, waiting for your instructions , tia
[E 2015 Original Android Development] openhacker:
New build's up with fixes that are *suspected* to cause the blackscreen bug.

Again mentioning, this build still works flawless on my device.

Need testers on this build.
[E 2015 Original Android Development] entony80:
same thing with new build, full wipe and installation with gapps but as soon as I select the region blackscreen

Test on XT1524

edit: I try an installation without gapps.... same result blackscreen
[E 2015 Original Android Development] openhacker:
This is bad :rolleyes:
[E 2015 Original Android Development] entony80:
do not worry you'll be able to solve the problem, I await new builds... :good:
[E 2015 Original Android Development] openhacker:
I can even shoot a long video to show you guys that I am currently running this build on my device. No flaws, nothing. Just smooth. :rolleyes: I contacted the other devs who themselves facing such issues in their builds.. have to check the source code :rolleyes: give me time guys, sorry for wasting your bandwidth
[E 2015 Original Android Development] entony80:
not have to worry because what you do is not an obligation then search the problem to solve it, I can not pull off a log for you also because it is the only device use
[E 2015 Original Android Development] grofweg:
[MENTION=6999328]openhacker[/MENTION] Please remove the Stable status from the OP. Thx. It's a bit misleading.
[E 2015 Original Android Development] Kahroo:
Ok nevermind I was able to get to the recovery,
[E 2015 Original Android Development] Rydes12:
If someone have black screen bug, try flash twrp again. in my xt1524 works
[E 2015 Original Android Development] Agusyc:
I'm going to test and report on XT1527.

I'm making a Backup of my current ROM, downloading this and Gapps.
[E 2015 Original Android Development] :
I just tested this on my Boost Mobile XT1526. Mainly so I could try to provide a logcat. I flashed the latest build along with OpenGapps and I got the blank screen during initial setup, after I chose my language. It sounded like the screen locked itself but wouldn't unlock. I could hear the lock/unlock sound. I attempted to get a logcat but wasn't able to. I wasn't able to enable USB Debugging so I could get a logcat using ADB.

If you could provide a build that has USB Debugging temporarily enabled at first bootup I could provide a logcat but right now I'm not able to provide a logcat. Sorry.

Only thing I can tell you is that I'm assuming 3G was working because I saw the phone had 3G before the screen went blank.
[E 2015 Original Android Development] Agusyc:
I get the black screen after I choose language. D:
[E 2015 Original Android Development] debojyotidey:
means after flashing rom we have to flash the twrp recovery again?
[E 2015 Original Android Development] scritch007:
ADB and logcat are disable by default. If you want to enable it, you have to edit the boot.img

in the default.prop

ro.adb.secure=0
ro.secure=0
persist.sys.usb.config=mtp,adb

and then repack the boot.img

Be carefull though if rom was booted, the persist.sys.usb.config can have been set to the previous value in data/cache, so you'll have to clean to have it fully working

Regarding the xt1526 devices, this build (if I understood correctly) is built upon the commonized repository we are working on. The original device for this repo is osprey, the changes for the boost devices have been removed from surnia, but one good thing is that osprey's user only have to flash the correct apns.xml files + add a few lines in the build.prop and they have 4G working for VM/boost/sprint

All the blobs have been commonized and only the sensors and the camera blobs are surnia specific, this is why we are getting some issues now that aren't there on my CAF build nor in cm12.1. Strange thing about the black screen is that I got it once, and now I'm all fine...

Let's hope I get it to
[E 2015 Original Android Development] :
Thanks scritch007. I still have the ROM zip on my external SD card. Tomorrow I'll see if I can pull the boot.img from it and add/modify those lines you mentioned. Once I figure out how to unpack boot.img under Debian.
[E 2015 Original Android Development] milkyzongs:
Just flashed "cm-13.0-20160110-UNOFFICIAL-surnia.zip" onto my xt1526 sprint/boost varient.

Looks as if the sim/3g isn't working right off the bat, is there a way to get this working? While reading through the thread it looks as if there are some lines of code to be added in order to make it work, anyone care to elaborate?

I'll be sure to post logs if nessecary. (need to root first, will edit when complete)
[E 2015 Original Android Development] spiked_mistborn:
You're right that AOSP webview is installed by default probably unless it's getting replaced by a particular gapps package or it's selected in aroma gapps. I use opengapps nano just to keep everything aosp except calendar. I just installed the google webview from the playstore and disabled the aosp webview, and after testing Waze a few times I haven't had the UI freeze at all, at least so far. Hopefully that fixed it. I have been on AOSP webview so far because I think there were some issues with early Android 6 builds, but I think that was related to permission problems.
[E 2015 Original Android Development] sirhc:
Yea I remember the AOSP webview issue before on Lollipop builds where the package was incorrectly named, causing Webview dependent applications to crash lol Glad you got it working ?
[E 2015 Original Android Development] bigblueshock:
It looks like builds as of 2/13 could have fixed this. I do not notice any more freeze ups in Waze.

At least the Teamsek version I am using, there are no more issues. Probably across the board.

---------- Post added at 08:06 AM ---------- Previous post was at 08:03 AM ----------

Interesting... What is the AOSP Webview actually called? I'm in apps, maybe I'm missing it...

Or maybe it was completely removed in the 2/13 version, which is why Waze is working for me now and I didn't touch anything, haha
[E 2015 Original Android Development] spiked_mistborn:
Make sure you select "Show system" in the menu. It shows up as Android System Webview. The AOSP version has a globe icon, com.android.webview package name, and is 2.8MB, while the Google version has a gear icon, com.google.android.webview package name, and is 57MB. Depending on the gapps package that you install it could either leave the AOSP version in place or replace it with the Google version.
[E 2015 Original Android Development] bigblueshock:
Bingo!!!! Thank you. I disabled it and installed the Market Place version.

I have opengapps micro installed. Didnt seem to include/overwrite the webview
[E 2015 Original Android Development] blacksh4dow:
[MENTION=6485916]squid2[/MENTION] can you compile new build?
[E 2015 Original Android Development] Orbiting234:
GPS not working in this yet from what I can tell. Anyone confirm?
[E 2015 Original Android Development] dandrumheller:
Haven't been on this in quite some time, but GPS worked for me. Try the GPS status toolbox app in the play store - I've had luck in the past using that to unhang stuck GPS.
[E 2015 Original Android Development] squid2:
February 20 Release

Here you go: http://www.mediafire.com/download/cg90f7sbow2po5t/cm-13.0-20160220-UNOFFICIAL-surnia.zip
[E 2015 Original Android Development] ManuelLima1994:
hello, a question [MENTION=6485916]squid2[/MENTION] because not compiled as often as other roms?

The live display doesn't work in automatic mode

only I happen to me or anyone else fails you live display?

Sorry for my bad english (:
[E 2015 Original Android Development] spiked_mistborn:
Auto live display is still working fine on my xt1527 after dirty flashing the Feb 20 build + r15-legacy kernel coming from squid2's Feb 1 build.
[E 2015 Original Android Development] blacksh4dow:
Thank you ;)
[E 2015 Original Android Development] ManuelLima1994:
[MENTION=4978031]spiked_mistborn[/MENTION], I do not understand, and because my not work me when in automatic mode :(? I do full wipe and install I do wrong? I can clear this up Bro?
[E 2015 Original Android Development] spiked_mistborn:
What ROM are you coming from? Does it work if you pick day or night? If it was working on an earlier build of cm13 for you maybe you could restore a backup (hopefully you made one) and try dirty flashing the new build (no wipe).
[E 2015 Original Android Development] ManuelLima1994:
[MENTION=4978031]spiked_mistborn[/MENTION] I currently use the ROM is cm12.1 the official build of today's date 20,160,220, the live display if it works if you manually eligo day or night, in automatic is when you do not want to change, as bro was saying last night the install before that I always make a backup with TWRP my current rom, then I did a wipe to art cache, data, system, internal memory and cache and then deliver this to CM13 20160220 Unofficial, well as extra information probe by the same procedure backup and full wipe with AOKP ROM and recompiling the 10th of rom @ squid2 but the live display in automatic mode does not want to change even late at night

What do you advise me bro for the live diplay work as making the switch should only do it manually without automatic?
[E 2015 Original Android Development] xukashi:
Changelog?
[E 2015 Original Android Development] hehk1234:
Thanks [MENTION=436307]squid[/MENTION] for your awesome work here, can you release the next update on OTA ? With changelog ? Everything I've test here works fine on my moto E2 LTE (Dual sim). Thanks bro :)
[E 2015 Original Android Development] harryspar:
Are you in the USA? The Sprint/Boost is hard locked and GSM cannot be used at all in the USA.
[E 2015 Original Android Development] xtermmin:
He didn't mention if he was trying to get the XT1526 running on a GSM operator, but it actually does have active GSM hardware (just have to change LTE/CDMA to LTE/GSM in the Phone Testing menu). The Sprint/Boost variants of the XT1526 are SIM locked though, so you need to get it unlocked via Sprint/Boost before you can use it on other carriers. The USC XT1526 is SIM unlocked by default.
[E 2015 Original Android Development] Black_reaper:
LED notifications support?

Does this ROM support LED notifications for surnia? I had heard that the LED present in the phone can be used with CM. Anyone please let me know.

Thanks!
[E 2015 Original Android Development] Sher1234:
Yes LED works great on cm & it also works on cm13 unofficial
[E 2015 Original Android Development] spiked_mistborn:
From what I can tell Live display is triggered based on time and not your physical location on the planet. Check under Settings / Date & Time and make sure your time and time zone are correct if they are set automatically. If I manually set the time I can trigger Live display to change around 6:45am when it is in automatic mode. It shows something like this in the logcat:

02-21 07:00:00.478 D/LiveDisplay( 788): Adjust display temperature to 5451K [r=1.0 g=0.93512034 b=0.87496614]
02-21 07:00:00.513 D/LiveDisplay( 788): Adjust display temperature to 5555K [r=1.0 g=0.9422893 b=0.8883116]
02-21 07:00:00.546 D/LiveDisplay( 788): Adjust display temperature to 5658K [r=1.0 g=0.949219 b=0.9013209]
02-21 07:00:00.561 D/LiveDisplay( 788): Adjust display temperature to 5711K [r=1.0 g=0.95273095 b=0.9079484]
02-21 07:00:00.579 D/LiveDisplay( 788): Adjust display temperature to 5764K [r=1.0 g=0.9561778 b=0.9144942]
02-21 07:00:00.595 D/LiveDisplay( 788): Adjust display temperature to 5812K [r=1.0 g=0.95928127 b=0.9203992]
02-21 07:00:00.612 D/LiveDisplay( 788): Adjust display temperature to 5864K [r=1.0 g=0.9625842 b=0.92672056]
02-21 07:00:00.628 D/LiveDisplay( 788): Adjust display temperature to 5914K [r=1.0 g=0.9657393 b=0.93277174]
02-21 07:00:00.645 D/LiveDisplay( 788): Adjust display temperature to 5960K [r=1.0 g=0.96859294 b=0.9382747]

Hope that helps.
[E 2015 Original Android Development] hehk1234:
Works everything :)
[E 2015 Original Android Development] Titanosx:
Guys i tried to instal this rom on my Moto E XT1524, but when i flashed it with gapps Micro/Full/Stock (triend them all). after everything was installend. When booting up i kept getting instalation wizzard stopped working it kept spamming and some google play services stoped worked also. Made it imposible to instal the phone and not use the ROM.

Do's anyone know what the problem is? and can someone maybe help me out because i would really like to work with CM13.

Thanks!

I Got CM 12.1 Nighly's working on it now, but their is a bug i cant use my SD card whatsover on it. So please help :)
[E 2015 Original Android Development] sirhc:
Do a full wipe and Flash GApps right after you flash the ROM
[E 2015 Original Android Development] Titanosx:
i did that like 4 times :(, no good so far.
[E 2015 Original Android Development] Titanosx:
Can Someone help me out?

Or can you give me the link too the proper Gapps?

Thanks!
[E 2015 Original Android Development] PriPhaze:
You dont need to double post.. with a simply edit is enough..

Ehm there are a lot of gapps out there and i always use Open Gapps pico

But you can algo get A-gapps or slim gapps etc and try out
[E 2015 Original Android Development] Titanosx:
Ill give Open Gapps a try, just to be clear it is Arm 6.0 Right?

Thanks for your help!
[E 2015 Original Android Development] PriPhaze:
Yes is arm Open gapps pico is what i use
[E 2015 Original Android Development] Titanosx:
It finally works now thanks! only camera is bugged now. I can shoot 1 photo, the its freezes/stops.

But have cm13 now so im happy, now only the camera haha