Develop Bugs

Not so smooth interface, could be due to OC?

Hello,
Until yesterday i never OCed my desire, I had DJ Droid rom and it was always smooth and slick in terms of interface and apps jumpiness.
Yesterday I decided to try the 1384Mhz rom from OpenDesire. Done full wipe of course, installed the ROM, then after the installation my Desire was pretty hot (probably due to all sync apps work) even before i installed set cpu or did any OC.
Then I said, ok lets try OC, I installed Set CPU, And tried 1300Mhz level and also the maximum levels. and it froze up, i had to pull off the battary and reboot.
Then I tried 1272, Again froze up during browsing...
Then I tried 1Mhz and ran stress test for long, no errors no freez ups.
However, OpenDesire wasnt slick and smooth for me, I mean during sliding the apps menu, it was not smoooth i felt some slowdowns... same about the main interface windows slide right/left. especially with live wallpapers from some kind.
Is it normal? Could I damage something in my CPU/GPU due to this OC? Which causing this?
I tried even full wipe and again from zero placing the OD rom...still had same feeling of none smoothness.
thanks

Any ideas?

I had this problem. I usually leave my Desire overnight so it can sync, titanium backup, fix permissions etc.
After installation of OD, I find that just signing in, then rebooting, installing extras like statusbar then rebooting, then titanium restore, fix permissions, then a reboot usually sorts me out, leaving my desire on sync overnight (market is very slow after fresh install for me =/)
Very long process
OD supports ext3 for A2SD+. Some users have reported that they had problems with several A2SD roms because they haven't got a ext2/3 partition, or a ext4 which I don't think is supported on OD. This can slow a rom down severely, as the phone is looking for the sd-ext partition.
Final mention would be setCPU itself.
Saying this, I have had issues with the performance scaling or whatever it is called... the "interactive", Ondemand, powersave etc.
I dont trust interactive scaling atm (had alot of FC on Pinkys and OD 3.5), as it seems relatively new, and still has some kinks.
Sticking with ondemand, with a sampling rate of about 20k and a CPU threshold of about 85%, I have pretty good performance. I have found that upon starting up setCPU on OD 3.5.2, the settings are 20k/11% which could be your problem.

Tried now GeFrost, well the apps icons panel ( 5 pages long...) when sliding again had freezy/laggy feeling....I've wiped GeFrost and installed LeeDroid rom with Sense UI, Now i feel good again I suspect that "none sense UI" Simply not for my touch and feel style... Sense UI feels much more smoother just like DJ droid rom i had...
So my CPU isnt damaged and could not get damaged from what I did... right?

rommark said:
So my CPU isnt damaged and could not get damaged from what I did... right?
Click to expand...
Click to collapse
Your CPU could have been damaged from overclocking - I'm not saying that it has been, but there is always an element of risk when you overclock.
If you really want to overclock, my advice is to always start low and then incrementally increase. If you get to a point where the phone starts to become unstable, drop the speed back down a notch.
Furthermore - not all CPUs are made equal. Just because someone else manages to overclock their CPU to 1384MHz doesn't mean that you will be able to - it's just the luck of the draw.
Regards,
Dave

Hey,
Thanks for your answer.
Well on regular clocks its not freezing up to the level where I need pull off the battary...Something that indeed happened to me on OD with OC.
So far LeeDroid rom works smooth.
How can i find out if my CPU got damaged?
Anyone else had such lock ups which needed battary pull off, with OC on Desire?
Thanks!

Whenever you use a OC kernel, you run the risk of damaging the internals.
Non of the internal components are EXACTLY the same. Some can support lower voltages, some can substain higher Clockspeeds.
My lockups with OD is purely on the SetCPU settings.
Have you got a EXT3 partition on your SDcard? Because I see LeeDroid supports Froyo A2SD, while OD&DeFrost Ports are all LegacyA2SD
This may be the problem, instead of a issue with your internals, as the internals would most likely fail/rapidly overheat altogether if there was a problem.

Well I think my desire is warm as usual... not warmer. Only time it was really warmer then usual. Was when i just installed the OD rom and market was syncing all my massive list of apps all together which i think caused CPU over work but thats was even before i installed set cpu and did any OC....
Anyways LeeDroid now works i think as smooth as DJ droid. without any OC.
As for your question about EXT3 How do i check that? could this cause the lock ups with set cpu while using OD oced?
thanks

