Related
Hey guys,
I've been reading the forums for the past few weeks and have been enjoying the discussions here, yet not having too much to add (constructively). Apologies if there is a thread on this already. I have done a couple of quick searches but nothing came up that seemed to fit the bill.
I got in this evening and took my S2 out of my pocket to find something wrong with it. I'll explain below. First of all software details:
Baseband Version:
I9100XXKI4 (up to date as far as Kies is concerned - stock ROM)
Apologies in advance if I'm missing any important information (I'm trying to sift through and try pick what I think are the relevant points).
Issue:
I felt my phone vibrate twice and took it out of my pocket (expecting a text). Instead I found the "Desk Clock" part of the stock "Clock" app flashing on and off the screen. When I tried to close it I came to the lock screen, unlocked it and then the desk clock opened again. It reloaded every time I attempted to close it. I tried to end it using the task manager but it didn't show up on the active applications list. I restarted the phone.
When I restarted it didn't seem to load properly with app icons all over the screen and the home screen numbers in the middle of the screen. I have a screenshot which I'll try to upload later. I restarted again.
This solved the arrangement issue but didn't stop the desk clock popping up. I also became aware of another problem. The battery was showing 12% (down from ~35% it was showing before - when checking battery usage). I plugged it into my laptop via the USB lead I have (which I had used earlier in the day to charge it). It didn't recognise immediately that it was charging. I swapped to AC, it started charging.
It then started showing "driving mode activated" and asked me whether I wanted to complete the task with UlysseSpeedometer or Voice Talk. I didn't press anything. When I pressed back it then asked me again a few seconds later. I restarted the phone again.
This time it showed 37% battery! I switched to the USB charger to try to back the phone up. It had trouble connecting but did eventually. I left it perfectly still as it tried to back up but failed twice partway through doing so.
Recent changes:
Only real changes are installing Super Compass today, which when (re)reading reviews didn't seem suspicious. I have uninstalled just in case.
Additional information:
I updated to 2.3.5 through Kies about a month ago (the first time it was available for me after checking for updates every few weeks - I have friends with the same phone on 2.3.4 and 2.3.3). Since then the countdown timer on the clock app sometimes shows the preprogrammed 1 minute countdown even when I have a timer running. The timer alarm still goes off at about the right time (haven't tested it properly) though.
In addition to this I have customised the apps that stay at the bottom (can't think of the terminology at this time of night) by swapping the Phone for GMail. Every time I restart the phone the GMail app is removed but the Phone app doesn't replace it. On a similar note I keep getting asked to choose my default PDF reader after ticking the box to select it multiple times.
My thoughts:
It appears to be a software issue to me. It's late now but tomorrow I plan to attempt to back up again (perhaps just by copying all the files on the phone using Windows Explorer if need be) and attempting to reinstall the firmware through Kies. If that doesn't work I'll do a factory reboot. After that I'll contact my carrier (O2 UK) to get some support.
Question:
I was wondering whether anyone has any insight, has experienced similar problems, or has any other advice regarding this?
Thanks in advance for any help you can offer
Regards
T
It sounds like it might actually be a hardware fault - basically what's happening is that something on the phone (whether hardware or software related) is triggering it to think it's being connected to a dock. The desk clock is what pops up as soon as you put the phone in a Samsung desktop dock and car mode similarly pops up when you use the vehicle dock, so there may be something funny going on with your phone's connecter that leads it to think these events are happening. (The weirdly arranged home screens tie in to this, as they can be a slightly buggy result of unplugging the phone from the one of the docks while in landscape mode - the launcher tries to load the home screens in landscape and just makes a mess.)
As a bit of a bodge-job fix you can install an app from the market called 'NoDock' if you're rooted, as this stops the phone ever being triggered in to dock mode, but to be honest id say your best bet is to speak to O2 or a Samsung service centre about getting it fixed or replaced!
Anyway, I hope this helps and you manage to get it sorted - I don't know what I'd do without my Galaxy S2!
Sent from my GT-I9100 using xda premium
Hello, quite a late night here as well but I'll try to give you my insight (and then slam myself to the bed )
It seems that the widget in your device went corrupt and perhaps then some more... I recommend backing up your data and then doing a factory reset and eventually re-flashing thru kies (come to think of it, i don't really know if KIES supports full-wipe reflash ). Also, for customizing the quicklaunch bar, use GO Launcher EX (free from the market) - its customizability far surpasses that one of the TouchWiz
If a factory reset doesn't help, you can help yourself by reflashing the original firmware by yourself via ODIN (but be sure to read tutorials and know your firmware first!), you'll find all the needed information here
Hope you get your problem resolved
TUnit said:
Hey guys,
I've been reading the forums for the past few weeks and have been enjoying the discussions here, yet not having too much to add (constructively). Apologies if there is a thread on this already. I have done a couple of quick searches but nothing came up that seemed to fit the bill.
ITS a question = Q&A so well done that man for posting in the right section .
I got in this evening and took my S2 out of my pocket to find something wrong with it. I'll explain below. First of all software details:
Baseband Version:
I9100XXKI4 (up to date as far as Kies is concerned - stock ROM)
Thats the modem not the firmware .
Issue:
When I restarted it didn't seem to load properly with app icons all over the screen and the home screen numbers in the middle of the screen. I have a screenshot which I'll try to upload later. I restarted again.
My thoughts:
It appears to be a software issue to me. It's late now but tomorrow I plan to attempt to back up again (perhaps just by copying all the files on the phone using Windows Explorer if need be) and attempting to reinstall the firmware through Kies. If that doesn't work I'll do a factory reboot. After that I'll contact my carrier (O2 UK) to get some support.
Rule one is backup data and factory reset the phone then test .
Follow that with a Kies upgrade if available .
jje
Click to expand...
Click to collapse
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Hmm, sounds like a faulty phone to me. Try taking it back to get it exchanged for onother one. S3 was built to fly not crawl.
You'll want to go through a process of elimination to figure out when might be causing it.
Something you can try and test with (one at a time)
-turn on airplane mode
-turn off live wallpaper
-shut down all running tasks
-change your lock screen security method
-limit the number of widgets running on all the screens
-reduce the number of active screens
Probably other things you can try to pull out of the equation, but thats a good start
After looking up dial-a-phones returns policy it would seem that I have 28 days to return if the handset is faulty, so this atleast gives me some breathing room to try out any suggestions for fixes. I will begin to eliminate each of the suggested items above however as the lock screen problem is intermittent it make take a day so actually see if it has had an effect, which is annoying at the least.
On another note a numberupted of people are stating high battery life on their devices however mine doesn't seem to be as good and I do have power saving on as well as nfc etc. turned off. This makes me believe my handset could have a fault, but tbf I haven't allowed for a discharge to 5% and the recharging to 100% which I heare allows for optimisation of the battery.
EDIT**** I have changed the lock screen previously and found it had no effect on the problem and I do not have a live wallpaper in use.
Phone Freezing after reboot and auto wifi signal found on.
Same here, been happening the last few days after I installed Avast. Also, turning off and on the auto on wifi seemed to replicate the problem.
The phone will boot to the lock screen and freeze a bit, and sometimes the news ticker freezes, and then after unlocked, I try to turn off wifi signal has been found on the notification dropdown and then tries to auto connect to wifi, the phone will freeze up if I dont turn it off in time.
Once the auto wifi connect is off and reboots, then the phone will keep glitching up until it catches up processing alot of processes it was trying to do for about 1/2 hr. Also, if phone freezes up for too long, like after trying too many time of unlocking the screen while freezing up, the phone gets stuck at the lock screen and the phone almost overheated, in an area right below the battery. I had to pull the battery out to cool it off.
It seems to be a glitch in the auto wifi, especially if alot of resources are being used. Once Avast was on my phone about 1.5GB RAM is being used sometimes and since has really slowed the phone down. Going uninstall alot of apps.
JCrinage said:
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Click to expand...
Click to collapse
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
sassorock said:
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
Click to expand...
Click to collapse
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
S3 black screen after unlocking
Has there anyone experience S3's screen went on black? I have pebble blue S3 - GT-I9300. Cases when unlocking, answering an incoming call or attempting to turn off an
alarm? Mine happens when after unlocking the screen then it goes black and screen becomes unresponsive. It happens intermittently and even after 3 times of
reprogramming. I am now going to have it replaced. I am having a lot of troubles -- it exits on its own when im reading or composing an SMS; files were deleted after
restarting the unit, and an app opens up even not touching the scree. This is expensive and I am paying a lot just to experience this king of inconvenience.
DavidNieuwpoort said:
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
Click to expand...
Click to collapse
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Flodas said:
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Click to expand...
Click to collapse
Just the latest stock ROM but rooted. I've found out that turning off the wifi power safe mode fixes the problem for me. To do this:
- In the dailer enter *#0011#
- Press the menu key
- Select wifi
- Press the on/off button.
The wifi power safe mode will however be turned on during boot. So rebooting will set it back on.
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
I am also on stock Rom and rooted. Interested to know any non-rooted phone got this problem?
BTW. I found a quick (at least quicker than pull the battery) way to get out of the forzen lock screen (sometimes forgot to do the 0011 trick): press the power button (screen will Dim instead of OFF), then hold the home button for few seconds, as soon as you see the "menu" and "back" button lit up, the lock is un-freeze...
A permanent solution is appreciated for such an advance phone....
sassorock said:
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
Click to expand...
Click to collapse
Not that I know of.
Problem solved. For me anyway. Hope works for all of you having the same trouble.
My trouble begin with recent upgrade to LH3. My S3 was rooted by S3 toolkit v2.0. CWM installed was v4 something.
I un-rooted the phone. Uninstalled S3 toolkit v2.0. Re-installed the S3 Toolkit v5.0. Rooted the phone again (CWM become v6....).
I do not know it was CWM version caused the trouble or not. But my S3 is ok now.
I got it on my non-rooted phone, any additional solutions/suggestions? or service?
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
JB 4.1.1 caused these WiFi issues on my phone
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
Exact opposite for me...never had the problem then since loading stock JB 4.1.1 with root I get lockups or freezes whenever WiFi is turned off or I leave my router's range. As soon as I disconnect from WiFi the whole phone freezes.
The *#0010# also locks up the phone when I turn off the WiFi power saving feature.
None of this happened before JB...and I replaced my phone with week via warranty due to this and the new phone does the exact same thing as soon as I upgraded to JB with root.
Any ideas?
Black screen / random reboot solution
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
giz_zard said:
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
Click to expand...
Click to collapse
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
For me this also worked. Resolved everything. (on i9300 int)
Boomer6345 said:
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Click to expand...
Click to collapse
This is on JB 4.1.2, Phone had been updated to 4.1.2 for about a month. The issues started after a pdf download. Once all pdf's were deleted the handset works perfectly.
Giz
Okay, I would have liked to post this in development but apparently I dont have enough posts. What is th deal with the phone dropping out on CM10 when the screen goes black from the sensor, then coming back when the call is dropped by the other person. Does anyone have a fix for this, the CM10 thread gets so diluted with different issues you'd think people would start making other topics regarding issues rather than discussing them throughout a 30 page thread.
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
tallyforeman said:
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
Click to expand...
Click to collapse
Yeah but it also drops the phone call when that happens.
Thanks really strange. Try getting a fresh download with the gapps and flash it again.
It's a good thing you didn't post this in the development because it would have been moved here. You can always PM me with questions and I try my best to respond to everyone in a timely manner.
Anyhoo. I'm not quite sure as to why this isn't working yet. I've called my family, friends, girlfriend, whomever a few times already and haven't ran into the problem yet. With this being said, no one is giving any real details on what leads up to the problem or how to really reproduce it. The best I've received so far is "I make a call, the screen goes off and won't go back on." What I need is someone to get me the logs of this happening. As weird as this may seem it's the only way I can help anyone with it. Apparently from what I hear the phone is still "working" but with the screen just not turning back on. If this is the case, anyone should be able to plug their phone into their computer and get me a logcat of what is going on (this doesn't require any screen interaction if the phone is setup properly). If you have any questions on how to get one, search the forums. It's been posted in just about every development forum for every phone including ours.
My phone did that last night. People in the CM10 thread have been blaming it on the bluesleep fix but who knows. I had that flashed at the time too. When it happened, I was on a call and the call dropped a few minutes into the conversation, the screen stayed black and didnt come back on. I had to pull the battery and restart. I called the person back and it happened again. Long story short, due to my own error, one thing led to another and I ended up SBF'ing. Since last night, I made one call and it didnt happen. I need to make more calls to see if it persists. The problem is, I dont call people very much. lol
Just want to add that I was having this issue also. I only noticed it after I installed the bluesleep fix... I SBF'd and installed clean with no bsfix and have not had this issue since... Maybe it has nothing to do with bluesleep but thats some really strange timing if it doesnt.
If it happens to me again I'll get a log for you DZK but seeing as I don't plan on flashing the bluesleep fix back I don't think it will happen.
Well I sent a message to you DZK cause i'd really rather avoid SBF if I could. But if I have to I will because most people are linking it to the bluesleepfix which I did indeed install. In any case, the phone just hangs when the screen shuts off until the other person hangs up the phone then the call is ended and the screen comes back, but until then voice is dropped the call is droped and the screen remains off as that person tries to talk to me but isnt disconnected until they end the call.
[Tutorial] How To Logcat
Logcat or it never happened.
download adb
place it in folder I use
Code:
c:/root
open command prompt
Code:
cd/
Code:
cd c:root
Code:
adb logcat *:E > oh_nos_it_crashed.txt
should work
oh_nos_it_crashed.txt will be in root folder can name it
Code:
adb logcat *:E > dropped_call.txt
if you want
I'm having similar issues. The phone locks up on a call and can't be unlocked. I just have to pull the battery. The call continues for me, so at least I can finish the call, but to hang up - pull the battery.
I currently have the CM10 ROM, gapps v5, and bluesleep fix applied.
So, how does one get rid of the bluesleep fix? Can I delete is somehow using a root browser, adb, or... ? If not, can I just reflash the ROM and gapps files (without the bluesleep fix) without a factory reset, etc.? Or am I in for a complete refresh of the phone and reflash of the ROM and gapps?
TIA
no way to remove bluesleep that i remember
just restore nandroid of rom other than cm10, then reflash cm10
This started happening to me tonight.
I haven't installed the Bluesheep fix... unless that's the MX2 wifi patch.. if that's the case then I have that too.
My current workaround is using headphones, which disables the proximity sensor.. I also put my phone to stay cycle a little longer.
I just flashed my phone with CM10a3 Wednesday and ran into this issue with the first call I tried to make. I'm still new to rooting and flashing ROMs (my first time lol) so I don't have too much useful information, I will try and gather some logs next time it happens. Unfortunately it is not something that seems to happen every call. My current work around is to use bluetooth or speaker phone as the issue does not happen then.
I'm using
CyanogenMod 10-20130113-Daytona Alpha 3
gapps-jb-20121011-signed
I'm also running into issues with the mount locations and losing settings upon restart, however I still need to do more research on those items first.
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
licwid said:
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
Click to expand...
Click to collapse
lol carrying headphones around? that sounds a bit overkill.
Hello everybody! I'm a newbie when it comes to these things, so please bear with me
I recently bought a Galaxy Grand, however, it seems to have a problem - it hangs up once every day on an average which requires a boot by holding down the power button for 5 seconds or more (sometimes even requiring a battery removal).
It seems to happen at random times, sometimes when the phone is being used, sometimes when it is just lying idle. The main problem is that when it is actually hung up, people trying to call me will hear the normal ringing tone (with which they assume my phone is ringing), but my phone neither rings, nor stores the call log on reboot!
So in effect I would not get to know if someone called me or not, which is not a good situation to be in!
I am trying to get to the bottom of this, so what I did was install CatLog to monitor the activities of the phone. As I have been made aware, Jellybean does not support logging programs fully unless rooted (and my phone is not), so it shows only basic logs. However my phone shows crazy usage (almost 70 entries per second – mainly something like this over and over (full log file attached - till a hang).
02-14 12:23:37.544 I/brcm-gr ( 6506): [gralloc_lock]: new usage 0x933
I tried the same test with an S3 (jellybean), and that showed around 1 entry in approx 10 seconds (which I assume is normal).
Can you please help me figure out what the problem is? Do you think this is a hardware or a software issue? I have attached a log file with this message, that goes all the way upto once instance where the phone had hung up.
Some other points to note:
It seems the phone hangs up more frequenty when the GPS is on
The phone does not hang up in the 1st 3-4 hours after rebooting
The phone has not yet hung up at night (coincidence, perhaps?)
Thanks a ton
DM
Hi,
sorry for posting here without being a developer myself. It seems like nobody on the other boards knows enough about android to be able to help me with this particular problem - which is the most strangest problem with electronic devices I have experienced so far:
The tends to "loose" sensors after a while. This mostly happens when in sleep mode, but can also happen during charging, sometimes after half a day, sometimes after a few seconds. The following sensors are affected: Accelerometer (including auto rotation), light, magnetic field, orientation and GPS. The sound and battery sensors keep going.
Now, while this is very annoying, it is not really strange. The strange part is the following: Two times I thought to have found the problem and get it back working normally, only to learn better 2 days later:
1) when I uninstalled the Dolphin browser - which never really worked on this device - the problem disappeared for more than a day and I thought it solved. Alas, it returned about two days later. So, Dolphin may have been a cause, but something new jumped into its place after 2 days.
2) at some point, I decided to uninstall Smart Launcher 3, which I had installed right at the start. E voilà: problem gone, the sensors worked perfectly without a single glitch for 2 days. So Smart Launcher must have been the culprit, right? -> wrong! Two days later the problem reappeared, worse than ever! All it takes now is putting the tablet to sleep for ~ 1 minute and the sensors are gone. If I want to use the sensors, I have to either prevent the sleep mode or restart the tablet whenever I want to use it.
So far, I haven't found another solution to make it work for 2 days (or even longer than a couple of minutes). But anyway, it doesn't make any sense. Why would uninstalling an app make the problem disappear, but only for 2 days? Then the same story again, when uninstalling another app?
Any kind of hint or suggestion is greatly appreciated, I am desperate and have no more ideas what else to try. All pleasure in the device is gone, it's just frustrating.
Thank you a 7'200 times (seconds in 2 hours)!
- spitfire
It just got more weird. I figured out, that enabling the power save mode caused the tablet to work somewhat normally, meaning sensors would still work after sleeping most of the time.
But guess what: 3 days later even that workaround doesn't work anymore. Restarting the tablet brings the sensors back, but switching the screen off (sleep mode) for 5 seconds is enough to disrupt them, always. This doesn't make any sense at all. Why does the device always find a way to counteract my workarounds after 2-3 days? Is the thing alive and doing it on purpose? It starts to drive me really mad :crying:
Please, does anybody have an idea? I am looking for
ways to restart the sensors without having to reboot the tablet. There must be some service to kill and restart, right?
ways to identify the cause of the problem. There must be some kind of event log where the sensor crash and what happened before is recorded.
I am sure somebody must know about those things, at least in this forum. Otherwise I don't know what to do, I run out of workarounds, the evil device wins this battle and will soon target the world - welcome Skynet.
Thanks very much for any kind of help
Pesche
edit: I noticed that when the problem occurs, it takes the tablet longer to wake up than the few times when everything is fine. This indicates that there is something going wrong with the wake up process. It must be possible to see in some kind of log what exactly happens, but my sparse knowledge of android isn't deep enough. I already tried OS monitor to access the catlog and I do see some warnings (pink W), but they don't tell me much. E.g.: OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without. Or: Syste: ClassLoader referenced unknown path: /mnt/expand/.../com.eolwral.osmonitor... (which rather sounds like a problem of OS monitor itself than a problem of the system).
i installed termux... ran top... i see a /system/vendor/bin/sensorhubd
i assume thats the process not "waking up"
is there a way to monitor that? or to tell it to restart? so we dont have to reboot everytime.............
isak.sr said:
i installed termux... ran top... i see a /system/vendor/bin/sensorhubd
i assume thats the process not "waking up"
is there a way to monitor that? or to tell it to restart? so we dont have to reboot everytime.............
Click to expand...
Click to collapse
I think i found whats killing it: google play services... disable body sensors permission in settings-->apps-->google play services-->permissions--> body sensors
also uninstall mcafee.