Related
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
random shutting down
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.
ice3186 said:
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.
Click to expand...
Click to collapse
I havent been using ATK at all. Also does SetCPU really work with the hummingbird processor? When it boots it always kicks down to 19.2 which is obviously too low. I removed it just in case. I also set it back to the default settings. I would really enjoy SetCPU to save battery if it works of course. I thought it only works on HTC devices and Motorola devices?
i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.
domin8 said:
i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.
Click to expand...
Click to collapse
I deleted SetCPU and I thought it might be Screebl so I disabled it. Sure as hell it just went to a black screen and shut off again. God this is beyond annoying. I dont want to have to bring back this great phone but I need the phone to work.
We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.
madjsp said:
We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.
Click to expand...
Click to collapse
Yes but if I am correct none of these issues will be fixed until they decide to release FroYo?
EDIT: I just tried removing the MicroSD to see if that resolved the issue. Shocker...it didnt...
spyz88 said:
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
Click to expand...
Click to collapse
This has happened to me once. Came out of a meeting, pulled it out of my pocket, and couldn't get it to wake from sleep. I have not installed SetCPU, so it's not that. Not sure what the root cause was.
What apps do you have installed would probably be the more relevant question. And what have you changed?
Mine is doing the same **** and it is driving me NUTZ!!! I thought SetCPU first so I uninstalled and rebooted. Phone is still doing it. Please someone figure this out quickly. I am going through my apps one by one and uninstalling them to try to pinpoint the problem. Subscribing to the thread.
Interesting.... I haven't heard this happen to me yet so its probably an application or process your guys all have in common.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have a feeling it is setcpu. I just did a reboot after installing and now it is not happening. Cross my fingers!
I'm having the same issue and I never had setCPU installed. sucks..
-Teklock
Like a lot of you, I started uninstalling my apps one by one when this happened. It stopped restarting after I finally uninstalled Launcher Pro. After that, the phone stayed on the whole night last night. It's weird because it worked with Launcher Pro for a good 2 days.
I'm also experiencing this issue, ad i've only downloaded a few apps.
Has anyone exchanged their phone over this yet?
Teklock said:
I'm having the same issue and I never had setCPU installed. sucks..
-Teklock
Click to expand...
Click to collapse
I reflashed to stock firmware and I'm still having an issue. I noticed that if you take the battery cover off the battery and push on it then it seems like it has a little give to it. Can anyone who is not having this problem confirm? Also, anyone who has this issue, please see if your battery has a little give to it.
It should be on the side WITHOUT the contacts. Also, if this doesn't work I'm bringing the phone back. I already had a problem with the first one and since this is my 2nd exchange AT&T wont exchange it anymore. They told me I need to go through the warranty. They are out of their minds the phone isn't even a week old. Never had these problems with HTC...
EDIT: I uninstalled ADW Launcher as a test to see if thats it.
EDIT 2: Make sure the battery door is covered tightly. I pushed mine all the way down until it clicks. Hold it down and then close the slider. I think this actually might fix the issue.
Anyone figure out why this keeps on happening? I've reflashed the stock as well and it still occurs randomly.
Strange this dosnt happen to me, and i installed setcpu(performance governor 1ghz/800mhz) but uninstalled it after seeing that it ****'s up gles 2 rendering...
I found this thread via Google search, and I just wanted to add that my phone started doing this last night, however, I have not added anything to my phone, nor is it modded in any way. It's completely stock. The only thing I have done thus far was remove all of the extra home pages and rearrange some app icons, and that was on Thursday and Friday. It does it both when it goes to sleep normally or if I hit the sleep/power button.
I narrowed mine down to SetCPU being underclocked while asleep. Bumped up the minimum clock and took off the profile I had set, phone hasn't rebooted in 4 days.
I've been getting these weird "flashes". Sometimes the screen actually flashes white and sometimes not, but when it happens (once every few minutes or sometimes even several times a minute), if I'm in Chrome, the bar will appear, if I'm in an IM app the keyboard will disappear and reappear and then if I continue typing, it moves the cursor to a random spot in my typed passage and replaces a word with the last word I typed, if I'm in the YouTube app, the video will restart, if I'm watching a video in the normal video player, the video will pause, etc. This has happened on two Moto Xs after rooting. I tried disabling every customization I instaled (a few Xposed modules) and I still had the problem. The PwnMyMoto root has to be the cause, unless I'm missing something. Any ideas on how to get these to go away?
Slusho,
That is not normal, nor is it happening to my rooted+SS Moto X.
I recommend flashing back to stock and starting over. The problem could be hardware related, but based on your description it sounds like software.
I am not experiencing this issue either. I'm on stock and rooted with PwnMyMoto. I would go with what Ctrl-Freak said. Try going back to stock.
Because I've experienced this on every device I root, how would going back to stock and rerooting fix it? It's certain to happen again.
Slusho said:
Because I've experienced this on every device I root, how would going back to stock and rerooting fix it? It's certain to happen again.
Click to expand...
Click to collapse
You should go back to stock and not reroot to see if it is truly root that is causing the problem.
Dark9781 said:
You should go back to stock and not reroot to see if it is truly root that is causing the problem.
Click to expand...
Click to collapse
Okay I'm trying it. I have to back everything up, unroot, check if it's still happening, root, check if it's still happening, and restore everything. It'll take a while. I don't think I can just back up in one fell swoop like on custom recoveries, right?
Okay I've confirmed it doesn't happen when not rooted (as it didn't before). Moving to root...
...and it isn't happening. Strange. I'll enable the Xposed modules now, but I already troubleshot that, so it shouldn't cause it.
And that didn't cause it to happen either. I don't know what's changed, and this mystery will haunt me for the rest of my days...
Thanks though.
I went to bed and it was fine, but I wake up and my phone's back to doing the flashes. Another thing is that I freeze Updater but the update dialog still pops up. I doubt they're related but I guess I should mention it.
Sounds to me like a faulty digitizer. Had similar issue with previous device. Sometimes wouldn't happen for months. Some ROMs seemed to provoke it more as well. When it happens again, go into dev options and select show touches or grab a painting/drawing app off play. Run the app when its acting up and you may see it drawing by itself. That or your phones haunted, it is almost Halloween.
Tried it, and it didn't register any touches. These things that happen can't happen due to touches anyway. And this has happened on every Moto X I've rooted. Perhaps it won't happen if I use the old root method?
The problem is present with the old root too. Guess I just can't have root on my Moto X.
Slusho said:
The problem is present with the old root too. Guess I just can't have root on my Moto X.
Click to expand...
Click to collapse
I'm sure you are tired of troubleshooting but, no one else is reporting having this problem. So its either something you are setting up on your phone, or you should return your phone. It may have something to do with what you are restoring after you root.
jayboyyyy said:
I'm sure you are tired of troubleshooting but, no one else is reporting having this problem. So its either something you are setting up on your phone, or you should return your phone. It may have something to do with what you are restoring after you root.
Click to expand...
Click to collapse
I'm only restoring normal Play Store apps that I doubt are doing this, Xposed, MotoXposed, Gravity Box, and Advanced Power Menu. I tried disabling those and it didn't stop the flashing, so I didn't think it was the Xposed modules, but I'll try wiping and rerooting my phone without those. If that doesn't work, I'll just use it unrooted. Does anyone know of some diagnostic software that could detect what's doing this? Also, this has happened on multiple devices and only after rooting so I don't see how it could be a hardware problem.
Slusho said:
I'm only restoring normal Play Store apps that I doubt are doing this, Xposed, MotoXposed, Gravity Box, and Advanced Power Menu. I tried disabling those and it didn't stop the flashing, so I didn't think it was the Xposed modules, but I'll try wiping and rerooting my phone without those. If that doesn't work, I'll just use it unrooted. Does anyone know of some diagnostic software that could detect what's doing this? Also, this has happened on multiple devices and only after rooting so I don't see how it could be a hardware problem.
Click to expand...
Click to collapse
perhaps you are using the wrong root exploit?
jayboyyyy said:
perhaps you are using the wrong root exploit?
Click to expand...
Click to collapse
I've used both of jcase's Moto X root exploits.
jayboyyyy said:
perhaps you are using the wrong root exploit?
Click to expand...
Click to collapse
Slusho said:
I've used both of jcase's Moto X root exploits.
Click to expand...
Click to collapse
I think jayboyyyy meant was did you grab the right one for your carrier?
Sent from my Moto X
Slusho said:
. Does anyone know of some diagnostic software that could detect what's doing this? Also, this has happened on multiple devices and only after rooting so I don't see how it could be a hardware problem.
Click to expand...
Click to collapse
Terminal emulator and logcat
Dark9781 said:
I think jayboyyyy meant was did you grab the right one for your carrier?
Sent from my Moto X
Click to expand...
Click to collapse
Oh. Yes, I did.
xxxo said:
Terminal emulator and logcat
Click to expand...
Click to collapse
I tried logcat with adb. I take it anytime it says "E/" there's an error. I tested it when Chrome makes the top bar appear randomly, and got a ton of
Code:
E/ActivityThread ]
Failed to find provider info for com.motorola.blur.setupprovider
I tried it while playing a video in the default video player and got a lot of
Code:
E/AwesomePlayer ]
LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec
as well as
Code:
E/OMX-VDEC-1080P
I got that a lot while playing YouTube as well.
These errors come up dozens of times a second. This is getting too low level for me to understand. I can't find the specific moment/problem since there are hundreds of lines generated for just a minute of logging.
Slusho said:
I tried logcat with adb. I take it anytime it says "E/" there's an error. I tested it when Chrome makes the top bar appear randomly, and got a ton of
Code:
E/ActivityThread ]
Failed to find provider info for com.motorola.blur.setupprovider
I tried it while playing a video in the default video player and got a lot of
Code:
E/AwesomePlayer ]
LPAPlayer::Clip duration setting of less than 30sec not supported, defaulting to 60sec
as well as
Code:
E/OMX-VDEC-1080P
I got that a lot while playing YouTube as well.
These errors come up dozens of times a second. This is getting too low level for me to understand. I can't find the specific moment/problem since there are hundreds of lines generated for just a minute of logging.
Click to expand...
Click to collapse
just to clarify, you did try rooting the device without running tibu to set your apps back up and you still ran into the issue? If it failed to find motorola blur stuff it seems that you may have restored some stuff with tibu accidentally that is screwing up some system apk's. I'm not sure this is the case, but again, you are the only one reporting this so in the end I still really feel it is something you are doing. The errors you are reporting should not be affected when rooting your phone unless you are altering something post root that you are unaware you are altering or that you think you aren't altering but in fact you are.
Touchscreen Issue: This thing has been persistent from the very beginning. After struggling for months, it has been mostly fixed with the last update. But double tap to wake is still a 50/50 chance, most of the time it's 4 taps to wake.
WiFi Issue: I have come across may complaint across internet about wifi issue for LG G4, ppl suggested several solutions but none really worked. Wifi connection suddenly drops, and also takes a considerable amount of time when waking up from sleep. It gets very annoying when I am on a voip or hangout call.
No it's not my router or my phone. Because it's the same on my home and work network, where other devices just work fine. Also I don't have any of those issues on CM12.1 rom. CM is quite nice on LG G4 but having to be using it on CM is not an option, as I lose the camera.
Besides I didn't pay the money to purchase a flagship device to use it on a different rom.
So, that's it. LG better fixes it on the Marshmallow, otherwise Good Bye LG.
Update: The WiFi is much better since I uninstalled Xposed. I am guessing that some xposed module had something to do with it. Can anybody confirm?
No change in the double tap to unlock though. Funny thing is that it works perfectly with CM.
Sorry to hear you are still having issues with your device. My only issue is the double tap to wake/sleep, but its something that I can live with. I never had an issue with wifi on any network, work/home/neighbors, ever.
Have you tried any of the roms supplied by our great devs or are you on stock?
esjames said:
Sorry to hear you are still having issues with your device. My only issue is the double tap to wake/sleep, but its something that I can live with. I never had an issue with wifi on any network, work/home/neighbors, ever.
Have you tried any of the roms supplied by our great devs or are you on stock?
Click to expand...
Click to collapse
I tried stock rooted debloated, also stock-based xtreme rom. Always having these issues.
Hmm..... Thats weird, My G4 has been runing good since I first purchased it in september..... Guess I got lucky.
I feel the ops pain, because I've had the WiFi issues a few times, and the tap to wake is 50/50 at best. I'm also growing tired of waiting for updates from LG or Tmo.
The poor 5GHz wifi support kills me. Only device in the household that has that issue. Other than that, though, I've been pretty happy with the G4.
I purchased my G4 a month ago and don't have those issues. Double tap works fine and my phone uses 5g WiFi at home. I wish you luck op.
As far as the WiFi is concerned, I have the same problem. Using WiFI Analyzer, I can see that all available wireless networks near me drop to 0 every minute or so, and then start back up. My wife also has a G4, and her device does not do that. I'm wondering if there was either a bad batch of WiFi radio chips, or poor connections to the mainboard for a group of these.
I think the tap to wake issue is because of that other stupid "feature" that I'm sure not a single person uses.
You know the one where when the screen is off, you swipe down from the top of the screen and it shows the clock? My phone often mistakes my taps to wake as swipes and tries to activate that instead (I can tell because the notification led comes on when that is activated).
Is there any way to turn that thing off? It is completely useless. It would be one thing if it showed the notifications but no it just shows the clock
aptalca said:
I think the tap to wake issue is because of that other stupid "feature" that I'm sure not a single person uses.
You know the one where when the screen is off, you swipe down from the top of the screen and it shows the clock? My phone often mistakes my taps to wake as swipes and tries to activate that instead (I can tell because the notification led comes on when that is activated).
Is there any way to turn that thing off? It is completely useless. It would be one thing if it showed the notifications but no it just shows the clock
Click to expand...
Click to collapse
I agree with you on... that is probably the case. A completely useless feature, which also doesn't work half the time.
suhridkhan said:
Touchscreen Issue: This thing has been persistent from the very beginning. After struggling for months, it has been mostly fixed with the last update. But double tap to wake is still a 50/50 chance, most of the time it's 4 taps to wake.
WiFi Issue: I have come across may complaint across internet about wifi issue for LG G4, ppl suggested several solutions but none really worked. Wifi connection suddenly drops, and also takes a considerable amount of time when waking up from sleep. It gets very annoying when I am on a voip or hangout call.
No it's not my router or my phone. Because it's the same on my home and work network, where other devices just work fine. Also I don't have any of those issues on CM12.1 rom. CM is quite nice on LG G4 but having to be using it on CM is not an option, as I lose the camera.
Besides I didn't pay the money to purchase a flagship device to use it on a different rom.
So, that's it. LG better fixes it on the Marshmallow, otherwise Good Bye LG.
Click to expand...
Click to collapse
Not sure if you seen in the g4 dev section there is a flashable zip for a camera now. I'll never go back stock.
It's your phone... Those problems don't exist for everyone.
Sent from my LG-H811 using Tapatalk
Video recording not working after rooting.
Someone help please! I after rooting my LG G4 h811. My video recording stopped working. My snapchat videos will also not load. I what is the problem and what is can I do to fix this?
Crispy0707 said:
Someone help please! I after rooting my LG G4 h811. My video recording stopped working. My snapchat videos will also not load. I what is the problem and what is can I do to fix this?
Click to expand...
Click to collapse
Did you just root, or are you using other apps that uses root access? Did you uninstall or delete any system app?
It's very unlikely that rooting would break the camera. Try unrooting.. Super Su has the option to unroot in its settings. If doesn't work you may have to do a factory reset.
suhridkhan said:
Did you just root, or are you using other apps that uses root access? Did you uninstall or delete any system app?
It's very unlikely that rooting would break the camera. Try unrooting.. Super Su has the option to unroot in its settings. If doesn't work you may have to do a factory reset.
Click to expand...
Click to collapse
I rooted and installed wtrp, the first app I opened was snapchat and I was not able to open video snaps or make my own. I thought it was the app being supervised and I didn't check the camera app recording. I later installed apps for root like xposed installer to obtain snapprefs, but the problem continued to appear. After the download of a few apps and mods for root. I downloaded instagram and I was still not able to record videos. Finally I opened the camera and it was the same problem. I unrooted my phone and the video recording is working. I will root again and only test the camera app after root and after each app and mod I added before. I did try the factory reset and no luck.
Crispy0707 said:
I rooted and installed wtrp, the first app I opened was snapchat and I was not able to open video snaps or make my own. I thought it was the app being supervised and I didn't check the camera app recording. I later installed apps for root like xposed installer to obtain snapprefs, but the problem continued to appear. After the download of a few apps and mods for root. I downloaded instagram and I was still not able to record videos. Finally I opened the camera and it was the same problem. I unrooted my phone and the video recording is working. I will root again and only test the camera app after root and after each app and mod I added before. I did try the factory reset and no luck.
Click to expand...
Click to collapse
Since you already got twrp up and running, I can try MicroMod777's stock rooted debloated rom.
Never had problems with my H811 even installed different ROMs from LP to MM and back. Never had hardware issues.
My only problem with the h811 is the stupid gps not shutting off and killing the battery, fixed by app ops
I'm stock everything and my notifications have basically just stopped working out of no where. I've tried every solution there is on the web to fix it except a factory reset - is this what it comes down to? Do I have to factory reset every few months just to keep the phone running normally? That's not really ideal.
partylikeaninjastar said:
It's your phone... Those problems don't exist for everyone.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
this
Hello there,
I've just bought Infinix Hot 2 (1GB version) because it's the only Android One device in Egypt (Awesome specs for the price, too!)
I was wondering if the current Marshmallow build is stable enough for daily use/doesn't have major bugs and if you think I should upgrade right away or stay on Lollipop for a while?
SAM209 said:
Hello there,
I've just bought Infinix Hot 2 (1GB version) because it's the only Android One device in Egypt (Awesome specs for the price, too!)
I was wondering if the current Marshmallow build is stable enough for daily use/doesn't have major bugs and if you think I should upgrade right away or stay on Lollipop for a while?
Click to expand...
Click to collapse
do not upgrade it now until a stale one comes out
its good enough for daily use,just backup your data first or you will lose it when you update
Well... Apart from all the marshmallow goodies the phone sometimes behaves weirdly, like when you leave the phone for a while then push the power button the screen takes about 5 seconds to turn on, no idea why maybe it's not stable yet as others said and it has to do with doze but otherwise I haven't encountered any major bugs, crashes... Etc.
I hope they will roll a patch soon though, maybe you should wait until then if you're worried.
i have not gotten my own update..... whats going on???
is it available in Nigeria yet??
Gotten mine
mitchy_feargod said:
i have not gotten my own update..... whats going on???
is it available in Nigeria yet??
Click to expand...
Click to collapse
I'm in Nigeria & I got the update. It's 836.6MB in size but I haven't installed it.
i dont like it
lolipop more stable and smooth
Barbiox Dogg said:
I'm in Nigeria & I got the update. It's 836.6MB in size but I haven't installed it.
Click to expand...
Click to collapse
but why havent i gotten my own yet .....maybe they paused the rollout coz of the issue......when did you recieve ur update:crying:
quite buggy update
My girlfriend updated her Hot 2, and there are quite a few issues
* As previoulsy stated, when the phone is in sleep mode, and when pressing the power button, it can take a few seconds for the screen to display the lock screen..
* When she wants to hang up a call, sometimes the screen stays black, sometimes the screen shows the hang up button, but it is not possible to click it, and she has to wait that the other side terminates the call
* caller name display does not work correctly, depending on how the caller's number is entered in contact list (with spaces between digits, and minus, etc....).
* when using to sim and configured "always ask" for sending SMS, it is not possible to send SMS anymore. When pressing the send button, an error message states that no prefered network is selected. SMS network must be forced in SIM menu
* contact list management is bad : merging seems to be broken, deleting duplicate entries prevents selecting remaining entries, and so on
I'm considering to rollback to 5.1, current bugs are very annoying and prevents correct usage of the phone, while it was working very well previously
Temporary fix for delay on screen light waking up
Hi, anyone who updated to marshmallow is facing the issue with the screen taking too long to awaken.
To fix that you can go to the play store and instal an app called wake lock.
Once you've installed it, select: PARTIAL_WAKE_LOCK.
This seemed to solve the problem with the screen taking too long to wake up but it came at the cost of battery life. The battery drains a little quicker than regular.
This also fixes the issue with the screen not responding or coming back on after you make/receive a call.
The issue with the contact names not showing is annoying and I still haven't figured out how to fix that yet. Let's just hope Google fixes it soon.
Hope this helped.
guys , i am already on marshmallow but i got nw another update 836.6 mb
anyone got that update ?
Got the same update you are talking about. It's the monthly security patch for February. Came with some changes to the system like audio profiles and "do not disturb" when u swipe from the top of the screen and some other stuff. Try it out
Mine same
I used infinix hot 2 (2gb).. Laggy happened and freezing
I lost all of my data.. All my files... Everything. So pissed. But apparently, the files still take up all the space they took up. So my phone is still full.
Haps Rehsi said:
Hi, anyone who updated to marshmallow is facing the issue with the screen taking too long to awaken.
To fix that you can go to the play store and instal an app called wake lock.
Once you've installed it, select: PARTIAL_WAKE_LOCK.
This seemed to solve the problem with the screen taking too long to wake up but it came at the cost of battery life. The battery drains a little quicker than regular.
This also fixes the issue with the screen not responding or coming back on after you make/receive a call.
The issue with the contact names not showing is annoying and I still haven't figured out how to fix that yet. Let's just hope Google fixes it soon.
Hope this helped.
Click to expand...
Click to collapse
I deleted all my contacts and re-imported them from a .vcf backup I had and they're working fine now!
I'm currently own infinix hot 2 2gb model with M installed in it. The cameras (rear-front) becomes dark when taking a video on apps (except default camera for sure). As also having the same problems above you guys have explained. Any one have camera bugs too? Why M released too soon for IH2 if it comes with tons of bugs? ?
sixtus ohans said:
I lost all of my data.. All my files... Everything. So pissed. But apparently, the files still take up all the space they took up. So my phone is still full.
Click to expand...
Click to collapse
Actually the files are not lost. They just in a folder which is hidden. You only see them when you root the phone... After rooting, just enable root explorer in a file manager like es explorer and u will see them..
olalbinx said:
Actually the files are not lost. They just in a folder which is hidden. You only see them when you root the phone... After rooting, just enable root explorer in a file manager like es explorer and u will see them..
Click to expand...
Click to collapse
Hi, thanks for the suggestion. I have a similar issue. Please How do I go about rooting the phone in such a way that I won't lose my data? What working method do you suggest I use?
olalbinx said:
Actually the files are not lost. They just in a folder which is hidden. You only see them when you root the phone... After rooting, just enable root explorer in a file manager like es explorer and u will see them..
Click to expand...
Click to collapse
But each time I try to turn on the root explorer it says. This feature cannot work on your phone.... Please, what do I do?
Have turned off AOD as I don't need it nor want it and the white fingerprint circle pops up every ten seconds or so even though I've said I don't want AOD.
Has anyone else got this crap behaviour??
dladz said:
Have turned off AOD as I don't need it nor want it and the white fingerprint circle pops up every ten seconds or so even though I've said I don't want AOD.
Has anyone else got this crap behaviour??
Click to expand...
Click to collapse
LoL! Try Settings-Personalizations-Fingerprint animation-None
galaxys said:
LoL! Try Settings-Personalizations-Fingerprint animation-None
Click to expand...
Click to collapse
Haha it is
Haha, well then select settings in there, and Fingerprint Off
Lol honestly mate, AOD is off and fingerprint animation is also off. Try it yourself, I think it's a bug.
I've just turned on AOD, going to leave that bitmoji thing on. Why not.
I've tried everything to get rid of the FP, it just won't go.
Yeh sounds like a , I don't use Fingerprint and I leave aod on...
Cheers
galaxys said:
Yeh sounds like a , I don't use Fingerprint and I leave aod on...
Cheers
Click to expand...
Click to collapse
I'm sure if you tried it would do the same thing. Probably one of the many issues.
It's definitely a beta this firmware
dladz said:
I'm sure if you tried it would do the same thing. Probably one of the many issues.
It's definitely a beta this firmware
Click to expand...
Click to collapse
Just tried on my Global usa model and I'm not seeing it. Also, I've never added a fingerprint to the device....
galaxys said:
Just tried on my Global usa model and I'm not seeing it. Also, I've never added a fingerprint to the device....
Click to expand...
Click to collapse
Lol no idea then mate.
Not the end of the world
dladz said:
Have turned off AOD as I don't need it nor want it and the white fingerprint circle pops up every ten seconds or so even though I've said I don't want AOD.
Has anyone else got this crap behaviour??
Click to expand...
Click to collapse
I even went so far as to disable the system AOD apk via an apk disabler tool & that did not work.
IDK if you ever found the actual toggle to turn it off......I finally found it by selecting the search result in Settings.
I typed in Always & stopped there,finding "Always-On Display".
The toggle is at the very top of the page (FWIW,I missed this earlier when in the settings,it was easy for me to overlook the toggle in dark mode).
If you've already tried this & it's still coming on,here's what I'm trying for the next day or so:
Turn Always-On Display back on & set a scheduled time for one minute.
For example,I've got it turning on at 4:00 A.M. & turning off at 4:01 A.M.
ATM,option 2,the scheduled on/off time,seems to be working.
EDIT;after a few minutes,AOD is coming back on.
This is annoying....... Not looking good as a keeper,not liking OxyColor OS at all,what a mess compared to the OP7T Pro.
Not just this,but,the settings layout (for individual app settings is a trainwreck & power/performance options not sticking,keeps reverting back to out-of-box settings.
Well I think I found a permanent fix for this...it's actually a bug (in my case anyway)
I was forced to wipe my phone, which was a huge pain due to a problem with a mod I'd installed..
Anyway on boot I set everything back up then realised it's got AOD on by default and I went a turned it off.
Low and behold it stayed off..no need to do anything.
So what I think has happened is the update that came recently (11_A.12) that could have caused issues, always good to wipe after an update.
I honestly don't know if this will fix things for you, but it did for me.
Couple that with the fact that I'm now getting unbelievable battery life...I think it's maybe a good idea to at least try, you may not fix your AOD but you may get better battery. As I did, I think you'll probably get both.
Here's a bunch of pics from the last 24 hours, midnight on Thursday evening /start of Friday up till now.
Absolutely amazing.
dladz said:
Well I think I found a permanent fix for this...it's actually a bug (in my case anyway)
I was forced to wipe my phone, which was a huge pain due to a problem with a mod I'd installed..
Anyway on boot I set everything back up then realised it's got AOD on by default and I went a turned it off.
Low and behold it stayed off..no need to do anything.
So what I think has happened is the update that came recently (11_A.12) that could have caused issues, always good to wipe after an update.
I honestly don't know if this will fix things for you, but it did for me.
Couple that with the fact that I'm now getting unbelievable battery life...I think it's maybe a good idea to at least try, you may not fix your AOD but you may get better battery. As I did, I think you'll probably get both.
Here's a bunch of pics from the last 24 hours, midnight on Thursday evening /start of Friday up till now.
Absolutely amazing.
Click to expand...
Click to collapse
Are you using an Unlocked model, or a carrier (T-Mobile US) model (& are you rooted or unrooted)?
THX.
Turn this off
KOLIOSIS said:
Are you using an Unlocked model, or a carrier (T-Mobile US) model (& are you rooted or unrooted)?
THX.
Click to expand...
Click to collapse
EU unlocked. Ne2213
Bliszcur said:
View attachment 5596247
Turn this off
Click to expand...
Click to collapse
It was mate, they all were, it was a bug.
dladz said:
Well I think I found a permanent fix for this...it's actually a bug (in my case anyway)
I was forced to wipe my phone, which was a huge pain due to a problem with a mod I'd installed..
Anyway on boot I set everything back up then realised it's got AOD on by default and I went a turned it off.
Low and behold it stayed off..no need to do anything.
So what I think has happened is the update that came recently (11_A.12) that could have caused issues, always good to wipe after an update.
I honestly don't know if this will fix things for you, but it did for me.
Couple that with the fact that I'm now getting unbelievable battery life...I think it's maybe a good idea to at least try, you may not fix your AOD but you may get better battery. As I did, I think you'll probably get both.
Here's a bunch of pics from the last 24 hours, midnight on Thursday evening /start of Friday up till now.
Absolutely amazing.
Click to expand...
Click to collapse
I just got the 1st system update for the T-Mobile US version.
The AOD option to turn it off is now working.
Here's what is/was strange, pre-update:
The only way I could see/access the Always-On Display settings/toggle was to have the stock OnePlus Launcher as the default home app.
Even then, AOD stayed on, whether toggled on or off.
I was able to figure this out from prior experience with the original Oppo Find X & VIVO NEX.
Very strange that certain (seemingly unrelated) settings would be hidden due to choice of home launcher,but,apparently,BBK doesn't see this as an issue/bug(feature, LOL) that needs to be addressed, guessing this "feature" is persistent on the home market China models/firmware.
Glad it was cleaned up for the T-Mobile US update.
On a somewhat related note, pre-update, I could not find a way to choose "No Lock Screen". I looked in the usual place to find such & it was not available, AFAIK.
Now, post-update, that setting is found in "Developer Options". (Why?????? LOL)
On an unrelated note, post-update, another bug has apparently been taken care of for the T-Mobile US version :
T-Mobile bloatware apps now stay disabled, if chosen to do so. Pre-update, they would re-appear after a reboot.
With these bug fixes, my outlook on keeping this phone has definitely changed for the positive. I still have about 10 days remaining before T-Mobile's buyer's remorse return window closes.