I seem to be having issues where my service does not seem to be as strong on CM12.1 compared to the stock ROM. Any idea on a fix for this?
IMHO, common problem on almost every device with CM. The difference with stock is noticable but not huge. (Saw it on xt912, xt926, xt1080 etc.)
It is unfortunate as this issue is the difference between getting LTE and 3g. Back to stock I guess...
I get LTE just fine
Sent from my DROID Turbo using Tapatalk
nubia11 said:
I get LTE just fine.
Click to expand...
Click to collapse
Same here. To the op: what carrier do you have? Have you flashed the appropriate radio/BL from the CM12.1 quark thread? It's in the op there.
http://forum.xda-developers.com/showthread.php?p=64074102
I tried everything... Finally just installed freeks ROM... Not much dev in turbo huh?
Not overly much, but then again my old phone was a Casio Commando 4G... You want moribund development try those forums. Yikes!
Also keep in mind that the Moto Maxx XT1225 forum is very helpful as well, being that it's the basically the same phone. If the answers aren't here, they are likely there.
And fwiw I haven't had any problems be it with computerfreek, cm, mokee, or resurrection. I suspect there's more than a few of us lurking about without issues as well. So I figure the devs are doing pretty good. Then again, coming from Casio-land I instinctively expect very little. Having at least 4 roms with varying degrees of activity is awesome as far as I'm concerned.
MazinDLX said:
I tried everything... Finally just installed freeks ROM... Not much dev in turbo huh?
Click to expand...
Click to collapse
You just aren't looking in the right place. All the Quarks have the same hardware, and except for the Droid Turbo they all had unlock-able bootloaders from the very beginning via Motorola websitie. So, there's tons of development.
For almost a year the Quarks were all in this forum. But because the Droid Turbo was locked down (per orders from Verizon), the Droid Turbo people got mad because they saw all this neat dev stuff they couldn't get. So, they petitioned XDA mods to split the forum into the "dead" Droid Turbo dev forum and the active rest-of-the-Quarks forum.
The forum split happened in September 2015...
Then, guess what? About two months later, exploit was found to unlock the Droid Turbo bootloaders! So, now all the Droid Turbo users who want custom ROMs, custom kernels, etc, have to trek over to the rest-of-the-Quarks forum -- aka Moto Maxx forum, but it's also the Moto Turbo forum. Yeah, there's TWO Quarks called Turbo.
After the Droid Turbo bootloader unlock, the CM dev started a CM thread over here --but it's the SAME ROM as in the Moto Maxx forum, and most people (even Droid Turbo users) just post over there.
_______
The only difference in all the Quarks ("international" Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250, Droid Turbo XT1254) are the radios. (In fact the U.S. Moto Maxx XT1250 and Droid Turbo XT1254 are identical in every way, including the radios! Even the same FCC ID.)
The DEVICE called the Droid Turbo was NEVER exclusive to Verizon. The exact same phone is/was sold by U.S regional CDMA/LTE carriers as the U.S . Moto Maxx. Motorola even used the "Turbo" name again for another Quark. Only the "Droid" name was exclusive, because Verizon licenses that name from LucasArts. So, yeah you can only buy a "Droid Turbo" from Verizon, but you can buy the EXACT SAME PHONE (with the same bands) from another carrier in the U.S. Put a Verizon SIM card into a U.S. Moto Maxx and it runs on Verizon just like a non-Verizon Nexus 6...
It would be like Samsung calling their Galaxy S6 the "S6", everywhere but Verizon. For Verizon, it would be called the "Yabba Dabba Do" phone. And Verizon puts out press releases: The "Yabba Dabba Do" phone is EXCLUSIVE TO VERIZON! It's still just a Galaxy S6! Oh, but the Verizon version would have a locked-down bootloader...
____________
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Only the Quark radios are different. Everything else is identical, which is why all these Quark ROMs below work on all the Quarks -- including the Droid Turbo XT1254 (with unlocked bootloader):
CM12.1 ( @Skrilax_CZ dev)
Resurrection Remix ( @baybutcher27 dev)
Mokee (AOSP ROM, @baybutcher27 dev)
Xperia Z5G
as well as custom kernel BHB27 ( @baybutcher27 dev).
Droid Turbo owners are using all of these above. But except for the CM dev, the devs aren't posting duplicate threads over here in the Droid Turbo forum. You have to go over to the Moto Maxx forum to participate.
ChazzMatt said:
You just aren't looking in the right place. All the Quarks have the same hardware, and except for the Droid Turbo they all had unlock-able bootloaders from the very beginning via Motorola websitie. So, there's tons of development.
For almost a year the Quarks were all in this forum. But because the Droid Turbo was locked down, Droid Turbo people got mad because they saw stuff all this neat stuff they couldn't get. So, they petitioned XDA mods to split the forum into the "dead" Droid Turbo dev forum and the active rest-of-the-Quarks fourm.
The forum split happened in September 2015...
Then, guess what? About two months later, exploit was found to unlock the Droid Turbo bootloaders! So, now all the Droid Turbo users who want custom ROMs, custom kernels, etc, have to trek over to the rest-of-the-Quarks forum -- aka Moto Maxx forum, but it's also the Moto Turbo forum. Yeah, there's TWO Quarks called Turbo.
After the Droid Turbo bootloader unlock, the CM dev started a CM thread over here --but it's the SAME ROM as in the Moto Maxx forum, and most people (even Droid Turbo users) just post over there.
_______
The only difference in all the Quarks ("international" Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250, Droid Turbo XT1254) are the radios. (In fact the U.S. Moto Maxx XT1250 and Droid Turbo XT1254 are identical in every way, including the radios! Even the same FCC ID.)
The DEVICE called the Droid Turbo was NEVER exclusive to Verizon. The exact same phone is/was sold by U.S regional CDMA/LTE carriers as the U.S . Moto Maxx. Motorola even used the "Turbo" name again for another Quark. Only the "Droid" name was exclusive, because Verizon licenses that name from LucasArts. So, yeah you can only buy a "Droid Turbo" from Verizon, but you can buy the EXACT SAME PHONE (with the same bands) from another carrier in the U.S. Put a Verizon SIM card into a U.S. Moto Maxx and it runs on Verizon just like a non-Verizon Nexus 6...
It would be like Samsung calling their Galaxy S6 the "S6", everywhere but Verizon. For Verizon, it would be called the "Yabba Dabba Do" phone. And Verizon puts out press releases: The "Yabba Dabba Do" phone is EXCLUSIVE TO VERIZON! It's still just a Galaxy S6! Oh, but the Verizon version would have a locked-down bootloader...
____________
Only the Quark radios are different. Everything else is identical, which is why all these Quark ROMs below work on all the Quarks -- including the Droid Turbo XT1254 (with unlocked bootloader):
CM12.1 ( @Skrilax_CZ dev)
Resurrection Remix ( @baybutcher27 dev)
Mokee (AOSP ROM, @baybutcher27 dev)
Xperia Z5G
as well as custom kernel BHB27 ( @baybutcher27 dev).
Droid Turbo owners are using all of these above. But except for the CM dev, the devs aren't posting duplicate threads over here in the Droid Turbo forum. You have to go over to the Moto Maxx forum to participate.
Click to expand...
Click to collapse
Thanks for explaining this in such detail. A lot of people are probably surprised to know this. It's been going on for many generations of the Android phone,and can get confusing when forums start splitting up. Nice detail!!
Sent from my DROID Turbo using Tapatalk
Related
I recently purchased a Motorola RAZR M 4G (LTE) here in australia from a local retailer. The details of which can be found at:
http://www.dicksmith.com.au/unlocked-smart-phones/motorola-razr-m-4g-unlocked-dsau-em5184
I have since unlocked the bootloader (I think it may of actually came pre-unlocked anyway), rooted and flashed Carbon KitKat ROM onto the phone.
In flashing Carbon I thought that for an XT905, I should of used the unified moto_msm8960 build. However, the install zip starts with an assert to check that the phone is correct for the ROM and thereby has a check (with others) for "scorpion_mini". But, my phone was returning "scorpion_mini_u". So, I editied the install zip to enable it to flash, and it all went smoothly and has been working fine. But, recently I looked at some logs generated by my phone, and it is showing up as msm8960dt; which if I am not mistaken in used by a MOTO X (among others).
So, it would appear that my Motorola RAZR M thinks it is not a scorpion_mini but a scorpion_mini_u, and it also thinks its a Moto X (msm8960dt ), but is "happy" to run a moto_msm8960 ROM, instead of an msm8960dt ROM.
I guess my questions are:
1. Has anyone else come across the above mix of identities? and understands whats going on?
2. Although the ROM appears to be running well, should I really only be flashing the "dt" ROMS onto my phone? either way, it does NOT match the available options in the assert statement for either ROMs.
I don't know if this helps anyone explain the above, but I found this thread:
http://forum.xda-developers.com/showthread.php?t=2528344
and when I checked the CPU Info
[email protected]_u:/ # cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 4 (v7l)
processor : 0
BogoMIPS : 13.53
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x1
CPU part : 0x04d
CPU revision : 4
Hardware : msm8960dt
Revision : 82a0
Serial : XXXXXXXXXXXXXXXX
Click to expand...
Click to collapse
I've pushed http://review.cyanogenmod.org/64451 for the scorpion_mini_u assert.
I'm not surprised it's confusing for you. The "dt" in "Machine: msm8960dt" you see in dmesg actually means "device tree".
In the case of moto_msm8960dt family (Moto X, Droid Ultra, Droid Maxx, Droid Mini), msm8960dt refers to SoC - MSM8960DT.
SoC used by moto_msm8960 family (Razr HD, Razr M, Atrix HD, Photon Q) is MSM8960.
Builds for your Razr M are moto_msm8960. moto_msm8960dt builds wouldn't boot on xt905 at all.
EDIT: yes, the thread you've found is about the same matter.
Thanks. When trying to find references to the scorpion_mini_u on the web, I also came across references to the "scorpion_mini_t"
https://github.com/mattlgroff/cwm/tree/master/motorola
I just came across the following web site whuich details some of the mapping between the codes, which may help in fuirther improving the cross over of the unified build.
https://support.google.com/googleplay/answer/1727131?hl=en
Motorola
201M (scorpion_mini_t/201M)
A1680 (umts_lucky/A1680)
Atrix (olympus/MB860)
Atrix (olympus/MB861)
Atrix (olympus/ME860)
Atrix HD (qinara/MB886)
Backflip (motus/MB300)
Backflip (motus/ME600)
Charm (umts_basil/MB502)
Citrus (cdma_ciena/WX442)
Citrus (cdma_ciena/WX445)
Citrus (cdma_ciena/XT301)
CLIQ (morrison/MB200)
CLIQ (morrison/morrison)
Cliq-XT (zeppelin/MB501)
Cliq-XT (zeppelin/ME501)
Defy (umts_jordan/MB525)
Defy (umts_jordan/MB526)
Defy (umts_jordan/ME525)
Defy (umts_jordan/ME525+)
Defy (umts_jordan/unknown)
Devour (calgary/calgary)
Devour (calgary/Devour)
Droid (miler/A854)
Droid (sholes/Droid)
Droid (umts_sholes/A853)
Droid (umts_sholes/Milestone)
Droid (umts_sholes/umts)
Droid (umts_sholes/XT701)
Droid (umts_sholes/XT702)
Droid (umts_sholes/XT720)
Droid 3 (cdma_solana/DROID3)
Droid 4 (cdma_maserati/DROID4)
DROID BIONIC (cdma_targa/DROID BIONIC)
Droid Bionic (cdma_targa/DROID BIONIC)
Droid II (cdma_droid2/A955)
Droid II (cdma_droid2/DROID2)
Droid II (cdma_droid2we/DROID2 GLOBAL)
Droid MAXX (obake-maxx/XT1080)
Droid Mini (obakem/XT1030)
Droid Pro (cdma_venus2/DROID PRO)
Droid Pro (cdma_venus2/DROID Pro)
Droid Pro (cdma_venus2/Milestone PLUS)
Droid Pro (cdma_venus2/XT610)
DROID RAZR (cdma_spyder/DROID RAZR)
Droid RAZR (umts_spyder/XT910)
DROID RAZR HD (vanquish/DROID RAZR HD)
DROID RAZR HD (vanquish_u/XT925)
DROID RAZR i (smi/XT890)
DROID RAZR M (scorpion_mini/XT907)
Droid Ultra (obake/XT1080)
Droid X (cdma_shadow/DROIDX)
Droid X (cdma_shadow/MB810)
Droid X (cdma_shadow/ME811)
Droid X (cdma_shadow/Milestone X)
Droid X (cdma_shadow/MotoroiX)
Droid X2 (daytona/DROID X2)
Droid X2 (daytona/Milestone X2)
DROID4 (cdma_maserati/DROID4)
Falcon (falcon_cdma/XT1031)
Falcon (falcon_umtsds/XT1033)
Flipout (umts_ruth/MB511)
Flipout (umts_ruth/ME511)
Flipout (umts_ruth/MotoMB511)
Glam XT800 (titanium/XT800)
i867 (destino/i867)
i940 (fawnridge/i940)
Iron Rock (umts_irock/XT627)
IS12M (cdma_spyder/IS12M)
Master Touch (umts_primus/XT621)
MB200 (morr/MB200)
MB501 (zepp/MB501)
MB508 (umts_sage/MB508)
MB520 (umts_kobe/MB520)
MB610 (umts_begonia/MB610)
MB611 (umts_begonia/MB611)
MB612 (cdma_kronos/MB612)
MB632 (umts_elway/MB632)
MB865 (edison/MB865)
ME632 (umts_elway/ME632)
ME863 (umts_solana/ME863)
ME865 (edison/ME865)
Milestone (A853/Milestone)
Milestone2 (umts_milestone2/A953)
Milestone2 (umts_milestone2/ME722)
Milestone2 (umts_milestone2/MotoA953)
MILESTONE3 (cdma_solana/MILESTONE3)
Moto E (condor_udstv/XT1025)
Moto E (condor_umts/XT1021)
Moto E (condor_umts/XT1023)
Moto E (condor_umtsds/XT1022)
Moto G (falcon_cdma/XT1028)
Moto G (falcon_cdma/XT1031)
Moto G (falcon_cdma/XT937C)
Moto G (falcon_umts/XT1008)
Moto G (falcon_umts/XT1032)
Moto G (falcon_umts/XT1034)
Moto G (falcon_umts/XT939G)
Moto G (falcon_umtsds/XT1033)
MOTO G (falcon_umtsds/XT1033)
Moto G Google Play edition (falcon_umts/XT1032)
Moto X (ghost/XT1049)
Moto X (ghost/XT1050)
Moto X (ghost/XT1052)
Moto X (ghost/XT1053)
Moto X (ghost/XT1055)
Moto X (ghost/XT1056)
Moto X (ghost/XT1058)
Moto X (ghost/XT1060)
Motoroi (sholest/Milestone XT720)
Motoroi (sholest/Motorola XT720)
Motoroi (sholest/XT720)
MOTOROLA ELECTRIFY 2 (cdma_yangtze/XT881)
Motorola Master Touch (umts_primus/XT621)
Motorola Master Touch XT621 (umts_primus/XT621)
Motorola MOT-XT681 (ironmaxct_cdma/Motorola MOT-XT681)
MOTOROLA RAZR M (smq_t/201M)
Motorola RAZR MAXX (cdma_spyder/Motorola RAZR MAXX)
Motorola Razr V (umts_yangtze/XT885)
Motorola Razr V (umts_yangtze/XT886)
Motorola XOOM 2 (fleming/MZ609)
Motorola XOOM 2 (pasteur/MZ617)
Motorola_i1 (iDEN/Motorola_i1)
MOTWX435KT (Triumph/MOTWX435KT)
MT620 (TAHITI/MT620)
MZ505 (Graham/MZ505)
MZ505 (graham_wifi/MZ505)
MZ604 (wifi_hubble/MZ604)
MZ605 (umts_hubble/MZ605)
MZ607 (fleming/MZ607)
MZ608 (fleming/MZ608)
MZ609 (fleming/MZ609)
MZ616 (pasteur/MZ616)
MZ617 (pasteur/MZ617)
Opus One (rubicon/Motorola Titanium)
Opus One (rubicon/Titanium)
Photon 4G (sunfire/ISW11M)
Photon 4G (sunfire/MB855)
Photon 4G (sunfire/Motorola Electrify)
Quench XT3 (XT502/Motorola-XT502)
RAZR D1 (hawk35_umts/XT914)
RAZR D1 (hawk35_umts/XT915)
RAZR D1 (hawk35_umts/XT916)
RAZR D1 (hawk35_umts/XT918)
RAZR D3 (hawk40_umts/XT919)
RAZR D3 (hawk40_umts/XT920)
Spice (sesame/XT300)
XOOM (stingray/Xoom)
XOOM (umts_everest/MZ601)
XOOM (umts_hubble/MZ601)
XOOM (umts_hubble/MZ605)
XOOM (wifi_hubble/MZ604)
XOOM (wifi_hubble/MZ606)
XOOM (wingray/Xoom)
XOOM 2 (pasteur/XOOM 2)
XOOM 2 ME (fleming/XOOM 2 ME)
XT303 (silversmart_umts/XT303)
XT305 (silversmart_umts/XT305)
XT311 (XT311/XT311)
XT316 (dominoq_umts/XT316)
XT316 (XT316/XT316)
XT317 (XT317/XT317)
XT319 (XT319/XT319)
XT320 (tinboost_umts/XT320)
XT321 (tinboost_umts/XT321)
XT389 (argonmini_umts/XT389)
XT389 (XT389/XT389)
XT390 (XT390/XT390)
XT530 (XT530/XT530)
XT531 (XT531/XT531)
XT532 (XT532/XT532)
XT535 (tinboostplus_umts/XT535)
XT535 (XT535/XT535)
XT550 (ArgonSpin/XT550)
XT550 (argonspin_umts/XT550)
XT555C (tinboostplus_cdma/XT555C)
XT556 (tinboostplus_cdma/XT556)
XT557 (tinboostplus_cdma/XT557)
XT560 (tinq_umts/XT560)
XT560 (XT560/XT560)
XT603 (cdma_pax/XT603)
XT605 (umts_jorian/XT605)
XT610 (umts_venus2/XT610)
XT615 (ironmax_umts/XT615)
XT615 (XT615/XT615)
XT626 (umts_irock/XT626)
XT627 (umts_irock/XT627)
XT687 (ironmaxtv_umts/XT687)
XT701 (choles/XT701)
XT711 (choi/XT711)
XT800+ (cg_tita2/XT800+)
XT800W (ttu_skt/XT800W)
XT806 (qilin/XT806)
XT860 (umts_solana/XT860)
XT882 (swordfish/XT882)
XT897 (asanti_c/XT897)
XT897S (asanti_c/XT897S)
XT901 (solstice/XT901)
XT905 (scorpion_mini_u/XT905)
XT910 (umts_spyder/XT910)
XT910K (umts_spyder/XT910K)
XT910S (umts_spyder/XT910S)
Click to expand...
Click to collapse
My fiances m8 got lollipop before the turbo. The reason I got this phone was this phone was supposed to get lollipop and the battery. I am so disappointed I will never get another Motorola phone.
sal_shawn said:
My fiances m8 got lollipop before the turbo. The reason I got this phone was this phone was supposed to get lollipop and the battery. I am so disappointed I will never get another Motorola phone.
Click to expand...
Click to collapse
Ok.
sal_shawn said:
My fiances m8 got lollipop before the turbo. The reason I got this phone was this phone was supposed to get lollipop and the battery. I am so disappointed I will never get another Motorola phone.
Click to expand...
Click to collapse
http://m.ebay.com/itm/like/171490729222?lpid=82&chn=ps&varId=470546673204
Problem solved! Mods feel free to lock this as it is now resolved!
Perfectly content to wait for bug free 5.1
Depends on what is important to you in a phone. I am always amazed to see people itching for the next update, etc, but honestly, if you always want the latest "greatest" (Personally, I cannot stand all the white in Lollipop), perhaps you will be disappointed in the Turbo. Perhaps once Vzw "approves" (like they have any power in that equation really) the update, it will be flawless, but i wouldnt hold my breath. As far as HTC goes, I can say I have never used an HTC phone with the same signal quality as its Moto counterpart. (Moto knows antennae/signal like no other) Also, If you read up on the Moto Maxx Lollipop update, it isn't too great. @adrenalyne can attest to that. Honestly, the real reason to be upset with a Turbo is the lack of bootloader unlock, as that would motivate Cyanogenmod to create a base that would translate to buttloads of Lollipop roms with the capability to return to stock KK Moto, am option you will not have once it updates as the keys do not allow reverting. Then, you would have the capability to experience it, realize it is not all its cracked up to be yet, and go happily back to where you are now. I know I went back to OSE KK happily from the best motox/droid ultra/maxx lollipop roms. the x8 architechture makes these newer moto phones amazing,(notice how Active Display does not kill your battery) but also has been the reason Lollipop has taken this long for those (msm8960dt) phones. Its hard to be patient, but I assure you, you aren't missing too much. and once you get lollipop, you will be stuck with it, for better or for worse.
zathus said:
http://m.ebay.com/itm/like/171490729222?lpid=82&chn=ps&varId=470546673204
Problem solved! Mods feel free to lock this as it is now resolved!
Click to expand...
Click to collapse
Actually, no, that's a GSM phone. If they're using the Turbo, they're likely on Verizon.
Not Motos fault
adrynalyne said:
Ok.
Click to expand...
Click to collapse
You act like this is even 1% motos fault and not Verizon (the biggest sticklers known to man.). If I remember right moto said awhile ago that the update had been delivered to VZW for inspection, but Verizon is so terrified that somebody might (gasp) root their phone that they hang onto it until they are pretty positive that there is no simple root method available
renegadeone8 said:
You act like this is even 1% motos fault and not Verizon (the biggest sticklers known to man.). If I remember right moto said awhile ago that the update had been delivered to VZW for inspection, but Verizon is so terrified that somebody might (gasp) root their phone that they hang onto it until they are pretty positive that there is no simple root method available
Click to expand...
Click to collapse
You got all that about me from word eh?
I am impressed!
Verizon is not necessarily to blame. They have approved update for the HTC and Samsung phones. I don't know why we haven't received the update. It seems people that have it aren't all that impressed and some are unhappy. Droid-Life days lollipop is a buggy mess. But I don't think we can blindly blame Verizon since they have approved it for other phones. That said... Don't buy a phone anticipating an update.
Sent from my Droid Turbo using Tapatalk
The source code for Lollipop has been out over 4 months now. It's absolutely ridiculous that this phone does not have Lollipop yet. It has a near stock android version and a widely used chipset. Samsung, HTC, and LG have ALL updated their skinned versions of android already. I don't care who's fault it is - Verizon or Moto - all that matters is that somebody screwed up with this delay. If we had an unlocked bootloader, we would already have Lollipop thanks to unpaid devs. My old phone and tablet are both running Lollipop thanks to these devs I speak of. This is the last time I buy a phone with a fully locked down bootloader and no hope of root. I just couldn't resist that battery!
ahaynes42 said:
The source code for Lollipop has been out over 4 months now. It's absolutely ridiculous that this phone does not have Lollipop yet. It has a near stock android version and a widely used chipset. Samsung, HTC, and LG have ALL updated their skinned versions of android already. I don't care who's fault it is - Verizon or Moto - all that matters is that somebody screwed up with this delay. If we had an unlocked bootloader, we would already have Lollipop thanks to unpaid devs. My old phone and tablet are both running Lollipop thanks to these devs I speak of. This is the last time I buy a phone with a fully locked down bootloader and no hope of root. I just couldn't resist that battery!
Click to expand...
Click to collapse
All the Roms are buggy as hell with some major issues from what I have read. The way I look at it is better to have a smooth os then the newest buggy os.
sent from "my kungfu is stronger then yours" XT1080
bigv5150 said:
All the Roms are buggy as hell with some major issues from what I have read. The way I look at it is better to have a smooth os then the newest buggy os.
Click to expand...
Click to collapse
The "it's still buggy" argument seems to be the general response when people like me are getting impatient. And while that does hold some truth, I think 5.0.2 has fixed most of the major issues. I'm running CM12 based on 5.0.2 on my Galaxy S4 and my Asus Tablet, and they both are running well now. There were some issues when the nightlies first came out, but 5.0.2 seems to be pretty stable now depending on what hardware you have.
https://plus.google.com/101651363550089117949/posts/UgxKuJxEEgo
Maybe good news? 5.1 for turbo? Maybe we get when nexus 6 is for sale at vzw?
I realize it could be untrue since it didn't come directly from moto or Verizon but interesting nonetheless.
Moral of the story? Buy a phone(or any product) for what it offers AT THAT TIME.
draco259 said:
Moral of the story? Buy a phone(or any product) for what it offers AT THAT TIME.
Click to expand...
Click to collapse
Or you can believe an advertised feature of the device being "Upgradeable to Lollipop" as listed in the original press release for the Droid Turbo. (link) Moral of the story for me is not to trust OEMs when they make upgrade promises. Sure they didn't give a specific timeframe when they promised Lollipop for the Turbo, but 4+ months after official release of source code is a joke.
There isn't a phone on Verizon with Lollipop and VoLTE (Advanced Calling) so the DT is not behind yet.
Character Zero said:
There isn't a phone on Verizon with Lollipop and VoLTE (Advanced Calling) so the DT is not behind yet.
Click to expand...
Click to collapse
Galaxy S5.
Character Zero said:
There isn't a phone on Verizon with Lollipop and VoLTE (Advanced Calling) so the DT is not behind yet.
Click to expand...
Click to collapse
Are you sure? I think you are wrong.
Here's the Advanced Calling list for Verizon. LG G3 is on the list and several users got Lollipop from Verizon.
http://www.verizonwireless.com/landingpages/advanced-calling-devices/
Several LG G3 users since February 23 have reported Lollipop update being available to them. NO, they were not part of soak test.
Verizon’s LG G3 Reported To Be In The Process of Getting Android 5.0.1 Lollipop Update
http://www.androidheadlines.com/201...ss-getting-android-5-0-1-lollipop-update.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hmm ok I forgot about Galaxy S5. Didn't know LG G3 update ws avaialable to everyone.
Character Zero said:
Hmm ok I forgot about Galaxy S5. Didn't know LG G3 update ws avaialable to everyone.
Click to expand...
Click to collapse
I'm not sure it is available for everyone. On further research may be a very slow rollout. But some people are getting it...
I been reading that we will be getting 6.0. Has anyone heard or read when? How is Marshmallow to Lollipop?
Sent from my XT1254 using Tapatalk
Claps1775 said:
I been reading that we will be getting 6.0. Has anyone heard or read when? How is Marshmallow to Lollipop?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
This was discussed in the link below, but the topic got moved to Q&A for some reason. I guess because it's a question? Your question will probably be moved too.
http://forum.xda-developers.com/showpost.php?p=65288659&postcount=4
This was my response:
Two bits of news, now in the 2nd week of February 2016...
I wouldn't be surprised if we got Marshmallow on all the Quarks by end of February.
_________________________
1) Moto Maxx: Android 6.0 tests are finally starting in Brazil
http://arena4g.com/2016/02/soak-test-moto-maxx.html
E-mail invitation to update the Moto Maxx | Source: Anonymous User:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Marshmallow soak tests are going on in Brazil for the "international" Quark, Moto X1225. What does this mean for Droid Turbo users?
The only difference in all the Quarks ("international" Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250, Droid Turbo XT1254) are the radios. (In fact the U.S. Moto Maxx XT1250 and Droid Turbo XT1254 are identical in every way, including the radios! Even the same FCC ID.)
Everything else is identical, which is why all the Quark ROMs work on all the Quarks -- including the Droid Turbo XT1254 (with unlocked bootloader):
CM12.1 ( @Skrilax_CZ dev)
Resurrection Remix ( @baybutcher27 dev)
Mokee (AOSP ROM, @baybutcher27 dev)
Nexus Experience (AOSP ROM),(EDIT: Nexus Experience has not been updated recently and does not work with Droid Turbo radio.)
Xperia Z5G
as well as custom kernel BHB27 ( @baybutcher27 dev).
Droid Turbo owners are using all of these above.
These Motorola soak tests usually last a week or two, then the official OTA is pushed out.
Point is, as soon as the soak test is over and the OTA officially hits the XT1225, the devs will update all the custom ROMs to Marshmallow and the Droid Turbo owners can install them. The custom ROMs all auto-detect the appropriate radios for each model. No need to wait for Verizon.
________________________________________________
2) Our Quark CM dev @Skrilax_CZ is already making Marshmallow kernel updates.
@baybutcher27 has also contributed. Here's the thread. One of them is titled "FIX:quark: Update filesystem config for 6.0"
baybutcher27 said:
@Skrilax_CZ
Nice work on the fix of the kernel. I try had no luck.
Are those the final changes before released the first test build?
As you just released those, I had not the time to test yet...
Check this before you release one... very minor fix...
https://github.com/bhb27/android_de...mmit/60f2c0f697bf2a97354d5d32d370859c9a76e6d2
https://github.com/bhb27/android_de...mmit/07bebb5d30cc58e27b2268779143677188e7df4a
config_screenBrightnessSettingMinimum in the 1° config_screenBrightnessDim as it is duplicated.
the last one is present on cm12 too.
:good:
Click to expand...
Click to collapse
Skrilax_CZ said:
Yes, there was a major patch to fix display HAL in the kernel. Thx for the rest, reviewed, pushed.
Click to expand...
Click to collapse
baybutcher27 said:
@Skrilax_CZ
I know you may have not finished...
But check...
this on the kernel
https://github.com/bhb27/android_ke...mmit/ea3c27bee339852dfb42cfac42b67e4192a57607
need this
https://github.com/bhb27/android_ke...mmit/7c1352298e00059769724b806b3a3c0fc47d4b9a
........
this I add in the pass on L...
https://github.com/bhb27/android_de...mmit/52b11efc1eeca7ea2f3a63912638d21f1dae95f6
and this M only
https://github.com/bhb27/android_ke...mmit/bed942732b86b5d46be8d0d679f3677c839e1bb4
https://github.com/bhb27/android_de...mmit/ba797f67f306bfbbf3b09c7cc4960b8ddabf6624
this may need blobs have not tested this yet... is easy to test with the ROM on the device, I test when have the ROM and the time...
https://github.com/CyanogenMod/andr...mmit/a39a9b51c93af54b3f0a46ae424631fa442daf7f
:good:
PS...
I find this minor thing...
https://github.com/bhb27/android_ke...mmit/eef0532fa70ae727ff5cdab262fed31d89edbcb5
Click to expand...
Click to collapse
Skrilax_CZ said:
Will review.
Click to expand...
Click to collapse
This has to mean CM13 (Marshmallow) is very close -- even without Motorola's Marshmallow OTA update! And Resurrection Remix is based on CM.
Either way, I wouldn't be surprised if we got Marshmallow on all the Quarks by end of February.
Click to expand...
Click to collapse
________
Now, obviously, if you want stock Verizon OTA, there's no estimate on when that will roll out.
Then you.
Sent from my XT1254 using Tapatalk
Claps1775 said:
I been reading that we will be getting 6.0. Has anyone heard or read when? How is Marshmallow to Lollipop?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
You can join MFN (Motorola Feedback Network) to be involved with testing future updates including the upcoming one. However, you must follow the rules they ask to continue to participate. A bonus is getting this update before the public even knows about it so you get surprised.
Sent from my DROID Turbo using Tapatalk
richii0207 said:
You can join MFN (Motorola Feedback Network) to be involved with testing future updates including the upcoming one. However, you must follow the rules they ask to continue to participate. A bonus is getting this update before the public even knows about it so you get surprised.
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
Joined them years ago.
Sent from my XT1254 using Tapatalk
Claps1775 said:
Joined them years ago.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Never got invited? That's odd. Perhaps the Motorola feedback app is detecting your system as nonofficial so it could be skipping you. Are you on stock? I ask because my GF was invited to test (stock software) and I still have not, as I have been on CM for quite a while.
Sent from my DROID Turbo using Tapatalk
I am on stock. Will check and see what phone I have on my profile. Might be the maxx still.
Sent from my XT1254 using Tapatalk
I don't think the Turbo will be getting Marshmallow at all. The Turbo 2 XDA page is a frenzy because something on Verizon leaked and other websites are saying MM rolling out right now for the Turbo 2 but the XDA users are saying nothing has come out. But keep note, the DROID Turbo and DROID Ultra were supposed to get LP. We got it, the Ultra? STILL has not received it, they are on 4.4.4 KK. So what happened to them MIGHT happen to us. Your only hope for MM is when @Skrilax_CZ releases CM13.
Aravindtop said:
I don't think the Turbo will be getting Marshmallow at all. The Turbo 2 XDA page is a frenzy because something on Verizon leaked and other websites are saying MM rolling out right now for the Turbo 2 but the XDA users are saying nothing has come out. But keep note, the DROID Turbo and DROID Ultra were supposed to get LP. We got it, the Ultra? STILL has not received it, they are on 4.4.4 KK. So what happened to them MIGHT happen to us. Your only hope for MM is when Skrilax releases CM13.
Click to expand...
Click to collapse
The Droid Maxx is also supposedly supposed to get Lollipop but it's been stuck on KitKat.
Once CM13 is released all other Quark ROMs will follow.
Latiken said:
The Droid Maxx is also supposedly supposed to get Lollipop but it's been stuck on KitKat.
Once CM13 is released all other Quark ROMs will follow.
Click to expand...
Click to collapse
Maxx/Ultra are all part of the same family, kind of like the Maxx 2 and Turbo 2. I am wondering why Maxx/Ultra never got LP. I am just rooting for @Skrilax_CZ. Another phone that never got LP was the z3v, but an actual, fully functioning build with stagefright patches was leaked onto the web for any z3v users to flash, but no official release from Verizon.
Aravindtop said:
Maxx/Ultra are all part of the same family, kind of like the Maxx 2 and Turbo 2. I am wondering why Maxx/Ultra never got LP. I am just rooting for @Skrilax_CZ. Another phone that never got LP was the z3v, but an actual, fully functioning build with stagefright patches was leaked onto the web for any z3v users to flash, but no official release from Verizon.
Click to expand...
Click to collapse
Considering Skrilax brought Lollipop to Quark devices before Motorola did, I'd say we can count in him. Especially since soak tests have begun on one of the Quark variants, the Moto Turbo.
Latiken said:
Considering Skrilax brought Lollipop to Quark devices before Motorola did, I'd say we can count in him. Especially since soak tests have begun on one of the Quark variants, the Moto Turbo.
Click to expand...
Click to collapse
Yeah, I just wish we had a BL unlock back then. But no matter how great CM13 will be. I will be dumping it and switching back to Computerfreeks ROM if MM is released for the Turbo. Moto Display is a nonexchangeable commodity. Ambient Display just doesn't match up to how simple Moto Display is.
Latiken said:
Considering Skrilax brought Lollipop to Quark devices before Motorola did, I'd say we can count in him. Especially since soak tests have begun on one of the Quark variants, the Moto Turbo.
Click to expand...
Click to collapse
Just leaving this here:
Skrilax_CZ said:
Otherwise, camera shim we need is only this and not victara hacks: "https://github.com/CyanogenMod/android_device_motorola_quark/blob/cm-13.0/libshims/moto_camera.c and I've not noticed we'd need to turn off video stabilization.
btw. I somehow missed that in cm-12.1, when recording video, there is a distortion in the sound. Same goes for cm-13.0.
Otherwise, looks like with that all basic features are working
Click to expand...
Click to collapse
He and @baybutcher27 are trading notes on CM13.
Aravindtop said:
Yeah, I just wish we had a BL unlock back then. But no matter how great CM13 will be. I will be dumping it and switching back to Computerfreeks ROM if MM is released for the Turbo. Moto Display is a nonexchangeable commodity. Ambient Display just doesn't match up to how simple Moto Display is.
Click to expand...
Click to collapse
I miss the Moto features greatly as well; CF was porting over the Moto features to work with one of his ROMs, but he discontinued it for now. (Due to personal matters)
I'm hoping someone picks up on his work and successfully ports them into a flash able zip. Once it works on one ROM, it should work on all.
That would make this phone 10000% perfect for me.
[Moto MAXX XT1225 / Droid Turbo XT1254][PREVIEW] CyanogenMod 13.0
http://forum.xda-developers.com/mot.../moto-maxx-xt1225-droid-turbo-xt1254-t3315912
Very tempted!
Wife's HTC M8 got the 6.0 update today. We should be close behind. Need to rsd lite to OEM. Could VZW make 6.0 lock our bootloaders?
Sent from my XT1254 using Tapatalk
So has anyone gotten actual confirmation that the verizon XT1254 will get MM? I know Moto says Droid Turbo but after what happened with the 2014 X, how are we to trust that MM will come to the carrier version of the turbo?
veloct said:
So has anyone gotten actual confirmation that the verizon XT1254 will get MM? I know Moto says Droid Turbo but after what happened with the 2014 X, how are we to trust that MM will come to the carrier version of the turbo?
Click to expand...
Click to collapse
I hear u I still have my droid maxx and that was suppose to get lollipop for almost two years before they finally just came out and said it's not happening. Thank God I finlaly gave up and bought a turbo at least I have an unlocked bootloader with this
Was wondering what the best ROMs are for the turbo?
Sent from my XT1254 using Tapatalk
It depends on what your preference is.
If you want an enhanced stock ROM computer freaks is the way to go.
If you are a fan of cyanogenmod than I reccomend CM13,
If you like lots of customization options Resurrection Remix is the way to go. All the ROMs available are great choices its just up to you which one really suits you best
jb14813 said:
Was wondering what the best ROMs are for the turbo?
Click to expand...
Click to collapse
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
http://forum.xda-developers.com/droid-turbo/development/roms-t3347701
Here's a list of all current ROMs for Quarks, Lollipop and Marshmallow. The threads are listed. You can go in, read user comments.
They work for the Moto Turbo, Moto Maxx, and Droid Turbo. Yeah, there's two Motorola Quarks called "Turbo". But these ROMs work for ALL the Quarks.
With previous phones there's always been custom roms released that bring customizing of pretty much everything. Loads of settings.. Status bar for instance, change the front, color, clock location etc.
Why is there none for the turbo, is it not possible?
I assume you have the DROID Turbo XT1254?
Is your bootloader unlocked? Are you rooted? If so...
List here:
http://forum.xda-developers.com/droid-turbo/development/roms-t3347701
Location here:
http://forum.xda-developers.com/moto-maxx
The Quark forums (XT1254 Droid Turbo/XT1250 U.S. Moto Maxx/XT1225 Moto Maxx/XT1225 Moto Turbo) were split last September 2015 into two forums because locked-down Droid Turbo XT1254 owners didn't want to see any dev work for the booloader unlocked Quarks (Moto Maxx/Moto Turbo -- YES, there's another Quark called "Turbo") in their forum.
So, due to XT1254 user requests XDA mods physically removed all the custom ROMs, kernels, etc for the bootloader unlocked Quarks and transferred them to another forum, called the "Moto Maxx" forum.
Ironically, less than two months later, in November 2015 Sunshine exploit unlocked the Droid Turbo bootloader (for SUTL-44). Suddenly Droid Turbo users WANTED all this dev work... but it's mostly still posted over in the OTHER Quark forum.
The Quark CM dev graciously replicated CM threads back over here even after being thrown out, but still most people go over there to discuss.
Some XT1254 users said they have now requested the forums be joined again, but I think it's low on the list of XDA mod priorities. Especially now that the recent OTA (SUTL-49) has locked out Sunshine procrastinators, less and less Droid Turbo XT1254 owners can participate.
Ahh that explains it. Thank you very much for the explanation and links. Yes I'm unlocked, rooted and running cm for now.