Dev friendliest phone - Nexus 5 Q&A, Help & Troubleshooting

So until now the N5 is the Dev friendliest phone ATM. Do you think it will lose that position when the one plus one is released? Do you think its worth switching to it when it comes out? Sorry if this is the wrong category or this post is stupid, I will gladly delete it if its not needed
Sent from my Nexus 5 using XDA Premium 4 mobile app

Radixtrator said:
So until now the N5 is the Dev friendliest phone ATM. Do you think it will lose that position when the one plus one is released? Do you think its worth switching to it when it comes out? Sorry if this is the wrong category or this post is stupid, I will gladly delete it if its not needed
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
any latest nexus will always be the dev friendliest phone. the one plus isnt an aosp phone.

I never really got the difference, the makers of the one plus said it will run cm with ability to install stock android. Doesn't that mean its aosp?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Radixtrator said:
I never really got the difference, the makers of the one plus said it will run cm with ability to install stock android. Doesn't that mean its aosp?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well AOSP and CM are different. That's why when you look at ROMs you see AOSP based and CM based mainly and same with kernels. CM actually has its own kernels now and can't run AOSP kernels.
Sent from my Nexus 5 using Tapatalk

Radixtrator said:
I never really got the difference, the makers of the one plus said it will run cm with ability to install stock android. Doesn't that mean its aosp?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what is the difference between Android and CyanogenMod?
About 1-2 times a year, the vanilla Android operating system (known as AOSP, or the Android Open Source Project) is internally developed, then released to the public, by Google. They provide the source code to anyone who wants to download it. The CyanogenMod community, comprised mostly of unpaid volunteers and enthusiasts from around the world, takes this newest Android code and "ports" it to dozens of new and older (aka "legacy") devices. At the same time, other CyanogenMod developers start adding features, fixes, and improvements that Google didn't include to the CyanogenMod code, which benefits all the devices. The CyanogenMod community has a whole infrastructure for people to build and test experimental versions, report bugs, and contribute back to the source code.
Sometimes features that started in CyanogenMod have appeared in newer version of "official" Android. And every time Android does a new "code dump" of their latest version, CyanogenMod benefits from Google's changes.
In this way, CyanogenMod is one (but not the only) community distribution of what started as vanilla AOSP. The Android community is vibrant, with numerous "modders" and "themers" and "performance enhancers" taking the source code and doing incredible things to it. Generally, there is a spirit of sharing knowledge and empowering people to experiment with controlling their devices, often giving old phones new life, and hopefully having fun in the process.
Source: http://wiki.cyanogenmod.org/w/About

Radixtrator said:
I never really got the difference, the makers of the one plus said it will run cm with ability to install stock android. Doesn't that mean its aosp?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ability to install stock android isnt the same as having everything made specifically for your phone(drivers and all). many phones can run aosp, after they have drivers hacked or added later. that doesnt mean that they are aosp phones. the drivers that come from aosp are made specifically for a nexus and cant be run on other hardware.
---------- Post added at 03:40 PM ---------- Previous post was at 03:31 PM ----------
mistahseller said:
So what is the difference between Android and CyanogenMod?
About 1-2 times a year, the vanilla Android operating system (known as AOSP, or the Android Open Source Project) is internally developed, then released to the public, by Google. They provide the source code to anyone who wants to download it. The CyanogenMod community, comprised mostly of unpaid volunteers and enthusiasts from around the world, takes this newest Android code and "ports" it to dozens of new and older (aka "legacy") devices. At the same time, other CyanogenMod developers start adding features, fixes, and improvements that Google didn't include to the CyanogenMod code, which benefits all the devices. The CyanogenMod community has a whole infrastructure for people to build and test experimental versions, report bugs, and contribute back to the source code.
Sometimes features that started in CyanogenMod have appeared in newer version of "official" Android. And every time Android does a new "code dump" of their latest version, CyanogenMod benefits from Google's changes.
In this way, CyanogenMod is one (but not the only) community distribution of what started as vanilla AOSP. The Android community is vibrant, with numerous "modders" and "themers" and "performance enhancers" taking the source code and doing incredible things to it. Generally, there is a spirit of sharing knowledge and empowering people to experiment with controlling their devices, often giving old phones new life, and hopefully having fun in the process.
Source: http://wiki.cyanogenmod.org/w/About
Click to expand...
Click to collapse
aosp is constantly getting developed, not twice, three, or four times a year. there is code constantly being added. some of that code also makes it to future android os updates. and bug fixes make it into aosp way before they get released for android os. cm has nothing at all to do with aosp. sure, some of their code makes it into aosp, so does some code of our developers here on xda that have nothing to with cm. cm is just a custom rom, nothing more. a custom rom that somewhat became a little larger because some manufacturers are using it on their devices. its a custom rom, just as rastakat is, just as purity is, etc.

