Hi guys, I'm a jailbroken iPhone 6S+ user. I'm currently a slave to Apple's ecosystem (iPad, Apple TV, Watch but not a Mac) I apologize for the wall of text below, but I know you guys are always glad to give a helping hand.
I've been using iOS since the iPod Touch 2G, taking a break for a couple months only in the Galaxy S3 days, which was my first and only android experience. Many iOS users are in the same boat as me.
Android was a whole different thing back then. Nowadays, when I see the curved, bright and saturated screen of an S7 and how well it pairs with the material design, I feel like I'd love to give that a spin. My problem is that I've been fed constant complaints on behalf of android users, using different handsets and at different times. Here are my main concerns:
I've always heard that, after a "honeymoon" period, almost without fail, all android handsets start to experience stuttering, freezing, rebooting, framerate drops, etc. (maybe one of those at a time, sometimes all of those are common occurrences) does this happen? This is the most important one for me, because if there's something that none of my iPhones ever suffered from, was reduced performance.
Software glitches which are mostly hardware-specific. I've visited the 6P subreddit, only to find a plethora of people complaining about the camera app freezing or crashing, some focus issue I believe as well, or maybe just reduced performance in other parts of the OS (which is the purest form of android). I've also heard that Samsung's bloatware, although only a fraction of what it was back on the S3 days, still causes the phone to feel sluggish at times. Haven't heard about Huawei or HTC bloatware, but I have watched reviews which mentioned some lag here and there.
Software updates. The whole ordeal of having to choose a phone thinking about whether it will get updates in the future or not is pretty sad. I know that Nexus phones are guaranteed to get updates for two years I believe, but as I stated before, visiting the 6P subreddit, I've seen people complain about Google updating the OS but leaving bugs unresolved for several iterations of it. How do you handle this when choosing a phone?
Customization. If there's one area that I've been always convinced Android was leaps and bounds ahead of iOS was this. However, as a jailbroken iOS user, I find that I get most of what you guys can get out the box, but in a prettier package. As in, jb tweaks are very tightly integrated and always match the OS look and feel. In Android, you work with apps or, after rooting, with "modules" I think they're called. How do these differ from JB tweaks (stability-wise as well)? How different is the process of waiting for root vs waiting for a JB? Is rooting as necessary as jailbreaking?
Lastly:
Apps. I am aware of the differences in general app quality when comparing the App Store and the Play Store. Big names such as FB, Twitter, Instagram, etc are mostly the same. But when you start digging a little bit deeper, you find that there's a big difference in not only availability, but also variety and polish. At least, that's how my experience was and what I tend to hear from Android users. How's the Play Store these days? Has this changed a bit?
I apologize once again for the wall of text. If you could answer each point with one or two lines I'd be immensely grateful. Honestly, since these points are big question marks in my head right now, I wouldn't even know what handset to look into, because I don't want to be unpleasantly surprised later on. Android screens though... Damn. Most of them are sexy.
Anyway, thank you very much for your time. Any help is deeply appreciated.
Stuttering/Freezing. You might find this on some low-end devices but the "flagship" devices that I've used haven't suffered from this. This would generally be caused by lower end hardware (lower clocked CPU and lower RAM).
Software glitches. I own the 6P and have never had the camera crash or freeze, never had any software issues with this phone actually. Samsung phones are pretty well known to suffer from being sluggy, this is due to their Touchwiz UI which hogs quite a bit of RAM. The HTC devices I've owned haven't had this issue. Can't speak for Huawei's own UI. The Huawei 6P uses pure Android, I don't notice any real lag issues on this phone.
Updates. If you want guaranteed software updates your best bet is a Nexus. I've noticed no major bugs on the 6P apart from a 4G bug that was specific to an Australian carrier but that was patched pretty quickly. There have been things in Android that people label as bugs that haven't been patched immediately though. Even if you choose a device that may not be updated officially you will very often be able to update via a custom ROM, custom ROMs are often developed for devices long after official support has stopped.
Customization. Android is definitely far ahead in terms of customisation. Most people find customisation via a custom ROM (a customised version of the OS, sometimes based on the stock OS, sometimes based on AOSP (Android Open Source Project or "pure Android"), sometimes based on something like CyanogenMod). A ROM will almost always have extra features and tweaks, these features are usually very well implemented and tie in very nicely with the OS. When speaking about modules you'd be referring to Xposed Modules which are used with the Xposed Framework. Xposed basically opens up a lot of customisation ability, it requires root, it can be used on a stock ROM with root or with a custom ROM. There are a plethora of modules available, too many to even begin to list, the best way to see what they can achieve is to look in our Xposed Modules section. As for root in general, you don't generally need to wait for root like you would with jailbreaking. Having root access is also far more flexible than jailbreaking, you can pretty much do anything with your phone, you have full access to the otherwise blocked system partition. Root methods will vary from device to device but you'll usually need an unlocked bootloader. The easiest devices to root and modify are the Nexus devices, they're designed to be tinkered with, development phones first and foremost.
Apps. In the early days of Android, and even up until a few years ago, the Play Store really lacked in terms of availability and quality. The last few years have seen a dramatic increase in both areas though, there's a wide variety available and the quality has become top notch.
In summing up, it looks like the worries you have are misconceptions commonly held by Apple users.
As a former board level apple technician who used the first ever apple products in kindergarten nearly 30 years ago, I must say I can't even use an iPhone. With all respect, most of your thoughts are not accurate.
Sent from my Nexus 6P using XDA-Developers mobile app
Related
Hi everyone,
I'm a writer for LockerGnome.com and currently putting together an article exploring Google's new Android strategy. I'm looking for some opinions, particularly from developers, about what Google's new strategy portends for ROM development.
In a nutshell, here's Google's new strategy for Android: It will be giving multiple mobile-device makers early access to new releases of Android and to sell those devices directly to consumers. (Search "site:wsj.com google" for the Wall Street Journal's report. Hopefully you'll be able to access the link I've provided, but if not: Essentially, Google will be offering consumers more phones to purchase with a "vanilla Android" experience; they will then be able to take these phones to the cellular carrier of their choice. A researcher quoted in the article believes that Google is moving toward a more iOS-like experience, with less variance among devices.
What I'd like to know is what those in this community feel will result due to this new strategy. Since they're may be less variances among future Android devices, will there be less of a demand for "vanilla-ized" Android ROMs? My understanding of CyanogenMod is that one of its main appeals is that it allows for users to experience a plain, "vanilla" Android on devices -- with enough new devices already offering a pure, bloatware-less Android, will the CyanogenMod scene begin to fade in relevance?
Please let me know if I can use any of your comments in my article, and let me also know how you would like to be attributed if I use your comment(s). (Private message me, if you'd like, with a link to one of your online profiles or a website that you run, or some such thing.)
Thanks!
I'm a writer for LockerGnome and
well i dont think its gonna be an iOS-like experience at all, its all gonna be pretty much the same cept we'll have 5 nexuses, manufacturers are still gonna be making their devices with their 'OEM skins' just the like theyre doing it now. i also can feel like manufacturers are gonna release same device theyll have as nexus with their skin on top (picture the One X with the option to choose if you want it with sense or with vanilla/stock android) kinda like the Desire Z and the T Mobile G2, its gonna be even better for us flashaholics cause well be able to flash more ROMs
also Cyanogenmod its gonna keep growing cause even if its AOSP based they add their own optimizations making the experience even better, every more and more people are flashing that particular ROM even if their device has vanilla android already in it
nonione said:
well i dont think its gonna be an iOS-like experience at all, its all gonna be pretty much the same cept we'll have 5 nexuses, manufacturers are still gonna be making their devices with their 'OEM skins' just the like theyre doing it now. i also can feel like manufacturers are gonna release same device theyll have as nexus with their skin on top (picture the One X with the option to choose if you want it with sense or with vanilla/stock android) kinda like the Desire Z and the T Mobile G2, its gonna be even better for us flashaholics cause well be able to flash more ROMs
also Cyanogenmod its gonna keep growing cause even if its AOSP based they add their own optimizations making the experience even better, every more and more people are flashing that particular ROM even if their device has vanilla android already in it
Click to expand...
Click to collapse
Thanks for your comments. So with the introduction of more "Vanilla" Android devices, you believe the "flashaholic" community will continue to grow? Won't the majority of consumers who purchase the unlocked Android devices no longer have a reason to flash their devices? It's obvious that "flashaholics" enjoy optimizing and overclocking their phones (even at the expense of other things, such as battery life) -- but don't you think most consumers would prefer not to void their warranty (and would generally opt for better battery duration rather than a speed boost)?
You can use anything. Please attribute me as "lalop".
Note: An important distinction to make (not having the article at hand, I'm not sure if the researcher made it himself): Google is attempting to reduce the variance in the software of Android phones. In terms of hardware, it is the complete opposite. Encouraging competition between multiple Nexii will ensure that only the most cutting-edge designs are sent in. Without any OEM differentiation on the software, the contest truly becomes that of the best manufacturing. (This means no more half-assed Nexus specs/accessories *cough Samsung cough*.)
charssun said:
What I'd like to know is what those in this community feel will result due to this new strategy. Since they're may be less variances among future Android devices, will there be less of a demand for "vanilla-ized" Android ROMs? My understanding of CyanogenMod is that one of its main appeals is that it allows for users to experience a plain, "vanilla" Android on devices -- with enough new devices already offering a pure, bloatware-less Android, will the CyanogenMod scene begin to fade in relevance?
Click to expand...
Click to collapse
CyanogenMod turns OEM skins into AOSP, that is true, but the result can hardly be called "vanilla". The "Mod" itself adds so much customization and speed that, as I noticed firsthand from using the Galaxy Nexus, the stock ROM and CM9 aren't really comparable at all.
Now, you talk about "vanilla-ized" ROMs, but I would suggest this is a misnomer. Yes, anyone can compile AOSP if they just want a "vanilla" ROM, but there's almost no point to just stopping there and going no further. The ROM and/or kernel are just begging for your tweaks, your mild improvements, and this is precisely what drives the homebrew developer.
As such, it turns out that almost every custom ROM has something differentiating it from the original; even the so-called "vanilla experiences" are generally designed to be smoother and have better battery life. No number of stock phones from Google could possibly reduce the demand for (nor the incentive to create) such things. So I would say that the answer is "no" on all accounts.
---
Now, the effect of multiple Nexii on homebrewing that would worry me is "fragmentation" (though not in the usual sense of the word). Having five Nexuses would effectively detrone each one from its former pedestal as the (no pun intended) Nexus of development. Since most homebrew developers would probably not purchase all five (and would have a harder time maintaining all versions even if they did), this could end up having an adverse effect on their development. Although having a fleet of Nexus is practically a dream come true, I fear that five may be too many, and may unintentionally compromise their development as a whole.
Now, as pointed out by lazaro here, this would not affect ROM development per se, only low level stuff like kernels. The obvious way I can think of to avoid the issue is to mandate similar hardware for all the Nexus - and yet I feel this is undesirable. After all, competition is key here, and I'm sure we're also all waiting for our Nexus Note™, of course! *hint hint*
http://t.co/9rTNXkvM
Here are some of my thoughts on the matter.
I am more excited about this than I have been for any other Android news ever! I am ready to get out of the continuous contacts and upgrade dates, especially the high prices for service.
As far as development goes, some of the best development has been done on Nexus devices, except of course the hd2... What will be good for manufacturers is that they will receive earlier updates for android allowing them to tweak their proprietary versions sooner allowing quicker updates!
For custom rom's you will see a lot of activity.
Sent from my PC36100 using xda premium
thebobp said:
You can use anything. Please attribute me as "lalop".
Click to expand...
Click to collapse
Thank you for taking the time to post your comments; my own response to yours is below.
thebobp said:
Note: An important distinction to make (not having the article at hand, I'm not sure if the researcher made it himself): Google is attempting to reduce the variance in the software of Android phones. In terms of hardware, it is the complete opposite. Encouraging competition between multiple Nexii will ensure that only the most cutting-edge designs are sent in. Without any OEM differentiation on the software, the contest truly becomes that of the best manufacturing. (This means no more half-assed Nexus specs/accessories *cough Samsung cough*.)
Click to expand...
Click to collapse
I was vague in my description of what was mentioned about device variance in the article. Here's exactly what the writer of the article stated:
Rajeev Chand, head of research at Rutberg & Co., said Android has become a kind of "Wild West" in which app developers have struggled to make sure apps are compatible with hundreds of different Android-powered devices. Both device makers and carriers have left their imprint on devices, meaning the "customer experience is highly variant", he said.
Mr. Chand said Google's shift appears to be a move "to create a more standardized experience for consumers and app developers," similar to that of Apple.
Click to expand...
Click to collapse
Does that fit what you're asserting?
thebobp said:
CyanogenMod turns OEM skins into AOSP, that is true, but the result can hardly be called "vanilla". The "Mod" itself adds so much customization and speed that, as I noticed firsthand from using the Galaxy Nexus, the stock ROM and CM9 aren't really comparable at all.
Now, you talk about "vanilla-ized" ROMs, but I would suggest this is a misnomer. Yes, anyone can compile AOSP if they just want a "vanilla" ROM, but there's almost no point to just stopping there and going no further. The ROM and/or kernel are just begging for your tweaks, your mild improvements, and this is precisely what drives the homebrew developer.
Click to expand...
Click to collapse
The term Vanilla is how the CyanogenMod "look" is described at http://www.cyanogenmod.com/about. I should have recognized that there is a world of difference between aesthetics and performance. Thanks for pointing that out.
thebobp said:
As such, it turns out that almost every custom ROM has something differentiating it from the original; even the so-called "vanilla experiences" are generally designed to be smoother and have better battery life. No number of stock phones from Google could possibly reduce the demand for (nor the incentive to create) such things. So I would say that the answer is "no" on all accounts.
Click to expand...
Click to collapse
I don't have any experience with iOS devices; is there a similar incentive to modify iPhones and iPads purchased directly from Apple?
thebobp said:
Now, the effect of multiple Nexii on homebrewing that would worry me is "fragmentation" (though not in the usual sense of the word). Having five Nexuses would effectively detrone each one from its former pedestal as the (no pun intended) Nexus of development. Since most homebrew developers would probably not purchase all five (and would have a harder time maintaining all versions even if they did), this could end up having an adverse effect on their development.
Although having a fleet of Nexus is practically a dream come true, I fear that five may be too many, and may unintentionally compromise their development as a whole.
Click to expand...
Click to collapse
One thing to note: Google will be working with "as many as five manufacturers at a time to create a portfolio of 'Nexus' lead devices that include smartphones and tablets." To me, this doesn't necessarily imply just give devices -- there could be a few devices from each manufacturer.
thebobp said:
Now, as pointed out by lazaro here, this would not affect ROM development per se, only low level stuff like kernels. The obvious way I can think of to avoid the issue is to mandate similar hardware for all the Nexus - and yet I feel this is undesirable. After all, competition is key here, and I'm sure we're also all waiting for our Nexus Note™, of course! *hint hint*
Click to expand...
Click to collapse
Thanks again for your views. If I use your comments I'll be sure to attribute them to "lalop"; is there also a URL you are associated with that I may link to? If you prefer privacy, that's perfectly understandable. Also: Are you a developer?
So I've seen this word thrown around a lot since switching to Android from my old iPhail 3G (yes, I actually lived with that horrible laggy device for ~4 years) and in comparisons between Android and iOS (which I'm not trying to get into here). I've also read lots of people saying Jelly Bean was supposed to be 'snappier' compared to ICS. I wasn't sure if they were referring to lag as in fps or a delay in reaction. My Note II is currently stock 4.1.1, but I'm definitely noticing some delay in games, such as Air Hockey, between moving my finger on the screen and the paddle moving in the game, for example. It's quite noticeable in apps like Maps too. I had the Galaxy S III for a short time before I decided I wanted the bigger (and better specs) Note II, but not long enough to make any comparisons. My question is, is there a way to increase the snappyness without doing anything too dramatic, such as flashing a different ROM, etc. Or will a ROM like beanstown106's Jelly Beans help? Or is this a problem that is inherently part of Android operating system/devices? Thanks in advance.
marcmy said:
will a ROM like beanstown106's Jelly Beans help? .
Click to expand...
Click to collapse
I can tell you that flashing beans ROM made absolutely no speed difference whatever over my previous debloated/rooted stock ROM (and I didn't really expect it to)
One thing is, it is noticeably laggy when running the inferno galaxy live wallpaper, but pretty much instant response with regular WP.
The "snappieness" in individual apps is really down to the app itself combined with phone specs.
Poorly coded apps may have lag.
High end apps may push the hardware harder and cause lag.
I would bet its mostly the former when it comes to the Note 2.
Samsung also put touchwiz on these phones, which does affect overall performance to some degree. If we get the ability to remove much of it in favor of AOSP versions, then it should perform a little better overall.
The differences between iPhones and Android... is that Apple focuses on user interaction over all other things. So this means they will sacrifice performance in other areas to ensure that user interactions are kept smooth, or at least keep the appearance of smoothness. For example, iOS will stop loading web pages when you start to scroll the screen, so the CPU can focus on smooth scrolling. This means that the page will never finish loading if you keep scrolling around on the screen. Android does not do this or these kind of things. The new "project butter" implemented in JB is designed to help smooth out the interface and user interactions, without sacrificing performance in other areas. Its not perfect though, and it requires good specs and more power than the iOS way of "one thing at a time".
Great response ty very much. I guess next question is will we be able to get those AOSP versions later on or are we SOL in that department?
Sent from my SCH-I605 using xda app-developers app
Depends on which version you have.
I am on Verizon, so my device is locked down, other versions are not.
This device is also unique in the fact it has a Wacom stylus and functionality, so that must be considered.
Often times, you can swap things out without too much issue. AOSP lockscreen instead of touchwiz lockscreen... AOSP launcher instead of touchwiz launcher... without too much trouble. Problem is, underneath the ROM is still touchwiz... or at least that is how it worked on HTC Sense phones. (this is my first touchwiz device) HTC do a lot of work to the underlying framework which meant wholesale replacement of everything wasn't possible, so it depends on how much Samsung changed Android to put touchwiz on it.
Basically they "DE-Touchwiz" the phone and do some background tweaks for added performance, plus they "de-bloat the ROM. (they remove all the unnecessary crap that the carriers and Samsung put in, that served them some benefit, but not benefit the users) The advantage of this method is that you can keep much of the functionality of the stylus.
Another method is to use a ROM based on stock, but tweaked and de-bloated. This usually retains all the functionality of the device as it came out of the box... but the performance is usually only a little better than stock, and less than one where the AOSP stuff has been put in. This method does allow you to keep most of the stylus functionality.
As far as straight up custom ROMs based on AOSP...
They usually offer the best performance for a given device, having no extra crap, and being tweaked for performance... But you will lose most if not all the stylus functionality. Some ROMs may have limited stylus functionality, but they have to put that in themselves, meaning more work on their part.
As far as performance gains... I can only speak of HTC Sense devices with sureness. Where pure AOSP usually had significant improvements to performance/battery life. (mostly due to how extensive Sense is, touchwiz may be better in this regaurd) "De-sensed" ROMs where they removed all of the Sense stuff they could and replaced with AOSP equivalents, had good performance increases. "De-bloated" and tweaked but otherwise stock ROMs had some improvement.
But as was said, the stylus functionality is something that must be considered when looking at ROMs
After using AOSP ROMs quite extensively in both of my two Galaxy 3s, I have no desire whatever to run those type ROMs in my Note 2 (and lose things like pen functionality).
I could never see any performance difference whatever (except maybe in useless benchmarks) between a completely debloated TW ROM with all the features working perfectly and a buggy AOSP ROM in my G3s (and I tried every G3 ROM available at least twice).
Posters where constantly claiming this ROM is PERFECT when discussing any AOSP ROM but two posts later someone else would post "can anybody get NFL Mobile to work??" The next post would say "that has never worked in AOSP but I never use it anyway so who cares........"
Good call. I'd rather keep most functionality
Sent from my SCH-I605 using xda app-developers app
You could go into a store and try some of those games out on a DNA. Hopefully some are free so you don't have to put your google account in the play store and then clear the data. The DNA's gpu is much faster. It sounds like it's the app coding though. I don't have any input lag with on screen buttons playing GTA or N64oid, and emulators are pretty heavy on the processor.
With my old tablet the custom roms always meant a performance increase too, but:
I've tried pretty much well every single custom rom available for this tablet by now and i still havent managed to find one that actually increases the performance of the tablet. When im running the stock firmware i get about 7500-7600 on quadrant and my browser is really responsive and stuff. There's not been a single custon rom out there that has even performed better then 5600 on quadrant. Is it just me, or are the custom roms not hat good performance wise?
EDIT: By better performance i mean how snappy the tablet feels, using benchmarks as a secondary frame of reference.
Not sure if quadrant is doing a good job. I also am getting same results as you with 7xxx for stock and 5xxx for all CM based ones. Although the CM roms feel smoother here.
Sent from my SGP311 using XDA Premium HD app
I abstained the vote cause the question does not bear a black and white / yes or no answer anymore these days.
In my humble opinion, and I picked up the smartphone / PDA / mobile device modding bug back about when this site catered to the the original HTC XDA almost exclusively, and Steve Jobs was merely having wet dreams about his iPhone (*1)... nodded RIMs have gotten to a state where they are overvalued. Saying a custom ROM is always way ahead of stock is like saying "one device with a fixed featureless fits everyone perfectly".
Custom ROMs had their deserved heyday when the industry loaded up near every carrier distributed smartphone with scrappy bloatware that made you weep. Depending on the mobile OS at any given time it was nigh impossible to get rid of that stuff, unless you flashed the whole shebang. From there on the custom ROM scene kinda exploded along with the market distribution of smartphones and later on tablets, certainly owed to the introduction of Android over older generation closed source systems, which enabled much more in-depth possibilities of adding novel features, fixing stuff that was basically broken out of the box and integrating all of this nicely.
(For a frame of reference: I tossed my PalmPilot and Nokia phone when the HTC Wallaby (Telekom MDA or so)hit the shelves... Early adopter by nature and I thought combining cellphones and PDAs, bother which I used avidly was the most revolutionary idea since the combustion engine. This was generation Windows Pocket PC, basically a PDA with cellphone feature thrown in as an afterthought (the antenna actually doubles a stylus compartment). Phone integration was a PITA on good days. On bad, long work days it might just happen that your moody battery would jump from 35% to flat out dead within a mere six minute phone call. Yet, no biggie right? Well, it was, the devices had no non volatile storage. Dead battery means go home, pray your last phone backup is recent enough and restore the entire thing. I spent a lot of time fixing this device (windows style - shoehorning in binary OS components from newer PocketPC versions and prodding the registry on the phone (!)...) to a point where it was almost usable as PDA only device, supplementing telephonly with a Nokia.
A while later better devices came out, PocketPc was scrapped for Windows Mobile and in high hopes I got a HTC Charmer. This looked like a more solid platform and indeed proper custom ROMa emerged, adding real functionality and allowing to get rid of carrier branded crap, later even RIMs emerged with Windows Mobile version updates never intended for that phone, some even taking the recent cutting edge HTC front-end, the first incarnation of Sense (I think it was called vanilla). I figured the really bad conceptual problems were fixed and merrily went along. But, as god hates my guts, I drained the battery accidentally, only to find that the phone would still go dead, deaf, dumb and wiped despite a good three or four years of technological progress. I was so confident that I neglected backups with that model and basically lost the majority of my stuff again. The Nokia dumbphone was back in the game, the HTC left a dent in the wall that required plaster and a patch of new wallpaper.
TL;DR: The first gen smartphones (PDA with cell module afterthought were such flawed concepts, badly integrated, that keeping recent backups and maintaining it operational took quite an effort on user side, on that sort of negated the higher productivity of using one altogether. But bear with me now, I am still circling around the point or two I want t. Make.
Because a few months after I abandoned smartphones for good (or so I thought) Apple coughed up their iPhone prototype and a few months later pumped it to market. I was amazed (not because of the technological feat, they were more or less throwing R&D money bricks at existing tech and concepts, however they exactly figured out what went wrong in the early generations, fixed that stuff, added fingerdriven multi-touch in favor of stylus driven displays and, this is the real kicker, in a time and age when the cool cell to have was a Nokia 8 Series or a decent, very small flipphone or clamshell they managed to brainwash their customers into what PDA and smartphone adopters at that time already knew - it's totally worth to dump the train of ever smaller telephony only cells for a much larger, more fragile device because of all the freedom and power those things offer you.
I kept my guard and obviously went for Android devices once I got back on the horse. HTC Desire, a backup Wildfire, Desire HD, Sensation, One S and a few tablets along the way. Now, here is the kicker. The Desire ran much better with a custom. The Wildfire could only be updated to a recent Android version with a custom ROM due to HTCs sometimes appalling quick update discontinuation. The Desire HD ran a basically stock custom ROM! But with lots of lovely icon eyecandy, so I stuck with that too. The Sensation benchmarked equally (give or take 5%) but the ROM added novel features, properly implemented, which I decided to stick with. But frankly, it was because I could. I would not have recommended a newbie to Android flashing to take the plunge. My current HTC One S has a recovery downloader and is rooted cause some essential apps I can't live without need it. Full custom ROM switch. I see no point. Android has come a long way. If today I have bloatware I can go to App Manager and disable them. Icon gone, runtime resource hogging gone. Many features that were the selling points for a custom ROM a while back are now natively incorporated.
This is just how I feel about my Sony SGP311 now. It runs 4.2.2 rooted, no recovery yet. This is planned, maybe at some point a stable, close to stock custom kernel to allow some overclocking on a per app basis for XBMC. But other than that it just Danny works. The Sony skin put over stock Androi. Is not that bad, and more to the point it never gave me the impression of hogging the system. Turn off what is useless to you, Office suite, walkway, etc and be on your merry way. It just comes down to what you do with the device, but as a custom ROM junkie who has just gotten off the habit, for me it makes no sense anymore.
Now, if you made it all the way here, I ran two benchmarks on my 4.2.2 root but stock. Maybe they aid you in your decision.
EDIT: the attachments are garbage. Here are proper links:
http://i.imgur.com/vMFEX1p.png
http://i.imgur.com/IEPVvMS.png
http://i.imgur.com/mB5MKSH.png
Also, none of the above is supposed to rain on the developers parade or something. I admire your skills and dedication over all those years, and there isn't a single custom ROM that went onto my devices withour a PayPal "crate of beer" donation ever. However, the fiddling, time spent reading up on custom ROM choice, issues and unlocking process etc is just not in relation for me anymore. Those thoughts are yours to reject, spindle, mutilate, adopt, oppose or plainly ignore... Just speaking for myself here.
Thanks for this! I was also trying to decide if I should be flashing a custom rom on my XTZ. I am itching to flash but couldn't come up with any strong reason to do so, probably for battery life and stock look?
Will be interesting to hear from another person who is a strong believer of flashing custom rom on XTZ.
Sent from my GT-N7105 using Tapatalk
i got slightly better score using a custom rom. Plus i get themes, expanded desktop and pie control which is a must for this tablet. I hope more xda developers develop for this tablet. Will reward with donations
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Spartoi said:
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Click to expand...
Click to collapse
4.3 too bugy for me
im using 4.2.2 cm rom FXP242-cm-10.1-20131021-UNOFFICIAL-pollux_windy.zip
i already sent team a donation hope to keep em motivated
Spartoi said:
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Click to expand...
Click to collapse
Sorry, the post was incomplete. Changed it.
r1ntse said:
Sorry, the post was incomplete. Changed it.
Click to expand...
Click to collapse
I prefer 4.2 ATM. I get close to 30 Mbps download speed on this ROM where on 4.3 roms only 2mbps download? Also video cam recording, screen is squashed on 4.3. Other than that they run great but I personally cant feel a performqnce boost from 4.3 to 4.2. I also installed crossbreader and Supercharger V6 script which addresses screen redraw lags, so if there is a slower issue with 4.2 i would have addressed it with these two mods and may not be able to tell.
Or will it ever get better ?
I switched from IPhone to Android back in 2013 when Samsung announced the Gakaxy S4. My opinions were mixed and i kept switching back and forth between the iPhone and the S4. I decided to switch to the S4 as my daily driver and since then i never looked back. I kept on upgrading every time to the latest flagship Note 3, Tab S 8.0, and now my Note 4 & Tab S2.
I noticed that android improved a lot in such a short time, but in some areas it remained the same. All of my devices not as smooth as my old iPhone in scrolling specially in websites that contains ads. I tried my best to fix this issue and tried other devices but it seems that Android is plagued with this issue on play store, chrome and many others. It seems like the developers can't hit the right spot in coding.
I tried to look for an answer but most of the info i found pointing to the problem that only Google can fix. Some say that UI rendering is not getting the priority in the process some other they say its because Apple optimize its ios on their phones and other say its because Android coding is hard compared to ios.
Will we ever see Android as smooth as Ios ? The question is going in my mind for a long time and the only reason I'm still with Android is because i love the filixablity that it offers to the user despite the other issues that we face with scrolling and surfing websites.
Would love to hear your opinion and if you have something to share.
Regards
Yathani
Sent from my SM-T815 using Tapatalk
Hello again everyone,
Interesting conversation I want to have with users here; which Android skin do you like most and why?
Obviously AOSP != what Pixels run.
What if a future Honor device ran Android One/Go? Would that be enough to convince you buy one? What if Kirin hardware was still used even with Android One?
What do you like and not like about EMUI?
Really want to get your all's input and feedback.
AOSP has always been my favorite, primarily because it adheres to Google's design standards, and theoretically allows OEMs to deliver faster updates overall.
Skins like EMUI deter from Material Design a fair bit, and it makes it fragments the experience in that sense. It looks too much like iOS, but honestly, I don't mind it too much, because the features it brings with it are actually useful rather than bloat (I'm not saying EMUI is exempt from bloat). Overall, it's a good stock experience, but not something I'd run.
AOSP is also very flexible with projects here on XDA, and it allows for the ease of development and synchrony.
The code is generally cleaner than the additional stuff that OEMs add, and there usually a performance benefit. Skins usually overdo it (I'm looking at you Amazon), and it detracts from what we come to expect from Android itself.
And finally, I'm not sure why, but devices that ship with AOSP-esque ROMs generally feel more premium. Probably because there is less useless garbage.
Those are just my quick thoughts. I hope Honor puts the feedback to use
EMUI tries too much to be like ios. EMUI doesnt incorporate Googles material design. EMUI needs to follow Android design guidelines and features. The share menu looks and functuion like IOS why? We need a better lqauncher. the icons are ios inspired.
Miui und EMUI feel like the interpretation of a 13 years old fan boy of how his phone should work and look like. While AOSP looks much more mature in total feel.
I switched from a phone running Near-AOSP Android 7.1 and now 8.0 to my first EMUI 8.0 device.
EMUI 8.0 on my Mate 10 Pro is a flaming piece of sh*t.
I don't even care about the design. Yeah, it looks like iOS puked all over Android KitKat after a drunken stupor - but that can mostly be remedied with a custom launcher and/or an EMUI theme.
I don't even care that the settings menu feels like it was organized by someone trying to hide their porn collection inside a labyrinth of subfolders back in the 90s. It's stupid, but you get used to it.
I *do* care about the insane amount of things that Huawei/Honor actively broke, removed or replaced with ****tier versions of the same thing.
That things that don't work is staggering:
* Many widgets don't reliably update, they simply die after a while and never show new information. Even Google Widgets are affected, like Google News & Weather.
* Notifications are unreliable. If you don't use an app for a while, don't expect to get any more notifications until you open it - even after fully whitelisting it from everything. I missed several important Facebook Messenger messages because of this. And if Do Not Disturb is enabled, notifications aren't just silenced, they frequently simply disappear into nowhere.
* Some apps simply can never show notifications when in the background on EMUI for more than half an hour, no whitelisting possible.
* Forget about running apps in the background long term, they are frozen eventually, regardless of your settings. And, no, not via Android Doze but via Huawei's own battery management that has all the surgical precision of a sledgehammer.
* You can't disable many system sounds. They also ignore the do not disturb setting and play full volume regardless (like the battery charging sound).
* You can't enable "Do not disturb" for x minutes/hours - that was removed for no reason at all.
* The AOD is essentially useless, it only supports Huawei's own apps, nothing else.
* Lock screen messages can't be expanded or interacted with - the arrow to expand them exists but doesn't do anything.
* You can't even set WiFi connections as metered, the feature was removed - you can't limit background traffic for those connections in EMUI. Forget about ever using a mobile or otherwise metered hotspot with EMUI.
* AdGuard doesn't survive a network connectivity change. When it reconfigures the VPN connection the battery manager kills it, regardless of whitelisting. The only workaround is to never let it reconfigure.
* You can't configure your billing cycle. If it doesn't start at the beginning of the month you are out of luck. One of the many, many native Android features that were simply removed in EMUI with a sledgehammer for no sane reason at all.
* You can't reliably set default apps or even launchers, EMUI loves to reset them back to default randomly. So you launcher of choice decided to roll out an update on the Play Store? Time to enjoy Huawei's launcher again from now on ...
* The same goes for many settings, even in Huawei's own apps - many settings just don't "stick" and are reset after some hours or weeks.
* By default the battery management eventually even stops Chrome from running in the background. Which is the sole WebView provider - breaking just about anything that uses WebView. Insane. At least here the manual whitelisting works as a workaround.
* The camera shortcut was moved from the power button to the volume button for no sane reason, which means it doesn't work when you listen to anything or when the screen is on.
* It has a ludicrous amount of Bluetooth compatibility issues. You though Bluetooth on Stock Android could be iffy? It's compatibility heaven compared to what Huawei somehow managed to do with it.
* Huawei removed Google's Smart Lock and replaced it with ... Huawei Smart Unlock, which currently *only* supports Bluetooth unlock, nothing else, and naturally doesn't even do that reliably.
* You enjoy "OK Google"? Well, Huawei has "OK Emy" as the only assistant capable of waking the phone. It literally has exactly two features (find phone, make a call) and the only semi useful one does not work - at all.
It's the dumbest, most infuriatingly, most idiotic take on Android I have ever experienced.
I still *love* the hardware of the Mate 10 Pro. It's near perfect for me: It's beautiful, fast, great display, amazing build quality and the best battery life and fastest fingerprint sensor of any current flagship.
But I hate EMUI's guts after a couple of months with it. And I really, really tried to like it.
Seriously, why anyone would prefer EMUI over AOSP, or pretty much any other Android skin, is beyond me.
I just miss an Android experience that just works and that I don't feel like I'm constantly fighting. I still love Huawei's hardware, but I'll avoid future EMUI phones like the plague.
freibooter said:
Seriously, why anyone would prefer EMUI over AOSP, or pretty much any other Android skin, is beyond me.
I just miss an Android experience that just works and that I don't feel like I'm constantly fighting. I still love Huawei's hardware, but I'll avoid future EMUI phones like the plague.
Click to expand...
Click to collapse
Just trying to understand users. Some like features from skins that AOSP doesnt offer.
Really appreciate what was stated. I too wish notifications on the lockscreen were improved. Hope to continue the trend to make improvements with EMUI and listen to our users
[email protected]_USA said:
Just trying to understand users. Some like features from skins that AOSP doesnt offer.
Really appreciate what was stated. I too wish notifications on the lockscreen were improved. Hope to continue the trend to make improvements with EMUI and listen to our users
Click to expand...
Click to collapse
Please try a stable custom rom like Omni ROM and you will understand that most people here on XDA just want good developer support. AOSP doesn't have features but it is designed well and less in your face like EMUI. And those that are here on XDA probably root it and install a custom ROM that is based on AOSP with added features without the cartoon like UI that some custom skins like Samsung, Huawei, LG provide.
syl0n said:
Please try a stable custom rom like Omni ROM and you will understand that most people here on XDA just want good developer support. AOSP doesn't have features but it is designed well and less in your face like EMUI. And those that are here on XDA probably root it and install a custom ROM that is based on AOSP with added features without the cartoon like UI that some custom skins like Samsung, Huawei, LG provide.
Click to expand...
Click to collapse
I've personally used custom ROMs through my android history of close to 2 dozen devices. AICP, DU, AOSPA, LOS, Slim, RR, etc etc. been apart of the XDA community for close to 8 years.
I really want to support the dev community and have a passion for it. :good:
[email protected]_USA said:
Which Android skin do you like most and why?
Click to expand...
Click to collapse
I prefer pure Android itself over OEM's skins. Why? It is not only the cleanest, but it's also way smoother and i have also nothing to complain about AOSP. One example (of many out there) could be Huawei Nova which I've owned. It was way smoother with LOS 14 and also had much better battery backup. It might be featureless compared to OEM's skins, but how many of us actually use all the features implemented by OEM? I personally don't.
Sometimes simplicity is the best.
What if a future Honor device ran Android One/Go? Would that be enough to convince you buy one?
Click to expand...
Click to collapse
Only Honor ones? Anyway, yes, that'd convince me. I don't care about Android One program, but I do care about AOSP.
What if Kirin hardware was still used even with Android One?
Click to expand...
Click to collapse
No, then I wouldn't consider it. The reason I've bought Huawei Nova was because it had Qualcomm, otherwise I wouldn't have bought any Huawei. Qualcomm is popular and easier to develop for (correct me if I'm wrong). IMO, this is one of the reasons why XDA forums for Huawei are dead.
What do you like and not like about EMUI?
Click to expand...
Click to collapse
Things I like:
Lockscreen - I really like how the lockscreen looks, especially with a cool wallpaper. I'd choose this lockscreen anytime over AOSP's one as I like that's not "blurred", that I can see the wallpaper properly on a good screen. It just looks gorgeous. The widgets which can be accessed from the bottom is also nice. Would've been nicer if we could also choose own actions for that widgets.
White-blue themed - I love this man. I've always wanted this kind of theme.
Things I don't like:
Phone Manager - Man, this is just bull****. Apps are getting killed even after disabling the options in Phone Manager to not kill them. It's the most annoying thing. It's known that task killers are harmful for Android, yet that's what you're doing. Just let Android handle the things how it was meant to, it doesn't need task killers or some kind of RAM management. I also don't like the fact that battery stats is implemented in that and after removing Phone Manager, you no longer can see the battery stats, and if I remember properly, the option to block calls is also gone. That virus scanner is another ****. I mean, come on... It would have been so much better without this ****, Phone Manager. It's not only a bloatware, but it's also harmful.
Kernel - it's a mess. Just few examples: root scanner and some other protection which I don't remember right now (was related to rw system if I'm not mistaken), some configs in defconfig with "HISI" in the name are enabled on Nova which has Qualcomm. On top of this, you're providing the kernel as tarball making it hard to remove your **** for someone which is not pro, like me. I'm not the only one who said that your kernels are a mess.
Dark notification panel - Why black? Just why? Why didn't you make it white-blue themed just like the rest of the skin? It would have looked so much better. Dark one just doesn't make sense IMO when EMUI is white-themed. I'd have understood if EMUI was black themed, but it isn't.
Bloatware - removable, but still.
Privacy - I care so much about this and I doubt about it on EMUI, no matter what you would say. I haven't checked, but I'm sure that's possible to check out if there's something going on in the background. It's not like you would be the only OEM doing it though.
Screen Recorder - it's laggy and you better wouldn't have added it. I've recorded my Nova's screen when I've been on AOSPExtended even when gaming and there's no lag when I'm watching the recorded video. It was same on LOS, but I think it was slightly better on AEX. I haven't tried to record screen through terminal command on EMUI though, so I don't know if it could be better.
There were more things I like / don't like at EMUI, but right now nothing else cross my mind.
I had a list with things I like and I don't like in an app on my Nova and there were more things, but I've forgot what I've wrote there. Since it's broken, I can't access it, but I think I had a backup of that app made with Titanium Backup, so maybe I'll grab it through TWRP and restore it on my old phone to check.
I remember though that on the list I don't like was persistent notifications and seeing 0mb at apps in Developer Options > Running services, but when I've tried the last update they were actually solved (persistent notifications were really persistent and I could see the proper RAM usage at apps).
Why I won't buy Huawei anymore as of now:
I'd say that the percent is 99%.
EMUI - already listed some things I don't like and some of them are annoying af. As I've said, I have nothing to complain about AOSP, no annoying things or whatsoever.
Huawei support - this is a joke IMO. Lemme give examples. Huawei Nova came with Marshmallow (EMUI 4.1). You've updated it to EMUI 5 and even today it doesn't have a rollback update to go back to EMUI 4.1. Basically, people are stuck with EMUI 5 and obliged to accept your new changes which may not like. There's no full EMUI 4.1 firmware on Firmware Finder and the only way to go back to EMUI 4.1 is to unlock the bootloader, install TWRP and restore a backup of EMUI 4.1, only if you're lucky to get one from someone else. When I've asked Huawei support about rollback update, they've said about going to service. Well, **** that.
Second example is about the kernel source. You've uploaded EMUI 5 kernel source for a Chinese model of Huawei Nova and there was no EMUI 5 kernel source uploaded/mentioned for CAN-L11 and the other models. I've asked several times Huawei support about publishing the source for CAN-L11 and I've been told the same thing always. After a long time (couple of months), I've seen that there was a new category on their opensource website, with EMUI 5 kernel source for CAN-L11 and other models. I've downloaded it and compared it with the first EMUI 5 kernel source released which was for a Chinese version and I was surprised to see that's the ****ing same source code. Basically you've uploaded the same source after a long time and made a new category on your website where you've added the rest of the models at one source when you could mention the compatible models from the beginning or editing your website...
The kernel is a mess - already said it before...
Kirin chipsets - I've never used one and i would never use one.
XDA support - kinda all Huawei phones are dead on XDA. Some of the things listed before should be helping this.
That's pretty much all I had to say. If you're really looking into making changes, then I'll also be looking forward to those changes. I hope you're actually willing to make changes and that this thread won't be useless.
I'd really consider Huawei again if it's gonna have AOSP / Android One and Qualcomm chipset.
PS: Just noticed that there was a typo ("bloatwait" instead bloatware lol). I'm sorry if there's more typos/mistakes. I've wrote on my old phone which is a Galaxy S Advance with 4 inch screen and the keyboard is small...
I have used every single OEM based distro since the beginning of android. I have to say that out of all of them Sense was the one I liked the best. Here are my reasons why.
1. They had their own style (original Sense versions) They didn't copy anyone else. This is a big deal really. I personally am not a fan of material design. It looks very childish and unprofessional.
2. Added features that didn't bog down the UI (Hey Samsung)
3. They didn't add useless features just because everyone else did.
Now these things have changed as of late and I wouldn't use the new HTC sense (was part of their beta group at one time. They didnt listen)
With people using things like custom launchers, icon packs, themes and wallpaper apps like KLWP the over all UI of the OS really doesnt matter as its almost never seen. I mean how many times does someone really go into settings outside the first time setup? The notification shade is the major thing of the underlying OS that people see the most.
Android Go is really pointless unless you plan on lowering the specs of the honor devices. They lose functionality which is pointless if the hardware good enough for the standard version.
As for the chip. Well really that will only matter if the team puts in the time to help developers with documentation for working with the chip. This is the reason for the support of qualcomm chips. They have gone out of their way over the years helping developers with documentation and apis for working with the chips. You provide this and it will help alot.
I want to say Aosp will make you guys a Huge hit all around the globe. Especially if you bring Aosp over One flagship and one budget phone.
Personally i love emui. But market more oriented to Aosp
I'd take the Nokia approach to this matter. Since Huawei uses their AI mostly in the camera app, I'd love if there was an honor flagship running android one software and Huawei / honor camera app. Also, the background user data analysis for better battery and resource optimisations, claimed to be in EMUI 8 are being implemented in android P, so it's a win win for both the company and the customers
For those that are claiming aosp is the way to go atop and think about this. Samsung is the biggest Android oem and it is not because it get aosp. It's because of the features that touch Wiz offers that Google doesn't. Aosp really is bare bones enough that it can be compared to running Linux on a pc. It works but not as full featured or as well as something built for the hardware.
zelendel said:
For those that are claiming aosp is the way to go atop and think about this. Samsung is the biggest Android oem and it is not because it get aosp. It's because of the features that touch Wiz offers that Google doesn't. Aosp really is bare bones enough that it can be compared to running Linux on a pc. It works but not as full featured or as well as something built for the hardware.
Click to expand...
Click to collapse
Completely agree with you man, but Honor doesn't really have much hardware differentiation like Samsung has infinity displays and S pen. All other EMUI features like Knock gestures are barely used and features like app twin can be done using a third party app like parallel space. But the benefits that Android one like ROM offers, like smoother UI experience and enabling faster updates with little to no feature exclusions. So I beg to differ in my opinion that OEM skin (EMUI) offers any benefits over Aosp.
iamsabresh said:
Completely agree with you man, but Honor doesn't really have much hardware differentiation like Samsung has infinity displays and S pen. All other EMUI features like Knock gestures are barely used and features like app twin can be done using a third party app like parallel space. But the benefits that Android one like ROM offers, like smoother UI experience and enabling faster updates with little to no feature exclusions. So I beg to differ in my opinion that OEM skin (EMUI) offers any benefits over Aosp.
Click to expand...
Click to collapse
But see android one is a watered down version of android really. To be honest honor software is over all crap. I'm not sure who they ha E writing the software but they should be demoted.
zelendel said:
But see android one is a watered down version of android really. To be honest honor software is over all crap. I'm not sure who they ha E writing the software but they should be demoted.
Click to expand...
Click to collapse
I was just stating my opinion and I truly believe android one or stock android, for that matter, make a midrange phone, with lesser CPU power and RAM, perform equal to Honor / Huawei's 2017-18 flagship, the View 10 or the Mate 10 pro, running EMUI, and having better battery backup. I agree that EMUI is okayish to an extent because it is better than any other custom skins except Oxygen OS, but fragmenting the UI into region based firmware is a completely useless thing to do, considering that it slows down updates, takes more human resources to develop updates to separate regions and not to mention that they state regional feature prioritisation as the reason, but most of the basic features are common and they just add bloat like Paytm integration in Indian version and stuff like a separate Huawei app store on the international version, which is essentially useless because of all the stocks being updated either through the playstore or OTAs. Just My Opinion and I speak only for myself.
iamsabresh said:
I was just stating my opinion and I truly believe android one or stock android, for that matter, make a midrange phone, with lesser CPU power and RAM, perform equal to Honor / Huawei's 2017-18 flagship, the View 10 or the Mate 10 pro, running EMUI, and having better battery backup. I agree that EMUI is okayish to an extent because it is better than any other custom skins except Oxygen OS, but fragmenting the UI into region based firmware is a completely useless thing to do, considering that it slows down updates, takes more human resources to develop updates to separate regions and not to mention that they state regional feature prioritisation as the reason, but most of the basic features are common and they just add bloat like Paytm integration in Indian version and stuff like a separate Huawei app store on the international version, which is essentially useless because of all the stocks being updated either through the playstore or OTAs. Just My Opinion and I speak only for myself.
Click to expand...
Click to collapse
It won't make it equal to a flagship, it will just make a mid range not suck as much.
zelendel said:
It won't make it equal to a flagship, it will just make a mid range not suck as much.
Click to expand...
Click to collapse
Exactly my point. But when you take a powerful midranger like a Nokia 7+ and compare it with an honor flagship running EMUI, say a View 10, I agree that the raw power of the CPU or the SoC would make the flagship open apps much quicker and load much faster, but since we are talking about UI experiences, we must touch the issues like memory management, resource allocation, battery optimisations, etc. I'd say based on my usage that once the apps are loaded onto memory on both phones, I find switching apps and multitasking a bit smoother on the stock android (android one) and with very comparable battery sizes (3800 vs 3750 mAh), the Nokia 7+ provides a bit more extended D battery life on heavy usage. Light to moderate usage yields very much the same battery life of around 7.5 - 8 hrs SoT, but think of what honor phones with flagship specs could achieve with android one or stock android. I'd say that at this point, with very comparable hardware on almost all flagships, UI makes a lot of difference and I think EMUI, though providing a lot of features and is almost as fast as android one, I'd say the extra features added only weigh it down in terms of raw performance.
Pure Android is always better choice over other custom UIs. It is fast, smooth and lag free.
It is fine even if it doesn't have some customizations that other UIs offer.
EMUI memory management makes some apps does not work properly.
[email protected]_USA said:
Hello again everyone,
Interesting conversation I want to have with users here; which Android skin do you like most and why?
Obviously AOSP != what Pixels run.
What if a future Honor device ran Android One/Go? Would that be enough to convince you buy one? What if Kirin hardware was still used even with Android One?
What do you like and not like about EMUI?
Really want to get your all's input and feedback.
Click to expand...
Click to collapse
Problem wid skin like emui is, OEMs take longer to bring android updates. More the skin is close to stock android more easier it is to give timely updates.
Honor itself has pathetic record in rolling out updates, that's the thing i dislike about emui