Hi,
Just wanted to share a bug I found with a friend, regarding the otg feature. Doing a quick look on xda, I've notices that this bug is also present on other Samsung devices, such as the SGSII and the Galaxy Note.
After disconnecting a storage device (such as a pendrive), the unmount process keeps running, preventing the phone going into deep idle status (see pictures below).The issue is solved by restarting the device (I guess you can kill the process/service if the phone is rooted, haven't looked deeper yet). I discovered it after having a serious battery drain yesterday night and thanks to BetterBatteryStats.
Maybe some of you have run into this issue and found a fix.
{
"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"
}
Cheers
Same thing happens on my S3.
I think we may all have the same problem. Even GNote and SGS2...
There are many threads on this regard on XDA, (e.g. http://forum.xda-developers.com/showthread.php?t=1525860) and I think we should keep investigating. There should be a way of make a script to kill the process (or propery unmount).
EDITED: After some tests, it seems that if you unplug or go to the notification bar and click unmount, it will trigger the issue. But, try the following:
Go to Settings, Storage, scroll to the end and hit Unmount OTG Storage
It won't trigger the bug. Confirmed by at least 2 devices.
alex_herrero said:
I think we may all have the same problem. Even GNote and SGS2...
There are many threads on this regard on XDA, (e.g. http://forum.xda-developers.com/showthread.php?t=1525860) and I think we should keep investigating. There should be a way of make a script to kill the process (or propery unmount).
EDITED: After some tests, it seems that if you unplug or go to the notification bar and click unmount, it will trigger the issue. But, if you go to Settings, Storage, scroll to the end and hit Unmount OTG Storage, it won't trigger it. Did any of you try it this way?
Click to expand...
Click to collapse
I just tested it and when unmounted the way you described, the bug doesn't appear. Decent temporary fix until Samsung gets around to fixing it.
Well, that's it then! Solved!
So you know, if anyone's still looking, I've got a 6810 with the UK 4.0.4 stock (rooted), which displays the same behaviour but the fix suggested doesn't work, the only thing that does is a reboot after disconnecting any USB storage.
EDIT - retracted, the workaround does work, I was looking at old data.
alex_herrero said:
I think we may all have the same problem. Even GNote and SGS2...
There are many threads on this regard on XDA, (e.g. http://forum.xda-developers.com/showthread.php?t=1525860) and I think we should keep investigating. There should be a way of make a script to kill the process (or propery unmount).
EDITED: After some tests, it seems that if you unplug or go to the notification bar and click unmount, it will trigger the issue. But, try the following:
Go to Settings, Storage, scroll to the end and hit Unmount OTG Storage
It won't trigger the bug. Confirmed by at least 2 devices.
Click to expand...
Click to collapse
I was directed to this thread from the Note forum. On the Note, running the latest German ICS 4.0.4 release this option does not exist within the storage settings. The only option I have found is to unmount from the notification bar. This method is still invoking the wakelock, so no fix for us Note users yet, it would appear.
I had to reboot just to save my device and my sanity.
tdodd said:
I was directed to this thread from the Note forum. On the Note, running the latest German ICS 4.0.4 release this option does not exist within the storage settings. The only option I have found is to unmount from the notification bar. This method is still invoking the wakelock, so no fix for us Note users yet, it would appear.
I had to reboot just to save my device and my sanity.
Click to expand...
Click to collapse
Hi, i'm a new user. After a couple of tests with my galaxy note, i have seen that removing the usb pen "directly" without click on the safe removal notification doesn't activate the bug.
However, even if you safe remove your usb storage, kill the MTP usb mount process by going into "settings--->applications--->running--->show cached process on the bottom on the page, the bug is still here.
Oh crap, just noticed my SGN has this bug (running NoteCore with CleaNote). And even after stopping the MTP USB Mount process from cached applications, it still shows up in BBS i.e. still running. :|
Yep. Same here. Everytime I remove the USB stick I forget to reboot and phone doesn't sleep. Next time I will try the fix. What a f... up Samsung.
Sent from my GT-I9300 using xda premium
Is there some where we can go to file this bug with samsung?
UsbStorageUnmountter
Same thing on my S3 with original actual Samsung firmware. I must reboot to deactivate the UsbStorageUnmountter.
alex_herrero said:
I think we may all have the same problem. Even GNote and SGS2...
(...)
There should be a way of make a script to kill the process (or propery unmount).
EDITED: After some tests, it seems that if you unplug or go to the notification bar and click unmount, it will trigger the issue. But, try the following:
Go to Settings, Storage, scroll to the end and hit Unmount OTG Storage
It won't trigger the bug. Confirmed by at least 2 devices.
Click to expand...
Click to collapse
Possibly off-topic, but I found the same issue exists, and workaround works, for my Galaxy Tab 8.9 (P7300 (3g), but with P7310 (wifi-only) stock ICS). Thanks for the hint I will post this workaround in our own sub-forum, with credits.
I've searched around for a way to kill the UsbStorageUnmountter, but couldn't find one.
I noticed that "Quick System Info Pro", in the Processes tab, will show a (thread/activity/whatever) under "Android System" called "UsbStorageUnmountter", when the bug was triggered (by unmounting from notifications). I haven't tried yet to kill this process (pid=191)... my instinct says it does more than just usb unmounting, so I doubt it's "safe" to kill. To be continued...
Thank GOD, i am not the only one here
alex_herrero said:
I think we may all have the same problem. Even GNote and SGS2...
There are many threads on this regard on XDA, (e.g. http://forum.xda-developers.com/showthread.php?t=1525860) and I think we should keep investigating. There should be a way of make a script to kill the process (or propery unmount).
EDITED: After some tests, it seems that if you unplug or go to the notification bar and click unmount, it will trigger the issue. But, try the following:
Go to Settings, Storage, scroll to the end and hit Unmount OTG Storage
It won't trigger the bug. Confirmed by at least 2 devices.
Click to expand...
Click to collapse
Hello Everybody, i have the same BUG here, S3
I am on a custom ROM ( ICS based ) and i was afraid that it would be a bug in the kernel or something
I connected my pen drive three days ago and the battery was like HELLLL
Draining like the japanese bullet train
I am really hoping for a solution other than rebooting the device
For the above workaround, i cannot see "Unmount OTG Storage" under storage settings
Do u mean to select this option when the drive is connected, rather than selecting the option in the notification bar ???
Yes...
Because if you un-mount through the notification bar, that's what triggers the bug...
shouk_1987 said:
For the above workaround, i cannot see "Unmount OTG Storage" under storage settings
Do u mean to select this option when the drive is connected, rather than selecting the option in the notification bar ???
Click to expand...
Click to collapse
Can't use OTG
I have the latest Official jelly bean, and nothing happens when I plug the pen drive, do I have to enable it somewhere?
The bug is present in latest 4.1.2 (ELK4) leak also.....
I agree with KotDroid. Issue on ELK4 4.1.2 Jellybean.
I try building a script to kill UsbStorageUnmountter when media are disconnected.
p
lelinuxien52 said:
I agree with KotDroid. Issue on ELK4 4.1.2 Jellybean.
I try building a script to kill UsbStorageUnmountter when media are disconnected.
Click to expand...
Click to collapse
Waiting for your script
kerbiii said:
Waiting for your script
Click to expand...
Click to collapse
Work in progress, BUT I have a big failure. It unmounts also external SdCard :'(.
Related
I have tried the Airplane Mode trick, and it did not work...anyone find a solution? This build runs great other than this battery life issue...
Did you try this method: http://forum.xda-developers.com/showthread.php?t=651848
Thanks for the suggestion. I tried that previously, and while it reduced the "time without signal", the awake time is remains at 100%.
Does anyone know if this 100% awake is an issue with Fresh Rom 2.0c?
ronnienyc said:
Does anyone know if this 100% awake is an issue with Fresh Rom 2.0c?
Click to expand...
Click to collapse
That issue isn't guaranteed to happen, or *not* happen, on any particular 2.1 rom, but seems to happen to people on occasion on different roms, and perhaps for different reasons. I did not have that issue on Fresh 2.0c, for what it's worth.
No matter which rom you want to end up on, it might be a good idea to restore back to something that previously worked, confirm that it still does, then re-wipe (Data/Dalvik/Ext) and re-flash the rom of your choice. If all goes well you won't have the issue, and will have only a slight lingering frustration over what unknown factors were causing it.
...and good luck!
This sounds fine, except for having to set up all my apps., etc, etc all over again :-(
Is there a way to avoid that?
ronnienyc said:
This sounds fine, except for having to set up all my apps., etc, etc all over again :-(
Is there a way to avoid that?
Click to expand...
Click to collapse
Depends on what you mean by 'set up' -- saved .apks for easy re-installation, yes. Saved .apks with all relevant configuration intact -- well, that's what nandroid is for, so in that case no, not really.
Best case, if you happen to be using apps2sd, when you do a nandroid backup (+ext) it puts all your .apk in a neat and tidy .tar file for you labeled ext. You could certainly unzip that and push them back after you get the basics set up again.
If you are not using apps2sd, you can still backup most of your .apk files using AppMonster or Astro, both free from the market. They might not be able to backup some paid apps, or certain protected free ones, but it will get most of them. If you are comfortable reading up on, and learning adb a bit, you can 'adb pull [source] [destination]' to get the files that the apps won't copy on to your PC.
Regardless, don't rush to dump everything back before you check to see that your awake time drops when the phone is off for a while (and not plugged in to pc, for good measure).
I am assuming hat wiping and using a nandroid backup will not fix this issue...correct?
ronnienyc said:
I am assuming hat wiping and using a nandroid backup will not fix this issue...correct?
Click to expand...
Click to collapse
Oh it might, but if the rom you restore isn't the rom you want to end up on you will clearly still have a few more steps to take. Since the issue isn't really that well understood the only way to find out for sure is to try it.
If I had to wager, I would say that yes, if you restore a backup of a rom that didn't give you 100% awake time trouble before, it should be fine once again when restored over a setup that was giving you trouble.
The real point is that if you then went *back* to the one that was giving you trouble, there is just as good a chance that it would work fine this time as there is that you would have the same issue again. Only one way to find out...
Thanks for all of your help askwhy. Too bad no one understands this issue - it seems that it *should* be a very simple fix ;-)
Wow, I just flashed Fresh 2.0b and the awake time issue is resolved. Also, the Cell Standby issue is also solved - it's at 29%, rather than the 69% I had with the Damaged One...now tlet's see what is broken in the Fresh version...
I had 100% awake on DamageControl v2.0r2. Just flashed Damaged-Regaw 2.0b1.3 and the issue is solved as well as all the other issues I was having.
Troy, what other issues did it solve, and where did you get it?
I am now thinking of staying with Fresh, as it seems to be more responsive...thanks.
i am on darkledgend 4.2.2 and to fix the problem on that rom here are the steps, give it a try.
from dialer
*#*#4636#*#* (give it a second and you will go into a menu)
press menu hard key
press select radio band (you will get a force close, acknowledge and ignore it)
select "cdma auto prl" from the drop down menu
press home hard key
you have to do this every time you reboot
ronnienyc said:
Troy, what other issues did it solve, and where did you get it?
I am not thinking of staying with Fresh, as it seems to be more responsive...thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=654300 there is a list of fixes here as well
Thanks Smitty. I tried that some time ago, and while it seems to fix an issue, but it does nothing to help the 100% awake issue. Thanks though.
for what its worth i have never had the issue using the full rom -
{
"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"
}
I updated my first post with some info, try run spare parts, go to battery history & check partial wake usage
Are the people with 100% awake time already patched with this file?
http://www.4shared.com/file/252386050/cb94052d/Facebook_DamagedTrev.html
(From the first page of http://forum.xda-developers.com/showthread.php?t=653622 )
I noticed I had the 100% awake time before trying to fix the Facebook syncing problems; patched with this file and now I'm down to about 50% awake time (sounds accurate as I haven't had the screen off for a lot of the time).
Its only been a bit over an hour but though I would mention it.
good point about fb urinsane last thing i did before i started session in above screenshots was test out that update.
TrevE said:
good point about fb urinsane last thing i did before i started session in above screenshots was test out that update.
Click to expand...
Click to collapse
Oh wow, didnt realize there was a patch. when i posted above about Regnaw's rom, I hadnt set up facebook yet.....so it wasnt syncing. Once I did, it was back to 100% up time so I tried the facebook fix zip and wouldnt you know it....up time is once again going back down.
Hi,
My Nexus 4 is running completely stock 4.2.2, it's not even unlocked let alone rooted (first phone I've felt happy enough without root) and was running fine until yesterday when it ran out of storage space and gave me a warning. So i uninstalled a couple of games, hoping to free up a couple of gigs.
Now though, i can't get to the settings menu or any associated screen. I can toggle the quick settings from the pull down menu, but if try to enter the main settings menu it briefly flashes up and then closes. It's the same if i try to access settings through the launcher, and if i try to get to any settings menu via other means (ie. long press an icon in Nova and select 'app info' or 'uninstall') the associated menu again just flashes up and then vanishes within a split second as if I've pressed back straight away.
Nothing else seems out of the ordinary - apps update, i can get to the play store, apps run fine, just the settings menu.
Any ideas? I can't find anything similar searching here or elsewhere. I've obviously rebooted the phone but without access to the settings i have no idea what else i can change. I'd factory reset but I've not backed up a couple of apps and usb debugging is off so i can't use Carbon (for some reason it's always had problems keeping the initial enabling and needs plugging in regularly),and i can't use Titanium without root so i wanted to see if anyone had any bright ideas first
Perhaps there's a way to just reset the settings menu? I've no idea what it's process is, but some action similar to "clear app data" should reset it :/ Just brainstorming here.
if nothing helps do a factory reset. your apps will come back automatically through the play store when you log in.you'll loose your highscores but most apps are cloud driven anyway,
molesarecoming said:
if nothing helps do a factory reset. your apps will come back automatically through the play store when you log in.you'll loose your highscores but most apps are cloud driven anyway,
Click to expand...
Click to collapse
Sorry for the OT but is that a genuine quote in your sig?!
Anyway @OP I think factory resetting is probably your only viable solution here, it's a very odd issue and there's not much you can do to solve it without a settings menu.
You need to clear the data for settings. Install titanium backup and see if you can. You'll need to root it first though. Crap..I forgot forgot you said you arnt rooted.
{
"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"
}
Factory reset it.
Sent from my Nexus 4 using Tapatalk 2
Cheers for the suggestions, was hoping there would be a fix but I guess a factory reset in the morning it is.
Frustrating as this sort of thing really shouldn't be happening out of the blue from a stock phone - it's a fairly huge bug!
Ironic that I resisted rooting to ensure I kept the reliable and simple experience of the nexus, only for it to be what stopped me fixing it when it broke :-\
Won't make that mistake again!
This probably won't work but try opening your quick toggles then long pressing on wifi or bluetooth, that's supposed to take you to those individual settings. Then if you hit the icon in the top left you may be able to get back to the main settings.
Nigeldg said:
This probably won't work but try opening your quick toggles then long pressing on wifi or bluetooth, that's supposed to take you to those individual settings. Then if you hit the icon in the top left you may be able to get back to the main settings.
Click to expand...
Click to collapse
Nope, sadly does the same thing - the settings menu briefly flashes open before closing.
Sent from my HTC One using Tapatalk 2
Hey OP, did you figure it out yet? I just noticed that trebuchet launcher allows you to go into settings via a shortcut in the app launcher. Probably won't work, but hey. Try another launcher?
Yes cheers a factory reset wasn't needed in the end - I worked out the problem.
I've been using my sim with my n4 as well as my new HTC one and hot swapping between the two for a week or so. I also have avast installed on the n4 which has an option 'disable settings when no sim inserted' which I'd forgotten about.
I only thought of it because when I initially took the sim out I got an email saying 'warning unauthorised sim inserted, id: {null}' or similar.
It didn't work with my sim installed either but I logged into avast, turned that setting off and everything was back to normal. Turned the setting back on now (once the sim was in) as it's obviously going to be an absolute pain for thieves too!
I guess it's a problem with hot swapping the sim while avast was running, the switch didn't get triggered even when I reinserted it? Either way now it just means I turn the n4 off before removing the sim now!
Sent from my HTC One using Tapatalk 2
Haha, at least you now experienced first hand how secure your settings menu is. :laugh:
Exactly what I was thinking! Nice it gave no clue why it was happening and if I didn't know the password for avast it would have made life very difficult as it also disabled usb debugging, so anyone who wanted to wipe the phone would have needed some serious android knowledge.
Sent from my HTC One using Tapatalk 2
Hello All,Ive purchased Gionee Elife E7 and there is a problem with WhatsApp that there is no push message notification...When I open WhatsApp i can see the messages notification of what all messages ive received..any one facing the same problem and have a solution to it??
GTARaja said:
Hello All,Ive purchased Gionee Elife E7 and there is a problem with WhatsApp that there is no push message notification...When I open WhatsApp i can see the messages notification of what all messages ive received..any one facing the same problem and have a solution to it??
Click to expand...
Click to collapse
Yes Me too facing the same issue. Didn't find a solution either.
Here's a fix:
Grato said:
Yes Me too facing the same issue. Didn't find a solution either.
Click to expand...
Click to collapse
This is a known issue with the default launcher of Elife E7. Whenever you quit an app (by sliding it away on the homescreen), the launcher force quits the app. So, if you close WhatsApp like this, you automatically turn off the notifications.
There are two ways to solve the problem:
1) Don't ever quit WhatsApp by sliding to clear it in the Navi launcher.
2) Use another launcher, like Nova Prime or so.
1995ad said:
This is a known issue with the default launcher of Elife E7. Whenever you quit an app (by sliding it away on the homescreen), the launcher force quits the app. So, if you close WhatsApp like this, you automatically turn off the notifications.
There are two ways to solve the problem:
1) Don't ever quit WhatsApp by sliding to clear it in the Navi launcher.
2) Use another launcher, like Nova Prime or so.
Click to expand...
Click to collapse
It still doesn't do that trick. Unless you keep opening it frequently, It will be killed in the background after a while. Really annoying.
One thing I tried to no avail is to install Xposed and install the 'App Settings' module and make Whatsapp a RESIDENT app. Still it will get killed.
NHS2008 said:
It still doesn't do that trick. Unless you keep opening it frequently, It will be killed in the background after a while. Really annoying.
One thing I tried to no avail is to install Xposed and install the 'App Settings' module and make Whatsapp a RESIDENT app. Still it will get killed.
Click to expand...
Click to collapse
Really Amigo is a fail by GiONEE...either they should improve the OS or discard it..i think i bought a wrong handset..
Whats app on e7
i m also facing the same problem with my whats app on my gionee eife e7.
I'm not sure if this option could help, but try disabling that "Auto-clean" option under Power saving and it should stop closing processes like Whatsapp and others -
{
"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"
}
1manshow said:
I'm not sure if this option could help, but try disabling that "Auto-clean" option under Power saving and it should stop closing processes like Whatsapp and others -
Click to expand...
Click to collapse
I also thought that might be it but It triggers if we enter power saving mode right? Such a confusing app. I never enable power-saving,
but hey! lets try it.
Maybe you guys can go to Developer Settings and increase the background process limit. Worth a try I guess.
I was quite interested in this phone but I've no clue about Gionee's service nor do I know if they will ever post OTA updates for the phone.
NHS2008 said:
I also thought that might be it but It triggers if we enter power saving mode right? Such a confusing app. I never enable power-saving,
but hey! lets try it.
Click to expand...
Click to collapse
:good: Sure, I just got my phone delivered, but haven't opened the box yet. Let me know if that option works and WhatsApp works fine after disabling that.
Evander_F said:
Maybe you guys can go to Developer Settings and increase the background process limit. Worth a try I guess.
I was quite interested in this phone but I've no clue about Gionee's service nor do I know if they will ever post OTA updates for the phone.
Click to expand...
Click to collapse
I've heard (both internet and local word of mouth) that their service is good and improving day by day. Also you can check their twitter/FB account and I see many past devices getting updates over the air, so I don't think they would miss out any possible updates on their flagship phone :fingers-crossed:
1manshow said:
I've heard (both internet and local word of mouth) that their service is good and improving day by day. Also you can check their twitter/FB account and I see many past devices getting updates over the air, so I don't think they would miss out any possible updates on their flagship phone :fingers-crossed:
Click to expand...
Click to collapse
Thats good to hear! I might just consider it, I'm just waiting to see some active development on this phone, it's got a beast of the cpu
A custom kernel and AOSP rom would make it fly
^^ You can check this thread to keep an eye on active development talks for this device -
http://forum.xda-developers.com/showthread.php?t=2649623
If you are a dev or know someone who can help, please ask him to provide his inputs on that thread. burakgon has kernel sources already and asking for more information what we should get from Gionee.
work around for it to work.
if you install go launcher.. whatsapp returns to its normal mode... tried and tested and using..
Solution
GTARaja said:
Hello All,Ive purchased Gionee Elife E7 and there is a problem with WhatsApp that there is no push message notification...When I open WhatsApp i can see the messages notification of what all messages ive received..any one facing the same problem and have a solution to it??
Click to expand...
Click to collapse
If you are still facing the problem, the solution is using GO Launcher or any other launcher instead of default. Once u make Go Launcher default it solved the isse and whatsapp is normal back to routine notifications. Let me know if works for u
Guys there is option of 'sync off' in the power manager app settings. Uncheck it and use any launcher push notifications will be there.
Sent from my E7 using xda app-developers app
My gionee f103 Whenever I shake the phone all running apps close automatically what is the solution for it??
Dear all,
I have received my Axon 7 (A2017G) yesterday and I'm considering to return it to the vendor.
While the hardware is close to perfection (I really love the device), some software bugs are driving me crazy.
For your information, before registering my Google account or installing any app, I have updated to B10, Nougat and then 7.1.1 (build A2017GV1.2.0B01).
I do not want to root my device because I may loose access to my corporate data (and also may loose my ability to return the device and get my money back).
The biggest issues the inability to use my Samsung smartwatch Gear S2. Soon after the phone is locked (screen off), the Gear S plugin is killed by the OS and I loose the connectivity between the phone and the Watch. I have to restart the gear application manually. I have played a bit with the applications power management options but without success (I have unticked all policies for the Samsung Gear application and even restarted the phone but the same behavior is happening). I don't see how it could be possible to solve this issue without rooting the phone...
The other issue is the famous playstore issue. I can't understand how such a visible and blocking issue has not been adressed by ZTE yet (after a week). Even if a workaround exist, it's still embarassing. Furthermore it raises concerns about ZTE software quality related processes...
Besides that, I may have missed some text messages yesterday (to be confirmed) and I have also encountered other suspicious behaviors.
Anyway, I'm hesitating because I really love the device itself but I need at least:
1) To fix the issue with my Gear S2
2) To obtain some assurance that ZTE will quickly fix the playstore issues (this is honestly difficult to understand)
Thank you in advance for your feedback and suggestions.
Best regards,
Did you try going to the power manager and disabling any battery-saving feature on that plugin app as shown here?
{
"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"
}
Was beat to it, but I suggest disabling all power management options for the Gear app. I had issues work Pandora closing when I locked the screen.
As for the Play store issue: I don't understand why it's embarrassing. Google changed something in the apk that of choosing an issue. It is an issue that had been posted on the ZTE Axon forum (https://community.zteusa.com/thread/15221?start=225&tstart=0) so I'm pretty sure they know about it and are working on it.
As I said, I have already disabled all power management options for the gear app and it's not solving the issue unfortunately
Maybe this is because the gear app is in fact an app (Gear app) and a "service" (the gear plugin), but the gear plugin is not displayed in the power management options...
fraga said:
As I said, I have already disabled all power management options for the gear app and it's not solving the issue unfortunately
Maybe this is because the gear app is in fact an app (Gear app) and a "service" (the gear plugin), but the gear plugin is not displayed in the power management options...
Click to expand...
Click to collapse
Have you disabled screen-lock cleaning?
gumbyx84 said:
Have you disabled screen-lock cleaning?
Click to expand...
Click to collapse
Yes, it was disabled for the Gear application. Now, I have disabled screen lock cleaning for all. Let's see what happen today.
I will wait until the week-end to take a decision...
fraga said:
Yes, it was disabled for the Gear application. Now, I have disabled screen lock cleaning for all. Let's see what happen today.
I will wait until the week-end to take a decision...
Click to expand...
Click to collapse
Well, it doesn't fix either, application got killed...
That's really incredible
fraga said:
Yes, it was disabled for the Gear application. Now, I have disabled screen lock cleaning for all. Let's see what happen today.
I will wait until the week-end to take a decision...
Click to expand...
Click to collapse
If you're ok with it, I suggest deicing to the performance power plan. My only other suggestion is to perform a factor reset. Since you plan to returning it if you can't get it working your going to lose everything on they phone anyway.
Yep, that's what I will do this week-end.
Factory reset and try to see if major issues are still present. If this is the case, I'll return it.
Thanks
fraga said:
Yep, that's what I will do this week-end.
Factory reset and try to see if major issues are still present. If this is the case, I'll return it.
Thanks
Click to expand...
Click to collapse
ZTE already announced a B2 that fixes the Play store, and Whatsapp. hang on tight. You can fix the playstore by deleting the updates and cancelling the auto update that appears, until it tries again at least.
For the Gear issue I guess you should find a way to check why the app closes. maybe there's a monitor app somewhere?
You can also try downgrading to Marshmallow B11 or B10 for some time. I think you can with the stock MiFavor installer... I guess it might even fix your Gear.
Hi fraga i might be able to provide u some information regarding this issue.
may i have ur email address.
Hi nharees, you can contact me directly in this thread or via private message in the forum. I don't understand why you would need my private email address.
So most of the issues have been fixed with the lastest version except the gear S2 which is still not working as expected (gear S plugin regularly killed by ZTE application manager...)
Just went non stock and haven't looked back. I was running a buggy b29 (camera bug) for months, and as soon as the sound issue was fixed I jumped shipped. Battery life is great, no crappy mifavour skin and everything works as expected from my testing... Just a thought
This phone is driving me nuts.... I've been using this device since 2 months now and it is extremely annoying. You just can't play any bloody games that require you to react in a very short time... The taps register very late. For example, It's impossible to use SwiftKey or swipe keyboard because if you swipe too fast it will miss a few letters and predict the wrong word.
Any custom ROMs or kernels that may fix this? Sd835 is useless if I just have to play tic tac toe..
Android P fixes it entirely, that was a huge issue I had with the phone as well. I don't notice any lag at all now.
crixley said:
Android P fixes it entirely, that was a huge issue I had with the phone as well. I don't notice any lag at all now.
Click to expand...
Click to collapse
Hey sir thanks again for helping me with my rebooting issues... Essential checked the logs and I'm sending in under warranty. It did get better with your tips though . on this note, why does P still not have an option to reboot into the other sides partition? It would make restoring much simpler because you could do it without a computer. Is there a wat to reboot into the other partition without one?
KingBeefy said:
Hey sir thanks again for helping me with my rebooting issues... Essential checked the logs and I'm sending in under warranty. It did get better with your tips though . on this note, why does P still not have an option to reboot into the other sides partition? It would make restoring much simpler because you could do it without a computer. Is there a wat to reboot into the other partition without one?
Click to expand...
Click to collapse
Anytime!
Glad I could help to some degree.
I'm not sure any phone with an A/B partition has that option, unless I'm mistaken. That is really there for system use only, not for those looking to tinker.
I have the ph-1 since one week and I have the exact same problem. Swiftkey or Gboard with swipe gesture typing is absolutly impossible to use with this phone! It drives me crazy since 90% what I do with a phone is writing text messages in Whatsapp. I am using Swiftkey since my Galaxy S2 and I had a couple of low class phones since then. None had this problem. I cannot confirm Android P fixes it. Any other ideas/fixes/custom roms that address this issue?
Same problem here. This phone drives me crazy -.- i can't use swiftkey and swift.
Here a touch screen test. Left screenshot is the essential phone, right one is my xiaomi redmi note 4.
And what happens if i try to write "this is a test" three times.
{
"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"
}
I need a fix for this, isn't there any custom rom or kernel or whatever that fix this?
I'm using the official android p version.
This is a test
This is a test
This is a test
All with gboard swipe, all first time
This is a test this is a test this is a test this is a test
And again.
Maybe you have a faulty digitiser?
kboya said:
This is a test
This is a test
This is a test
All with gboard swipe, all first time
This is a test this is a test this is a test this is a test
And again.
Maybe you have a faulty digitiser?
Click to expand...
Click to collapse
could you download the "touch screen test" app and post a screenshot, how it looks like on your phone?
Would be great, thanks!
As requested
I contacted essential supported they told me following:
There are a couple of settings available to fine tune how the screen responds to touches (and scrolling) that you can customize for your own preferences and might have an impact on what you have noticed when using swipe gestures on the keyboard. These are in Developer Options in Settings. If you haven't enabled this menu, these instructions will make it available:
In the Settings menu, scroll down and tap on the System menu.
In the System menu, tap About phone.
Scroll down until you see "Build number" at the bottom of the menu.
Tap the "Build number" 8 times in a row.
After 8 consecutive taps, a message will pop up alerting you that Developer Options has been enabled.
Developer Options can now be found in Settings > System
Once we've enabled Developer options, I would suggest disabling "Grip Rejection" and testing to confirm if that helps with the touch responsiveness issues that you are noticing. Also in this menu, you will find the option for "Touch Sensitivity", if you are noticing issues when scrolling, you can experiment with other values to see what works best for you. The higher the number, the screen will be more sensitive to touch but you could notice more "jitter" when scrolling.
Also, if you are using a screen protector (or left the protective plastic on the device), it can impact how the device responds to touch, so I would recommend removing it and re-testing if none of these settings result in an improvement.
Because Android 9 Pie has just been released, it is also possible that specific apps haven't been optimized for this OS, so I would also recommend reaching out to the developer to provide the feedback that you have noticed in case some improvements can be made in a future update.
Click to expand...
Click to collapse
At first I thought it would be better. But when using Swiftkey longer I still miss words due inaccuracy. Does it help you guys in any way?
Thanks kboya!
@br3ak
i already tried this too but it didnt help in any way.