The moto x has a dev version, made by a Google owned company, and it has many flashing limitations that the Nexus line does not have.
That's only an example, but no, I don't think any dev edition phone will ever have the development a nexus phone has, or the limitless possibilities a nexus has. Like bootloader complications, like the moto x DE has.
Sent from my cell phone telephone....

kj2112 said:
The moto x has a dev version, made by a Google owned company, and it has many flashing limitations that the Nexus line does not have.
That's only an example, but no, I don't think any dev edition phone will ever have the development a nexus phone has, or the limitless possibilities a nexus has. Like bootloader complications, like the moto x DE has.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
motorola is now own by lenovo
http://www.engadget.com/2014/01/29/lenovo-nearing-3-billion-deal-for-motorola/

So in only dev terms speaking, for people that love flashing everything possible, nothing beats a nexus not even the "superphone" oneplusone?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Radixtrator said:
So in only dev terms speaking, for people that love flashing everything possible, nothing beats a nexus not even the "superphone" oneplusone?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so in terms of devs or people that love flashing everything possible? those are 2 very different things. developers not only work on rom or kernel code, they also create apps, games, and other things for us to use. if all you want is a phone to flash on, you can use any phone(nexus for ease since its bootloader is unlockable). the one plus might come with an unlockable bootloader for ease of flashing, but that ease of flashing doesnt make it a developer phone.

No what i meant was, there should normally be More content avaible for nexus devices as its easier for devs to make them correct?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Radixtrator said:
No what i meant was, there should normally be More content avaible for nexus devices as its easier for devs to make them correct?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes. but there is more "hacking" going on with other devices, since much of the code is availble for the nexus 5 right away but needs to be hacked to work with other devices.

Zepius said:
motorola is now own by lenovo
http://www.engadget.com/2014/01/29/lenovo-nearing-3-billion-deal-for-motorola/
Click to expand...
Click to collapse
Yes, but Google was in charge when the Moto x's were made, and they really limited them, even the dev models.
Sent from my cell phone telephone....

simms22 said:
yes. but there is more "hacking" going on with other devices, since much of the code is availble for the nexus 5 right away but needs to be hacked to work with other devices.
Click to expand...
Click to collapse
OK that's what I thought.. God I'm so torn between opo and my n5.. But I love the n5 and its community so I guess I'll stick with it.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Related

CM7 compatible?

