No WiFi location on [ROM][4.4.2][GSM] Official CM11 (Nightlies) - Motorola Droid RAZR

On the latest nightlies my XT910 (umts_spyder) is not using WiFi location.
GPS and Cell location are working. I tracked my location
history and find out that the issue occured with an update
at the end of march. Unfortunately i can't say, which nightly
i installed before and after it was not working. I only can say,
that i was running a cm11 nightly before 03/26 and the wifi location
worked. With an update available at 03/26 no wifi location was used
anymore. In this time i updated the nightlies once a week (may be two)
using cm-updater ota.
I also tried a clean install of the 2014-04-17 nightly on a newly
created SS rom slot 1 --> didn't work.
I read that someone also described this issue in the dev-thread but there
was no real feedback. Does anyone know, if this issue is already known to the
devs and if thy are working on it?

Seems that nobody has an idea... but I still have this issue and tried alot.
(New nightlies in clean slots; other cm-based roms, various switching of
possible options...)
Now the interesting part:
One try was to flash an old nightly, For this nightly I know that the wifi-location
worked with it. But surprisingly after flashing it didn't work ... so I think, that issue
isn't related only to changes in nightlies.
Yesterday proofed it. I restored an SS-Backup from the end of February. And for
a short time after the boot my location was correct and as precise as it was before.
Around half an hour later the location was unprecise again and wifi wasn't used
anymore. The only thing happened in the meantime, was the pushing of updates.
So I'm quite sure, that a silently pushed update of a google package or service
is causing it.
I also checked my location history again and compared it to my backups. During this,
I noticed, that I wasn't flashing any update the time, when the wifi-location mode or "fused
location provider" stopped working correctly... for me it was around lunchtime on March 26...

ranziger said:
Seems that nobody has an idea... but I still have this issue and tried alot.
(New nightlies in clean slots; other cm-based roms, various switching of
possible options...)
Now the interesting part:
One try was to flash an old nightly, For this nightly I know that the wifi-location
worked with it. But surprisingly after flashing it didn't work ... so I think, that issue
isn't related only to changes in nightlies.
Yesterday proofed it. I restored an SS-Backup from the end of February. And for
a short time after the boot my location was correct and as precise as it was before.
Around half an hour later the location was unprecise again and wifi wasn't used
anymore. The only thing happened in the meantime, was the pushing of updates.
So I'm quite sure, that a silently pushed update of a google package or service
is causing it.
I also checked my location history again and compared it to my backups. During this,
I noticed, that I wasn't flashing any update the time, when the wifi-location mode or "fused
location provider" stopped working correctly... for me it was around lunchtime on March 26...
Click to expand...
Click to collapse
I have the same problem (HTC One max KiteKat 4.4.2)
The problem is a version of Google Service Play.
- 4.2.x working
- 4.3.x NOT working

pan-x said:
I have the same problem (HTC One max KiteKat 4.4.2)
The problem is a version of Google Service Play.
- 4.2.x working
- 4.3.x NOT working
Click to expand...
Click to collapse
Thanks for that. Now I know it's probably not device-spezific.
Also tried with a clean install of M6 snapshot... issue persists

Related

FXP41+ Data Loss Bug Hunt (Bug Squashed)

