Related
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.
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
The devs would say do a full format and flash and see if it still happens.
Sent from my LG-P500 using XDA App
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Try tuning down your overclock frequency... if you have overclocked it... it sometimes happens cuz of that... if you havent overclocked then theres some other problem...
Sent from my LG-P500 using xda premium
samrox144 said:
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Click to expand...
Click to collapse
I've done that, but does logcat hold on to recent logs automatically, or do I have to turn on "save to sd card"?
I think I might be having this same issue. I left my phone on and plugged in to charge not even for a half hour or less then I came back to it later and pressed the power button to try to turn it back on but it wouldn't turn on. Then I pressed and held it a second and it wouldn't turn on. I unplugged the battery then plugged it back in then it powered up fine. I seem to be having this issue every once in awhile and I am not quite certain why it is doing this. Also it seems like it has an issue with charging on my computer. I plug it and it the computer is telling me that it can be connected to a higher speed port which makes no since as I have 2 usb 2.0 ports and 1 usb sata port. But basically I plug it in with a full charge and it has no problem keeping it charged but when it ends up going down to at least 50% the charge just keep deceasing and never charges. I just hope that I can make it stop this as it is getting quite annoying maybe it is just the battery or something but I can't see how as it isn't even 6 months old.
I've tried using Logcat but unless you set it to save the log every few seconds it doesn't help. If there's an error it doesn't get caught by Logcat because whatever it does, it turns off the whole phone.
What are you overclocked to?
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Oneiros42 said:
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Click to expand...
Click to collapse
Well then. I don't know. Have you tried reflashing the ROM?
Not yet. I was hoping Mik's CM7 6.6.1 would have been declared stable by now, but I guess I'll have to settle for 6.5.8.
Quick off-topic question: ADW Launcher always comes to a grinding halt immediately after a reboot, to the point it gives the force-close option window. Is that because there are widgets installed to the partition on the sdcard, thanks to app2sd? I checked under applications and it says they're installed to the phone, but I thought I heard that app2sd (I'm using Darktremor's, as suggested by Mik) effectively takes the option out of your hands, making it moot. If that's the case, how do I delete the partition, since I'll be doing a full wipe and reinstall when I flash the ROM again.
I don't play games 2
Dammit! Yesterday I did a complete wipe (return to factory, wipe dalvik), reformatted the sd card, and updated the ROM to 6.5.8 and it just shut down on its own again. I even saw it happen... while it was sleeping, I saw the buttons light up and blink once or twice, then it shut off. The screen stayed off.
I did a clean install and haven't touched the clock settings. I reinstalled my apps of course, but I don't have anything that runs constantly in the background that I'm aware of. I installed ADW Launcher EX, I don't know if that matters.
Does this mean it could have a physical fault somewhere? I'd really hate to have to go through the hassle of reloading the LG stock ROM and unrooting it (that's possible, right) to send it in for repair.
I had the same problem with gingerbread and the related roms.
But my problems were about the overclock frequencies. I used the italian rom GingerLoL 1.5.2 and I set the frequencies in this mode: 320-729 smartass v2. No more problems.
I don't know why I hadn't this problem with Froyo's rom...
I'm tempted to fiddle with the clock settings now that I know just reflashing the rom doesn't help. It seems by default CM7 is set to 245-600mhz, with the "smartass" governor. I figure I might as well bump the low end to 320, but where's the "v2" version of smartass you mention? It's not in the list.
I have exactly the same issue! Tried 3 different firmwares, 3 different roms and different kernels too, but it seems to reboot by itself and also really slow sometimes to scroll. Can't solve this... maybe some hardware troubles? some new defected cpu ? I sent this phone 1 month ago in warranty and they changed me the logic board, then when i got it back, it started to have this trouble. Before this, never had this trouble.
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
FPChaim said:
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
Click to expand...
Click to collapse
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Oneiros42 said:
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Click to expand...
Click to collapse
I'm my case the phone boots and when it load all the aplications it reboots... but one time i quickly go to setting>applications>manage applications and there has less than 1 mb... so i think it was building something like caches... I wiped everything and my phone worked as usually... but i installed a lot of things again and it keeps rebooting and rebooting... i wiped everything again and installed just few things, leaving my phone to have high internal memory... it worked!(actually i have 42 mbs of free space and it never happened again)
I'm posting this here because I hope some devs might be able to get a handle on the problem. I think it has something to do with the launcher.
Since I upgraded my phone to a 2.3.4 ROM, I've had constant problems with its randomly rebooting, or occasionally just freezing. (I say "rebooting", but it always gets stuck in a boot loop, and so it might as well be frozen.) The first ROM was Synergy, but I've had the same trouble on Warm, and with three or four different kernels (OC'ed and not OC'ed) on each of those ROM's. In some configurations it's better, and in some it's worse, but I've nearly always had the reboots happen at least once a day. Sometimes it happens while charging, sometimes while it's not; sometimes it happens while I'm touching it, and sometimes when I haven't touched it in hours (kind of annoying when it's my alarm clock--I missed a meeting last week). There's not a lot of consistency in when it happens, though I should say, for the record, that I've been using Launcher Pro the whole time.
Obviously, I'm not the only one with this problem: for some, like me, it started with 2.3.4 (including, in many cases, the stock OTA); for others, it started when the phone was first released; while for others, it's never happened at all. The fact that some people haven't experienced it at all may mean hardware has something to do with it, and I even read one account of a guy who took five different phones back to Sprint for replacements before finding one that worked right.
After searching high and low, I found a thread on the Sprint Community forums that suggested editing the data.prop file to keep the launcher in memory constantly (Look here and scroll down to post #9.). I tried this a couple of days ago, and it hasn't fixed the problem, but it did dramatically reduce it: I went from rebooting every two hours to rebooting once or twice a day.
I've noticed one other interesting thing: a couple of months ago, I started playing Godville, and I've been propping the phone up next to me and letting it idle with the screen on (while on USB), so that I can glance over every once in a while to see if anything is happening in the game. I've noticed that, every few minutes, the home screen wallpaper briefly replaces the app I have open; it happens so fast that I can't tell for sure if the whole launcher is coming up, but I suspect it is. I wonder if this constant yanking of the launcher into the foreground might be the source of the instability.
my mind is like..... blowwwwn
---------- Post added at 01:37 AM ---------- Previous post was at 01:28 AM ----------
no but on a serious note man... many people have had problems with reboots since the launch of the 3D, which was 2.3.3 based. I doubt that was the issue (launcher, your update, your games... gnomes...)
i would say flash the RPM PGIMG86423million update whatever that number is for the bootloader update.zip, and see if that rids you from the reboots.
for me, i fixed my reboots by getting a new SD card... i had the same issue when i first got my 3D late in july. Did it both on 2.3.3 base, and 2.3.4... it occurred to me one day that a bad disk would cause system reboots... and not being able to change out the one built into the phone... i opted for the SD card because it was cheap and i wanted a better one anyways. reboots went away immediately.
it also never occurred to me initially that my SD had been bad for a long time... not just when i had my 3D.. on my previous phone (samsung moment with froyo), whenever i would move apps to the SD card, i would always get some kind of error message. trying to move them a couple times would always successfully move the app(s) to the SD card.. i figured this was a problem with the rom i was on (speaking of my samsung moment)...
then when i transferred my card to my 3D, same problem, along with the reboots, and a light clicked on in my brain and said "***k-tard, your SD card is bad. derp."
haven't had a single reboot since then. i even wonder if the paramount number of people having reboot issues on the 3D was due to HTC possibly shipping them with defective SD cards...
just something to mix around in your brain for a bit...
Yeah, I considered the SD card as a problem, but the reboots happen even when the SD card is mounted as a USB drive. Also, a bad SD card wouldn't explain why keeping the launcher in memory dramatically reduces the problem.
I'll be giving it a try.
Just a side note. I've been using the stock kernel lately and havn't had a single reeboot. I'm on synergy rom and since he put back in the stock kernel w/ no OC I've had no issues.
I may try that, but it would be sad to not to able to OC a rooted phone. I'm starting to wonder if it's a bad internal flash drive, though.
You should try a stock ROM to see if that solves your issue if that's doesn't work maybe you have defective phone
Sent from my PG86100 using xda premium
All my problems went away when I used Senseless ROM. I think the kernel in the ROM is stock. It's been over two weeks since my phone has frozen on me and no more random reboots.
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
I'm having the same reboot issues. I've noticed a few things:
1. Doesn't matter what sd card or how new, my phone reboots unexpectedly
2. Phone ONLY reboots RIGHT when the screen times out. Only on Android 2.3.4 w/ sense! It does not matter what kernel. Whatever I do, all reboots are directly related to sense on 2.3.4.
3. The only solution I have found is to deactivate the screen time out or gut HTC proprietary sense from the ROM.
P.s. I DO NOT have problemswith any ota based off 2.3.3
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Click to expand...
Click to collapse
Tiamat isn't stable for me.
MTKnife said:
Tiamat isn't stable for me.
Click to expand...
Click to collapse
Nor for me. It causes daily hard lockups that require a battery pull on my phone. Tiamat exhibited this on multiple ROMs for me.
I think trying a largely stock rom is a must as a start to tracing your problem. So is incremental additions of apps, tweaks, etc. Basic debugging and defect isolation stuff.
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
What about bcblend by mwalt? Senseless rom has been using that for quite some time and I haven't had any issues. When it was switched to tiamat for a short time (2.5 & 2.6, i believe) I had problems with lockups and reboots. Reboots would occur when the screen timed out every once in a while.
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Tiamat has not been stable for me either. I tried many different rom and kernel combos and am still having the issue. I noticed it is mostly happeneing when the phone is plugged in. but it also happens sometimes when im on a call. So there has to be more than one issue one being the proximity sensor and i cant figure out the other ive hset charging profiles to 384max and 198 min and other low clock speeds to see if it would help. Also set a temp profile to underclock when its over 38.0 celsius. Right now im running olympus trinity xe titan i ran it for a few days with mild anthrax and it only froze/rebooted a few times a day. I tried the anthrax kernel and it rebooted twice the first half hour so i flashed tiamat last night. Im trying to give it time to settle in but it just rebooted again when i plugged into pc. I bought my phone used and rooted before i even activated it so i dont know if this is something kernel/rom related. I started another thread a few days ago about this and the few responses i got were people running stock romand kernel not rooted. So i guess all we can hope for is the devs to figure it out or sprint to give us an ota that fixes it since im starting to belive its a hardware issue.
If you're on titan freezas is recommended.
Sent from my PG86100
I saw a few people talking about that but I thought they were talking about for when he released Hades. I'm gonna find the dl link now thanks.
Sent from my PG86100 using XDA App
Cabe24i said:
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Click to expand...
Click to collapse
Not for that long a period, no--unfortunately, I haven't been in a position where I could give up most of the use of my phone for that long. Once I have grades submitted next Monday, I can probably do more methodical testing.
I'm still freaked out by the way the launcher pops up every few minutes, though--has anyone else ever seen anything like that?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to General
One of my favorite rom and kernel combo's is infected eternity with anthrax but random reboots are common for me with any sense based rom. I run MIUI with whatever aosp kernel and everything is flawless. Other than experimenting with kernels to find battery life, MIUI is the most stable rom I have used so far and is my new daily driver!
Sent from my HTC EVO 3D using xda premium
My evo also reboots and i havent rooted my phone at all. I did get a new SD card and that reduced the amounts of reboots i get! . Although, i still get a few every week.
hope sprint/person finds a fix for this soon.
Mine did it stock / rooted stock and viper ROM I an on fresh and so far smooth as butter ... Stock rooted was awful every time it would time out bam reboot
Sent from my PG86100 using XDA App
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.
Some of you might have encountered this, and some of you possibly could in the future (let's hope not), but this will hopefully be of help. I once had a problem with my Live with Walkman in which it boots up until it reaches the homescreen before entering a bootloop. Strangely enough, it also happened to two of my friends who owned SE 2011 MDPI devices as well. These are some of my observations:
Bootloops when network is in GSM (2G) mode
If in WCDMA/GSM mode, phone bootloops the moment 3G signal is lost
Phone works without SIM card, but bootloops when a certain load is placed on the CPU (rebooted when I played Minecraft)
With that said, I've tried formatting my SD card and resetting factory settings a hundred times over; I was even in between firmwares, ROMs, and kernels, but to no avail. In my desperation, I tried using the battery from my then-girlfriend's Xperia X8 (my phone and hers have the same type of battery, EP400), and it miraculously cured the bootloop. I did buy a new battery, and my phone was as good as new. When the same thing happened to my two friends, using a new battery also did the charm. There were a few problems with the new battery though. I'll list the possible solutions I've found.
BATTERY MISCALIBRATION (sudden drop to 0 or misreading)
Reason/s: It may just be a kernel problem, or your phone might be adjusting to the new battery.
Solution/s: Try installing a different kernel. If it does not fix this, drain your battery to 0, then charge it fully offline. Keep repeating until battery is calibrated.
NOTE: Battery calibration apps won't really do much - you don't necessarily need them.
Click to expand...
Click to collapse
SUDDEN REBOOTS
Reason/s: You're probably putting too much weight on the CPU or GPU (more likely if you're a gamer), or you might have overclocked your device and is using a governor that hangs around in the higher frequencies.
Solution/s: If you really are a gamer, I'd suggest using GB - you won't really need to overclock as it's great performance-wise. If you must overclock, never go beyond 1.4 GHz (this is the default CPU frequency of the Xperia Arc S), as it may kill your new battery. Also, try to avoid gaming or using your CPU heavily for long periods of time. Our phones need to rest too.
NOTE: For help on kernel governors, check out THIS AWESOME GUIDE by zhanjia.
NOTE: The said problem is more likely to occur on higher versions of Android, as they naturally consume more power, CPU, and RAM.
Click to expand...
Click to collapse
Other than those two, I've had no other problems. If this ever happened to you (again, let's hope not), always check the software first. If it does not fix the problem, you can try doing what I did.
P.S. I'm not saying that you should stick with Gingerbread if you encounter the battery miscalibration and the sudden reboots. You are absolutely free to use any ROM (we have a handful here on XDA, and we have our fantastic developers to thank for that). Cheers!