I'm considering rooting my Vibrant & going with the one click lag fix. Has anyone noticed a decrease in their battery life after doing this? I'm not sure exactly what this does to the phone. Does it overclock the processor?
If One Click Lag Fix is not running, I honestly don't think you will see a decrease in battery life if you did this particular lag fix. I never had any decrease while using it for a little over a month.
If it is running as it does on boot, I am unsure and cannot give you an answer if it decreases battery life while running in the background. I think it only checks to make sure everything is okay each time the device is booted. You may be able to find more at the topic: http://forum.xda-developers.com/showthread.php?t=760571
This lag fix just takes your /data? if I recall correctly at this moment and changes it over to the EXT2 filesystem.
As far as overclocking the processor, no it does not overclock it. SetCPU and whatever other tools out there, or custom roms, would do this however for you if you wanted to do that.
I believe the one click lag fix doesnt change it totally over to ext2. It creates a sizable ext2 partition and runs stuff from there. I've heard the problem with this method is if you are using it long term for months and months it could corrupt some data.
Sent from my SGH-T959 using XDA App
ihackyourtech said:
I'm considering rooting my Vibrant & going with the one click lag fix. Has anyone noticed a decrease in their battery life after doing this? I'm not sure exactly what this does to the phone. Does it overclock the processor?
Click to expand...
Click to collapse
Does posting in the wrong section get you want you want? In this case yes, it does. Just be sure to post in the correct place from now on.
It shouldn't do much if anything to battery life. It creates a Ext2 file system partition for apps on your internal SD card. Essentially giving apps better read/write speed over Samsung's RFS file system.
ok WOW. I got the update tonight and was using launcher pro plus and the phone was laggier than before. I switched back to the TW launcher and rebooted my Vibrant. Now, it is much faster than before. The market downloads page loads instantly now and apps load quicker.
3G speed is also improved. I'm now getting over 2.5 down and .5 up. This along with working GPS is a massive update. Now, I can't wait for froyo, but i'm not so anxious.
Thread moved to Q&A.
I installed the Nameless v4 yesterday and v4.1 today.
On the Froyo roms my battery pull on idol was -2 to -10ma [i use battery monitor widget]
Now on the GB i am getting -100 to -275.
Is anyone else experiencing this kind of draw?
[I do understand that the GB is a wip]
I can't speak on the new build, but I was running the 4.0 build and my battery ran down so quickly that I thought I left my gps running with a connection. I also was having quite a lot of issues with the rom, so I thought it was a fluke. I'm on 4.1 and it's been running much better, so hopefully the battery drain isn't as great.
Definitely sounds like you've got a runaway process or wake-lock occurring somewhere. Have a look around the processes and see if something's keeping the CPU running hard. Also run a dumpsys power from adb and see if something's keeping it from sleeping.
Im getting quite the opposite here. It's been almost a day and after moderate use I have a little over 50%. It's amazing because I would be getting half of that on a full charge in froyo.
Looks like it may have been the Widget itself.
But i am not sure, if i closed the running application of Battery Monitor it dropped down to -1 or -2 but then ten mins later its back up to -300.
The other possibility is when i kill the app the widget gets no information and defaults to a low number.
Thank you everyone for your input. I will keep on testing to find my battery killer.
I also may try uninstalling K-9 mail and reverting to the stock Mail client
It being on stock kernel and a lot of debugging features being enabled will do that to your battery.
Sent from my SCH-I500 using XDA App
A lot of people have reported poor battery life with K-9, FWIW, though the K-9 devs say there isn't an issue. I haven't used it myself so I can't really say... you could try this though:
https://market.android.com/details?id=org.r3pek.k9datakiller&feature=also_installed
4.1 drained my battery from 100% to 10% in about 4 hours today. But then I plugged in and rebooted and I had 40%, so I would imagine a battery stats wipe is needed on my phone.
My home button does not work as well, so I am going to re-install again and see if it fixes these issues.
Anyone else had the home button issue?
Edit: The re install fix the home button/lock screen issue. Will report back on the battery tomorrow.
Weird, my battery is AMAZING on Nameless. After 11 hours with using Screeble, with moderate use, I'm at 50%.
xwhofarted said:
I installed the Nameless v4 yesterday and v4.1 today.
On the Froyo roms my battery pull on idol was -2 to -10ma [i use battery monitor widget]
Now on the GB i am getting -100 to -275.
Is anyone else experiencing this kind of draw?
[I do understand that the GB is a wip]
Click to expand...
Click to collapse
I tried Nameless 4.0 and it used less than 20% during the first 6 hours.
Whenever I flash a new rom, it uses more power at first and less and less as you use the phone. Some people insist that you do not have to kill the apps especially on Gingerbread.
zas311 said:
Some people insist that you do not have to kill the apps especially on Gingerbread.
Click to expand...
Click to collapse
Assuming you're talking about task killers, "some people" = Google. With the exception of apps like Watchdog (which just notifies you of apps using excessive CPU, like >50%), task killers hurt more than they help -- they're all effectively scams.
Google's serious techy explanation:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.
An excellent, understandable article from Lifehacker:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
I thought I read somewhere (either the EC09 Leak thread on the Nameless v4 thread) that auto-rotate is causing 50% cpu for this EC09 leak, would that have something to do with battery drain?
http://forum.xda-developers.com/showthread.php?t=1131213&page=15
Thanks
saw the one about auto rotate and turned it off, then i was in the -50 to -100
But that is still bad coming from froyo`s -2 to -10
So i went back to Com Rom and will be awaiting the best Devs on XDA to crack the Leak and make some fantastic ROMS, just like they did with Froyo!
Keep up the good work!
xwhofarted said:
saw the one about auto rotate and turned it off, then i was in the -50 to -100
But that is still bad coming from froyo`s -2 to -10
So i went back to Com Rom and will be awaiting the best Devs on XDA to crack the Leak and make some fantastic ROMS, just like they did with Froyo!
Keep up the good work!
Click to expand...
Click to collapse
I suggest disabling auto rotate, rebooting, and then never turning auto rotate on again. (even toggling on/off can get the events/0 process stuck at high cpu usage) Once I did this, the full bloated GB leak is spanking Froyo battery life.
This more than makes up for the poor contacts scrolling for this guy.
Also full bloated GB leak appears to be much safer for you SD card than other versions of the leak.
Scrappy1 said:
I suggest disabling auto rotate, rebooting, and then never turning auto rotate on again. (even toggling on/off can get the events/0 process stuck at high cpu usage) Once I did this, the full bloated GB leak is spanking Froyo battery life.
This more than makes up for the poor contacts scrolling for this guy.
Also full bloated GB leak appears to be much safer for you SD card than other versions of the leak.
Click to expand...
Click to collapse
This. My battery life (and signal dBm) has been MUCH better even at work, which is notoriously hard on the battery due to being so well insulated.
I've had ZERO issues with the SD card so far, and it's a huge mystery what exactly is causing that. I ODIN'd the leak an hour after it was posted, then the NamelessV4 rom, then the NamelessV4.1 and haven't had a single issue. There needs to be a better process of defining it, and I'd be willing to bet it has something to do with the recovery the person used when it was flashed.
sarkozy said:
I've had ZERO issues with the SD card so far, and it's a huge mystery what exactly is causing that. I ODIN'd the leak an hour after it was posted, then the NamelessV4 rom, then the NamelessV4.1 and haven't had a single issue. There needs to be a better process of defining it, and I'd be willing to bet it has something to do with the recovery the person used when it was flashed.
Click to expand...
Click to collapse
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
xwhofarted said:
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
Click to expand...
Click to collapse
That's definitely what I'd be leaning towards. I also took the added (though not really needed) step of using the GB root exploit app, and confirming all was well before ever flashing CWM3.xx in ODIN, then going onto the nameless ROMs. I've actually tried to re-create the problem since I stuck in a spare 4GB card waiting for it to happen, but nothing so far.
Everything is so new, it's really all speculation for the time being. I personally don't think it's the ROM or the leak causing the problem, although it's obviously a factor. There are so many different combinations of recoveries being used (as if all of us read directions in full) and ROMs were flashed in different sequences that it's impossible to nail it down.
Aside from disabling auto rotate, I've had no complaints about the leak or ROM. I ran CM7 forever on my Eris before getting this Fascinate, and while I like it, it's a pain to deal with the missing functionality at times.
xwhofarted said:
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
Click to expand...
Click to collapse
I went from stock odin to nameless and my card was eaten alive...I followed the steps exactly as listed not missing one thing. So it has nothing to do with flashing from another rom
detox07 said:
I went from stock odin to nameless and my card was eaten alive...I followed the steps exactly as listed not missing one thing. So it has nothing to do with flashing from another rom
Click to expand...
Click to collapse
So, immediately upon flashing the sd card was corrupted?
It'd be nice if there was more cooperation among everyone to figure out the common problem. It seems like for all the trouble reports, there are as many or more of us with no issues. I can't see anything in logs that would tip off a problem, so it needs to be someone who has the issue.
I'm still leaning towards it being a recovery issue. It's odd that some people are saying the files still appear on the sd when viewed through the CWM interface.
Sent from my SCH-I500 using Tapatalk
Man, that would be awful if the CWM we were told to use is what is killing the SD cards, and a diffr version would have worked :O
I used the CWM linked in the nameless thread and no issue so far, but only 2 days so far.
I have around a strange persistant problem.
I have around 250MB of internal app storage space left and used about 650Mb of storage of apps on my external 32Gb SDHC card.
I am using autostarts and task manager to manage the start up of apps and stop things running which works really well at prolonging battery life to the point where I reach a good 14 hours with heavy use on battery (I have five e-mail accounts pushed all sorts of widgets and use the phone fairly heavily on an average day, admittedly I get a little less if I use multimedia to any extent) I am using a stock 2.3.5 build from which I have removed some bloat stuff so I have about 35MB of rom storage left. It's rooted and has CWM installed etc.
In total I have something approaching 650 app elements in Titanium Backup depending on what I do or dont have installed at any given point.
Without the SD card the phone boots fine everytime. With the SD card in depending on the amount of .asec files in the .android secure folder the phone will often boot up and then during the processes after boot semi crash. By this I mean it will boot up then about 2-5minutes during the afterboot it will stop working and drop in a loop where it is still trying to run after boot process like scanning for media and stuff but loses connection with the carrier and then loops. Removing the sdhc card and moving some of the .asec files out of the the .androidsecure folder usually fixes this. It does not come up with safe mode or anything like that.
Has anyone else experienced this? Have I simply reached the limits of what the phone can do? My guess is that the problem lies with the process of copying/unpacking the .asec files into the /mnt/asec structure?
Can anyone offer any useful advice the 32Gb SDHC card is only class 2 (all that was available when I got it) I am thinking a faster one MIGHT solve the issue but that seems only a possibility and investing in a new card simply to find out it doesnt fix the issue would be a relatively expensive mistake. Has anyone else found similar limits?
You realise that's intimidatingly long to read right? Please write in shorter forms.
Sent from my GT-I9100 using XDA App
ionious said:
You realise that's intimidatingly long to read right? Please write in shorter forms.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Not exactly helpful... Its far better to have a decent descriptive long post than people who writes "I have tons of apps but I get problem with connection".
@op I also have a tons of apps, fairly close to the amount you have, but still have quite a bit of space left, do you make a lot of backups and such? Check your SD card, because I remember a post here saying that deleting files within the lost folder can save space. (some people lost GBs, some just a few MBs) Best if someone here can confirm its safe to delete the files within though.
A known problem with some phones is 32GB cards some work well others dont some phones play up others dont .64GB even worse .
jje
Hmmmm seems like you are stressing the filesystem's/IO scheduler's timeout limit to the max with a class 2 card.
I would recommend you doing two things:
a) You have your phone rooted, try installing SiyahKernel, Voltage Control and change the I/O schedulers - thru set on boot -> init.d script (try alternating between noop, sio, bfq and VR), if that still doesn't help, try adding Thunderbolt Scripts as well - especially the remount script via script manager (links in my sig).
b) Try a different rom perhaps? Stock ROMs are not the most optimized things under the sun in terms of SGS2... back up your media to your PC, do a nandroid/titanium backup to your external sdcard and try flashing another rom. If it doesn't work, you can always restore the nandroid.
Hope it helped somewhat ^^
Thanks for the advice guys, think I might see if I cant test a faster card off a mate see if that helps.
Otherwise I will try that syrah kernel and scripts, not too keen to go for custom roms my experience of them with the galaxy s was they all seemed to have a major bug that I couldn't live with I always ened up back on stock with mods. Haven't really tested any on the s2 but if I were to I would need to be very stable with very few bugs. I also kind of like some of the samsung stuff? for example I'm using a hack versions (fragg0rs) of TW4 with it I can run the buddies now widgit from the original galaxy s and I love that. nearest thing I can find to the carosel I used to get on the samsung omnia i8910 (great phone badly let down by symbian)
To the guy that criticised the length of the original post on top of what else that has already been said, do you have the first clue about troubleshooting? especially an issue that is not referenced anywhere else? The golden rule is the more information the better. This is an issue I have been working around now for several months, I have been searching for similar (on and off not obsessively) issues posted anywhere and found nothing that helps but thanks for your rather pointless input stick to helping with the noob posts eh?
This is known problem. I have this problem too.
Several threads already talked about this since long time ago.
Here are some of threads exactly describing same problem with OP:
http://forum.xda-developers.com/showthread.php?t=1285844
http://forum.xda-developers.com/showthread.php?t=1102920
http://forum.xda-developers.com/showthread.php?t=1328191
http://forum.xda-developers.com/showthread.php?t=1446961
That last one is the thread I created last month and still active until now.
So here is the summary:
- This problem is side effect since ROM version 2.3.5.
- Version 2.3.4 and earlier does not have this problem.
- This problem still exists in ICS LPB leak
- It seems that Samsung does not know about this problem.
The only workaround solution:
- Downgrade to version 2.3.4 or below
For us who have this problem, please add your post to the thread I created above (http://forum.xda-developers.com/showthread.php?t=1446961) and rate high to keep the thread alive so it will get attention from many users and hopefully from Samsung.
you just saved me money buying a new card thanks for that.
Today I got the dreaded notification that has haunted my past xperias for years, you have low storage memory available
I'm an app hoarder and keep apps ill probably never use for months.
I remember seeing an article somewhere that moving apps to the sd card can really slow down your phone. I hope that this won't happen to my phone and am wondering if anyone else has moved apps to internal storage and does it affect the speed?
My xs has been very good to me and barely ever lags, something that I have never experienced unfortunately, I hope it stays that way :S
In short...
Q. Does moving apps or anything in general to internal storage affect the speed of the XS? Have you noticed any difference?
Bump, why isn't anyone answering :'(
theXperiance said:
Bump, why isn't anyone answering :'(
Click to expand...
Click to collapse
because your question is easily google-able... heck even if u're using a little logic, u can answer the question urself.
A: the answer is NO. it's in the same memory chip (the 32 gB one), so the speed is must be the same. the difference maybe will come in the filesystem (ext4 v fat32), but afaik the speed different is really minimal (if any )
So I checked my kernel setting earlier today to tweak some things, and I notice that my cpu is always running all 4 cores, all of which are are running at the highest frequency. I'm using the stock kernel from the official cm builds, and I even updated to make sure it wasn't a rom issue, I've had this device for over a year and it's never done this, and it's really eating my battery up now, anyone have any suggestions for me?
Edit: I've noticed that taking my micro SD card out seems to solve the issue, why would my micro SD causing so much strain on my cpu? I've had the same card for three years and two different phones and never had this problem till now and I've noticed under my battery settings that "media" has killed 20% of my total battery and I've literally used no media at all, I've tried wiping my cache/dalvik, I've tried reflashing my rom, nothing works, any help is appreciated
Common issue with sd cards. I used to get that problem a lot on my Samsung phones. Sounds like your card has a lot of stuff in it and something in it is not playing well. Time for a clean up. That's the only suggestion that ever worked for me.
Sent from my SM-N915P using XDA Free mobile app