So,i started getting some weird problems with my phone. The phone started randomly opening apps,closing,doing anything that could be done in the app i was. I activated "Show touches" in Developer Options and i could see touches all around the screen even if i am not touching it at all. This usuall happens when i enable the Data. I'll try to get a logcat later.
Did anyone have this problem ?
I am on : MySensedx5 and Infinity Kernel V6.
nightwalkerkg said:
So,i started getting some weird problems with my phone. The phone started randomly opening apps,closing,doing anything that could be done in the app i was. I activated "Show touches" in Developer Options and i could see touches all around the screen even if i am not touching it at all. This usuall happens when i enable the Data. I'll try to get a logcat later.
Did anyone have this problem ?
I am on : MySensedx5 and Infinity Kernel V6.
Click to expand...
Click to collapse
Same rom & kernel as you, used to get it really bad (nexus kernel) but after flashing newest build of infinity kernel i get it less so, i think a few devs have looked into it already but to no avail
nightwalkerkg said:
So,i started getting some weird problems with my phone. The phone started randomly opening apps,closing,doing anything that could be done in the app i was. I activated "Show touches" in Developer Options and i could see touches all around the screen even if i am not touching it at all. This usuall happens when i enable the Data. I'll try to get a logcat later.
Did anyone have this problem ?
I am on : MySensedx5 and Infinity Kernel V6.
Click to expand...
Click to collapse
Try my latest kernel. It should reduce those fake touches. Btw I'm on sense4+ currently and I dont have that bug..
Hey! I faced this problem today when I was trying to switch to 2G network. It never comes with 3G. Weird.
I had the same experiences while my screen was just dirty. I cleaned it and it didn't happen again.
Related
ive searched for things such as "sleep crash", "sleep bug", "screen wont turn on" etc. but can seem to find anything that tells me anything other than turn off wifi (which i tried to no avail). My issue is that when i press the power button for 1 second to turn off my archos 70 screen it will not turn back on. Same thing happens when i let it fall asleep. If i leave it plugged in and not allow it to turn off screen i have no issues. My apologies if i just don't know what words to search for ... i tried. In on the .4 firmware (latest) with no mods. This has happened through the last 3 firmwares from archos. Any ideas?
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Techngro said:
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Click to expand...
Click to collapse
I will try this and report back. I have been installing firmware over the issue
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
I am try before formatting and report back
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
this worked!!
mallman said:
this worked!!
Click to expand...
Click to collapse
spoke too soon. did not work. it stopped after a few tries
it works again if i recalibrate but wont hold.
Zoidpilot said:
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
Click to expand...
Click to collapse
by the way, the deep sleep option also kills mine.
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
ramso said:
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
Click to expand...
Click to collapse
just tried it . i hit the icon to disable sleeping. i pressed the screen button and when i went to turn screen back on it would not wake. Did i use the app wrong?
No, you use the app rigth. The app only disable deepsleep.
Sent from my A101IT using Tapatalk
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
bbop said:
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
Click to expand...
Click to collapse
err I'm afraid that I spoke too soo. My device keeps getting stuck and won't awake from sleep. This seems to happen most after switching wifi on or off, specifically whilst the device is playing music.
Zoidpilot said:
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
Click to expand...
Click to collapse
how are you installing the firmware? maybe im doing it wrong. I let the device update to latest 2.1.4 and then i wiped it via the settings and repair menu in android.
Edit**
like this??:
Step 1: Download the android 2.2 firmware for your archos tablet from here,you might a get a false positive notification from your browser as they are unaware of .AOS format, so ignore that and download it.
Step 2:Go to Menu > Settings > Device Storage & USB connection > USB connection mode of your tablet and set the connection mode to Mobile Media Device (MTP) and now connect your Tablet to pc.
Step 3:Now when the tablet is detected you will see a hard drive icon,double tap and open it and copy and paste the firmware (.AOS) file into the hard drive(make sure you dont copy it in any folder inside it like Music,Videos etc).
Unplug the USB connection and the Archos device will automatically locate the update file and will prompt you for the update,just follow the screen options and you are done,if it does not prompt you for an update then you might have accidentally misplaced the file in one of the folders,just locate the .AOS file from the file manager and and open it to start the update.
No no it wasn't that complicated... It was actually the simplest fix for a difficult problem. My device when I got it was running 2.1.2 out the box... Even then It had the screen problem. When I got the chance I installed 2.1.3 OVER THE AIR. Straight from Archos. Still had the issue though, I figured it would have been fixed but was greatly disappointed... Then I sort of just lived with the problem for awhile... I saw that the 2.1.4 update was released but was wary about downloading it because sooo many people are having issues. Just the other day though, the device cut off on me again and I figured to hell with it... So I downloaded the 2.1.4 OTA as well... no website, no manual install, I just let the device run its course on its own. After the update, it rebooted normally and it's been working great since... Sorry to hear not everyone is so fortunate... I really hope this helps somewhat
Dear memeber
i have a new problem with my htc legend its sometimes when i need to do something the touch screen give me a wrong selection and other times it not respond ,,, i do a restart for the phone and it back to work .. but i can't keep turn the phone off and re on it if somebody no how to fix this error its will be great and i keep the screen clean from everything i keep clean it but that is not help
Hello,
It happens too with my old ROM (B0.4.8), but didn't find the origin of the problem.
Sometimes it happens with my new ROM (CM9 Beta4) but only when I charge it (when by USB), as soon as I disconnect the cable, the phone is functionnal...
yeah but its not a problem with the room because i didn't do anything for the Os on it .. it just start like this sometimes it respond other times no .. if it work you have to made a selection many time or restart the phone
I experience it too. As I remembered after installing HomICS Venus this problem occur. I do not know whether its ROM related or not. I tried to flash another ROM ex. BlaYO ROM and CRQ 1.3 but the problems still persist.
I had this problem too - sent it to HTC and they exchanged my Legend for a new one ----- as I heared it is a common problem and has to do with the grounding of the touchscreen -> that is why it works sometimes and sometimes it doesnt
Sorry to say that I too suffer from this problem. Also, the part of my screen, where the power widget on the notification bar is resting, is completely unresponsive. I need to use the trackball to hit those buttons. And also, sometimes the screen can just go bananas and go into spasmic movements on its own. In my frustration once I hit the screen really hard with my knuckles and that temporarily fixed the spasmic movements. But it still reoccurs. I assume I would need my warranty to replace my phone, but my warranty has already ran out.
I can also confirm that it has NOTHING to do with your ROM. It started for me when I was running CyanogenMod 7.1, but I still have the same problems on stock ROM, HomICS, Miui, basically any ROM.
Unsure if this a problem caused by CM 10.1 or android 4.2.2 but using both jellybam and paranoidkangdroid I am unable to put the screen to sleep, the hardware button still works for shutting down just not turning off screen. I also have a hard time getting music to play, requires reboots and shutting down of apollo app, unsure of which of these actually does the trick or if its just luck.
Part of the symtoms include a flashing black screen, what it looks like is a black overlay with part of the status bar still visible. As well as rare random reboots.
Does anyone know if this a problem with the i717 and the most up to date roms or something else.
Help much appreciated thanks.
The only issue I can comment on is Apollo. Mine you have to select the music you want or hit play, wait, hit back when the app freezes and then wait for the pop up saying "Apollo has stopped working". Press Ok and go back into the app and hit play or the song you chose again to get it working. After that the app works amazing! I think it actually is a common problem on 4.2.2 but can't say for sure. The rest, I don't really know what to suggest. Sorry
Best of luck to you
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
bak3donh1gh said:
Unsure if this a problem caused by CM 10.1 or android 4.2.2 but using both jellybam and paranoidkangdroid I am unable to put the screen to sleep, the hardware button still works for shutting down just not turning off screen. I also have a hard time getting music to play, requires reboots and shutting down of apollo app, unsure of which of these actually does the trick or if its just luck.
Part of the symtoms include a flashing black screen, what it looks like is a black overlay with part of the status bar still visible. As well as rare random reboots.
Does anyone know if this a problem with the i717 and the most up to date roms or something else.
Help much appreciated thanks.
Click to expand...
Click to collapse
I'm getting this same issue in JellyBAM, PAkangdroid, and CM10.1 M-release (2013-04-11 latest). Re-flashing the ROM in recovery seems to fix it for a while, but I still haven't been able to narrow down a root cause yet.
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
If this happens on a stock rom, it is probably a hardware issue.
audit13 said:
If this happens on a stock rom, it is probably a hardware issue.
Click to expand...
Click to collapse
Thank you for your reply, but this does not happen on the stock rom.
It's definitely good that this doesn't happen in stock.
Sounds like a incompatibility between the phone and rom. Have you tried earlier or later versions of lineage?
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
I can also confirm this on the latest lineageos nightly update to date. It's as if phone is on standby/sleep and no way to wake it up without rebooting the phone by holding down the power button until phone restarts. I don't need to go into recovery like OP. Anyone else?
Are we the only ones experiencing this issue? Any help would be appreciated.
Gizmotech said:
Are we the only ones experiencing this issue? Any help would be appreciated.
Click to expand...
Click to collapse
You got a reply in the other thread where you posted about it:
minealex2244 said:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.
Thank you @Gizmotech for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
Click to expand...
Click to collapse
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Providing the last_kmsg will help Simon to find a solution. If you only complain about this issue then it won't be solved. Next time make sure to include last_kmsg.
---------- Post added at 19:49 ---------- Previous post was at 19:45 ----------
shivadow said:
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
Click to expand...
Click to collapse
Really? Do you know what beta means? I'm sure that you don't. Beta means that it is not really stable (80% or less of the things are working) while stable means that 95% of the things are working. This explains why LOS 14.1 for S6 was considered stable: because everything was working. Also that issues are already listed in the forums.
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. st the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Same problem with last lineage version. Are you found solution ?
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
cRaZy-bisCuiT said:
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
Click to expand...
Click to collapse
The problem is the rom or kernel. It happens to all custom roms and kernels on the s3. No-one has found the source of the problem.
Everything custom is beta even if it is considered stable. Beta means "not final". Unless you see a rom with "final" on it then you'll encounter issues at some point.
The only truly final product if you want root is stock rom rooted. If you flash a kernel you'll get the same problem.