yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] murso74:
Got this a few times
[X 2014 Original Android Development] nanca:
murso74 this could be an app issue. is it ready to be used on 5.1?

i'm using nokia's solution for gps navigation. works like a charm.

btw, despite of this, are you happy with this last nightly?
[X 2014 Original Android Development] nerotix:
[MENTION=3857343]crpalmer[/MENTION] Small bug report: when using chop chop to turn flash on and chop chop again to turn it off again, when you go into quick settings, the flash light icon still shows as the flash light being on.
[X 2014 Original Android Development] 0.0:
I've reported this too and a fix for now is to remove the flashlight quick setting tile
[X 2014 Original Android Development] murso74:
Happened on Waze and maps
[X 2014 Original Android Development] FooBazza:
ROM looks promising. Might try out once I finish developing a working AOSP kernel for victara and try building for CM-based ROMs as well :good:
[X 2014 Original Android Development] sudhamsu:
Delayed response in adaptive brightness

Is it just me or the adaptive brightness seems slow in adapting to ambient light changes? Even compared to stock, it seems slow. CM11 used offer a sensitivity setting (low, medium, high) in the auto-brightness settings. Can anyone else confirm if its too slow on their device? It takes anywhere between 2-5 seconds before adjusting, while on stock it was definitely faster than that (or at least felt like it). [MENTION=3857343]crpalmer[/MENTION], is it possible to increase this sensitivity? Or make it configurable by user?

Also, the ambient display invoke upon hand-wave seems kinda slow.
[X 2014 Original Android Development] alvareo:
It's slow since CM12. Sometimes I unlock my phone on broad daylight and the brightness is at the lowest for about seven seconds.
[X 2014 Original Android Development] crpalmer:
Danny Baumann seems like he was trying to fix the slow reaction to high brightness, but never pushed it:

http://review.cyanogenmod.org/#/c/93027/1
[X 2014 Original Android Development] Flamehell:
[MENTION=3857343]crpalmer[/MENTION] Tnx mate,the last nightly(20-04)is running sweeeet!!!:)
[X 2014 Original Android Development] sudhamsu:
Alrighty then. Let's see where that goes.

Adding a number to this: It takes a full second to begin fading in, and some more to reach it's full brightness. Can we decrease the time lag before invoke and increase the fading speed?

Been testing the User-aware display. The sensitivity surprised me! I read somewhere long ago that the IR sensors in our devices sense up to around 6-8 inches. While that's true for gestures like wave, the real maximum distance that it can sense seems to be around 12-13 inches. The User-aware display works well with such sensitivity. And I like that it switches of the screen quickly when there's no object in front of it and the timeout has already passed. This also addresses the issue I raised a few posts back. Awesome work here!

I was suspecting that range limitations of IR-sensors will limit the feature. But, so far, so good. Will test further...
[X 2014 Original Android Development] tacosrdelicioso:
I've tried 8/16 on up none worked for me. So I'll try flashing a baseband but I think I already have the latest

---------- Post added at 03:12 PM ---------- Previous post was at 03:08 PM ----------

Yeah I already have 13r. I'll try flashing anyway. Hmm [emoji20]

---------- Post added at 03:30 PM ---------- Previous post was at 03:12 PM ----------

It thinks I have a 1095 and baseband isn't read. Idk. I've been flashing ROMs since the droid incredible days. Never has one of my devices been so confused. Ugh! Frustrated
[X 2014 Original Android Development] invisiblek:
Weird...can you pastebin the output of: adb shell getprop

For me please?
[X 2014 Original Android Development] tacosrdelicioso:
Huh. Device not found

http://pastebin.com/sdQFKRhJ
[X 2014 Original Android Development] invisiblek:
if you're already in an adb shell, just issue: getprop
[X 2014 Original Android Development] tacosrdelicioso:
Oops lol

http://pastebin.com/zaECh2T0
[X 2014 Original Android Development] :
Are you guys using the stock kernel or another developers ?

I've been noticing that my battery has been dying quicker and my phone has gotten a

way lot hotter than before.

Currently on 8-23-15 [nightly_build]

X1095_TMOBILE_TOWER=IPV6

Also find me on #cyanogenmod [MENTION=3207252]samthewildone[/MENTION]
[X 2014 Original Android Development] Amisuta:
Using the only other kernel, render kernel. Works fine
[X 2014 Original Android Development] :
Fixed. Thank you.View attachment 3450391
[X 2014 Original Android Development] tacosrdelicioso:
Any ideas?
[X 2014 Original Android Development] Nebelschwaden:
Anyone else getting an awesome battery life lately?

