Database Info

[Q] MIUI Infuse Airplane mode not turning off.

I have the most recent version of MIUI for Infuse. I have correctly flashed it and everything works great. However recently Airplane mode can not be turned off. No matter what I try the only way to get it to turn off is by reboot, and if I leave it in sleep mode airplane mode turns on and stays that way. Is there a fix for this?

Yeah same here. Can not figure out what to do. I have tried several available modems and they all seem to do it. I have tried UCKD5, UCKE3, UCKJ1, UCKJ2, UCKJ4 and UXKG3 and they all seem to have the same problem. HELP

Any solution to this? Thanks!

i have the same issue. it seems that the toggle doesnt really work through the settings. restarting the phone as of now is the only way to turn it off. unfortunately for me sometimes its on for a long period of time before i noticed that its on, and i end up missing calls/texts

[Q] - Random Wifi Shut-Offs And Problem Turning Back On

One day my skyrocket started acting up. I have the AT&T version. what happens is The wifi could be working perfectly fine then when i let it sleep and then wake it the wifi is on and sometimes turns right back on and connects and other times it won't turn on, even when I try to manually. I've tried going back to pure stock, ICS Stock, and tried custom roms and it's all the same. Sometimes on first boot the wifi won't even turn on. Then sometimes when I'm out of wifi Range I turn it off and when I come back and try to switch it on it says "Wifi turning on.." then the toggle goes back to off but it still says that. Sometimes when the phone is in use, screen on, I could be browsing the web or on facebook and it shuts off and won't come back on. This has nothing to do with the Power Saving mode, I never touched that setting and I checked and it's set to "Always." So what could it be? It gets extremely frustrating. someone please help me :l
I searched the forums before I posted, I know this may fall into the development category but I couldn't post there..

r0ttenways said:
One day my skyrocket started acting up. I have the AT&T version. what happens is The wifi could be working perfectly fine then when i let it sleep and then wake it the wifi is on and sometimes turns right back on and connects and other times it won't turn on, even when I try to manually. I've tried going back to pure stock, ICS Stock, and tried custom roms and it's all the same. Sometimes on first boot the wifi won't even turn on. Then sometimes when I'm out of wifi Range I turn it off and when I come back and try to switch it on it says "Wifi turning on.." then the toggle goes back to off but it still says that. Sometimes when the phone is in use, screen on, I could be browsing the web or on facebook and it shuts off and won't come back on. This has nothing to do with the Power Saving mode, I never touched that setting and I checked and it's set to "Always." So what could it be? It gets extremely frustrating. someone please help me :l
I searched the forums before I posted, I know this may fall into the development category but I couldn't post there..
Click to expand...
Click to collapse
when you say pure stock, do you mean you odin'ed back to stock? i'm no expert but if you've had the same issues on pure stock rom, custom roms it sounds as though it may be a hardware issue.

ctalcant said:
when you say pure stock, do you mean you odin'ed back to stock? i'm no expert but if you've had the same issues on pure stock rom, custom roms it sounds as though it may be a hardware issue.
Click to expand...
Click to collapse
Well yes odin'd back, & also used kies through download/recovery mode. well the custom roms it does it on are all stock based... well I had installed MIUI but idk If it had done it on there. this issue is very frustrating..

i realized last night that the bluetooth does it too, so if it's a hardware problem does that mean the motherboard could be bad, not the actual components?

[Q] Moto G XT1032 - Lags / Reboots / Hangs - Hardware or Software Issue?

