Related
Hi,
I'm seriously considering going out and buying this phone but I'm really not sure after seeing all the threads with people saying that they go back to their phone and it's switched off and requires a battery pull.
This seems to be a fairly serious problem but I was just wondering if it is happening to everyone who owns the O2x?
Please let me know if you are unaffected by the problem!
DarthOps said:
Hi,
I'm seriously considering going out and buying this phone but I'm really not sure after seeing all the threads with people saying that they go back to their phone and it's switched off and requires a battery pull.
This seems to be a fairly serious problem but I was just wondering if it is happening to everyone who owns the O2x?
Please let me know if you are unaffected by the problem!
Click to expand...
Click to collapse
Dont do it go for SGS2
Mine is fine! 1 month of use and never crashed.
My phone has been fine not one reboot or freeze, stayed stock rom for first week then rooted and changed roms several times and still no problems, got mine off ebay brand new, can give u the link to the seller if you like
Sent from my LG-P990 using XDA App
I've had mine since March and I have not experienced any freezes or reboots.
It really is a great piece of hardware. I'm not that fond of LGs software, but that can be solved with a custom ROM.
// A
aholstenson said:
I've had mine since March and I have not experienced any freezes or reboots.
It really is a great piece of hardware. I'm not that fond of LGs software, but that can be solved with a custom ROM.
// A
Click to expand...
Click to collapse
Have you done anything (or have any tips) to try and avoid the issues or do you think you're just lucky lol
KeePeeR26 said:
Dont do it go for SGS2
Click to expand...
Click to collapse
Unless you want accurate GPS that is.
Rusty! said:
Unless you want accurate GPS that is.
Click to expand...
Click to collapse
So, how do you get on Rusty, you seem like a very experienced XDA member.. how is the O2X treating you?
i am not the best guy to talk to . i just got the phone used yesterday for very cheap. i figured that if i dont like it, i can sell it for the same money or even make a little more and get the SGS2.
but so far. no crashes/reboots.. been more than 24 hours. using custom rom as well.
i got the phone for 300$. the stickers still on it. i figure if i decide to sell it. i wont lose at all..
so far. i am really loving the phone. i love the UI of LG. but its slow. it laggs. i wonder if there is a custom rom with the LG UI but smooth one.
right now i am on modaco. with 3000 quadrant. if i switch to google launcher. phone is smooth. if i switch to LG one, it laggs a little in the home screen. i tried the Tmobile version 2.3 on my optimus. its super smooth. but i cant make phone calls on it lol.
and i had a screen problem with the cayanogen rom. for some reason my screens dims and go bright on its own.
oh yeah. i also have a screen light leak/bleed. but it doesnt bother me much because the only way i can notice it if the room is dark and i have a black wallpaper.
Mine went slow once on stock, once isn't bad though. The froyo Rom does seem rushed in truth, (I have random battery drains from my Dialer which makes no sense) but I'm sure Gingerbread will have everything sorted.
DarthOps said:
So, how do you get on Rusty, you seem like a very experienced XDA member.. how is the O2X treating you?
Click to expand...
Click to collapse
Pretty well to be honest. I use CM7 nighties (I bought the phone specifically because it was going to be supported by them) so I cannot expect a bug free experience at this early stage.
I am enjoying it though, I came from a Nexus One that had bugger all internal storage and a poor digitizer, so proper multi-touch and 1.5GB spare for apps is fantastic.
The IPS screen is great if you can overlook the associated backlight bleed (it's not just the 2X, look at iOS devices as well, same thing), the GPS chip is excellent, I can get locks in place that my N1 couldn't.
The stock ROM is turd, frankly. It's fast, until you install something, then it becomes unusable for a bit until it's finished with the app... quality coding
fine
i have my lg optimus 2x now for over a month, no problems here.
i stil have the stock rom.
first v10a. no problem
later v10b. no problem
I have had 2 O2x now for litle over a month
one of them has had BSOD and restarts randomly - the other had none, atleast for the first month - but these past days this one has now also rebooted a couple of times.
Both are completely stock - not rooted and not using any custom roms.
Only using a different launcher which do help make the BSOD and Reboots less often.
DarthOps said:
Have you done anything (or have any tips) to try and avoid the issues or do you think you're just lucky lol
Click to expand...
Click to collapse
I haven't done anything special, so I guess I'm just lucky.
KeePeeR26 said:
Dont do it go for SGS2
Click to expand...
Click to collapse
I returned my O2X and did exactly this. SGS2 on the way to my door!
smokie700 said:
I returned my O2X and did exactly this. SGS2 on the way to my door!
Click to expand...
Click to collapse
TRAITOR hehehehe
Look at all the problems they are having aswell over at there forum
No Issues
I have had it since first day it came out. Not one reboot. Other then minor screen bleed love the phone 1,000X better then my Vibrant
Kickasskev said:
TRAITOR hehehehe
Look at all the problems they are having aswell over at there forum
Click to expand...
Click to collapse
I been over there as well. Most of the problems on the SGS 2 are either software or can be solved with apps. My O2X had so many problems that I could never use the phone and wifi at the same time. Bleeding, constant reboots/freezes crashes even with Custom ROMs. Since Im in afghanistan now I need a phone that will work not just when it feels like it. I will say that when the O2X was working it was a sweet phone. I just dont see the same problems with the SGS2 and Samsung tends to be better in the service side instead of LG leaving us pissing in the wind waiting for a "possible update" that might fix things or not.
guess i´m a lucky guy, too!
i have no crashes/reboots and absolutely NO backlight bleeding
Mine is also working properly.
Sent from my LG-P990 using XDA App
I've been busy lately so I'm having difficulty staying on top of the latest news. What's the progress with CM7 and it's insomnia?(sleep troubles) I love CM7 but if it keeps being a Vampire my Battery will be at risk and I'll have to switch ROMs. Any News?
____________________________________________________
Sent from NookColor CM7 using Tapatalk
Dalingrin is working on the .32 kernel, the future successor to our current kernel. He has fixed the sleep issue in this new kernel but he still has work to do on other aspects of it. This has all happened fairly recently so stay tuned.
Sent from my DROID2 using XDA Premium App
TJNooker said:
Dalingrin is working on the .32 kernel, the future successor to our current kernel. He has fixed the sleep issue in this new kernel but he still has work to do on other aspects of it. This has all happened fairly recently so stay tuned.
Sent from my DROID2 using XDA Premium App
Click to expand...
Click to collapse
Good to know If anybody else has more info I'll gladly accept.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
It would be sweet if the fix gets the battery performance to be as good as that of Stock 1.2!
Waiting eagerly for the release. Using Froyo 0.6.8 R7 in the meantime.
is it just me or CM7 in general goes through a battery noticeably faster? I guess I can try doing a simple comparison using the browser or something.
s52m3 said:
is it just me or CM7 in general goes through a battery noticeably faster? I guess I can try doing a simple comparison using the browser or something.
Click to expand...
Click to collapse
Between the overclocked kernel and the fact that it doesn't go into a deep sleep, yes, CM7 currently consumes battery very quickly relative to stock. It sounds like the new kernel will address the latter, but you're always going to pay some cost for higher performance with an overclocked kernel while you're actually using the NOOK.
SCWells72 said:
Between the overclocked kernel and the fact that it doesn't go into a deep sleep, yes, CM7 currently consumes battery very quickly relative to stock. It sounds like the new kernel will address the latter, but you're always going to pay some cost for higher performance with an overclocked kernel while you're actually using the NOOK.
Click to expand...
Click to collapse
I haven't overclocked anything, I have it set at 800 max in the setup.
s52m3 said:
I haven't overclocked anything, I have it set at 800 max in the setup.
Click to expand...
Click to collapse
Then it's most likely due to the lack of deep sleep.
japzone said:
Good to know If anybody else has more info I'll gladly accept.
Click to expand...
Click to collapse
Like reading the cm7 thread?
khaytsus said:
Like reading the cm7 thread?
Click to expand...
Click to collapse
I don't have time to read all the threads and other things. You know how many things are posted there. I loose hours just reading through threads and I don't have hours to do so right now. So any info on the Sleep Fix would be appreciated.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
So
I'm running the latest nightly, and I highly recommend everyone at least flash up to n63. In there Dal was able to get the speaker to shutup when it's sleeping (you'll still hear the buzz when the screen is on, but when off...nice and quiet )
That, plus the 1.3GHz kernel, I'm getting MUCH better battery, and it seems snappier (and has since the base changed to 2.3.4).
ace7196 said:
So
I'm running the latest nightly, and I highly recommend everyone at least flash up to n63. In there Dal was able to get the speaker to shutup when it's sleeping (you'll still hear the buzz when the screen is on, but when off...nice and quiet )
That, plus the 1.3GHz kernel, I'm getting MUCH better battery, and it seems snappier (and has since the base changed to 2.3.4).
Click to expand...
Click to collapse
Sweet, I prefer to stay as stable as possible but with these updates I'm pretty much sold on at least updating to your specified version. Unfortunately I'm away from home at the moment and this Net connection is slow. I prefer making an Image Backup before I update anyway, just incase. That way I can always Flash back if anything screwy goes on.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
ace7196 said:
So
I'm running the latest nightly, and I highly recommend everyone at least flash up to n63. In there Dal was able to get the speaker to shutup when it's sleeping (you'll still hear the buzz when the screen is on, but when off...nice and quiet )
That, plus the 1.3GHz kernel, I'm getting MUCH better battery, and it seems snappier (and has since the base changed to 2.3.4).
Click to expand...
Click to collapse
Glad to know I'm not the only one to see an improvement on 63, but... I have not been able to replicate it since. I had better than 0.25%/hour right after flashing but have been close to 1% in the day since. Oh well. Someday...
Any new Progress?
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
think they fixed ith with test build in cm7 developer thread
Wow thread got barried.
~~bump~~
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
Wow thread got barried.
~~bump~~
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
IM sorry, but in a tenth of the time you were waiting for somebody to do the search for you, you could have done a search and found your answer.
Hint, its in the dev forum (as previously hinted at 8 hours ago by the previous poster).
The new Beta 2 solve the sleep issue. Lot of dev over there, progressing to Beta 3
http://forum.xda-developers.com/showthread.php?t=960537
Divine_Madcat said:
IM sorry, but in a tenth of the time you were waiting for somebody to do the search for you, you could have done a search and found your answer.
Hint, its in the dev forum (as previously hinted at 8 hours ago by the previous poster).
Click to expand...
Click to collapse
I was busy at the time and couldn't check, it takes time to look through a forum which I didn't have but making a post on a already started topic takes a minute. Now, I have free time to check myself.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
I have nightly 70 running now and the sleep issue can be put to bed. CM7 is now all it should be. I guess I will wait a bit longer for kinks (although everything seems fine for me) to be worked out and I can finally flash to eMMC and ditch the stock rooted ROM.
-Steve
My phone is up and running from quite long time and still going on (no signs of rebbot )
1221:56:13 ~ 50 days.
Wanted to know if this is good or bad for the Phone hardware.?
Should i rebbot my Phone.
Screw it.
Start a phone up time challenge thread.
Sent from my HTC Incredible S using xda premium
10:16:10...
I'm on 36 hours. I get to about 80 and always restart my phone.
Sent from my Incredible S using xda premium
+1 Phone up time challenge thread
orange2784 said:
Wanted to know if this is good or bad for the Phone hardware.?
Should i rebbot my Phone.
Click to expand...
Click to collapse
How would rebooting the phone help the hardware? Ask yourself that question.
There's TVs that have been on in the bar I work at for the last 9 years non stop 24/7, they won't die.
Sent from my HTC Incredible S using xda premium
as far as my understanding goes ... few of the process uses some part of memory continuously and can cause few glitches to hardware since its hitting same place again and again... Reboot free up everything and start new processes allocating new memories.. (I may totally wrong or dumb ) ... that y asked..anyways I'll keep it running until totally needed to reboot...
Heyy!! +1 for UP Time Thread ... havent seen that thread for Incredible S....
mine was 400+ hours untill I reboot it for rom upgrade
237:46
Up since the last time I updated the ROM.
Sent from my HTC Incredible S using XDA
Only 92 hours here... too bad I forgot to charge it once so it died: (
Sent from my Incredible S using XDA
apologies for digging the old thread...
I managed to keep the Phone up till " 2570:25:57 " with stock Rom 2.3.5 ..
had to restart coz of network problem..
Wondering is ICS is going to keep up like this..I heared Evo3D got ICS update and response is slow and it lags...hope this wont happen with Incredible S...
orange2784 said:
apologies for digging the old thread...
I managed to keep the Phone up till " 2570:25:57 " with stock Rom 2.3.5 ..
had to restart coz of network problem..
Wondering is ICS is going to keep up like this..I heared Evo3D got ICS update and response is slow and it lags...hope this wont happen with Incredible S...
Click to expand...
Click to collapse
Thats a long time
So do you find that it performs the same after that long as if you had just rebooted?
I never have mine on for more than 48 hours
When I charge overnight, I turn the phone off
I also have it set to do heaps of performance enhancing stuff on boot so maybe mine is just faster after reboot because of that
markj338 said:
Thats a long time
So do you find that it performs the same after that long as if you had just rebooted?
I never have mine on for more than 48 hours
When I charge overnight, I turn the phone off
I also have it set to do heaps of performance enhancing stuff on boot so maybe mine is just faster after reboot because of that
Click to expand...
Click to collapse
True it work faster after reboot... running so long it started showing lags, apps load slow... and main problem I faced was network..it started loosing network quite frequently... once complete reboot all gone and response is little better...
Hi Folks, I hve had my note for 1 year now and haven't had any battery problems until 2 days ago when I flashed a jb rom. All was fine for about 10 hours when I started to recharge the battery again that went fine, charged to 100% and unplugged, the phone said it was at 100%. After another few hours the phone cut out, no warning just cut out. I could get the phone back on but only when plugged into the charger. So, heres my problem, phone says battery is fully charged but when I unplug the charger it cuts out now. if I boot in to recovery with out the charger it stays on for hours. if I try to start the phone up normally with out charger it doesn't work. I have tried another battery again it started fine for almost a day then the same problems again. I have tried several kernels and roms in case it was one of those that was causing the problem but its the same every time. Im not a newb when it comes to flashing roms some im 100% sure its all ok in that department. any help would be appreciated.
thanks
Graham
My note is also about 10 months old. I want to know if my battery stats. I feel like my phone is giving me short time.
My question is do i need a replacement with these stats????
Sent from my GT-N7000 using xda app-developers app
qazibasit said:
My note is also about 10 months old. I want to know if my battery stats. I feel like my phone is giving me short time.
My question is do i need a replacement with these stats????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
What really matters here is your screen on time (I can get around 4h30 with heavy use). I also see you have a few notifications so there might be some draining apps running in the background (like that *** Facebook app which is constantly running in the background even with notifications off). In any case BBS should help you identify the "rogue" app (if any). Also I don't use Google Now as it's kind of a battery killer.
this problem is same with me...after 1 year use gnote
and this is battery problem..i dont know whats is causing it...
i try to enter recovery mode and ..battery is good..almost 4 hours screen on recovery mode
but if I try to start the phone up normally phone is reboot after 1minute in homescreen android
trying with different rom jb ..same problem ..
after replace my battery ..problem is gone..
@strachg If the phone used to work well before you flashed JB I'd recommend going back to ICS to see if the problem persists. If it disappears the reason is JB which would not supprise me since all JB roms for the Note are not really bug free. If the phone continues to behave like you described and changing the battery does not help either I'd say it's a hardware failure.
Sent from my revived Galaxy Note
altae said:
@strachg If the phone used to work well before you flashed JB I'd recommend going back to ICS to see if the problem persists. If it disappears the reason is JB which would not supprise me since all JB roms for the Note are not really bug free. If the phone continues to behave like you described and changing the battery does not help either I'd say it's a hardware failure.
Sent from my revived Galaxy Note
Click to expand...
Click to collapse
Hi, Yeah I already tried going back to ics and it was just the same, it just seems like a bit of coincidence and really annoying lol. The only thing I can think off that is causing it is as you say that its a hardware fault and it must be overcharging the battery and breaking it. If it was JB that was causing it im sure I wouldn't have been the only one by now.
thanks
Graham
how did you install jb? Was it clean on safe kernel? You havent eliminated the possibility of software issues.
Qazibazit, it looks ok.
Guideline 3,5-4,5 hours on screen time is normal (if you play games can be less, thus is from full to 1%). Total standby time, usually more then 24 hours is normal.
If you have a lot less, go read ahalfords sticky on wakelocks. All you need to know to optimize battery.
Sent from my GT-N7000 using xda app-developers app
Hi baz 77 yeah using safe kernel, tried a few actually. And using utackas. Version of paranoid android now again tried a few Roms. Everything was wiped and redone the process about 20 times. I looked through all the roms. And kernel threads and no one has had this problem. New battery coming so will see how it goes now.
Cheers
Sent from my GT-N7000 using Tapatalk 2
strachg said:
Hi baz 77 yeah using safe kernel, tried a few actually. And using utackas. Version of paranoid android now again tried a few Roms. Everything was wiped and redone the process about 20 times. I looked through all the roms. And kernel threads and no one has had this problem. New battery coming so will see how it goes now.
Cheers
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
yep thats pretty definitive, at least if all those roms are not having same base and thus posibly same issues.
Your new battery will improve your experience quite a bit if its a good one!
Have fun with it and let us know if it worked for you
I need a little help. My I897 is running on MPD 2.0 ROM, w/ EyeCandy v 3.15 and Corn Kernel 7.06, and it is stuck bootlooping at the swirling optical illusion at start-up. I don't know why, all I was doing was playing a couple of games and it was really lagging, and freezing up and it has been a lot lately. I even posted about it yesterday or the day before? Whatever?
So tonight, it just froze while playing a game and it was totally unresponsive so I let it sit. After about 10 minutes, I noticed it was on the optical illusion and stuck with the illusion spinning away. I pulled the battery, restart the phone same thing. Goes through the first start up screens and gets to the swirl thing and goes no further.
I pulled the battery again and replaced it, went into recovery and hit the reboot device and started it up. Same thing.
Should I reflash the Rom? If I do, I have to do a full wipe and that will suck.
Has anyone had this problem on MPD 2.0?
Maybe someone has an answer.
Thanks, whoever tries to help me with this.
Sent from my SGH-T989 using xda premium
kaiserXDA said:
I need a little help. My I897 is running on MPD 2.0 ROM, w/ EyeCandy v 3.15 and Corn Kernel 7.06, and it is stuck bootlooping at the swirling optical illusion at start-up. I don't know why, all I was doing was playing a couple of games and it was really lagging, and freezing up and it has been a lot lately. I even posted about it yesterday or the day before? Whatever?
So tonight, it just froze while playing a game and it was totally unresponsive so I let it sit. After about 10 minutes, I noticed it was on the optical illusion and stuck with the illusion spinning away. I pulled the battery, restart the phone same thing. Goes through the first start up screens and gets to the swirl thing and goes no further.
I pulled the battery again and replaced it, went into recovery and hit the reboot device and started it up. Same thing.
Should I reflash the Rom? If I do, I have to do a full wipe and that will suck.
Has anyone had this problem on MPD 2.0?
Maybe someone has an answer.
Thanks, whoever tries to help me with this.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I'm not so sure what MPD is but Corn kernel is on GB. Therefor, there's no developping nor support being made for it, which could explain why you got no answer on your previous post.
Luckily, you can get in recovery. Make a backup, wipe cache/dalvik and try to boot up. If that doesn't work, back in recovery, wipe cache/dalvik, factory reset and reflash your ROM. Altough, I would suggest looking at the newer ROMs out there as we're up to JB 4.2.1 (you're on GB 2.3.5).
If you go ahead with the upgrade, make sure you follow the full instructions in the OP.
Thanks, I already reflshed and its running. I know that there are newer Roms I only flashed it because I hadn't yet flashed anything from the Collective and the eyecandy theme I wanted to check out also.
But after running great for a couple weeks, it started getting buggy. Now I'm gonna do something else. My SII is running darkside Evolution #5 4.03 by thederekjay w/venom kernel, and I wanted an older Rom in my Cap, for contrast.
I'm not sure what I'll do next. I just needed it running. It is my business line for my electrical contracting company. And it will start ringing in about a ½ hour.
Thanks, for your response and have a great day.
Sent from my SGH-T989 using xda premium
kaiserXDA said:
Thanks, I already reflshed and its running. I know that there are newer Roms I only flashed it because I hadn't yet flashed anything from the Collective and the eyecandy theme I wanted to check out also.
But after running great for a couple weeks, it started getting buggy. Now I'm gonna do something else. My SII is running darkside Evolution #5 4.03 by thederekjay w/venom kernel, and I wanted an older Rom in my Cap, for contrast.
I'm not sure what I'll do next. I just needed it running. It is my business line for my electrical contracting company. And it will start ringing in about a ½ hour.
Thanks, for your response and have a great day.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Wait, the collective? The Collective and The Family used to be one team.. Yet I dunno what you mean by MPD?
And if you're looking into something stable, I would highly suggest either AOKP or AoCP (4.1.2).
MPD is a KK4 based Rom put together by robm1911 of the Collective. The Multiple Personality Disorder ROM http://forum.xda-developers.com/showthread.php?p=27985912
Sent from my SGH-I777 using xda premium
4-2ndtwin said:
MPD is a KK4 based Rom put together by robm1911 of the Collective. The Multiple Personality Disorder ROM http://forum.xda-developers.com/showthread.php?p=27985912
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Oh I see, was made while I was away. Thanks for the clarification 4-2ndtwin
What would you recommend for a stable build? I use my Cap as my business line. So it has to be reliable. Camera, GPS, texting, etc..., all have to function. But I also like to have the little extras. As you know I'm on the kk4 kernel, and I'm OK with flashing, not okay with having to run anything that needs me to use Linux or do any command lines that kinda thing. I still new to everything. Thanks
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
kaiserXDA said:
What would you recommend for a stable build? I use my Cap as my business line. So it has to be reliable. Camera, GPS, texting, etc..., all have to function. But I also like to have the little extras. As you know I'm on the kk4 kernel, and I'm OK with flashing, not okay with having to run anything that needs me to use Linux or do any command lines that kinda thing. I still new to everything. Thanks
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
kaiserXDA said:
Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
If you look up, I already made 2 suggestions
AoCP or AOKP (4.1.2)
kaiserXDA said:
Sorry, but I forgot to mention that it running pretty normal now. I got rid of the eyecandy theme. It is the culprit from what I can tell. Without it the phone is better. Still a little laggy though.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
There are also tweaks in recovery that u can choose from and even the ability to change the partitions to Ext4. Check the kk4 corn kernel's op for info on these things.
I use my cappy for work and pretty much have stock kk4, with Root, debloated, Ext4 on all partitions and the tweaks i have are sio Scheduler and smartassv2 Governor. Runs great !
Sent from my SGH-I777 using xda premium
I have it running on deadline and smartass v2 and it runs pretty damn well, I dont know too much about partinoning so I have stayed clear just in case I screw something up.
What about the kernel tweaks (ROM toolbox pro) the voltage controlsyscti tweaks? What is that for, signalling the different MHz -0mV? I'm an electrician and have been for 20 years but electronics is a new hobby and the phones my new medium. I would love to know more, so if you could tell me what I should read or??? That would help me learn more I would be stoked.
Thanks KK
kaiserXDA said:
I have it running on deadline and smartass v2 and it runs pretty damn well, I dont know too much about partinoning so I have stayed clear just in case I screw something up.
What about the kernel tweaks (ROM toolbox pro) the voltage controlsyscti tweaks? What is that for, signalling the different MHz -0mV? I'm an electrician and have been for 20 years but electronics is a new hobby and the phones my new medium. I would love to know more, so if you could tell me what I should read or??? That would help me learn more I would be stoked.
Thanks KK
Click to expand...
Click to collapse
OC = Overclock
UV = Undervolt
SoD = Sleep of Death
I don't suggest changing voltage on the cappy (UV). The processor isn't strong/fast enough, therefor it takes more time to process what you ask of it = more screen time = more battery drain. While screen off though, your battery will be better (can also cause black screen and SoD at unstable state). Screen on is the main battery drain for androids. So basically, reducing your voltage (UV) will lower your battery consumption, of course at a price = slower processing and despite you intention to reduce battery drain, it might increase it. The Captivate has proved to be quite unstable with OC/UV on GB and up.
Up'in your Mhz (OC) will make your phone faster but at the cost of faster battery drain and faster hardware usage. On top of that, both can make your phone unstable. Finding the right combination can take some time if you really wanna get into it. There are guides about it which you can find with a little search, altough, once again, I don't recommend it.
Thanks Bwolf, I really appreciate you taking the time to explain some of that. I have read some some of that stuff in other posts, over the past year or more that I've been on XDA, although it was Greek to me at the time. Now I knowwhat you guys are saying, I just don't know the hows or whys. In time.
I will follow your advice on the voltage and the OC and leave it alone.
There was a time a while back when I first started messing around and I changed something it might have been voltage, and my Cap went nuts. It was sucking down my battery right before my eyes, so fast and getting hot, I pulled the battery and I don't remember how I got it straightened out, but I did. Crazy! So, I know better, curiosity killed the cat (cap) lOL. Thanks Again
kaiserXDA said:
Thanks Bwolf, I really appreciate you taking the time to explain some of that. I have read some some of that stuff in other posts, over the past year or more that I've been on XDA, although it was Greek to me at the time. Now I knowwhat you guys are saying, I just don't know the hows or whys. In time.
I will follow your advice on the voltage and the OC and leave it alone.
There was a time a while back when I first started messing around and I changed something it might have been voltage, and my Cap went nuts. It was sucking down my battery right before my eyes, so fast and getting hot, I pulled the battery and I don't remember how I got it straightened out, but I did. Crazy! So, I know better, curiosity killed the cat (cap) lOL. Thanks Again
Click to expand...
Click to collapse
Hehe np. As for what happened before, pulling the battery most likely reseted your kernel settings (OC in this case) as it probably wasn't ''set on boot''. Probably saved you a lot of hastle too