ext3 is a linux filesystem partition that you would of installed onto your SDcard, either by RomManager or Linux LiveCD/Linux OS
As your unsure, I'm pretty certain that you have not partitioned your SDcard. With A2SD+ (which are both on the OD and Frost roms), the phone is told to read Apps and delvik cache from the SDcard. This means no applications are actually installed on the phone, but the "internal" memory is now the ext3 partition on your SDCard.
Ext3 is required for both OD and De/GeFrost roms.
With this, it sounds like your CPU is fine, as LeeDroid is running fine, and that you are using Froyo A2SD.

Danifamous said:
ext3 is a linux filesystem partition that you would of installed onto your SDcard, either by RomManager or Linux LiveCD/Linux OS
As your unsure, I'm pretty certain that you have not partitioned your SDcard. With A2SD+ (which are both on the OD and Frost roms), the phone is told to read Apps and delvik cache from the SDcard. This means no applications are actually installed on the phone, but the "internal" memory is now the ext3 partition on your SDCard.
Ext3 is required for both OD and De/GeFrost roms.
With this, it sounds like your CPU is fine, as LeeDroid is running fine, and that you are using Froyo A2SD.
Click to expand...
Click to collapse
Thank you for your kind help.
Should Desire feels warmy in hand during its being connected to computer's USB?
Thanks!

Yea, thats usual. There is still power coming from the computer to charge the battery, so its fine.
I've had my phone hit about 50 Celsius on several occasions, while I've fell asleep ontop of it while playing music, and so far, no visible damage to performance etc
Again, the issues with OD just seem to be based around the lack of a ext3 partition on your SDcard, so don't worry too much about the CPU being damaged.
Just be cautious in the future with OC, and never OC more than you need It can drain more battery, and end up breaking your phone (in extreme cases).

Danifamous said:
Yea, thats usual. There is still power coming from the computer to charge the battery, so its fine.
I've had my phone hit about 50 Celsius on several occasions, while I've fell asleep ontop of it while playing music, and so far, no visible damage to performance etc
Again, the issues with OD just seem to be based around the lack of a ext3 partition on your SDcard, so don't worry too much about the CPU being damaged.
Just be cautious in the future with OC, and never OC more than you need It can drain more battery, and end up breaking your phone (in extreme cases).
Click to expand...
Click to collapse
Thank you so much,
So indeed OD / Gefrost was an EXT3 issue (lock ups, super slow down and lock ups which caused battary pull offs). How can i confirm this?
While DJ droid and LeeDroid working smooth with Sense UI.
thnx!

Only way is to reformat the SDcard, either with Rom Manager which is easiest (available for free on Android Market) or a Linux variant. This will remove all data currently on the SD, so back up everything
Add a ext3 partition to your SDCard (swap size is unnessacary), and install OD/GeFrost.
There will be a major boost in performance compared to previous times.

trouble shooting slowness

Maybe someone already asked but I couldn't find it. I've had my rooted Inc for about 4 months and still trying Roms out. However whatever rom I use, except cm7, I get some lag. Some slow load times and such when I unlock or open a new app. I'm just curious if its an Inc problem, a sense problem, or maybe my hardware was ddamaged. I bought the phone refurbished from verizon
Sent from my ADR6300 using XDA App

infidelmatt said:
Maybe someone already asked but I couldn't find it. I've had my rooted Inc for about 4 months and still trying Roms out. However whatever rom I use, except cm7, I get some lag. Some slow load times and such when I unlock or open a new app. I'm just curious if its an Inc problem, a sense problem, or maybe my hardware was ddamaged. I bought the phone refurbished from verizon
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
If it was a hardware issue, even CM7 would show it. Sense ROMs have a lot going on, especially when you go to unlock the screen. Some kernels will switch governors to Performance as soon as the screen is turned on and until it's unlocked. Scripts can be written to accomplish this in most kernels.
Certain widgets, such as the SetCPU widget, will bring things to a grinding halt with the graphics. I can't tell you why, but I've used a few apps where the widget for it was whacky like that.
Newer Sense versions are also going to entail some lag as well. Overclocking will help a little, but the GPU in that device isn't real powerful and is easily overwhelmed by a Sense 3.0 environment. The limited memory is an issue as well.
If you can, create a swap file. That will free up some memory.
Do NOT use task killers. They slow everything down by killing apps that need to be restarted, thus taking up NAND bandwidth, eating power, and freeing up RAM that's there to allow for recently used apps to run faster.
Wipe your Dalvik cache with each new ROM/Kernel. A properly built Dalvik cache is there to minimize app launch lag. Basically, it's a cache of application byte code that's been pre-compiled so that it can be executed while the JIT compiler determines the most efficient compiling of the remaining application code.
On the dInc, my SCcard seemed to access files quicker than if stored on the internal eMMC. Moving your Dalvik cache to the SDcard could allow it to be accessed faster since it's not sharing bandwidth with the rest of the system trying to access OS and app data from eMMC. I don't know if there's a way to test that or not, but it might be worth a try.