Any chance of running a vanilla version of gingerbread?
r_3 said:
Any chance of running a vanilla version of gingerbread?
Click to expand...
Click to collapse
Once HTC releases the kernel source code for the Inspire, then the work on a CM 7 compatible kernel can begin.
If you want to play around with it, you can install the DHD version. It runs quite well besides having no audio. The source code is needed to build a kernel that supports the inspires audio.
tpbklake said:
Once HTC releases the kernel source code for the Inspire, then the work on a CM 7 compatible kernel can begin.
Click to expand...
Click to collapse
How long after releasing a device is the manufacturer supposed to release the source code? I'm not too familiar with the whole open source thing
HTC is quite good about it. Usually a couple of weeks or so.
JaysFreaky said:
HTC is quite good about it. Usually a couple of weeks or so.
Click to expand...
Click to collapse
Ahh cool, hopefully sooner than later xD I haven't had any Cyanogen love since my Nexus One
r34p3rex said:
Ahh cool, hopefully sooner than later xD I haven't had any Cyanogen love since my Nexus One
Click to expand...
Click to collapse
Yeah I hear you. I've never had a device that was really supported (loaded it on my Streak, but next to nothing worked). I've always flashed my friends devices with it and I'm quite jealous. lol
Good news is that they plan to support it. If you go to their forums they've added the Inspire to the Desire HD.
This is great news I have also installed a ton of cm7 on all of my buddies phones and can't wait to actually run it myself.
Sent from my Desire HD using XDA App
tpbklake said:
Once HTC releases the kernel source code for the Inspire, then the work on a CM 7 compatible kernel can begin.
Click to expand...
Click to collapse
What is it that htc does or doesn't do that makes so many of its phones compatible with cm? Or does the cm crew simply prefer to support htc phones compared to others?
peachpuff said:
What is it that htc does or doesn't do that makes so many of its phones compatible with cm? Or does the cm crew simply prefer to support htc phones compared to others?
Click to expand...
Click to collapse
well, for starters, they use the standard mtd partition layout (unlike Samsung who uses bml) which means the "fastboot" commands can work. on top of that, their devices are also usually extraordinarily similar between generations which leads to most of the exploits and such working on multiple phones. so you have a LARGE number of devices being worked on by a LARGE number of developers with extreme similarities. this leads to a lot of tools working on multiple devices (the Inspire is actually a good example of this, seeing as how it's basically a Desire HD... it's even got the Ace codename--same as the Desire HD) which makes the rapid pace of development understandable.
Add to the fact that htc and tmobile (who had the first android phone which also happened to be htc) both encourage this "hobbyist" attitude from the developer community on non-dev phones (all dev phones were htc until the Neuxs S... G1/ADP, Magic/Ion, Nexus One... and they are almost entirely open source from my understanding) to both encourage people to buy their phones and also to ENJOY their phones. HTC provides software they consider to be the best "overall user experience" and I think that means they provide android (usually with Sense UI) so that it will appeal to the widest range of people. But then there are people who want that vanilla UI without buying the dev phone (such as myself and possibly you) and I'm betting htc doesn't want to actively discourage people having this option because it means improved sales from the hobbyist community. Now I have no inside info, but I'm sure the only exploits and such that they patch are security vulnerabilities (which are the ones exploited to get root). htc even fixed cyanogen's personal Nexus One due to a faulty power button even though his "hackery" voids the warranty. Tmobile provided/collaborated with cyanogenmod with the theme-ing engine for CM7. This history of collaboration between google, htc, tmobile, and the developer community has led to strong ties and familiarity with the platform.
tl;dr:
tmobile likes having the developers on their service because it means more subscribers; htc likely wants to appeal to both the average consumer and the developers so offers an out of the box experience that most can enjoy (Sense) but doesn't actively try to discourage developers.
Kaik541 said:
well, for starters, they use the standard mtd partition layout (unlike Samsung who uses bml) which means the "fastboot" commands can work. on top of that, their devices are also usually extraordinarily similar between generations which leads to most of the exploits and such working on multiple phones. so you have a LARGE number of devices being worked on by a LARGE number of developers with extreme similarities. this leads to a lot of tools working on multiple devices (the Inspire is actually a good example of this, seeing as how it's basically a Desire HD... it's even got the Ace codename--same as the Desire HD) which makes the rapid pace of development understandable.
Add to the fact that htc and tmobile (who had the first android phone which also happened to be htc) both encourage this "hobbyist" attitude from the developer community on non-dev phones (all dev phones were htc until the Neuxs S... G1/ADP, Magic/Ion, Nexus One... and they are almost entirely open source from my understanding) to both encourage people to buy their phones and also to ENJOY their phones. HTC provides software they consider to be the best "overall user experience" and I think that means they provide android (usually with Sense UI) so that it will appeal to the widest range of people. But then there are people who want that vanilla UI without buying the dev phone (such as myself and possibly you) and I'm betting htc doesn't want to actively discourage people having this option because it means improved sales from the hobbyist community. Now I have no inside info, but I'm sure the only exploits and such that they patch are security vulnerabilities (which are the ones exploited to get root). htc even fixed cyanogen's personal Nexus One due to a faulty power button even though his "hackery" voids the warranty. Tmobile provided/collaborated with cyanogenmod with the theme-ing engine for CM7. This history of collaboration between google, htc, tmobile, and the developer community has led to strong ties and familiarity with the platform.
tl;dr:
tmobile likes having the developers on their service because it means more subscribers; htc likely wants to appeal to both the average consumer and the developers so offers an out of the box experience that most can enjoy (Sense) but doesn't actively try to discourage developers.
Click to expand...
Click to collapse
And this is why HTC is full of win
If only the Inspire had a front facing camera, it'd be perfect.
r34p3rex said:
And this is why HTC is full of win
If only the Inspire had a front facing camera, it'd be perfect.
Click to expand...
Click to collapse
I agree! I have heard on XDA that there should be an HTC Android device on At&t later this year with the front facing camera and all that.
Sent from my Desire HD using XDA App
mentalcase said:
If you want to play around with it, you can install the DHD version. It runs quite well besides having no audio. The source code is needed to build a kernel that supports the inspires audio.
Click to expand...
Click to collapse
Can we install CM7 then install our original radio to get sound back?
kirbo20 said:
Can we install CM7 then install our original radio to get sound back?
Click to expand...
Click to collapse
Sounds more like a kernal issue.
kirbo20 said:
Can we install CM7 then install our original radio to get sound back?
Click to expand...
Click to collapse
No. It's the kernel...not the radio.
Sent from my Desire HD using XDA App
I have never tried out CM at all so I will deffinately check it out once it is available for the Inspire
Just tried out CM7, no audio as expected. Someone needs to figure out what makes the Inspire kernel different from the standard Desire HD kernel, then port it to the CM7 kernel xD
r34p3rex said:
Just tried out CM7, no audio as expected. Someone needs to figure out what makes the Inspire kernel different from the standard Desire HD kernel, then port it to the CM7 kernel xD
Click to expand...
Click to collapse
You need the source first.
Sent from my Captivate.
From what I understand CM7 RC1 was released for the Desire HD last night so all we should need is an appropriate kernel to flash over that. I also read some people were able to get sound from a TELUS kernel for that device. Can anyone confirm that?
Sent from my Inspire 4G using XDA App
rootdude said:
From what I understand CM7 RC1 was released for the Desire HD last night so all we should need is an appropriate kernel to flash over that. I also read some people were able to get sound from a TELUS kernel for that device. Can anyone confirm that?
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Seems any dhd Rom will work. If cm7 was ported then it should work like any other Rom with the TELUS.
Inspire (rooted)
Leedroid v2.0.0
TELUS kernel

