I have infocus epic 1 device and its standby is terrible from the day of purchase(>2.5%/*h).It stays awake 100% of time.I rooted the phone on sole purpose of fixing it.after doing some research now i am sure it's something related to radio layer interface because when i don't install sim card mobile goes deep sleep 98% of time.better battrey stat show's kernel wakelock ttyC0 as main culprit.i think com.android.phone is the reason behind it.i have found one tedious solution to fix it.first i ve to freeze the package com.android.phone pluck the sim out restart the phone put sim back in and defreeze the package.but rebooting the phone again starts the problem.but i want to completely fix it without need to do so.also it would be hepful if i can some how block mandatory restart after inserting sim in the sim slot so i dont have to freeze and defreeze the package com.android.phone
I think you should try a (few) different SIM card(s). It may be the card itself that causes problems.
Then, I’d reboot the phone, after entering the PIN, wait a minute of so for everything to initialize, and then check dmesg (aka the kernel/driver log), or even logcat for that time period.
Also, if you can, try making a complete backup image of your system (all partitions), and
1. try a factory reset of your phone (ideally flashing the original system on there after the factory reset), or even
2. flash an older Android (6? 4.4?),
and see if the problem exists there too.
You should be able to find the newest/best case where it works, vs the oldest/worst case where it doesn't, and then look at what’s different between the two (with some graphical diff tool, using dmesg and logcat output among other things, for example) , especially with regard to your problem, to find the answer.
Related
Okey, my problem is this.
I have installed the phone locator beta from their website. Like the name says it's an app to see where your phone is if it gets stolen, wipe it through sms and do some other stuff. I did not manage to finish the application setup cause I got a phone call during the process. After that I'm locked out of the phone and the phone screen keeps shutting down. It instantly shuts back down after I turn it on. It stays on for like half a sec sometimes, sometimes less. I have managed to uninstall the application through adb to no avail. I have made a backup through recovery also hoping I will be able to restore it without getting the same problem.
But it appears that if I restore the data I get the same thing happening.
Other things I have tried:
Reflashing ROM. It's the stock one from Vodafone.
Reflashing CF-Root Kernel.
Trying to figure out which process I have to kill through adb. But I'm not experienced enough with this to do it.
Trying to remove everything about the app I find out. Still did not work.
Anyone has another idea. I really had a lot of data I don't want to lose.
Thank you.
Update: Solved in post 3.
justrome0 said:
Okey, my problem is this.
I have installed the phone locator beta from their website. Like the name says it's an app to see where your phone is if it gets stolen, wipe it through sms and do some other stuff. I did not manage to finish the application setup cause I got a phone call during the process. After that I'm locked out of the phone and the phone screen keeps shutting down. It instantly shuts back down after I turn it on. It stays on for like half a sec sometimes, sometimes less. I have managed to uninstall the application through adb to no avail. I have made a backup through recovery also hoping I will be able to restore it without getting the same problem.
But it appears that if I restore the data I get the same thing happening.
Other things I have tried:
Reflashing ROM. It's the stock one from Vodafone.
Reflashing CF-Root Kernel.
Trying to figure out which process I have to kill through adb. But I'm not experienced enough with this to do it.
Trying to remove everything about the app I find out. Still did not work.
Anyone has another idea. I really had a lot of data I don't want to lose.
Thank you.
Click to expand...
Click to collapse
What I would do is enter recovery mode. From there mount usb storage and transfer everything that's important to PC. Then wipe everything, format system, format sd card and reflash a ROM through CWM. Obviously mount again usb storage to push the ROM from PC to sd card. Maybe it's a little drastic but I can't think of anything else since I'm not a pro user or anything. Well, just an idea.
Hey thomas. Thanks a lot.
I think that's a great idea. At least it's something I did not try and might work well.
I just found out that you can enter usb storage from recovery, right now it seems I can only see the /mnt/sdcard partition. I will play with it a little to see if I can mount the other partitions before mounting USB. I think the application data is in /data/data am I right?
Okey I have managed to fixed it in the most stupid way possible.
I have noticed that if I leave the screen off for like 15 seconds then I get like 2 seconds window before the screen turns off again. I have managed to go to the screen timeout settings and it seems like the application changed that to a very low value as none of the defaults value were ticked. I have ticked the 1 minute value and now the screen stays on.
I have uninstalled the app and I'm really afraid to test it again I should probably make another backup in this state
After a normal reboot of my phone, it suddenly doesn't read my sim card anymore. When I turn it on, I'm not asked to enter the pin code and the phone doesn't connect to the network.
If I go into settings and change the pin code, or turn it off, I'm asked to enter the original pin code, so in that way there's still a connection to the sim card.
When I've done any of the above, the sim card seems to been "activated", and the phone connects to the network, and everything is as it should be until the next reboot. Then I manually have to "activate" the sim card again.
The phone has worked without any problems for a long time with the current CyanogenMod 9 custom rom and my current provider, and I haven't changed anything that suddenly can cause this.
Some suggestions to what can be wrong?
Does the sim work with other phones ? If so, it probably isn't a problem with the sim. In that case, try a factory reset in the first instance.
If that fails to work, try a fresh/clean install of CM9. If that doesn't work, reflash a Gingerbread stock rom & see if the problem persists. If the problem persists with a GB rom, then it's likely to be a sim/hardware issue.
The other thing that comes to mind is have you flashed a recent CM9 nightly ? This might explain it working OK previously with CM9 & not working now. Obviously CM9 is beta, and something funky might be going on with a more recent build/nightly.
I've now finally managed to find another phone and another sim-card.
My own sim-card works fine in the other phone - and when I put the other sim-card in my own phone it doesn't ask of the pin-code and it doesn't connect to the network.
So I believe my phone needs a complete reset - when I've got the time to do it...
One strange thing is, that at one reset earlier this week my own phone asked for the pin-code - but only once...??
I think I've found the problem. Either it's caused by Avast Anti-Theft alone or it's a combination of Avast Anti-Theft and CyanogenMod 9.
I believe it's the last one, because everything worked fine during the first time I switched from stock ROM to CM9, but then suddenly the error with the pin-code occured, and I could be caused by an update in the CM9 version.
But when I restored factory settings on my phone and started again from zero, everything was okay, and I was promted to enter my pin-code. It was the same when I restored my apps and data with Titanium Backup, but then when I installed Avast Anti-Theft the error occured again.
Actually I restored my phone once again just to make sure, and it was the same - when I installed Avast Anti-Theft, I was no more asked to enter the pin-code and the phone did not connect to the network.
So now I know what's wrong and maybe also why - but I don't know how to solve it...!?
I've had Cyanogenmod 9 nightlies on my SGS2 since April. I didn't install every single one, but pretty much only those with good ratings, specifically those that had no complains about battery drain and heating...
Currently on the 06-28-2012 nightly. This ran fine at first, but over time, it started to occasionally crash into Kernel Panic. I figured I'd just pick a new nightly, but then I ended up having to travel and installation of a new nightly got delayed.
Now I'm home, and I can't use the phone at all, cause it crashes into Kernel Panic almost as soon as I unlock the screen after Android finishes booting. The last thing I see up in the message bar is "WhatsApp error" and the screen goes dark. It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
I don't think its a problem with WhatsApp, cause WhatsApp used to run fine, while Kernel Panics originally mainly seemed to happen after I got a "storage full" message. In response, I deleted a load of pictures after rebooting, to make sure there's free space, but it kept crashing occasionally, till now, its just unusable.
I've tried to flash a stock Samsung ROM (I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar.md5) but that hasn't been working either.
Kies drivers are installed on my Laptop. Odin sees the phone too.
I followed the instructions from the rom page, changed no settings in Odin, just picked PDA and selected the ROM.
Odin goes "Added" when I plug in the phone, verifies the ROM, then the whole thing hangs on "setting up connection"
So I unplug, pull the battery and then reboot, which works fine, but once booted, it won't stay on longer than a few seconds.
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Tsais said:
It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
<snip>
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Click to expand...
Click to collapse
What's preventing you from factory resetting from recovery?
Lack of knowledge is preventing me!
How do you factory reset from the "Kernel Panic Download Mode"...?
Download Android Commander from here:
http://androidcommander.com/
Boot your phone, don't unlock.
Start Android Commander, navigate to /data/apps and delete WhatsApp's apk (com.whatsapp1.apk or something like that) or rename it to .apk.bak
Restart your phone without unlocking.
Hope the errors gone.
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!
Hello everyone,
Several days ago, i damaged the EFS partitions on my LG G3's new motherboard by overwriting it with a backup from the old motherboard, which is also D852 but originally from a different carrier. I managed to "partly" fix the problem - original thread here: https://forum.xda-developers.com/showthread.php?t=3912717
Now the problem i'm having is that cell network keeps dropping after a few hours, or often right after a call. I can sometimes reconnect by killing and restarting the "RIL" service, but most often i need to reboot the phone. This happens both with Lineage OS and with stock firmware, and with any of the "fixed" EFS i generated, either by:
(1) restoring the backup from the other LG D852 board, then booting the stock firmware and using Qualcomm's "product support tool" to write the correct IMEI of the new motherboard, or
(2) zeroing out the modemst1 and modemst2 partitions, then rebooting with the stock firmware to have the Qualcomm chipset re-generate them, then using QPST to poke back the correct IMEI as described above.
Additional info: I noticed that since this happened, after wiping the data partition in stock firmware i have to manually set up the APN before i can use cellular data, however in LineageOS 15.1 it puts the (almost) correct one by default, but i can't edit it, remove it, or add another one from the settings app. The Proxy and Port fields say "Not set" however the "MMS Proxy" and "MMS Port" are correct.
Also the battery power used by "Mobile network standby" is extremely high (almost 50% overnight with a PowerBear 6500MAh battery) but i guess that is caused by continuously trying to reconnect to the network.
...anything else i could try? Thanks very much for any assistance!!!
I just wanted to add: from futzing around with restores and backups, i've noticed some weird behaviour that i can't explain.
For example, if i restore a TWRP backup of Lineage 15.1 after restoring stock firmware (4.4 i believe) then wifi is unusable until i re-flash Lineage from the install zip. Until then i can't turn it on in the settings, it turns itself off after 1 second. There is no problem if i restore the data from a Lineage backup aftewards however. I haven't looked deep into details about this yet, but i have no idea what causes it. All the backups contain both system and data partitions.
I also noticed that if i make consecutive backups of the phone's EFS partitions (without writing anything to them in between) they don't match. This happens both with TWRP backups, and with dd'ing the /dev/block/... device nodes to files manually, either from TWRP or from the main OS. So something is clearly writing to those partitions while the phone is in normal use. Again, i have no idea what that could be, especially since EFS/NVram is kind of a sealed "black box" with no specs available anywhere, and very little tools available to manage anything about it.
Ok, now stuck in a bootloop, this is the second time this sh!#$%t happens: i setup a tasker profile to try to reconnect to the cellular network when the phone gets booted from it. It shuts down the RIL daemon, rewrites the modemst1 and modemst2 partitions from a backup, waits 30 seconds, then restarts RIL. It worked when testing it, then "sometimes" worked during actual use in the past 20 hours or so, and then suddenly i take the phone out of my pocket and it's stuck bootlooping on the LCD's hard-coded startup logo.
FAAAAAAAAAAACK the engineers that design and sell this purposely sabotaged junk should be skinned alive and hanged by the balls until they die