Check number and frequency of items synched; quick hit on responsiveness. Task killer or antivirus installed? Uninstall to see whether they are the culprit.
Sent from my ADR6300 using XDA Premium App

Autokiller memory optimizer.

Hi i found an app called auto killer memory which ive been running for a while. this app has worked wonders for my wilderbeast, its on fire. so ive been tampering alot with things but this seems to have stabalised my phone loads. presets i set to lost, enabled advance mode,apply at boot,ticked all system tweaks and of course when promted enabled super user. my phone is now running sweet and battery has improved too. i dont know if this makes any sense but i have noticed a difference. whoop whoop. am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Ok I've ammended my settings within this app after doing some research And in memory values I'm now running at 6/10/16/100/120/160 to keep my phone running snappppppy. To explain the values in brief...... if free memory goes below 160mb my phone starts to kill empty apps etc etc as free memory goes below next value the phone starts to kill corresponding apps. Kind of makes sense to me now. Ok I know my settings makes the phone kill more frequently but its damn snappy now,and it can lower the oom settings by long pressing the app in processes section you wish to lower and choosing lower oom. Lowering the oom basically gives the app less chance of being killed.

Personally I haven't had a low memory situation since I rooted and installed cm7, the app your talking about I have installed after reading one of your other posts about it, I presume that it would work the same way as juwes after setting the low memory values, I don't use those settings with it though as I have juwes script installed, the other tweaks seem fine but again I think I had some of them covered from editing my build.prop (still have work to do on that though) and a few other little things, I can't knock this app though as it does seem to have made my battery last a bit longer since installing yesterday, I'd personally rather change the settings myself than have yet another app doing it for me but until I figure which setting seems to be helping my battery out I'll keep it installed.
A couple of other apps which might help you keep it smooth,
Autostarts- I swear by this app its one of my best buys from the market, why use a task killer when you can just stop the app starting in the first place??
Fast reboot pro- after time apps hold memory which they don't really need, hit this and it'll quickly reboot everything (unless you tell it to leave something alone) freeing up spare ram.
Sent from my HTC Wildfire using xda premium

Cheers for info,really happy with this app at the moment.by the sounds of things its doing similar job to other script mods,which I can't get working cos of s - off issue. Posted this for s on users benefit. Hope it helps others.

Edit my settings. Read 1st post.
sent from my wilderbeast/buzz

The only problems I see with having higher settings are if it closes something you use regular it'll be slower to open that app, I'd rather keep them set low and have apps open quickly.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
The only problems I see with having higher settings are if it closes something you use regular it'll be slower to open that app, I'd rather keep them set low and have apps open quickly.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I agree but this app lets you temporary lower the oom level for apps,so I just lower oom on most important. Long click on process or service and to lower.
sent from my wilderbeast/buzz

Does it?..........I didn't spot that nice find!!
Sent from my HTC Wildfire using xda premium

Yep,long click app in service or process then choose to lower oom.it resets if you reboot so get your settings desired then leave by pressing home button.
sent from my wilderbeast:buzz

whats up with these settings for the pages? what do these settings change?
atm i have these settings:
2560
4096
25600
30720
40960

gozzaa said:
whats up with these settings for the pages? what do these settings change?
atm i have these settings:
2560
4096
25600
30720
40960
Click to expand...
Click to collapse
Change the view from pages to mb and these are the values when it will start killing processes etc. Ie. When your memory gets to the amount your phone starts freeing up starting with the highest setting (empty apps)
Its all explained above,just that you have the pages view instead of mbs.
Quote " its healthy to have enemies, it means you've stood up for something you believe in "

ahh the pagesettings are the same as the MB ones?
i thought its two different things
thanks for the explanation!
btw. do you still use the same settings?

Yes to this day I still use this app even though I'm now s-off with the settings I posted,I will just double check and ammend if needed on 1st post.
" once its gone,its GONE."

