Related
I have with all three OSs but somehow iOS and WP7 feel much more stable. They never crashed yet, iOS can't even crash I think, while Andoid crashed many times. It it because of the linux based kernel?
Your question doesn't really make sense. Android is not unstable. It just depends on your rom and hardware capabilities. If they are good, your device will be fine, if not, then of course it's not going to be the smoothest thing in the world. So blame your device (even if it's a good device, you still need to make the best out of it), not Android.
Run the latest iOS on the original iPhone. Tell me its stable
ugothakd said:
Run the latest iOS on the original iPhone. Tell me its stable
Click to expand...
Click to collapse
Classic .
Android seems pretty stable to me, I've never had any crashes on my SGS2, I've had a couple force closes but I'd imagine that's down to apps being bad rather than the actual OS.
This sounds like it was started as a troll thread by the OP to me
Given the right conditions, any piece of software can crash and do so hard
http://cdn2.iphone4jailbreak.org/forum/wp-content/uploads/mobile-substrate-crash-iphone-4.jpg
http://gradly.net/wp-content/uploads/2011/02/20110215_ibook_crash.png
iOS is a very modified verison of unix/bsd (well unix serves somewhere under it as the base), which is what linux is modeled after. Take that as what you will.
Neither iOS or wp7 allow users the chance to screw up your phone nearly as much as android does as well (well unless you have one of those android phones with a locked bootloader).
Another thing you need to take into account is the hardware restrictions used by WP7 and IOS. With WP7 you have to meet the minimum requirements set by Microsoft. IOS hardware is only built and created by Apple and each model is now only being supported for so many years before they won't allow it to be updated to the most recent IOS version.
With Android, you have multiple manufacturers creating a variety of devices where there is almost no hardware restrictions except whether the phone will run the ROM or not. Android phone hardware can vary by huge amounts of memory, CPU speeds, and GPUs.
if there are problems it has to do with the manufacturer of the phone and the rom they developed, not android. Get a nexus phone, stable, fast, smooth, and it has the vanilla version of android. After I removed all the bloatware off my phone and installed cm7, my captivates been a different phone. Makes me remember why I went with android over IOS or wp7.
Everyone seems eager to fork over their hard earn money to be Google's beta tester. But I'm more surprised at how people take pride in how "stable" android is, while they have to hack the beck out of it for it to be a decent phone.
otnos said:
Everyone seems eager to fork over their hard earn money to be Google's beta tester. But I'm more surprised at how people take pride in how "stable" android is, while they have to hack the beck out of it for it to be a decent phone.
Click to expand...
Click to collapse
Look at the nexus line, Pure Vanilla android. I don't hear too many crashes from the stock users.(if any at all)
otnos said:
Everyone seems eager to fork over their hard earn money to be Google's beta tester. But I'm more surprised at how people take pride in how "stable" android is, while they have to hack the beck out of it for it to be a decent phone.
Click to expand...
Click to collapse
Did you expect everyone to say android sucks on an android subforum? I think you would want to head to the apple subforum if you want to hear that.
People use android because it works for them. However, it may not work for everyone and those that it does not, are more than welcome to use a different phone
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?
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
https://www.dropbox.com/s/bgce2efur8tq1ot/Screenshot_2017-05-13-17-13-44.png?dl=0 She said it was not compatible yet it got the wifi alliance http://www.wi-fi.org/content/search-page?keys=SM-A310F :confused: I think it's true because only the a5 2016 and a7 2016 got it but the a3 2016 hasn't?:crying:
Based on the existence of the certificate the update exists and is/was already under testing.
The only possible reason not to release it if they f*cked up the optimization of touchwiz for nougat like they did before a few times, resulting in failure to release updates to below flagship devices (like S4 mini).
The A36 is marketed as an ultra mid range device, so if it happens again despite their promises they could probably say goodbye to mid range buyers for once.
Let me explain: power users know Android. They (we) know that with every major update it's more and more optimized and less demanding on hardware, but Samsung seems to have a trouble following that trend with tw. They almost do the opposite, while people demand updates, and it's also in the interest of Google, so they have already warned manufacturers to do their best on the matter, specially Samsung after their past neglections. This topic has a great influence on our preferences and despite the other fields Samsung devices excelling in our eyes, it could change the situation. Now, most simple users choose devices based on our opinions. They ask us for advices. If I prefer Samsung devices, 100-150 people around me will prefer Samsung too based on my opinion; but if I prefer another brand instead, they will buy their devices instead. Now imagine how the numbers come with a lot more power users exisiting in the world, not just me.
The nougat update for A36 (having the broadest market amongst other A and J series devices thanks to it's handy size, yet powerful hw and quality housing) is a big opportunity to show us they have changed their attitude towards mid-range users, something people and Google are waiting for a long time, so they know it would be a disaster for them to back out from it in the final moments. I hope they won't.
I hope they release it but it explains why a7 and a5 2016 got nougat before the a3
link is broken
...if I get Nougat on my A3 2016...I won't ever enter this forum again.
Spreading negative information like this by pointing broken links as source is 3rd grade child stupidity.
It's not my fault if it doesn't work I saw it myself
Anyway if you want the link it's here https://www.dropbox.com/s/p9w3d54sk2fvguj/Screenshot_2017-05-18-18-20-37.png?dl=0. Next time don't swear at me.
arif8912 said:
Anyway if you want the link it's here https://www.dropbox.com/s/p9w3d54sk2fvguj/Screenshot_2017-05-18-18-20-37.png?dl=0. Next time don't swear at me.
Click to expand...
Click to collapse
These support guys don't know what they are saying... "I'm afraid it's not compatible" => there is no such thing. If they make a compatible build than it is compatible, simple as that. Also, when I've asked them, I got the response that IT IS GOOGLE WHO MAKES THE UPDATES, THEN THE CARRIERS REVIEW IT AND RELEASE IT. Yes, this is how it should be ideally if there would be a flexible hardware abstraction layer, but sadly it is Samsung who has to build the update after Google releases the source, and before carriers can deploy it... When I had to rate the conversation I wrote them that their support department has no access to proper information even about HOW updates work which is very troubling for conscious users who chose Samsung because of Android (+their quality hardware) and expect them to properly provide updates for their ultra mid range devices too, not just for their overpriced flagships.
http://www.samsung.com/tr/support/newsalert/100061 A3 2016 update got delayed to 29th may-2nd june
I'd like to get to as close to vanilla as possible. Not a fan of Samsung's ui or bloat. I'm coming from the tab s1 which had some pretty good roms. There are none for this device and it's almost 6 months old. I would make one myself but lack the necessary skills
Most of the newer top end Samsung Tablets get very little developer support since they cost so much. Happens with every new tablet having people asking where the developer support is for it. Samsung newer UI much nicer and any vanilla roms would take away most of the functionality that makes the tablets great. Apparently the S5e has some dev support.
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Markeee said:
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Click to expand...
Click to collapse
Not everyone gets the update at the same time (don't know how they handle when and who should receive the update). I only got a November update a few days ago (though some claimed to have already gotten it) and it offered few improvements. The tablet still feels the same as usual.
As one must choose between custom ROMs and Knox (especially warranty), I'm currently at a loss myself, and for the time being I haven't heard of anyone trying (or succeeded in) booting a GSI on S7/S7+ probably because of this, although it's theoretically possible (again thanks to Treble). At least we now have TWRP... it might be better if one day custom kernels become available.
So far this is the only tablet I know that can offer 120Hz display. My current phone (Razer Phone 2 which is also 120Hz-capable) still doesn't have a specialized ROM but I can already run GSIs on it with adequate performance. For new devices, going for GSI might be easier, but performance-wise it still has a way to go compared to specialized ROMs.
Think it has to do with the fact that snapdragon is locked on samsung