Related
Just my feeling...
Since I like Android more than WM now, so 24h are using Android.
I set my HD2 only on 2g in Android/WM(same usage), am I get wrong feeling the battery drop faster then WM?
Or Android run on SD so more power is used? Low power on WM run on nand ?
Any user get same feeling?
If real makes me waiting for nand much much...
Sent from my HTC HD2 using XDA App
On standby, we can assume we've all (except battery drain problems) reached WM6-level
When actually using the phone, another story.
- (I) have a very huge drain when using GGNav, Internet or when playing. HOWEVER, it may be...me, actually USING my phone a lot more since i'm not on WinMo anymore
naaah. ive always used win mobile a lot and never had problems with battery unlike android. Something is not perfect with it. when u turn on wifi or 3g the battery runs out so fast that i feel 1-2h using it would be enough to drain all the battery. In windows mobile i can use it for 2 days running the same types of application.
too bad i was going to stick with android till i grab one wp7 device.
Its a port on the hd2... you can't expect a port of android to run as well as a native device that has proper drivers. Android ports always tend to drain batteries quickly. They have done a really remarkable job getting android running as well as it does on the hd2... but its always going to be a hacked on port of android.
From what I can tell by watching the devs talk, the nand version seems just as power hungry as the Haret version. The SD card really doesn't use that much power. Everything gets booted into ram anyways, so the SD only gets accessed intermittently. Some SD cards seem to use more power than others.... but overall, I don't think the SD card makes a noticeable difference in power consumption.
We just need to hope for more improvements to be made in the kernel regarding power management... but you can't expect a port to run as well as a native phone... you will be disappointed.
Sent from my HTC HD2 using XDA App
This topic gets created like every week.
There's really no advantage at all...the devs are just working on the NAND version for android just for fun.
zarathustrax said:
Its a port on the hd2... you can't expect a port of android to run as well as a native device that has proper drivers. Android ports always tend to drain batteries quickly. They have done a really remarkable job getting android running as well as it does on the hd2... but its always going to be a hacked on port of android.
From what I can tell by watching the devs talk, the nand version seems just as power hungry as the Haret version. The SD card really doesn't use that much power. Everything gets booted into ram anyways, so the SD only gets accessed intermittently. Some SD cards seem to use more power than others.... but overall, I don't think the SD card makes a noticeable difference in power consumption.
We just need to hope for more improvements to be made in the kernel regarding power management... but you can't expect a port to run as well as a native phone... you will be disappointed.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
stop spewing more BS than what we already have. I think you need to learn how a RAM operates when you say "everything gets booted into ram."
lude219 said:
This topic gets created like every week.
There's really no advantage at all...the devs are just working on the NAND version for android just for fun.
stop spewing more BS than what we already have. I think you need to learn how a RAM operates when you say "everything gets booted into ram."
Click to expand...
Click to collapse
Most people in the vouge forums say they have much improved battery on nand than from sd. However there are some that have noticed very little difference.
http://forum.xda-developers.com/showthread.php?t=645308
That means driver not nand...
Hope xda can get better driver for more using time in future.
Sent from my HTC HD2 using XDA App
lude219 said:
This topic gets created like every week.
There's really no advantage at all...the devs are just working on the NAND version for android just for fun.
stop spewing more BS than what we already have. I think you need to learn how a RAM operates when you say "everything gets booted into ram."
Click to expand...
Click to collapse
What BS? Why don't you correct it if there's something incorrect about what I said instead of just saying its BS. If I'm not understanding it correctly or not explaining it correctly, I would like to know.
I didn't use the right wording when I said everything gets booted into ram... I meant it is loaded onto ram. Everything runs from ram, whether its stored on SD or nand.
Sent from my HTC HD2 using XDA App
zarathustrax said:
What BS? Why don't you correct it if there's something incorrect about what I said instead of just saying its BS. If I'm not understanding it correctly or not explaining it correctly, I would like to know.
I didn't use the right wording when I said everything gets booted into ram... I meant it is loaded onto ram. Everything runs from ram, whether its stored on SD or nand.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Where do you get your facts about SD cards dont consume that much power?
When you say "everything gets booted to ram," do you really know what you're referring to?
And how are the SD card being accessed? and if it happens only intermittently, why would the Devs care so much about NAND?
SD cards don't make noticeable differences in power consumption? Better tell the devs to stop wasting their time with NAND development and start working on better drivers, then.
Quick summary: don't be confused with an OS and its bootloader (which is the main part of the bolded section). You've been here for over 3yrs so you should know the difference. In case you haven't, do a quick search around the boards. Only a bootloader gets loaded onto the RAM, the rest (i'll let you figure out what that refers to) runs on the SD card, which is why NAND development is such a BIG DEAL.
Nothing runs from SD or nand... they are persistent storage and are too slow too run anything from. Everything runs from ram. The SD or nand are accessed when data needs to be read or written from them. The os is running from ram... when you open a new app, the necessary data is read from the SD or nand and moved to ram to run. That's why opened programs take up ram and people kill tasks to free up ram. The SD card is not constantly being used when android is running. If it was, then all this power you say that the SD card is eating up would still be sucking all that power while your phone is sleeping, as android is still running.
The SD card does use some power when it's accessed a lot... but it doesn't use that much power. I really don't think nand is going to affect the battery life as much as people think.
Sent from my HTC HD2 using XDA App
Hi every one!
I want to use Android on SD card, but the battery time is very low (~ 01day).
So, please help me select the best WM6.5 Rom for dual boot (maximum battery time & best performance)
Thanks you.
no one help me?
haihazin said:
no one help me?
Click to expand...
Click to collapse
I use energy rom reference series and sd android miui
Use radio 2.15.xx and turn off your 3g data when not used
Hope that helps you
Cheers
Let I try, thanks.
silverwind said:
I use energy rom reference series and sd android miui
Use radio 2.15.xx and turn off your 3g data when not used
Hope that helps you
Cheers
Click to expand...
Click to collapse
I'm a new member!
My HD2 T-mobile use radio 2.15.50.14
Should I need to up radio before up Energy ROM? Is it the radio best for SD android?
Thanks very much!
I know this is older, but for anyone searching this same subject, I figured I'd offer some info. I don't think this question can be answered as asked. There is no such thing as a "best" rom. In addition, as I understand it, the choice of Droid rom/kernel, and when that is started, is going to have more to do with battery use than the choice of WM rom. That said, I can tell you what I use. I run Core Cell Evo (6.5.5 base) V4.1 which includes a dual boot option built in. This is a Sense rom. With it I run a Droid SD rom from the same developers, Core Droid V0.8. I do have an HTC extended battery so I did need to update the Droid kernel to Hastarin v8.5.3 EB (with Extended battery support). If you can't find the kernel updater zip file, let me know and I'll send it to you. I also updated the WM rom to CHT and CHTE to v2.0 final (as opposed to the V2.0 beta that comes with the rom), along with updating CleanRam to V2.5 - as outlined here http://forum.xda-developers.com/showpost.php?p=16850333&postcount=1512 This combo as modified has worked well for me. Battery usage is not great, but not bad by any means. Keeping services shut down unless needed is probably the most important thing you can do. If I am running wifi and bluetooth all day, battery life is much worse. if you don't need data, shut it off, ditto wifi, GPS, and bluetooth. if you are not going to run WM other than as a boot shell, try this WM rom http://forum.xda-developers.com/showthread.php?t=776971 My one issue with an SD Droid rom is that you need to be careful about accidentally corrupting the SD card. I had to soft reset once while in Droid and after I did that my SD card was corrupted and Droid would not boot properly. Also several WM apps located on the SD card would not run either. I had to do a complete reinstall of both WM and Droid. This makes sense to me as the Droid OS is running on the SD card so it is reading and writing to it a lot more often. Anything that would interrupt while the card is being written to, could result in problems. So if you do run an SD Droid, be careful about shutdowns and card removal (virtual or real). I always use a full power off now when I want to reboot, never a reboot. I never soft reset unless I absolutely have to, and I never take the SD card out without powering down first, or disconnect the USB from the computer without "ejecting" the Card from the computer first (safe removal option works too). I run the stock TMOUS radio 2.15.50.14 I am very happy with this setup. I generally run bluetooth 3-4 hours a day (listening to my tunes) and the wifi all day (updating various things on a regular schedule such as email, weather, etc.) I do not use a wireless data service ever, and I only use the phone when I am away from home (we do not have cell service at my home). But my wifi use more than makes up for the lack of phone and data services. I also use GPS 5-6 times a day. My phone is seldom in full sleep mode during the day, it is always doing something. The HTC extended battery is a big help. The generic 3500mAh battery was not. It did not even require extended battery support from the kernel. It gave me an extra hour or two, max.
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.
Hi Guys,
I am on ICS 4.0.4 and my S3 shows 779 MB, which is always busied by 680 or so!!!
I checked an S2 with ICS 4.0.4 and the memory is 830, and is busied by 450 on average. (S2 has larger memory than S3 on ICS4.0.4???)
So what is wrong with the S3 memory? i keep on killing apps all day and night to bring it to 450 or around, I dont have too many programs, and, i am not using except two widgets, checking on the background processes annd programs, most of the system's stuff is running on its own, even if i freeze some using Titanium pro.
Anyone has the same problem (if i can call it a problem?!) is that normal??!
Why would you consider it as a problem? Android is best at multitasking. You don't have to kill apps, its the nature of the beast so to speak to have a semblance of the apps running in the background for your convenience.
Sent from my GT-P3113 using XDA Premium HD app
Bigger screen and stuff like Smart stay and S voice eat up extra Ram.
Yeah it's really dumb to kill apps and clear ram the whole time, phone will feel sluggish because it needs to fore up stuff all the time that would normally sit kindly and wait for you in ram... You are making your phone slow and killing your battery
Sent from my GT-I9300 using xda premium
Okay, i got it, No more killing APPS , now the question is, how come the S2 has more overall ram than the super S3, on ICS4.0.4??? considering the 779MB to the 830? its just a noob question
gennoz said:
Q: Whats up with the ram?
Click to expand...
Click to collapse
Q: What's up with searching the forum?
Why are people asking the same questions over and over again?
i flashed mine with stock I9300XXALF2 now my average ram usage has dropped by at least 150mb & is much snappier on the home screen redraw
goodie said:
i flashed mine with stock I9300XXALF2 now my average ram usage has dropped by at least 150mb & is much snappier on the home screen redraw
Click to expand...
Click to collapse
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Anyways, i found two posts, one about a stock ALF2, and the other talking about deoxed and oxed .
What is the difference between :
GT-I9300_WanamLite.Stock.Deodexed.XXALF2.NO-WIPE.zip
GT-I9300_WanamLite.Stock.Odexed.XXALF2.NO-WIPE.zip
gennoz said:
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Click to expand...
Click to collapse
Bullied?
Try reading the rules before posting. Rule number 1 is search before asking a question. Now you're asking the difference between odexed and deodexed... Do you seriously think you're the only person who has asked this? It's discussed EVERYWHERE!
gennoz said:
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Anyways, i found two posts, one about a stock ALF2, and the other talking about deoxed and oxed .
What is the difference between :
GT-I9300_WanamLite.Stock.Deodexed.XXALF2.NO-WIPE.zip
GT-I9300_WanamLite.Stock.Odexed.XXALF2.NO-WIPE.zip
Click to expand...
Click to collapse
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
The search on the site is horrible. I use Google and type xda after anything I'm looking for
Sent from my LG-P999 using XDA App
Roastario said:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
Wow, seriously thanks for your time
Query on RAM....
norpan111 said:
Yeah it's really dumb to kill apps and clear ram the whole time, phone will feel sluggish because it needs to fore up stuff all the time that would normally sit kindly and wait for you in ram... You are making your phone slow and killing your battery
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Dude... My s3 ram in task manager is showing 883..... previously it was 779mb.... i donno wat would b the cause for this.... i have updated to jelly bean.... please ans my query....
Roastario said:
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
I suppose "standard ROMS" have no apps or anything in the "Dalvik cache" ? (as all apps have "stand-alone" APK's ?) ... correct ?
well, I guess its widely know how android manages memory, and clearing ram is more of a performance inhibitor than a booster. I gave up all hope when I took my s3 to the service center and was given the solution of clearing the RAM repeatedly to solve the horrible ram issue.
the problem i was and still am facing is, the ram usage increases automatically within few hours of usage with hardly any apps installed. its extreme as it crosses 790mb and stays in that range. whats bad is apps keep on restarting in the background, phone slows down terribly ( switching between apps, moving out of an app just to stare at the app drawer 3-4 secs for all the apps to load, even the keyboard takes time to pop up). So moderate ram usage is good, but high ram usage is bad especially when it causes to slow down basic use. now what problem i am left with is deciding whether to root and flash a custom ROM and void the warranty on my one month old device, as both the times i revisited the service center the only thing the guy did was format and reload the firmware, which didn't solve anything. this was prevalent on stock ICS as well after the JB update via kies. as a last resort I am thinking of trying an official firmware from another region. as Indian one was causing the issue. my friend got his s3 from saudi and he hasnt had such severe problem(certain sluggishness is acceptable on a bloated stock firmware). so i am thinking of flashing that firmware. is it safe to do that? and i wouldnt need root access for that right, only odin and the firmware correct?
noobee1 said:
well, I guess its widely know how android manages memory, and clearing ram is more of a performance inhibitor than a booster. I gave up all hope when I took my s3 to the service center and was given the solution of clearing the RAM repeatedly to solve the horrible ram issue.
the problem i was and still am facing is, the ram usage increases automatically within few hours of usage with hardly any apps installed. its extreme as it crosses 790mb and stays in that range. whats bad is apps keep on restarting in the background, phone slows down terribly ( switching between apps, moving out of an app just to stare at the app drawer 3-4 secs for all the apps to load, even the keyboard takes time to pop up). So moderate ram usage is good, but high ram usage is bad especially when it causes to slow down basic use. now what problem i am left with is deciding whether to root and flash a custom ROM and void the warranty on my one month old device, as both the times i revisited the service center the only thing the guy did was format and reload the firmware, which didn't solve anything. this was prevalent on stock ICS as well after the JB update via kies. as a last resort I am thinking of trying an official firmware from another region. as Indian one was causing the issue. my friend got his s3 from saudi and he hasnt had such severe problem(certain sluggishness is acceptable on a bloated stock firmware). so i am thinking of flashing that firmware. is it safe to do that? and i wouldnt need root access for that right, only odin and the firmware correct?
Click to expand...
Click to collapse
Generally RAM usage depends a lot on running widgets.
I personally use only one widget on screen at all times. (Google search) which is enough to get the job done for anything. And I run only 3 home screens
I would usually have about 200 free ram
Also Im on Omega 34 rom which is by far best (In my opinion for RAM management). It automates in such a way that 200mb ram is free at all times.
I really dont care much about warranty ,the first thing I do when I get an android device is to root it. (You do know you can unroot right ?)
So if RAM is really so important to you its best to root.
corleno said:
Generally RAM usage depends a lot on running widgets.
I personally use only one widget on screen at all times. (Google search) which is enough to get the job done for anything. And I run only 3 home screens
I would usually have about 200 free ram
Also Im on Omega 34 rom which is by far best (In my opinion for RAM management). It automates in such a way that 200mb ram is free at all times.
I really dont care much about warranty ,the first thing I do when I get an android device is to root it. (You do know you can unroot right ?)
So if RAM is really so important to you its best to root.
Click to expand...
Click to collapse
yes I am well aware of rooting/un-rooting and other basics, had done all that on my S2(i9100), also found it more fun and efficient than stock but time is the only factor that's stopping me from experimenting. and thanks for the omega tip. I am certainly going to flash a custom ROM, after trying out few official ones, When I do, I would definitely go for Omega, alot of people recommending that one.
Omega is good as is WanamLite, Foxhound and Hyperlight. Smoothest I've used were Foxhound and Omega although I'm running WanamLite at the moment. Smoothest version I've used.
Has anyone tried either of these on our phone? I somewhat understand how fstrim works, but a bit confused on whether Forever Gone does the same thing (people claim to get the same results). I tried Forever Gone first and feel like my device has been zippier since, but I'm not sure, could be placebo. I ran LagFix the day after, so can't say either way.
http://forum.xda-developers.com/showthread.php?t=2104326
https://play.google.com/store/apps/details?id=com.kovit.p.forevergone&hl=en
I thought I'd post this for discussion, experiences, etc.
Right now I'm running seeder and lagfix, using both together with 1.72 overclock my device has never been smoother (battery life is better since i'm underclocked as well). Both might be overkill especially since our newer version of android should be cleared of the problems. But it seems to make an impact on my device. As for forever gone, it seems like all it does it clean up your sd card (internal and external? not sure if it does both, will try later) but that probably wouldn't affect the actual speed of the device unless you accessing videos, pictures, cached files from the sd (game files i.e.). Lagfix seems to be specifically for the phone main used partitions (system, data, etc.)
But I'm always willing to try out new things =D
Thanks for the post.