Bug issue has been solved as if FXP45. Thanks to all who helped track this nasty critter down.
I've been asked to start up a thread specifically for tracking down the data loss bug in FXP41,42 and 43. I'm currently one of the very few that are not suffering from this problem.
Background
The data loss issue is when your wifi or 3g status indicators still show you as being connected to the internet and Google (green indicators) but no data is transferred. A reboot of the phone will restore data for a limited period of time before the same thing occurs again. After a fresh install, it can take anywhere from a few minutes to a few hours for data loss.
For those that have the problem nothing tried so far as been able to rectify the problem for any length of time and for those of us that don't have the problem we can't duplicate it.
What needs to be done
We need to find some common denominator between the devices / users that are having this problem that is also something that none of the working devices / users don't have. If you have anything to add that you've tried to do to duplicate the problem or fix the problem please post or PM me with the details and I'll keep this OP up to date.
What been tried to duplicate problem on working devices
1. Fresh install - Nope
2. Market update / downgrade - Nope
3. Forcing sync - Nope
4. Factory data reset and login with different account - Ongoing
What's been tried to fix the problem
1. Fresh install - Nope
2. No Gapps - Nope
3. Market downgrade - Nope
What still need to be tested (suggestions please)
1. Working device/user create a different Google account and test with that.
2. Who is using 2 step verification and do they have problem or not.
3. Compare results of a clean install using the same account on a working and not working phone. (I have account setup PM me for login if you want to help test)
This should get the ball rolling, I'll add some more is a couple of hours once I get my head in gear.
I've had the problem today. I didn't try to format the sdcard first, but maybe it helps. I can't try it until next week at least
Enviado desde mi X10i usando Tapatalk
I was on this rom (fxp041) for a while, it was at least two weeks before i got the data bug. I'll have another go tomorrow installing the latest version fresh. I'll experiment to see what causes it. Hopefully report back tomorrow with some report.
cheers, lunar.
Sent from my X10i using XDA App
I've just done a factory data reset and setup the phone using a different gmail account that I created for this test. If I loose data then maybe it's account related.
Well, I have tried two different google accounts, so either both of my accounts are screwed, or it isn't something tied to the Google account. However, it didn't happen to me UNTIL I installed the GApps addon package either time - first time I installed the ROM, had data no problem for about 3 hours, then was like "Whoops, wait a minute, need my Gmail / Market apps", so I installed the package and lost it. Second time, installed both, had net, did a Market download of a few apps, checked gmail, worked fine for about half an hour, then went kaput. Did the second time with a DIFFERENT google acct.
Hi,
The data bug began for me with the fxp30b release. I tested so many things to tackle that nasty bug.
Cu
Sent from my X10i using Tapatalk
FXP043 also have data bug. I will use stock or VMOD version later.
Hi GBD,,
I have tried everything you have in the op and nothing has worked for me too, also you can rule using a new account as i have tried that too even on a fresh install.
I thought that when market updated it was that causing the issue but yesterday i froze the marketupdater app with titanium, signed in, and the problem still occurred.In fact before signing into google the phone had worked fine for several hours with no data issues.
I wonder if Crowds has found the solution here..
http://forum.xda-developers.com/showpost.php?p=18795198&postcount=13384
Maybe we do have a fix so waiting now for good news.
I have gone back to fxp030 for now as i need my phone for work.
colossus said:
I wonder if Crowds has found the solution here..
http://forum.xda-developers.com/showpost.php?p=18795198&postcount=13384
Click to expand...
Click to collapse
let´s see what i sent to FXP will do
i had the same issues as many but after i´ve tried several mixes i was able to stay connected all the time without interruption since 21:00 yesterday till now
cheers
R
i think its related to new Market... on ARC i have similar issues on CM7 as well as stock ROM
DooMLoRD said:
i think its related to new Market... on ARC i have similar issues on CM7 as well as stock ROM
Click to expand...
Click to collapse
for some it seams like but for many still have issues
i didn´t change/delete anything from original rom and i´ve manage to work everything. well...almost. seams that i´ve lost capabilitie to turn bluetooth on
Maybe when superuser update automatically the data bug start???
DooMLoRD said:
i think its related to new Market... on ARC i have similar issues on CM7 as well as stock ROM
Click to expand...
Click to collapse
Can someone test this out. Do a fresh install and as soon as you boot up and connect to your google account, manually set your time to 11:59pm and allow it to roll over to the next day.
The market should update when the roll over occurs and if it's the cause, you'll loose data at that time.
GreatBigDog said:
Can someone test this out. Do a fresh install and as soon as you boot up and connect to your google account, manually set your time to 11:59pm and allow it to roll over to the next day.
The market should update when the roll over occurs and if it's the cause, you'll loose data at that time.
Click to expand...
Click to collapse
Did fresh install of FXP043, after first boot up connected with account, selected some Gapps to install, at that time it automatically synced. Connected to wifi to download gapps faster, after that changed time to 11:59 pm (decided to stay on edge, no wifi). 2 minutes later there was new market, and everything worked just fine. Visited some websites, changed to wifi and back. Data still working. I can't reproduce data issue...
I came from FXP030b in which data was also working for me(had few issues at the beggining first but then data was working fine)
Crowds said:
let´s see what i sent to FXP will do
i had the same issues as many but after i´ve tried several mixes i was able to stay connected all the time without interruption since 21:00 yesterday till now
cheers
R
Click to expand...
Click to collapse
How you getting on bro? are you still running fxp043 without any data loss issues, if so did you manage to sort out the bt problem?
colossus said:
How you getting on bro? are you still running fxp043 without any data loss issues, if so did you manage to sort out the bt problem?
Click to expand...
Click to collapse
i was from 21PM yesterday till 13PM today without any issues besides bt and to be honest i don`t even try to manage that i the meanwhile i change rom again
Maybe it's kernel related? Maybe you can try flashing fxp30's kernel over fxp43 and test?
I'm running FXP43 and just encountered data loss but found a solution (at least in my case, not sure if it's 100% effective for everyone).
What I did:
- Went into Dev Tools > Bad Behavior > Crash the system server
- Screen seemed to freeze but I let it sit for a good 30+seconds to see if it would become responsive
-After no response I pulled the battery and removed my sd & sim cards for 30+seconds then replaced them
-Booted my device and data is back
If anyone tries this method and it helps I'd appreciate the THANKS!
hhill13 said:
I'm running FXP43 and just encountered data loss but found a solution (at least in my case, not sure if it's 100% effective for everyone).
What I did:
- Went into Dev Tools > Bad Behavior > Crash the system server
- Screen seemed to freeze but I let it sit for a good 30+seconds to see if it would become responsive
-After no response I pulled the battery and removed my sd & sim cards for 30+seconds then replaced them
-Booted my device and data is back
If anyone tries this method and it helps I'd appreciate the THANKS!
Click to expand...
Click to collapse
Dude, this isn´t neccesary and doesn´t solve the problem. After a reboot data is always back but disappears again after a while. There´s no need to crash the system server.
has anyone tried to flash new gapps (this) instead of the one provided in the post?

GPS not working with CM9?

Hi,
Yesterday I flashed CM9 resurrection edition (before that I had a 2.3.5 stock ROM) and GAPPS.
Everything seems to work fine, apart from the GPS function...
In 2 times I tried, it took my SG2 about 15-20 minutes to lock on to a signal (and after that it was fine...), but in all the other times, it doesn't get a lock on.
I d/l GPS status and GPS Test and I get nothing.
I tried the AGPS patch from here, but nothing seems to work.
I looked all over the net for a solution, but didn't got to anything useful.
Can anyone help?
Try to flash a newer CM9 Nightly. Many improvements have been committed since last resurection release.
You may have a look here http://forum.xda-developers.com/showthread.php?t=1419102
sagybp said:
Hi,
Yesterday I flashed CM9 resurrection edition (before that I had a 2.3.5 stock ROM) and GAPPS.
Everything seems to work fine, apart from the GPS function...
In 2 times I tried, it took my SG2 about 15-20 minutes to lock on to a signal (and after that it was fine...), but in all the other times, it doesn't get a lock on.
I d/l GPS status and GPS Test and I get nothing.
I tried the AGPS patch from here, but nothing seems to work.
I looked all over the net for a solution, but didn't got to anything useful.
Can anyone help?
Click to expand...
Click to collapse
try GPS Fix app from play store, hope it will resolve ur Gps issue
GPS Fix
Sun90 said:
try GPS Fix app from play store, hope it will resolve ur Gps issue
Click to expand...
Click to collapse
I read GPS fix installs tons of spam and push ads. I prefer avoid it.
Any other idea?
Flash latest nightly. The latest commit found below fixes your problem
http://review.cyanogenmod.com/#/c/18705/
Sent from my Galaxy S2 powered by CM9

[Q] How to fix GPS on CM10 stable for Galaxy S3 (Sprint)?

I have been using CM for years, first on the Evo 4G and now on the GS3. Ever since I can remember, I've had issues with GPS on CM. In the Evo days, I always remember flashing a GPS fix (or doing a CLR fix after flashing in from a Sense ROM). Now, with the GS3, I continue to have challenges with GPS on CM. When I had the M builds, I had decent performance with GPS and could get the navigation to lock - as well as maps finding my location. Ever since I went to the CM10 stable build, the navigation just sticks on "waiting for location" and the maps cannot find my location. Super frustrating. I even switched over to AOKP for the time being as the GPS seems to be working great (as well as most of the other features).
I am still itching to get back to CM though...
Here are my questions:
1. Is there a flashable fix for the GPS problem in CM10 on the GS3?
2. I've seen that a few people flashed into ICS, locked nav, and then flashed back to CM - does this work? if so, after doing this, can I re-flash a backup or do I have to wipe clean first?
3. Even if one of the two fixes above works, will I still have sub-par performance with GPS?
Thanks in advance.
Not my answer, rochers from androidforums:
took me quite some time to figure this one out, thought i should post it here in case anyone else has a similar problem.
When i updated to android 4.1.2, i noticed that my google navigation stopped working. It would simply sit there endlessly "waiting for location..." fortunately, there's a simple fix:
1. Go to "settings > accounts > google > location settings".
2. Flip the switch to "on" (i found this was off in my case).
3. Try google navigation again, it should work fine.
I'm not sure why google decided to break up the location settings into two different places like this, but it's a bit silly imo as it's definitely going to catch some people out.
Found this solution on xda, cant post link, but this works.
Click to expand...
Click to collapse

GPS won't lock even after many attempts to fix

Hello XDA Developers,
I come to you all with a problem. I am having trouble with my GPS; it won't lock. I have tried these things:
Using GPS Status and other GPS fixers
Doing a factory reset using Mr. Cook's ROM Wipe Script
Clearing data and cache of my GPS apps (Waze and Google Maps)
Idk what else to do. Every time I use the GPS apps to pinpoint my location, after a navigation session, it goes back to getting stuck on "waiting for GPS".
Any help is appreciated.
What firmware are you running? Have you had the same problem with other firmware?
creepyncrawly said:
What firmware are you running? Have you had the same problem with other firmware?
Click to expand...
Click to collapse
I am currently on an unofficial nightly of CM11 ported by RenderBroken. When I was experiencing those problems, I was on Omni ROM for Android 4.4. I was on ShoStock3 before the Omni ROM, and it was the same problem.
I don't run anything AOSP based so I can't speak about how those might affect GPS, but since you have the problem across various roms, and even on SHOstock3, I wonder if the phone has a problem with the GPS hardware? Have you ever had good GPS at any point with that phone? If so what were you running at the time.
I've had some GPS issues in the past but am not having any issues currently. I've been on SHOstock3 for a long time. My issues were on an earlier version of SHOstock, I don't remember which one exactly. When my GPS would fail to lock, just as you described, a reboot would fix the issue and result in a fast lock, but then the next time I would try to use GPS, I would have to reboot again. It was very annoying. Someone said that to format cache, wipe dalvik cache and fix permissions would fix the problem, so I tried that, and yes I would then get a lock in 5 - 10 seconds and it would stay good for a few weeks until I would have to do it again. I never experimented to see which of those three things helped, or if you had to do all three. That was back around June or July of this year.
As I recall, the next base change on SHOstock completely eliminated the issue.
creepyncrawly said:
I don't run anything AOSP based so I can't speak about how those might affect GPS, but since you have the problem across various roms, and even on SHOstock3, I wonder if the phone has a problem with the GPS hardware? Have you ever had good GPS at any point with that phone? If so what were you running at the time.
I've had some GPS issues in the past but am not having any issues currently. I've been on SHOstock3 for a long time. My issues were on an earlier version of SHOstock, I don't remember which one exactly. When my GPS would fail to lock, just as you described, a reboot would fix the issue and result in a fast lock, but then the next time I would try to use GPS, I would have to reboot again. It was very annoying. Someone said that to format cache, wipe dalvik cache and fix permissions would fix the problem, so I tried that, and yes I would then get a lock in 5 - 10 seconds and it would stay good for a few weeks until I would have to do it again. I never experimented to see which of those three things helped, or if you had to do all three. That was back around June or July of this year.
As I recall, the next base change on SHOstock completely eliminated the issue.
Click to expand...
Click to collapse
I have had a lock before. When I used GPS Status, it would get a lock for a short while, but when I ran the navigation, it would get stuck at waiting for location again.

official Z7mini 5.0 beta bugs

Hi,
as some people may not be sure before switching to the beta version released by nubia, it may be a good idea to list the issues that we found with this rom
here are mine (I only use one sim card)
1: UI is slow and even more slow with full brightness (installing another launcher could help)
2: the notification switchs (data) will be ON whereas data is off . Plain mode also turn off data but the switch stay on
3: bluetooth audio is crappy... there are like sound hole every 5 seconds... can't use it correcly in my car
beside that, it did not tell the car what music is playing (there was no issue on CM12 and Mokee 5)
4: once the new system is installed, you can't reinstall directly install your previous backups as the partition is now different..
new CM12/mokee will be released soon to fix this. In the worst case you can still reinstall kitkat with the nubia update tool
alain57 said:
Hi,
as some people may not be sure before switching to the beta version released by nubia, it may be a good idea to list the issues that we found with this rom
here are mine (I only use one sim card)
1: UI is slow and even more slow with full brightness (installing another launcher could help)
2: the notification switchs (data) will be ON whereas data is off . Plain mode also turn off data but the switch stay on
3: bluetooth audio is crappy... there are like sound hole every 5 seconds... can't use it correcly in my car
beside that, it did not tell the car what music is playing (there was no issue on CM12 and Mokee 5)
4: once the new system is installed, you can't reinstall directly install your previous backups as the partition is now different..
new CM12/mokee will be released soon to fix this. In the worst case you can still reinstall kitkat with the nubia update tool
Click to expand...
Click to collapse
I've tried to duplicate the problem in number 1, but have not had problems. I've also read (don't remember where now) on a couple of the Chinese bbs that this seems common. Some people really think the new UI is slow and others do not have problems. I actually think it runs pretty smoothly.
I agree with number 2. Additionally, even though I have vibrate turned off, the phone always vibrates. Unless I have the phone on silent, then there is no vibrating and no sound. I've tried to have vibrate for silent only and it does not work.
I don't use bluetooth, so I cannot confirm number 3.
I partially disagree with point 4 because you can get much of what you had back previously if you used something like Titanium Backup. As I stated in one of my previous posts, I used Titanium backup to backup all apps and data. After that, I copied the folder to my computer. After installing the Nubia beta update, I transferred the folder back to the phone and restored everything without any problems. On the other hand, number 4 is correct. You cannot go back and reinstall a previous TWRP or CWM backup because of the unified storage. In my opinion, this has nothing to do with Nubia as this applies to any phone that upgrades from 4.4 to 5.0/5.1. If a rom says that it is Android L, but does not use unified storage, it is still technically a modified version of 4.4.
A couple of additional points that I don't like:
Cannot modify the actions of the buttons
No theme engine for further UI modifications
No clock widget (I know it's minor, but many people are complaining about this on the Chinese bbs too.)
One thing that is nice is that I had issues with my battery overheating frequently and since I have updated this has not happened at all. Maybe it's just me, but I'm kind of an app junkie. I'm always trying new apps; installing them, uninstalling them and so on. This process seems to be much quicker now. Additionally, I think that the signal has improved. I now have mobile reception in several areas where it was a dead zone previously.
thank you for your long feedback
in fact i prefer using cwm or twrp backups as i change the entire rom, it may be that some settings are not located at the same place so using a tool like titanium that run on the rom itself may not find all settings (but maybe they improved it since i first tried)
Concerning the UI slownes, I used Mokee and Cm12 on this phone and the feeling was a lot smoother
other people confirmed this. Try sliding from one desktop to an other with brightness level at minimum and retry it with maximum brightness you'll notice a visible difference
concerning the existing CM12/Mokee 5 roms, these are indeed Android5. But maybe they didn't change the storage to be 100% compatible with existing nubia partition
oh i also forgot, like in previous nubia rom, the UI has no notification access menu... I don't understand why
this is particulary useful if another device needs to read the notifications like a watch or a band... (but you can access it by installing 3rd party tools)
i'm on Cuocu92's modified Android 5 (he added some stuff like multilang, removed some useless apps and added google apps)
but I will switch back to Mokee or Cm12 as soon as they release a working version... the bluetooth and notification switch issue are two point that force me to switch
I do agree that Mokee and CM12 were a bit smoother. However, even when I change brightness from minimum to maximum I don't seem to notice any drastic change in smoothness. Maybe it's the launcher that you use like we talked about in the other thread. I agree with you on the notification access menu, that's a pain in the a$$. Interesting about the CM12/Mokee; I've read several places that state otherwise, so I'm not sure what to believe. I also agree, I too will switch back to Mokee or CM12. The FIUI rom has also been having some really nice improvements and I may try that if they switch to 5.0. For me the notification, the button customization, and the themes make me want to switch back.
Have to agree that the UI on 5.0 is pretty laggy even when using Nova launcher which is usually butter smooth their is major frame drops. And it especially gets laggy when brightness adjusts its self if set on auto.
Also at some point the home button stopped working for some unknown reason. I had to use the back button to exit apps. I don't know why some guys say that they don't have a theme engine. I have one on my ROM.
All in all I would not recommend someone using this ROM as a daily driver. Stick to 4.4 or any of the CM12, CM12.1 or Mokee versions.
I happen to have 2 Z7 minis with me and they both had the exact same bugs. I had to revert back to CM12.
i went to new CM12.1
but for people who need GPS => CM12.1 has a broken GPS, no signal, not even one satelite got detecte. Even outside with a clear view. Whereas official nubia can fix whitin 10 seconds inside ...
chalimoja said:
Have to agree that the UI on 5.0 is pretty laggy even when using Nova launcher which is usually butter smooth their is major frame drops. And it especially gets laggy when brightness adjusts its self if set on auto.
Also at some point the home button stopped working for some unknown reason. I had to use the back button to exit apps. I don't know why some guys say that they don't have a theme engine. I have one on my ROM.
All in all I would not recommend someone using this ROM as a daily driver. Stick to 4.4 or any of the CM12, CM12.1 or Mokee versions.
I happen to have 2 Z7 minis with me and they both had the exact same bugs. I had to revert back to CM12.
Click to expand...
Click to collapse
I agree now and finally see what people are talking about. Certain apps have really slowed down. It's apps that I don't use very often, but it's getting to be annoying. Going to give the new CM12 a try.
alain57 said:
i went to new CM12.1
but for people who need GPS => CM12.1 has a broken GPS, no signal, not even one satelite got detecte. Even outside with a clear view. Whereas official nubia can fix whitin 10 seconds inside ...
Click to expand...
Click to collapse
Can anyone help me? I was trying to flash the new CM12.1 using TWRP and in the middle of it the phone went black. Now I can't turn it back on, can't do anything. Ideas anyone? This sucks. Fortunately, I just did a backup of everything, but now the phone won't even power up. I'd appreciate any suggestions. Yes, I had already upgraded to the official nubia beta.
Edit: The phone still won't turn on, whether it's plugged in or not. However, when I plug it into the computer I can see 5 different partitions of various odd sizes with different aspects of the phone software visible.
Edit 2: So I did a hard reset and was able to get back to TWRP. Next I tried wipe data, cache, dalvik and it did the usual trying to format partitions and it kept failing, saying it couldn't access data. I tried flashing CM12.1 and it gave me the same error, although it said it installed successfully. I also flashed gapps. Now I'm waiting for it to boot up.
alain57 said:
i went to new CM12.1
but for people who need GPS => CM12.1 has a broken GPS, no signal, not even one satelite got detecte. Even outside with a clear view. Whereas official nubia can fix whitin 10 seconds inside ...
Click to expand...
Click to collapse
I've been on CM12.1 for almost 24 hours now and have not had this problem. GPS was off by default when I installed it and I had to enable it. I've used G-maps and a couple of other apps that need GPS and all of them locked on within a few seconds.
pedrud said:
I've been on CM12.1 for almost 24 hours now and have not had this problem. GPS was off by default when I installed it and I had to enable it. I've used G-maps and a couple of other apps that need GPS and all of them locked on within a few seconds.
Click to expand...
Click to collapse
did you tried with gps device only settings ?
because maps use wifi and network localisation to have a position even when gps is not turned on
this really makes me crazy...
I installed gps test and it stay a "no fix"
whereas when i restore my nubia 5.0 OS and tried gps test it fix directly
restoring back the CM12.1 got again no fix :/
alain57 said:
did you tried with gps device only settings ?
because maps use wifi and network localisation to have a position even when gps is not turned on
this really makes me crazy...
I installed gps test and it stay a "no fix"
whereas when i restore my nubia 5.0 OS and tried gps test it fix directly
restoring back the CM12.1 got again no fix :/
Click to expand...
Click to collapse
You are correct. I had not tried device only - it does not work. This is frustrating. Off to the Chinese forums to see what they say....
Hey guys I'm using the official v3.01 and I have so many bugs and crashes. Worst of all it crashes when I have an incoming call and sometimes the screen goes dark when I get a call and I can't swipe and answer the phone. Is there anyway to go back to KitKat 4.4.4? Can anyone explain the steps?

Categories

Resources