At the moment the phone is running for about 24 hours and I got little over 5 hours of

screen on time. (cannot attach a screenshot somehow....)

I am on 20150819 with stock kernel.
[X 2014 Original Android Development] AntsInMyPants:
I am having the exact same issue. CM thinks my Verizon XT1096 is a XT1095 and won't recognize the SIM Card. If I revert back to mikeoswego's stock 5.1 everything works fine.

Is there a build.prop edit that will make it recognize it as a XT1096?
[X 2014 Original Android Development] invisiblek:
This should be fixed in the latest nightly.

http://review.cyanogenmod.org/#/c/107600/
[X 2014 Original Android Development] :
View attachment 3451009
[X 2014 Original Android Development] mcardielo:
The next nigtly will contain motorola specific permisions for play store moto apps, loking foward to test it.

http://review.cyanogenmod.org/#/c/106208/
[X 2014 Original Android Development] tacosrdelicioso:
8/24? Or wait until 8/25 is up
[X 2014 Original Android Development] :
No, not 24, the next build...

http://www.cmxlog.com/12.1/victara/

init: use ro.boot.cid for variant determination (android_device_motorola_victara)
[X 2014 Original Android Development] bongostl:
My phone gets a black screen of death when i am on the phone and a call comes in for callwaiting.

Has happened on the last few nightlies. I am NOT using any custom kernel, etc...

Anyone else?

XT1095
[X 2014 Original Android Development] nanca:
same problem mate!!!! i figured out that pushing the power button while ringing wakes up the screen so you can answer the call.

(trying to logcat it, but this issue seems to be random. also, its better to use an app for that or logcat it using adb on computer? i got this command: adb logcat -v long > name of problem.txt. is it the right one to help you? )
[X 2014 Original Android Development] tacosrdelicioso:
Version is fixed but no baseband no sim no service issue remains
[X 2014 Original Android Development] :
Sorry, a bit off-topic...

After some fiddling, I was able to install Moto Camera 5.0.21.4, it seems to be working...

When you launch it, and swipe right to get to the camera settings, there's a button at the bottom right that takes you to pages with dezens of advanced settings.
[X 2014 Original Android Development] AntsInMyPants:
Same thing here.
[X 2014 Original Android Development] alexfiorani:
Last Friday I updated from 12/08 to 21/08 nightly and started having some random reboots. The strange thing is that I didn't actually see any of the reboots, and the only way of knowing they apparently happened is because of 2 things: first, there is a 'blank' bar at the battery stats (like when you flash a rom and there is a gap between the moment the phone powers off and on again. Second: there is a difference in the 'uptime' displayed in the settings and the one displayed on better battery stats. The uptime displayed in BBS checks with the blanks on the battery graphs, and that is strange. So, to give an example, I rebooted the phone and went to sleep. When I woke up I saw that around 6 am there was a big gap at the battery graphs, and the uptime according to the phone was 9 hours (from when I rebooted to that moment) and the BBS data showed 4 hours of uptime. Has anyone seen anything similar to this? As I never saw the reboots, nor was asked pin or SIM pin at any time (maybe because it is a soft reboot?), I don't actually know if this is some battery data problems affecting the graphs and BBS raw data or if the reboots are really happening. I returned to 12/08 and everything is fine. Thanks for the attention.
[X 2014 Original Android Development] Tommebaas:
Where can I report major bugs?

Sent from my Moto X
[X 2014 Original Android Development] JuggaloDroid:
To my knowledge, Jira is the place to do that.
[X 2014 Original Android Development] tacosrdelicioso:
Hope they get to the bottom of it soon so I can run carbon haha
[X 2014 Original Android Development] adm1jtg:
can someone post one of the older builds mentioned in the earlier posts, the builds where the "no bass" issues were not present. I think it was mentioned like 8/18 or so.

Thanks
[X 2014 Original Android Development] Munns86:
It looks like in the latest build (8/25) users are now able to download Motorola only apps from the Google Play.

So far I've only tested the Moto camera app and it works well. A little slower than on stock.
[X 2014 Original Android Development] :
Is the slowmo video recording working?
[X 2014 Original Android Development] 0.0:
Nope. Slowmo probably requires Moto framework code, which CM does not have