source code released for up coming 9505g google edition

will we see an official rom soon 2 for us 9505 users
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-I9505G
I don't think that helps us one bit. Hope I'm proven wrong, though.
Nice ty.:angel:
I wonder what Ill get first Wednesday. Windows 8.1 preview or stock Android 4.2.2 for I9505 =]
Aerys said:
Nice ty.:angel:
I wonder what Ill get first Wednesday. Windows 8.1 preview or stock Android 4.2.2 for I9505 =]
Click to expand...
Click to collapse
Do you even have to ask that? Android, of course! :victory:
any leaks yet team..
SALAH100 said:
any leaks yet team..
Click to expand...
Click to collapse
My friend, wait 1 day and we probably have official rom
How to use the code?
John Chu said:
How to use the code?
Click to expand...
Click to collapse
Dial *#THE CODE# and your phone will change to GT-I9505G
DjeMBeY said:
Dial *#THE CODE# and your phone will change to GT-I9505G
Click to expand...
Click to collapse
Careful now, he might actually believe it.
I am still trying to figure out the logic of wanting the stock AOSP for the S4 from Samsung.
How will this be any different from running any other AOSP rom? I mean, if you check out PA GamerZ ROM, that works quite well as a daily driver. Why would we want to use this stock AOSP (with features that are quite basic)? Just to get 4.3 when it comes out? So? Some dev will port that anyways.
I mean, if someone bought the S4, wasn't it for the features? If anyone wanted stock AOSP then why not Nexus 4? Ok if hardware is the question, then really waiting for the next Nexus isn't that hard.
So can someone explain to me why?
kingzain900 said:
I am still trying to figure out the logic of wanting the stock AOSP for the S4 from Samsung.
How will this be any different from running any other AOSP rom? I mean, if you check out PA GamerZ ROM, that works quite well as a daily driver. Why would we want to use this stock AOSP (with features that are quite basic)? Just to get 4.3 when it comes out? So? Some dev will port that anyways.
I mean, if someone bought the S4, wasn't it for the features? If anyone wanted stock AOSP then why not Nexus 4? Ok if hardware is the question, then really waiting for the next Nexus isn't that hard.
So can someone explain to me why?
Click to expand...
Click to collapse
For someone like me, it's not about running the stock AOSP on S4. It's about how it can improve the AOSP based custom roms like CM, PA, etc.
Hopefully, Samsung/Google will release proper source codes as quickly as for Nexus devices so that custom roms can run better on S4.
I've been using GS3 (i9305), mainly with CM for the last 10 months or so. It works ok as a daily driver, but not as well as it could've been, mainly because not all the necessary sources are available/released.
I tried Nexus 4 for about a couple of weeks and running CM was definately more fluid/enjoyable than on GS3.
But I couldn't really get used to not having the physical home button and lack of storage space. If GS4 Google Edition is released with exact same hardward as normal i9505, then this will be almost perfect - custom roms running as well as on Nexus devices with physical home button and MicroSD slot.
kingzain900 said:
I am still trying to figure out the logic of wanting the stock AOSP for the S4 from Samsung.
How will this be any different from running any other AOSP rom? I mean, if you check out PA GamerZ ROM, that works quite well as a daily driver. Why would we want to use this stock AOSP (with features that are quite basic)? Just to get 4.3 when it comes out? So? Some dev will port that anyways.
I mean, if someone bought the S4, wasn't it for the features? If anyone wanted stock AOSP then why not Nexus 4? Ok if hardware is the question, then really waiting for the next Nexus isn't that hard.
So can someone explain to me why?
Click to expand...
Click to collapse
In simple terms.
Google gets to have its vanilla version of Android on a flagship device without having to subsidize the cost of designing the hardware.
Unlike Nexus devices where Google invests R&D money to make the hardware... having Samsung and HTC put a version of Stock Android on the device pretty much absolves Google of any financial liability in relation to hardware development.
Nexus devices are traditionally spartan... and Google likes it that way... but what if mobile manufacturers want to have nexus compatible device with all the bells and whistles... they will all compete on who has the most Nexus compatible device.
This will attract developers and customers that prefer the stock Google experience
Bear in mind also Google is still developing their Motorola flagship device... this has handset makers very jittery.
Having a GE also puts the latest Android on a device and puts pressure on the makers of the device to move build it out into their MAIN version of Android.
So Key lime pie or 4.3 should come quicker on the HTC and S4 than would be tradtional.
Another issues is transparency.
For too long handset makers have said "our phone can't run the latest version of Android" when we know they lie.
Samsung has been good.. the S2 has JB while the HTC Sensation 4G has all but been dumped by their makers.
Companies that have a Google edition will have that extra edge in longevity.
Gillion said:
In simple terms.
Google gets to have its vanilla version of Android on a flagship device without having to subsidize the cost of designing the hardware.
Unlike Nexus devices where Google invests R&D money to make the hardware... having Samsung and HTC put a version of Stock Android on the device pretty much absolves Google of any financial liability in relation to hardware development.
Nexus devices are traditionally spartan... and Google likes it that way... but what if mobile manufacturers want to have nexus compatible device with all the bells and whistles... they will all compete on who has the most Nexus compatible device.
This will attract developers and customers that prefer the stock Google experience
Bear in mind also Google is still developing their Motorola flagship device... this has handset makers very jittery.
Having a GE also puts the latest Android on a device and puts pressure on the makers of the device to move build it out into their MAIN version of Android.
So Key lime pie or 4.3 should come quicker on the HTC and S4 than would be tradtional.
Another issues is transparency.
For too long handset makers have said "our phone can't run the latest version of Android" when we know they lie.
Samsung has been good.. the S2 has JB while the HTC Sensation 4G has all but been dumped by their makers.
Companies that have a Google edition will have that extra edge in longevity.
Click to expand...
Click to collapse
Very good answer. Makes sense. It'd be exciting to see what Motorola device Google releases. MoNex (MoNey?).
kingzain900 said:
Very good answer. Makes sense. It'd be exciting to see what Motorola device Google releases. MoNex (MoNey?).
Click to expand...
Click to collapse
This could be the much rumored Google X Phone...
Sent from my GT-I9505 using Tapatalk 4 Beta
Theshawty said:
Careful now, he might actually believe it.
Click to expand...
Click to collapse
Easy, everyone knows that to work, he'd to input: *#THE SOURCE CODE# , otherwiste it will not work :laugh:
what time the phone will be up for eating anyone knows?
Sent from my GT-I9505 using xda premium
big_b0sss said:
what time the phone will be up for eating anyone knows?
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Don't think I'd want to eat a phone, actually.
Bet it'll be up noonish, USA time, which means roughly 18.00-19.00 Brit time.
big_b0sss said:
what time the phone will be up for eating anyone knows?
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
I think it can be all day in USA
Aerys said:
I think it can be all day in USA
Click to expand...
Click to collapse
yeah thats right all day i remember how nexus 4 was eaten within an hour
Sent from my GT-I9505 using xda premium
big_b0sss said:
yeah thats right all day i remember how nexus 4 was eaten within an hour
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
I hope we get firmware today

