Related
I recently flashed CM11 from stock firmware on my Xperia M from the thread: http://forum.xda-developers.com/showthread.php?t=2584956
Shortly after that, I noticed my standby time of the phone reduced from 2-3 days on official firmware to just about 16-18 hours, which is odd, because the official firmware is more bloated than CM.
I notice that most of the battery is taken by "Android System" and "Mediaserver". Is there any script/tweak that could help?
Thanks in advance.
Try the reincarnation engine in the original android section of the xperia m. If that doesn't help, then try the greenify app from the play store
Press Thanks If I Helped!!
Get rid of FXP
paper13579 said:
Try the reincarnation engine in the original android section of the xperia m. If that doesn't help, then try the greenify app from the play store
Press Thanks If I Helped!!
Click to expand...
Click to collapse
Remove FXP and change back to stock rom asap. There is an issue with the rom. Corrupting internal partition
lanthrax said:
Remove FXP and change back to stock rom asap. There is an issue with the rom. Corrupting internal partition
Click to expand...
Click to collapse
corrupting internal partition? can u show us the proof....please dont spread rumors ..this is very bad...devs are working very hard to get cm11 stable as possible...
Sorry for my vague comment
ansebovi said:
corrupting internal partition? can u show us the proof....please dont spread rumors ..this is very bad...devs are working very hard to get cm11 stable as possible...
Click to expand...
Click to collapse
I have been using Cm11 since Mr Pecan started working on it. I am a big fan of the developers working on this project. However, i believe there is bug with the FXP rom (latest versions)
Please check
http://forum.xda-developers.com/showthread.php?t=2756223
There are several other threads with the same issue. All of these bugs have started with FXP 17 and onward. I am sorry for the vague comment earlier. But, please do proceed with caution. I have no phone for use now . I have no issues with that, since i knew the risks of using custom roms before hand. However, i would like to give people using these roms a heads up
lanthrax said:
I have been using Cm11 since Mr Pecan started working on it. I am a big fan of the developers working on this project. However, i believe there is bug with the FXP rom (latest versions)
Please check
http://forum.xda-developers.com/showthread.php?t=2756223
There are several other threads with the same issue. All of these bugs have started with FXP 17 and onward. I am sorry for the vague comment earlier. But, please do proceed with caution. I have no phone for use now . I have no issues with that, since i knew the risks of using custom roms before hand. However, i would like to give people using these roms a heads up
Click to expand...
Click to collapse
You bricked your device because you might have flashed boot.img immediately after unlocking the bootloader, you should have booted it up with unlocked bootloader first, so it could wipe all data in proper sequence. You can flash STOCK FTF using FlashTool. That's what I did.
49645986 553
Just a question guys, which one should I use: Reincarnation Engine or Fly-On Mod?
Sir , you are mistaken
tyus2 said:
You bricked your device because you might have flashed boot.img immediately after unlocking the bootloader, you should have booted it up with unlocked bootloader first, so it could wipe all data in proper sequence. You can flash STOCK FTF using FlashTool. That's what I did.
Click to expand...
Click to collapse
Sir,
You must understand, I have been using Cyanogenmod for 3 months now. I have been regularly updating the phone to the latest FXP. this problem occurred suddenly when the phone was already in running state.
Reincarnation Engine helps guys, but only extends battery by 2-3 hours. Did anyone try Fly-On Mod?
try using wakelock detector, it can help you find what is causing the battery drain. There was a recent issue with google play services keeping the phone awake continually, I fixed it by rebooting
No, as I already posted in OP, the most battery drain is caused by "Android System". The battery lasts maximum 8-10 hours, and once I went to official, it lasted about 24-28 hours. The most of the battery drain is caused in standby mode, which is weird. I will try Fly-On mod and report.
Hi all,
I have had used CM on my z1c since August 2014 and did updates with nightlies quite regularly without any issues. But last Friday, after I updated from
cm-12.1-20150925-NIGHTLY-amami to
cm-12.1-20151002-NIGHTLY-amami
my wifi problems started. Whenever it reconnects to the wifi I see the exclamation point next to the icon, then it disconnects again. It also shows the exclamation point next to the mobile reception icon. But I seem to have mobile data connection via the mobile phone provider. However, wifi is broken, resolving domain names doesn't seem to work.
I cannot downgrade to the last working version either because whenever I try to do that using Cyanogenmod recovery, the phone is stuck in the boot animation for hours so I had to give up.
In addition, I cannot activate bluetooth anymore. Whenever I switch it on, it switches itself off after a few seconds.
Does anyone have an idea what the problem might be and how to fix/debug/investigate this any further? Where do I start looking? Any help would be greatly appreciated.
Thanks!
BTW: forgot to mention: I'm on cm-12.1-20151004-NIGHTLY-amami now but problem remains the same.
miir01 said:
Hi all,
I have had used CM on my z1c since August 2014 and did updates with nightlies quite regularly without any issues. But last Friday, after I updated from
cm-12.1-20150925-NIGHTLY-amami to
cm-12.1-20151002-NIGHTLY-amami
my wifi problems started. Whenever it reconnects to the wifi I see the exclamation point next to the icon, then it disconnects again. It also shows the exclamation point next to the mobile reception icon. But I seem to have mobile data connection via the mobile phone provider. However, wifi is broken, resolving domain names doesn't seem to work.
I cannot downgrade to the last working version either because whenever I try to do that using Cyanogenmod recovery, the phone is stuck in the boot animation for hours so I had to give up.
In addition, I cannot activate bluetooth anymore. Whenever I switch it on, it switches itself off after a few seconds.
Does anyone have an idea what the problem might be and how to fix/debug/investigate this any further? Where do I start looking? Any help would be greatly appreciated.
Thanks!
BTW: forgot to mention: I'm on cm-12.1-20151004-NIGHTLY-amami now but problem remains the same.
Click to expand...
Click to collapse
You didn't happen to flash M5 kernel, did you? I've read that it breaks WiFi on latest night lies. Besides that, I've read about various people having troubles with WiFi and BT on some CM Roms, but I haven't experienced it myself. Look through the CM 12.1 thread in 'original development' forum for fixes, etc.
I can confirm that all nightlies from cm-12.1-20150929-NIGHTLY-amami.zip to cm-12.1-20151004-NIGHTLY-amami.zip have issues with wifi and bt.
Currently it is not possible to get an older version than 20150929 from CM servers.
Does anyone have a link to cm-12.1-20150925-NIGHTLY-amami.zip ?
pr3ddi
levone1 said:
You didn't happen to flash M5 kernel, did you? I've read that it breaks WiFi on latest night lies. Besides that, I've read about various people having troubles with WiFi and BT on some CM Roms, but I haven't experienced it myself. Look through the CM 12.1 thread in 'original development' forum for fixes, etc.
Click to expand...
Click to collapse
Thanks for the hint. Will search for more info in the forum. :good:
However, how would I know if I flashed a M5 kernel? I definitely wasn't aware of flashing it. My current kernel version is 3.4.0-cm-g1e19761
pr3ddi said:
I can confirm that all nightlies from cm-12.1-20150929-NIGHTLY-amami.zip to cm-12.1-20151004-NIGHTLY-amami.zip have issues with wifi and bt.
Currently it is not possible to get an older version than 20150929 from CM servers.
Does anyone have a link to cm-12.1-20150925-NIGHTLY-amami.zip ?
pr3ddi
Click to expand...
Click to collapse
I still have the package for cm-12.1-20150925-NIGHTLY-amami.zip on my phone. But can't downgrade to it because after flashing it, my z1c is stuck in the boot animation. I have waited at least 3 hours before I gave up and reflashed the newer version.
EDIT - sorry, link's dead. I should've checked it first. I would also be interested in trying an older build.
Does this help?
https://download.cyanogenmod.org/get/jenkins/127851/cm-12.1-20150928-NIGHTLY-amami.zip
Did anyone test cm-12.1-20151008-NIGHTLY-amami.zip ?
Changelog says that wifi and bt problems have been fixed.
www . cmxlog . com/12.1/amami
jira . cyanogenmod . org/browse/NIGHTLIES-1877
Giulio Cervera added a comment - Yesterday 4:28 AM
this was 2 issue:
1) the channel bonding
2) taimport was running with wrong timing, and BT and wifi mac address was not exported in /data/etc
fix for both is merged
Click to expand...
Click to collapse
pr3ddi
Just installed 20151008, I had been having major issues with wifi EAP previously (think i was on a MAY2015 build), this build's looking a lot better. The app launcher is alphabetized, and toast notifications have an icon from the app that generated them. I haven't tried bluetooth yet - my previous build was very bad with BT, I'm hoping this one's better.
Running 20151010 for over 6hrs now ...
wifi and bt are running stable and it looks like the issues have been resolved
pr3ddi
same problem
Same problem on my z1 with latest 20151010 any help please ? am using the normal z1
Good morning guys, I'm Italian and I'm new on the forum. I'd like to flash the cm12.1 on my device but i can't find a changelog about bug. Can you tell me the usual bugs or if I can use safely this rom without problems? Thank's a lot, and excuse me for my bad english
iSpammer said:
Same problem on my z1 with latest 20151010 any help please ? am using the normal z1
Click to expand...
Click to collapse
Not sure, no idea if they share the same hardware etc?
I've found battery life is a LOT better in this build too. AudioFX still having its moments though.
---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------
ULT][MO said:
Good morning guys, I'm Italian and I'm new on the forum. I'd like to flash the cm12.1 on my device but i can't find a changelog about bug. Can you tell me the usual bugs or if I can use safely this rom without problems? Thank's a lot, and excuse me for my bad english
Click to expand...
Click to collapse
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.[/QUOTE]
I saw a new build released today and yesterday, but I haven't rooted my device and can't install twrp or cwm.
I tried to install "XZDualRecovery] PhilZ Touch & CWM & TWRP" with no root mode, but nothing is changed
ULT][MO said:
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.
Click to expand...
Click to collapse
I saw a new build released today and yesterday, but I haven't rooted my device and can't install twrp or cwm.
I tried to install "XZDualRecovery] PhilZ Touch & CWM & TWRP" with no root mode, but nothing is changed[/QUOTE]
I'm using TWRP for my recovery. I believe you'll need to get an unlock code from the sony website for your phone before you can start rooting/flashing.
How to install (and root) Z1C
known issues for CM12.1 on Z1C
Note that my phone has experienced random reboots, about once or twice a day with CM21.1-20151008.
I tried to flash recovery in every mode God has invented but nothing: when I open flashboot i have evry time the same fu**ing message
"sending 'recovery' (8778 KB)...
OKAY [ 0.557s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.561s"
bootloader is unlocked, installed flashtool and relative drivers
Please guys help!
Sorry if I've posted in wrong place
Solved: I've repeated bootloader unlock procedure reported by Sony. Seems ok now
Has anyone trie 10132015 build if wifi is fixed?
amnher said:
Has anyone trie 10132015 build if wifi is fixed?
Click to expand...
Click to collapse
I tried, not fixed. For me wifi it's essential
Hello everyone,
I recently installed LineageOS 14.1 on my Nexus 5, but I am stumbling upon some issues that are really bothering me. To start off, it does not have the theme engine like CM13 I had previously, and apps such as Snapchat are not working. I have been searching for a fix but nothing really explains why it does not work. Apparently, Snapchat does not work on rooted devices but mine is not rooted - I simply have an unlocked bootloader (obviously) and a custom recovery and a custom ROM, but no root. My question is: is there a fix for this issue and, if not, can anyone tell me where I can download CM13 since the CyanogenMod website is no longer active or if LineageOS has an equivalent OS version for the Nexus 5?
Thanks in advance,
Cheers
Same error
Hi !
I had the same error for a week and i tried many things about root ( root swich,..) it doesn't seem that root access ils the problèmes.
I hope someone could help us !
Thank you !
PS sorry for bas english
Hi Guys/Girl
so iv been a fan of the Xperia projects and tinkering out there for the Sony Xperia S models
and i have tried bunch of them.
the problem i have been facing is something i cant find anywhere so i was wondering if anyone could help me or shine a light on whats wrong with my lil Hardware that could
The problem:
after i jumped from 5.1 android to 6.0 i had to partition it and do a bunch of stuff i don't fully understand (basically following a guide blindly ) and wallah i got marshmallow running on my phone, but i started noticing some bugs which is normal i suppose giving the circumstances that im using Custom Roms, so i sorta gave up on it for a bit , now iv been tinkering with it again and it seems no matter what Rom i use or what android versions.
it always gives me error messages if i don't have gapps installed i get:
masquerade has stopped
- with gapps -
nothing google related will work and i get
google services has stopped
does anyone have any clue what could be at fault
my sneeky suspicion is that it has something to do with when i was partitioning it
from a huge fan
Palli
Btw: sorry if my English isn't 100% :silly:
I have the same issue too
I hope to find a solution
THIS IS A SOFTWARE PROBLEM, DO NOT POST REGARDING ANYTHING HARDWARE RELATED!
My phone is perfect in condition and has no hardware defects. This only happens on certain ROMs, mainly Lineage OS, I didn't have this happen while I was on AOSPA 7.2.3 and it started as soon as I switched back to Lineage OS. If you post about this being a hardware problem I will laugh at that and not reply.
I've had this going on since Lineage OS began.
I go to turn my phone off, and it instantly starts rebooting.
When I click on the keyboard options in settings it instantly reboots.
I have magisk, busybox installed, using substratum themes, hebf optimizer & adaway. If any of these could cause this please let me know why and how.
These same things happen also on my Shield K1, also running Lineage OS 14.1 with the list of things above on it too.
Thanks.
Techie Android said:
THIS IS A SOFTWARE PROBLEM, DO NOT POST REGARDING ANYTHING HARDWARE RELATED! My phone is perfect in condition and has no hardware defects. This only happens on certain ROMs, mainly Lineage OS, I didn't have this happen while I was on AOSPA 7.2.3 and it started as soon as I switched to Lineage OS...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within one of the following Official LineageOS threads for your device.
https://forum.xda-developers.com/showthread.php?t=3543489
https://forum.xda-developers.com/showthread.php?t=3526394
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I started getting this last week (I think it's the same as the OP). Reboots randomly for any reason at any time in any app. I've had LineageOS 14.1 Osprey running for almost 2 years and on 2 different Sony Xperia Z2's. The problem does not present in safe mode, so for sure it's some kind of [new] incompatibility. No new software that would indicate the source of the issue. And it still does it even if I stop all but the most essential processes. I'm actually here on XDA because I intend to just wipe the device and start clean (doing a backup as I type). But then I saw this post. I'll do some more searching, but if anyone knows wtf, please shout out!
I'm facing the exactly same issue with my Lenovo Vibe K6 w Lineage 14.1.
My phone soft resets everytime I try to open de restar menu or try to change the keyboard.
Anyone got a solution to this bug?