sent from my Moto X Pure Edition
[X 2014 Original Android Development] bongostl:
Constant chrome fc on newest build. Anyone else?
[X 2014 Original Android Development] 0.0:
A commit broke it. Next nightly, it'll be fixed

sent from my Moto X Pure Edition
[X 2014 Original Android Development] Gafanhotz:
Deezer just started to reboot my phone like crazy, I believe it's connected to the use of DRM (Widevine libs?), did anyone else has any issue with Spotify, Deezer or Rdio?

I can't upload an last_kmsg right now but I'll do it tomorrow asap. Couldn't get a logcat yet though, always happens randomly.
[X 2014 Original Android Development] adm1jtg:
Testing rdio now and so far no issues.. Also listened to Pandora for a few hours yesterday and also no issues. Build from the 26th with render Kernel
[X 2014 Original Android Development] dg4prez:
Anyone able to use a wired headset on the phone? When I use mine the mic doesn't appear to work. Works fine on Bluetooth.
[X 2014 Original Android Development] vista178:
I'm not getting a mobile data link when flashing from the 5.1 stock image to the latest nightly 20150826. Anyone else having this issue? I've read several pages back and some are having similar issues but seemed to resolve them when they updated their modem. I'm already on the 5.1 modem.

Phone: XT1096 (Verizon)
[X 2014 Original Android Development] Tommebaas:
I flashed an other rom called Euphoria OS from june.

The music sounds so much better :)

I'd suggest you flash that rom.
[X 2014 Original Android Development] :
Chrome crashing seems to be fixed now. Thank you.
[X 2014 Original Android Development] crpalmer:
Can someone provide a link (either here or PM) and specific playback instructions (app used, output device, etc) that has significantly worse audio quality now (the more extreme difference the better)? I don't notice any problem but I only ever listen via Bluetooth so I don't know what was "normal".
[X 2014 Original Android Development] Aroch925:
I'm having the same issue with the xt1096. It says the baseband is unknown and it can't detect the sim card. I hope this is fixed soon
[X 2014 Original Android Development] tacosrdelicioso:
Nope the issue hasn't been resolved yet
[X 2014 Original Android Development] adm1jtg:
new to cm and am having 2 MINOR issues that I haven't seen listed anywhere....

1) Under sounds/interruptions "When calls and notifications arrive" I set to ALWAYS INTERRUPT. I then setup downtime for appropriate times and days and only select to allow calls. Everything works great until I reboot, after the reboot the "When calls and notifications arrive" setting is set to allow only priority interruptions and puts the star in my statusbar. I can reset it back but it always goes back to allow only priority interruptions after a reboot. I have cleared dv and cache, updated to 8/27 build and same results. Back on 8/25 build ATM as thats what I had a full nandroid of.

UPDATE:When the downtime kicks off it does change to priority only mode as it should but again NEVER switches back, so seems the whole downtime mode isnt working right with switching the priority notifications.

2) On kk stock I had an OTG sdcard reader i used all the time. On any version of lp, stock or cm the device is no longer recognized. The light doesn't even come on anymore. Render kernel has this issue as well.

Any help on either os the above issues would be GREATLY appreciated. The cm build is great I will be staying on it just hope to get these issues resolved.
[X 2014 Original Android Development] slogar25:
I'm on the 8/26 build and on the xt1096 with Verizon working just fine.
[X 2014 Original Android Development] vista178:
Which baseband version are you on?
[X 2014 Original Android Development] slogar25:
Sorry I'm on 8/25
[X 2014 Original Android Development] mikeoswego:
I've been running the 0825 nightly since it came out without trouble.

The only complaint I have is that somehow the system time is getting mangled when I go into TWRP and the time is off by about 62 hours into the past causing the time stamps on backups to be wrong; this does not happen with the stock rom.
[X 2014 Original Android Development] vista178:
Have either of you tried the 8/27 nightly?

Edit: I just flashed from the 5.1 stock build to 20150825 and data wasn't working for me on that build either.

Edit: I've tried 20150824 and 20150827 from stock 5.1 and neither result in working mobile data.
[X 2014 Original Android Development] mikeoswego:
Probably an unnecessary question.. You have wiped data before trying the CM rom? You probably can't dirty flash from stock to CM, there are too many differences.
[X 2014 Original Android Development] vista178:
That's right, I did wipe before installing.