CyanogenMod - Moto G

What are the chances?
I waiting for too +1
It will come.
Sent from my XT1032 using xda app-developers app
I hope it will be officially supported!
Inviato dal mio Xperia U utilizzando Tapatalk
Flip a coin I'd say, not the most powerful device and not a nexus device either so I'm not sure but hopefully
Sent from my GT-N7000 using XDA Premium 4 mobile app
considering the price specs and unlocked bootloader it will almost definitely be supported
Sent from my HUAWEI U8950N-51 using Tapatalk
I hope CM's cozying up with Chinese manufacturers doesn't affect their motivation to support other brands. There's now business involved too.
On the other hand the latest Moto handsets are the closest thing to a Nexus without actually being one. Moto/Google's level of openness and the code they release should be telling. An interesting issue is also support for the dual-sim edition. I understand CM has been working towards it behind the scenes and shortly the first dual-sim device by Moto/Google themselves will be on sale. Will they or won't they release the code for dual-sim support for incorporation in parallel Android projects too?
myanogencod said:
I hope CM's cozying up with Chinese manufacturers doesn't affect their motivation to support other brands. There's now business involved too.
On the other hand the latest Moto handsets are the closest thing to a Nexus without actually being one. Moto/Google's level of openness and the code they release should be telling. An interesting issue is also support for the dual-sim edition. I understand CM has been working towards it behind the scenes and shortly the first dual-sim device by Moto/Google themselves will be on sale. Will they or won't they release the code for dual-sim support for incorporation in parallel Android projects too?
Click to expand...
Click to collapse
The model that probably will have the support of CyanogenMod will be the A 8GB chip, 2 chips but who knows Also gain support, This will depend on the developers. What remains is to wait
Sent from my GT-I9070 using xda app-developers app
myanogencod said:
I hope CM's cozying up with Chinese manufacturers doesn't affect their motivation to support other brands. There's now business involved too.
On the other hand the latest Moto handsets are the closest thing to a Nexus without actually being one. Moto/Google's level of openness and the code they release should be telling. An interesting issue is also support for the dual-sim edition. I understand CM has been working towards it behind the scenes and shortly the first dual-sim device by Moto/Google themselves will be on sale. Will they or won't they release the code for dual-sim support for incorporation in parallel Android projects too?
Click to expand...
Click to collapse
Cyanogen is still community based.... If there will be an developer who sync the cm repo with the device and fixes the bugs and offical submit it to cm there will be "official" cm support. Check out the CM Forum and the Rules to geht offical cm support then you can answer this question your own.
Gesendet von meinem Galaxy Nexus mit Tapatalk
arison1988 said:
Cyanogen is still community based.... If there will be an developer who sync the cm repo with the device and fixes the bugs and offical submit it to cm there will be "official" cm support. Check out the CM Forum and the Rules to geht offical cm support then you can answer this question your own.
Click to expand...
Click to collapse
What part of my message were you unhappy about again?
I can't see how The Rules would have anything to do with what I was wondering about.
Tschüss/Cheers
+1
need it!
me too
I'm confident the Moto G will be popular and there will be a wide variety of ROMs available, both stock and AOSP based should there be much difference (?).
I think the variety of ROMs will be more important than the presence or not of any specific ROM.
The $200 or less price point for the features has resulted in a LOT of online admiration by the sorts of people who root, ROM & customize.
Just convince ROM devs that it's a wonderful phone and the process will begin.
For those who prefer expensive flagships for their personal use, the Moto G is great for backup (after failed flashes etc, LOL) and great for the kids, grandma, and the rest of the family.
Now that it's been rooted (quite easily), it might not take too long till we see some custom roms popping aroud.
i don't understand why this device isn't more popular..
In the short time i had i've been very amazed at the pricepoint/performance, and on top of that the device is a google device with unlockable bootloader and android 4.4 promised, so i would've thought the developers would jump on board. Hopefully more developers will start working on this device :fingers-crossed:
Well, give it some time, this device is rather new, I am sure it will be popular, it's the cheapest quad-core around
Sent from my XT1032 using Tapatalk
First of all Motorola has to release the Blobs and Sources, which may happens next Week with Luck.
I've read somewhere that it's gonna get an update in January... maybe it's gonna be where everything will start.
Kameo said:
I've read somewhere that it's gonna get an update in January... maybe it's gonna be where everything will start.
Click to expand...
Click to collapse
It has already started.
theoneofgod said:
It has already started.
Click to expand...
Click to collapse
Source?

