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.
It is ok yesterday.
And I installed about 10 apps today and found that it will reboot if I lock the phone (the screen goes dark).
I don't remember the name of those apps.
So, how can I find out the problem of the certain app?
Must I uninstall all the apps to find out the problem?
THX!
If u go to the market and download a app called (instant uninstaller) it lets u choose to show the apps by date installed
Sent from my ADR6400L using XDA Premium App
thx！ let me try it.
So did this fix your issue? I am having the exact same problem.
I'm rooted (using ADB method), running Das BAMF 2.1 with Imoseyon's 2.54test4 kernel .
I can reproduce the a reboot everytime by doing this:
1. With the phone unplugged from the charger, press the lock button so the screen goes off. Once the screen goes off, in about 10 seconds it will reboot everytime.
2. Or, if I leave it set and the screen goes off by itself, it will reboot in about 10 seconds (after the screen goes off) everytime.
If I leave it on the charger, or never let the screen go off, it has never rebooted on me. I got this phone 2 days ago and have been battling it ever since.
UPDATE:
I have eliminated the following as a potential issue.
1. I wiped everything and flashed a new ROM, Kernal, and Radio, and still the exact same results.
2. I tried a new battery, and still the same results.
3. Tried two other kernals with each of the two ROMS, and still the same results.
Out of ideas at the moment.
Thinking of trying to flash back to stock so I can see if it still does it then.... Lost.
Solved my problem for now. Here is what I did.
1. Flashed back to these radios
CDMA: 1.13.605.7
LTE: 1.12.605.6
2. Flashed back to Froyo based ROM, Das BAMF 1.8.
Of course, I wiped everything before doing so. I've been up for about an hour now with my phone resting comfortably with no reboots at all.
Will try again in a few days to flash back to a gingerbread based rom, as I would really like to have Netflix.
If anyone has a gingerbread ROM and radio combo that they have working well together please let me know. You might also shout out which kernal you are using too.
UPDATE:
So I have obviously done some more troubleshooting on this, and I may have something to make sense of.
Since I flashed the GB MR2 radio and ThunderstickGB rom using the kernal provided with it. After bootup, I again had the reboot issues everytime the screen timed out or was locked. Just like before, It would reboot everytime unless the screen was kept on or plugged in to a charger.
I flashed back to the original Froyo radio just to see if that would make a change. Of course, I had no signal, but it would at least tell me if it were the newer MR2 or MR2.5 radios giving me fits. Even with the original radio, it still gave me the same reboots on screen timeout or locked.
So, I started over and this is what finally worked:
Flashed MR2 radio and ThunderstickGB rom again. This time, I flashed the stock GB kernal, instead of using a modified one. Bingo.... no reboots at all.
My feeling is that for some reason, some of the Kernals are undervolting the unit to a point that it shuts off or reboots. I am completely technically illiterate when it comes to the inner workings of Kernals and such, but the one common demoninator between my working Froyo and GB roms was that there was no Governor or Speed Tweak controlling the processor other than what comes in stock form.
Oh and by the way, thanks for eveyone's help with this.... I couldn't have done it without you.
I'm using Gingervillain mod rom but also has this issue on erenz miui. Randomly I lose my volume, home, menu and back key functions. No light on home key but power key works fine! I select reboot and I regain function for a while.
I have not flashed any new kernels. I have checked my apps and can't see any new ones that could be causing a problem. I thought it could be overclock related but at stock frequency its the same.
Tearing my hair out please help! Will test a stock rom after work tonight...
Sent from my X10 using xda premium
i lost menu button function once.in first WB backup after doing factory reset. but didn't face that problem.Anyway it's 100% software problem.as volume buttons have nothing to do with home and back keys.
Also can u enter Recovery mode or flashmode ? then ur keys are fine.i can enter recovery mode in DoomKernel by volumeUp button.YOU know every one would suggest you to revert back to stock ROM. it's the best way to test your keys.
Hope they're fine.
Omar
I will try stock rom and kernel. However I know my current set up worked fine for at least a week or so. It must be a rogue app update or something its just impossible to pinpoint!
I can enter recovery just fine. All of a sudden my phone is OK for now but I know it will happen again!
Sent from my X10 using xda premium
Just an update.
I wasn't prepared to try stock rom as i KNOW my current setup did work. So at first i thought it was Titanium backup causing it as it happened straight after restoring apps. Installed apps manually but eventually got the error again.
Now i've flashed Dooms failsafe kernel and i'm testing that. If not it is an actual app from the market causing this!
Sorry for multiple posts. Just a bump to get this noticed. All appears well on failsafe kernel. My guess is my phone all of a sudden didn't like the undervolting as I didn't have it overclocked.
Ephumuris
Hi,
Originally my phone was from the UK Carphone Warehouse (CPW)
I have upgraded it from 2.2 to 2.3 etc...
The last time I did a firmware upgrade to ICS was a few months back and I didn't have any problem doing it.
After the upgrade, I had a few bugs. I used this file - GT-I9100_XEO_I9100XXLPW_I9100OXALPW_I9100XXLPW.tar and the main bugs I have are - The screen won't lock and when I press the Power Button, it will turn the screen off but when I hold it for 1 second the phone closes down.
So today I thought, lets see if I can change my firmware to a CPW version, so I downloaded GT-I9100_XEU_I9100XWLP7_I9100XXLPS_I9100XEULP5.tar and installed that. It went through the usual stuff and upon restarting I was getting an "android.core" crash. The screen stops working and after several reboots nothing change. I also booted up and cleared the cache, and this didn't do anything either.
I have just reverted back to the first ICS upgrade but still has not screen lock or when I press the power button for 1 second it closes down.
I wondered if anyone else has had these problems or could recommend to me what may fix it.
I appreciate all help
Thanks
TBS
TheBritScott said:
Hi,
Originally my phone was from the UK Carphone Warehouse (CPW)
I have upgraded it from 2.2 to 2.3 etc...
The last time I did a firmware upgrade to ICS was a few months back and I didn't have any problem doing it.
After the upgrade, I had a few bugs. I used this file - GT-I9100_XEO_I9100XXLPW_I9100OXALPW_I9100XXLPW.tar and the main bugs I have are - The screen won't lock and when I press the Power Button, it will turn the screen off but when I hold it for 1 second the phone closes down.
So today I thought, lets see if I can change my firmware to a CPW version, so I downloaded GT-I9100_XEU_I9100XWLP7_I9100XXLPS_I9100XEULP5.tar and installed that. It went through the usual stuff and upon restarting I was getting an "android.core" crash. The screen stops working and after several reboots nothing change. I also booted up and cleared the cache, and this didn't do anything either.
I have just reverted back to the first ICS upgrade but still has not screen lock or when I press the power button for 1 second it closes down.
I wondered if anyone else has had these problems or could recommend to me what may fix it.
I appreciate all help
Thanks
TBS
Click to expand...
Click to collapse
You're in the wrong section, this has nothing to do with development
Sent from my SGH-I777 using Tapatalk 2
First of all wrong section mate... By the way u hav written it seems that u hav not wiping the DATA or factory reset after every flash. Try wiping DATA before and after flashing.. Also wipe cache..
Hey guys,
Been lurking on the site for a while, I've searched all morning for what i need but with no success.
Setup: Att sgh-i777 rooted etc. running JellyBam 5.1
Problem: Power button stopped working, cannot use recovery to backup/flash new software.
Plenty of threads on the button issue, that's not the main question (suggestions welcome though) I just really want to backup before I send it off for repair.
Seems my best course of action is to get a kernel with touch based recovery. I tried downloading mobile Odin to flash a new kernel but it's telling me my phone isn't supported for some reason? I ran the dump file Odin suggested but not sure what to do with that info now. Next best option appears to be to get a .tar of the siyah kernel and flash it with Odin via PC. I just can't find a .tar for that kernel anywhere and I don't have enough posts to ask in the siyah thread.
So, can anyone give me a hand- either with trouble shooting mobile odin, or tracking down a .TAR of the siyah kernel or...any other suggestions?
Edit: Just found this- http://forum.xda-developers.com/showthread.php?t=1644240
I realize this is in the 9100 forum but looks like it simply converts a zip to an odin flashable tar which is what i'm looking for. Anyone have any experience with it?
Thanks in advance for any insight!
You want to do a nandroid backup? Yes just flash the siyah kernel in the development forum with mobile Odin. It does work with our phones.
Phalanx7621 said:
You want to do a nandroid backup? Yes just flash the siyah kernel in the development forum with mobile Odin. It does work with our phones.
Click to expand...
Click to collapse
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
flet2 said:
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
Click to expand...
Click to collapse
It possibly can be ROM related (but I am not certain). User AJ's Siyah kernel 7.6.8, it's works well with all the ROMs.
BeenAndroidized said:
It possibly can be ROM related (but I am not certain). User AJ's Siyah kernel 7.6.8, it's works well with all the ROMs.
Click to expand...
Click to collapse
Yup, running 7.6.7 now and enjoying it.. My power button is currently working again but i turned on 'swipe to wake' in Stweaks so when it fails again, at least i'll still have a working phone. the volume wake from AOKP settings doesn't work when the phone is in deep sleep so pretty useless. As long as i stay on Siyah kernel i guess i'll be able to limp along until i get the button fixed.
The Odin thing is still strange though, will have to try another ROM and see if it recognizes my phone then. Tried Jellybam 4.1 but kept getting reboots even with full wipe- tried flashing it twice. Maybe i got a bad download, i'll try again tonight.
flet2 said:
Yup, running 7.6.7 now and enjoying it.. My power button is currently working again but i turned on 'swipe to wake' in Stweaks so when it fails again, at least i'll still have a working phone. the volume wake from AOKP settings doesn't work when the phone is in deep sleep so pretty useless. As long as i stay on Siyah kernel i guess i'll be able to limp along until i get the button fixed.
The Odin thing is still strange though, will have to try another ROM and see if it recognizes my phone then. Tried Jellybam 4.1 but kept getting reboots even with full wipe- tried flashing it twice. Maybe i got a bad download, i'll try again tonight.
Click to expand...
Click to collapse
Try 7.6.8, I'm using 7.6.8-S and swipe works perfectly fine on my end.
BeenAndroidized said:
Try 7.6.8, I'm using 7.6.8-S and swipe works perfectly fine on my end.
Click to expand...
Click to collapse
Oh yea the swipe to unlock for siyah works great. I was referring to JellyBam's AOKP settings which offers a volume to wake. Volume wake works when on charger, but won't wake it from deep sleep. Siyah's Swipe wake does both :good:
I would still love to have an odin flashable .tar of siyah though- If anyone has any insight on how to get that (or make it from the .zip) that would be awesome. I used the tool from the thread linked in the OP and it did turn the kernal zip into a .tar but i don't dare flash it to test...
flet2 said:
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
Click to expand...
Click to collapse
Read somewhere that jellybam 5.1.0 places the wrong phone info in the rom. It show up as i777 instead of sgh-i777 and this might be causing Mobile odin to fail on the compatibility test.
To turn your volume up button into a power button edit the /system/usr/keylayout/gpio-keys.kl file to read:
key 115 POWER WAKE
key 114 VOLUME_DOWNWAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
key 115 is the volume up button. This only works in the fully booted os. Doesn't work in recovery.
Sent from my Apple IIe
Quicksilver13 said:
Read somewhere that jellybam 5.1.0 places the wrong phone info in the rom. It show up as i777 instead of sgh-i777 and this might be causing Mobile odin to fail on the compatibility test.
Click to expand...
Click to collapse
Yup that was exactly it. I notice it when i went back to Jellybam 4.1 and saw the full device name in the 'about'. Hopefully 5.2 drops soon with all the necessary fixes!
billyjed said:
To turn your volume up button into a power button edit the /system/usr/keylayout/gpio-keys.kl file to read:
key 115 POWER WAKE
key 114 VOLUME_DOWNWAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
key 115 is the volume up button. This only works in the fully booted os. Doesn't work in recovery.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for this info. Is there a thread or tutorial somewhere that will explain how to access and edit this file? I assume it's not as simple as just navigating to it and making the changes?
Also, how do i get volume to go up if i turn it into a power button? wouldn't that make my phone lock every time i tried to turn up the volume then?
flet2 said:
Yup that was exactly it. I notice it when i went back to Jellybam 4.1 and saw the full device name in the 'about'. Hopefully 5.2 drops soon with all the necessary fixes!
Thanks for this info. Is there a thread or tutorial somewhere that will explain how to access and edit this file? I assume it's not as simple as just navigating to it and making the changes?
Also, how do i get volume to go up if i turn it into a power button? wouldn't that make my phone lock every time i tried to turn up the volume then?
Click to expand...
Click to collapse
It actually is just as simple as finding the file, mounting the directory as r/w and then editing the file. As far as turning up volume, you would have to turn down volume and then use the on screen volume panel to adjust.
Sent from my Apple IIe
Great thanks. So to mount the directory it appears i need to use ADB, or could i use an app such as Root explorer or something like this? https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en
Can i access the file right from my phone to make the changes once i have the directory mounted correctly?
flet2 said:
Great thanks. So to mount the directory it appears i need to use ADB, or could i use an app such as Root explorer or something like this? https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en
Can i access the file right from my phone to make the changes once i have the directory mounted correctly?
Click to expand...
Click to collapse
I use root explorer on the phone. If you use a rom that has support, you can add a line into your addon.d files to keep from having to manually change it everytime you update your firmware.
Sent from my Apple IIe
Thx for the info, i'll have to test this out. I'll nandroid and back up the original file too just incase!
Let me know how it works out for you.
Sent from my Apple IIe
Hi,
My wife's power button went out on her i777. Backed up the file and changed key 115 to power wake. Rebooted. This made volume up and down both stop working. Changed it back, they both work. Any ideas?
I have it running AOKP with AJK kernel.