Edit: I also have the same baseband as slogar25.
[X 2014 Original Android Development] adm1jtg:
new to cm and am having 2 MINOR issues that I haven't seen listed anywhere....

1) Under sounds/interruptions "When calls and notifications arrive" I set to ALWAYS INTERRUPT. I then setup downtime for appropriate times and days and only select to allow calls. Everything works great until I reboot, after the reboot the "When calls and notifications arrive" setting is set to allow only priority interruptions and puts the star in my statusbar. I can reset it back but it always goes back to allow only priority interruptions after a reboot. I have cleared dv and cache, updated to 8/27 build and same results. Back on 8/25 build ATM as thats what I had a full nandroid of.

UPDATE:When the downtime kicks off it does change to priority only mode as it should but again NEVER switches back, so seems the whole downtime mode isnt working right with switching the priority notifications.

2) On kk stock I had an OTG sdcard reader i used all the time. On any version of lp, stock or cm the device is no longer recognized. The light doesn't even come on anymore. Render kernel has this issue as well.

Any help on either os the above issues would be GREATLY appreciated. The cm build is great I will be staying on it just hope to get these issues resolved.

Can anyone confirm or deny the downtime issue I listed?
[X 2014 Original Android Development] slogar25:
I actually am on Tameseks CM with no radio issues. Strange how some are having issues.
[X 2014 Original Android Development] tacosrdelicioso:
I don't get it. Maybe certain Verizon sims just won't work with it
[X 2014 Original Android Development] nanca:
My phone is rebooting like crazy all the time. Got more than 20 reboots during this day. Tried a clean install wiping partitions. No luck. Anyone else?
[X 2014 Original Android Development] G4 Man2:
Running 8/28, working fine for me.
[X 2014 Original Android Development] nanca:
Trying this one. Got a reboot a few minutes ago. =/

Please, try taking panoramic pictures using Google camera (setting the quality to high). I was doing that when it happened.
[X 2014 Original Android Development] G4 Man2:
Taken and processed just fine!
[X 2014 Original Android Development] Aroch925:
Just tried temasek on my xt1096 and it still has the same problem
[X 2014 Original Android Development] invisiblek:
Here's an interesting idea: post a log along with your mention of an issue.

Before you ask "how do I do that?" go on and google it.
[X 2014 Original Android Development] Tommebaas:
Is know one having sound issues with the latest nightly?

I can't be the only user here listening to music with my phone.

Sent from my Moto X
[X 2014 Original Android Development] vista178:
My sim works in a XT1060 running cm12.1 so I don't think this is true.
[X 2014 Original Android Development] mikeoswego:
Google Play Music is working fine for me on speaker or bluetooth. I haven't tried Eleven or wired headphones.
[X 2014 Original Android Development] crpalmer:
Two days ago I asked for information from you people have have audio problems and received no feedback.

I asked for a link to a specific file and specific information about how you are playing it.
[X 2014 Original Android Development] booyashakas:
I'm having bad sound problems as well. Well, I'm not sure if it's sound problems so much as just the low end missing in music. I've used multiple music players, shuttle, Google play, and the cm music one, all to no effect. I tried the 0.0 patch for fixing audio fx and while it did allow control then, the low end was still missing. I've also altered mixer paths to increase headset volume but still, while much louder, still missing that low end. When attempting to adjust it via equalizers, upping the low frequencies does next to nothing because I think they're not actually there to amplify.

I went back to nexus experience rom, factory reset, cleared cache, data, system and Dalvik and the issue is now in this rom as well.

When we're the 5.1.1 blob things implemented, and what do they do?

Edit: playing through headphone jack, listening in different cars through aux. I've found with all music, however if you need something specific try Girl Talk - all day - triple double
[X 2014 Original Android Development] tacosrdelicioso:
Haha. I usually don't have WiFi available when I try it. And I usually just use an app to get logs so I never got them

But I'll be flashing again soon
[X 2014 Original Android Development] Aroch925:
Here's my log for the xt1096 no sim problem. This is the first time I've ever done a log so if it's not done right I apologize in advance and please tell me. Hopefully I can get CM to work on my phone. Thanks in advance!

https://drive.google.com/file/d/0B6kWVVJhYz9KVGhzYUljX1ZMd0E/view?usp=sharing
[X 2014 Original Android Development] invisiblek:
K, so I assume my vendor init is working properly now (it shows XT1096 as the model in your settings right?). If that's the case, it should be setting the proper telephony flags. I'm guessing I'll need a radio logcat to debug this further (adb logcat -b radio).