Hi,
I have a Moto G XT1032 (2013, 1st gen) with Lollipop 5.0.2
Stock Firmware: 220.27.1.falcon_umts.Retail.en.GB
On Sunday the phone began suddenly rebooting itself (it did so almost constantly at times). Sometimes I was able to get past the boot animation (which itself "lagged" on some of the boots/reboots) and be able to navigate menus or apps for 30 seconds and then another reboot would occur.
I decided to do factory reset (from the phones menu, one time I was able to navigate there without the device rebooting). Once I set up the phone, a few moments later (before the apps I had previously would download from my accounts synch) it began rebooting again... I gave up hope until the next day.
I followed to clear cache and Wipe data through the phone's stock recovery. Once I set it up, it began working fairly better. But the "hangs" and "lags" during normal operation were still occurring. The phone now rebooted rarely, but it still happened.
Yesterday and today the phone seems to be working better, and suffered no reboots, but for some reason I wake up and my phone is turned off... When turning it on again the battery was half-full.
I would like to know if this could be a hardware or software issue. In case of the former, I will have a bad time (money wise). In case of the latter, what should I do? Reflash stock firmware? Or what other thing would you recommend?
Thanks in advance.

My brother has the 8GB version, enGB-retail from Amazon.co.uk and for the last two days, the phone is unusable! It restarts all the time until the battery dies and when you put it on the charger, the phone resumes the boot loop (( I've managed to boot it and do a factory reset, then it was fine for like an hour, then it started lagging hard and after that the boot loop came again. And the phone is turned off right now, because it won't boot and it won't charge. Could this be due to a hardware failure? 'Cause if there's a chance I have to ship it back to Amazon... The phone is pure stock, 5.0.2 Lollipop, no rooting and stuff ever performed! And I don't know if an app was recently updated, something that might be causing the issue...
I have the 16GB version and it is working fine.
Any idea why this happened? :/

Right now it seems to be working well... For the whole day... Including phone calls(half an hour call with no issues). Even lags are not happening... I will check if the phone is off when I wake up... I don't have a clue of could make it turn off during the night.
How could this be happening? Suddenly fixing it by itself? This could mean the device's software is somehow sorting itself out? Or an intermittent hardware issue?

Ok so I'll post my problems :/
My phone was rebooting like crazy lately. I don't know what was causing it. My normally working system which was the optimized stock rom from here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Was working great for some time. Then suddenly it started to reboot like every 5 to 10 minutes...
Now I clean installed the stock rom, then TWRP recovery and every thing was working great through the day. Then when I was browsing the net in chrome at night the phone froze for like 10 seconds, restarted and froze at the "bootloader unlocked" screen. Also if that's any help here you have battery stats:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hop you can help because now I'll try to flash CM12 or some other rom to see if it'll help anything :/

XT1032 gets powered off randomly after lollipop 5.0.2 update
Hi,
My issue is similar but not exactly same.
My 1st Gen Moto G has undergone system upgrade (as Motorola made it available) to lollipop 5.0.2 by end of April 2015. Everything was fine after this upgrade, except I noticed 3-4 times that the mobile just simply powers off when it was in standby mode. Suppose, I wake up in the morning and tried to make the screen on by pressing the power button, but it did not start. Then I realised the phone is switched off. It happened in the first week after upgrade and only 3-4 times which then I forgot as by 20th May it didn't happen. Then suddenly for last 7 days it became rampant. On 21st, it happened 4 times. - mostly when it is on standby mode. Once it happened as the mobile was just restarted - so it happens when not in standby mode as well. Then once I rebooted it by holding power and vol lower button together for 120 sec. Then it ran for almost 2 and half days without the issue. Then suddenly yesterday it was powered off again
Can anyone suggest anything? It seems to be software issue as this issue was not there before the upgrade. Is it a bug of Lollipop 5.0.2? Is there any resolution for this? Can I downgrade my phone OS to Kitkat 4.4.4 as it was before the issue?
Model :
XT1032
Baseband version :
MSM8626BP_1032.3105.93.00R TESCOGB_CUST
Karnel Version :
3.4.42-gdd242b0
[email protected] #1
Fri Jan 23 08:12:33 CST 2015
System Version :
220.27.1.falcon_umts.TescoSL.en.GB
Build Number :
LXB22.46-28.1
Any suggestion would be helpful. Due to rampant shutdown - the phone has become unreliable. I frantically check after every 5 min if the phone is switched on.
Thanks in advance,
Bijitesh

Advise please
It seems the issue is not wide spread and there is no solution. Is there any crash report stored in Android which we can check to get to root of the issue? Just for info, the handset is not rooted yet. So advise accordingly.
Thanks,

wrbl said:
Ok so I'll post my problems :/
My phone was rebooting like crazy lately. I don't know what was causing it. My normally working system which was the optimized stock rom from here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Was working great for some time. Then suddenly it started to reboot like every 5 to 10 minutes...
Now I clean installed the stock rom, then TWRP recovery and every thing was working great through the day. Then when I was browsing the net in chrome at night the phone froze for like 10 seconds, restarted and froze at the "bootloader unlocked" screen. Also if that's any help here you have battery stats:
Hop you can help because now I'll try to flash CM12 or some other rom to see if it'll help anything :/
Click to expand...
Click to collapse
Its weird how your WiFi stays running while every other stops at the freeze. Mine did it the other day while I was browsing chrome screen went white then black for about 15 minutes, then rebooted. And sometimes when I start a app it takes ages for the app to load. Motorola defiantly need to sort it out with this memory bug with an update. They can't just leave users with this mess of a lollipop update, can they?

Lockups, app crashes, phone freezes, random reboots

Hi guys, I have a very irritating issue with my international Galaxy S6 Edge (SM-G925F) and hopefully someone could help me fixing it. I know that this is the forum for the flat Galaxy S6, but since the main hardware components are the same I guess that both devices could suffer from the same problems.
I'm experiencing frequent lockups mostly when trying to wake up/unlock the phone. The device becomes totally unresponsive to screen or home, back, window button taps and eventually after lots of tries it comes back to life and behaves as normal. The problem becomes way less frequent (almost disappears) if I connect it to a charger.
What I tried up to now with no luck fixing the problem is:
Disabled all the TouchWiz smart features, location services, wifi and radio broadcasts, rotation, nfc, sound, bluetooth, fingerprint scanner,
Checked all the sensors from the *#0*# menu and they seem fine,
Flashed through Odin, Smart Switch, TWRP official and custom roms (5.1.1, 6.0.1),
Tried rooted and non-rooted roms,
Tried odin's NAND erase all option and repartioned the phone using the ZEROLTE_EUR_OPEN.pit file,
Wiped the persistent partitions (sda11, 13) using the ADB commands dd if=/dev/zero of=/dev/block/sda11, dd if=/dev/zero of=/dev/block/sda13, which however gave me:
dd: /dev/block/sda11 (sda13): No space left on device,
so I don't know if it was successful or not,
Updated (PASS) the TSP FW version from the *#2663# menu,
Opened the phone and powered it up after disconnecting all components apart from screen and battery,
Tried different battery.
Does anyone have a similar problem and knows how to fix it? Unfortunately, my device is out of warranty so I wouldn't like to visit a Samsung service centre.
I haven't tried alternative PIT files with hidden partitions of various sizes yet. Do you think that it will make any difference or, furthermore, is there a chance of further damaging my phone?
Could someone please with a similar device dial the *#2663# code and give me the following information? Phone's and part's TSP FW version, TSP threshold.
Is there a Phone's and Part's Touch key FW version available? In my phone I cannot see the Phone's, Part's Touch key FW version paragraph at all and I'm curious if this is related to the problem.
Looking forward for your tips! Thanks!

I had this too, but *seem* to have it solved.
Maybe I did some unnecessary step, but it now flawlessly works for half a day, compared to reboot/freeze every few minutes.
- calibrate battery (use an app from play store, or L Speed (has an option for that, too))
- backup stuff to pc
- re-install stock firmware using Kies (works with knox trip, too)
- don't activate wifi, accounts in first start wizard
- do factory reset
- restart
- again no wifi, accounts in first start wizard
- factory reset again
- restart
- again no wifi, accounts in first start wizard
- go to stock recovery (adb reboot recovery or phone off, then power+home+vol up)
- clean cache
- factory reset
- clean cache again
- reboot
- setup normally (ie with wifi et all)
- profit (?)
- optional: install twrp through ODIN
- optional: flash custom rom (let the aroma installer do the wipe)/or supersu if you plan to stay on stock [I'm on PureStock Extra Lite by ambassadii, mist stable ROM from my personal experience]
- additionally you want to disable account sync or play/galaxy auto updates (known to increase issues, but likely not required once phone works again normally)
I know that excessive factory resetting sounds stupid...
But a single factory reset or single cache clean did NOT fix it for me. Also FXR and other options did not do the trick for me.
You might aswell try with just one factory reset, but mine worked normally again upon third + manual in stock recovery... (might aswell just be bad luck).
I hope my device is over with it.
I hope this may help you to solve your problem aswell.
Gesendet von meinem SM-G920F mit Tapatalk

Thanks for your help mate, but unfortunately it didn't fix the problem. Perhaps it seems a bit better, but not fixed for sure. Could you please dial in *#2663# and give me the info that I mentioned in the first post?

Screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It happened for me again, too, once late at night. But during day it seemes fine.
Might be a deep sleep issue?
Gesendet von meinem SM-G920F mit Tapatalk

It seems an external problem, not a software problem...i had similar issues with Arter kernel (galaxy s3 l9300), then i changed to boeffla and now it works without any minimal lag.
I suggest changing your kernel instead of the rom...
Always do a backup before doing anything!

After finishing all the updates my phone returned back to the unusable condition. It seems that it is related to deep sleep issues, but not sure if it's a software or hardware problem though. As long as I keep my phone "warm", ie browsing, playing or any other sort of activity it runs smoothly. The problem appears when I try to wake it up from deep sleep.
Now, regarding the *#2663# menu, I thought you had the edge variant and wanted to see if you had the "Touch key FW" version menu. As I said, in my phone the "Touch key FW" version menu is not appearing at all, but maybe it has to do with the fact that it is the Edge version and not the flat one. A colleague's "healty" flat S6 reports the same info like yours, so everything seems fine there. In any case try the update thing and see if it helps you solving the issue. In my case it didn't, but you can still try!
Regarding, the kernels I tried plenty of them - stock, custom, 5.1.1, 6.0.1, (un)rooted - and the problem was always there.

I'll check how arter97 kernel with system less root behaves.
Gesendet von meinem SM-G920F mit Tapatalk

Wait... You said this problem almost disappears if you put your phone to charge...
Try changing the voltage settings of your CPU at first higher and then lower...
Try also to turn off some cores and overclock the others...
I'm saying this because it seems the only way to see if the problem is the hardware or the software.
(Always backup first!)

I have to admit that this is something I haven't tried yet. At the moment I have turned my wifi off, removed the sim card and rebooted the phone. 4 hours running on battery with not a single problem. I'll check is behaviour for the rest of the day and then I'll try to fiddle with the cpu settings!

Unfortunately, I didn't manage to get rid of the problem. I tried to overvolt cpus, gpus, busses and it didn't make any difference. I repartitioned the phone with a different PIT file and it didn't help either. If you have anything else to suggest please do so.

I tried that, too and also updated to Pure Stock ROM v5.4 with hacker kernel.
No more issues for me since ~24 hours, compared to twice before. I hope it'll stay like that.
Gesendet von meinem SM-G920F mit Tapatalk

Just a small update for ppl that are having similar issues. The only thing that seems to bring my phone back to normal state is heat: if I heat my phone from both sides with a hairdryer for 10-20 seconds it comes back to life with no problem at all. Nothing else seemed to help.
Apart from that, @Setialpha recently published a ROM that hopefully solves the random lockups, reboots etc. I'll try it and report back.
Give it a go and if it works thank the dev!

Wait...you heat it up and it works?
Could it be the multicore powersave?
(Saves energy shutting off cores)
Sent from my GT-I9300 using XDA-Developers mobile app

Problem found
Hello guys i found a temporary fix for this problem i think its a software bug, a cpu gouvernor related bug.
What i did ??
I flashed a custom rom based on mashmallow then i flashed hacker kernel i tried changing different kernel settings but it didnt fix the problem...what it actually worked was changing the cpu governor from the stock interactive to ondemandplus and the problem never came back ! Please try that and get back to me
PSndemandplus governor drains battery more than stock interactive because it keeps the cpu cores awake.

Question AOD and screen wake on notifications stopped working

Hi all!
I've been searching for a solution for some time but couldn't find any.
Always On Display stopped working on my Pixel 6a. It's all turned on in the settings but it simply doesn't work. It works only in those cases:
1. When device is rebooted into an Airplane mode
2. When device is rebooted into the Safe Mode
3. When device is rebooted but not unlocked for the first time
There are also no notifications displayed so screen wake on notification doesn't work. Same story as above.
I thought there is some app blocking it but couldn't really figure out which, I tried to disable many of them but none helped.
I did a factory reset once but issue came back after few days.
I seriously have no idea what might it be. Hope someone here might have had similar problem and found a solution.
Thanks!

Czarls said:
Hi all!
I've been searching for a solution for some time but couldn't find any.
Always On Display stopped working on my Pixel 6a. It's all turned on in the settings but it simply doesn't work. It works only in those cases:
1. When device is rebooted into an Airplane mode
2. When device is rebooted into the Safe Mode
3. When device is rebooted but not unlocked for the first time
There are also no notifications displayed so screen wake on notification doesn't work. Same story as above.
I thought there is some app blocking it but couldn't really figure out which, I tried to disable many of them but none helped.
I did a factory reset once but issue came back after few days.
I seriously have no idea what might it be. Hope someone here might have had similar problem and found a solution.
Thanks!
Click to expand...
Click to collapse
Would you be down to try flashing a custom ROM?
I've read in another thread not long ago someone saying their Tap to Wake randomly stopped working. We narrowed it down to an issue with the proximity sensor (so the phone thought it was in a pocket/covered, therefore didn't let Tap to Wake work, he had to use the power button to turn the screen on). He then flashed a custom ROM (it was LOS, I think), and that solved the issue for him.
I've also had some issues with the stock ROM, flashing a non-factory one solved all of them
If you want to keep on using the factory ROM, you might wanna try using the Android Flash Tool instead of just factory resetting to make sure no corrupted settings can live on.

Lada333 said:
Would you be down to try flashing a custom ROM?
I've read in another thread not long ago someone saying their Tap to Wake randomly stopped working. We narrowed it down to an issue with the proximity sensor (so the phone thought it was in a pocket/covered, therefore didn't let Tap to Wake work, he had to use the power button to turn the screen on). He then flashed a custom ROM (it was LOS, I think), and that solved the issue for him.
I've also had some issues with the stock ROM, flashing a non-factory one solved all of them
If you want to keep on using the factory ROM, you might wanna try using the Android Flash Tool instead of just factory resetting to make sure no corrupted settings can live on.
Click to expand...
Click to collapse
I would say it does not have anything in common with the proximity sensor since it works fine with airplane mode turned on. I want to stay with the factory ROM. Maybe it's an issue that will be fixed any time soon?

Czarls said:
I would say it does not have anything in common with the proximity sensor since it works fine with airplane mode turned on. I want to stay with the factory ROM. Maybe it's an issue that will be fixed any time soon?
Click to expand...
Click to collapse
Why do you ask for advice if you just want to "wait for it to get fixed"?
If you've done a factory reset already, it's not a hassle re-flashing the factory ROM (since you already have your data backed up).
Fwiw, the guy with the proximity sensor issue also had it sometimes work and other times not, much like your issue

Lada333 said:
Why do you ask for advice if you just want to "wait for it to get fixed"?
If you've done a factory reset already, it's not a hassle re-flashing the factory ROM (since you already have your data backed up).
Fwiw, the guy with the proximity sensor issue also had it sometimes work and other times not, much like your issue
Click to expand...
Click to collapse
I'm trying to figure out if it's a software issue in a ROM or some applications impact..