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.
Related
I've been running a ROM, Bugless Beast, but its started causing trouble lately. I'm thinking of reverting to CM7.2 and was wondering if anyone had good thoughts to improve performance. I'm thinking I may try out the mod EXT4All and perhaps even the script V6 Supercharger. Anyone had good results with these? Would switching to Incredikernel help also? Just figuring out what all I could do before breaking down and simply buying a new phone.... Thanks in advance! Hope someone has been successful in maximizing performance from this device.
just a suggestion but let me just give a plus 1 for updating to the new Tiny CM10.1 rom. it;s really breathed new life into my device. while not everything works perfectly, it is has been pretty stable for me. i have to do without a working video camera and a few other minor bugs but overall it;s been positive.
maybe it;s an illusion but what i find surprising is how long my battery lasts in standby.
plus since going this route, i haven;t had a 2am reboot.
I also have the ext4 mod installed to fix the low 149 mb application space issue(a must do for any Dinc owner as this stupid limit is about the equivalent of the old dos 640k memory limitation)-supposedly since the file system is ext4, its supposed to run things faster as well-i don;t know how to test that.
tekweezle said:
just a suggestion but let me just give a plus 1 for updating to the new Tiny CM10.1 rom. it;s really breathed new life into my device. while not everything works perfectly, it is has been pretty stable for me. i have to do without a working video camera and a few other minor bugs but overall it;s been positive.
maybe it;s an illusion but what i find surprising is how long my battery lasts in standby.
plus since going this route, i haven;t had a 2am reboot.
I also have the ext4 mod installed to fix the low 149 mb application space issue(a must do for any Dinc owner as this stupid limit is about the equivalent of the old dos 640k memory limitation)-supposedly since the file system is ext4, its supposed to run things faster as well-i don;t know how to test that.
Click to expand...
Click to collapse
tiny's cm 10 (not 10.1) rom with ext4 is just about perfect, if you want something slightly more stable
I've got a lovely rooted, unlocked LGOG LS-970 plugged in right next to me. But, I'm finding myself feeling a little left behind in more than one instance:
I've got the impression that swapping AOSP and stock ROMs is a finicky task with our LGOGs. It's really a chore; as far as I can tell, I have to wipe internal data coming from either camp. And I can't even switch from Vectus to any other stock ROM successfully without wiping internal data.
Is this par for the course?
Insofar as the stock playground goes, I'm only able to get up to the 1.22 Liberty Kernal; if I run any of the OC'd ones, the phone lags considerably, especially at boot, and doesn't read that it's clocking higher than 16ghz even when max is set to 17 or 18ghz. Burning hot or cool, same same.
I've doodled around a bunch trying to get the more recent Liberties to work, to no avail. I've had a bit more luck with TricksterMod than ROM Toolbox Pro, but no one else in that thread seems to be having similar issues (or has given advice I haven't tried out).
Welp! Just a general "hey? you smell that too?" inquiry.
And I think this is my first thread. Party.
ihitcows said:
I've got a lovely rooted, unlocked LGOG LS-970 plugged in right next to me. But, I'm finding myself feeling a little left behind in more than one instance:
I've got the impression that swapping AOSP and stock ROMs is a finicky task with our LGOGs. It's really a chore; as far as I can tell, I have to wipe internal data coming from either camp. And I can't even switch from Vectus to any other stock ROM successfully without wiping internal data.
Is this par for the course?
Insofar as the stock playground goes, I'm only able to get up to the 1.22 Liberty Kernal; if I run any of the OC'd ones, the phone lags considerably, especially at boot, and doesn't read that it's clocking higher than 16ghz even when max is set to 17 or 18ghz. Burning hot or cool, same same.
I've doodled around a bunch trying to get the more recent Liberties to work, to no avail. I've had a bit more luck with TricksterMod than ROM Toolbox Pro, but no one else in that thread seems to be having similar issues (or has given advice I haven't tried out).
Welp! Just a general "hey? you smell that too?" inquiry.
And I think this is my first thread. Party.
Click to expand...
Click to collapse
I'm not sure what your question is......par for the course? I wish I could say no. But, I've been rooting and ROMing phones since 2010, when I got the HD2 and could not believe the Windows 6.5 garbage that came installed. I've rooted, ROMed, and customized 7 different phones in the time and so far the only phone I had MORE trouble with was the G2x. God, that phone almost swore me off of LG for good. When the Nexus 4 came out, I decided to take another chance. But, I digress. The fact of having to wipe internal memory is not the end of the world. It does not dump your files, only your memory related to the ROM(app cache, data, etc) As far as OCing is concerned, I've found that OCing is not the end of the world either. Not too long ago, phones weren't very fast, and OCing was a viable option to get a little more speed out of the device. We have one of the fastest phones made these days, so OCing shouldn't be that big of a deal,and you won't notice distinguishable speed differences anyway(I tried with my N4; it would over clock, and seem a LITTLE faster, but that was all) As for switching between 'stock' and 'custom' ROMs, I'm afraid that is kinda par for the course. I personally believe the issue stems from most stock ROMs being 4.1.2, and most custom ROMs being 4.2.2. But, I have no real proof of that, just a suspicion. If you are rooted and unlocked, and want to try something different than stock, try one of the builds I make (JellyBeer, Beanstalk, and CM10.1/Linaro). The custom ROMs are not without their quirks, so if you need complete and total stabilty, they may not be for you. But, they are cool to use and you may like them enough to look the other way at the occasional hiccup, I do. The CM/Linaro build is a good stock-ish ROM with some added speed that has been noticed by the users of it. If you prefer a total stock feel, try Lifeless or Vectus. Both are very well made and those who use them swear by them. Be cool. PM me if you need any help with anything. Oh, and watch out for those cows!
BMP7777 said:
I'm not sure what your question is......par for the course? I wish I could say no. But, I've been rooting and ROMing phones since 2010, when I got the HD2 and could not believe the Windows 6.5 garbage that came installed. I've rooted, ROMed, and customized 7 different phones in the time and so far the only phone I had MORE trouble with was the G2x. God, that phone almost swore me off of LG for good. When the Nexus 4 came out, I decided to take another chance. But, I digress. The fact of having to wipe internal memory is not the end of the world. It does not dump your files, only your memory related to the ROM(app cache, data, etc) As far as OCing is concerned, I've found that OCing is not the end of the world either. Not too long ago, phones weren't very fast, and OCing was a viable option to get a little more speed out of the device. We have one of the fastest phones made these days, so OCing shouldn't be that big of a deal,and you won't notice distinguishable speed differences anyway(I tried with my N4; it would over clock, and seem a LITTLE faster, but that was all) As for switching between 'stock' and 'custom' ROMs, I'm afraid that is kinda par for the course. I personally believe the issue stems from most stock ROMs being 4.1.2, and most custom ROMs being 4.2.2. But, I have no real proof of that, just a suspicion. If you are rooted and unlocked, and want to try something different than stock, try one of the builds I make (JellyBeer, Beanstalk, and CM10.1/Linaro). The custom ROMs are not without their quirks, so if you need complete and total stabilty, they may not be for you. But, they are cool to use and you may like them enough to look the other way at the occasional hiccup, I do. The CM/Linaro build is a good stock-ish ROM with some added speed that has been noticed by the users of it. If you prefer a total stock feel, try Lifeless or Vectus. Both are very well made and those who use them swear by them. Be cool. PM me if you need any help with anything. Oh, and watch out for those cows!
Click to expand...
Click to collapse
Yuppo. I just did some backuping, and factory-, data-, and delvik-wiped Lifelessv14 three times to flaash the latest Vectus V3.
"FAILED"
Doh! Again?!
Fair enough. Even though it's stock-to-stock, stuff happens. I have backups.
Insofar as overclocking, it's not so much that I'd like to push the phone faster (this phone, we know, is fast), but that I just couldn't figure out why, after a fair amount of trials, I wasn't able to, when, seemingly, many others could.
Basically, I want to ask, when you say wiping internal data doesn't dump your files, which files do you mean? My /sdcard gets dumped.
... Incomiiing! *mooooo*
EDIT: But, then again, I just sideloaded it and it said "FAILED," and booted. Who'da thunk?
Hi folks, I purchase a LG Nexux 5X and will arrive soon and was wondering where should I start modding it.
I have done several mods in other phones and on the gear 2 neo, so I know how to use odin and some adb functions.
I usually don't tamper with a new phone unless it is really slow or annoying me with some bug, but would like to know if there are some minor tweaks I can begin to tinker with that will enhance my overall experience with this phone.
Thanks in advance
Best Regards.
-Ich
Icharius said:
Hi folks, I purchase a LG Nexux 5X and will arrive soon and was wondering where should I start modding it.
I have done several mods in other phones and on the gear 2 neo, so I know how to use odin and some adb functions.
I usually don't tamper with a new phone unless it is really slow or annoying me with some bug, but would like to know if there are some minor tweaks I can begin to tinker with that will enhance my overall experience with this phone.
Thanks in advance
Best Regards.
-Ich
Click to expand...
Click to collapse
Getting my Nexus 5X tomorrow but currently use a Nexus 5. With any Nexus you want to start off with setting up the Android SDK and all the Nexus drivers on your computer so if something does go south, you are ready to fix it with the factory images. The first thing I am going to do with mine is put Android N on it since I haven't had the chance to try it yet. Then root and most likely be happy with that for a while. Since Android N will probably be officially released soon, I'm sure that's when a lot of stuff will start happening around here. Hopefully Xposed will get updated to work with it. If so, that will be my setup. Stock, rooted and Xposed. That's basically what I have been running on my Nexus 5 for a while now. But if you want to try out custom ROMs, there are those too.
jsgraphicart said:
Getting my Nexus 5X tomorrow but currently use a Nexus 5. With any Nexus you want to start off with setting up the Android SDK and all the Nexus drivers on your computer so if something does go south, you are ready to fix it with the factory images. The first thing I am going to do with mine is put Android N on it since I haven't had the chance to try it yet. Then root and most likely be happy with that for a while. Since Android N will probably be officially released soon, I'm sure that's when a lot of stuff will start happening around here. Hopefully Xposed will get updated to work with it. If so, that will be my setup. Stock, rooted and Xposed. That's basically what I have been running on my Nexus 5 for a while now. But if you want to try out custom ROMs, there are those too.
Click to expand...
Click to collapse
Thanks for your reply. good advice to save the original rom image! I will probably root too, because I usually OC my phones hopefully that won't be so much a hassle.
If I were you, I wouldn't OC at all. Snapdragon 800 series likes to overheat and throttle itself, making it slower than usual.
Icharius said:
Hi folks, I purchase a LG Nexux 5X and will arrive soon and was wondering where should I start modding it.
I have done several mods in other phones and on the gear 2 neo, so I know how to use odin and some adb functions.
I usually don't tamper with a new phone unless it is really slow or annoying me with some bug, but would like to know if there are some minor tweaks I can begin to tinker with that will enhance my overall experience with this phone.
Thanks in advance
Best Regards.
-Ich
Click to expand...
Click to collapse
I have the N5X for several months.
I previously had the N4, N5, and OnePlus One (still have it, wife uses it).
I used stock, I used to flash ROMs at least twice a week minimum (same on the other devices). Various ROMs, to test their performance, their tweaks, their perks, their battery life... you name it.
However, flashing ROMs and trying out various mods feels very much like living on the road with your backpack on, rather than staying at home and having a steady job. Because while flashing ROMs, you don't always re-install all the things you had (Even if you backup with Titanium Backup, as some things don't survive data restore very well). Last week I made the decision to go stock and stay stock (well, not really, I went stock Android N Preview 5, which will receive OTA to full Nugget in about a month).
I have to tell you... I don't quite feel any difference other than losing a feature or two. Speed is still great; snappiness is snappy, no bugs and no issues. It feels great even though its encypted (by default), while all this time I was certain being un-unecrypted made the device any snappier; that was just a placebo I guess.
So yeah, you can go ahead and flash a custom ROM (or many of them!), but don't do it for improved performance. Stock performance is truly awesome, and while some ROMs make it better, for sure - it's not THAT better, not in any noticeable way. Do it for features, do it for fun, do it for curiosity, DO IT! But just know the simple truth that Stock Android 6 and definitely 7 are so good and bug-less, that there is no need to get customized to resolve any bugs or performance issues; there are none.
thenessus said:
I have the N5X for several months.
I previously had the N4, N5, and OnePlus One (still have it, wife uses it).
I used stock, I used to flash ROMs at least twice a week minimum (same on the other devices). Various ROMs, to test their performance, their tweaks, their perks, their battery life... you name it.
However, flashing ROMs and trying out various mods feels very much like living on the road with your backpack on, rather than staying at home and having a steady job. Because while flashing ROMs, you don't always re-install all the things you had (Even if you backup with Titanium Backup, as some things don't survive data restore very well). Last week I made the decision to go stock and stay stock (well, not really, I went stock Android N Preview 5, which will receive OTA to full Nugget in about a month).
I have to tell you... I don't quite feel any difference other than losing a feature or two. Speed is still great; snappiness is snappy, no bugs and no issues. It feels great even though its encypted (by default), while all this time I was certain being un-unecrypted made the device any snappier; that was just a placebo I guess.
So yeah, you can go ahead and flash a custom ROM (or many of them!), but don't do it for improved performance. Stock performance is truly awesome, and while some ROMs make it better, for sure - it's not THAT better, not in any noticeable way. Do it for features, do it for fun, do it for curiosity, DO IT! But just know the simple truth that Stock Android 6 and definitely 7 are so good and bug-less, that there is no need to get customized to resolve any bugs or performance issues; there are none.
Click to expand...
Click to collapse
Agree. I used to root and ROM the crap out of phones but with the 5X I've stayed stock. Yeah, I see more ads now and miss Viper4Android but I spend no time F-ing with the phone and all the time just using it. No gyrations to go though to install monthly security updates or trying to get banking apps to work with root (like Android pay). Try it stock for a while.
przemcio510 said:
If I were you, I wouldn't OC at all. Snapdragon 800 series likes to overheat and throttle itself, making it slower than usual.
Click to expand...
Click to collapse
I was reading that thermal problem post, it does present an issue to me because when I ride a bike I usually have the phone on the handle in a rubber case exposed to the sun and the heat that can easily reach over 35°. Thanks for the heads up.
thenessus said:
But just know the simple truth that Stock Android 6 and definitely 7 are so good and bug-less, that there is no need to get customized to resolve any bugs or performance issues; there are none.
Click to expand...
Click to collapse
I hear you, I have prolonged the life of my smartphones more than it should, by tweaking and using customs roms. I have had only 2 other SP in the spam of 6 years and had never had to be subject to a phone/data plan. I just ride the wifis signal or pay per use the 3g signal. Even-thought this LG is not a big inversion in itself, I hope I can squeeze several years of it and the old practice of using custom roms, seems kind of pointless or not worth the trouble considering as you say the stock is as good.
adobeman said:
Agree. . Try it stock for a while.
Click to expand...
Click to collapse
Oh I will! there's so much I can do with it as it is, it seems.
Hi all,
For about 8 years I've enjoyed having Android devices and modding them. I've been on ATT during most of that time and have gone with whatever flagship Samsung had at the time. My current device is a very dated GS5 and honestly from the locked bootloader to what I feel is disappointing hardware I decided a while ago that I would be trying a different manufacturer next. Right now ATT's android offerings are lacking to be generous. So I decided to buy the first off contract phone in a while an unlocked Moto Z Play.
I decided a long time ago that the best thing to do was purchase a flagship model no matter what but the lack of a headphone jack in the force and the battery capacity of the Play made me go this route. I don't do mobile games I just want a seamless experience from apps to browsing content heavy Internt pages.
If I do a total strip, unlock, root and flash of my Moto Z Play using a stable kernel and good ROM build will it make me feel good about my purchase?
Thanks in advance
Considering how the phone at stock is and what you want from it: "I just want a seamless experience from apps to browsing content heavy Internt pages", how is it not performing that?
Your post is very confusing. Other than it not being a "Flagship" phone, you offer no actual issues you are having with the z Play. Here's what I like about The Z Play. Like you, I only ever had Flagship Sammys. My last 2 Were Note 7. After I returned it I decided to get this phone to hold me over until the Note 8. This battery is insane. Yesterday I had almost 7 hours of SOT and the battery was at 50%, the screen brightness at 50% as well . Other than heavy gaming, there's no noticeable difference in the chip performance from the 820 in the Flagship phones. The stock system /UI takes a little bit to get used to if you had one of the more recent Samsung phones, which you haven't. The battery mod I got with this phone is great for a little extra juice on the rare occasions I need it. Overall, this is a solid phone with a great price tag.
Unless you have a particular need for a root-required feature (ad blocking options, certain apps) or you aren't willing to wait a little bit for Nougat, you probably will lose more than you gain by rooting and romming. Unlock kills your warranty, and depending on where you go ROM wise, you'll lose Android pay and anything else that requires safety net, unless you go one of the few routes that seem to support magisk.
Performance wise there doesn't appear to be much gain at this point, and if you go to a non stock based custom ROM, you may have camera issues, and you definitely lose Moto mod support.
The stock ROM on this phone is pretty clean, just includes the Moto stuff that is pretty functional for minimal overhead for most people, and you can always turn it off if you don't like it. Throwing in an SD card more than makes up for the small amount of extra storage you gain from a mild debloat.
Based on your post, I didn't see anything that indicates you would benefit from root and ROM. Keep it stock. It's awesome.
The MZP is a great performer and everything is smooth, except demanding 3d games (regular 3d games are just fine). Don't recommend messing with the firmware
Also, wait till you see how long it goes on a charge
It's the most powerful 32-bit phone ever.
Judging by the tone of some people I guess I stepped on some toes. I'm sorry if my post triggered you.
I don't even have the phone yet so yeah, maybe it'll be everything and more I could ever dream of in a device right out of the box. Who knows.
Thanks to the folks who provided some helpful info I very much appreciate it.
adam_l_c said:
Judging by the tone of some people I guess I stepped on some toes. I'm sorry if my post triggered you.
I don't even have the phone yet so yeah, maybe it'll be everything and more I could ever dream of in a device right out of the box. Who knows.
Thanks to the folks who provided some helpful info I very much appreciate it.
Click to expand...
Click to collapse
You will not be disappointed. This is the first phone I have where I don't really see the need to change anything. Buttery smooth, great battery out of the box and it has nougat already.
Maybe root to install adaway but i now use dns66 thanks to whoever recommend it to me a few days back and that too is gone.
I'm used to owning Nexus phones.
The Moto Z play combines raw Android along with Moto actions which are pretty great. It's a premium feel, build and design. I average between 10-14 hours SOT....The battery life is untouchable
vietkao said:
Maybe root to install adaway but i now use dns66 thanks to whoever recommend it to me a few days back and that too is gone.
Click to expand...
Click to collapse
It was me. Glad to hear it is working fine for you.
There are still two points which make rooting advantageous if you are not interested in modifying the system. First is, backup is difficult if you have no access to your own data stored by the apps. There is a way (adb), but it is not that convenient compared with Titanium backup. Second is, if you copy or move files, the timestamp can't be kept without root. You can't sort files by age once you move them, and syncing and revision control gets more difficult.
@adam-l-c I'd also say stripping should be done carefully if it is really seen as necessary. There often are services waiting for another service. If you only disable or remove one service and don't recognize the dependant, it may cause system load. You seem to have an idea what you're doing, so I wish you good luck and would be glad to hear what you find is really worth disabling. The device is working smooth as it is, at least for me (still using Marshmallow).
Believe it or not I gave my unlocked pixel XL to my wife and took her Moto z play. I needed proper ms exchange services that AOSP doesn't have. Nougat would be nice. The pixel camera is slightly better. The z is pretty heavy but built like a tank. Typical Moto. I don't notice the lower res screen or slower processor. I live in a world of good enough apparently.
tag68 said:
It was me. Glad to hear it is working fine for you.
There are still two points which make rooting advantageous if you are not interested in modifying the system. First is, backup is difficult if you have no access to your own data stored by the apps. There is a way (adb), but it is not that convenient compared with Titanium backup. Second is, if you copy or move files, the timestamp can't be kept without root. You can't sort files by age once you move them, and syncing and revision control gets more difficult.
@adam-l-c I'd also say stripping should be done carefully if it is really seen as necessary. There often are services waiting for another service. If you only disable or remove one service and don't recognize the dependant, it may cause system load. You seem to have an idea what you're doing, so I wish you good luck and would be glad to hear what you find is really worth disabling. The device is working smooth as it is, at least for me (still using Marshmallow).
Click to expand...
Click to collapse
ADB backup does not work on the lastest Moto phones, AFAICT. Ditto Helium which is just a front end for same. ADB disable apps quit working with one of our patches, December I think, VZW anyway.
TY for DNS66 mention.
To Op,
Moto pulled a whopper on this phone. While the screen brightness is better for daylight viewing on the sisters and they have VR and better gaming. Yet I would not trade to those.
adam_l_c said:
Judging by the tone of some people I guess I stepped on some toes.
Click to expand...
Click to collapse
You're not stepping on anyone's toes. Sounds like you're a bit sensitive.. People are just saying how good the phone is and I agree with them.
It's fast, battery life is damn good, and Moto actions are pretty awesome.
Nice performance
Awesome battery life
Gaming is also fine
I was surprised to notice that there is no official version of Lineage OS for the Pixel. Then looking around it just seems like there aren't that many ROMs for the Pixel. And I'm surprised to see that a year after release there still seem to be difficulties with root and using TWRP.
Am I right in perceiving that the Pixel has gotten less development interest than Nexus devices of the past? If so, why?
I ordered a Pixel 2 (to replace my Nexus 4--which has offical lineage support) and was assuming that it would get all the usual developer love that I've exeperienced in the past. Now I'm a bit worried that it will be difficult just to root it and do nandroid backups.
Thanks for any thoughts and observations.
I think they are having issues with the increased security and dual OS partitions. Will take some time.
scottjal said:
I think they are having issues with the increased security and dual OS partitions. Will take some time.
Click to expand...
Click to collapse
Yeah, I saw that the dual partitions are an issue and the dm-verity check (don't quite understand what that is). But still, the Pixel has been out for a year. Nexus phones usually had tons of development by that point. I imagine if the devs were really into this phone there would be more interest. Especially the lack of official Lineage OS support, the most fundamental of all ROMs. There are unofficial versions of Lineage OS for the Pixel, so it works. I guess that's why I was starting to get the impression that the Pixel is not that popular with the devs (compared to past Nexus devices).
Price doesn't help either, I'm less likely to mess with a phone that costs a grand. Also prices it out of the hands of those that just want to tinker.
I also wonder how much baseline performance plays a role. The Pixel is really quite great out of the box, it's the first phone I've owned in recent times that I haven't had the desire to root, mod, rom, etc. custom roms are generally known to improve the end user experience, can't say that has been my experience on the Pixel and that's a big reason why I've decided stock is best for me.
mlin said:
I also wonder how much baseline performance plays a role. The Pixel is really quite great out of the box, it's the first phone I've owned in recent times that I haven't had the desire to root, mod, rom, etc. custom roms are generally known to improve the end user experience, can't say that has been my experience on the Pixel and that's a big reason why I've decided stock is best for me.
Click to expand...
Click to collapse
For me ROMs have never been about performance, they are about features. They often have more privacy features and remove some of the pernicious behind the scenes stuff. There are more options for quick settings tiles. You can control the notification LED better. I don't want a total makeover; I'm happy with basically stock Android. But there are a lot of little things that are improvements to me. I guess this is why I especially like Lineage OS, since it is not a heavily modified OS. Also you sometimes get updates for security problems sooner (the once a month standard from Google is pretty lame--in Linux security patches are pushed out the day they are ready). As for rooting, it lets you use the iptables firewall in the Linux kernel and programs like adaway, as well as a root file manager (there are many times I find it useful to browse the system files); there is Titanium backup that is so much more powerful than any other backup tool that requires root; and a rooted device can also often get around issues with tethering. And having a custom recovery like TWRP allows nandroid backups, which have saved me from disaster so many times. So I think even on a phone like the Pixel, there's a lot to be gained from ROMs, rooting, minor mods, a custom recovery.
Anyway, I guess maybe it is just about the cost of the Pixel. Or perhaps the complexity of the dual partitions--are the Pixel phones the only ones that do this? I wonder what new phones get the most developer attention these days, if it's not the Pixels.
No, there's significantly less development, regardless of what a few users say (when I mentioned it a week ago after coming from a 6P, people were shocked when I said there's no development lol). I had to point out that 5 ROMs does not even compare to the 30 ROMs of the 6P.
At first, the pixel seemed like a downgrade to me. But after using it a week or so, it is a little smoother I got, and has better battery life, which is awesome. But those are about the only pros. Camera on mine is the same quality as the 6P, and I can't get used to the crappy downfiring speakers (last 2 devices had dual front facing).
All in all, it's an ok phone. It's about 2" taller than it should be, due to Google love affair with gigantic bezels. Haha. But sometimes using a bezeless phone one handed if tough, because your thumb can't reach the navbar.
Sent from my Pixel XL using Tapatalk
cb474 said:
For me ROMs have never been about performance, they are about features. They often have more privacy features and remove some of the pernicious behind the scenes stuff. There are more options for quick settings tiles. You can control the notification LED better. I don't want a total makeover; I'm happy with basically stock Android. But there are a lot of little things that are improvements to me. I guess this is why I especially like Lineage OS, since it is not a heavily modified OS. Also you sometimes get updates for security problems sooner (the once a month standard from Google is pretty lame--in Linux security patches are pushed out the day they are ready). As for rooting, it lets you use the iptables firewall in the Linux kernel and programs like adaway, as well as a root file manager (there are many times I find it useful to browse the system files); there is Titanium backup that is so much more powerful than any other backup tool that requires root; and a rooted device can also often get around issues with tethering. And having a custom recovery like TWRP allows nandroid backups, which have saved me from disaster so many times. So I think even on a phone like the Pixel, there's a lot to be gained from ROMs, rooting, minor mods, a custom recovery.
Anyway, I guess maybe it is just about the cost of the Pixel. Or perhaps the complexity of the dual partitions--are the Pixel phones the only ones that do this? I wonder what new phones get the most developer attention these days, if it's not the Pixels.
Click to expand...
Click to collapse
While custom ROMs may not be about performance to you, I know that it is to others. I think there are a lot of variables at play, and I don't discount the out of the box experience as one of them. Take that custom ROMs are prone to decreased stability, especially with the Pixel and the argument for advantages of custom ROMs gets diminished fairly quickly. Unless of course you must have all the frivolous tweaks at the cost of stability and performance.
mlin said:
I also wonder how much baseline performance plays a role. The Pixel is really quite great out of the box, it's the first phone I've owned in recent times that I haven't had the desire to root, mod, rom, etc. custom roms are generally known to improve the end user experience, can't say that has been my experience on the Pixel and that's a big reason why I've decided stock is best for me.
Click to expand...
Click to collapse
I agree, this phone is pretty hard to improve on. I'm missing all the flashing and tweaking but I'm coming to the conclusion that stock is the ticket. The stock firmware doesn't feel like a compromise anymore, it feels like it works best. With payment via phone and bank accounts on board, security is also an issue I've not worried about before but I guess I need to deal with.
mlin said:
While custom ROMs may not be about performance to you, I know that it is to others. I think there are a lot of variables at play, and I don't discount the out of the box experience as one of them. Take that custom ROMs are prone to decreased stability, especially with the Pixel and the argument for advantages of custom ROMs gets diminished fairly quickly. Unless of course you must have all the frivolous tweaks at the cost of stability and performance.
Click to expand...
Click to collapse
I didn't say no one cares about performance. In fact, I only said that there are a lot of things ROMs do other than performance, so even if that issue is less with a phone like the Pixel, it hardly negates the many and varied reasons that people like ROMs. So I was just suggesting that reducing it all to performance as the fundamental issue, I think, oversimplifies how varied and complicated the custom ROM community of users and devs is.
Anyway, my main question in the OP wasn't really why do people like or dislike custom ROMs, nor was it do they think they are unnecessary for the Pixel. My main question was, do people think my perception is correct that devs are less interested in the Pixel than in past Nexus phones?
Personally, I believe not all developers are created equal. The pixel design and new os introduced complexities beyond the abilities of the cut and paste developer. The truly talented developers are either still hard at work or have concluded, no not worth it.
Who knows?
There are many roms out there. There are just not on xda anymore.
Development is just so much harder on the pixel, so we need to wait till the first running custom rom is out there so the other devs can pick from there. It's already been working hard on it.
Development is not so high cause a dev need the device and not every dev has the money to buy a 1000 $ device every year.
Hopefully some developers fell into some pixels when Google started giving them out as replacements for 6Ps. We'll have to wait and see.
I still suck at G+. I can't get the hang of how to search it for roms, or even how to actually get the rom, when I know a developer has one on their page. I wish Google could have tried out the service before they released it, maybe they would have noticed how difficult it can be - or maybe it's just the developers and how they organize their page...who knows.
Sent from my SM-T330 using Tapatalk