[BOUNTY] Android Lollipop for the One X

I have been trying really hard to replace my One XL with a new Lollipop enabled phone, but have been hard pressed to find a replacement. the OPO is brilliant, but is a bit too big for me (though I might still cave in).
So, considering I am planning to stick with my One XL for sometime, I'm trying to see if we can get devs interested in porting Lollipop over. The biggest advantage that I'm looking for is performance and battery life boost - due to Volta and ART, which may extend the usefulness of the One XL considerably.
Why should you be excited for Lollipop on the One X
Material Design UI - http://www.wired.com/2014/11/googles-quest-write-rulebook-interactive-design/
ART and Project Volta - http://www.latinpost.com/articles/16930/20140711/android-l-battery-life-glance-project-volta-art.htm
REQUIREMENTS:
Be the first person to create the following:
AOSP Android 5.0 OR Cyanogenmod 12 port OR Paranoid Android Lollipop port for the One XL
Voice+data (atleast HSDPA), Wifi, Bluetooth, GPS, NFC
ART instead of Dalvik
Project Volta enabled
Make a post in this thread with the following:
Proving it works with appropriate photos and/or screenshots
Providing full step-by-step instructions for which anyone else can follow
Confirmation from at least 2 persons on these forums that the ROM is working
Claim your bounty via PM from pledger(s)
Payment(s) will be processed between each member and the bounty collector via PM on an individual basis.
LIST OF PLEDGES
sandys1 - 10$
eyemyt - 15$.
obsidian_eclipse - 15$
I'm in. My pledge 15$.
Sent from my One XL using Tapatalk
great to see the ball rolling !
Are bounties payable via PayPal? We all live in different countries and that would probably be the safest and most effective way of doing it.
If the above features can be worked in (im tempted to make it harder and say have Sense added to - because I like sense) then I'll add $15 to the sum so far.
An indication from a developer on the scale of the job and its setbacks, realism and expectations too would be appreciated early on.
obsidian_eclipse said:
Are bounties payable via PayPal? We all live in different countries and that would probably be the safest and most effective way of doing it.
If the above features can be worked in (im tempted to make it harder and say have Sense added to - because I like sense) then I'll add $15 to the sum so far.
An indication from a developer on the scale of the job and its setbacks, realism and expectations too would be appreciated early on.
Click to expand...
Click to collapse
IMHO Sense is closed source - what has happened till now is that binaries of Sense UI have been made to run on newer and newer Android versions (going to 4.3 I think). However, as the newer Android diverges from what was the original intended Android version (for Sense), it becomes harder and harder. I think Sense development has pretty much stagnated on the Evita because of this.
I would say it will be a little hard and unrealistic for Sense to be ported over as such - but I think you will love what Lollipop and Material Design UI has tooffer. If you have the change to spare, I think it would be a good bet !
Last time around (in the Evita bootloader unlock), we transferred the bounty using Paypal. I'm planning to do mine that way this time as well.
Take a look at http://www.wired.com/2014/11/googles-quest-write-rulebook-interactive-design/
sandys1 said:
IMHO Sense is closed source - what has happened till now is that binaries of Sense UI have been made to run on newer and newer Android versions (going to 4.3 I think). However, as the newer Android diverges from what was the original intended Android version (for Sense), it becomes harder and harder. I think Sense development has pretty much stagnated on the Evita because of this.
I would say it will be a little hard and unrealistic for Sense to be ported over as such - but I think you will love what Lollipop and Material Design UI has tooffer. If you have the change to spare, I think it would be a good bet !
Last time around (in the Evita bootloader unlock), we transferred the bounty using Paypal. I'm planning to do mine that way this time as well.
Take a look at http://www.wired.com/2014/11/googles-quest-write-rulebook-interactive-design/
Click to expand...
Click to collapse
You mean AOSP.
Sent from my HTC One XL using XDA Premium 4 mobile app
CyanJustice said:
You mean AOSP.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure what you mean. I was replying to the poster above who was asking for the possibility of Sense being ported to lollipop on this phone.
Ok lollipop does look pretty great sans sense so it sounds like a good investment, provided a reasonable time scale for it's production, so hopefully the pledges will come in.
sandys1 said:
Not sure what you mean. I was replying to the poster above who was asking for the possibility of Sense being ported to lollipop on this phone.
Click to expand...
Click to collapse
Oh yeah he did, my bad lol
Sent from my HTC One XL using XDA Premium 4 mobile app
CM12 work has started - https://github.com/CyanogenMod/android/tree/cm-12.0 Now, it's upto a dev to volunteer for the evita!
Waiting for the good news.....
Sent from my HTC One XL using xda premium
paras33 said:
Waiting for the good news.....
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
this is not for the evita - this is for nexus 5 and newer variants. In fact if we do not convice someone to build a CM12 variant in time, our phone will be dropped from any nightly builds
http://www.landofdroid.com/2014/cm12-roadmap-leaked-exciting/
Device cutoff based on specifications. We expect 512mb devices to be fine, but the issue here will be GPU and non-Kitkat binaries. Expect a hard line here drawn in the sand with respect to device support. This will not be pretty for many older generation devices (pre-ICS).
Click to expand...
Click to collapse
Which is why this bounty was created in hope of accelerating that development.
sandys1 said:
this is not for the evita - this is for nexus 5 and newer variants. In fact if we do not convice someone to build a CM12 variant in time, our phone will be dropped from any nightly builds
http://www.landofdroid.com/2014/cm12-roadmap-leaked-exciting/
Which is why this bounty was created in hope of accelerating that development.
Click to expand...
Click to collapse
Well psh, we're definitely not pre-ICS.
Sent from my One X using XDA Premium 4 mobile app
I've always been of the opinion that HTC could have quite easily given us KitKat officially but they wanted to push people to upgrade unnecessarily. From the way lollipop sounds android promote it as being faster and more efficient than either KitKat or jellybean so if anything it should be pretty decent on our hardware.
obsidian_eclipse said:
I've always been of the opinion that HTC could have quite easily given us KitKat officially but they wanted to push people to upgrade unnecessarily. From the way lollipop sounds android promote it as being faster and more efficient than either KitKat or jellybean so if anything it should be pretty decent on our hardware.
Click to expand...
Click to collapse
You hit the nail right on the head there, that's exactly why they don't provide official updates. They're a business and profit is their bottom line. If they provide updates for older devices then the owners of those older devices have less reason to upgrade, less people upgrading means less profit for them.
Transmitted via Bacon
timmaaa said:
You hit the nail right on the head there, that's exactly why they don't provide official updates. They're a business and profit is their bottom line. If they provide updates for older devices then the owners of those older devices have less reason to upgrade, less people upgrading means less profit for them.
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah but you'd think people will upgrade naturally because of better hardware and specs, etc.
Sent from my One X using XDA Premium 4 mobile app
CyanJustice said:
Yeah but you'd think people will upgrade naturally because of better hardware and specs, etc.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Some do, but others are more focused on squeezing as much out of their current device as they can.
Transmitted via Bacon
timmaaa said:
Some do, but others are more focused on squeezing as much out of their current device as they can.
Transmitted via Bacon
Click to expand...
Click to collapse
Exactly, that's why I still have my HTC Inspire 4G, HTC One X, and my new LG G3. No sense in getting rid of the old ones when they work great with all of the ROM development that occurs! That old Inspire works great as a walkman while out in the mountains!
should just be happy with the kk roms and cm11 with gapps until something better comes out. I really like the 5.0 interface but it is really nothing ground breaking
Agreed...only thing to look to is if any real performance improvement....
Sent from my HTC One XL using xda premium

