Hey guys, instead of trying to describe my problem I'll just post this brief report.
Product:
Archos 101 - 16gb
OS:
Urukdroid
Build:
1.0
Firmware:
2.1.8
pre-conditions:
Before installing urukdroid I completely formated the hdd; Urukdroid is installed in the internal storage.
Expected result:
After the power button is pressed the tablet should wake up properly.
Actual Result:
I need to press the power button several times making the screen blink a couple of times. Every now and then I cant wake it up at all. However, after holding the power button for a few seconds the screen blinks for a brief moment before turning itself off.
- This error is not reproducible when Im using the stock ROM or Chulri's method.
One more question: If im using Urukdroid 1.0 am I stuck with firmware 2.1.8? Is it possible to update to the latest firmware?
Thanks guys!
Same problem..but
ActuallyDan said:
Hey guys, instead of trying to describe my problem I'll just post this brief report.
Product:
Archos 101 - 16gb
OS:
Urukdroid
Build:
1.0
Firmware:
2.1.8
pre-conditions:
Before installing urukdroid I completely formated the hdd; Urukdroid is installed in the internal storage.
Expected result:
After the power button is pressed the tablet should wake up properly.
Actual Result:
I need to press the power button several times making the screen blink a couple of times. Every now and then I cant wake it up at all. However, after holding the power button for a few seconds the screen blinks for a brief moment before turning itself off.
- This error is not reproducible when Im using the stock ROM or Chulri's method.
One more question: If im using Urukdroid 1.0 am I stuck with firmware 2.1.8? Is it possible to update to the latest firmware?
Thanks guys!
Click to expand...
Click to collapse
I have the same problem but i noticed that the problem occurs with certain apss. for example with paypal. After installing it i have the same problem. By the way its not only with Uruk because i formatted and reinstalled with latest firmware and the same thing happens. I do not have a solution yet but uninstall the apps which cause the problem...
ActuallyDan said:
Hey guys, instead of trying to describe my problem I'll just post this brief report.
Product:
Archos 101 - 16gb
OS:
Urukdroid
Build:
1.0
Firmware:
2.1.8
pre-conditions:
Before installing urukdroid I completely formated the hdd; Urukdroid is installed in the internal storage.
Expected result:
After the power button is pressed the tablet should wake up properly.
Actual Result:
I need to press the power button several times making the screen blink a couple of times. Every now and then I cant wake it up at all. However, after holding the power button for a few seconds the screen blinks for a brief moment before turning itself off.
- This error is not reproducible when Im using the stock ROM or Chulri's method.
One more question: If im using Urukdroid 1.0 am I stuck with firmware 2.1.8? Is it possible to update to the latest firmware?
Thanks guys!
Click to expand...
Click to collapse
not sure it is the problem, but try to set the brightness level >30%..
fly_us said:
not sure it is the problem, but try to set the brightness level >30%..
Click to expand...
Click to collapse
Sadly, that's not the problem. I always keep the brightness around 11% to save the battery.
ActuallyDan said:
Sadly, that's not the problem. I always keep the brightness around 11% to save the battery.
Click to expand...
Click to collapse
Try to increase it to >30% and restart again. It is an very old bug of gen 8 Archos since first froyo rom. Any brightness <30% make the wake up process become very unstable.
fly_us said:
Try to increase it to >30% and restart again. It is an very old bug of gen 8 Archos since first froyo rom. Any brightness <30% make the wake up process become very unstable.
Click to expand...
Click to collapse
Oh sorry, there was a small misunderstanding on my end. I actually read <30% last night . Anyway, I have set it to 50% now and so far everything has been working just fine. Thank you!
Related
My O1 shuts down every few hours by itself. As everybody told me, i removed the sd card to see if that is the problem, but it still shuts down. Al this "shutdown frenzy" started after i flashed the first custom rom, Void.
I flashed back via nand recovery, i did all possible stuff, but nothing. As i tried reinstalling the original firmware i found out that i coudnt, theres no firmware for Romania, and the KDZ crashez on my machine...
Any suggestions on this one?
Ruwin said:
My O1 shuts down every few hours by itself. As everybody told me, i removed the sd card to see if that is the problem, but it still shuts down. Al this "shutdown frenzy" started after i flashed the first custom rom, Void.
I flashed back via nand recovery, i did all possible stuff, but nothing. As i tried reinstalling the original firmware i found out that i coudnt, theres no firmware for Romania, and the KDZ crashez on my machine...
Any suggestions on this one?
Click to expand...
Click to collapse
Strange... it's really hard way to resolve, but what about some logging on SDCARD? Problem is that it can be really huge file. And Murphy law... it definitely will not restart for many hours...
I just bought a class 6 sd card, i'm testing it, maybe it's the card that shuts down the phone... i'll post the result tomorrow.
Lol man , I have the V10B for romania . I can give it to you on messenger if you add me : zerobarat1 .
Cheers
I had void with gapps, gingerbread, kernel, a2sd, blink, tapps folders on sd. Then I flashed milk_os kernel. Everything was fine.
Then I created stage fright and hwacc folders for quadrant testing. Something happened my neocore score was only 9 fps (though quadrant was 1100). I deleted stage fright, hwacc and kernel folders. Phone was fine again. But was going to sleep of death after some time of non usage. Didn't reboot even from power button. Had to take put and reinsert battery.
So I created the kernel folder again and rebooted. Went into recovery again and applied milk_os kernel again and rebooted. Everything is fine now.
Something remotely similar happened to me a while ago. I found the phone turned off without any particular reason and it refused to power on until I removed and reinserted the battery. It had me worried, but fortunately this didn't happened again ever since.
My problem seems unsolved. I also found my phone dead two times again only in last 4 hours.
Guys any solution. I have void with a2sd enabled and with mik_os kernel 1.1
Did you have the same problem when you were on stock? It might be a physical fault rather than the rom. Also, I believe the latest void already have mik_os kernel 1.1? So there was no need to flash it again.
a2sd maybe? I read quite a lot of issues with that thing.
Miks kernel 1.1 has some scrolling bugs, flash 1.0 and maybe problems solved
I applied mik_os v 1.0. Now everything seems ok for last 16 hours. Will notice further.
Everything ok till now. May be it was something related to mik_ os 1.1.
With 1.0 problem seems to be fixed as of now.
Try dev kernel v3, it's enhanced version of mik's v1.0 kernel
Sorry to say, but this damn bug stroke again. I just found my phone dead, unwilling to reboot unless I took out the battery (which, by the way, was 94% full).
I'm using void #alpha with a2sd and mik_os kernel 1.0 and I don't have the sdcard unmount problem. I can't tell if this also happens on stock ROM since I don't intend to go back to stock ROM until LG rolls out the 2.3 version.
Waiting for some stock ROM user input, but my guess is that this is hardware related.
Any help?
That happens to me all the time!! I took it to LG center and they said it's because of software problem. Anyway, now my phone has one problem. I accidentally made the locker apps to make default screen and it totally black out my home screen. I can't access to my setting to get rid of this apps or can't make even calls. I tried restarting again and again but it doesn't work. How can I uninstall the apps on phone storage by using PC? Or any better way to solve it. I'm a beginner to Android. So, please kindly help me. It is so annoying.
Hit the search button on phone and if search screen appears, type settings in it. If you are able to reach settings, you can do everything from there. Try playing with the search button on the phone.
If this does not help, you will have to do a factory reset. You can do a factory reset by the pressing the combo of home + vol down + power on buttons if you are on stock rom. If other rom, do via recovery.
winnie34 said:
That happens to me all the time!! I took it to LG center and they said it's because of software problem. Anyway, now my phone has one problem. I accidentally made the locker apps to make default screen and it totally black out my home screen. I can't access to my setting to get rid of this apps or can't make even calls. I tried restarting again and again but it doesn't work. How can I uninstall the apps on phone storage by using PC? Or any better way to solve it. I'm a beginner to Android. So, please kindly help me. It is so annoying.
Click to expand...
Click to collapse
same here too .... (when the phone turn off the screen automatically...or auto suspend...is the same) i have the #echo and .... i have the random power off and... some times... it keeps on the boot loop when it supous to suspend... butn when i suspend the phone whit the power button ... the phone keeps working fine... i dont know what to do... XD
I got the class 6 SD and since then i had no problems with shutdown. Though at the time i'm writing, my O1 is at service. It seemed that the shutdowns are related to the sd, even if you don't get any unmount errors. My logs say that each time the phone shut down, it was trying to access a service from the sd memory, and, guess what, there was no sd! So it closed all the services.
could it be unmounting sd card?
After a long time of checking how to fix this, I, finally found it.
I had this error several times, and, I always tried to check where it was the error. I did a factory reset and, suddenly this error stopped. But I needed to know exactly by "doing what" this error appeared.
This error appears in one of this two:
- if you dissactivate the "rotation" in your phone.
- if you dissable bluetooth in your phone
One of those two. If I dissable this two, my phone, in about 1 hour, it suddenly shutdown. But inmmediatly if I enable this options, its stops to crash.
You can toogle this options with the "battery" widget in your phone.
I hope this will help you, as it helped me. Plz, tell all the ppl about, how to fix this.
Hi,
I recently updated to the XWKI8 stock firmware and now the screen fails to time out I have tried setting the time out to 15s/30s/1 min but the screen never switches off.
Is this a know issue? Is there any work around? I am getting fantastic battery time gains by upgrading from 2.3.3 but all is lost the moment the screen gets turned on due to an incoming message (when the phone is in my pocket) and then never gets turned off)
--Ashwin
kkashwin said:
Hi,
I recently updated to the XWKI8 stock firmware and now the screen fails to time out I have tried setting the time out to 15s/30s/1 min but the screen never switches off.
Is this a know issue? Is there any work around? I am getting fantastic battery time gains by upgrading from 2.3.3 but all is lost the moment the screen gets turned on due to an incoming message (when the phone is in my pocket) and then never gets turned off)
--Ashwin
Click to expand...
Click to collapse
1) Tried normal reboot since flash?
2) Updated via Kies? So maybe you try to reflash it but then you have to do it via Odin (Kies just see that it's the actually one)
Here the files and instruction: http://forum.xda-developers.com/showthread.php?t=1075278
CHEERS
kkashwin said:
Hi,
I recently updated to the XWKI8 stock firmware and now the screen fails to time out I have tried setting the time out to 15s/30s/1 min but the screen never switches off.
Is this a know issue? Is there any work around? I am getting fantastic battery time gains by upgrading from 2.3.3 but all is lost the moment the screen gets turned on due to an incoming message (when the phone is in my pocket) and then never gets turned off)
--Ashwin
Click to expand...
Click to collapse
Please try the following - if not already done:
1. Wipe cache partition in recovery mode (Volume UP + Home + Power).
2. If you have CWM then also clear Dalvik cache (for Java VM).
If that does not help either, you may have to make a hard reset (*2767*3855#).
As this will wipe internal SD card, be sure to have everything in a backup elsewhere.
EDIT:
Here is another guess to try before.
There are two different places where you can set the screen off time.
The one you found is (I am sure) in Menu => Settings => Display => Screen timeout.
The other one is in Menu => Locations and Security => Timeout.
Maybe there is an other value set on your phone.
Try to change this setting before wiping everything.
Good luck !
Resolved!
A combination of the above two suggestions resolved the problem. Tried setting and unsetting security options and rebooting. It seems to be working now.
Thanks guys!
I've updated my Sony Tablet S through S.ony AiO tool v3.1 2 months ago to Android 4.0.3.
There was some bugs that i don't know why and how to fix, I've done the factory data reset several times but those bugs were not gone.
1. When I go to Youtube app and tap the search box, 1/3 screen flashes constantly, each 15 mins after getting out the home screen, and get in Youtube again, it's still like that but only in 5 seconds and then I watch normally.
2 . Sometimes, when I was in some apps, it automatically press the back button or home button on the screen when i do nothing and the app exits.
3. Sometimes, when i do somethings seems "heavy", it restarts.
Can I flash back to Honeycomb 3.2.1, if yes, how?
Thanks a lot!!
kerisbozu said:
I've updated my Sony Tablet S through S.ony AiO tool v3.1 2 months ago to Android 4.0.3.
There was some bugs that i don't know why and how to fix, I've done the factory data reset several times but those bugs were not gone.
1. When I go to Youtube app and tap the search box, 1/3 screen flashes constantly, each 15 mins after getting out the home screen, and get in Youtube again, it's still like that but only in 5 seconds and then I watch normally.
2 . Sometimes, when I was in some apps, it automatically press the back button or home button on the screen when i do nothing and the app exits.
3. Sometimes, when i do somethings seems "heavy", it restarts.
Can I flash back to Honeycomb 3.2.1, if yes, how?
Thanks a lot!!
Click to expand...
Click to collapse
If you have root then yes. Also there is a new 4.0.3 known as release 1a. Be sure to preroot before install, if you want go maintain root.
Chur
Stifilz
stifilz said:
If you have root then yes. Also there is a new 4.0.3 known as release 1a. Be sure to preroot before install, if you want go maintain root.
Chur
Stifilz
Click to expand...
Click to collapse
ok, tks a lot!
I have an Archos 101 G9 Turbo 250GB hard disk tablet.
I have modified it in the following way:
1) Installed a Samsung 830 series 512GB SSD (7mm thick)
2) Installed the Official SDE Menu
3) Installed the ArchosG9 freezenook's Rom [BUILD6]
What I find is that randomly and very frequently; the screen becomes unresponsive. These are the symptoms:
1) The screen does not react to touch
2) Music continues to play
3) Volume button works
4) Power button works
5) External keyboard can be used to control the tablet
If I use the power button to turn the display off and then back on again then most of the time the screen becomes responsive again. Other times I have to completely reboot the tablet.
I tried reinstalling “ArchosG9 freezenook's Rom [BUILD6]” and “Stock Archos Firmware 4.0.28 (file version of 2nd Mach 2013)” multiple times to no avail.
I should add; The screen issue may have started when I first installed a rooted rom. I only use this tablet as a media player for my car. Power on / power off / start and play music app are all automatically controlled via Tasker. And since I play audio books a lot; I hardly ever used to touch the screen unless I wanted to pause / rewind. Therefore I am not sure when the screen problem may have started and with which rom.
Can anybody help in resolving this issue?
Thanks in Advance.
Is the new hdd same size as the original? It might push the screen and cause the issue.
GEN9 tablets are known to have bad screens here on xda, so it might be just that also.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Is the new hdd same size as the original? It might push the screen and cause the issue.
GEN9 tablets are known to have bad screens here on xda, so it might be just that also.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply.
The Samsung 830 series 512GB SSD is 7mm thick. I bought this drive especially to prevent the "push the screen" issue. Also, the tablet worked ok for the longest time with the SSD I am not sure but I think the screen problem occurred sometime after I installed a rooted firmware. I think the first rooted firmware was the "Stock Archos ICS Firmware 4.0.7 - ROOT Version". Since then I have flashed many Stock based firmware finally settling on the "ArchosG9 freezenook's Rom [BUILD6]"
Is the screen OK in stock firmware? Rooted firmwares do not touch the stock FW, so reinstall it to get kernel back if you deleted it and test it. You can also test rooted 4.0.7 ROMs to see if the issue is 4.0.2x ROMs.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Is the screen OK in stock firmware? Rooted firmwares do not touch the stock FW, so reinstall it to get kernel back if you deleted it and test it. You can also test rooted 4.0.7 ROMs to see if the issue is 4.0.2x ROMs.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I will try that. But first, I have started to:
1) Uninstall the SDE,
2) Install the stock Firmware from Archos site.
3) Test with this firmware
then I will
1) Install SDE again
2) Install rooted firmware
3) Test with this firmware.
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!