Related
Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.
I use either the aggressive or custom depending on the Rom honestly. DC ROMS= Aggressive. FRESH ROMS= strict. and all others = custom
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
I have the damagecontrol rom and I dont know if it came with auto killer or what...I restored my titanium backup and all i know is i dont have it now...is there an apk floating around for it?
Try the market
I thought it was a custom xda application. I didn't see it in
the market.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?
I used either the aggressive or strick on Fresh 2.0d. So far everything is running the smooth and fast. This the way HTC hero should have come out of the box.
What does each preset do? Is this for speed or battery life or both?
flammenwurfer said:
I've been using Aggressive on Fresh 2.0d and it's been running great.
I tried Moderate for a while at first, but Homerun Battle 3D wouldn't even startup consistently. Once I changed it to Aggressive it has been working great.
Another quick note. I know Autokiller is supposed to reapply the settings on boot, but I'm not sure mine is. I haven't rebooted for a day or so, but the last couple times I rebooted I couldn't get Homerun Battle to run. Then I went into Autokiller and applied Aggressive again and it would start. Anybody else having similar experiences?
Click to expand...
Click to collapse
Damn. I wish Homerun Battle 3D would run great for me. Problem is I get crummy service at work and with it going in and out of 1x and EVDO, causes the game to lag.
I have noticed sometimes on first opening HRB, it force closes but it always opens the second time.
james33440 said:
Those of you running auto killer in your roms, did you use the aggressive settings or custom?
I'm just curious to see if anyone increased the auto kill.
Click to expand...
Click to collapse
i'm running aosp 1.6 from gbhil and i used custom autokiller settings.
the way i see it they made these phones with all this ram may as well use it, what good is it to have all this free ram?
1536,3072,4096 (all default) then hidden app is 7680. content provider is 8960 and empty app is 10240. i normally run around 40-45 free ram thats about where i like it. the phone still runs fine all the way down to 20mb free but any less than that it starts going downhill.
so, im MB my settings are 30 then 35 then 40. runs great!
yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.
flammenwurfer said:
yeah, I get some lag now and then if I don't have great service. Playing offline seems to work fine though. I think it's just the online play that it effects. A co-worker has a Droid and his lags when playing online as well if he's in a spot without good service.
Click to expand...
Click to collapse
Well, mine actually lags on offline play too. As long as the phone isnt switching back and forth, it runs smooth.
How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail
vedwed said:
How can you remove this autokiller crap, I have tried freshkitchen, uninstaller, and from settings-applications menu, all to no avail
Click to expand...
Click to collapse
Using command prompt (adb)
adb shell
# rm Autokiller.apk
troyboytn said:
Using command prompt (adb)
adb shell
# rm Autokiller.apk
Click to expand...
Click to collapse
Ohh thanks much appreciated.
I did not try that way, I figured if it couldn't be done in freshkitchen then it was just built into the rom. Thanks much again
Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.
Sawawa said:
Just stop using task killers entirely. This isn't Windows Mobile guys. You're getting all OCD in here about the placebo effect.
Click to expand...
Click to collapse
Autokiller does have a built in task killer but its real use is to tweak memory settings at boot and then shuts itself down (so Android can take care of the rest). So, in reality it is not really a task killer per say.
Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.
Sawawa said:
Fair enough, but it's still entirely pointless. I trust the device manufacturer and Android far more than I ever would the random numbers that I might otherwise delude myself into believing were somehow better.
Just let Android do its thing all of the time. It doesn't need any additional help (particularly with the process management in 2.1). Stop including this garbage in ROMs.
Click to expand...
Click to collapse
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that
Jus10o said:
It actually very useful for making roms run smoother. By default the memory numbers are very low, which lets a TON of apps run at the same time. The higher the memory numbers the more it ends apps that you werent even using. It gives what you are currently running or recently ran more priority. Even if you dont use AutoKiller, which is just an app to adjust the memory setting, every rom comes with an edited memory setting other then htc's default. Its most commonly known as gumbo's memory settings.
Also in AutoKiller you can adjust the settings to default, or just really low like htc would have them set.
Its really not a bad thing to include in roms because most people want there rom to be smooth and as close to lag free as they can get. AutoKiller helps achieve that by ending stuff you dont currently have up making the phone run faster. Thats if you have a decently set setting. I run mine on optimum, and it doenst close unnecessary things like if im on the web it stays running.
I can understand an app like Task Killer which just terminates the apps. AutoKiller is just setting the memory setting of your phone, which end apps the same way as if the phone were running normally. Just if the numbers are higher the more apps it will end quicker freeing up more space.
Also you really trust htc and sprint?? haha good luck with that
Click to expand...
Click to collapse
Either way it should be a choice made by the USER not someone who decides what I need or do not need on my phone. What I choose to have running or not running, there is no need for this garbage for the average joe who just wants something that does not look and feel like Sprint garbage. If its such a great and useful thing put it on the market and let users have a choice.
I'm having some awful slow-down issues with my N1. Like, 3 second delays between clicking widgets and their intended effect, and even longer switching between home screens (if the screens switch at all).
There's no auto task-killer enabled, I've very recently wiped and re-installed CM, and cleaned out my unused apps. I've got around 200MB of RAM free, constantly. SetCPU is keeping my processor at 461MHz or higher. This is obnoxious as balls, and I can't think of much. :s
Any suggestions?
I'm running CM 5.0.6, btw.
i have the same problem
My N1 is not rooted and I am experiencing slowdowns. When opening txt messages now take 3-5 seconds, and typing completely locks sometimes for 20 seconds. Gmail now takes 5+sec to open and other apps are also seeing this. I just had 10+ programs update themselves and all these issues started appearing suddenly. Also when exiting apps my desktop will be blank for 3-5 seconds. This just happened all within the past 2 weeks or so.
reddragon72 said:
This just happened all within the past 2 weeks or so.
Click to expand...
Click to collapse
Yeah, the issue is very recent for me too. Last week.
I am wondering if Google sent out an OTA that is prepping the phone for the 2.2 update??? The reason I say this and not point to an app is the simple fact that I have all my apps stopped completely and the issues still exist.
reddragon72 said:
I am wondering if Google sent out an OTA that is prepping the phone for the 2.2 update??? The reason I say this and not point to an app is the simple fact that I have all my apps stopped completely and the issues still exist.
Click to expand...
Click to collapse
Mmm, I dunno about that. I'm running CyanogenMod. I don't get OTA updates. Do you remember, recently, getting an OTA?
Unless it was pushed inside of a market-updated Google app (uhh.. No.), I wouldn't have got it.
Zak Jones! said:
SetCPU is keeping my processor at 461MHz or higher.
Click to expand...
Click to collapse
You set your CPU at 461Mhz?? Sure it slow down and lagging. What the point buying a 1Ghz processor phone decide let it run at 461Mhz?
Check the profile if you are not set at 461Mhz, maybe accidently make a profile setting and enable.
Or set your setCPU setting from on demand to on performance.
What kernel are you running?
Andrewtst said:
You set your CPU at 461Mhz?? Sure it slow down and lagging. What the point buying a 1Ghz processor phone decide let it run at 461Mhz?
Check the profile if you are not set at 461Mhz, maybe accidently make a profile setting and enable.
Or set your setCPU setting from on demand to on performance.
Click to expand...
Click to collapse
I think he's setting the minimum at 461 hence the "or higher" part.
Well, I can't actually help much except to suggest that perhaps you could try Kang-o-rama (see my sig) and see if that works. It's a stable and fast bundle with no apparent lag. At least I know that setup works.
If you did proceed then posted your results in that thread I might be able to assist. You shouldn't be experiencing lag with this phone... and if you still are after installing Kang-o-rama we could look at logs for you.
No promises but I know Kang-o-rama works...
Success? Sorry for the laggy reply.
JCopernicus said:
I think he's setting the minimum at 461 hence the "or higher" part.
Click to expand...
Click to collapse
Yeah, Copernicus is right, it's at a minimum of 461MHz (now 499MHz.), with a max of 998MHz, running 'on demand'.
antoniouslj said:
What kernel are you running?
Click to expand...
Click to collapse
I'm using whichever kernel comes with CM. (2.6.33.2 is specified in the relevant section of his changelog.)
djmcnz said:
Well, I can't actually help much except to suggest that perhaps you could try Kang-o-rama.
Click to expand...
Click to collapse
Yeah, won't lie, I'm sick of reinstalling all my stuff, so I don't want to do it again. If I keep having issues, I'll look into it though.
Just last night, I wiped both the data partition (factory reset?) and cleared the Dalvik(sp?)-cache. Started from scratch (without Google settings sync.), and reinstalled apps one by one. SO FAR, I haven't had the slowdown, but who knows. All I've got installed yet are the applications that I actually had desktop shortcuts to. (I didn't have very many more, but these are the ones I actually used frequently.)
Anyway, yeah, I'll see how this goes.
K, need a suggestion.
Zak Jones! said:
Anyway, yeah, I'll see how this goes.
Click to expand...
Click to collapse
Sooo, it's not going. Still experiencing the slowdown. I honestly can't think of what's doing this. Advanced Task Manager reports > 190MB free (28 processes running), SetCPU is still running at 499MHz or greater (I can't get 'show CPU to work in Dev Tools?).
Ending everything in the "All Apps" tab does not fix the problem; it's speedy for about 30 seconds, then resumes being slow, with the same problems (so maybe it's a process taking up all my CPU cycles? (But my CPU isn't scaling up like it would in that situation...))
Anything I can try doing before re-flashing and/or wiping? I'd rather avoid that, but, of course, if it's the only solution, whatever. Maybe try flashing a new ROM?
Can't think of what else to do here, gentlemen.
Get rid of SetCPU. I had it installed and it started weirding out on me, would not set the processor higher than 384 and nothing I did in the profiles would set it back to 1 GHz. After I uninstalled, my phone returned to it's normal speeds.
Zak Jones! said:
Sooo, it's not going. Still experiencing the slowdown. I honestly can't think of what's doing this. Advanced Task Manager reports > 190MB free (28 processes running), SetCPU is still running at 499MHz or greater (I can't get 'show CPU to work in Dev Tools?).
Ending everything in the "All Apps" tab does not fix the problem; it's speedy for about 30 seconds, then resumes being slow, with the same problems (so maybe it's a process taking up all my CPU cycles? (But my CPU isn't scaling up like it would in that situation...))
Anything I can try doing before re-flashing and/or wiping? I'd rather avoid that, but, of course, if it's the only solution, whatever. Maybe try flashing a new ROM?
Can't think of what else to do here, gentlemen.
Click to expand...
Click to collapse
You might not like my advice but it's likely to work:
Don't uninstall SetCPU but set your CPU min to 245 and the max to what you want. Disable profiles but select 'Set on Boot' and 'On Demand'. Do nothing else with SetCPU, leave it alone and do not use the active widget. Your current setup is crazy.
Full wipe (as you've done before) data, cache, dalvik-cache, battery, rotate and then install Kang-o-rama 0.7b1 (no, I'm not simply pushing it, I just know it so well that I can assure you it works).
Do not, under any circumstances restore any data or apps for any application with any application. As soon as you set up your Google account go into Settings | Privacy and disable "Back up my settings" and hit Okay.
Install a task manager if you like for monitoring purposes. Install SetCPU as above if you like for OC.
Install no other apps (now that's the painful part) and use your phone for long enough for you to know with certainty whether it's working as you expect.
In all honesty, if it's still broke after that then you've probably got a hardware issue. If it's working after that then slowly add your apps back until you find what's causing the problem.
Good luck, report back.
So far, uninstalling SetCPU is doing wonders for me. Y'know, over the last 15 minutes. I'll use it throughout the day and see if it keeps performing.
Space for future updates:
****ING BALLSACK. <--- First impression of Kang-o-Rama (I decided to just go for it and flash as soon as I saw it included CM.)
^^^^^^^^^^^^ That text is to be read: Kang-o-Rama is amazing. The theme is sexy, I LOVE the Desire camera, and the bundled stuff (kernel, apps, etc) are quite awesome. We'll see if it solves my performance issues.
I was getting the same thing....
Task kill setcpu and reboot it again. If you keep getting the lag then stop using setCPU.
Zak Jones! said:
****ING BALLSACK
Click to expand...
Click to collapse
It takes a twisted mind to interpret that as a complement.
Zak Jones! said:
...Kang-o-Rama is amazing...
Click to expand...
Click to collapse
But thank you!
Delete all widgets that profile your cpu in any way. Stop killing tasks with task killers. Uninstall setcpu. Set exchange email app to "PUSH". Download "Quick System Info Pro" and check what's using up Cpu.
I had the same problem and it turned out to be 2 things: SetCPU widget and exchange email app stuck in a sync cycle.
Maybe theres an ill-performing app that you installed. Since it seems you wiped your phone a couple times including cache. Did you happen to restore apps thru Titanium backup or manually one at a time thru the market.
I always wipe my phone completely and reinstall all apps manually, time consuming, but I have never had a problem.
To further diagnose your problem, see if after installing each app, try the phone to see if there are any slowdowns afterward. Again, I know this is time consuming, but trying to find the problem rather than living with it would be better.
I'm also using 5.0.6 but with no problems or slowdowns.
You can also post a logcat or look thru it yourself if you know how and see if any errors or hangups occur. Logcats are a great way to see the commands being given to your phone and this will most likely reveal your problem.
Same problem, it's annoying.
Just wonder guys, I know my X is supposed to be a beast of a phone, but my Incredible seemed faster and more responsive.
I dont know if I am doing something wrong. Here's what I did:
Re-loaded most of my apps once I loaded on MyBackupPro, the SD card in the phone is the one I took out of the Incredible.
Now the phone kind of chugs along at times, more so than my Inc ever did.
I even have Task Killer Pro killing the MotoBlur apps since I am not using it, I know I know taskillers are 50/50 shot, but I like them.
Anyway, if there is anything I have done or am doing that may be slowing the thing down, let me know please and I will try it.
This thing is supposed to be a quick behemoth, so why is it stalling and chugging when I even try to open the app drawer?
Please any help would be great, thanks.
Many people are having this problem, including myself. You might want to go into Launcher Pro's setting and turn on keep in memory under general settings. The Launcher Pro forms also mentioned turning the memory usage preset to very low. I haven't tried that last thing though.
grdm said:
Just wonder guys, I know my X is supposed to be a beast of a phone, but my Incredible seemed faster and more responsive.
I dont know if I am doing something wrong. Here's what I did:
Re-loaded most of my apps once I loaded on MyBackupPro, the SD card in the phone is the one I took out of the Incredible.
Now the phone kind of chugs along at times, more so than my Inc ever did.
I even have Task Killer Pro killing the MotoBlur apps since I am not using it, I know I know taskillers are 50/50 shot, but I like them.
Anyway, if there is anything I have done or am doing that may be slowing the thing down, let me know please and I will try it.
This thing is supposed to be a quick behemoth, so why is it stalling and chugging when I even try to open the app drawer?
Please any help would be great, thanks.
Click to expand...
Click to collapse
go into menu>preferences>advanced and set all your scrolling and opening speeds up some to make transitions faster......also i know you say you like them but i would ditch the task killer...just another task running!
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
They dont't need to support non standard dpi but they should let applications to show up in Market. This is the reason I downgraded the Market version on my phone, but this is not a solution. I hope Google will let the users decide what dpi is best for them.
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Seen a couple of these pop up so far. The problem has been affecting me for a while now, but I just figured out what caused it last week. Lots of people (myself included) seem to have thought nobody else had this problem.
Post: Changing DPI and new market makes apps incompatibility
Post: [Q] Cannot update multiple installed apps, is it the new market?
blackspp said:
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
Click to expand...
Click to collapse
I'm almost surprised it took so long for them to notice that trend, considering they surely have facilities to notice trends in their databases. Score one for XDA! (Very cool of Google to provide such tailored support, though!)
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
To "permanently" change your DPI to "XYZ", add these lines to /data/local.prop:
Code:
ro.sf.lcd_density=XYZ
qemu.sf.lcd_density=XYZ
(Note: If /data/local.prop does not exist, you may create it yourself.)
- OR -
If you would prefer that the change not persist when flashing a new ROM, you could edit /system/build.prop, which should already contain the "ro.sf.lcd_density" property unless you're on a 160dpi device. /system/build.prop will be overwritten any time you flash a new ROM, even if you do not wipe first.
Both of these methods will require a reboot for changes to take effect.
---
Alternately, if you would like to avoid editing system files by hand, there is an app called Blade Buddy which allows you to modify various properties in /data/local.prop, including LCD density.
To save your changes from Blade Buddy, tap Menu -> Save. If you choose not to reboot, you can then tap Menu -> Apply to apply the changes in RAM and restart the UI to see them in action. (Applying density without rebooting seems to be hit-or-miss.)
---
Regardless of how you set your LCD density, the Market will exhibit the incompatibility bug.
As a workaround, I have set my density "permanently" with Blade Buddy and use LCDDensity for Root to revert to default once and a while, so I can launch the Market and get all my updates. LCDDensity for Root is designed specifically to change density temporarily, on-the-fly, and on as many devices as possible.
Thanks, Mr. Bezeek. Actually what I'm looking is the permanent solution of not having to temporarily switch back and forth. As for editing .props I already have experience before with my Streak. Hehehehe
But still, thanks anyway and hope you not offended. I like it the way you help others in precise and detailed manner. Keep it up, bro *thumbs_up*
Not a problem, just doing my bit to make sure the information is out there.
As far as avoiding the temporary switching goes, I'll be on vacation for the next week, but I intend to try a little hacking when I get back, to see if I can find a way to spoof the dpi. That is, if Google doesn't throw us a bone in the meantime.
Users have reported that older versions of the Market still work. The one shipped with the latest OTA for my Evo worked for me, and I suspect that any version released before they changed the Market UI will. YMMV.
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
tslovejoy1969 said:
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
Click to expand...
Click to collapse
Good to know! Being able to compare a "working" ROM to mine will surely make it easier to identify a workaround.
Nice info never noted this before!! yeah i dint get any updates over a last few weeks. Im at 200 dpi.
I've been switching back to 240 periodically to get updates, not a big deal to me, but would be nice if things worked normally. My only real issue with running lower dpi (160 here) is that some apps don't scale properly. IE the Dialer.
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Thank for this information! I've been wondering why some standard apps weren't compatible.. It's weird, since they work if you side load them ...
I hope google finds a solution.
---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------
I just switched from 190dpi to 160. Angry birds seasons is now compatible( wasn't with 190dpi)
Dank U vriendelijk
Wow. This has been driving me crazy trying to work out why apps where missing. Guess I need to swap to 240 occasionally for updates.
I am using 200 / 192 DPIs from day one. (3 months). its working fine.I never faced incompatibility issue with market. however some games doesn't run correctly which usually i don't play.
i have a workaround idea, and i started a thread to discuss here: http://forum.xda-developers.com/showthread.php?t=1288150
The google support thread for this is here: http://code.google.com/p/android/issues/detail?id=19744#makechanges
I still have this issue and if you do a web search you'll see that many still do. Reply in the support thread to raise awareness ! or if you have a workaround please share You also might want to check out his Idea thread, if you have some developing skill please help.
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
I came from a streak as well and it's this is the biggest annoyance I've had with the sgsii.
The reason why i enjoy Android over any other mobile OS is because i can tailor the OS to how i want it. Not allowing me to download apps because I'm using a non standard density is crippling.
For now, i urge everyone to go to the google support thread and simply press click the star. No need to comment (unless you found a fix), the more stars the issue gets, the more likely Google will look into it.
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Ke11ett said:
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah i seem to be ok ive just got the version from androidpolice last night. im on 3.3.11 now, still cant install stuff from the website though says my phone is incompatible for everything lol
Gmail & K9mail both use wakelocks. I don't trust them even in manual check mode. Something much more light weight seems appropriate.
It's important to get this right since the main point of a Nook NST for me is saving battery and being able to pick it up and use it straightaway. If an app starts waking up and draining battery even a little then it's no longer going to last for a month.
Using a browser such as Opera can work but it's a little clunky and so is freezing and unfreezing apps even with a widget. Any recommendations for an email app?
Not sure about email apps so this doesn't answer the question you're actually asking, but may have a functionally similar outcome. Using a CPU scaling app with profiles and setting it so the range of frequencies the CPU can use when the screen is off has both the maximum and minimum values at the lowest possible helps a lot for me.
neoman4426 said:
Not sure about email apps so this doesn't answer the question you're actually asking, but may have a functionally similar outcome. Using a CPU scaling app with profiles and setting it so the range of frequencies the CPU can use when the screen is off has both the maximum and minimum values at the lowest possible helps a lot for me.
Click to expand...
Click to collapse
Thanks buddy but I find I get a month as it is just making sure that the phone.apk and related stiff that starts after rooting is removed. I don't think I need CPU scaling because that's already working for me. Main thing is to watch those wakelocks. There are tons of apps that cause them including skype, paypal, facebook, whatsapp. Only fix is to freeze them, avoid or get the progammers to do it properly and program thier app in 2 parts