hey everyone,
I installed Liquidsmooth v2.5 on my dorid razr a few days ago.
All in all it works good and could be used as a daily driver but nonetheless there are a few bugs.
I installed in on System1 with BMM. and i always need a cuple of tries to startup my pohne.
The other times, BMM loads the files, starts kexex to boot and i keep stuck with a black screen and the green LED alight.
I gotta restart the phone up to 5 or 6 times if i finally see the boot animation and the phone starts normally.
And I'm not sure but I gotta feeling this rom drains the battery.
The process 'Android OS' used 46% and display did only 19%. This seems kind of weird because with the ICS stock Rom I always had display as the number 1 in consuming battery.
Does anyone has got the same problems, or even better knows to fix the boot issue?
greetings
I have a LiquidSmooth ROM out there, I know for a fact it works amazing. As for your recovery problems, I would advise using safe strap instead. Liquid smooth ROMs are reserved for slot 3 in safe strap.
i run Liquid smooth on BMM and never had any problems dude.....and about startup's yes it does take some tries if you had hard reset the phone...if u have done normal reboot then u wouldn't encounter this problem....so the fix as of i know is to not hard reset the phone....
and about battery drain i have great battery life i recommend u to use hotplug+noop as governor....and use setCPU and there is option to turn down CPU speed to 300 min and max being 800 under profiles...add a profile when screen off and set the given CPU freq..
Related
I have been running Das Bamf 1.7 Stripped no for quite some time without any problem, but recently I have been having quite a few random reboots. This morning I try to turn my phone on and It will not respond. This has happened before and all I had to do was plug it into the charger for a few minutes and then do a battery pull and it would start up. I tried that and all that it will do is give a small vibration and then do nothing.
Any help is appreciated.
I would try leaving it plugged in for like an hour and then give it a shot to see if it'll start up. The problem is every reboot eats a good percentage of battery so if you have enough of them you'll pretty much drain it down to where it will not power on.
I had this issue a long time ago but after leaving it plugged in for about an hour I was able to bring it back up easily.
Its kernal related
trentreed said:
Its kernal related
Click to expand...
Click to collapse
please enlighten us oh great one...
Hey, i am using thory GB rom lastest release 3.5.1 and it works perfectly but when i did the speedtweak.sh and set it to extreme my phone will not boot now it stays stuck at HTC and reboots itself but never goes past it how could i fix this please.
Was there a resolution?
No. I finally was able to boot into recovery and i deleted the kernel and re installed it and it finally booted back up idk why that did that if the speedtweak.sh preset settings should be safe.
every now and then, my phone will completely shutdown by itself. the only way to get it back on is to do a battery pull. it doesn't matter what kernal/radio/rom variation I use either. oddly, I find it seems to do it when I set my phone down for awhile. I haven't experienced it while I'm actively using the phone.
is this a common issue? fix?
Power Off
I have had the same issue. I thought it was something I did wrong. Beware, the problem suddenly got much worse for me today. My phone will only stay on about 90 seconds before powering off. It powers off even while in RECOVERY! It powers off unplugged, plugged into ac, and plugged into usb. The only time it does not power off is while in HBOOT. Does anyone have a fix to this problem or am I stuck going to Verizon and telling them I dropped my phone in the toilet?
Did you recently overclock because i was messing with mines today and it wojld also do that but now i got mines at 1.9ghz and has stopped doing that i guess mine is stable
Mine shuts off if i under clock it to low. 368 is my stable underclock. Anything lower and I risk being late for work LOL.
If I helped you in any way please use the thank you button
I have been using Imoseyen's (please forgive any spelling errors as I am doing this from memory) lean kernal 3.8.0 with the 184 MHz option left locked with bamf forever 1.0.7 for a few weeks now. My phone would freeze and reboot if I even tried to run at the 184 MHz setting, but I never had an issue with it at the 245760 Hz setting but I would up the power to 875 for that speed up from the 850 value used in extreme option. After I fixed power and speed values in init.d, I had an incredibly fast and smooth system (2500+) quadrant with a sense rom 245Mhz-1.6 GHz overclocked and undervolted at my custom power values.
Yesterday I decided to try an A05P rom to see if they were faster than the sense counterparts. I tried ShiftA05PHacked V2.7 again with Imoseyen's lean kernal for A05P 3.9.2. I did a nandroid of my stable and wonderful sense rom then did a complete wipe (dalvik cache, battery stats, system, and factory reset). So I get this puppy running and do all the same tweaks and things I did to my sense rom and I end up with an amazingly fast rom! I got a quadrant score of 3000+ when clocked from 245Mhz to 1.59 GHz. Again it was very stable but I missed my sense stuff so I thought I would just nandroid and wipe again to try a few more roms.
The next time I wiped and loaded Liquid Smooth v 1.6, I never got it booted before the random power off thing started happening. So I reboot into HBOOT by holding down volume after it powers down and go into recovery. I immediately attempt to format /system to no avail. I have wiped everything multiple times and cannot get my phone to stay on in recovery. Any ideas???
Problem Solved
Hey all, I have a solution to the problem I had and would like to share it. It isnt pretty or fun but it WORKED!
I tried to flash a rooted/deodexed stock rom as HBOOT was the only thing working for me...didnt work. My last step before dunking the phone in the sink with the screen on was to put a truely stock ruu (unrooted and all) on it. For whatever reason this cured the problem! I have since then re-rooted my t-bolt and have been able to get back to testing roms and tweaking to my flash-addicted heart's content!
BTW I have seen a lot of confusion about the flashing AMBER led light. It was due to the battery being dangerously low. Thank you to everyone here and the people at AndIRC #thunderbolt. You were great helps!
Hi all,
recently I flashed Ressurection Remix v3.8 with Siyah kernel 3.0.15
it worked pretty well but from time to time my phone would freeze up, get really warm and reboot (or not, and possibility to turn it on is to take the battery out and turn it back on)
after the phone is switched back on, the battery goes to 1% or 3 % and switches off quite quickly.
when I plug it in to charge it almost immediately goes back to the original battery charge
does anyone recognize this problem?
or if not any ideas whether it is an issue with the rom, kernel, radio or something else?
many thanks
supermooshman said:
Hi all,
recently I flashed Ressurection Remix v3.8 with Siyah kernel 3.0.15
it worked pretty well but from time to time my phone would freeze up, get really warm and reboot (or not, and possibility to turn it on is to take the battery out and turn it back on)
after the phone is switched back on, the battery goes to 1% or 3 % and switches off quite quickly.
when I plug it in to charge it almost immediately goes back to the original battery charge
does anyone recognize this problem?
or if not any ideas whether it is an issue with the rom, kernel, radio or something else?
many thanks
Click to expand...
Click to collapse
What is the real version of your Siyah kernel? because Siyah 3.0.x can never boot RR 3.8!
Jokesy said:
What is the real version of your Siyah kernel? because Siyah 3.0.x can never boot RR 3.8!
Click to expand...
Click to collapse
my bad, it's SiyahKernel S2-v4.1.5
supermooshman said:
my bad, it's SiyahKernel S2-v4.1.5
Click to expand...
Click to collapse
I recognise your problems.
1. "The phone will freeze up" may be caused by some user unstable settings on the kernel, or the general instability of your ROM + the kernel combo, or maybe you are using a conflicting script.
- Next time your phone freeze up, just hold down the power button for about 8-10 seconds instead of removing the battery.
- to solve this problem,
a. Reset all your kernel settings to default
b. remove any other scripts that might be running on your phone.
c. try to track what activity normally trigger this freeze up
d. If the problem persists, you can try another kernel.
2. "after the phone is switched back on, the battery goes to 1% or 3 % and switches off quite quickly". this one may be caused by the fact that your fuel gauge chip is not yet settled.
- to solve this one,
a. charge you phone,
b. Install and run Extweaks, under misc, select Reset Fuel Gauge chip.
c. Exit extweaks and leave your phone untouched for about 1hr to allow it to settle down.
Thanks, I'll give it a try!
Sent from my GT-I9100 using xda app-developers app
Jokesy said:
I recognise your problems.
1. "The phone will freeze up" may be caused by some user unstable settings on the kernel, or the general instability of your ROM + the kernel combo, or maybe you are using a conflicting script.
- Next time your phone freeze up, just hold down the power button for about 8-10 seconds instead of removing the battery.
- to solve this problem,
a. Reset all your kernel settings to default
b. remove any other scripts that might be running on your phone.
c. try to track what activity normally trigger this freeze up
d. If the problem persists, you can try another kernel.
2. "after the phone is switched back on, the battery goes to 1% or 3 % and switches off quite quickly". this one may be caused by the fact that your fuel gauge chip is not yet settled.
- to solve this one,
a. charge you phone,
b. Install and run Extweaks, under misc, select Reset Fuel Gauge chip.
c. Exit extweaks and leave your phone untouched for about 1hr to allow it to settle down.
Click to expand...
Click to collapse
hmmm didn't quite work:
1.
- reset the kernel
- removed all init.d scripts
- no idea how to do that :-s
- going to try this now (any suggestions by any chance?)
2.
- couldn't use extweaks as my phone would switch off before I could open it
fun trivia... my battery level went to -1 when I switched my phone back on... darnit
supermooshman said:
hmmm didn't quite work:
2.
- couldn't use extweaks as my phone would switch off before I could open it
fun trivia... my battery level went to -1 when I switched my phone back on... darnit
Click to expand...
Click to collapse
Did your battery run out of charge?
how many hours/mins can your phone work on battery when idle and when used?
You can try out a friend's battery and test if your problem still persists.
Jokesy said:
Did your battery run out of charge?
how many hours/mins can your phone work on battery when idle and when used?
You can try out a friend's battery and test if your problem still persists.
Click to expand...
Click to collapse
I don't think so as it happens at all different kinds of percentages, and when the phone restarts its mostly between 1% and 3%
on a single full charge when idle, the battery goes about 11 hrs
unfortunately none of my friends have a samsung - the battery of their iphone is not removable (... ok, lets not go there)
I did notice when it does happens, I am almost always using my phone (playing music, surfing, facebook etc), there is not really a particular app that is running when it happens (well maybe in the background)
also, about 5 seconds before it switches off my screen flickers, not sure if that is related (but I'm pretty sure it is)
thanks
My phone has been doing the exact same thing, screen flickers a few seconds then switches off, then the battery level has fallen ridiculously on reboot. Did you ever get to the bottom of this?
Sent from my GT-I9100 using xda app-developers app
I bought a new battery over the weekend, until now, the days and still nothing weird has happened
Maybe as jokesy mentioned, try a battery of a friend or buy a new one (they're not that expensive)
Good luck!
Sent from my GT-I9100 using xda app-developers app
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Are you undervolting/ under clocking this can cause a sod
Hi. Nothing like that, just used neat Rom or disaster Rom as they come.
sent from my Westcrip powered S2
Your phone(battery) has insane gauge chip search for this it answer in your question(it's only for battery)
Happy new year
Paulius
Hi, thanks for the reply. I'm not sure my issue is to do with the guage chip directly, as my phone will switch itself off at any battery level. The issue designed in the other thread its having something like 56% and then having a much lower value after an intended reboot.
Shutdown it's called sleep of death( scary name) but it not death it's just sleeping forever... it problem with your kernel and battery problem is insane gauge chip...
Happy new year
Paulius
I've just charged to full charge, unplugged - and within 2 minutes, the phone froze, could not do anything - so i pressed the power button until it went off, and it booted back up again without me doing anything - when it booted, it showed i had 2% battery. Then it did the same thing, froze, i had to reboot - then it showed 37% battery.........no idea what's going on apart from maybe a faulty battery...
Buy new battery. It was here on the forum a few times.
Yes. When phone hot(sometimes not) it take battery about 50-60%(I don't know exactly) but sometimes it add battery...
If you flash siyah kernel with stweaks(5 version) you can reset it but chip do funny thing even you reset...
Happy new year
Paulius
try Battery caliberation app ...
if it doesnt work buy a new battery
What are you talking about ? It's not battery Fault it's Insane Gauge Chip.... And Battery Calibration not helping...
I decided to go the whole hog and go back to a stock unrooted ICS, after wiping everything, then CFRoot - then reinstalled Neatrom light - currently restoring apps via Titanium - fingers crossed...
I think you don't have anymore BSOD But if you have flash Syiah kernel
Try new kernel and reset fuel gage
Try installing a new kernel like siyah or dorimanx and then reset your battery log this should resolve your problem if not buy a new battery.
karfeef said:
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Click to expand...
Click to collapse
I think I have a very similar issue. The randomly reboots happens several times a day, it does not happen though when charging (never). By now I'm on jb leak and still have the issue. When it shuts down, the sreen dims a bit and then it's gone, the weird thing is that often I have to pull the battery or charge the phone before reboot is possible, the battery shows different values after rebooting, sometimes close to what was before (especially when rebooting on charger), and sometimes way off the values before. I came initially from slimrom with siyah or dorimanx kernel, I really hoped jb leak would help (also tried different kernels), but it didn't. It also seems to me that it happens more often with the sd card (32gb) and without the phone seems more stable, but still it happens from tme to time. Once the screen dim (only one or two steps) and shut down even happend when in CWM recovery, is it maybe hardware related? It's very hard to find the source of the problem, anybody else experience similar issues? By the way the shutdown I have is not a proper shut down, the phone doesn't show the message "is shutting down".
I've completely wiped, used Odin to go back to ics stock, installed cfroot, then installed neatrom light. Had the same issue, so I've installed siyah, and used stweaks to reset the battery fuel gauge. I've only been off charge for 10 mins so far, but normally it would have shut down by now, so here's hoping...
sent from my Westcrip powered S2
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
karfeef said:
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
Click to expand...
Click to collapse
I had the same problem - SOD several times a day. I change the batery with a fresh new samsung 2000 mA one.
Unfortunatelly SOD came back, but I found a trick: turn off WiFi. Use it only manually.
For the past 3 months I succeded to have 0 SOD's.
I know that manual WiFi is a setback but it works with those experiencing SOD.
Hope it will be usefull.
Hello all,
My Note has been acting funny as of late. I am running Flapjaxx Cyanogenmod build. Earlier today, the device went into a boot loop fit and wouldn't get past the Samsung logo. On first notice, I thought that the power button may be stuck, causing the device to constantly restart. Upon further investigation, I noticed that:
On plugging in my device to a charger, the charging screen says that the battery is almost full, but on booting into team win recovery, it says that the batter is at 5 percent.
The battery seems to have gotten a tad bit fatter. When I take the back cover off, the battery just falls out when the phone is battery side down. It may be worth noting that I can't seem to get the back cover on all the way the past few weeks.
But the reason I am posting instead of just fixing the battery is because this started out of nowhere and my phone has been on this rom for many weeks now. Could the battery be causing all of this?
I have wiped the caches and I can get it to power on now but it keeps saying that "android is updating, optimizing x out of 60", which means that it is rebuilding the dalvik cache. Any help on this would be appreciated as I use this device a lot.
Back up and try another rom ....
••••changes with every flash••••
shayneflashindaily said:
Back up and try another rom ....
••••changes with every flash••••
Click to expand...
Click to collapse
I did want to avoid data loss if at all possible. I would take the latest unbloated ATT ROM.
I guess this what I get for developing on the Apple platform instead of android
I recently had a 6 month old Anker battery fail. It would cause my phone to boot to the samsung screen and hang. Had to install a backup each time it happened as no matter what I did the ROM would not load. After replacing the battery I had no more issues.