You may want to PM that to me, or at the very least scrub it for your IMEI and phone number before posting it publicly.
[X 2014 Original Android Development] Tommebaas:
There is almost no bass anymore when listening to music with headphones or when an aux cable is plugged.

The overall volume is also lower.

Playing YouTube videos, notifications, the ringtone etc are all lower.

Something happened with the sound a few nightlies ago.
[X 2014 Original Android Development] adm1jtg:
Can you tell us which nightly is the last nightly it was OK on
[X 2014 Original Android Development] Aroch925:
Yeah it now shows the xt1096. I'll just PM you the log when I get a chance
[X 2014 Original Android Development] coldheat06:
What did you have to do for it to install?

Sent from my XT1095
[X 2014 Original Android Development] :
I think the feature was added in the 2015 08 25 nightly

victara: add motorola-specific play store props and permissions (android_device_motorola_victara)

But when I updated from the previous nightly, I was getting an error from the play store, I tried clearing the play store cache and data, and also android framework, but that didn't seem to work, I think I then did a clean flash of the 25 august nightly.... I just tried installing the moto camera just now, it installs and seems to work.

Of course any nightly after 25 should work.
[X 2014 Original Android Development] slogar25:
How did you flash your modem files?
[X 2014 Original Android Development] coldheat06:
OK, thank you. Is the the Moto camera the best camera app that you have used so far?

Sent from my XT1095
[X 2014 Original Android Development] :
I honestly can't say, since I really don't snap that many pics, and never attempted to compare pics from different camera apps.

You would have to snap the same pics with different apps and then view them on a large monitor to see any difference, unless exposure and color balance are really off. You can also try Mark Harman's free Open Camera from the play store.

Also, the Moto Camera has some advanced options, like disabling noise reduction, etc. in CM, look for the lady bug bottom right side, after swiping right to settings.
[X 2014 Original Android Development] booyashakas:
Update on the sound issue. I'm still running Nexus Experience, but the sound issue carried over from this rom (was running Nexus Experience prior to this without the issue). But last night I was switching songs and all of a sudden the bass was back to normal. Then I got a call, and when I went back to resume the song it was bad again. So I;ve started switching songs and bands and podcasts and every now and then I can get it to go back to normal sound for a bit. Odd

Wondering if its possible its getting stuck in that lowered sound state from when you get notifications
[X 2014 Original Android Development] Aroch925:
First I flashed invisiblek modem from his site through recovery. That didn't help so I flashed mikeoswego modem files from his thread through fastboot. That didn't fix it either
[X 2014 Original Android Development] vista178:
I received the update through the official update.
[X 2014 Original Android Development] slogar25:
Just to be thorough,

Through fastboot you ran,

Fastboot flash modem NON-HLOS. bin

from the 5.1 factory images.

And then

Fastboot erase modemst1

Fastboot erase modemst2
[X 2014 Original Android Development] mikeoswego:
The modem files for Verizon XT1096 variants are in this archive:

5.1bins.7z - Kernel, modem and other 5.1 update files

Extract the files from the 5.1bins.7z archive and then run these commands to make sure your modem files are up to date:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2

If you were on a 5.1 version before going to CM, you should already have these files installed.
[X 2014 Original Android Development] Aroch925:
yeaht thats exactly how I did it
[X 2014 Original Android Development] mikeoswego:
The moto camera app is fine but there is nothing fantastic about it. Give it a try and see if you like it. Try the Google camera too if you want to try a different approach to panorama shots (and the photo sphere option.)
[X 2014 Original Android Development] :
What about:

fastboot flash fsg fsg.mbn

I'm no expert, but I thought fsg.mbn contains the carrier info? I used to also flash that when I flashed a different variant firmware on my previous phone, rather like this:

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn
[X 2014 Original Android Development] Aroch925:
Yeah I tried that too. It didnt work
[X 2014 Original Android Development] invisiblek:
try adding this to your build.prop and rebooting:

ro.telephony.default_cdma_sub=0

EDIT: If that doesn't work, try a data wipe with that in there as well.
[X 2014 Original Android Development] Aroch925:
It didn't work. Even after the date wipe
[X 2014 Original Android Development] vista178:
Looks like our issue might be fixed with tonight's build?

http://review.cyanogenmod.org/#/c/107954/