Related
WARNING This is a long post describing various events of my G1 and things I was going through, so Im basically doing a dump of my thoughts and possible reasonings to put everything I can report, case it is a ROM, Hardware, or Software flaw somewhere or just user error. But since this forum is about feedback for devs or rom providers =)
Ok I dont know where to begin with this post. Last night my G1 needed a wipe. Why? Cause all it did was reboot over and over not getting past 1st home screen, then finally android screen. What happened before this? All I have of the things going on during that time frame was this:
(Now before the below stuff, earlier that day, Quest Live glitched on me, and when I was at the home screen, I tried to scroll left and right and it got stuck half way, which WORRIED me since I thought the touch screen was messed up. To my luck after a reboot and iso alcohol rub down on screen, it was fixed. Tho only after I unplugged it from the car charger (Which seems to really make the G1 % battery jump in record speed.. glicth?) Or Power Manager issues? Tho this wasnt the updated one, so the new one may have fixed the issues the dev said power manager was causing.
I plugged in the usb to a ubuntu running PC. To charge it, thus triggering Power Manager. Same time, I was trying to install SnapPhoto, which it downloaded, but didnt install, I was also noticing abit of lag, So I ran task manager to turn off some apps running in background, Camera, Gallery, Gaming Buzz Widget, Weather app Widget, Calender. (Then as I rem.. I tried to update AdFree when the new version came out.. it didnt install but same time when I tried to load it, it just came up black.. sign of a bigger issue maybe?)
After that of course couple of them came back. Then I tried to change the volume using the side button, It didnt respond, The on screen worked fine tho. So I decided ok, time to reboot fresh on the phone. Rebooted, Then it loaded to home screen before radio signal, then rebooted. After getting tired of not booting, (I had unplugged it from the USB btw which at 1st kept the charging light on before I rebooted it. ) I pulled the battery out. Which MAYBE I pulled it out at the wrong time during the android screen. Cause after that and I put it back in, all it did was goto the G1, then Android cycling screen, but no longer went to the home screen to try to load. Then was too late for this trick, but the Safe mode attempt. Which MAY have worked when it made it to the home screen, but once it was on Android only, safe mode didnt load at all. Just endless stuck on Android. So I had to wipe 1st then I reapplied the JF 1.51 update.zip to fix it and get the G1 to turn on again and boot.
Advice tip: If you can still boot to the home screen "somewhat" next time it cycles, try holding "Menu" in to have the G1 bypass any apps and load into safe mode, which may allow you to uninstall or fix whatever the issue is.
To my surprise. The Apps when the G1 started installing again went to the SD card. (I do not use apps2sd, Only Lucids orig) Now thats when I noticed more hell.. I went to the market to look at "My Downloads" and WHAM, the 10 apps it auto downloaded (Which I guess was a sync) are the only ones in the My Download section.. nothing from my past downloads.. Which is 110 more apps.
Advice tip: Use Atrackdog to "Export" your database to a text file and keep that on your PC. This way if ANYTHING happens, you least know which apps to look for.
Advice Tip: Upon reflection I probably should have made a nandroid backup after 1.51 was smooth. So if you havent, Id suggest looking at it) I know I will once Im set back up.
So now I am left with a interesting ponder. I msged Lucid to see if his scripts would allow me to use my 2GB which had my 1.51 data on it and somehow relink it to the G1 and have everything restored, then recopy to the 4GB which is my current one. But chances are I need to 1 by 1 install again. (Anyone know how you get apps back that arent on the market anymore? Extract from the SD card maybe?)
Anyways now I am wondering, If you install too much to the G1, will it in the end cause a problem? Im not a dev so I dont know how that all works with the ROM builds. But that wouldnt be good news if you have 129 apps, things could start messing up. (Tho not sure if that was a cause for any of the above)
Another thing I learned, if you have a GOOD screen protector on the G1 (Not the one it came with) and it smears up, or gets smudgy it seems it may interfere with the response of the touch screen. Ive notice if the screen thinks its being pressed in, a app could hang, lock up or choke the G1 to where it fixes itself by doing a reboot. Now that sounds odd that the G1 is sensitive to smudges or oil from your hands (If you had a humid hot day). Anyways fixed that with iso rubbing alcohol and a soft wipe cloth. Then rebooted.
Now my next task is to 1: Find out if my Cache since the wipe is running on the SD still, or if its on Internal. The app "Move Cache" I hear could do that, but I heard it messes up market, maps etc.. so not what I wanna do atm. Then I just gotta see if I can restore apps from SD using a app or terminal, which I am studying now, but just wanna end this post for now.
Will post more as I get around to it. Maybe I can restore the market cache manually.
do you still experiencing the touch screen error problem after all the steps you have taken? because i have the same problem. sometimes when i use touch screen to switch screens, the screen get stuck in the middle and shaking. i also cannot select anything correctly by touching. and i've read from various forums that this has something to do with the charger / charging process. i think that my problem occured because i charged using usb cable to my computer. because i never done that before (i usually charge my phone using a wall charger) and when i did, the problem happened.
How I fixed it? I turned off the G1, used rubbing alcohol with a tissue to gently wipe the screen off and clean it. Then turned back on and it was fine.
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Are you using apps2sd?
No, I'm not using the apps2sd feature.
The lockscreen text showed "No service" and the notification bar icon showed the same. The "phone" application was the only one that would attempt to restart after being forced closed. After a second fc though, it would apparently give up.
Oh, and just remembered one other oddity.. Once booted and all force close messages removed, attempting to turn on the mobile network resulted in a hard reboot. I really didn't expect anything since there was no service link, but I was just clicking various shortcuts to see what did or didn't work.
Good part is that a Nandroid restore saved the day, so it's more of a curiosity at this point to what the root cause might have been.
I wouldn't have thought that a battery drain could have corrupted the apps or prevented the root filesystem from mounting.
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
mkhopper said:
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Click to expand...
Click to collapse
oddly enough I've had a similar experience. it was 2 days before christmas and i was doing all my last minute shopping. heavy use of the phone caused the battery to die, so i just threw it on my car charger. it booted, but REFUSED to get any data at all (i didn't run into any fc's, however). I rebooted it 3 times and each time the issue persisted.
I was running the AOSP 2.0 build at the time, so i flashed my backup of 2.1 and everything was fine from there...
patches11 said:
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
Click to expand...
Click to collapse
Hmm, good possibility there. Just did a count and I do have 85 apps installed.
(whoof, I had no idea the number had gotten that high. just too many useful apps for this phone.
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
ks-man said:
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
Click to expand...
Click to collapse
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
jbkmin said:
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
Click to expand...
Click to collapse
Did your issues first start after you upgraded to lollipop?
ks-man said:
Did your issues first start after you upgraded to lollipop?
Click to expand...
Click to collapse
Definitely after the upgrade.
While on KitKat, it never happened (1 month ownership). But after upgrading to lollipop, it has happened 4 times (6 nights since lollipop).
Have you figured anything out with your situation? Woke up this morning to my backup alarm and the Yellow Sprint screen on my phone.
I guess I'll have to try another factory reset and if it still happens try and get a replacement. It just doesn't seem widespread enough of an issue to be a software bug with 5.0.1.
Very frustrated. I did another factory reset but the issue still plagues my device. It still only occurs once or twice a week but when I hear my old clock radio alarm in the morning I know when I look over I'll see the yellow frozen Sprint Spark screen. I am completely out of ideas and guess I will need to have it replaced under warranty. I'm hoping Sprint won't give me a hard time as this will be very hard to demonstrate.
It definitely appears to be a software issue as it never happened before I upgraded to Lollipop but there must be more to it or others would be complaining.
If anybody has ideas please let me know. Thanks.
Response to Note 4 Freeezing while charging
I have found that after turning the quick charge feature off the problem is not happening. Hopefully this is fixed in 5.1
I'm having the same issue even after turning quick charge off..def a lollipop bug, never experienced this on kk.
I know its not the BEST option, but after taking the update to lollipop, sometimes left over kitkat files can make the system poop out. Sometimes a factory reset will take care of the leftovers. But of course, then you have to set your phone up again
If you've tried this or plan to to, let us know the results.
(When i first took the update, my heartrate monitor sensor was always on, so i did a factory reset and it fixed my problem).
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
same problem here
Ive tried turning off fast charging option on the powersaving mode
And also tried the option on developer mode, the "keep device awake while charging"
And even flashing dofferent firmwares from sammobile through ODIN and installed custom roms. These options doesnt resolve the issues on freezing while charging..
I think turnong off your device while charging is the only option..
Im using note4 N910C..
Clasimodo said:
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
Click to expand...
Click to collapse
Thanks a lot, Mate. I'm trying your workaround now. Will report later if it works on my phone. BTW, so, are you sure it is a just a system issue? Definitely, isn't a hardware problem? Did you fix it, after your post -a month ago-, installing, for example, lollipop 5.1.1 or Cyanogenmod 12.1? I'm on 5.0.1, SimpleRom V4. Of course, mi device, N910C, is rooted.
Thanks again.
With lollipop 5.1.1 the problem is solved for me, even without this workaround.
Sent from my SM-N910F using XDA Forums PRO
I'm having similar issues as you guys. I found out that my phone will only perform normally when I charge it with my laptop USB port which I think is around 0.5amps. Anything above that, even a 1amp charger would cause the phone to freeze, reboot and turn off and not turn back on. The phone has been in repair 4 times and the problem is still there. Now every night I'm forced to charge my phone with my laptop which takes an age instead of the fast charger that came out of the box.
Currently my phone is still freezing and rebooting when I'm out and about and the only way I can get it to perform normally is when I plug it into my laptop. This normal functioning would only last whilst the phone is plugged in.
My experience with my S7 has been great so far. However, a couple days ago it did something odd. Whenever I plugged it into my PC with any cable it behaved as if the recent apps button had been pressed randomly. Sometimes fast, others slow and inconsistently. I went into recovery and wiped the cache and then went in and deleted a few more recently installed apps. I also used ES Explorers cleaning function and everything has been fine since. Then today I rebooted it and the first screen showed your typical rooted device screen with "Custom" and the unlocked symbol before going on to load everything else. I've tried rebooting it a few times to get photographic evidence of what had shown up but it hasn't done it since.
What is going on with this phone? Is it compromised? Perhaps I just need to do a full wipe and reset?
I have similar sporadic issue on my 935F, even when my finger far away from "recent apps" button, no a single clue why. Now trying edge option turned off, perhaps this what ghosts it.
wjenya said:
I have similar sporadic issue on my 935F, even when my finger far away from "recent apps" button, no a single clue why. Now trying edge option turned off, perhaps this what ghosts it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/s7-edge/help/false-recent-app-presses-causing-multi-t3333785