Related
getting mt3gs in two weeks
but i doubt i will root it
has anyone seen and IMPROVEMENT before with rooting?
not as in features and whatnot but as in speed, stability, battery life?
be honest here
i had a g1 and i rooted it and every rom that was made [FAST] or [STABLE]
was really just an easier way to say [ALMOST WORKS AS GOOD AS STOCK, BUT NOT REALLY, JUST ALMOST]
i have a feeling if i root my slide that i will just be on an epic quest to find a rom that actually works meaning functions properly
i want to be able to base the rom i use on features and not functionality...
has anyone noticed any improvements? be honest here
im a die hard android lover and have done every hack and run every rom there is
but i feel like you get so used to how they work that your idea of blazing fast
is in reality just barely keeping up with a stock setup
i have yet to find a rom that will still be blazing fast a week after use
they all seem to crash and burn miserably
has anyone else noticed this?
i just really want to know if it is an improvement to root my mt3gs or just kind of a "thing to do"
and yes this is my first post but i never felt like me taking up space would help anyone
i learned everything i know from here but i am no dev by any means
i just felt like this is something that needed to be said
ParkerOviedo said:
getting mt3gs in two weeks
but i doubt i will root it
has anyone seen and IMPROVEMENT before with rooting?
not as in features and whatnot but as in speed, stability, battery life?
be honest here
i had a g1 and i rooted it and every rom that was made [FAST] or [STABLE]
was really just an easier way to say [ALMOST WORKS AS GOOD AS STOCK, BUT NOT REALLY, JUST ALMOST]
i have a feeling if i root my slide that i will just be on an epic quest to find a rom that actually works meaning functions properly
i want to be able to base the rom i use on features and not functionality...
has anyone noticed any improvements? be honest here
im a die hard android lover and have done every hack and run every rom there is
but i feel like you get so used to how they work that your idea of blazing fast
is in reality just barely keeping up with a stock setup
i have yet to find a rom that will still be blazing fast a week after use
they all seem to crash and burn miserably
has anyone else noticed this?
i just really want to know if it is an improvement to root my mt3gs or just kind of a "thing to do"
Click to expand...
Click to collapse
I came from a G1 also and I can agree with what you say....Kinda. I was able to find a few ROM's for my G1 that were very stable and much faster than my stock ROM. I used several for weeks and didnt have any problems with them slowing down' but there were some that didnt work as well also.
You will definitly see speed improvements in the future for the MTS but right now it is so new that the ROMS coming are doing smaller tweaks such as removing all the bloatware and alot of the sense UI stuff.
After you get your MTS you will want to root it when you see all the crap bloatware and stuff that t-mobile and Htc put on it. Thats what got me to do it.
I forgot to tell you: I havent noticed a speed change since I rooted but those changes will come. A overclocking kernel will be made so it can be overclocked and that will speed it up. I will say it is pretty fast right now ( more than I thought it would be) and coming from a G1 it is a big improvement.
Rooted myself but still on the stock ROM. The phone has not slowed down any since I have had it or since I have Rooted. I happen to like the Sense UI so I am waiting for a 2.2 With a Custom Sense/speed improvements.
That is exactly how I felt about the G1. And the Slide is so fast that I was hesitant to root and jump into someones ROM that is supposedly stable and fast but in reality is not. Luckily we can root and stay on the Tmobile ROM which is what I did.. now I have some of my convenient root apps including wifi tether and hopefully soon can delete some bloatware and ill be happy as can be with the stock rom.. no apps2sd no non sense crap.. I like the phone how it is.. That being said my bluetooth has been acting up and I did not notice this until after rooting..
Anyone please?
My holiday is ending, and I still have to find an answer!
Thanks.
There are a lot of lag fixes, and their differences are beyond 'this one is better'.
So in the end it's down to personal preference and the way you use your phone.
I personally like supercurio's Project Voodoo lagfix the most. He will release a public version (beta2) pretty soon .
If you want a lagfix right now, use One Click Lag Fix. If you can wait, wait for supercurios Voodoo lagfix beta 2.
There is a tiny battle going on between filesystem of choice - EXT2 or EXT4 - for lagfix. This is good for us users for speed and stability of the fix. I would suggest you wait for a couple of days to see if Voodoo Beta 2 fits you. Else you have OCLF which yields a lot of Quadrant scores and keeps a lot of people happy here already.
Personally, I am on JM7 with Voodoo Beta 1.
I have JM7 with the One Click Lag Fix, suits me perfectly, the phone just "flies". Also, the ease of install is the best - just install it from the market.
I have a couple of questions. Do I need to root in order to do the lag fix? I noticed that the One Click Lag Fix app can root my device too.
Also, how will my phone react when Froyo is released? Can I upgrade my phone through Kies without doing anything, or do I need to somehow get rid of root/lag fix?
Tried all the lag fixes EXCLUDING Voodoo. I can say my phone is better off them even when it WORKS. While they do some "cosmetic" speed improvement, I find them actually INCREASING lag in some typical activities like installing, uninstalling apps, multitasking, etc.
Latest I tried OCLF 1.6 and finally revert the lag fix to see my phone working "normally". Hope you could read through the punctuations
Prankey said:
Tried all the lag fixes EXCLUDING Voodoo. I can say my phone is better off them even when it WORKS. While they do some "cosmetic" speed improvement, I find them actually INCREASING lag in some typical activities like installing, uninstalling apps, multitasking, etc.
Latest I tried OCLF 1.6 and finally revert the lag fix to see my phone working "normally". Hope you could read through the punctuations
Click to expand...
Click to collapse
what version rom are u using??
The easiest lagfix (which also greatly improves GPS (in my opinion) as a side benefit) is to just upgrade your firmware to one of the following: XFJM6, HVJH1, or XWJM7. Note the bolded F in the JM6, XWJM6 is not lag-free.
Those three firmwares seem pretty lag-free out of the box, though after a lot of up time, you might get some lag, but that took a couple of days for me, and a reboot fixes.
The next easiest lag-fix is to disable all the fancy animations and window transitions in the GUI. Do this in Settings.
The next easiest lag-fix is to get AutoKiller from the Market and use one of the medium to aggressive settings in the pre-sets. This works well at reducing some lag, and has the benefit of being easy to uninstall if you're not happy with it for some reason.
Now, if those three things don't give you a happy phone experience, personally I am in the Voodoo (by curio/supercurio) camp to be the BEST experience so far. Easy to install, best overall reduction in lag (as in I have ZERO lag even after 90+ hours of uptime and heavy usage), no Market install/download issues, no random freezes. EVERY OTHER lag-fix, from Mimocan to RyanZA's OCLF have those issues still, Voodoo does not, for me.
If I couldn't use Voodoo, I would use the mimocan fix, specifically by using the Samset/mimocan kernel.
I won't get into the ext2 vs ext4 debate that the supercurio and ryanza camps have fallen into.
My advice right now, try the first three things I suggested and WAIT until the end of the week to try supercurio's Voodoo Beta 2 when he goes public with it.
As of right now, I am on XWJM7 firmware with voodoo beta 1, and installing voodoo beta1 is the first time since buying this phone that I have been satisfied with its performance. YMMV, of course.
edit: ps - to be clear, I have tried just about all of them...
distortedloop said:
The easiest lagfix (which also greatly improves GPS (in my opinion) as a side benefit) is to just upgrade your firmware to one of the following: XFJM6, HVJH1, or XWJM7. Note the bolded F in the JM6, XWJM6 is not lag-free.
Those three firmwares seem pretty lag-free out of the box, though after a lot of up time, you might get some lag, but that took a couple of days for me, and a reboot fixes.
The next easiest lag-fix is to disable all the fancy animations and window transitions in the GUI. Do this in Settings.
The next easiest lag-fix is to get AutoKiller from the Market and use one of the medium to aggressive settings in the pre-sets. This works well at reducing some lag, and has the benefit of being easy to uninstall if you're not happy with it for some reason.
Now, if those three things don't give you a happy phone experience, personally I am in the Voodoo (by curio/supercurio) camp to be the BEST experience so far. Easy to install, best overall reduction in lag (as in I have ZERO lag even after 90+ hours of uptime and heavy usage), no Market install/download issues, no random freezes. EVERY OTHER lag-fix, from Mimocan to RyanZA's OCLF have those issues still, Voodoo does not, for me.
If I couldn't use Voodoo, I would use the mimocan fix, specifically by using the Samset/mimocan kernel.
I won't get into the ext2 vs ext4 debate that the supercurio and ryanza camps have fallen into.
My advice right now, try the first three things I suggested and WAIT until the end of the week to try supercurio's Voodoo Beta 2 when he goes public with it.
As of right now, I am on XWJM7 firmware with voodoo beta 1, and installing voodoo beta1 is the first time since buying this phone that I have been satisfied with its performance. YMMV, of course.
edit: ps - to be clear, I have tried just about all of them...
Click to expand...
Click to collapse
I agree completely with you, except about waiting for Voodoo BETA 2 at this point. Please note the BETA - even though it will be pretty heavily tested, please don't jump onto these lagfixes until they are out of beta, especially if you don't know what you're doing. There may be complications, especially if you grab it as soon as it's released.
Please, this type of thing is marked BETA for a reason! When it goes to RELEASE, then you can jump on it!
Of course if you want to test stuff out, then please try the betas, but things can and do go wrong!
As far as the OCLF fix, it has proven so far to be very safe, with thousands of people using it without issue so far. Comments and stats available here, and this only includes market downloads: http://www.appbrain.com/app/com.rc.QuickFixLagFix
The general consensus is that OCLF does make your phone faster, but these types of things are very subjective. It also doesn't use custom kernels or similar, and works on all firmwares, which is a plus for some.
Your point that Voodoo is in beta, make that BETA, is well taken. Supercurio won't release it to public until it's well tested. Some of the other methods released here weren't approached so conservatively in their early days, but anyone in this particular forum should be aware of the risks.
Please note that the original poster said "I want the best/newer one (in terms of speed and stability), I don't mind if its not the easiest to install," which implied to me he's up to some beta stuff.
That said, your method's lack of needing custom kernels being a plus is spot on as well, but it also opens the door to the whole ext2 vs ext4 debate, since you're using ext2 and that's why it doesn't need a custom kernel, and I specifically said that I wasn't going to step into that one...
Anyways, I think your method has some plusses, of course, and it turns in some amazing Quadrant scores, for whatever that's worth, but in every day use, lag and GUI freezes still exist occasionally with it, and that is not my experience with voodoo. Voodoo also turns in some great Quadrant scores (about right in the middle of what mimocan and OCLF give me (mimo-1400, Voodoo-1800, OCLF-2200)).
Voodoo works best for me in every day "feel" of the phone. It's my recommendation to anyone if they can get into the beta. It's truly lag-free. And free space on the device is accurately reported.
Mimocan works well and is based on the apps2sd concepts that have been tried and tested over many devices and firmwares and mods like Cyanogen's. It's mostly lag-free.
OCLF is super easy to install with apps from the app store and batch programs for Windows users and has a very dedicated and respected devs behind it. It's mostly lag-free, but I'm not comfortable with the whole ext2 loop mount business it uses and the last time I used it had the disadvantage of inaccurate free space reporting, and the huge file it creates makes clockwork backups very slow and very large. I'm not recommending against OCLF, It's just not my first choice.
RyanZA said:
I agree completely with you, except about waiting for Voodoo BETA 2 at this point. Please note the BETA - even though it will be pretty heavily tested, please don't jump onto these lagfixes until they are out of beta, especially if you don't know what you're doing. There may be complications, especially if you grab it as soon as it's released.
Please, this type of thing is marked BETA for a reason! When it goes to RELEASE, then you can jump on it!
Of course if you want to test stuff out, then please try the betas, but things can and do go wrong!
As far as the OCLF fix, it has proven so far to be very safe, with thousands of people using it without issue so far. Comments and stats available here, and this only includes market downloads: http://www.appbrain.com/app/com.rc.QuickFixLagFix
The general consensus is that OCLF does make your phone faster, but these types of things are very subjective. It also doesn't use custom kernels or similar, and works on all firmwares, which is a plus for some.
Click to expand...
Click to collapse
distortedloop said:
That said, your method's lack of needing custom kernels being a plus is spot on as well, but it also opens the door to the whole ext2 vs ext4 debate, since you're using ext2 and that's why it doesn't need a custom kernel, and I specifically said that I wasn't going to step into that one...
Click to expand...
Click to collapse
Not true at all, EXT4 is very easily added to the running kernel as a module. Tayutama has an EXT4 version that works fine on the stock Samsung kernel. People just don't use it very much because it's slower. *shrug* I haven't had any requests to include EXT4 in my app either, so I haven't done it yet. And you stepped into it, but I needed to clear it up.
distortedloop said:
Anyways, I think your method has some plusses, of course, and it turns in some amazing Quadrant scores, for whatever that's worth, but in every day use, lag and GUI freezes still exist occasionally with it, and that is not my experience with voodoo. Voodoo also turns in some great Quadrant scores (about right in the middle of what mimocan and OCLF give me (mimo-1400, Voodoo-1800, OCLF-2200)).
Voodoo works best for me in every day "feel" of the phone. It's my recommendation to anyone if they can get into the beta. It's truly lag-free. And free space on the device is accurately reported.
Mimocan works well and is based on the apps2sd concepts that have been tried and tested over many devices and firmwares and mods like Cyanogen's. It's mostly lag-free.
OCLF is super easy to install with apps from the app store and batch programs for Windows users and has a very dedicated and respected devs behind it. It's mostly lag-free, but I'm not comfortable with the whole ext2 loop mount business it uses and the last time I used it had the disadvantage of inaccurate free space reporting, and the huge file it creates makes clockwork backups very slow and very large. I'm not recommending against OCLF, It's just not my first choice.
Click to expand...
Click to collapse
Unfortunately, both mimocan and voodoo (BETA1, hopefully fixed in BETA2) have very annoying battery issues, and bad battery life is worse than occasional lags. Your experience with it might have varied though.
I'm currently trying to get a fix similar to voodoo going that won't need a custom kernel, but it unfortunately needs gnu parted to do that. And gnu parted is proving to be horribly difficult to port to Android.
RyanZA said:
Not true at all, EXT4 is very easily added to the running kernel as a module. Tayutama has an EXT4 version that works fine on the stock Samsung kernel. People just don't use it very much because it's slower. *shrug* I haven't had any requests to include EXT4 in my app either, so I haven't done it yet. And you stepped into it, but I needed to clear it up.
Unfortunately, both mimocan and voodoo (BETA1, hopefully fixed in BETA2) have very annoying battery issues, and bad battery life is worse than occasional lags. Your experience with it might have varied though.
I'm currently trying to get a fix similar to voodoo going that won't need a custom kernel, but it unfortunately needs gnu parted to do that. And gnu parted is proving to be horribly difficult to port to Android.
Click to expand...
Click to collapse
No, I still haven't stepped into the ext2 vs ext4 debate, but I stand corrected that you don't need a custom kernel to use it. Is that a recent innovation?
I'm specifically avoiding the speed and potential for data loss argument. It's debated ad nauseum in several other threads.
I suspect the reasons you didn't see requests for ext4 in your own apps are two-fold. 1- you are very clearly against it, and argue strongly that ext2 is faster and that that is part of the reason your fix works and that ext4 would slow things down *shrug* and 2- many, like me, incorrectly assumed you needed a custom kernel for it. Go figya!
I've heard battery complaints about your fix method as well. I do not experience them at any noticeable rate with any of the methods. I've never made it through a full day without using up most of battery with any smartphone since my first iPhone; others claim to make it for 2-3 days. Who knows what we all do different that impacts this. It's a cheap and easy shot to take at any app or rom or mod, and for every one complaint of "drains my battery faster" there's usually a post from someone who says "doesn't affect mine."
Battery complaints are such a sore spot in the Android community. Every new custom ROM for the Nexus One, the first thing you'd see is dozens of complaints of battery life sucking. It's the same with the SGS, and now the various lag-fixes.
I'm not sure which is more obsessed about with SGS owners; lag, GPS, or battery life.
distortedloop said:
No, I still haven't stepped into the ext2 vs ext4 debate, but I stand corrected that you don't need a custom kernel to use it. Is that a recent innovation?
I'm specifically avoiding the speed and potential for data loss argument. It's debated ad nauseum in several other threads.
I suspect the reasons you didn't see requests for ext4 in your own apps are two-fold. 1- you are very clearly against it, and argue strongly that ext2 is faster and that that is part of the reason your fix works and that ext4 would slow things down *shrug* and 2- many, like me, incorrectly assumed you needed a custom kernel for it. Go figya!
I've heard battery complaints about your fix method as well. I do not experience them at any noticeable rate with any of the methods. I've never made it through a full day without using up most of battery with any smartphone since my first iPhone; others claim to make it for 2-3 days. Who knows what we all do different that impacts this. It's a cheap and easy shot to take at any app or rom or mod, and for every one complaint of "drains my battery faster" there's usually a post from someone who says "doesn't affect mine."
Battery complaints are such a sore spot in the Android community. Every new custom ROM for the Nexus One, the first thing you'd see is dozens of complaints of battery life sucking. It's the same with the SGS, and now the various lag-fixes.
I'm not sure which is more obsessed about with SGS owners; lag, GPS, or battery life.
Click to expand...
Click to collapse
I get tons of emails and messages every day about OCLF, and none have mentioned EXT4 or battery that I can think of. About a million other issues though! Mostly getting to recovery console though.
I haven't heard any battery complaints about OCLF so far, but I may have just missed em. Anyway, my complaints with battery life on custom kernels are entirely that - my complaints. Whenever I use a custom kernel and leave my device overnight, it drains around 30% of the battery or more. With a Samsung kernel, it usually drains at most 10%. This seems to be mirrored by others I talk to as well. I believe it may be wifi-driver related - the GPLed driver may not be as good as the proprietary driver or something equally bizarre.
I agree with the fact that RyanZa's solution is by far the simplest of the methods available. You can easily make out that me is a still a noob....
I don't speak for others, but my best guess is for some the ease of use matters, and for some, regardless of the complexity involved, the other methods work just fine. It usually really is a personal choice and an equally personal experience. What works best for some, does not necessarily work best for others. Some like a mild fight put up by the hardware, some dont (I dont. Yet!! )
Not wanting to get caught in you folks exchange here, but I guess the saying sums it all.
To each, his own....
P.S.: Dont flame for it...
Cheers....
skiddhard said:
Some like a mild fight put up by the hardware, some dont (I dont. Yet!! )
P.S.: Dont flame for it...
Click to expand...
Click to collapse
Gonna flame you! What are you doing here if you don't like messing with your phone/toy?!
But yeah, that's the whole point of computers, phones, and almost everything else. Making it easier for others.
Wow! Thanks for the answers guys!
I think I'm gonna wait 1 or 2 weeks... maybe the 2.2 update comes to change all of this.
Regards!
Paulo
I won't go into saying which method is best, definitely not, nor will I mix myself into ext2 vs ext4.
However, I have seen some people claim both in this thread and in other threads that upgrading firmwares alone is enough. I assure you it isn't. Whether you use mimocan's, mine, Ryan's, curio's, etc fix they all result in having a much faster device. Sure, each of the fixes has their own quirks, con's and pro's, but give it time, one of us will get this exactly right, sooner or later. If not, mayhaps Samsung will.
To be honest, I didn't notice _that_ much difference in speed initially either. And indeed noticed that in some places it was occasionally a tad slower (though with the latest versions of the various fixes I haven't personally experienced this). The only place where I noticed an amazing difference was the email app (5 exchange accounts synced, with 100's of messages a day, on 30-day sync). The difference just blows you away - with setting up the accounts too, not just using them.
But today I had the greatest notice of all. By now some of my coworkers have SGS's as well, but I'm the only one running a lagfix at the moment. It's in the small things: when I put my lagfixed device next to one of their non-lagfixed devices, even with the latest firmwares, it's just amazing how much faster mine is, how much more responsive. Simple taps that resond twice as fast. Granted, theirs aren't usually slow, but mine is just noticably faster, to a level where I'm annoyed by the few millisecond delays when handling their devices.
At the moment, I would say curio's method is the most promising, though certainly not what I would advise just anyone to use. And by curio's method I mean converting the flash itself to a filesystem, instead of using a filesystem image inside an existing filesystem. If his implementation will be the best, remains to be seen
Don't make the "n00b" mistake: I don't see a difference, I'll uninstall. Because probably, your device is fresh and clean. Once it gets cluttered a bit the lagfixed definitely help!
I currently use official JM1 firmware with OCLF apk and find it still lags a bit although not as much. I'm a little worried about the custom kernel fixes not working once froyo comes out as it's mere weeks away.
lokhor said:
I currently use official JM1 firmware with OCLF apk and find it still lags a bit although not as much. I'm a little worried about the custom kernel fixes not working once froyo comes out as it's mere weeks away.
Click to expand...
Click to collapse
Like most, I would say wait till Curio's beta2 is released later this week (hopefully). Ive used almost every variation of every method of seen of the forums, and found the using an ext4 partition on my external sd to store my dalvik-cache and app data is the most smoothest & most reliable 'band-aid'.
Although all the loopback methods work well (EXT2 or EXT4, not getting into it), data corruption is inevitable due to the fact that our loopback partition is never getting properly unmounted on shutdown or reboot. Although the corruption may be mild, I found it eventually starts to lag again as you use the fix for a week or more (more corruption each reboot\power cycle). Even using a fschk, you eventually will get corruption
Ive used all the loopback method several times for around a week or so, and found the smoothest, most reliable method is using an ExternalSD for dalvik-cache and app data until a native EXT file system can be put on /data.
Although Ive throughly tested my conclusion (and I wish it werent true, as I love the speed immediately after installing a loopback lagfix), these are simply my observations and I'm throwing them out there for others.
Thanks to everyone who is working hard to fix the "lag" issues on Galaxy S devices. Its quite an ordeal to fix this, and IMO, not enough "thank yous" get passed around, despite differing opinions.
hi all, i'm still here
i installed android on my kaiser (scooter's cyanomod build froyo), and i'm happy (exept for the camera... still hoping) but i have a question :
it's normal that the animation are slow, the menu are ... don't know... "fat" to appear even with a fresh installation...
i mean, i know that kaiser is not the fastest phone on the Earth, but i think that a completely empty android coud be handeled by it..
i tried to play with compache settings, but i dont have manu results, and i prefere not to overclock, due to the high battery drain
ps : i tried to search in the forum and in google, but with no results
thanks !
I know what you mean. I wasn´t here in the Kaiser thread for a long time because i have a HTC HD2 now. But i loved Android for my Kaiser.
I can say that the older Donut builts runs much faster/smoother than froyo. The Kaiser is an old Phone but quite good. But it is like as it is on PC. You can run Vista on an old machine but the experience is... uhm...
I had Myn´s Warm Donut on my Kaiser but it seems that there is no further development. But RLS5 was fast an stable...
Another thing for smoothiness is the kernel you use. I changed to an older kernel because under a newer one the animations seems to be laggy. I dont know how it is now with the kernels. But you should test some different kernels.
I should dig out my Kaiser an play a little bit around with the new kernels and androids... ;-)
@ highcoder:...
2 builds of Froyo I would suggest is ThoughtlessKyle's NSS (Not So Super) Froyo and Incubus26Jc_'s Super FroYo RLS15 with .25 for a kernel. You have to put in a wireless update, and either 1.65 or 1.70 radio ROMs (both work great), but so far so good. 520MHz OC and everything on NAND and the only app that FC's on me is Pandora radio (I guess because it uses so much memory for each song)
I will probably be trying ThoughtlessKyle's Fat Free Froyo soon with the same .25 kernel here soon, but the 2 suggested above seem to be what I like to use.
Fat Free Froyo is by far the fastest release I tried.. But I'm still facing some problems with my battery, it drains so fast.. I think i will go a release back and try Donut for a change
EIDT:
highcoder said:
I can say that the older Donut builts runs much faster/smoother than froyo. The Kaiser is an old Phone but quite good. But it is like as it is on PC. You can run Vista on an old machine but the experience is... uhm...
Click to expand...
Click to collapse
Best explanation quote
thanks for reply
poor kaiser, is a little oldie phone =) but with android maquillage tadaaan, it seems brand nes (ehm...)
i'll try with a stable .25 kernel version then
but htc touch (touch dual) is better than kaiseR? the cpu freq is the same... (even worst, in compasrison wih the first touch 200mhz)
thanks again
I'm running the .35 kernel with an overclock at 500Mhz done using Atools.I have always overclocked to 500 using this method & my battery lasts for a good couple of days with moderate use.well,texting,the odd phone call and a bit of data usage.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
scooter1556 said:
I'm running the .35 kernel with an overclock at 500Mhz done using Atools.I have always overclocked to 500 using this method & my battery lasts for a good couple of days with moderate use.well,texting,the odd phone call and a bit of data usage.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
Click to expand...
Click to collapse
I found using Vaniji Eclair with the .25 kernel is the fastest, and gives me decent battery life (about 12hrs with moderate use). I've been using Gingerbones with the .32 kernel, but because of how unstable .32 kernel is, I kept getting crashes, data corruption, etc...
Scooter, how did you get the .35 kernel? Can you IM me how or where you got it, so I can maybe compile my own version? The thought that you get several days under moderate use makes me want to get inside the kernel to check out if CPUFreq is indeed working on that kernel.
can i have your kernel too? or where to get it
thanks !
Krazy-Killa said:
Scooter, how did you get the .35 kernel? Can you IM me how or where you got it, so I can maybe compile my own version? The thought that you get several days under moderate use makes me want to get inside the kernel to check out if CPUFreq is indeed working on that kernel.
Click to expand...
Click to collapse
The kernel i am using is compiled from dzo's original .32 git repo, i have made a few adjustments to it which i can't remember because it was before christmas. Once i've got my jan exams out the way i will do a git diff and push any changes i have made. Life's a little chaotic at the minute though. I am running my 5.5 build, phone came off charge at 9 this morning and was reading 97%, after a day of texting, some data usage and general gaming on the toilet (as you do!!) my battery is reading 70%. It's the original samsung battery too, so it's quite a few years old.
scooter1556 said:
The kernel i am using is compiled from dzo's original .32 git repo, i have made a few adjustments to it which i can't remember because it was before christmas. Once i've got my jan exams out the way i will do a git diff and push any changes i have made. Life's a little chaotic at the minute though. I am running my 5.5 build, phone came off charge at 9 this morning and was reading 97%, after a day of texting, some data usage and general gaming on the toilet (as you do!!) my battery is reading 70%. It's the original samsung battery too, so it's quite a few years old.
Click to expand...
Click to collapse
Oh nice! Looking forward to compiling this myself, though really don't mind trying it out now. lol
Well back on topic, since everyone here is saying go Donut, I think I'll be a rebel and say go Eclair, it's not far from Froyo, and ahead of Donut, so you kinda get the inbetween of the two.
today i tried to overclock my kernel to 500 mhz...
now, i see a lot of artifatcs... now i rollback, but anyone had the same issue?
with "atools" can i set something that can help me to inmprove performance?
thanksy
update : rolled back to base kernel... but artifacts still here
another update : downloaded from frash the kernel, applied the overclock to 500 and no other options : no more artifacts
Ok i´ve reactivated my Kaiser to try around a little bit.
The last one i´ve tried was Fat Free Froyo with the latest 2.6.32 Kernel from DZO and it´s a very fast & stable built. Not as fast/smooth as Myn´s warm Donut (with an older Kernel) but for a Froyo on Kaiser much impressive.
@bboygolem
Overclocking ist not the best way to improve performance. Better... its a poor way. Even if you have a new big battery the batterylife is not so long... one day or so... and if you now speed up your CPU your batterydrain is much higher, the thermal stress for CPU and other components is higher and the chance of force closes, app hangs, artifacts, system crash, data corruption/loss is very high. On the other side you have only a little performance increase. Too little that you dont recognise it in all day use. Of course a calculating benchmark will show you maybe a 20% performance boost but only for calculating things. But the Speed of an operating system is defined by the weakest thing in the whole chain.
Better get a good optimized android built. building a android for kaiser nowdays is easy as going to toilet, but cook a highly optimized, smooth runnin, slim rom is the real deal...
So you have to test and compare the builts and the kernels (the newest is not always the best).
The best (fast,smooth,stable) built on the first Forumpage is Fat Free Froyo.
But still the best (most suitable for Kaiser) built i´ve ever tested is Myn´s Warm Donut RLS5 in conjunction with an older Kernel from Kallt_Kaffee. The best combination ever.
It is an Android 1.6 so it is older but smaller too. So it runs faster and smoother and you have more RAM for apps. Especially when you run resourcehungry programs like Navigon Mobile Navigator you need the extra Memory. With eclayr, froyo you have only force closes...
But at least it´s on you. Your favors, your taste, your choice...
highcoder said:
it´s a very fast & stable built. Not as fast/smooth as Myn´s warm Donut (with an older Kernel) but for a Froyo on Kaiser much impressive.
Click to expand...
Click to collapse
May I ask about the battery consumption in Myn's warm Donut release? is it the same as Froyo built?
highcoder, thanks for you reply, but i have some questions:
1 - i know that overclocking the cpu , i have a more battery drain and disease percentage, but i noticed a little performance increase.... can it be "placebo effect"?
2 - I thought to use the old kernel, but i read somewhere that is slower than the new one. It's true?
3 - I can install the donut, i don't care about eyecandy's, but I'm afraid that a lot of apps in the market shall not work with the "donut" distribution.. am i wrong? using fat free froyo with the old kernel shall improve my performance?
thanks again
sorry, dobule post
Oh that are a lot of questions i cant answer properly.
The overclocking has of course an effect. But it is only a little average performance increase. Hard to notice that. the most of that is really placebo. But the risk of brick something or to have an instable system ist sigificant higher... so its not worth it...
i dont know about the older kernels because i have a HTC HD2 since 6 Month so there was a lot of change here. Froyo have got a real performance increase the last months. So the kerneldevs and the chef´s here do a good work. But the best Foyobuilt (2.2) here with the newest kernel don´t beat the smoothieness and felt speed of Myn´s warm Donut (1.6).
I never had a problem with market apps and donut. Shure there will be apps that wont work with donut anymore but for that case there are enough alternative apps that will work.
If you want i can search my HDD´s for the kernel i used an give it to you...
But now i´ll go to bed.
thanks highcoder, it'd be very kind from you =)
have a good night
@bigboss2200 & bboygolem
Battry Drain Test with newest DZO Kernel and Fat Free Froyo is in progress. After that i will test Myn´s war Donut with a NEW Kernel. So i can compare these builts about batterydrain and Speed. May be the speed improvements of the new Froyobuilts i´ve noticed are only Kernel related. In this case Myn´s warm donut should benefit from this kernel optimizations too an we will have a real performance boost. I'm curious about it.
I will post my results...
in the meantime, i installet latest dzo kernel and fat free froyo, and it seems stable and usable
but if using the .25 kernel i will be able to use the camera and to shut down the phone permanently, keeping an accettable speed, i think i'd downgrade the kernel
i'm looking forward to see your test results
ok i have tested Myns warm donut with .32 kernel = laggy animations
so i downloaded the latest .25 kernel from here. After that i downloaded the mandatory update for all older builts from here. Without this update wifi won´t work. In newer builts it is cooked in already.
Flash the kernel.
Install Myns
Install Update
Weeehaaaa! It works with the newer .25 too. Smooth animations, very responsive and snappy. WLAN works fine... battery drain will show a longer test...
I always made some adjustments. Go to spareparts -> Window Animation = fast and transition animation = fast, fancy input animation = on
Give it a try... Let your Kaiser feel "young" again ;-)
EDIT: Dont use the builtin Astro filemanager. Its outdated... Download a newone from market. My Favourite is Estrong ESfileexplorer. Because it can handle FTP and SMB. That mean Windows network shares too. So you can exchange your files over wlan with your PC.
Did anyone tested this build? That thread stopped 2 weeks ago and no one seem to comment on it no more. Please post your experience good or bad, here or in the original Andasa thread. Thank You all.
minimimi98 said:
Did anyone tested this build? That thread stopped 2 weeks ago and no one seem to comment on it no more. Please post your experience good or bad, here or in the original Andasa thread. Thank You all.
Click to expand...
Click to collapse
i am giving it a go now with HO!NO! kernel v5 and it is very quick and smooth. the ui kicks ass and shows off our nitro's glorious screen capabilities better than any other rom i've run and i've run them all. i've not got enough time with it to gauge the battery, it does force close when trying to access about phone in the settings.
it moves the notification bar to the bottom and makes the icons in it a bit bigger and much more legible, speaking of the nav bar, i like how this handles the notification drawer, very slick.
i recommend giving it a whirl, at least temporarily, just to see what the ui and graphics are like on the nitro HD.
:good:
OK, I took a plunge and I do like the result of it. Still on stock kernel though. Also I have no problem on settings->about, no FC, all sweet
Will stay on stock kernel for some time, will see if I jump to the V5 side
What is the benefit, beside overclocking? As phone is heating like space heater as it is, I do not need it to fry my...
It was overheating on GB already, so nothing new here.. and a few people had same issue, so I even installed Ant Tu-Tu to under-clock to 1.3, so it would not burn hole in the pocket.
Ok, So far, so good, smooth install, Quadrant jumped from 2.3K to 3.2K, so I am happy.
Thanks Andasa, nice ROM
minimimi98 said:
OK, I took a plunge and I do like the result of it. Still on stock kernel though. Also I have no problem on settings->about, no FC, all sweet
Will stay on stock kernel for some time, will see if I jump to the V5 side
What is the benefit, beside overclocking? As phone is heating like space heater as it is, I do not need it to fry my...
It was overheating on GB already, so nothing new here.. and a few people had same issue, so I even installed Ant Tu-Tu to under-clock to 1.3, so it would not burn hole in the pocket.
Ok, So far, so good, smooth install, Quadrant jumped from 2.3K to 3.2K, so I am happy.
Thanks Andasa, nice ROM
Click to expand...
Click to collapse
the v5 kernel is undervolted as well as being overclocked, not sure if that would help with the heat issue, the kernel does make it all run a bit snappier imo.
i wonder why i am getting the about phone fc, i even backed up this install, wiped all data and did a fresh & clean install and still get the about phone fc! no biggie though.
I installed kernel V5 and got Quadrant boosted to 3600, not bad at all, and that is at stock speed 1.52 Ggz
I am afraid to move it up, though, or it might melt from heat.
One thing I noticed that this ROM does not have Exchange service, so I had to find it in another post here on xda.
Battery drain is much higher than on GB, but I guess that was expected and talked over in many other posts.
Hello,
G2 owner here, I am considering flashing a new rom onto my not so tech savy friends Desire HD. I'm wondering how good the experience of the JB roms is? On the G2 the roms are unusable but it's certainly not a good experience, lots of random slow downs and lag, plus the camera quality sucks. I'm wondering if that is much the same on the DHD.
Would you flash a JB rom onto your Mum's phone, or would you stick with CM7? Consistent random slow downs / lag plus sub par camera quality isn't acceptable!
Also, if someone has a nice clear guide handy for rooting and installing recovery from 2.3 a link would be appreciated
Thanks!
I think you should be here http://forum.xda-developers.com/forumdisplay.php?f=750.
Good luck!
koningjim said:
I think you should be here http://forum.xda-developers.com/forumdisplay.php?f=750.
Good luck!
Click to expand...
Click to collapse
Sorry my bad! I am a G2 owner, but I am looking at flashing a rom onto my friend DHD. -- updated the OP
whilst the jb roms are very stable, i wouldnt recomend them for a complete technaphoab. better safe than sorry.
on the other hand, http://forum.xda-developers.com/showthread.php?t=1968854 this is very good, but synergye(lead dev) is focusing more time on http://forum.xda-developers.com/showthread.php?t=2003273 this.
the sense interface is very basic http://forum.xda-developers.com/showthread.php?t=1839004
and if you want the mind numbing simplicity of ios, try http://forum.xda-developers.com/showthread.php?t=1991558 (i havent tried this one yet though)
as always, read the threads first
Hard to tell, depends what they use... JB ROMs (and ICS) are really stable. No reboots or crashes. Really. There are small minor bugs, but I suppose most of the people wouldn't notice them, since not all people use all functionality. I.e. I wouldn never notice Bluetooth bug since I never use it, etc.
Now, IMHO, the best combination is JT plus KangBang kernel 1.9 stable. It works great, really smooth and fast. I have really a lot of apps and everything works just fine. With KB kernel, at least on my device, I can overclock to more than 1.2Ghz, i.e. 1.5, and it really works well. 4.1.2 is the best Android for me, fastest. I also have Nexus 7 and now that I have 4.2.1 I see how slower it is compared to 4.1.2. But Nexus is so fast that it doesn't matter. On DHD it might, because it is only single core. I tried CFX also and I had lockups and slowdowns. It is also stable, but would just stop responding for me from time to time.
But all in all I would make a backup of your current ROM (stock) and go for JB/KB combo. The only downside for me is battery life, which is worse than stock, but that doesn't happen on all sets (go figure).
D.