Ive been running CyanogenMod V4.0.4 for a while now with No problems
last night I decided to Install a theme with the CM updater and went with Dark Dream
everything seemed fine till about 12 noon today
In those 2 hours I lost 3g and can only get on edge
Rebooting fixed this for a short while. Then it was stuck on edge again
rebooting took forever and it was still stuck on edge.
then the phone rebooted itself about 3 times randomly
Now i cant get the phone to boot past the G1 screen
any ideas? I do have a nandroid backup from last week and even though thats easy I am hoping i dont have to do that
Thanks in advance
I forgot to add that it is the latest stable release of the theme from the CM updater
and i cant boot into recovery mode, it is just stuck on the G1 screen
basically, if you flash a theme, and then want rid of that theme, you flash over the current cm your running. so if you still have it, try flashing it over the top.
if not, nandroid restore.
double. pardon my dust
p.s there is a new cyanogen mod out, id upgrade to that if i were you.
isnt the newest CM still experimental ?
at any rate My phone is stuck on the G1 screen and i cant get into recovery
Ok, went away while the Phone was stuck on the G1 screen
battery died in a hurry, plugged it in and it booted fine
Still on edge but once charged ill see if i can get a better signal
I guess I like the theme enough to give it another try as i dont see anyone else with these issues
and for the record i did try the latest CM experimental build 4.1.999
and it was BLAZING fast. the only reason i went back to 4.04 is because I couldnt get my browser and market working even with a wipe following the CM steps
I may try to wipe the SD card and re do the partion if things are still not stable with the theme and 4.0.4 .. thank god for nandroid haha
Yea- this doesn't surprise me, as that theme messed up my phone bigtime- try to pull the battery, do a "recovery boot" when you put it back in, and see if you get there after that- chris
Hmm, well the phone seems fine for now
but you have me wondering if it will happen again
I couldn't get the phone to go into recovery, I think i got lucky after waiting a while
I guess I will look into re doing the partion and trying 4.1.999 again
I really loved the speed and smoothness and if i can get market and the browser working like everyone else it will be great. i can wait on bluetooth to work as i dont use it much lately
this should be in the Q&A thread
but anyways i would flash cyans latest release if i were you
I don't understand. This theme works fine for me! Never had any trouble with it.
Just like when some people have an issue with a rom that others dont
I imagine it could be any number of reasons.
now i am running 4.1.9.9 and though i had issues with the phone turning off and freezing on the G1 screen it hasnt happened in 4 days and i havent done a thing
You have to remember that sometimes the .zip files simply get errors for some reason. If you read around you will find a number of people who try and install only to get an error, then then restore via nandroid and re-download the file and re-apply and it works. If you are using the browsers google chrome, Safari, or EI, I would say switch to firefox when it comes to downloads of .zip files. I have noticed that I have 100x more errors when not using firefox.
i had dark dream on 404 before and it slowed my phone down so much i didnt even care for the theme anymore. seems all cyanogen roms WITH a theme die. except his his older ones.
Hi,
I trawled threads and guides before starting my upgrade from CM7 to CM9. Thought I had everything in order so set-off. Ended up in a bootloop when I was done. Managed to get the phone sort-of working by installing my previous CM7 zip. I installed just the CM9 file over that and it started working....to a point. It wouldn't take the ICS gapps but did take an older version which at least has my mail and contacts working but I can't get into Play and get regular errors for basic stuff, like clock etc.
I've tried what I can but am now plain stuck and could really do assistance. I'm comfortable with the install procedure (I think!) although realise now that I cocked up my back-up first time round. Have to live with that now. Just want to get to a functioning ICS install.
These are files running right now.
CM9-NIGHTLY-120329-Defy
gapps-20111128
Honestly can't remember which kernel is running now, and confused which should be running. 95% confident that mine is a red lense but never seen another to compare.
CM9_Kernel-signed
CM7_Kernel-signed
These gapps didn't seem to work.
gapps-ics-20120317-signed
gapps-ics-4.0.3-20111217
I'm UK based with a regular Defy. I followed the guide and links (also pulled files from elswhere when the probs kicked in) in here.....http://forum.xda-developers.com/showthread.php?t=1386680
I have posted the problem in there but not sure it's the best place. I'll put a note in there to say I've started a thread. Don't want to upset anyone by double-posting!
Did I mention that I really could do with some guidance?!!!
Gobsheen said:
Hi,
I trawled threads and guides before starting my upgrade from CM7 to CM9. Thought I had everything in order so set-off. Ended up in a bootloop when I was done. Managed to get the phone sort-of working by installing my previous CM7 zip. I installed just the CM9 file over that and it started working....to a point. It wouldn't take the ICS gapps but did take an older version which at least has my mail and contacts working but I can't get into Play and get regular errors for basic stuff, like clock etc.
I've tried what I can but am now plain stuck and could really do assistance. I'm comfortable with the install procedure (I think!) although realise now that I cocked up my back-up first time round. Have to live with that now. Just want to get to a functioning ICS install.
These are files running right now.
CM9-NIGHTLY-120329-Defy
gapps-20111128
Honestly can't remember which kernel is running now, and confused which should be running. 95% confident that mine is a red lense but never seen another to compare.
CM9_Kernel-signed
CM7_Kernel-signed
These gapps didn't seem to work.
gapps-ics-20120317-signed
gapps-ics-4.0.3-20111217
I'm UK based with a regular Defy. I followed the guide and links (also pulled files from elswhere when the probs kicked in) in here.....http://forum.xda-developers.com/showthread.php?t=1386680
I have posted the problem in there but not sure it's the best place. I'll put a note in there to say I've started a thread. Don't want to upset anyone by double-posting!
Did I mention that I really could do with some guidance?!!!
Click to expand...
Click to collapse
To install ICS from scratch first make a backup of evrything you would like to hae later and then refer to the below mentioned link and install ICS:
How To Flash ICS(Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install ZIp from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash CM7 Kernel
7:Clear Cache and Dalvik Cache
FIrst Boot will take some time...
Click to expand...
Click to collapse
Ref: http://forum.xda-developers.com/showthread.php?t=1432100
Hope this helps!!
Thanks,
I'll have a good look through that thread tonight. I thought the CM9 kernels were the right one for my red lense defy......?
Should I just leave installing the Gapps zip until after everything else is done? I assume using one of the ICS gapp files is fine?
I installed they Defy+ nightly by Quarx:
http://quarx2k.ru/cm9-nightly-defy+/CM9-NIGHTLY-120330-Defy+.zip
This should already contain the GB kernel right? I flashed it anyway, just to be sure.
I have the Red Lense Defy, it's detected as a Defy+ now and the camera works.
HOWEVER, i had to flash the 'Batter fix for Red Lense', see first post here http://forum.xda-developers.com/showthread.php?t=1432100
This actually caused me a few hours sweat, since i did not flash it at first and then thought my battery was dead. It went empty after an hour or so, and then there was this battery you see when it's charging when then phone is powered 'off', with a big question mark within the battery -- and it would not boot!
I could get into recovery, but once i unplugged it from the power cable it went off shorty after and i did not have the battery fix on the SD card. For some reason i was only able to enter recovery when the usb was only charging, once it was a 'data' connection it would not turn on or turn off quickly. If i turned off my laptop and used the offline charge feature it would power on, however i could not copy over any files I had no microSD -> SD adapter to use my SD card reader.
Finally, having it on power only, I started into the bootloader (power on + Vol+), which also said low power (more fear of a broken battery). After a minute or so, it terminated itself and began to boot CM9 flawlessly. I was able to copy the battery fix from my webserver onto the sdcard. Flashed it. Battery detected again and charging like it should *phew*
This should be stressed A LOT more in the HOWTOs, i was not able to post to the CM9 dev thread yet (<10 posts). Maybe someone can.
Besides all that, it runs really nice now. Overclocked it to 1.3GHz and lots of things run quite smoothly, can't wait for full HW-Acceleration
It worked!!!
Thanks for your help guys. Flashed it as a Defy+ and all seems fine. Pity my main sd card seems to have crapped out during the mess so hoping I'll be able to get my files off it. But, the phone works again!
Gobsheen said:
It worked!!!
Thanks for your help guys. Flashed it as a Defy+ and all seems fine. Pity my main sd card seems to have crapped out during the mess so hoping I'll be able to get my files off it. But, the phone works again!
Click to expand...
Click to collapse
Congrats!!
You may use any data recovery software to retrieve the files ....
Thanks,
One thing I've noticed is that I've never had a 'H' signal since upgrading. It stays on 3G even in areas where I would have had a solid 'H' before. I double checked my APN & it's fine.
Any ideas?
Hey Folks, I need your help. I've got an ATT GS3. I've got intermediate skills with root/ROM activity, but have gotten in over my head.
After many months of bouncing around AOSP ROMs I decided to go back to TW based b/c I have had rebooting issues ever since CM went to 4.3.
I went from Carbon to Hyperdrive. It never would finish "activating" so I moved to Dandroid. It seemed fine. I restored from TB and got things setup. Everything seemed fine. I left it on the charger and after a couple hours I went to get it and see it locked up at the 'Samsung Galaxy SIII' screen you see right after power on button. I figured the ROM had issue and would try something else.
TWRP seemed to still work until I noticed that it could not mount any internal memeory, though it could mount/navigate the ext SD card. On the chance TWRP was messed up I tried a flashable recovery replacement from TWRP to CWM. The flash seemed to think it was good, but a recovery reboot still showed wonky TWRP. Next I tried to ODIN back to original OEM FW. Odin stopped with 'Fail (write)'.
I'm not sure what to do here as it seems the internal memory is just not there. I've searched for similar condition w/o luck. It is so strange that it was working fine for about 12hr on Dandroid and then just gone.
Anyone have an ideas?
Always a good idea to save anything u want to keep from the internal storage and wipe it also when going from aosp based roms back to tw...
After chasing this for many more hours it seems I'm screwed. My best assessment of the situation is that I've got "sudden death", which is a failure of the EMMC chip.
The fix can be done by these guys for about $150.
That's about all the phone is worth now so I guess I'm phone shopping for something new. Probably Note3 or Nexus 5. I've got my SIM in my old N1 and will slum until the Nexus5 announcement and make a decision then. It better be quick b/c the N1 is hard to swallow coming from GS3.
I've enjoyed the S3. Thanks to the devs for all the great ROMs.
[email protected] said:
After chasing this for many more hours it seems I'm screwed. My best assessment of the situation is that I've got "sudden death", which is a failure of the EMMC chip.
The fix can be done by these guys for about $150.
That's about all the phone is worth now so I guess I'm phone shopping for something new. Probably Note3 or Nexus 5. I've got my SIM in my old N1 and will slum until the Nexus5 announcement and make a decision then. It better be quick b/c the N1 is hard to swallow coming from GS3.
I've enjoyed the S3. Thanks to the devs for all the great ROMs.
Click to expand...
Click to collapse
I had the same problem tonight, but git it back. I flashed TWRP 2.6.1.0 d2att with Odin 3.06. Then from TWRP I flashed a stock rom.
Can you detail how to flash recovery with Odin?
EMMC failure. At best you'll be able to prolong the life a bit but you'll likely encounter issues no matter what. That's the most probable cause of your reboots, too.
[email protected] said:
Can you detail how to flash recovery with Odin?
Click to expand...
Click to collapse
Sure, Open Odin as Admin, load TWRP-2.6.1.0-d2att in PDA, uncheck everything except auto reboot, put your phone in Download mode, plug it in to PC, wait for com port to recognize, and start the flash. I really hope this gets your phone back.
Link to TWRP: http://techerrata.com/browse/twrp2/d2att
As i mentioned, get 2.6.1.0.tar, not img file.
Got a phone on eBay cheap that being said I did some things that normally shouldn't be done but the devices are so similar that it worked overall I wouldn't try if its your only phone I like the d710 so I did some digging and trying I don't think there is a ROM I have not flashed on here that is available I've even ported some have four d710s all together first time I tried this I got it to work but USB fried I guess from i9100 old bootloader the second time u was even less careful from my d710 cm11 running ROM I installed a kernel flasher I backed up the kernel I got a i9100 lollipop rom ,aosp kernel from rwilco12 I believe just started using it actually but changing the updater script asserts to match the d710 even the whole script pasted in works (except for the write boot part ) changing the device names on the build prop to match and changing libril. Whatever to libril40 like the d710 path zipped and flashed lollipop on d710 if the screen sleeps it restarts system ui so i changed sleep display setting to thirty minutes update supersu zip got me rooted no WiFi Bluetooth works though SD works but ext SD does not so I had to Bluetooth a lot of apps to the phone storage the file manager works to install the package installer works and installs apks fully rooted kernel flashed rebooted restored my backup and back on d710 I have also flashed a i9100 kernel and recovery the d710 recovery will flash a i9100 Kitkat compatible recovery but the i9100 recovery will only flash i9100 ROMs so went from d710 recovery flashed i9100 recovery and installed any i9100 lollipop ROM I have found the problems with WiFi is present in all but to the point it force closes the system ui it does not do that in the earlier method (but the earlier method can only be done with aosp I have tried and its always an endless bootloop of installing apps starting updating contacts and reboot to do it all over) as long as the screen does not sleep and the WiFi isn't messed with the ROM is stable on the d710 installed supersu zip to root installed all my root apps messed around full root flashed d710 kernel reboot wipe restore and back to d710 both methods worked for me installing with the i9100 caused more problems than just changing stuff but it works both ways I have been successfully other ways as well thething is the WiFi does not work the buttons are not mapped I mean there is no hard home key on d710 so it dont work the search key is the settings key and the back key is the back key the home key does Nada and the menu key does Nada the Bluetooth works the mobile data and calling do not but everything else I have tested on it does what can I do to fix this being that it works very well on the d710 looks amazing setting the DPI lower makes it look even more elegant its an obsolete phone I know but it still got a whole lot of life in it thanks to everyone at xda not my first phone not my only phone I'm a self learned guy and that was only possible with xda I went from what the hell is rooting? To this I am not trying to offend anyone with my chopping up of their ROMs to make them work they are the bosses I just want to be able to use those ROMs on my device and they function great dev phone its almost indestructible jig Odin stock or jig Odin custom I have been successful in flashing either through Odin installing through the phone popping battery out when done jig Odin aosp kernel reboot recovery update super and booted if anyone else have an interest in seeing lollipop on this phone it can be done
TLDR; Punctuation, man!
Trying to build it. Have been since the last post. I'm not a professional but I am in fact making progress. Porting drove me crazy, so I am now trying to build from source.
Sorry about the punctuation. There was a whole lot going on at once in my head. Hopefully its a little understandable
Built the boot.img. compiling rom now. Have not tested either.
Why Lollipop instead of Marshmallow?
Boot.img works.flashed cm 11, update supersu.zip ,4.4 gapps, installed xda premium.apk. i signed in and updated status it also has SD card readability unlike the i9100 recovery and I could explain why not marshmellow yet but the base of the explanation would be I am not a programmer . I am teaching myself to do this and I thought I would start on something that has a couple of ROMs to port not many marshmellow but I don't think I will stop at lollli I have noticed that there are typos that need fixed in the source files that after edited made me that lollipop recovery
Any updates? CM13 works on the I9100, so I'm wondering if that could ever be ported to this phone.
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Aztek92 said:
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Click to expand...
Click to collapse
You must have had a bad install as I've not heard of anyone else with those sorts of issues. Though it could be an incompatible app or bad/old data etc Z you might want to ry fixing first eg wiping all app data or factory reset or fresh install (backup your files first )
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Aztek92 said:
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Click to expand...
Click to collapse
1. I see from your link you have the 3g version of the mini, I didn't think that one supports NFC, only the LTE (I9195) has it I think. As NFC needs the right hardware you won't be able to get it. But I don't have the 3g version so I'm not 100% certain if it has support or not.
2. Ii don't think the battery is related to CM13 directly otherwise there would be lots of people with the issue. What is the exact date of the snapshot? There was one that had battery issue but they updated it a few days later is it definitely 20160820 and not the one from a few days before you are running?
Else: If there any app showing high battery usage that doesn't normally? Or is there a problem white a wakelock? You can install an app like Trepn that will show you apps with high cpu usage (even when they are showing in about the usual place in battery stats, my browser recently locked into some sort of loop and was using a high % of cpu occasionally)
3. Always possible but unlikely it's due to Heimdal flash. TWRP should do fine. More likely the wrong Gapps causing instability, you should be on Open Gapps 6 for CM13
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Click to expand...
Click to collapse
edit: see arco's reply below,
The 3g CM ROM will not have the NFC code I guess
No do not check "update recovery" as you might lose your current recovery
gotta go get my son now!
Sent from my Galaxy S4 Mini using XDA Labs
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
Click to expand...
Click to collapse
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
arco68 said:
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
Click to expand...
Click to collapse
Thanks Arco!
(I was trying to say toggle the "signature verification" option but that could lead to more problems if he has the wrong recovery!)
Sent from my Galaxy S4 Mini using XDA Labs
Yup, its GT-I9195, maybe that's from all the problems comes, wrong rom, wrong recovery. I feel kinda dumb, that i didn't check under battery before, sorry for that.
I have work to do today i guess.
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Aztek92 said:
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Click to expand...
Click to collapse
Hi, sorry for bringing up this somehow old thread, but I have the exact same battery issue on my wife's serranoltexx.
I just installed CM13 on her phone, and after a reboot battery dropped from 40% to 5%. This happened twice, so no coincidence here.
Have you found where the problem came for ? Was your battery dead or have you found a fix ?
Also, I have seen your post about sview cover, very interesting. Will try it out tonight !
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Aztek92 said:
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Click to expand...
Click to collapse
Thanks for your answer !
If changing ROM and calibrating did not help, then I guess it's a hardware problem. That was my first thought when I saw this drop yesterday and I already told my wife that we'll have to buy a new one. Cheers to Samsung for building phones with replaceable batteries !
Even a geeky workaround for the sview cover might suit her needs. I think she just wants to check the time and her notifications with the cover on, I don't think she even needs to answer calls (she said it never worked for her, a touchscreen sensitivity issue I believe).
If she doesn't like it, I still have the possibility to downgrade her to CM11. It seems that sview worked fine on this release. And I'm sure she won't mind kitkat as she's not as geeky as I can be
I've been using CM13 nightly (latest) for 4 days or so.
Pros:
Battery last much longer, you have many battery profiles which is nice.
External SD can be integrated as Internal (nice that some apps are automatically installed onto SD)
Cons:
Can't find tar file which is backup I made using CWM recovery rom. Looked everywhere!
Icons dissappear from home after every bootup
Can't move sys apps or preinstalled apps to ext sd card. Can't use Link2SD once you configure External SD as internal. Not so flexible.
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
kennyk09 said:
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
Click to expand...
Click to collapse
Look in /data/media it should be there somewhere. Need root access though.
I recommend using TWRP instead of CWM.
arco68 said:
I recommend using TWRP instead of CWM.
Click to expand...
Click to collapse
Yes, but TWRP can't flash CM11 if I'm not mistaken. Old ROM, I know, but it's the latest one with S-View Cover support.
Also yesterday, I tried to restore my stock ROM backup with TWRP but could not get it to work. Stuck on "starting apps" during boot. Wiping Dalvik and cache did not help.
@thewild
If changing ROM and calibrating did not help, then I guess it's a hardware problem.
Click to expand...
Click to collapse
Not nessessary. Please notice, that i moved from CM13 (i9590) to... CM13 (i9595). I had an issue with wrong recovery. I also didn't have any problem on stock rom. If you're still gonna change battery, tell me how it worked for you.
Btw. there is something called hall monitor https://github.com/durka/HallMonitor But still i have no idea how and if it (still) works.
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10€, so I'll give them a try and let you know.
thewild said:
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10â?¬, so I'll give them a try and let you know.
Click to expand...
Click to collapse
€10, they would have to be fake! (or used)
What is the screen on time (battery>screen) you are getting? I bet it's low & that is the reason for your sudden drops, with my old battery (original Samsung) I was lucky to get 3hrs and that had sudden drops, new battery gives me 6hrs SOT.
Can't tell you the sot because it's not my phone, but it sure is very low. And the battery drops from ~50% to 0% in seconds.
10€ seems to be the right price. They are 20€ on samsung's store, but 10€ is on Amazon, sold by Amazon. I never got fake / used items from them.
Anyway, it's worth a try. I can send it back for free if it's not OK.