Related
Was all the fuss about the cap worth it? Aside the screen tearing, is there really a noticeable difference? Do games run better? Is scrolling really smoother?
fix what fix ?
Where is this fix? and how do we tell what screen we have?
30 FPS fix is what this guy is talking about.
vinscuzzy said:
Was all the fuss about the cap worth it? Aside the screen tearing, is there really a noticeable difference? Do games run better? Is scrolling really smoother?
Click to expand...
Click to collapse
Yes the difference is quite noticeable, whole phone runs alot smoother and faster, better touch response, etc. That being said the screen tearing is pretty bad and it obviously comes with the other problems of breaking the camera and all that.
Anyway to those who might have been able to test it, Would say it has noticeable difference even if it didn't. What I mean is the folks who probably were not aware of it before are the ones who would most likely just jump and say it's better. Compared to those who noticed right off the back, if that makes sense.
These two threads: http://forum.xda-developers.com/showthread.php?p=6915937#post6915937
http://forum.xda-developers.com/showthread.php?t=704889&page=48
I have hardware revision 003 but I haven't tried the fix yet. My lag was never really that significant in the first place and I'm planning on replacing this when Sprint gets their updated batches with the light leak and screen fixes so I don't want to root yet. I'd rather hold off until there's a stable ROM with all the features working. (Camera is a necessity, unfortunately)
This is my first Android phone, and coming from a Touch Pro 2, I found the responsiveness slightly better on the the Evo than on the TP2.
I have a friend who has the Sprint HTC Hero, and I noticed his screen shifts and overall responsiveness to be waaaaay better.
I can say now having applied the fix, the UI is as snappy on the EVO as it is on the Hero. As far as games go, it's a lot smoother.
So I'll say this, from the perspective of a first time user, minus the bad press and forum posts, the Evo is a great phone. With the fix, it's even better!
Edit: Let me add that while I was not pleased in having a phone where the features were halved, this was still the phone for me. Having a technical background AND knowing HTC's history, as well as the history of the devs (ie GPS functionality in the Moguls), I knew it was a matter of time for the fix to be found. But I can definitely view this from the perspective of the non-technical person who don't want to fool with rooting anything. They want something that works out of the box. I may not agree with the "whining" of some, I could relate.
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.
As the title states.
Personally I love this phone, it's kind of like a really cool car, like an alpha romeo which has it's faults but just for the simple fact of the way it's made and the way it feels, I wouldn't change it.
EDIT: Maybe the battery life
Feel free to have a moan
I love the case I have and the way it perfectly matches the phone. It's a body glove and the phone is the darker one.
Video won't resume when going from the recent apps. It opens then disappears.
I love the speakers on front. When HTC did that year's ago I was amazed. Then I thought everyone should. I think it's crazy stupid not to. Sounds good too.
Screen is OK. I'd like bigger though and way better viewing angle. Gets dark when it's laying flat on my bed and I'm reading the web. I don't want to always hold it.
Keyboard is terrible in my opinion. Samsung works way better for me. I want keys a bit bigger and darker with numbers on top and much better auto correction. Swiftkey didn't work well enough for me.
Performance seems iffy. I mean I don't know if this is how things should be. I had the Verizon GS5 for 6 months like the 5th of this month so I'm used to that phone. Games sometimes jerk and seem to load no faster then on my GS5. They seem to crash much more. Games like the clash games, star Wars commander etc. Those types are all I play.
I want to disable apps I won't use so they're not always running. But this can cause issues maybe.
Battery needs a ton of help. Wish all phones had the power and 5000 mah battery would give.
I prefer Sense a little to tw and others based on color and lines separating options more in setting menus etc. Seems a bit more clean.
Have couple more days to return my phone and I'm not sure if I want to keep this and exchange for another or get a g3 or gs6. G4 not out for awhile still.
@buggs1a I hear you with the battery it isn't great but then I haven't tried to optimise it very much, once I cut out all the dead wood and find the wake locks it should be a lot better. 2 days is a possibility depending on usage. Haven't noticed the playback from video as I use MX player. Give it a whirl and use auto starts to kill off apps
buggs1a said:
I love the case I have and the way it perfectly matches the phone. It's a body glove and the phone is the darker one.
Video won't resume when going from the recent apps. It opens then disappears.
I love the speakers on front. When HTC did that year's ago I was amazed. Then I thought everyone should. I think it's crazy stupid not to. Sounds good too.
Screen is OK. I'd like bigger though and way better viewing angle. Gets dark when it's laying flat on my bed and I'm reading the web. I don't want to always hold it.
Keyboard is terrible in my opinion. Samsung works way better for me. I want keys a bit bigger and darker with numbers on top and much better auto correction. Swiftkey didn't work well enough for me.
Performance seems iffy. I mean I don't know if this is how things should be. I had the Verizon GS5 for 6 months like the 5th of this month so I'm used to that phone. Games sometimes jerk and seem to load no faster then on my GS5. They seem to crash much more. Games like the clash games, star Wars commander etc. Those types are all I play.
I want to disable apps I won't use so they're not always running. But this can cause issues maybe.
Battery needs a ton of help. Wish all phones had the power and 5000 mah battery would give.
I prefer Sense a little to tw and others based on color and lines separating options more in setting menus etc. Seems a bit more clean.
Have couple more days to return my phone and I'm not sure if I want to keep this and exchange for another or get a g3 or gs6. G4 not out for awhile still.
Click to expand...
Click to collapse
I would return it if I were you. Because much of what you mention, are not real issues, but are areas that just don't meet your desires. The screen is not going to grow, the battery is not going to grow, and the keyboard is what it is. I'm surprised you couldn't find a skin for Swiftkey that satisfied your needs. Also, it sounds like you may have an issue with your phone, as mine is buttery smooth, no crashes.
Sent from my HTC One M9 using Tapatalk
fernandezhjr said:
I would return it if I were you. Because much of what you mention, are not real issues, but are areas that just don't meet your desires. The screen is not going to grow, the battery is not going to grow, and the keyboard is what it is. I'm surprised you couldn't find a skin for Swiftkey that satisfied your needs. Also, it sounds like you may have an issue with your phone, as mine is buttery smooth, no crashes.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Although the battery will get better with updates
I'm averaging close to 5.5 hours of SOT on a full charge, but I'm with AT&T and am typically always in an area with a reputable signal. Apart from actual usage, and assuming there are no wakelocks going on, a phones signal is the biggest battery drainer. No signal or a weak signal will keep the phone signal searching and cause more drain on the battery. For this reason, I agree, battery life can be improved thru updates, especially if the radio firmware sees an update.
Sent from my HTC One M9 using Tapatalk
buggs1a said:
Keyboard is terrible in my opinion. Samsung works way better for me. I want keys a bit bigger and darker with numbers on top and much better auto correction. Swiftkey didn't work well enough for me.
Click to expand...
Click to collapse
I've been using the Minuum keyboard and have grown to really like it. At times it will frustrate me with it's auto-correction, but what keyboard doesn't? They have a free version to try, so maybe give it a spin.
I'm in agreement that the battery goes quick when power saver is not active. I have a feeling that it will improve with newer versions of Lollipop, Sense and perhaps even changed HTC bits that optimize the phone's performance on the 810 chipset.
Let us know which way you go...
I really like the phone! I had the S6 Edge just prior to this and went to Verizon to turn it in as I suddenly caught the auto rotate bug. The rep said this hasnt been fixed and that if it happens again I would have to go through Sammy to get a new one. Not wanting to do that I looked at the M9 and have been really happy since. It is comparable in almost every way to the S6. I do miss the edge on the edge LOL but that is sort of gimmicky.
I bought the M9 when it first came out and was very dissapointed... the first one was returned for overheating which didnt start well, I was annoyed at myself for impulse buying,. but after picking it up again a few days ago Im actually stating to enjoy it...
The camera has been improved alot (but not amazing) through the 1st firmware update and an updated camera app from the Play Store (Raw Format added) which makes me feel better about it.. although Cam still needs work. Boomsound Music Mode is great, as good as the M8.. and not the reported tinney-ness some reviews are reporting. It just has all the things I loved about the M8. For me though that "Sense Home" widget and start screen.. I dont know how this is a good idea, I find it drains the battery like nothing else, using location and tracking...
So far, battery life seems ok, I get about 2 days on Light to Modersate use - Music, Camera, BlinkFeed, I do actually like BF.. but so far.. Im happy with my M9, really like the added "Themes" engine... a nice touch.
It wouldve been nice to see HTC bump up the screen to 5.2 or even 5.5" @ 1080p (I think QHD screens on a device less than 7" is a bit unnecessary) . Just something to seperate it from the M8 other than a camera and Themes
I just hope HTC can get through this and pull out the stops for the M10.. now that Samsung are leaping their way back from the S5 fall with the S6 and LG with the amazing G4, It aint looking good for HTC. For me, they just didnt try hard enough, they just gave into internet pressure, relaced the camera and hoped for the best.. which wasnt a wise thing to do 3 years in a row from the M7.
M9 for me is looking great, just needs some fine tuning, which will hopefully come in 5.1
I exchanged my m9 for the g3 Friday yesterday. And I don't get it how videos show it has themes, but it don't.
No complaints at all coming from Xperia Z3 to M9. Happy I made the switch.
In fact it is the same feeling
It is too powerful to be contained, which is a really good thing
From the way Htc treats its flagships via software updates, i can see that this powerful machine will be even more optimised and speedy, and will get improvement in every area!
If you are not aware, the Taiwan M9 recieved an update to its base from 1.32 to 1.40 with some massive camera improvements! And it is said that people are getting past the 6 hours screen on time with the latest update, as well as reporting that the phone is a Lot cooler than the 1.32 base
So that is very great news indeed, which makes me feel very optimistic!
You see? Improved battery life, improved thermal management, improved camera performance! This is awesome
And still android 5.1.1 will boost the mobile's general perfromance with a lot of misc bug fixes and enhancements by google. The future is bright for this phone, i see
Mostafa Wael said:
In fact it is the same feeling
It is too powerful to be contained, which is a really good thing
From the way Htc treats its flagships via software updates, i can see that this powerful machine will be even more optimised and speedy, and will get improvement in every area!
If you are not aware, the Taiwan M9 recieved an update to its base from 1.32 to 1.40 with some massive camera improvements! And it is said that people are getting past the 6 hours screen on time with the latest update, as well as reporting that the phone is a Lot cooler than the 1.32 base
So that is very great news indeed, which makes me feel very optimistic!
You see? Improved battery life, improved thermal management, improved camera performance! This is awesome
And still android 5.1.1 will boost the mobile's general perfromance with a lot of misc bug fixes and enhancements by google. The future is bright for this phone, i see
Click to expand...
Click to collapse
Im still on 1.32 mate, I'm running Leedroid and I'd rather he got all the issues sorted prior to a release, I've heard good and bad about 1.40, some lag with proximity and opening screen. Camera is improved by all accounts. Will see what happens.
Cheers.
dladz said:
Im still on 1.32 mate, I'm running Leedroid and I'd rather he got all the issues sorted prior to a release, I've heard good and bad about 1.40, some lag with proximity and opening screen. Camera is improved by all accounts. Will see what happens.
Cheers.
Click to expand...
Click to collapse
I guess that's why the 1.40 isn't rolled out to the .401 region
Mostafa Wael said:
I guess that's why the 1.40 isn't rolled out to the .401 region
Click to expand...
Click to collapse
Not entirely sure as to why it hasn't been rolled out, I can see Lee, leapfrogging this version and going for the next one, the issues at this point appear to outweigh the benefits, besides the camera ofc
dladz said:
Not entirely sure as to why it hasn't been rolled out, I can see Lee, leapfrogging this version and going for the next one, the issues at this point appear to outweigh the benefits, besides the camera ofc
Click to expand...
Click to collapse
That is pure speculation on your part, unless you have some concrete evidence you can link us to.
fernandezhjr said:
That is pure speculation on your part, unless you have some concrete evidence you can link us to.
Click to expand...
Click to collapse
Just things I've heard around the threads to be honest. Not speculating at all..
Beyond the apparently improved camera which in all fairness isn't that much of an improvement, the white balance isn't fixed and its still far too sharp, I've heard about random reboots etc, some of this is in Lees thread too
Do a bit of reading and you'll see for yourself, I don't just make things up and I'm not about to continue a heated debate especially when someone is presumptuous towards me.
dladz said:
Just things I've heard around the threads to be honest. Not speculating at all..
Beyond the apparently improved camera which in all fairness isn't that much of an improvement, the white balance isn't fixed and its still far too sharp, I've heard about random reboots etc, some of this is in Lees thread too
Do a bit of reading and you'll see for yourself, I don't just make things up and I'm not about to continue a heated debate especially when someone is presumptuous towards me.
Click to expand...
Click to collapse
I do plenty of reading and what I have seen is improved camera, improved battery life, and a slight improvement performance wise. I'm not looking for a heated debate. I just haven't seen much posted in the way of negatives, yet you say the negatives outweigh the positives, which is why I ask for some links. Now, I'm talking stock. If a developer takes the base and his custom rom causes reboots, that's on him.
fernandezhjr said:
I do plenty of reading and what I have seen is improved camera, improved battery life, and a slight improvement performance wise. I'm not looking for a heated debate. I just haven't seen much posted in the way of negatives, yet you say the negatives outweigh the positives, which is why I ask for some links. Now, I'm talking stock. If a developer takes the base and his custom rom causes reboots, that's on him.
Click to expand...
Click to collapse
Do you have a point to make about your phone? Is there something you'd like to share about the m9? Did you read the title of the thread?
You've jumped on other people and have challenged each of them towards their point. But you yourself have said nothing and contributed nothing towards the thread, that's actually trolling, this Is not a thread for that, this is for people to have their say.. How can they do that or want to with you waiting there for everyone? Move on or contribute
dladz said:
Do you have a point to make about your phone? Is there something you'd like to share about the m9? Did you read the title of the thread?
You've jumped on other people and have challenged each of them towards their point. But you yourself have said nothing and contributed nothing towards the thread, that's actually trolling, this Is not a thread for that, this is for people to have their say.. How can they do that or want to with you waiting there for everyone? Move on or contribute
Click to expand...
Click to collapse
I think this phone is beast mode, granted I'm coming from the EVOLTE, but I picked HTC for sound and it's GPU power which is better than its competition. Only thing that upsets me is consumer reviews and the fact that this device got bashed because of the m9+ released in the foreign market and users thinking it was so much better because of a slightly bigger screen and finger print scanner. I just hope this "hero" device they are talking about releasing doesn't deter development on the m9. Just my opinion
Coming from an iPhone 4S, I am very glad with the Sony Xperia Z1C that I bought a few months ago to replace it. The Z1C is still running on KitKat and it works perfectly fine. It is not rooted btw.
Now I am considering to update to Lollipop, but I wonder if that would be wise. On various forums, e.g. the Sony support forum, I read some "horror stories" (o.k. a bit exaggerated maybe) about decreased battery life, overheating etc. after a Lollipop update.
I already asked for an opinion on the Sony forum, but got an, imo, rather meaningless reply saying that earlier updates also had many complaints and the started thread was locked almost immediately by a moderator after that reply.
Now I hope that I can get some advice here. Is there a more or less general consensus here about updating or not ?
Thanks in advance.
I have absolutely no complains about this update. Still have great battery life, but no overheating or whatsoever. The phone is as pleasant to use use as before the update if not more
Opinions differ. Some specialists from this forum reverted from LP to KK for different reasons.
My personal opinion is that with every step ahead software becomes more complicated, investigates you and your activities in bigger grade and is more troublesome during rooting and personal modifications.
Since long ago my principal rule is: "Don't touch things which work correctly".
I am still on KK .108 however I tuned it in 100+ places to suit my needs.
I had crapy sound problem and don't recommend lollipop yet.
F308 said:
"Don't touch things which work correctly".
Click to expand...
Click to collapse
Exactly.
For me, update to lollipop is a completely waste of time unfortunately again on 5.1.1. Poor multitasking, camera quality worst than kitkat (whitish tone on captured pictures and viewfinder lag in medium or low light conditions), battery draining... I prefer stability, performance and battery of kitkat than smoothness or visual changes from lollipop
performance on LP is better than KK. see aututu, it got 2000-3000 points more.
remember its a phone, and its better than 90% of the phones out there. it will never be S6 edge or whatever.
i like the smoothness in 5.1.1. if it was KK it would stand still for a sec or two, makes it feel slow, like this that is covered in animations.
about multitasking, got no issues, FB and the chat are great, instagram is fast, skype and viber work nice. 2 years almost and still kicking.
5.0.2 was laggy, and poor battery life.
5.1 is quick, good battery life, good multitasking.
The only thing worse about LP is the camera refresh rate. It look lower than 20fps (with KK it looks to be 60fps).
Rijnton said:
Coming from an iPhone 4S, I am very glad with the Sony Xperia Z1C that I bought a few months ago to replace it. The Z1C is still running on KitKat and it works perfectly fine. It is not rooted btw.
Now I am considering to update to Lollipop, but I wonder if that would be wise. On various forums, e.g. the Sony support forum, I read some "horror stories" (o.k. a bit exaggerated maybe) about decreased battery life, overheating etc. after a Lollipop update.
I already asked for an opinion on the Sony forum, but got an, imo, rather meaningless reply saying that earlier updates also had many complaints and the started thread was locked almost immediately by a moderator after that reply.
Now I hope that I can get some advice here. Is there a more or less general consensus here about updating or not ?
Thanks in advance.
Click to expand...
Click to collapse
From a technical standpoint, according to munjeni, who is well recognized as very knowledgeable in these things, KK is better, (.108 firmware specifically). He has a lot to say about it in his thread for his stock based LP ROM. Personally, I don't know much about all that, so for me it's more about user experience and trying something new. I like to go back and forth. I guess it just depends on what your priorities are.
F308 said:
Opinions differ. Some specialists from this forum reverted from LP to KK for different reasons.
My personal opinion is that with every step ahead software becomes more complicated, investigates you and your activities in bigger grade and is more troublesome during rooting and personal modifications.
Since long ago my principal rule is: "Don't touch things which work correctly".
I am still on KK .108 however I tuned it in 100+ places to suit my needs.
Click to expand...
Click to collapse
It's exactly my opinion too buddy :good: and since, from what I read here, there is too much discordance amongst opinion, I think I'm going to keep faith to this mantra still for a long of time LOL
levone1 said:
Personally, I don't know much about all that, so for me it's more about user experience and trying something new.
Click to expand...
Click to collapse
Well. This IS a point, especially if you have free time to spend.
Otherwise I suggest to root phone, tune sound, camera, fast dormancy, gps.conf, remove bloatware, use better battery stats to tune battery usage, install Xposed modules and do more similar actions.
No comparison to branded phone.
LP is great regarding the user experience (visuals and animations) and I was able to get rid of a couple of apps after switching from KK (lock screen notifications, bt watch keeping device unlocked -> smart lock). Performance and battery life are still ok and I can not notice any difference.
but ... if you are considering moving to cm12.1
you should wait until the wifi / bt bug has been fixed, which is a major problem
and there is an issue with AudioFX (equalizer) that keeps crashing, which is annoying
pr3ddi
yesterday i was checking if there was a firmware upgrade for my phone (SM-A325F) on samfw. well for other reasons. i saw an update for other regions that was unusual. Samsung had bumped the binary bit version from 2 to 3. Now this scared me. since if the fw arrives for all the regions it will make it undowngradable to one ui 3.1 or 4.1. since I am using gsi's (Generic System Images) which is currently crdroid 9.2. It may cause a problem if samsung breaks something with the update. Since i wont be able to downgrade to older firmwares. Twrp might also be a problem since i have seen threads on a12 that some twrp versions do not work for some binary bit versions. That scared me. Although i could get around this by using repacksuper but still. I have a custom kernel made by myself that i am daily driving. it will make it hard to install since i'll have to decompress and repack boot.img. Then disabling encryption... i am pretty sure gsi's wont boot with encryption enabled. I have no idea on how i' disable it. without twrp. there might be ways i'd have to do research.
I might just be overthinking. but yes. i'll have to test when it comes out for my region. I am also waiting for one ui 5.1 which may also have bumped binary bit version.
D:
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be!
Upgrades and updates can and do break Samsung's. It can easily turn into a time devouring hurt locker tour if it damages, alters or destroys features or functionalities you are using and depending on.
Doing nothing breaks nothing...
blackhawk said:
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be!
Upgrades and updates can and do break Samsung's. It can easily turn into a time devouring hurt locker tour if it damages, alters or destroys features or functionalities you are using and depending on.
Doing nothing breaks nothing...
Click to expand...
Click to collapse
Exactly
blackhawk said:
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be!
Upgrades and updates can and do break Samsung's. It can easily turn into a time devouring hurt locker tour if it damages, alters or destroys features or functionalities you are using and depending on.
Doing nothing breaks nothing...
Click to expand...
Click to collapse
thats true. but i have been facing weird issues with android 13 firmware's vendor. thats why i wanted to upgrade. I wont for now. It also seems a bit slow to me. unlike other people saying that running generic system images on their vendor works fine and smooth. while its laggy for me.
Captain_cookie_200 said:
thats true. but i have been facing weird issues with android 13 firmware's vendor. thats why i wanted to upgrade. I wont for now. It also seems a bit slow to me. unlike other people saying that running generic system images on their vendor works fine and smooth. while its laggy for me.
Click to expand...
Click to collapse
such as 60Hz bug happening on most new gsi's where it wouls refuse to switch to 90Hz. Only with A13 vendor. A11 vendor works fine.
Captain_cookie_200 said:
thats true. but i have been facing weird issues with android 13 firmware's vendor. thats why i wanted to upgrade. I wont for now. It also seems a bit slow to me. unlike other people saying that running generic system images on their vendor works fine and smooth. while its laggy for me.
Click to expand...
Click to collapse
Between a rock and a hard place... Google punches these systems out too fast. Problems are a given. Best to stick with one version, find fixes, work arounds and be happy. Otherwise you'll constantly be mucking with it.
I'm still running 9 and 10 on my stock N10+'s. No way I'm upgrading. I prefer Pie though. Current load on this N10+ will be 3yo in June, still running fast and stable. Zero security issues in that time.
Scoped storage... No. It wasn't needed; it just causes headaches and unwarranted complexity.
Gookill invariably makes a mess out of anything they do (or kill it) eventually; it's their nature.
blackhawk said:
Between a rock and a hard place... Google punches these systems out too fast. Problems are a given. Best to stick with one version, find fixes, work arounds and be happy. Otherwise you'll constantly be mucking with it.
I'm still running 9 and 10 on my stock N10+'s. No way I'm upgrading. I prefer Pie though. Current load on this N10+ will be 3yo in June, still running fast and stable. Zero security issues in that time.
Scoped storage... No. It wasn't needed; it just causes headaches and unwarranted complexity.
Gookill invariably makes a mess out of anything they do (or kill it) eventually; it's their nature.
Click to expand...
Click to collapse
these bugs i face are expected since these are not device specific roms. but fix is always possible. One ui itself for this phone is kind of terrible otherwise i wouldnt have tampered with gsi's to start with
Captain_cookie_200 said:
these bugs i face are expected since these are not device specific roms. but fix is always possible. One ui itself for this phone is kind of terrible otherwise i wouldnt have tampered with gsi's to start with
Click to expand...
Click to collapse
Ive gotten excellent mileage from One UI once the device was optimized. Before it was optimized it was a mess. However Samsung firmware can vary widely from model to model, region, hardware and so on. That makes things more difficult and unpredictable.
Until you get on top on it Samsung is a pain. One reason I refuse to upgrade hardware, firmware or software is this device is running pretty clean, fulfilling its mission, requiring very little maintenance and it's fun to use.
blackhawk said:
Ive gotten excellent mileage from One UI once the device was optimized. Before it was optimized it was a mess. However Samsung firmware can vary widely from model to model, region, hardware and so on. That makes things more difficult and unpredictable.
Until you get on top on it Samsung is a pain. One reason I refuse to upgrade hardware, firmware or software is this device is running pretty clean, fulfilling its mission, requiring very little maintenance and it's fun to use.
Click to expand...
Click to collapse
welp for me its the opposite here. one ui is absolutely laggy with its terrible restricted animations for Mid range phones. Then it lags while doing normal tasks. i have found gsi's to be more smoother than one ui. I hate firmware upgrades too. but since this shet is weird and has litt unkown bugs no one has ever seen before upgrading to a newer fw is my only option. Otherwise i'd be stuck on one ui with terrible optimizations for this phone. My friends own the same Galaxy A32 4G and i have seen one ui lag on their phones. it is terrible.
Captain_cookie_200 said:
welp for me its the opposite here. one ui is absolutely laggy with its terrible restricted animations for Mid range phones. Then it lags while doing normal tasks. i have found gsi's to be more smoother than one ui. I hate firmware upgrades too. but since this shet is weird and has litt unkown bugs no one has ever seen before upgrading to a newer fw is my only option. Otherwise i'd be stuck on one ui with terrible optimizations for this phone. My friends own the same Galaxy A32 4G and i have seen one ui lag on their phones. it is terrible.
Click to expand...
Click to collapse
Hard to say why that is without playing with it.
One UI should be fast, stable and use very little battery. If you saw this N10+ out of the box though it could be described as what you are seeing. It was a handful at first. Literally getting less then half the SOT it gets now. The lagging generally is caused by junk running in the background, that was noticeably slowing down this phone. Using up possessor and modem bandwidth. Quit the terror
I eventually got it optimized using with Package Disabler, settings and a few 3rd party apps. It's a completely different experience from that hog mess it first was.
blackhawk said:
Hard to say why that is without playing with it.
One UI should be fast, stable and use very little battery. If you saw this N10+ out of the box though it could be described as what you are seeing. It was a handful at first. Literally getting less then half the SOT it gets now. The lagging generally is caused by junk running in the background, that was noticeably slowing down this phone. Using up possessor and modem bandwidth. Quit the terror
I eventually got it optimized using with Package Disabler, settings and a few 3rd party apps. It's a completely different experience from that hog mess it first was.
Click to expand...
Click to collapse
using floating.xml tweaks i made my one ui installation some what usable. also note... (haha note..) your note 10+ is an older flagship phone. while the galaxy A32 is a mid ranger that samsung pays less attention to. Thus we are hit with such bugs and terrible optimizations disabled features till to this day. obv samsung rigs the one ui experience on these phones on purpose. otherwise they'll be "too good". even using alot of tweaks and mod doesnt help improve it much. trust me i tried daily driving one ui with floating tweaks and others..
Captain_cookie_200 said:
using floating.xml tweaks i made my one ui installation some what usable. also note... (haha note..) your note 10+ is an older flagship phone. while the galaxy A32 is a mid ranger that samsung pays less attention to. Thus we are hit with such bugs and terrible optimizations disabled features till to this day. obv samsung rigs the one ui experience on these phones on purpose. otherwise they'll be "too good". even using alot of tweaks and mod doesnt help improve it much. trust me i tried daily driving one ui with floating tweaks and others..
Click to expand...
Click to collapse
Likely true. The older N10+ is likely a better choice than the newer midrange Samsung's due mostly to hardware but maybe firmware too. The newer Samsung flagships haven't turned out all that well either. The variable refresh rate displays are causing a lot of troubles across the board. Scoped storage is another CPU cycle sucking issue on Android 11 and higher.
5G can add to the problem; if in use it can use a lot of resources.
Rather than squander money on their Fold technology Samsung maybe should have thrown the money at it's midrange phones...
blackhawk said:
Hard to say why that is without playing with it.
One UI should be fast, stable and use very little battery. If you saw this N10+ out of the box though it could be described as what you are seeing. It was a handful at first. Literally getting less then half the SOT it gets now. The lagging generally is caused by junk running in the background, that was noticeably slowing down this phone. Using up possessor and modem bandwidth. Quit the terror
I eventually got it optimized using with Package Disabler, settings and a few 3rd party apps. It's a completely different experience from that hog mess it first was.
Click to expand...
Click to collapse
Got a list?
blackhawk said:
Likely true. The older N10+ is likely a better choice than the newer midrange Samsung's due mostly to hardware but maybe firmware too. The newer Samsung flagships haven't turned out all that well either. The variable refresh rate displays are causing a lot of troubles across the board. Scoped storage is another CPU cycle sucking issue on Android 11 and higher.
5G can add to the problem; if in use it can use a lot of resources.
Rather than squander money on their Fold technology Samsung maybe should have thrown the money at it's midrange phones...
Click to expand...
Click to collapse
this is exactly why i am never getting a samsung again. especially midrangers. they are wful. idk why samsung even bothers to make phones if they cant maintain it properly. Yet mor phones are being added to A series line up day by day.
Like a software update literally bricked my fingerprint on display. looking at the logs. my keystore is gone and using no matter what firmware it wont come back. great samsung. the last great thing abt this phone for me is gone now.
Yet i remember how upgrading to one ui 4.1 from 3.1 caused an issue where my ril would restart when using data. It would happen randomly. One ui 5 fixed this later on but wow samsung...
i had to resort to gsi's to get a working phone again since one ui 3.1 was slow af.
samsung has basically fuked me in every single way. and now i am just stuck with this thing for 4-5 years.
so to fix such annoying bugs that still exist. i my have to do the update... Yes ik it may cause my ability of downgrading to go away but still.. atleast i may get a better experience hopefully. otherwise welp ig i'll be stuck on one ui again. sucks to be me.
Captain_cookie_200 said:
this is exactly why i am never getting a samsung again. especially midrangers. they are wful. idk why samsung even bothers to make phones if they cant maintain it properly. Yet mor phones are being added to A series line up day by day.
Like a software update literally bricked my fingerprint on display. looking at the logs. my keystore is gone and using no matter what firmware it wont come back. great samsung. the last great thing abt this phone for me is gone now.
Yet i remember how upgrading to one ui 4.1 from 3.1 caused an issue where my ril would restart when using data. It would happen randomly. One ui 5 fixed this later on but wow samsung...
i had to resort to gsi's to get a working phone again since one ui 3.1 was slow af.
samsung has basically fuked me in every single way. and now i am just stuck with this thing for 4-5 years.
so to fix such annoying bugs that still exist. i my have to do the update... Yes ik it may cause my ability of downgrading to go away but still.. atleast i may get a better experience hopefully. otherwise welp ig i'll be stuck on one ui again. sucks to be me.
Click to expand...
Click to collapse
The N10+ Snap is still a good choice if you don't need to root if you can get one running on 9 or 10. The Exynos variant can be rooted but the hardware isn't as good. The spen is very useful.
I learned the hard way with my S4+ that it's a big mistake to upgrade/update the firmware especially on carrier phones. Haven't repeated that mistake.
I don't blame you for being irate about Samsung. They are a mess. The N10+ is the only Samsung I would consider getting even now.
I think this is getting off-topic.
Arealhooman said:
I think this is getting off-topic.
Click to expand...
Click to collapse
yeah it is. main purpose of my thread was if twrp breaks due to diff version of bootloader. because i wont be able to downgrade once i upgrade. I could patch my stock recovery for fadtbootd but i would still love to have twrp.
An update. so i built a kernel for this thing using source samsung released with the bumped bit version. flashed it on an older bit 2 firmware. it works fine and i am daily driving it now. i thought it wouldnt boot. but it does.
So looks like the update i previously refered to had SB3 boot loader. i saw it for nepal. while i just saw one ui 5.1 drop for this phone with the U3 boot loader. i am upgrading and i'll tell wether the twrp and other stuff works. If not i'll report any workarounds i used.