Snapdragon 820 = AOSP?

Quite simply, from what I'm reading about S6, and Exynos, the main reason for lack of major AOSP ROMS (CM13 has been finally ported), is the idea that Exynos is not documented so coding for it is difficult.
Knowing now that Snapdragon 820 is a Qualcom chip, which apparently is the most common SoC used for phones, should we expect to see a lot of AOSP based ROMs?
I am very used to Vanilla Android, and I don't think I could deal with TouchWiz, I like CM Theme Engine, and RRO Layers, so the big reason for my question is based on the hope that the probability of non-TouchWiz ROMs is high.
Also, I had a moto x 2014 and I've come to fall in love with AMOLED, and would like to stick to a small form factor 5 to 5.1 inches, combined with healthy ROM community, I'm kind of hoping S7 with SD820 might be the phone for me.
Please don't say "If you like Stock don't buy a Samsung", I get it, but it looks like maybe that stigma might not hold up soon if the ROM cookers are supportive.
Thanks!
I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.
geoff5093 said:
I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.
Click to expand...
Click to collapse
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.
I don't do carrier contracts so I'd most likely look/hope for a developer/pure edition of the S7.
The Edge does not really interest me, unless they figured out some cool things to do with the curved screen that are actually useful.
I'd much rather have a fingerprint reader, and front sensors like the Moto's, I love waving my hand in front of the display to have it wake up and tell me the time.
People go... you are a Jedi!?
Airtioteclint said:
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.
Click to expand...
Click to collapse
I know AT&T and Verizon are different stories, good to know it works for T-Mobile though.
Most if not all Sprint phones have unlocked bootloaders too. At least last time I checked!
Yes. However you got something wrong there. The reason why Qualcomm has all the fancy AOSP based ROMs (I say fancy because most people consider non aosp roms boring) is because of this. This is where QCOM releases their soruce code for the platforms. This makes fixing easier because you actually have the code. However exynos and all the other ones don't give a crap about the small percentage of their users that actually flash roms etc. Infact, they only want money. And guess what? ROMs = Longer device lifespan. That's why they don't release it. Thankfully enough there are some geniuses here on XDA that still are able to do the job for exynos! However, QCOM has allot better optimization with CM in terms of performance than with any other chipset. I live in the EU, which means Exynos. After already owning 2 exynos devices, I'm tired of the work that has to be done for them. I was lucky enough that both of them had Exynos chipsets that already had allot of devs mainly from other devices which made building possible for me.
@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.
Shemploo said:
@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.
Click to expand...
Click to collapse
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.
..
CTXz said:
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.
Click to expand...
Click to collapse
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.
knitler said:
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.
Click to expand...
Click to collapse
Um... CM =/= Cyanogen Inc
CM is a completely separate group that is not affected in any way. It's like XDA and GOogle. XDA is for developing and still both work on android. I know some people in the official CM group, all of them very friendly and none of it is affected by Cyanogen Inc. You're making yourself lies that aren't true. It's like blaming the entire CyanogenMod team because one dev for a specific device didn't fix the issue yet.
If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk
barondebxl said:
If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
Because some people don't want a nexus
CTXz said:
Because some people don't want a nexus
Click to expand...
Click to collapse
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
And cripple it with bad, forever-beta, with half the functionally misssing software.
Sure hope we get aosp!
Sent from my SM-N920T using Tapatalk
I thought it was primarily due to the 64 bit architecture that was the hold up with aosp on the s6. Buy I could be wrong. Been a while since I went looking.
barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?
CTXz said:
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?
Click to expand...
Click to collapse
Might want to get used to it as sooner or later it will only be nexus devices that are worked on.
Also what's the point of getting the device fore the hardware when aosp doesn't take advantage of the hardware? Aosp drivers don't compare to the stock ones.

Categories

Resources