Related
It's a simple question, but without a simple answer. With all of the OEMs in the Android environment, none of them have ever released a phone with vanilla Android without the direct partnership (or prodding) of Google in some way.
Most everyone agrees that the OEMs want to differentiate themselves from the competition and this is how they go about it, but why hasn't one ever released a phone without additional "features" or UI overlays? It doesn't make sense to believe Google isn't somehow leveraging their brand recognition of the Nexus line when dealing with OEMs.
Has an OEM pushed out a vanilla Android Jellybean device (or ICS) not in the Nexus line that still comes with Gapps?
Edit:
Meant for Android General, not Nexus 7 forum. Sorry :3
Android is Open Source, so yes, they can. Don't know the deal with the Market though
In addition, if OEM wants to include the Play Store and any GApps, the device needs to be certified by Google. Therefore, you see many low-end tablets do not come with Play Store or GApps and must be sideloaded.
Lenovo just moved out of their App Shop business and going back to Play Store. Also, Acer is having issues with the Aliyun (Alibaba) issue with Google
simple question, simple answer.. yes. problem is the oem's want to add their own touches, and the providers want to add their crapware.
Probably the main reason I like ASUS is they seem to make very little changes to Android, looks almost stock, and they've been doing a good job updating tablets with the latest version of Android. So I think they are the closest we have to a pure Android non-Nexus tablet.
They released the g2x with vanilla android gb but still a lot of people wanted those extras from LG's optimus 2x features like its clock and launcher.
I just started enjoying touchwhiz after a few months and now I can't use my s3 without it.
The nexus 7 seems to actually to plain in my opinion since with all the improvements over that years with android and their respective manufacturers ui like sense and touchwhiz
Sent from either Galaxy S3 intl or Nexus 7
both on stock at the moment!!
Huawei u8150
Sent from my u8800-51 using xda premium.
T-Mo's G1, G2, and G2x (sorta) are vanilla. They all have their carrier bloatware, and the G2x actually runs some of LG's custom interface framework, but still vanilla-ish.
Asus. Pure vanilla with sprinkles on top. God I hope the Padfone 2 comes to the U.S.
The original Motorola droid was pure aosp froyo and gingerbread.....no blur at all
Sent from my Nexus 7 using xda premium
Smallsmx3 said:
The original Motorola droid was pure aosp froyo and gingerbread.....no blur at all
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but with added bloatware from verizon
Everyone *****es about the skins and delays. But sometimes oems add worthwhile features too. If I were an oem I would work with some third party developers and bundle good pay apps with the phone (uninstallable of course.) like nova launcher, Camera ect. Leave most of the base os alone, making updates easier.
Sent from my Galaxy Nexus using xda premium
On the dev edition Moto X? I mean the phone is fully unlocked, isnt it? There are hardly any roms available..
Well if you bought a developer edition wouldn't you cook your own rom?
Sent from the 215
The Moto X is probably the first phone where a custom rom takes many desired features away, so why bother?
gunnyman said:
The Moto X is probably the first phone where a custom rom takes many desired features away, so why bother?
Click to expand...
Click to collapse
Agreed. Similar to the G2, other than a few tweaks here and there, building a ROM defeats a lot of the stock features. Which in my opinion like the X, are very useful.
Now, if we were taking touchwiz, ROMS are needed to get rid of a lot of the crap!!!
jmill75 said:
Agreed. Similar to the G2, other than a few tweaks here and there, building a ROM defeats a lot of the stock features. Which in my opinion like the X, are very useful.
Now, if we were taking touchwiz, ROMS are needed to get rid of a lot of the crap!!!
Click to expand...
Click to collapse
G2? That has a lot of LG crap similar to touchwiz. You definitely need a aosp ROM for G2. For Moto X sure, it's stock android plus useful features not like the useless LG and Samsung gimmicks.
Sent from my XT1053 using Tapatalk
gunnyman said:
The Moto X is probably the first phone where a custom rom takes many desired features away, so why bother?
Click to expand...
Click to collapse
People could add the features on top of the current features.
For instance, it'd be nice to be able to modify quick setting tiles, center clock, etc. Xposed will hopefully give us those options though.
Sent from my Nexus 5
kirdroid said:
G2? That has a lot of LG crap similar to touchwiz. You definitely need a aosp ROM for G2. For Moto X sure, it's stock android plus useful features not like the useless LG and Samsung gimmicks.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
The S4 has a lot of useless gimmicky features. LG implements just enough useful features to not make it over the top like touchwiz. I definitely prefer the Moto X over those two but I just needed to stand up for the G2 which was a great device. The G2 was plenty fast and it didn't need AOSP.
phositadc said:
People could add the features on top of the current features.
For instance, it'd be nice to be able to modify quick setting tiles, center clock, etc. Xposed will hopefully give us those options though.
Sent from my Nexus 5
Click to expand...
Click to collapse
If you use GravityBox you can tweak tiles, clock, battery and much more.
bootloaders locked on ATT and Verizon probably don't help. I wonder what % of X's were sold through them.
I'll also agree with the fact that we'd give up some features with standard ROMS like AOSP, slimbean, PA, etc.
Island_King said:
If you use GravityBox you can tweak tiles, clock, battery and much more.
Click to expand...
Click to collapse
Is this working on 4.4 yet?
Dburgessme2 said:
Is this working on 4.4 yet?
Click to expand...
Click to collapse
Article in the Portal said Xposed is now working on 4.4, with most Apps
Sent from my HTC One using XDA Premium 4 mobile app
Dburgessme2 said:
Is this working on 4.4 yet?
Click to expand...
Click to collapse
The change log said that GB was experimental on 4.4 but I just tried to use it and it wouldn't load. My bad.
---------- Post added at 12:22 PM ---------- Previous post was at 12:15 PM ----------
qbanlinxx said:
Article in the Portal said Xposed is now working on 4.4, with most Apps
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The Xposed framework does work on 4.4 however many of the popular modules such as GravityBox and MotoXposed are currently not working/supported. It's also worth mentioning that Xposed Framework does not work with ART.
Island_King said:
The Xposed framework does work on 4.4 however many of the popular modules GravityBox and MotoXposed are currently not working/supported. It's also worth mentioning that Xposed Framework does not work with ART.
Click to expand...
Click to collapse
And take out all the fun of reading the article for everyone, Never!!
Sent from my HTC One using XDA Premium 4 mobile app
SupaSwag said:
The S4 has a lot of useless gimmicky features. LG implements just enough useful features to not make it over the top like touchwiz. I definitely prefer the Moto X over those two but I just needed to stand up for the G2 which was a great device. The G2 was plenty fast and it didn't need AOSP.
Click to expand...
Click to collapse
We shouldn't be standing up for any OEMs who crap android and make it harder to update
Why did the moto X get updated so fast? It's essentially stock android with value added features on top of it. G2 is fast? Sure it's running the latest awesome soc but over time without updates it'll be left out to die a painful death.
ASOP out for N4 and others on Moto G is trying it out or talking about it. Maybe we can too just to see. Whose knows what files lie within we can pick apart and build something. Just for fun its not a full platform
Anyone know how I can get the dialer from L?
Sent from my Nexus 7 using Tapatalk
Pick apart the files in developer preview
Lol this is impossible with a locked bootloader. Even with an unlocked bootloader, this is difficult due to lack of binaries and source for the MotoX.
No luck on dialer apks. They don't install. "Problem Parsing Package"
We will just have to wait..
abuttino said:
No luck on dialer apks. They don't install. "Problem Parsing Package"
We will just have to wait..
Click to expand...
Click to collapse
Why don't you just load the google dialer from 4.4.3 or 4.4.4?
Sent from my XT1058 using XDA Free mobile app
Because there has been no real success of using that as a primary dialer.. No history, no caller-id
Even if u manage to install the dialer you won't get the material design as the framework does not support it... Moreover the apps have a fallback UI so they will look like the KitKat version
Not worth it. A lot of work to port over just a preview OS.
I perfectly understand..
Just thought I might mention it for anyone who has too much time on their hands with more experience.
I feel like the moto x wont get android l till around next month or later. Motorola, HTC, and all the other companies dropped the 5.0 Source code so it probably wont be insanely difficult to port it to the moto x. Just gotta get some skilled devs down here so they can help us out. If anyone is willing to try to port L (5.0) to the 4.4.4 bootloader I'd be more than happy to test out whatever needs to be tested.
Hi. I'm thinking of getting a Nexus 6. One thing I'm curious is how are people coping with not have Xposed modules. Are you depending on custom roms and themes to make up the difference? Currently on my Note Edge I use App Settings, Heads Up Notifications, Multiwindow plus. Notifly Clean, Swipeback and YouTube Adaway among others. For example App Settings really comes in handy for changing look of apps and such (can give more of a tablet UI). I'd especially like to hear from folks that heavily used Xposed in the past to get their impressions. Anyways, I might get a N6 or wait a bit more to see what comes out at CES. Thanks!
mscion said:
Hi. I'm thinking of getting a Nexus 6. One thing I'm curious is how are people coping with not have Xposed modules. Are you depending on custom roms and themes to make up the difference? Currently on my Note Edge I use App Settings, Heads Up Notifications, Multiwindow plus. Notifly Clean, Swipeback and YouTube Adaway among others. For example App Settings really comes in handy for changing look of apps and such (can give more of a tablet UI). I'd especially like to hear from folks that heavily used Xposed in the past to get their impressions. Anyways, I might get a N6 or wait a bit more to see what comes out at CES. Thanks!
Click to expand...
Click to collapse
I have adaway on my Nexus 6 and it works great. It's part of the LS ROM. The Nexus 6 is fine without xposed even after using it heavily on all of my other phones. If you want a tablet UI then you can change the DPI on your phone to 320 (560 is stock) and most people seen to like 460-480dpi. It's well worth the upgrade if you love to flash. Anything from CES (LG, ASUS, Samsung etc..) Won't have nearly as much development if any compared to a Nexus device. I like to flash ROM's and kernels so rather than deal with the hassle of unbricking a LG or Samsung with factory tools I can flash the stock ROM via fastbokt with my nexus easily. It's all up to what you plan to use the phone for. Any new phone debuting this year won't have xposed anyway because they will have lollipop
Your problem is not the Nexus 6, your problem is with Lollipop. Due time, Xposed will be made to work with ART.
Regardless of whatever phone you're using, if it has Lollipop, Xposed will not work.
Pilz said:
I have adaway on my Nexus 6 and it works great. It's part of the LS ROM. The Nexus 6 is fine without xposed even after using it heavily on all of my other phones. If you want a tablet UI then you can change the DPI on your phone to 320 (560 is stock) and most people seen to like 460-480dpi. It's well worth the upgrade if you love to flash. Anything from CES (LG, ASUS, Samsung etc..) Won't have nearly as much development if any compared to a Nexus device. I like to flash ROM's and kernels so rather than deal with the hassle of unbricking a LG or Samsung with factory tools I can flash the stock ROM via fastbokt with my nexus easily. It's all up to what you plan to use the phone for. Any new phone debuting this year won't have xposed anyway because they will have lollipop
Click to expand...
Click to collapse
zephiK said:
Your problem is not the Nexus 6, your problem is with Lollipop. Due time, Xposed will be made to work with ART.
Regardless of whatever phone you're using, if it has Lollipop, Xposed will not work.
Click to expand...
Click to collapse
Thanks for your replys. I was wondering if folks could change dpi on apps individually instead of globally.
Clearly lollipop is inevitable. I've tried a recently released developers version of lollipop on my former dd (Note 3) and it has some nice features plus some Note 4 multiwindow improvements. But I also missed my Xposed mods when using it. The main problem I'm having with the EDGE is that I'm not sure how much development will continune on it. Currently there are two very nice roms (I'm refering to tmobile here variant) but no custom kernels. So I guess I'm suffering from developer envy lol... CES should be interesting in that more devices should be introduced with 64 bit processors along with, perhaps some of the larger screen sony devices. At lest that is the hope!
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
H4X0R46 said:
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
Click to expand...
Click to collapse
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). Or if the dev is particularly dedicated then they might use an AOSP base because they want to keep up with all the bleeding edge enhancements to android which may or may not have any real benefit. When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
StykerB said:
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
Click to expand...
Click to collapse
So all in all, Cataclysm is using stock Android and not AOSP, but done in a way that there are no legal issues? So in essence, flashing the system.img file from the dev site and adding Cataclysm mod to it is the the exact same difference as using the full Cataclysm installer? No AOSP added?
StykerB said:
.... "rock solid stability" that Google's team of software engineers created
Click to expand...
Click to collapse
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
NLBeev said:
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
Click to expand...
Click to collapse
Yes but would you rather not have something solid for people to build on? some of those things aren't even about stability... like the full resolution thing? assuming you're referring to onscreen buttons, and DPI is always on every device set in multiples of 80 for app standardization reasons. The overlay code for layers wasn't intended to be used for theming. Hence why google only used it for stuff like the ATT boot animation. and Google's apps and OS are separate and shouldn't be expected to adhere to a modding community's theme engine that they don't support. And dark themes were probably a design decision rather than actual stability issue.
StykerB said:
.....some of those things aren't even about stability... like the full resolution thing?....
Click to expand...
Click to collapse
You're right my list is not about stability only.
Using the N6 now for more than a year. I've seen a beta version with a dark theme, but it was removed. Why? Stability issues ?
To make the N6 acceptable for my daily use, especially battery life and readability, I had to change a lot of things. That has consequences for the stability. The N6 is still stable but I wouldn't say rock stable.
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
H4X0R46 said:
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
Click to expand...
Click to collapse
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
zelendel said:
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
Click to expand...
Click to collapse
Thanks! I was never sure just how much stuff is taken out of AOSP, but it's just small differences then. Glad I know that now! And hey, since we're on the subject, how are gapps legal? Aren't gapps those closed source bits that google DOES omit from AOSP? Play store and background things? Like, I know there's some legal thing where gapps shouldn't be preinstalled in an AOSP rom, but what's the grey area with gapps? Thanks again for the detailed description! Learning these things is good lol
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
zelendel said:
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
Click to expand...
Click to collapse
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
H4X0R46 said:
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
Click to expand...
Click to collapse
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
zelendel said:
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
Click to expand...
Click to collapse
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
H4X0R46 said:
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
Click to expand...
Click to collapse
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
zelendel said:
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
Click to expand...
Click to collapse
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
H4X0R46 said:
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
Click to expand...
Click to collapse
To be honest I never noticed. I don't use any of the stock sounds.
H4X0R46 said:
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Click to expand...
Click to collapse
I dont think the Nexus line will see many issues other then root becoming harder to get.
Some Samsung devices cant be rooted. Like my buddy that is a samsung fan has a note 4, note 5 and a few Galaxy s5 in his house and all of them are locked down.
More and more people are too worried about things like warranty to even bother really. I even waited on updating the n6 until root was gotten for it.
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
HipKat said:
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
Click to expand...
Click to collapse
Nope no root for the note 5. Only some can be. The tmobile version doesn't lock the bootloader but the rest do.
As tripping Knox is not an option for many as it voids their warranty but flashing roms does that anyway.