I'm currently on CM6 and using LauncherPro. However, it seems a bit sluggish for some odd reason. My setup is sort of mimicking my Sense layout before I moved to CM6.
Calendar - Internet Stuff - Contact Widget plus shortcut - Beautiful Weather widget, BatteryLife widget plus a couple shortcuts - Entertainment shortcuts - Tools shortcuts - Pure Messenger w/ Facebook and Twitter only
The main thing I think that's slowing things down is the Beautiful Weather widget. Not sure, though. Any recommendations on alternates for the same functionality?
Another thing possibly slowing it down is that I set the pixel density down to 200 with the app. Though, it's only graphical lag that all this encompasses. Benchmark scores are on par. Perhaps Snap is causing issues?
Any tips on making LauncherPro faster?
Do you have window transitions set to fast in spare parts?
and I set my drawer opening speed to 8 and min scrolling speed to about 75
that's all I can think of right now..
I'm not sure what did it, but something just sapped my battery like whoa. About an hour ago my battery was at about 75% and now it's down to 17%. WTF mate.
cosine83 said:
I'm not sure what did it, but something just sapped my battery like whoa. About an hour ago my battery was at about 75% and now it's down to 17%. WTF mate.
Click to expand...
Click to collapse
Wow, that's terrible.
What rom setup are you running?
I don't know that much about PowerTop, specifically if it can be run remotely or if it needs to be on the phone but that would help narrow down the problem..
CM6 w/ Snap 8.2 875mV. I'm trying out ADW and it seems to be a bit snappier for some reason.
cosine83 said:
CM6 w/ Snap 8.2 875mV. I'm trying out ADW and it seems to be a bit snappier for some reason.
Click to expand...
Click to collapse
yeah, something is definitely wrong if ADW seems snappier than launcher pro...
fwiw, I know a lot of people have had great success with them but I haven't found an alternative kernel that has been as stable and predictable as the stock CM6 kernel. No offense, it's definitely me, not knowing how to work with and tweak them. The kernel may be related to your awful battery drain?
I just reflashed the nightly to get the stock kernel. Gonna let that sit for a bit and see how it goes.
Agreed
nebenezer said:
The kernel may be related to your awful battery drain?
Click to expand...
Click to collapse
I'm gonna have to agree with you there.
I had Kingklick #6 kernel (yes, I have a Sense-based rom) and my battery life was shot to death.
Hopefully upping to #8 will help.
Make sure that you have the current version of whatever Kernel you are using.
Related
Ok so I use mainly 2.1 sense build running at 633mhz cpu speed, and have had no probs with SOD, or overheating whatsoever. I have read of people going 787mhz, and leads me to wonder, how much can the processor in our TP2's take? The reason I ask is because by overclocking in Android, I have experienced significant performance increase and little to no ill effect, and it looks like at some poin oc will be possible with Windows. I am hoping that oc will be key to making Windows run as smooth as it ought to, escpecially with the severely limited amount of ram these phones have. If oc makes the sense build run smooth enough to be used comfortably, I feel same is possible with Windows, but how fast is too fast ?
u mean me..lol. good question though. ;-) I've had no ill wffects or drawbacks
-------------------------------------
Sent from my AOSP on XDANDROID MSM
huggs said:
Ok so I use mainly 2.1 sense build running at 633mhz cpu speed, and have had no probs with SOD, or overheating whatsoever. I have read of people going 787mhz, and leads me to wonder, how much can the processor in our TP2's take? The reason I ask is because by overclocking in Android, I have experienced significant performance increase and little to no ill effect, and it looks like at some poin oc will be possible with Windows. I am hoping that oc will be key to making Windows run as smooth as it ought to, escpecially with the severely limited amount of ram these phones have. If oc makes the sense build run smooth enough to be used comfortably, I feel same is possible with Windows, but how fast is too fast ?
Click to expand...
Click to collapse
I believe demandarin got it up to ~760MHz with no ill effects, the only issue being if your phone goes to sleep, it'll freeze and you'll have to boot back into WinMo and run haret again. And as far as my testing goes, there isn't a significant hit to battery life.
Also, I'd recommend using the AOSP build (the one without Sense). I tried running the Sense build and it's much, much slower. I also hear you get less available RAM for Android use (and ATK reported this, too). Plus, with the overclock applied, the AOSP 2.1 build just *screams*.
With the battery fix in startup.txt (htc_battery_smem.fake=1 /if thats not it exactly its very close, you know which one I mean), I never get sleep of death. I know aosp is faster than the sense build, but sense runs pretty good for me at 633, and its so nice looking. I also have the sense build on my sd with sense disabled, I was going for basically a aosp build only with the sense build's 7 pages but it seems when you disable sense, you lose the 2 extra pages with it. I have had some freezes with sense due to apparently running it out of available ram, but anytime it does that, it just goes back to the klinux/htc bootscreen and starts right back up.
huggs said:
With the battery fix in startup.txt (htc_battery_smem.fake=1 /if thats not it exactly its very close, you know which one I mean), I never get sleep of death. I know aosp is faster than the sense build, but sense runs pretty good for me at 633, and its so nice looking. I also have the sense build on my sd with sense disabled, I was going for basically a aosp build only with the sense build's 7 pages but it seems when you disable sense, you lose the 2 extra pages with it. I have had some freezes with sense due to apparently running it out of available ram, but anytime it does that, it just goes back to the klinux/htc bootscreen and starts right back up.
Click to expand...
Click to collapse
If you want AOSP with more screens you should just use AOSP and get a different launcher. Sense is HORRIBLY slow, and even when you have it disabled that build is SUPER slow. I've got 110mb free RAM with AOSP running Launcher Pro without a buggy overclock (that really when you run benchmarks on the OC it doesnt help THAT much), and it blows that Sense build out of the water.
just to serve as a comparison: my tilt 2 running NRGZ28's latest titanium ROM I've only got 70 mb of free ram. Are you sure you have 110? that means your phone is only using about 40% of ram just sitting there. With WM6.5 and sense 2.5 I would hover around 65% after a fresh reboot and with titanium i am at about 60%....
brunodemelo said:
just to serve as a comparison: my tilt 2 running NRGZ28's latest titanium ROM I've only got 70 mb of free ram. Are you sure you have 110? that means your phone is only using about 40% of ram just sitting there. With WM6.5 and sense 2.5 I would hover around 65% after a fresh reboot and with titanium i am at about 60%....
Click to expand...
Click to collapse
Yes, I'm sure. Linux leaves a much smaller footprint.
Reefermattness said:
Yes, I'm sure. Linux leaves a much smaller footprint.
Click to expand...
Click to collapse
wow thats amazing.
Reefermattness said:
If you want AOSP with more screens you should just use AOSP and get a different launcher. Sense is HORRIBLY slow, and even when you have it disabled that build is SUPER slow. I've got 110mb free RAM with AOSP running Launcher Pro without a buggy overclock (that really when you run benchmarks on the OC it doesnt help THAT much), and it blows that Sense build out of the water.
Click to expand...
Click to collapse
I have the prolauncher one on my sd too, just havent set it up yet. Thats my next one to do. I have 2.01, 2.1 aosp, sense, and 2.1sense with no sense.
I have a 16 gb card so I figured why not. I really like the way sense looks, but I didnt know it was that heavy. Thats cool kinda gives me motivation to mess with it, I was stallin on it cause I hate goin thru fixing the time again.
Hey is there some way to build into the droid utility app the option to choose which build you wanna run, I assume it could be done by naming the anboot folders to andboot1 ,andboot2, etc. and then pointing the droid utility to whichever one is chosen right ?
huggs said:
I have the prolauncher one on my sd too, just havent set it up yet. Thats my next one to do. I have 2.01, 2.1 aosp, sense, and 2.1sense with no sense.
I have a 16 gb card so I figured why not. I really like the way sense looks, but I didnt know it was that heavy. Thats cool kinda gives me motivation to mess with it, I was stallin on it cause I hate goin thru fixing the time again.
Hey is there some way to build into the droid utility app the option to choose which build you wanna run, I assume it could be done by naming the anboot folders to andboot1 ,andboot2, etc. and then pointing the droid utility to whichever one is chosen right ?
Click to expand...
Click to collapse
Yup, we have actually discussed an online XML database, which would allow the app lots more options. Me and Piet have a huge list of things we want to add already, we just need to actually get the motivation and time to do it.
With the battery fix in startup.txt (htc_battery_smem.fake=1 /if thats not it exactly its very close, you know which one I mean), I never get sleep of
Click to expand...
Click to collapse
If you want AOSP with more screens you should just use AOSP and get a different launcher. Sense is HORRIBLY slow, and even when you have it disabled that build is SUPER slow. I've got 110mb free RAM with AOSP running Launcher Pro without a buggy overclock (that really when you run benchmarks on the OC it doesnt help THAT much), and it blows that Sense build out of the water.
Click to expand...
Click to collapse
+f course the Aosp build runs great right out da box. But with the overclock, it screams. Did various tests to see how much of a difference in improvement. I don't just go by benchmarks. I look for real time application. ;-) live wallpapers stock move ok. With the overclock, they fly all over and off da screen. The UI is wayy faster and more responsive. Programs load up faster. Tested different games b4 and after. After the overclock, games ran at almost normal speeds, Since hardware 3d not completly wrkn. Ill eventually go bck to stock speeds further along in development of this build. I got an early start Reefer, 4:20, U Ready? ;-)
-------------------------------------
Sent from my AOSP on XDANDROID MSM
anyone notice that the gsenor is off? when playing games that use the gsenor like labyrinth or doodle jump, its always slanted. I dont think its the calibration, because WM works well w/ the calibration...any info?
moto2000 said:
anyone notice that the gsenor is off? when playing games that use the gsenor like labyrinth or doodle jump, its always slanted. I dont think its the calibration, because WM works well w/ the calibration...any info?
Click to expand...
Click to collapse
Yeah by like 90 degrees. I spent a little while last nite looking for a way to calibrate mine, but I got tired and gave up.
Anyone manage to overclock WITHOUT using htc_battery_smem.fake=1 and not have the SOD issue? even if it's not that much of an overclock?
Hey..I'm new to the forum and the Evo. I've seen a few posts about this, but haven't really been able to find an answer.
As with the other people that typically notice this, I'm an iPhone 3GS user...I bought the Evo a few days ago and love it, for the most part. I'm used to extremely smooth performance with very little lag. I noticed that scrolling through the application drawer, or the built in messages application causes huge lag, along with other menus. It seems like the most choppy performance is as the scroll is slowing down (like, if you "flick" it). So, naturally, I rooted my phone. Oh and to be clear, I'm not talking about the touch-sensor lag.
Here is what I have done so far hoping that it would eliminate the lag:
- Obviously, I've used Advanced Task Killer and removed the Live Wallpaper. Didn't really do anything. I have about 160 MB of available memory.
- Using the stock OTA rom (rooted), I installed the netarchy-toastmod-3.7.3c kernel to remove the FPS cap on my screen. It worked. Now, my scrolling is more responsive, but still choppy.
- Froyo. I've tried a few different Froyo ROMs hoping that the claimed 250-300% speed increase would eliminate scroll glitches. It did not. I tried Ava and Cyanogen ROMs.
- I tried the netarchy-toastmod-3.7.3c Froyo kernel for the Froyo ROMs. Still...choppy...possibly a little better though. It's hard to tell without seeing it side by side.
My brother has a different Droid phone (I forget which), but it didn't have a noticeable lag like the Evo does, and I know it's specs aren't as good. Is this phone doomed to low-quality scrolling? Any other suggestions?
What you're probably noticing is a lack of refinement in the easing of the animation. The only "fix" will be to view it as more responsive.
Sent from my PC36100 using XDA App
You may want to try a different launcher. For super snappy response I have heard good things about Launcher Pro. Personally I am using CM6 RC1 with some ADW tweaks and I feel like its fluid enough for me with no choppiness.
Thanks! The ADW tweak posted made the application drawer seem a LOT better (mainly because of the horizontal scrolling). I suppose I'll either just deal with the other choppiness or take it back and wait for a different phone, like the Epic. Maybe I'm just being too picky >.<
I've had great success with CM6 nightly and LauncherPro. As smooth as you can get. I had a news widget that caused some slow downs as well so make sure a widget is not causing it.
I noticed this too.
Its almost like comparable to a computer game performance on a pc
when it goes from 60 frames per second to 20 frames per second you notice it more.
if they just made it stay at say 20fps speed then it would at least keep a reasonably smooth experience
I will try the CM nightly build see if I have any luck.
I love the evo too but man the iphone 4 seems so much smoother when in reality its probably not.
its all about the way its presented
i am currently using baked snack 1.1 with netarchy kernel
if i install cm do i have to flash a different kernel or will it automatically do it?
As title states, both launchers run pretty slow and choppy when running several widgets. I'm running last night's "nightly' with Pure Messenger and Pure Calendar widgets, along with stock news widget and feedr widget. After first reboot all is smooth, but after several minutes things become really really slow/choppy. I'm guessing it's a memory issue, but what specific settings do I need to adjust to smooth things back out? I'm sure I'm not the only one to experience this.
thanks guys,
Alan
Definitely sounds like a memory issue. You might have to cut back on a few things.
But first, try running the Snap kernel (I'd recommend 7.5-925) and see how that works for you.
drmacinyasha said:
Definitely sounds like a memory issue. You might have to cut back on a few things.
But first, try running the Snap kernel (I'd recommend 7.5-925) and see how that works for you.
Click to expand...
Click to collapse
Yea, I'm pretty sure it's memory related although I don't have that issue with Fresh's latest rom. I will try the snap kernel to see how that does...worth a shot.
thanks
Ok Im all backed up and ready to give it a go. I just have a few questions.
I don't use the Sense Launcher and have almost nothing on my home screens. just the scrolling dock at the bottom. launcher pro.
What are some things I am going to lose?
What is the differences in the Camera? Details?
What are the differences in the Dialer?
I like the dialer on Fresh 3.2 because of the FB integration.
I don't use 4G
I have not used HDMI as my flatscreen has a CPU connected already.
Is it possible to have the gallery from 3.2 with the FB pictures tab? or is that a sense thing?
Basically I don't know what all is strictly sense.
the default aosp dialer has what i consider to be a fault. you can't just spell out the name of contact. so i started using DialerOne.
dont' forget to check out both CM6 related threads (both are a bit quiet, but will answer many of the questions you may cross...search is your friend)
http://forum.xda-developers.com/showthread.php?t=735596
http://forum.xda-developers.com/showthread.php?t=729802
not sure on the FB stuff since I don't use it except to fill in the pics in my contact list.
give it a whirl. it will be a bit different.
enjoy.
Thanks Draginmagik (sportbike rider?) I had already thought out what I wanted to ask while at work and only had time to ask while on lunch. Figured Id get some input from some people who had used both but your input is appreciated to. I forgot about dialer one. That is one of my favorite things about the dialer I have. I tried Dialer One on The moment but couldn't get it to come up with the green button. I guess thats not a problem with the evo.
A few things ive noticed in Fresh 3.2 Vs Cyanogen mod is that...
Fresh's battery life (by itself, no kernal flashed) is by far the best of any of the ROMS ive used.
I like the sense camera sooooooo much more than the default android camera so thats a no brainer for me.
I do like the AOSP call history though, its much easier to navigate to and through.
Overall, im running Cyanogen right now but ill probably go back to Fresh later tonight... the battery difference is amazing.
Reading a little more I don't see where Sprint vvm / weird text message is there or not. I hated that on the Hero AOSP roms. Also want to get opinions on GPS as i need it to work at the end of this week. I will be flashing this tonight, just want to get some feedback so dont need the "just try it" post. Again, Im just trying to get a comparison so I know what to look for faster after I flash to be sure I like it before I head home this weekend. Once I get on the road and get back home, phone playtime is over until I get caught up at home . hahaha.
wanfaltm said:
A few things ive noticed in Fresh 3.2 Vs Cyanogen mod is that...
Fresh's battery life (by itself, no kernal flashed) is by far the best of any of the ROMS ive used.
Click to expand...
Click to collapse
Have you tried Kings ASOP kernrel? Im using #3 BFS and its great if I dont use the phone but it seems to suck down pretty quick when the phone wakes up. I'm over the battery thing, I just started carrying my usb cable in my back pocket and hit up a usb plug when I see one. lol But thanks for the info. Ill keep an eye on that too.
wanfaltm said:
I like the sense camera sooooooo much more than the default android camera so thats a no brainer for me.
Click to expand...
Click to collapse
Can you explain the difference? I just figured out on the Fresh camera that if you touch the screen it focuses on that spot. Awesome feature. Wish my real camera did that.
yamaford said:
Have you tried Kings ASOP kernrel? Im using #3 BFS and its great if I dont use the phone but it seems to suck down pretty quick when the phone wakes up. I'm over the battery thing, I just started carrying my usb cable in my back pocket and hit up a usb plug when I see one. lol But thanks for the info. Ill keep an eye on that too.
Can you explain the difference? I just figured out on the Fresh camera that if you touch the screen it focuses on that spot. Awesome feature. Wish my real camera did that.
Click to expand...
Click to collapse
not sure how the stock CM6 kernel is. a few days ago the CM6 nightly was upped to the .34 kernel. the custom ROM's are mostly on the .32 kernel still. i ran Kings on CM and it was 'ok'. the UI was smooth but the battery life reminded me of my previous stock kernels. perhaps as he rolls out more kernels that will be adjusted.
Cyanogen wrote the camera app in CM6. it also has the point touch focus. it has been much improved from the default aosp camera.
c'mon...make ur nandroid and jump in the beautiful cyan colored waters.
DraginMagik said:
Cyanogen wrote the camera app in CM6. it also has the point touch focus. it has been much improved from the default aosp camera.
c'mon...make ur nandroid and jump in the beautiful cyan colored waters.
Click to expand...
Click to collapse
All nanded up and flashed and restored most of my apps. Pandora sounds great. Ill test it in the shop but in the hotel its loud! I didn't Know that was a feature.
I liked the look of the dialer until the phone rang. YUK!
Im trying to finish up my Manup them but not sure if the ZIP I already have for the notification bar will work with CM6
The camera work good so far, as long as the pictures take good im OK with that. I hate 3d gallery, always have. its on my list of things to fix.
I downloaded the one in the link. Your on nightlys right? do they seem stable enough for you? whats the best way to try those out? The github link is kinda over my head.
DraginMagik said:
Cyanogen wrote the camera app in CM6. it also has the point touch focus. it has been much improved from the default aosp camera.
Click to expand...
Click to collapse
Cant forget having the ability to zoom while recording video. That's one of the big pluses of CM.
Well I found that the stock notification bar zip that I had on file won't work. I got the little blue android of death. After a quick reflash of cm6 all is well. still need that manup theme.
i'm on the 9/15 nightly. i think it was the 'swipe away items from the notification bar' feature or maybe a camera update that got me to flash up from the CM6final.
running it with -snap 7.6bfs kernel
currently, the CM6nightlys have slowed down so you just kinda keep an eye on the thread for nifty new features or updates...other than that, it's been very very stable for me since well before CM6final was released.
Hey xda
I come from cyanogen7 and went for the acesmod rom because I was missing the nice widgets, looks, and overall performance of sense. I have now spend some time on acesmod and I must say that it looks very nice and I especially think that the sense keyboard works a lot better when writing danish.
My problem is now that I find acesmod drinking my battery like crazy. Besides this I find it to be lagging a lot and not that smooth a experience that one could expect.
Do anybody know what I could do about this. Have you guys experiences the same.
Alternatively I am open to other sense based roms.
Thanks xda people!
Sent from my HTC Desire using XDA App
sense roms do use considerably more battery than cm7 roms, nothing you can really do about it apart from maybe calibrate your battery, theres a thread on here about how to do it
Again, calibration is not to be used to increase battery performance... Disable htc.com sync, use as less widgets and let them sync as rarely as possible. Disable pocket mode too, sign out of Latitude and make sure that your market and maps are not in the foreground when you turn your screen off as they won't release the wakelock then.
I can hear that there is not much I can do. Had every updating things disabled and also got the black wallpaper for power saving.
Are there then any sense based roms you would prefer over acesmod 007?
Sent from my HTC Desire using XDA App
I have good battery life on 007 mod.... But I have used only sense roms, so I cannot compare it to others.
mine life battery is good, try using andrev_oc
andrev_oc? (This is only my second rom)
see here how to install
http://forum.xda-developers.com/showpost.php?p=16803896&postcount=355
hope it helps
edit: with ES File Explorer (in settings tick the root explorer and mount file system) copy the freqs to system/etc/andrev_oc
Interesting... I have tried a few Sense ROMs and was quite dissapointed by the performance, memory consumption and battery life, went to CyanogenMod 7.1 and now tried Acesmod007.
For me, it does everyhing as smooth as cyanogen, and something obviously very strange - the same or maybe even longer battery time. A full day with gmail sync, active gtalk usage, a little browsing, ~25min of calls, messaging... on 2G+3G and (mostly) WiFi. And the battery level is still not very low.
I'm very happy with this
The new 007 mod (v39) has even better battery life!
And the speed...
lenyy3212 said:
Interesting... I have tried a few Sense ROMs and was quite dissapointed by the performance, memory consumption and battery life, went to CyanogenMod 7.1 and now tried Acesmod007.
For me, it does everyhing as smooth as cyanogen, and something obviously very strange - the same or maybe even longer battery time. A full day with gmail sync, active gtalk usage, a little browsing, ~25min of calls, messaging... on 2G+3G and (mostly) WiFi. And the battery level is still not very low.
I'm very happy with this
Click to expand...
Click to collapse
and you dragged up an old thread to post this why exactly?
elliottg61 said:
and you dragged up an old thread to post this why exactly?
Click to expand...
Click to collapse
It's definitely more informative than what you've posted... :-\