slymobi said:
am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Click to expand...
Click to collapse
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.

zephyri-xr said:
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
Click to expand...
Click to collapse
i tried supercharger and juuwes but had issues which i think were specific to me but one of the issues was bootlooping from supercharger as well as other things. im not saying one is better than the other but as you and myself had issues with one of the mods then its an alternative for others to use. i prefer this as you get to control the settings and mods yourself from the app. also this is available for s-on whilst the others i believe need s-off.

zephyri-xr said:
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
Click to expand...
Click to collapse
I got a boot loop from supercharger. I had to wipe my phone and start again from an RUU as all my previous backups became corrupted. Nightmare. TBH in the few days that it did work, i saw/felt no difference.
Using CM_7.1.0.1 probably wouldnt advise to use the supercharge, CM_7 minfree values are set to a pretty good level to keep things in order i think

slymobi said:
Hi i found an app called auto killer memory which ive been running for a while. this app has worked wonders for my wilderbeast, its on fire. so ive been tampering alot with things but this seems to have stabalised my phone loads. presets i set to lost, enabled advance mode,apply at boot,ticked all system tweaks and of course when promted enabled super user. my phone is now running sweet and battery has improved too. i dont know if this makes any sense but i have noticed a difference. whoop whoop. am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Ok I've ammended my settings within this app after doing some research And in memory values I'm now running at 6/10/16/100/120/160 to keep my phone running snappppppy. To explain the values in brief...... if free memory goes below 160mb my phone starts to kill empty apps etc etc as free memory goes below next value the phone starts to kill corresponding apps. Kind of makes sense to me now. Ok I know my settings makes the phone kill more frequently but its damn snappy now,and it can lower the oom settings by long pressing the app in processes section you wish to lower and choosing lower oom. Lowering the oom basically gives the app less chance of being killed.
Click to expand...
Click to collapse
I have tried supercharge script and does make phone smooth. Also Ive use ram manager new app and that too made phone smooth. But this app (Pro) is so far great. I tried out your settings for now to see if it suits me and had the app for an hour and the phone is very snappy and smooth (which is most important to me). I hope there is a slight battery improvement that many have said on the net but will test more and will leave feed back. A big thx m8!

no probs mate, like i said i have tried the lot and this one for me is really good and you get to be the controller lol.the only drawback i have noticed is that it takes a little longer for the phone to boot after a reboot but !!!!! im ok with that.

LMFAO looks like I didn't pay enough attention... I've used a lot of tweaks already to make my Willy faster, more snappy and stable but to be honest nothing gave it such a boost like that
BTW: are you still using the settings of the op?
Holy crap, I've read that really often here and elsewhere but it's the first it applies to myself: feels like a new phone

eventcom said:
LMFAO looks like I didn't pay enough attention... I've used a lot of tweaks already to make my Willy faster, more snappy and stable but to be honest nothing gave it such a boost like that
BTW: are you still using the settings of the op?
Holy crap, I've read that really often here and elsewhere but it's the first it applies to myself: feels like a new phone
Click to expand...
Click to collapse
I use aggressive setting mostly, all advanced tweaks except sdcard boost one as this bumps read ahead up to 2048, just my preference you might prefer 2048.
Say oooh la la

slymobi said:
I use aggressive setting mostly, all advanced tweaks except sdcard boost one as this bumps read ahead up to 2048, just my preference you might prefer 2048
Click to expand...
Click to collapse
I see. I just have to sort things out now. Regarding the SD card read - I have it already done by sdbooster (@2048) - I'm at a point where I should make a documentation to stay on track and to avoid double tweaks lol.
I'm also very interested into scratch's build.prop lol (guess that would help to drop even more tweaks). Thx again - I've not forgotten about your tip re. AMO - just shifted it too far lol.

[Q] Abduction Help?

I'm currently using the Abbduction v1.81 ROM with my Dinc and its been acting weird lately. Help?
-random restarts.
-boot screen sometimes goes Portal and infinite loops itself.
-random force closes (although better than my previous ROM)
-battery isn't nearly as good as i was told.

Did you wipe all data before flashing?

Firstly, I love the thread title.
Secondly, Abduction is based on AOKP, right? In my own usage, I have seen those same symptoms (particularly the reboots and batter life) when running straight AOKP; even as recently as M4. My phone seems to like Evervolv a LOT better, so I keep coming back to it.

