Related
Hello all,
i like XDA Forums for its master brains and respect it for all the support.
i used windows mobile and android on different HTC devices and enjoyed all the interesting things in it with the help of XDA.
now i wanted to try motorola milestone and got it and it was a sheer disappointment.
Motorola milestone users are ignored very badly by motorola without updating the buggy phone and not even caring to reply users queries. its even deleting all the users posts in developer forums. it locked down the bootloader with digital signatures when the same device in US "Droid" has got all the cakes with open bootloader and custom roms and device updates for issues. recently it has announced 2.1 for droid where milestone still didn't even get 2.0.1
i see ano place to report this and motorola wantedly deleting all such posts in their support forums. as this is common android section, thought i can post it here and see if any master brains can help us.
check here where a continent itself is complaining against motorola and there is no single reply or action for this
Thanks for understanding
its bound to happen really, the Droid is Motorola's gem now and it will be the one shown off and given what it needs ahead of other devices.
Same with HTC and there devices, there flagship one's get the bug fixes and new updates while lesser models dont.
I'm sure the Milestone will eventually get what it needs.
What do you mean by locked down boot loader?
as far as i understand the bootloader in milestone is little different than in droid. the milestone bootloader uses digital signatures everywhere to check for the software authentication which makes it impossible to put custom ROMs as we do with all other android phones.
even motorola is very slow in updating the issues with milestone. i don't understand why they are doing this but its like completely locked down and totally ignored fir the price everyone payed.
hello admins / moderators / master brains / everyone,
is it possible to check the Motorola milestone bootloader for bypassing the digital signature check so that we can install custom roms on it as its done on Droid.
please take this as a kind request as i lost hope on motorola releasing the open bootloader on milestone and they r very slow in releasing updates for this device and also ignorant in resolving most bugs.
i see that you are supporting non HTC devices like samsung, toshiba and Acer. so a little hope that its posible to look into this
please everyone
i am not a big techie to understand internals of the possibilities but you can see how many people want this on here http://www.facebook.com/motorolaeurope
Thanks to all for reading this
Motorola Milestone and Droid feature the same Hardware (while Droid is CDMA and Milestone GSM) but they did not get the same software build.
Droid = with Google (Maps Navigation etc.)
Milestone = Motorola Android (Multitouch, Motonav etc.)
Thanks to TI, M-Shield is available on both devices. With M-Shield it is possible to control booting and flashing.
While the Droid does accept every signature, the Milestone is locked to (probably) one.
So there we are.
Kernel without signature will not boot (blocked by Bootloader).
Flashing another modified Bootloader is not possible without signature.
Barnd83 said:
Motorola Milestone and Droid feature the same Hardware (while Droid is CDMA and Milestone GSM) but they did not get the same software build.
Droid = with Google (Maps Navigation etc.)
Milestone = Motorola Android (Multitouch, Motonav etc.)
Thanks to TI, M-Shield is available on both devices. With M-Shield it is possible to control booting and flashing.
While the Droid does accept every signature, the Milestone is locked to (probably) one.
So there we are.
Kernel without signature will not boot (blocked by Bootloader).
Flashing another modified Bootloader is not possible without signature.
Click to expand...
Click to collapse
all this has already been figured out. what they want to know now is how to un-fudge it so that they have the same abilities as dream and other android users. I have been reading EVERYTHING i can find on the matter, as i REALLY want a milestone. id just get a droid, but i HATE verizon and am staying on t-mobile no matter what phone i hafta use. so im stuck on g1 till the milestone gets figured out. what i have been thinking is that the signature is a key, so there must be a keyhole, right? if we could find and disassemble the "keyhole", could we not then reverse engineer a key?
All this locked/unlocked nonsense is making me want a milestone even more, just so i can help figure this out and give motorola a big "F-U" for what they are doing. because thats basically what they've done, they've told all their customers to go F*&$ themselves. well, just the ones outside of the US.
Honestly i dont see how motorola made it this far with a slogan like, "Go F*&$ Yourself", but whatever. thats why i HATE verizon, because they dont give two ****s about their customers, as long as they get paid. and thats what motorola is doing here...they dont CARE what milestone users want, as long as they keep selling milestones, and controlling EVERY ASPECT of them.
doesnt sound like an OPEN SOURCE attitude, to me...
-BMFC
Milestone 2.0.1 had been released before you wrote that post actually (it was released on feb 4th).
if you didn't get the update OTA yet you can even get it through their website
I assume you're in Germany so try here hxxp://direct.motorola.com/GER/SoftwareUpdateSummary.asp?country=DEU&language=GER&web_page_name=SUPPORT&strCarrierId=&strPhone=MILESTONE
chowdarygm said:
where milestone still didn't even get 2.0.1
Click to expand...
Click to collapse
now the hope is gone and i decided to sell my device. its such a dumb company which doesn't care about end users.
HTC is far better in these things without putting hard restrictions.
You must have missed the hooplah that surounded the era of phones HTC put out around the Tilt. Crap video drivers etc....
HTC is just like Motorola. They go where the money is, although I say Motorola went a little overboard with the signed bootloader, it still runs rings around the Hero and most other aandroid devices short of Desire/ Nexus One.....
Greetings, programs! Well my question is not likely something anyone could have a definitive answer for - but I welcome any opinions or ideas. I don't want phone that is locked up against tinkering, but the current "price" of this phone is so tempting. Just about everything I've read tells me I'd really love this phone - the only thing holding me up is my expectation that there will be little to no development done with this phone.
I see that the bootloader seems to have been successfully unlocked? Now that this is the case I wonder if it's likely to be something anyone puts work into as far as developing ROMS/kernels. I'm not expecting Nexus-level activity, but even the hope of something might help me make up my mind (or I may just get a GNex). Thanks,
Merman1983 said:
Greetings, programs! Well my question is not likely something anyone could have a definitive answer for - but I welcome any opinions or ideas. I don't want phone that is locked up against tinkering, but the current "price" of this phone is so tempting. Just about everything I've read tells me I'd really love this phone - the only thing holding me up is my expectation that there will be little to no development done with this phone.
I see that the bootloader seems to have been successfully unlocked? Now that this is the case I wonder if it's likely to be something anyone puts work into as far as developing ROMS/kernels. I'm not expecting Nexus-level activity, but even the hope of something might help me make up my mind (or I may just get a GNex). Thanks,
Click to expand...
Click to collapse
The boot loader is unlockable for the dev edition RAZR m and as for development, safe strap has been released and cm10 alpha has been released. I have no doubt that in the future, more will come out. If ur attracted to this phone, then I highly suggest you get it because of the size and specs.
Sent from my XT907 using xda premium
jarzy00 said:
The boot loader is unlockable for the dev edition RAZR m and as for development, safe strap has been released and cm10 alpha has been released. I have no doubt that in the future, more will come out. If ur attracted to this phone, then I highly suggest you get it because of the size and specs.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Totally agree with jarzy00 i am coming from evil land apple and this phone feels nice and compact replacing my i4 LMAO
Razr i, Razr M and Razr M XT905 (Future release for Euro market maybe) are one of the few phones left standing with this kind of small foot print.
ever one else moved on to larger screens. And the specs aren't too shaby =)
Ok, I see. My experience with Moto phones are limited, but do I have it right that using the bootstrap method you can flash custom ROMS, but custom kernels are a no go? Still waiting till I make a decision, but every bit of info helps.
Coorect Bootstrap allow you to load that Beta CM10.
(There isn't much support on that yet)
And no custom kernels unless you have the Dev edition
There are AU Edition, US Edition, Dev Edition, And the i (Intel), there are plans for a EU Edition which will be GSM only
Either get it and hand in tight, or look for a DEV
Merman1983 said:
Ok, I see. My experience with Moto phones are limited, but do I have it right that using the bootstrap method you can flash custom ROMS, but custom kernels are a no go? Still waiting till I make a decision, but every bit of info helps.
Click to expand...
Click to collapse
Not sure how far development is on Safestrap for the M, but it will allow custom kernels on locked devices using kexec. The version for the Droid 3 (which has a locked bootloader) allows a 3.x kernel to be run instead of the factory 2.6.x kernel in order for better ICS and newer compatibility. Unless Motorola has patched this kexec bypass then it should be possible to implement on the M.
Thanks guys for this thread. I was possibly looking at this phone, but I don't want to end up with the same situation we had with the bionic. I think I'll skip it until Moto wises up and unlocks the bootloaders.
If you really want some development here, look at the donate thread for getting nytro a razr m so he can develop for the retail version. In terms of safestrap, you could potentially get modify a custom rom. It just takes one rom to iron out the major bugs and people can start deriving from it.
i dont think moto will ever get smart with bootloaders, which is sad because they make quality phones, with unlocked bootloaders i dont think id ever buy another brand. but regardless, we have stable safe strap, just isnt a big flagship device, its not a new phone and with all the new better phones that are cake to unlock, this phone is just looked over and left in the dust, aside from a few very good devs we have working to give us some stuff to play with, we wont see much.
I was really surprised to learn that LG don't have a bootloader unlocking service like even HTC have done and given that the LG never managed to unlock the bootloader, I'm quite surprised that there wasn't more of a community outcry. What is up with that? Have LG ever spoken of supporting the development community? Is it unlikely that we'll see it happen within the flagship lifetime of our device?
NB: This is discussion topic, it's really not a question/answer topic.
sabret00the said:
I was really surprised to learn that LG don't have a bootloader unlocking service like even HTC have done and given that the LG never managed to unlock the bootloader, I'm quite surprised that there wasn't more of a community outcry. What is up with that? Have LG ever spoken of supporting the development community? Is it unlikely that we'll see it happen within the flagship lifetime of our device?
NB: This is discussion topic, it's really not a question/answer topic.
Click to expand...
Click to collapse
whoa is this 100% correct? if that's the case I will strongly reconsider getting the G3 and will probably go for either M8 or Z2...
Well, coming from an LG Nexus 5, I can tell you that the development community is booming over there. But that's to be expected with a Nexus device. I'm planning on switching from the Nexus 5 to the G3 (ordered yesterday) in an effort to no longer sacrifice hardware in order to get the vanilla Android experience. These days I'd rather give up some of the software advantages in AOSP ROMs in order to get significantly better hardware.
Unfortunately, it's a sacrifice one way or another. And if you buy a phone such as the G3 you must do so expecting that the development for it will take significantly longer and will likely have less options. However, in my opinion the interface/features offered in the latest stock LG interfaces are quite improved and look/feel much better than the interfaces provided by other manufacturers. I don't think I'll have any issue using the stock interface with the LG for many months after coming from the previous 4 generations of Nexus devices.
The vanilla Android experience has gotten quite boring in my opinion and I welcome the features that will be available on LG's stock ROM.
cez10 said:
whoa is this 100% correct? if that's the case I will strongly reconsider getting the G3 and will probably go for either M8 or Z2...
Click to expand...
Click to collapse
Sadly yes, it's something I should've looked into in the six months of waiting for this phone. But it's sadly the case. Even on the G2, they couldn't unlock the bootloader and instead had to bypass it.
sn0warmy said:
Well, coming from an LG Nexus 5, I can tell you that the development community is booming over there. But that's to be expected with a Nexus device. I'm planning on switching from the Nexus 5 to the G3 (ordered yesterday) in an effort to no longer sacrifice hardware in order to get the vanilla Android experience. These days I'd rather give up some of the software advantages in AOSP ROMs in order to get significantly better hardware.
Unfortunately, it's a sacrifice one way or another. And if you buy a phone such as the G3 you must do so expecting that the development for it will take significantly longer and will likely have less options. However, in my opinion the interface/features offered in the latest stock LG interfaces are quite improved and look/feel much better than the interfaces provided by other manufacturers. I don't think I'll have any issue using the stock interface with the LG for many months after coming from the previous 4 generations of Nexus devices.
The vanilla Android experience has gotten quite boring in my opinion and I welcome the features that will be available on LG's stock ROM.
Click to expand...
Click to collapse
If you have the patience, I'd recommend waiting a little while to see if they announce a GPe of the G3. That could provide you with the best of both worlds.
Development will improve for sure - the phone has only been out less than a week (D855) with most people still not having received their devices yet and is not even released in the US. It seems the Korean models have shipped with an unlocked bootloader (from what I have heard) and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Give it time, development is always slow in the first month of a new device (unless its a nexus), and tends ot only pick up after release in the USA.
sabret00the said:
If you have the patience, I'd recommend waiting a little while to see if they announce a GPe of the G3. That could provide you with the best of both worlds.
Click to expand...
Click to collapse
Eh, if they release a GP edition G3 it will still pay to have this one because any AOSP ROMs for the GP edition will be quickly ported over to the non-GP edition anyway. I plan on keeping this phone but will also still be happy if they come out with a GP edition as well so we can get some AOSP source code up and running for this device.
And I'm not worried about the bootloader being locked. Someone ALWAYS finds a way to unlock it rather quickly these days.
Personally, my goal with this phone is to root it to get my DPI settings where I want them and get rid of any bloat that may cause the phone to slow down. If I can manage to accomplish those two things, I'll be happy (and it's already doable). My days of rooting, flashing ROMs, bricking, unbricking, and flashing more ROMs are over. At this point I just want a solid phone that works flawlessly.
Lennyuk said:
Development will improve for sure - the phone has only been out less than a week (D855) with most people still not having received their devices yet and is not even released in the US. It seems the Korean models have shipped with an unlocked bootloader (from what I have heard) and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Give it time, development is always slow in the first month of a new device (unless its a nexus), and tends ot only pick up after release in the USA.
Click to expand...
Click to collapse
I'm not so much talking about from the community side, I have faith the community will find an unlock or bypass method. I'm more so talking about from LG's point of view. They don't seem to be supportive hence no official channel to unlock the G2 bootloader despite the G3 launching globally this week.
sabret00the said:
I'm not so much talking about from the community side, I have faith the community will find an unlock or bypass method. I'm more so talking about from LG's point of view. They don't seem to be supportive hence no official channel to unlock the G2 bootloader despite the G3 launching globally this week.
Click to expand...
Click to collapse
Remember it took years to get HTC to provide an unlock tool (and the company nearly going bankrupt!), Moto and Sony were the same - moto becoming better when Google acquired them and Sony nearly gave up making android devices completely before they decided to become more dev friendly.
Basically companies only provide unlock methods as a last resort, when they feel its the only way to improve their sales. LG haven't needed this yet.
There are still plenty of devices where you cannot officially unlock the bootloader, its not just an LG thing.
Lennyuk said:
Remember it took years to get HTC to provide an unlock tool (and the company nearly going bankrupt!), Moto and Sony were the same - moto becoming better when Google acquired them and Sony nearly gave up making android devices completely before they decided to become more dev friendly.
Basically companies only provide unlock methods as a last resort, when they feel its the only way to improve their sales. LG haven't needed this yet.
There are still plenty of devices where you cannot officially unlock the bootloader, its not just an LG thing.
Click to expand...
Click to collapse
I totally hear you, but with the success Sony have enjoyed, you'd hope manufacturers would get involved early on.
Lennyuk said:
and as for the D855 no one has yet confirmed it a) it is locked and b) if it can be unlocked.
I have certainly not looked into it yet myself, although if it is locked, unlocking via any "hacking" method, is beyond my knowledge, someone smarter than me will have to tell us how to do that.
Click to expand...
Click to collapse
Is this something that is easy to check?
Dubhar said:
Is this something that is easy to check?
Click to expand...
Click to collapse
I can't even access the bootloader. Despite turning USB debugging on, I can't get ADB to recognise the phone. I started a thread to check if others have a similar problem.
It's a flagship, I'm not worried about development support. Look at the g2, it got cm support. Plus the LG software looks decent, not too basic like HTC or too intrusive like Samsungs touchwiz
sabret00the said:
I can't even access the bootloader. Despite turning USB debugging on, I can't get ADB to recognise the phone. I started a thread to check if others have a similar problem.
Click to expand...
Click to collapse
I rooted D855 yesterday using ioroot and as a part of the process "adb devices" did show the phone with USB debugging on.
I had to install lg unified driver so windows 8 had a right driver for it.
Heisenberg420 said:
It's a flagship, I'm not worried about development support. Look at the g2, it got cm support. Plus the LG software looks decent, not too basic like HTC or too intrusive like Samsungs touchwiz
Click to expand...
Click to collapse
This thread is about development support from LG. Please read threads before commenting. The G2 you mentioned was given as an example of the lack of support previously provided by LG.
jodvova said:
I rooted D855 yesterday using ioroot and as a part of the process "adb devices" did show the phone with USB debugging on.
I had to install lg unified driver so windows 8 had a right driver for it.
Click to expand...
Click to collapse
Perhaps I need to update my drivers then. Though that's nearly unheard of as I'm on Linux.
If i can atleast root the phone to remove the bloatware, I'll be happy for a little while.
sabret00the said:
This thread is about development support from LG. Please read threads before commenting. The G2 you mentioned was given as an example of the lack of support previously provided by LG.
Perhaps I need to update my drivers then. Though that's nearly unheard of as I'm on Linux.
Click to expand...
Click to collapse
Hm, i've not check on Linux yet, but it is recognised on windows with the right USB drivers installed. Maybe its lacking some udev rule to properly recognise the device?
The LGD855 boots into recovery with adb reboot recovery, but not the bootloader using adb reboot-bootloader its just reboots. I goes into download mode with power+volume up, that about all ive tried.
Slash8915 said:
If i can atleast root the phone to remove the bloatware, I'll be happy for a little while.
Click to expand...
Click to collapse
towelroot worked.
on Win 7 by flashing sphinxrom for d855 and s,k,l :
when i was installing the lg driver, it installed the AndroidNet Sooner Single ADB Interface
i had to change it Android ADB Interface
what the hell the device just came out give it some time
daddioj said:
what the hell the device just came out give it some time
Click to expand...
Click to collapse
What the hell can't you read & understand what OP has said or trying to say? (sorry no offence intended). He isn't talking about the support of the development community to this device(G3), which by the way will certainly pick up from what it is now, but he is talking about LG's support to the development community(being more developer friendly as Sony & HTC).
And even if we talk about how much active Android development this device(& it's variants) will see, then let me tell you that the development activity of this device will(probably) never be as much as you see with other flagship devices like HTC One(M7 & m8), that is because a) HTC is more developer friendly by letting you to unlock the bootloader & thus making easy for developers to port(make) ROMs, recoveries & what not, where as with LG & G2 it is entirely different case(ask any developer involved in G2 development, how difficult it is or was to make a recovery or a ROM for G2 and for common flahers the risk factor of flashing those recoveries & ROMs that much more because all the solutions based on a bypassing solution with many permutations & combinations rather than a fully unlockable bootloader just as with HTC devices and b) they are more popular devices among people(as much successful the G2 was it wasn't sold as many as S4s & S5s or M7s & M8s).
We all hope that LG will follow HTC & Sony in being developer frienly. No doubt they are making beautiful devices like G2 & now G3. But sadly, as one of other member pointed out above, it is at the stage of extinction that a manufacturer tend to be more friendly with developer community.
st_7 said:
What the hell can't you read & understand what OP has said or trying to say? (sorry no offence intended). He isn't talking about the support of the development community to this device(G3), which by the way will certainly pick up from what it is now, but he is talking about LG's support to the development community(being more developer friendly as Sony & HTC).
And even if we talk about how much active Android development this device(& it's variants) will see, then let me tell you that the development activity of this device will(probably) never be as much as you see with other flagship devices like HTC One(M7 & m8), that is because a) HTC is more developer friendly by letting you to unlock the bootloader & thus making easy for developers to port(make) ROMs, recoveries & what not, where as with LG & G2 it is entirely different case(ask any developer involved in G2 development, how difficult it is or was to make a recovery or a ROM for G2 and for common flahers the risk factor of flashing those recoveries & ROMs that much more because all the solutions based on a bypassing solution with many permutations & combinations rather than a fully unlockable bootloader just as with HTC devices and b) they are more popular devices among people(as much successful the G2 was it wasn't sold as many as S4s & S5s or M7s & M8s).
We all hope that LG will follow HTC & Sony in being developer frienly. No doubt they are making beautiful devices like G2 & now G3. But sadly, as one of other member pointed out above, it is at the stage of extinction that a manufacturer tend to be more friendly with developer community.
Click to expand...
Click to collapse
i am Guilty of not reading the whole Thread
:laugh:
So I wanted to get this out there early and of course we will not know until the Nexus 6 is released, but I was hoping to start a pledge thread for the development of root for the Turbo and also the possiblity of adapting the Verizon Nexus 6 ROM to work or replace the Turbo's ROM. Now, I am no programmer and don't know if this can even be attempted or done, but from an analytical view, once the Droid Turbo is rooted and hopefully the bootloader can be unlocked, I would think there would be some possiblity of the Nexus 6 ROM to make it to the Turbo.... Let at some of the facts:
Just from stats alone the Turbo is basically the Nexus 6 with a smaller screen. RAM, Cameras, Processor, Screen Resolution, etc. are the same
One would have to believe that many of the internal components will match especially when it comes to the Verizon variant of the Nexus 6. Without teardowns of both, I would believe that the radios too would be very similiar, which would be one of the major hurdles for adapting the ROM to Turbo...
I know none of these similiarites may actually amount to anything that makes root or trying to bring the Nexus 6 ROM to Turbo possible, but hell I can take the amount of flames I may get for throwing the idea out there
Of course, someone will probably make a ASOP ROM as well, but I thought I might throw it out there and spark some interest from developers that are way more knowledgable in all things android than me. Plus, I know the Android L from Kit Kat makes it a difficult challenge as well.
Not going to offer a bounty but just mad praise. :good:
Thoughts?:silly:
I'll throw in $40 and more to come.
Ill pledge $25 bucks to that.
mahst68 said:
:laugh:
So I wanted to get this out there early and of course we will not know until the Nexus 6 is released, but I was hoping to start a pledge thread for the development of root for the Turbo and also the possiblity of adapting the Verizon Nexus 6 ROM to work or replace the Turbo's ROM. Now, I am no programmer and don't know if this can even be attempted or done, but from an analytical view, once the Droid Turbo is rooted and hopefully the bootloader can be unlocked, I would think there would be some possiblity of the Nexus 6 ROM to make it to the Turbo.... Let at some of the facts:
Just from stats alone the Turbo is basically the Nexus 6 with a smaller screen. RAM, Cameras, Processor, Screen Resolution, etc. are the same
One would have to believe that many of the internal components will match especially when it comes to the Verizon variant of the Nexus 6. Without teardowns of both, I would believe that the radios too would be very similiar, which would be one of the major hurdles for adapting the ROM to Turbo...
I know none of these similiarites may actually amount to anything that makes root or trying to bring the Nexus 6 ROM to Turbo possible, but hell I can take the amount of flames I may get for throwing the idea out there
Of course, someone will probably make a ASOP ROM as well, but I thought I might throw it out there and spark some interest from developers that are way more knowledgable in all things android than me. Plus, I know the Android L from Kit Kat makes it a difficult challenge as well.
I will throw in $50 for root. And $50 for Nexus 6 ROM. :good:
Thoughts?:silly:
Click to expand...
Click to collapse
A few things to note here....
There are no carrier specific versions of the Nexus 6. There is simply a US and International version. That being said, VZW isn't even selling them. You can buy them from the Google Play Store and take them to Big Red for activation, however.
The Nexus "should" be running an almost completely "vanilla" version of Kit Kat or Lollipop. So there wouldn't really be a benefit to porting the Nexus ROM when an AOSP build would achieve the same results.
Either way, unless a root / bootloader unlock happens (Chinese Middleman is about the only hope right now), there will be no point.
That being said, I won't pledge anything toward root until it happens.
I'll pledge a high five and some bragging rights to the man who achieves root and unlocking.
XDA barely tolerate pledge threads. You should follow open1your1eyes0 template for the OP and the collection of the bounty.
mahst68 said:
:laugh:
...And $50 for Nexus 6 ROM. :good:
Thoughts?:silly:
Click to expand...
Click to collapse
What exactly from Nexus ROM do you want on Turbo?
Turbo firmware is as plain as it can be - except the bloat. With no root - disable the bloat to get 99.9% vanilla Android. With root - remove bloat from system partition to get 100% vanilla Android.
I don't think this was thought through.
What exactly from Nexus ROM do you want on Turbo?
Honestly I want it all the way around, bring the Kit Kat ROM from the Turbo to the Nexus 6.
Moto maxx(turbo int variant) already have root and recovery, i really hope devs port anything aosp like for nor devices
Let's be honest to ourselves here guys, out beloved Moto X Style was officially released in September which means this phone has now been out for at least 3 months and while all the effort that has since been put in this devices by key developers and people from day 1 up till now is very much appreciated and will continue to be appreciated, the development of this device compared to most flagships has been slow motion.
I am just trying to understand what the hell went wrong with this phone that made it end up with such super slow motion development, as when I originally bought the device I was thinking this phone would be at least in the top 20 most active phones on XDA development wise.
It had so much going for it, easy root, easy unlockable bootloader, a pretty much almost complete stock version of android, kernel sources released and motorolas good track record of updating their flagship phones in a timely manner and good hardware to accompany the great bloatware free stock software and a cheap price compared to some other flagships from other companies such as Samsung and Sony
With all this in mind I thought developers would flock to this device and we would have a massive development forum with loads of options between custom roms, mods, themes and other tweaks etc
But this is far from the case and I know the Nexus 6P being released probably had something to do with it, Still this should have been at least in top 20
At first I thought when Android 6.0 MM will be released development will increase then we needed the kernel sources as that was apparently not enough, then we had kernel sources but apart from 1 or 2 roms showing up being in alpha stages nothings changed too much.
This is such a disappointment to say the least.
If only I could understand why this is happening maybe something could be done to fix this or increase the development of this phone, I dont know maybe get some developers from the nexus 6p forums on here some how ...
Any ideas why this has happened and if anything can be done to increase development?
IS THERE ANY WAY WE AS A COMMUNITY CAN GET MORE DEVELOPERS TO WORK ON THIS DEVICE?
djsynth said:
If only I could understand why this is happening maybe something could be done to fix this or increase the development of this phone, I dont know maybe get some developers from the nexus 6p forums on here some how ...
Any ideas why this has happened and if anything can be done to increase development?
IS THERE ANY WAY WE AS A COMMUNITY CAN GET MORE DEVELOPERS TO WORK ON THIS DEVICE?
Click to expand...
Click to collapse
I think it's due to a combination of factors, such as :
1) The popularity of the phone/ manufacturer. These figures show Lenovo/Motorloa in 5th place for sales, having a 3.7% market share in Q3 2015
2) The OS (Android) has improved a lot over recent years, to the extent where a lot of people (like me) are happy to stay with stock
3) With phones getting more expensive, more people are put off from unlocking their bootloader due to warranty issues
4) I'm no longer convinced about the benefits of custom ROMs - seems a lot of the time they break more things than they fix. Maybe a lot of other people now think the same.
5) Some apps, for example ones for mobile banking or subscrition TV & Video, will not work with a rooted phone.
In the past I've had various phones from various manufacturers, and I'd say if you get your kicks from installing custom ROMs, then buy a Nexus.
When i had the one plus one there were so many roms that was a brain storm... I prefer some and reliable roms than a plethora where you get confused!!!
2) The OS (Android) has improved a lot over recent years, to the extent where a lot of people (like me) are happy to stay with stock
Click to expand...
Click to collapse
4) I'm no longer convinced about the benefits of custom ROMs - seems a lot of the time they break more things than they fix. Maybe a lot of other people now think the same.
Click to expand...
Click to collapse
IMO you hit the nail on the head. I love this phone. I had the MXPE 2014 as well, was not a fan. Also owned the original, Loved it.
This MXPE has been great in imo, the lack of development has not been disappointing to me. The stock rom is really pretty good, there are minor tweaks that can be done but most can do these on their own.
I used to be a flash-aholic, but like @GretaLewd has stated...custom roms tend to break things. I'm more in favor of kernel development. But how many different kernels can you have? One way or another they'll be the same.
I also own a Nexus 6P, but my MXPE is my go to device.
I see users complaining about this phone constantly, I really don't think it matters what phone you put in the hands of those users...they would still find fault and complain.
Motorola and Lenovo did good by this device, I just hope they keep up with incrementals for a while.
Isn't the 64bit cpu reason because it takes more work to get cm/aosp roms?
Sent from my XT1575 using Tapatalk
Good thread. Would love to hear more thoughts
Sent from my XT1575 using Tapatalk
Ordered the device today. Hope slow development doesn't disappoint me on this device, as others have stated...
I have been using this device for 2 months now. I am happy with it an didn't face a single issue. I can do a little bit tweaking myself using Xposed.
So far the slow development doesn't bother me.
Only buy a device for what it can do out of the box, not what you hope it will be able to do with additional modding and development... Nothing else is guaranteed!
As it stands I'm very happy with my rooted stock Style, not need for custom roms.
chrisund123 said:
Only buy a device for what it can do out of the box, not what you hope it will be able to do with additional modding and development... Nothing else is guaranteed!
As it stands I'm very happy with my rooted stock Style, not need for custom roms.
Click to expand...
Click to collapse
That's a good way to approach Android phones I suppose but I believe
it's still nice to buy a phone that's great out of the box and good development wise, usually flagships tend to have good development and then the mid range and low end phones tend to get smaller developments but I guess there's an exception to everything.
patt2k said:
Isn't the 64bit cpu reason because it takes more work to get cm/aosp roms?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I doubt that's the reason since 64 Bit has been the standard since Lollipop and pretty much all the flagships have a 64bit cpu since the beggining of 2015 but that doesn't stop other development forums from flourishing.
GretaLewd said:
I think it's due to a combination of factors, such as :
1) The popularity of the phone/ manufacturer. These figures show Lenovo/Motorloa in 5th place for sales, having a 3.7% market share in Q3 2015
2) The OS (Android) has improved a lot over recent years, to the extent where a lot of people (like me) are happy to stay with stock
3) With phones getting more expensive, more people are put off from unlocking their bootloader due to warranty issues
4) I'm no longer convinced about the benefits of custom ROMs - seems a lot of the time they break more things than they fix. Maybe a lot of other people now think the same.
5) Some apps, for example ones for mobile banking or subscrition TV & Video, will not work with a rooted phone.
In the past I've had various phones from various manufacturers, and I'd say if you get your kicks from installing custom ROMs, then buy a Nexus.
Click to expand...
Click to collapse
Thank you for your break down on your thoughts of the subject and I must admit you've mention some very valid points here especially Point 1,2 and 5 but I think out of all of these its Point 1 and 2 that are the most significant, I suppose Motorola have a really small market share explains the lack of adoption between developers when comparing to some of the more prominent manufacturers such as samsung.
and The Android Stock OS has improved significantly within the past couple of years adding some new features that previously people had to root their phones to acomplish such as full app permission controls and backing up app data which google does for you now.
You need to follow development before buying a device these days. i.e. always wait at least 1-2 months. If you follow the development forums you would get an idea if developers are interested in said device or not. I for one, bought it right after I found out that AICP (CM12) rom was being developed. I was interested in running CM13 instead of other AOSP variations. And before I got the device the first (almost daily driver) builds were already uploaded.
Once cm is solid quite a few roms will pop up. Won't be long now.
Official MM has only been out for our phone for a little over a month. give it some time it may pick up. either way it's still an awesome phone out the box... and as stated above, once CM13 is stable im sure we'll see some of the other custom ROMs that are based off it.
GretaLewd said:
2) The OS (Android) has improved a lot over recent years, to the extent where a lot of people (like me) are happy to stay with stock
Click to expand...
Click to collapse
This is a great point, but I'd like to add that this is especially applicable to our MXPE. We're really close to stock as it is, so there's little motivation to go ROM to debloat like there is on Samsung, LG, and similar phones. On the flip side, we have a lot of really neat features (active display, approach, accelerator gestures, voice controls) that we would lose if we went ROM.
For me, these two points combine, leaving me with little motivation to ROM my phone, especially since I can could get most of the advantages of CyanogenMod with something like GravityBox, which will allow me to keep the Motorola features (I'm currently unrooted because of the warranty, but I'll be rooted in the future for sure) . Of course, these are my own personal opinions, but I suspect that they reflect at least some of the mindset of this community.
I agree with others, that custom roms are often more trouble than they're worth. The only reason to use them these days is if your device isn't going to be updated to the latest version of Android.
Ever since moto introduced 99% stock android + moto display, roms have been entirely unnecessary for me. I used to rom my phones to gain greater flexibility + customizability. Now that I have stock android + Xposed, I doubt I will ever flash another custom rom again.
I'm still waiting for custom super roms that will make this device best in the market. Why can we have a rom with 1080p display, tweak kernel with better control for heating issue for overall battery life and speed?
Sent from my XT1575 using XDA Free mobile app
The biggest issue is that developers don't support devices they don't own. With the launch of the nexus 6 (not the 6p) most developers got it and had no need to update to a y newer devices.
Also to the comment that all flag ships are 64 bit this is not the case. If you look the most popular devices as far as developers are concerned are non 64 bit.
Also as android matures you will see less and less roms. As it will be come harder. There are very few real development teams. Most are just kitchen sink roms. A base with tons of cherry picks and a new name. Nothing even worth looking at twice. But more developers are closing up the source of their projects because of these types of roms.
To be honest most users have no point in flashing roms. Only those that like the development side of it will continue to mod roms and flash things.