** Notice **
There are 2 new kernels out K011 & K012 that are supposed to fix the deep sleep issue. If you are using a ROM that does not include one of these new Kernels please do not continue reporting deep sleep issues on them. Contact your ROM developer and get them to update the ROM with the new kernel. You could try another ROM with the new kernel's included or try the fixes mentioned further down in this post.
Mainly interested in now is reports of deep sleep issue with K011 and K012. Thanks out to everyone for their help with this bug hunt.
**********
Time to find out what those of us who have no deep sleep when running the custom kernels have in common. Even if you don't have any problems with Deep Sleep, your input would be appreciated as it could help eliminate items. If you can think of anything else we can add let me know and I'll update this Post. If possible please attach the same information as I have below as it would help greatly in determining what phones that absolutely can not get deep sleep with the FreeXperia Custom Kernel have in common. When posting possible solutions please indicate if you have had problems getting deep sleep before or not.
Update - I've added a count at the front of each line to count the number of submittal's for that line. As Items are eliminated from confirmed working deep sleep users I'll change the font color to red.
Update 2 - Thread has grown beyond my ability to keep up so I'm Just going to but a synopys at the bottom. If you believe that any of my assumptions there are incorrect, please PM me with the details so I can keep this information as accurate as possible
When reporting deep sleep problem or working include the following information
-------------------------------------------------------------
Phone Information from under battery
Sony Ericsson 10a
Type: AAD-3880074-AV AAAB
FCC ID PY7A388074 CB5
IC: 4170B-A3880074 10W20
Carrier Information
1 Rogers Wireless
GSM/GPRS/EDGE on the 850 and 1900 MHz bands
UMTS/HSPA on the 850 and 1900 MHz bands
ROMS tried using custom kernel with deep sleep issues
All FreeXperia ROMs from V014 to V021
[ROM][MAY24]BlackEditionHD_1.4_SE[Gingerbread 2.3.4]
Base ROM's tried
Rogers 2.1 stock ROM
Generic X10a build 2.0.A.0.504
Generic X10i build 2.0.A.0.504
Baseband's tried
Base .52
J's custom .52
Base .49
Base .46
Mini-Boot versions tried
V1
V2
V3
Factory Unlocked No
-----------------------------------------------------------------------
Here is what I've been able to determine so far
Majority of X10a have Deep Sleep problems
Majority of X10i are able to obtain Deep Sleep in some way.
So far everyone reporting unlocked phones have deep sleep (Incorrect, some don't have deep sleep)
Possible solutions if you are having deep sleep issues
1. Install V2 or V3 of the mini-loader from the custom kernel thread (DoomLoRD) Link
2. Try the Screen Off Fix (9Lukas5) Link
3. Manually select your network operator. (The Gingerbread Man) Link
4. After fully charging the phone to 100%, reboot after disconnecting (DoomLoRD) Link
5. Un-check automatic updating in date & time settings. (Temoi19) Link
6. (My_Immortal) has a solution If it's the dialer keeping your phone awake. Link
#5 is what finally worked for me. If any of these fixes have worked for you make sure to thank whomever came up with it by following the link to their original post.
** BREAKING NEWS **
J has just posted in his CM7 thread.
small progress
weems that we have found the deep sleep issue
not shure for now but we will provide an baseband togherther with J003
this combination seems to fix deepsleep for all testers
ETA 24h to be shure
Click to expand...
Click to collapse
The new Rom release is now available in the second post here. The Kernel included does not include overclock so if you want overclock you'll have to download K012 from the first post.
Here are the known issues posted by J in his thread. Please note the items for Deep Sleep and make sure to apply them before reporting any deep sleep issues.
KNOWN BUGS
-after reboot USB mass storage is not working if USB in plugged (unplug/replug USB to fix)
-if you still have deepsleep bug disable autotime update and automatic network
-deepsleep appers only when device is not connected to USB and corect baseband is used
Click to expand...
Click to collapse
Nice one buddy, great idea, i do not suffer from deep sleep so will edit my post later with my results, do you want the date the phone was manufactured.
I ALWAYS HAVE HAD DEEP SLEEP.
*Sony x10i
*Type AAd-3880056-bv aaac
*FCC ID PY7A3880056 CB5
*IC 41708_A3880056 10w13
*manufacture date year 2010 week 13
Using 3UK, HSPA, i have tried only Jerpelea's roms and had deep sleep on every one, my generic rom used is Sony Ericsson X10i_2.1.A.0.435_X10i and i use J's bb52 but it works also for me on bb49/sony bb52.
My only other point is that my phone was factory unlocked which may be another good point.
For those that don't know how to tell the manufacture date its under the battery and is shown like mine as 10W12, 10 being the year 2010 and W12 is week 12 of that year so April.
Apps that are very active in background prevent my device from going to deepsleep. Like MSN Talk Pro, PowerAMP and idk what more. I dont think its hardware related.
Sent from my X10i using Tapatalk
smartgardens said:
Nice one buddy, great idea, i do not suffer from deep sleep so will edit my post later with my results, do you want the date the phone was manufactured.
Click to expand...
Click to collapse
Great idea!! Now just where would I find that info?
PlayGunsta said:
Apps that are very active in background prevent my device from going to deepsleep. Like MSN Talk Pro, PowerAMP and idk what more. I dont think its hardware related.
Sent from my X10i using Tapatalk
Click to expand...
Click to collapse
I've actually tried this from a fresh install, with only CPU Spy installed and still I didn't have deep sleep. I'm saying it's hardware related as it could just as well be provider related.
GreatBigDog said:
Great idea!! Now just where would I find that info?
Click to expand...
Click to collapse
No idea sorry, Doomlord should know, it is under the battery somewhere, iv'e looked but can not make it out.
Hi guys, no deep sleep, no matter what
Edit: i received from Tim-br...
X10a Sensuous Black
Mobile Phone GSM/GPRS/EDGE 850/1800/1900
UMTS/HSPA band 1/2/5/6
Type: AAD-3880074-AV AAAB
FCC ID PY7A388074 BY9
IC: 4170B-A3880074 10W21
This is my post in J's thread...
I'm trying to fix deep sleep issue since J release v21 final, but no success.
My steps:
* usual (wipe everything, install update.zip, BB from package.)
* v2 e v3 miniloader (one in each clean install)
* repair with seus (after that clean install of bb from package and rom)
*flash many se 2.1 firmware (after that clean install of bb and rom)
* clean install and bb .49.
*battery calibration (full charge "off line", wipe battery stats)
*applied patch "when screen off "
*no apps installed (in each installation, JUST CPU spy from market, without gapps.
*another formatted sdcard
*wifi set to "when screen off " or wifi disabled.
*GPS and bt disabled.
*tried adw or arc launcher
No DEEP SLEEP. (Just work with airplane mode active)
Sent from my X10 using XDA App
michaeljordam said:
Hi guys, no deep sleep, no matter what
This is my post in J's thread...
I'm trying to fix deep sleep issue since J release v21 final, but no success.
My steps:
* usual (wipe everything, install update.zip, BB from package.)
* v2 e v3 miniloader (one in each clean install)
* repair with seus (after that clean install of bb from package and rom)
*flash many se 2.1 firmware (after that clean install of bb and rom)
* clean install and bb .49.
*battery calibration (full charge "off line", wipe battery stats)
*applied patch "when screen off "
*no apps installed (in each installation, JUST CPU spy from market, without gapps.
*another formatted sdcard
*wifi set to "when screen off " or wifi disabled.
*GPS and bt disabled.
*tried adw or arc launcher
No DEEP SLEEP. (Just work with airplane mode active)
Sent from my X10 using XDA App
Click to expand...
Click to collapse
Can you edit your post please to add the information asked for in the first post. We are trying to find something in common between all of our phones.
GreatBigDog said:
I've actually tried this from a fresh install, with only CPU Spy installed and still I didn't have deep sleep. I'm saying it's hardware related as it could just as well be provider related.
Click to expand...
Click to collapse
Yes I tried the same earlier, its just a matter of finding something we have in common, what it is I don't know.
Ok guys just done some testing cm7.03 and disappointing results, atleast for me.
Flashed bb.49, wiped everything in recovery. Fresh install of v21 and flashed v2 miniloader (no reboot in between) and signed into Google, allowed it to sync contacts no Google restore, no gmail, skipped install of Google apps. I have only installed CPU spy through market. Nothing restored through titanium.
My SD card is being a SOB and for some reason thinks I have no pics on my card, so possible issue there so it wont allow me to upload the screenies I just took but I managed 9 seconds of deep sleep after leaving the phone alone after my install as described for maybe about 2 - 2.5 hours. Baseband.49 with v2 miniloader isn't the answer I'm affraid atleast for me. Tomorrow will try same kind of install but using v3 mini loader.
Edit; no luck sorry
Sent from my X10 using XDA Premium App
GreatBigDog said:
Can you edit your post please to add the information asked for in the first post. We are trying to find something in common between all of our phones.
Click to expand...
Click to collapse
Edited, my last post. I see small diferences between you and me.
i don´t remember what bb came with phone, but i gues was .46.
I´ll try that now....
.49 don´t fix deep sleep.
How come we havn't asked those with deep sleep working to make a nandroid backup from xrecovery and upload it so we all can try it out?
SkyStars said:
How come we havn't asked those with deep sleep working to make a nandroid backup from xrecovery and upload it so we all can try it out?
Click to expand...
Click to collapse
Good idea, worth a try, i will do one tomorrow if nobody has done it before, think i will just check with Jerpelea first if that's ok by him.
Edit .... I will just pm a few with it rather upload it.
Sent from my X10 using XDA Premium App
Great! let us know how that goes.
I guess I'm a bit behind on what this even is.. What is the deep sleep? I know sleep mode and hibernation on a PC, but how do I know if my phone has it or does it?
CPU spy from market
highaltitude said:
I guess I'm a bit behind on what this even is.. What is the deep sleep? I know sleep mode and hibernation on a PC, but how do I know if my phone has it or does it?
Click to expand...
Click to collapse
Sent from my X10i using XDA App
Deep Sleep is sort of like Stand-by mode on your PC, it will wake up by its own to sync mail and do whatever and then go back to sleep. Without deepsleep you will lose 5-10% battery an hour just idling instead of just 1% for every 5-10 hours.
GreatBigDog said:
I've actually tried this from a fresh install, with only CPU Spy installed and still I didn't have deep sleep. I'm saying it's hardware related as it could just as well be provider related.
Click to expand...
Click to collapse
Ok just tired another fresh install on bb.49 this time using miniloader v3. Same testing.g environment as mentioned in cm7 thread. It seems impossible for me.
Ok guys just done some testing cm7.03 and disappointing results, atleast for me.
Flashed bb.49, wiped everything in recovery. Fresh install of v21 and flashed v2 miniloader (no reboot in between) and signed into Google, allowed it to sync contacts no Google restore, no gmail, skipped install of Google apps. I have only installed CPU spy through market. Nothing restored through titanium.
My SD card is being a SOB and for some reason thinks I have no pics on my card, so possible issue there so it wont allow me to upload the screenies I just took but I managed 9 seconds of deep sleep after leaving the phone alone after my install as described for maybe about 2 - 2.5 hours. Baseband.49 with v2 or v3 miniloader isn't the answer.
Sent from my X10 using XDA Premium App
Does anybody have an unlocked phone that they could try a sim card from another provider with? I've tried a 2nd one from the same provider but my phone is locked so I can't try a different one.
cm 7.0.3 - bypass v3
I tried a different simcard today and got deepsleep on it but I also had deepsleep with my usual simcard until it hit 15 % battery. Maybe losing deepsleep had to do with coming out of airplane mode on my device. I couldn't restore it and tried everything written in the other thread.
I gave the hardware - software cause some thoughts. I don't think it is hardware related. Sony would never upgrade to GB if it would be hardware related but I remember they said that they had some trouble with GB and the kernel.
Anyways I use the same apps on J's GB that I used on freex10 and i have absolutely no problems with deepsleep. The problem must reside within the Kernel, bypass or GB since lots of people even get the no deepsleep on a fresh install or lose it after some time.
Also drivers are not complete like camera and proximity. I would guess that there are still lots of incompatibilities that could also be the cause for something like that. Maybe some piece of hardware doesn't get addressed right or something. Figuring out what would be the cause exactly is way out of my league.
Just some 5 cents from me.
Regards
No deepsleep here for the past 3 or 4 versions of J's kernel (didn't try any before that).
Phone info:
Code:
Sony Ericsson X10a
Type: AAD-3880074-AV ACAM
FCC ID: PY7A3880074 CB5
IC: 4170B-A3880074
MoP 1233-8309.10 SI 1237-4604
Manufacture Date: 10W33 (August 2010)
Made in China
Network info:
AT&T
HSPA
WCDMA preferred
(Sorry, don't know where to find the same network info you posted).
ROMs:
Only use Z's FreeX10 B4 - Hotfix 1 (with CM settings)
Basebands:
.49
.52
J's .52
Bootloader bypass versions:
V1
V2
V3
Running services:
Code:
XPERIA Flashlight; Process: jp.co.telemarks.ledlightx10
LedLightWidgetService
Digital clock; Process: com.sonyericsson.digitalclockwidget
DigitalClockService
Market; Process: com.android.vending
AlarmService
HTC_IME mod; Process: jonasl.ime
HTC_IME mod
Misc:
FreeXperia Recovery
I keep Wifi/3G turned off unless I am using them, so they shouldn't be causing an issues.
Not using any SetCPU profiles/task killers/OC APPS/UV APPS/UV modules
I do get deep sleep in airplane mode (only tested for 2 minutes, but that was 2 minutes more than I've gotten any other time).
Perhaps a radio is keeping the CPU running?
Related
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
benoitm974 said:
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
Click to expand...
Click to collapse
I have same problem in zombie panic kernel v 1.59 and v 1.61.
after i update to v 1.62, i don't had problem reboots. and everything it's ok.
Problem occurs usually when:
I use the phone for 10/15 minutes, that is running music or radio, or using the phone, like surfing and installing app from market.
I'll try the new 1.63 ...
Benoit
Sent from my U20i using xda premium
Hi, No reboots for me 4 days into 1.63+2.1, I did similar process only difference is I use clockworkmod, someone else will have to confirm but I remember a while back all the roms where coming out with "no longer supporting xrecovery". As said dont know might be nothing but everyone seems to use clockworkmod now for flashing.
Sorry assuming you used xrecovery to flash rom since you mention installing it.
Well strangely, the update to 1.63 did it, no more reboot and I can even OC the phone ! It works great no reboot, even with wavy usage of GPS navigation with CoPilot live over the week end ! this is perfect !
I only have an issue with the radio FM app which is buggy : sound start on the hp instead of head phone, favorite station are not kept, frequencies are written in green on black which is not visible and RDS name is overlapping frequencies ...
Another issue, I'm still not able to fine tune auto brightness to have good reactivity when phone get out of standb by on shiny day it take 1/ 1.5 second for the screen to detect it need to boost lightness ... Same when I'm in a call and I want to use the keyboard to dial, it takes 1/1.5 second for the phone to adjust brightness... I've tried several tutorial from forum but it still have this small lag in brightness reactivity.
Other the phone is now perfect to me in 2.3.5 ! Thanks very much slade87 ! One note I don't like the boot animation some less shiny would have been welcome ...
Cool you got it all working, yes there where instabilities with cross ROM/kernels.
I like the new bootanimation but you can allways change it out if you dont..
(update 7/7/11)[Boot Animation]more bootanim
Bootanimation Installer v3.3
I am writing in desperation.
My Xperia Active is about 3 months old.
It is the ST17a version but that has never made much difference to anything else.
It has been unlocked via testpoint method so warranty is not valid (plus they don't sell this phone in my country anyway).
Phone randomly reboots when it is not plugged in to power, especially when trying to bring the phone out of lockscreen standby, after using any GPS function or just unlocking the phone
The fact that this WILL NOT happen when plugged in to power is telling me perhaps it is a power management issue.
Things I have tried so far: COMPLETE REFLASH formatting all available mounts from recovery mode + format SD card and start fresh.
Combinations:
1.Spartan Rom 1.9.5 + non-oc kernel
2. Spartan Rom + Rage Kernel
3. Different baseband versions including original (56??), .66 and .62 (currently have .62 installed)
4. EX MIUI + ST17 satsuma kernel
Reboots still happen with all of the above configs
The problem started suddenly whilst using GPS SportyPal pro + Bluetooth music I have previously not had any problems in this area but now they will not stop.
I did not experience any reboots with CM9 but I did not stay in that rom very long as there was way too much stuff not working on my handset - it probably would have happened eventually. Sometimes I can get over half a day of usage without a reboot but then will get like 5 in a row.
I absolutely LOVE this phone but I bought it primarily for sports tracking and it keeps crashing and losing my workouts so I'm getting pretty pissed off.
If anybody can tell me what to look at to try and track this down I would really appreciate it. Checking logcats are no good because it will never reboot whilst plugged in to USB. Are there any other logs I should check???
OK - if not any help to identify the cause - can anyone comment on repair cost @ sony service center out of warranty?
Try fully stock 4.0.2.A.0.62 firmware, some other phones had issues with restarting all the time also, this firmware is known to fix this.
SOLVED - have carried out 5 days of testing.
I can confirm the latest version of MIUIex has addressed my reboot woes.
Have been running reboot logger 1.9 on the phone since then and have not had a single unexpected reboot. I am a happy camper.
Not sure if perhaps there is/ was a common driver or something that was causing these problems between a few of the up to date roms - I am just happy the issue seems to have passed for now.
And it's back. I switched back to Telstra, that means back to 850mhz band, reboots are back with vengeance. Might need to try and find a st17a specific Rom and radio.
bandario said:
And it's back. I switched back to Telstra, that means back to 850mhz band, reboots are back with vengeance. Might need to try and find a st17a specific Rom and radio.
Click to expand...
Click to collapse
Flash this via Flashtools: http://www.mediafire.com/?yvjnt0qctun9t6j
Is ST17a Specific ICS Firwmare. It contains ST17a specific baseband(radio).
Hope it helps
pastillero said:
Flash this via Flashtools: http://www.mediafire.com/?yvjnt0qctun9t6j
Is ST17a Specific ICS Firwmare. It contains ST17a specific baseband(radio).
Hope it helps
Click to expand...
Click to collapse
Wow, thanks!
Seems to have done the trick but now is back to vanilla flavour - seems the rooting process has gotten ridiculous lately, I wonder if it would be easier to pull this ftf to pieces and insert the radio detials etc into another rom file.
For now I guess I will use stock phone unrooted, at least it won't reboot.
THanks for your help!
i have also had that problem. I flashed the sti7a ics version and it is gone, after that you can use any rom without any prob.
bandario said:
Wow, thanks!
Seems to have done the trick but now is back to vanilla flavour - seems the rooting process has gotten ridiculous lately, I wonder if it would be easier to pull this ftf to pieces and insert the radio detials etc into another rom file.
For now I guess I will use stock phone unrooted, at least it won't reboot.
THanks for your help!
Click to expand...
Click to collapse
No prob..
You can flash any custom ROM you want, if it start rebooting again then get back to Stock..
Cheers
I had the same problem, it used to happen when signal was scarce or absent, i solved by getting a new sim card
Let me first explain what I did.
1. From stock rom, after doing the root (TWRP recovery), i flashed JellyDaemon v 2.0 listed here http://forum.xda-developers.com/showthread.php?t=2307247 . Used CPU control inbuilt in app to set CPU governer to OnDemand
Fantastic ROM with no problems.
2. After the news of 4.2.1 release came, I started looking for 4.2.1 based roms. I went with StarkHD listed here http://forum.xda-developers.com/showthread.php?t=2212028 . I think my download went wrong and file wasn't downloaded cleanly. I flashed with it. Flash went on successful. Phone got hung at the boot animation. Tried multiple methods to start the ROM. No success. Phone not booting into any ROM.
3. I had stock rom v 0.16 available with so flashed it with SP flash tools. Flash was successful.
4. Downloaded Naturewiz HD listed here http://forum.xda-developers.com/showthread.php?t=2319288 . ROM flashed and phone booted. Restored the apps. Used battery calibration app to calibrate the battery. After this, noticed that every time phone went into standby, it won't wake after that and needed reboot. I thought it to be bug in the rom.
5. Downloaded 4.2.1 based rom listed here http://forum.xda-developers.com/showthread.php?t=2306461 and flashed it. Flash was successful followed by successful TP upgrade. Installed everything. Same problem noticed. Phone won't wake from standby. Needed to be rebooted.
6. I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Any solutions to this? There are no other problems I am facing.
"I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Click to expand...
Click to collapse
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Sent from my CaNvAs HD using xda-developer app.
adizrox said:
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Click to expand...
Click to collapse
Thanks for your reply. I will try your suggestion and see. In the meanwhile, I removed TWRP and flashed CWM 6.0.3.0 and fixed permissions with that. The phone did not reboot on its own for close to eight hours (which it was doing earlier at random). I thought problem was solved. But trying to go through contacts list (DW Contacts), phone rebooted on its own.
Can anyone tell me a method where you do a clean install and bring the phone to a factory fresh state. Something similar to tutorial by team overcome for galaxy tab. Frankly, that seems to be the only possible solution: Get the phone in a completely formatted factory fresh state and then install any other ROM.
SP flash tools
To get your phone to a default factory status. you have to flash the original rom using SP tools. Links to both can be found in the forum.
Finally, tired after numerous attempts, decided to take it to the service center. Asked them to update to 4.2.1. They had the same problem. After flashing, the phone just wouldn't boot past the boot animation.
They kept trying. After two hours, they gave it back to me saying there is a hardware problem which requires a main board change.
I had suspected all along and now I know I was right. I asked them about the time line. The answer I got was even more shocking. Minimum two weeks, but there are lots of hand sets awaiting main board since more than a month
I guess I am better off with current status (Ver .20 installed and rooted).
Seriously, this episode has seriously dented my faith in micromax as a brand. One can buy there phones and be happy with whatever has been packaged. Trying anything new can be dangerous.
Hey everyone. redoing my thread now that we have tried alot of solutions, hopefully someone has a vague idea of what we can do to my phone lol.
So then, my phone (redmi note 3 snapdragon) refuses to go into deep sleep no matter what combination I've tried.
Tried Combos
1. RR+ radon and agni
2. Miui 8 stable and dev preview (7.1.5 and 8.1.1.0)+ stock, radon, and neon kernel (flashing using miflash with unlocked bootloader official)
3. Cm13 latest nightly+ radon, stock, and agni
4. Nitrogen os+ nagato kernel (current rom)
All combinations we're tried with clean installs (factory data, system,cache and internal storage)
Hardware methods tried
1. Physically disconnecting fingerprint sensor (goodix)
now then, with wakelock detector, we can see im troubled with a 99% awake time, along with 100,00's of event wakelocks over 6hours, now event wakelocks deal with the actual hardware of the phone from what i've seen, which makes little sense to me because the screenshot i am attaching was just over an entire night of not touching the phone. so why it has any activity is bizarre to me. so heres what we have tried so far on my previous thread.
Tried methods of fixing event wakelocks
1. Greenify, force doze, wakelock blocker and blocking everything in frustration. deep sleep battery saver.
2. physically deleting events one by one (going into dev/input/eventx (x being wakelocks 1-10) after deleting some my display eventually stopped working, most likely because i just deleted the event that controls the lcd i assume. rebooting fixed the problem and remade the events in their directory so no harm done.
3. removing zram usage figuring it was a thrashing problem (saw a thread in the hd desire of the same issue. didnt help sadly.
4. flashing modem in radon thread, ended up making my phones earpiece not work for calls and still had the wakelocks.
5. disabling gps, along with auto brightness and auto rotate
so then if anyone needs any other information just let me know, currently using an iPhone for the time being so im desperate lol. but still id rather fix and find the problem then go for returning the phone. better to solve a problem for future people in my shoes then just thrust it away is how i see it. also someone bug the strix and darkstrix about this maybe they know the solution. anyway thanks for reading and i hope we can fix my phone soon
^Update^ now using epic rom 7.1.12 from the xda thread, still got wakelocks on stock without any other apps.
I have same problem in all versions of stock MIUI Rom. I too tried all sorts of combination but the problem remains. Finally I'm using RR Rom 5.7.4 (20161113 build) + radon Kernel. My deep sleep problem have been solved (though not 100%). Now my phone looses very little battery in standby time like 1-2% over a night. Before RR Rom I tried many custom Rom but had same problem. If you have not tried the ROM (RR Remix 20161113) I've mentioned above give it a try. Best Of Luck.
Thanks rj I'll install and post logs after work. Fingers crossed that it fixes my problem.
use the rom android 6.0.1 with module powernap , u can fix it !!
http://repo.xposed.info/module/net.jzhang.powernap
Small update: testing stamina mod currently with xposed. ressurection remix will be next only because xposed seemed a bit easier lol
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Then once try nexus rom i am getting good battery life in this rom too.
rjrulz007 said:
Then once try nexus rom i am getting good battery life in this rom too.
Click to expand...
Click to collapse
surer rj which one?
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
That happens to me when background data enabled . when i disable backround data through data usage settings , the battery backup gets better, but sure my social apps wont sync.
It seems the wakelock come from android system itself , go check logcat and you will get messages like "ANDR_PERF_RESOURCES FAILED TO APPLY PERFORMANCE" , the likes of "decided to move IRQ from cpu0 to cpu1" , and the likes of "FPC listener : waiting..." , thats all that i notice and thats happening every single milisecond on every MM roms i have tried so far....
Well when i used miui 7 LL global didnt get that much messages on logcat , but its LL ...
I guess the problem is related to source code , i dont know .
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
D4xel said:
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
Click to expand...
Click to collapse
yes sir still nothing
rohit4kk said:
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
Click to expand...
Click to collapse
hey dont worry man you'll be the first when we find an answer lol
Zaccary said:
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Click to expand...
Click to collapse
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
deltatux said:
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
Click to expand...
Click to collapse
thanks for the tip but we are running on airplane mode only at this point just to make sure we don't have more things to worry about battery drain. i appreciate the information though ^_^
Mine kenzo, tried all miui version, always the same.
sbor-si said:
Mine kenzo, tried all miui version, always the same.
Click to expand...
Click to collapse
I'm not alone!!!
Hey hopefully we find an answer buddy
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
sbor-si said:
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
Click to expand...
Click to collapse
i believe last time i tried 7.3.2.0 it gave me constant reboots and lagged quite a bit. but i also heard it was the best for battery so i can try flashing through miflash again after work. im also going to be trying this rom here https://forum.xda-developers.com/re...nzo-lldlm18-1-3m866beta-real-factory-t3375250. since it uses edl mode instead of fastboot so hey maybe that will knock something lose?
Well, right now I'm trying to get it working - without luck. I can flash 7.3.2. with miflash via edl without troubles, phone started normaly, all seems good, until "No service" for gsm signal. Bad luck. I think that modem version from that old flash is not compatible with hardware.
But it looks so good - Android takes 20% and Android system 6%...
Hello!
Is it possible to install Lineage OS 14 on Xperia Mini pro?
If not, what is the latest Lineage OS version that is possible to install on Xperia Mini Pro?
Henrik Jansson said:
Hello!
Is it possible to install Lineage OS 14 on Xperia Mini pro?
If not, what is the latest Lineage OS version that is possible to install on Xperia Mini Pro?
Click to expand...
Click to collapse
CM12.1 (based on Android 5.1.1) should be the latest CM (or LOS) that Xperia Mini Pro support.
Ok, thanks!
Do you know where to download it, and if there is some step by step instruction somewhere on the internet how to install it.
Henrik Jansson said:
Ok, thanks!
Do you know where to download it, and if there is some step by step instruction somewhere on the internet how to install it.
Click to expand...
Click to collapse
Please head over to the DEV forum of this device. The thread is located the top several.
Sent from my D6503 using XDA Labs
Ok, where can I find "DEV forum"?
Xperia Mini, Mini Pro, Xperia Pro, Active, Live with Walkman Android Development
in legacy xperia you can download CM13 (android M). I´ve installed it in my xperia mini pro (mi only phone) and it´s enought stable for me to use it.
in my opinion, works much better than cm11
https://basketbuild.com/devs/AdrianDC/LegacyXperia/mango/LineageOS-14.x
How to install LineageOS 14.1 Rom (Android 7.1.2)
1. External memory card is required to install the rom (Ext4 only 1 partition). At least around 4gb, must be very fast (Class 10 u3), and should be at around 8gb if possible. All apps, data, etc will go here.
2. Flash boot.img (In fastboot mode).
3. Go wipe, swipe. Go advanced wipe and wipe system.
4. Go advanced --> sideload. Connect USB and type 'adb sideload rom-14.1-xxx.zip' & after type 'adb sideload opengapps-7.1-xxx.zip'
5. Reboot to system. Ignore any warning message.
Thanks for the mango link, but where is the boot. Img file ?
babaorum1973 said:
Thanks for the mango link, but where is the boot. Img file ?
Click to expand...
Click to collapse
Did you take a look inside lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip ?
Because I didn't test it yet: Are there any issues with this build (camera working)?
Just tried lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip and the installation overall was like described by Tromponauta.
The problem is that the touch screen is not responding within LOS. Everything else works (keyboard, camera etc.), just the touch screen seems to have problems. It works just fine inside TWRP and booting LOS for the first time it was responding for the first moment and then stopped (no response, like a frozen OS but the hardware keys still work). I've rebooted back inside TWRP to confirm the touch screen is working and it is.
Any ideas?
saljut7 said:
Just tried lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-mango.zip and the installation overall was like described by Tromponauta.
The problem is that the touch screen is not responding within LOS. Everything else works (keyboard, camera etc.), just the touch screen seems to have problems. It works just fine inside TWRP and booting LOS for the first time it was responding for the first moment and then stopped (no response, like a frozen OS but the hardware keys still work). I've rebooted back inside TWRP to confirm the touch screen is working and it is.
Any ideas?
Click to expand...
Click to collapse
There was a problem with my display cable. Changed the display and it works just fine now.
Just energy consumption seems to be very high. I bought a new battery which is listed as 100% for around 3hours and then drops down to 0% immediately.
saljut7 said:
Just energy consumption seems to be very high. I bought a new battery which is listed as 100% for around 3hours and then drops down to 0% immediately.
Click to expand...
Click to collapse
This problem is caused whenever a SIM card is inserted. Without SIM card the battery lasts a day as expected.
saljut7 said:
This problem is caused whenever a SIM card is inserted. Without SIM card the battery lasts a day as expected.
Click to expand...
Click to collapse
Its probably your phone hardware problem. I'm running CM14.1 on two mango phones.. without gapps and everything works .. well.. one of them have occasional freeze problems I'm struggling to diagnose, so removing battery is required from time to time to reboot it.
Anyway sim card works fine on both phones with normal battery use.
ROM is quite fast (maybe faster then CM11) but I'm using A1 sd card and no gapps ..
btw I also had some freezing problems on this phone when on other ROMs so maybe its hardware..
Its certainly worth giving CM14.1 try (as per other post earlier on)
EvilMonkey88 said:
Its probably your phone hardware problem. I'm running CM14.1 on two mango phones.. without gapps and everything works .. well.. one of them have occasional freeze problems I'm struggling to diagnose, so removing battery is required from time to time to reboot it.
Click to expand...
Click to collapse
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
EvilMonkey88 said:
Anyway sim card works fine on both phones with normal battery use.
Click to expand...
Click to collapse
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
EvilMonkey88 said:
ROM is quite fast (maybe faster then CM11) but I'm using A1 sd card and no gapps ..
btw I also had some freezing problems on this phone when on other ROMs so maybe its hardware..
Its certainly worth giving CM14.1 try (as per other post earlier on)
Click to expand...
Click to collapse
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
saljut7 said:
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
Click to expand...
Click to collapse
On main mango I get between 12-18 hours depending on use.. (its mostly light though.. messengers, emails, phone calls, etc not much browsing) so battery drain is same ish as other ROMs I tried..
2nd mango with CM14.1 works as alarm clock and sometimes squeezebox controller. mostly on airplane mode which gives over week battery life.. (no sim on that one)
3rd mango is on stock gingerbread converted into dashcam .. I get about 6-7 hours battery with HD recording on Daily Voyager (had to use tasker to turn off screen during recording though)
Got two more of those little buggers but sadly as spares now.. (broken screens)
Everyone tells me I'm mad to still use mini pro.. but I really like small phone with great keyboard.. (by today standards I should say tiny phone lol)
Once a while I consider buying new phone but haven't actually done it yet lol
Yes! +1 Thank you devs for all your work on xperia phones!.. Cheers
p.s I'm still hopeful for Android Go one day
Awesome... well I sitll doubt that my battery drain has something to do with the hardware. As far as I remember the battery life was already not very good when I was using the original Android for 2-3 years. My current battery is now at least 5 years old so I think the current battery capacity is quite okay. Before I had a Motorola xt894 with a Cyanogen Mod experimental/snapshot and the battery life was horrible in comparison to the standard Rom so I think it has something to do with a not optimized LOS.
btw: Did you experience any Wifi issues connecting to public Hotspots? Sometimes I have the problem that I can not connect to public hotspots that worked yesterday. The Wifi list says "saved" to the specific Hotspot after I tried to connect (insteadt of "connected").
saljut7 said:
I've experienced this as well but I doubt this has something to do with the hardware (except the fact that the hardware is maybe just too outdated to handle a current LOS and current apps).
Is there really no effect on battery drain if the ROM was not optimized for certain country GSM settings?
Yes, the sk17i is still a great peace of hardware for me used as "walkman" and for instant messaging. I'm very thankful that the sk17i is still suppoprted, thanks to all devs involved!
Click to expand...
Click to collapse
saljut7 said:
Awesome... well I sitll doubt that my battery drain has something to do with the hardware. As far as I remember the battery life was already not very good when I was using the original Android for 2-3 years. My current battery is now at least 5 years old so I think the current battery capacity is quite okay. Before I had a Motorola xt894 with a Cyanogen Mod experimental/snapshot and the battery life was horrible in comparison to the standard Rom so I think it has something to do with a not optimized LOS.
btw: Did you experience any Wifi issues connecting to public Hotspots? Sometimes I have the problem that I can not connect to public hotspots that worked yesterday. The Wifi list says "saved" to the specific Hotspot after I tried to connect (insteadt of "connected").
Click to expand...
Click to collapse
hmm maybe you could try battery calibration? or "new" battery.. those are very cheap. seriously no excessive drain here on LOS.. managed 19hours and 10% left today..
no experience of public wifi problems.. but I don't really use them tbh
My main problem with LOS is random freeze when display wont wake up (even when notification is working and background menu lights).. sometimes phone is OK for few days but other times it can freeze few times a day. I keep changing settings in kernel auditor but cannot find out cause yet.. for a while I had suspicion freezes are more likely when using build in browser.. but maybe it was just coincidence
EvilMonkey88 said:
sometimes phone is OK for few days but other times it can freeze few times a day.
Click to expand...
Click to collapse
My sk17i lists errors like
System UI has stopped
com.android.phone has stopped
Settings has stopped
and is always rebooting / in a boot loop. I wanted to reinstall LOS but somehow my whole system seems to be read only. I've already tried https://forum.xda-developers.com/droid-turbo/help/accidently-selected-read-twrp-how-undo-t3312533 but everytime I access TWRP after a reboot "Mount" -> "Mount system partition read only" is checked. I tried to reinstall TWRP with
Code:
fastboot flash boot boot.img
but this doesn't affect the checked "Mount system partition read only" setting so I think TWRP is not reinstalled. Any idea how to fix this? In the end I just want to start over with a new installed LOS.
saljut7 said:
My sk17i lists errors like
System UI has stopped
com.android.phone has stopped
Settings has stopped
and is always rebooting / in a boot loop. I wanted to reinstall LOS but somehow my whole system seems to be read only. I've already tried https://forum.xda-developers.com/droid-turbo/help/accidently-selected-read-twrp-how-undo-t3312533 but everytime I access TWRP after a reboot "Mount" -> "Mount system partition read only" is checked. I tried to reinstall TWRP with
Code:
fastboot flash boot boot.img
but this doesn't affect the checked "Mount system partition read only" setting so I think TWRP is not reinstalled. Any idea how to fix this? In the end I just want to start over with a new installed LOS.
Click to expand...
Click to collapse
Hmm not sure what to suggest as haven't experienced this. In my case everything went smooth on 3 different phones (sk17i) when following instructions from other post:
https://basketbuild.com/devs/AdrianD...LineageOS-14.x
How to install LineageOS 14.1 Rom (Android 7.1.2)
1. External memory card is required to install the rom (Ext4 only 1 partition). At least around 4gb, must be very fast (Class 10 u3), and should be at around 8gb if possible. All apps, data, etc will go here.
2. Flash boot.img (In fastboot mode).
3. Go wipe, swipe. Go advanced wipe and wipe system.
4. Go advanced --> sideload. Connect USB and type 'adb sideload rom-14.1-xxx.zip' & after type 'adb sideload opengapps-7.1-xxx.zip'
5. Reboot to system. Ignore any warning message.
Click to expand...
Click to collapse
maybe sd card is corrupted, have you tried different one..?
Try wipe plus format everything and try again?
So does sideload completes fine and then you got error and bootloop?
Out of interest what ROM have you had before?