graymonkey44 said:
Did you wipe all data before flashing?
Click to expand...
Click to collapse
yessir. i followed all the steps that were listed in the instructions. this is not my first ROM btw. i forgot to mention that i think..

Try a different recovery or use a superwipe script. Sometimes recoveries don't wipe things correctly leading to unexpected behavior. Also, the space on your phone could be getting clogged by the number of apps you have, which often results in random reboots. To prevent this, you can try moving apps to the SD card or just downloading fewer of them.

I disagree on the wiping having issues. There was a post by a lewd cm member on this a while back. How much space used or left on /data/data? HTC made the brilliant move of limiting /data/data to 150mb which doesn't get reported anywhere in the os. That is a possible cause of the force closes if the free space there is low. As far as reboots did you tweak voltages or overclock?
Sent from my Galaxy Nexus using Tapatalk

http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache

tiny4579 said:
I disagree on the wiping having issues. There was a post by a lewd cm member on this a while back. How much space used or left on /data/data? HTC made the brilliant move of limiting /data/data to 150mb which doesn't get reported anywhere in the os. That is a possible cause of the force closes if the free space there is low. As far as reboots did you tweak voltages or overclock?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
i did undervolt is when i started using Abduction, but before then i havent done anything but overclock it by a little bit. using the ROM control that came with AOKP.

tiny4579 said:
I disagree on the wiping having issues. There was a post by a lewd cm member on this a while back. How much space used or left on /data/data? HTC made the brilliant move of limiting /data/data to 150mb which doesn't get reported anywhere in the os. That is a possible cause of the force closes if the free space there is low. As far as reboots did you tweak voltages or overclock?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ughhh I mean lead.
How much did you over clock, OP?
If its 1113 MHz or less it should be fine. Try without overclock and see if you have the same issues.
Sent from my Galaxy Nexus using Tapatalk

[Q] mimicry 1.1.0 speed issue

Sorry that I have to post this here...I don't post much, just am a super power user... any thoughts on how to make this rom perform faster? I push a button and wait for the phone to respond. Especially slow when it comes to the maps app. An seriously contemplating going back to cm9b14 if not all the way back to gingerbread to get the speed I need from a device. I type faster than it is able to display the letters when searching in google. Not wure what feature to turn off or how much more I can overclock the thing.
On install I did a factory reset, total partition format, new sd card format, efs wipe, and ed's ril/gps fix after install.
Not sure how to tweak v6 supercharer. Seems too complicated honestly.
Thoughts?
Thanks...

I just started running Mimicry today and I find it to be quite a snappy ROM right out of the box especially if you picked the V6 Supercharger and the Virtuous OC Daemon from the Aroma installer. I believe doing this automatically increases your clock speed to 1209 Mhz. However if you want to increase the speed of your CPU some more, can modify it through the Performance menu or you can download SetCPU.
http://forum.xda-developers.com/showthread.php?t=505419

Bharakrama said:
I just started running Mimicry today and I find it to be quite a snappy ROM right out of the box especially if you picked the V6 Supercharger and the Virtuous OC Daemon from the Aroma installer. I believe doing this automatically increases your clock speed to 1209 Mhz. However if you want to increase the speed of your CPU some more, can modify it through the Performance menu or you can download SetCPU.
http://forum.xda-developers.com/showthread.php?t=505419
Click to expand...
Click to collapse
I can attest to that, mimicry is pretty fast, no issues so far. only problem I had was when I tried to multitask between navigation, whatsapp, and viber, my navigation froze and i got lost :crying:

toquer said:
Sorry that I have to post this here...I don't post much, just am a super power user... any thoughts on how to make this rom perform faster? I push a button and wait for the phone to respond. Especially slow when it comes to the maps app. An seriously contemplating going back to cm9b14 if not all the way back to gingerbread to get the speed I need from a device. I type faster than it is able to display the letters when searching in google. Not wure what feature to turn off or how much more I can overclock the thing.
On install I did a factory reset, total partition format, new sd card format, efs wipe, and ed's ril/gps fix after install.
Not sure how to tweak v6 supercharer. Seems too complicated honestly.
Thoughts?
Thanks...
Click to expand...
Click to collapse
Make sure your partitions are all ext4. Also, v1.1.1 is out

update
1.1.1 definately fixed a lot of issues i was having. i also removed the option to have the kernel installed and dropped the speed way down on setcpu. seems to be a lot better now.