Related
Disclaimer: I've searched the forums day after day and have found nothing that helps me in any way.
Hey guys, I'll get right down to this:
I've got a Moto X VZW MM 32GB, initially shipped with 4.2.2 and running 4.4 as soon as I got it activated.
Everything on the Moto X works great, fluid graphics, fast app opening, battery (for the most part). But I've got a bone to pick with bluetooth, as well as Android OS.
First off, the bluetooth bugs, or what I'd like to call, The Blues.
Problems
- I have Pioneer Premier FH-P800BT, running great for the past 6 months or so. I originally had a Galaxy Nexus from VZW, with CM10.2 on it and bluetooth worked flawlessly, save for an obvious quality issue with phone calls/echo cancellation. A2DP and HSP/HFP would connect immediately as soon as the car came on. With my Moto X, HFP/HSP connects fine on powerup of the radio, but A2DP will not, and my phone shows "Connecting..." in bluetooth settings. When I first pair the phone (or re-pair), all profiles connect and audio works without a hitch. But every time after, it doesn't work that way. I can get around the issue by putting my radio in pair mode and turning on bluetooth, which essentially re-pairs the devices together, and that works. I think the biggest thing is that my radio connects HSP/HFP first, and then A2DP, and the phone is expecting both at the same time, and this causes the glitch I'm having. I haven't FR'd yet because this could be something that a FR won't fix (aka software issue that wasn't fixed by Moto).
- On all bluetooth devices with A2DP, sometimes the quality is great, sometimes it does what I like to call a "stucho" aka a stutter/echo. The best way I can explain it is if you've ever heard a record skip back and keep playing the same part, multiply that by like 100x. Or better example, for you Galaxy Nexus users (other phones too, if they do it) when your phone would freeze from being overloaded, and it ultimately crashed (non responsive to anything, screen won't come on, or maybe stuck on) and the audio get's hung. The sound does that on the Moto X, but it continues playing the track without pausing/skipping. It's extremely annoying, and mostly occurs when surfaceflinger is active (I'd assume that's what it is), as it's when anything animation-wise caused by user input occurs. I've also had the audio deteriorate in the same manner, but after it does the weird stucho effect, the audio slows down a bit, noticeable, like, listening to "We Found Love" by Rihanna sounded like a man singing it, and then it will speed up and go too fast after about a minute, and then resume normal playback. Despite completely pausing on my Galaxy Nexus, that phone never did have the audio issues this Moto X does, and it occurs on every A2DP device I've tried (BMW iDrive, Hyundai Sonata factory radio, Philips SBT series, my Pioneer headunit).
Second issue I'm having: Android OS
- I've tried ART and running Dalvik as the runtime, and on both, after weeks of running them, I notice that throughout the day, 3-4% battery drain per hour, with nothing in recent apps, wifi on, and all VZW software except for backup assistant disabled. I'm not complaining because I tend to make it to the end of the day with 2 1/2 hours SOT and and about 10% left on battery, but I'm curious as to why it's not making it any further. I don't have much installed. Dropbox, Facebook, Exchange account, Wallet, and other programs that don't run in the background (OS Monitor, Dots (game), etc). While my SOT can show 2 1/2 hours, it's only taking like 35% of the battery while Android OS shows like 20% or more, and shows CPU time around 1:45 hrs.
Any insight on either of these issues would be appreciated. I love the phone, everything else is perfect, but these 2 things are kinda irking me because I know this isn't the way the phone should be operating, moreso with the bluetooth bug.
Bump
My Bluetooth works fine on my old Motorola visor mount device...music and stuff goes through my radio.
As far as battery goes....go to the general section and read the "how's your battery life " thread. Every bit of troubleshooting and issues is already there.
Good luck!
Sent from my Moto X cellular telephone...
Glad to hear that yours is working great, mine usually does. I'll also add that call quality is top notch over bluetooth, much cleaner than on my Gnex. It's just A2DP sometimes will do the above mentioned, and it's so annoying. Using the headphone jack it is fine, it's specific to bluetooth.
As for battery tips, I've tried a good portion, short of rooting the device and greenifying it. I ran my Gnex forever, and I kid you not, swapped/flashed at least 60 roms, so I know what I'm doing in terms of de-bloat and rooting and such, but if not for these bugs, I'd be happy with the phone itself.
Thanks for the tips though I'll look, but in the mean time, anybody else ever noticed what I'm talking about?
kj2112 said:
My Bluetooth works fine on my old Motorola visor mount device...music and stuff goes through my radio.
As far as battery goes....go to the general section and read the "how's your battery life " thread. Every bit of troubleshooting and issues is already there.
Good luck!
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
I don't have stutter/echo problems but after taking a call on it and trying to go back to music the app acts like it is playing but no music is heard. I have to cycle BT on/off or cycle the power on the adapter. This is on a car adapter, the Kinivo BTC450. The adapter was flawless with an iPhone 5s and pretty good with a nexus 5. I am hoping it is 4.4 bugs and 4.4.2 will clear it up. It is supposed to launch Feb. 1 in Europe with 4.4.2 so hopefully we'll all see an update. I'm tinkering with the idea of going back to 4.2.2 to see if it is any better.
Sent from my XT1053 using Tapatalk
Well, I've solved 2 of the 3 problems I was having. Android OS no longer takes over my battery, and thankfully, more people today had posted that Snapchat was a battery hog on 4.4 (or on any OS version for that matter). And I wasn't just hallucinating, considering at 50% battery, SOT was ~ 1 hr while Android OS showed like almost 2 hours of being active, and percentages were like 33-35% for SOT, and 20-25% for Android OS. So I think now that 33mins of SOT at 90% battery and Android OS only showing 5% usage, issue's resolved
Bluetooth stuttering was seemingly with all audio services on my phone, but after I tinkered, I found anything that passed through the built-in EQ was stuttering when surfaceflinger was active. And oddly enough, only with bluetooth, and not even all the time. So in short, disabling the EQ on the phone seems to have fixed the weird jerking/echo/stucho sound period. I'll test a bit further, but so far that seems to be good.
Did a bit more testing in regards to A2DP issues, and found that in a newer Sonata (2013 Limited) the factory bluetooth links to A2DP and HSP/HFP within 30 seconds and both work properly. In my car though (Sentra) with an aftermarket Pioneer headunit (model number in the 1st post) the headunit must connect in a different matter, as HSP/HFP always connects immediately but A2DP tries to connect and it fails out. I have to re-pair the phone to the headunit each time to get both to pair properly. I'll test more with this but for now, this is still a bug, hopefully 4.4.2 will fix these issues.
So disabling the audio effects in the audio menu fixed the stuttering for you? Going to give that a sit tomorrow as well as uninstalling snap chat
Sent from my XT1058 using Tapatalk
I can confirm that for the past 2 days, with the Audio Effects/EQ disabled, I have no stutter with audio over bluetooth, it plays much smoother now. Also, uninstalling Snapchat has 100% resolved my Android OS battery drain. I was only getting an hour and a half of SOT with 30% battery left before, and now I successfully hit 50% battery with right at 2 hours SOT, so it's definitely made a huge difference. That's with dropbox, exchange account, facebook, and a few other random apps running. Worth a shot to see if it really does it for you, but YMMV
murso74 said:
So disabling the audio effects in the audio menu fixed the stuttering for you? Going to give that a sit tomorrow as well as uninstalling snap chat
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
balleron24z said:
Did a bit more testing in regards to A2DP issues, and found that in a newer Sonata (2013 Limited) the factory bluetooth links to A2DP and HSP/HFP within 30 seconds and both work properly. In my car though (Sentra) with an aftermarket Pioneer headunit (model number in the 1st post) the headunit must connect in a different matter, as HSP/HFP always connects immediately but A2DP tries to connect and it fails out. I have to re-pair the phone to the headunit each time to get both to pair properly. I'll test more with this but for now, this is still a bug, hopefully 4.4.2 will fix these issues.
Click to expand...
Click to collapse
Any resolution on this? I have the exact same problem with my Pioneer head unit. So annoying having to repair every time!
Only problem I'm having with Bluetooth in my car is that incoming phone calls break my audio connection. Instead of resuming, the audio ceases and i have to unpair and repair to get my audio back.
balleron24z said:
A2DP and HSP/HFP would connect immediately as soon as the car came on. With my Moto X, HFP/HSP connects fine on powerup of the radio, but A2DP will not, and my phone shows "Connecting..." in bluetooth settings. When I first pair the phone (or re-pair), all profiles connect and audio works without a hitch. But every time after, it doesn't work that way. I can get around the issue by putting my radio in pair mode and turning on bluetooth, which essentially re-pairs the devices together, and that works. I think the biggest thing is that my radio connects HSP/HFP first, and then A2DP, and the phone is expecting both at the same time, and this causes the glitch I'm having. I haven't FR'd yet because this could be something that a FR won't fix (aka software issue that wasn't fixed by Moto).
Click to expand...
Click to collapse
I am experiencing a similar bug.
Subaru Outback 2013 with Navigation (Fujitsu-10). I can pair the device just fine, but the automatic connection doesn't work at all. It will just say "Automatic connection has failed" on the navigation screen, and no indication on the phone.
That is what happens when I turn on the car when the phone has Bluetooth already enabled.
If I turn bluetooth off and back on again, it connects.
If I go into the bluetooth menu and tap CAR MULTIMEDIA, it connects.
The only thing that doesn't work is the *automatic* connection.
Like you, I previously had a Samsung Galaxy Nexus. I was running CM 10.2 and CM11 on it, both worked perfectly well with Bluetooth in the car.
Se7enLC said:
I am experiencing a similar bug.
Subaru Outback 2013 with Navigation (Fujitsu-10). I can pair the device just fine, but the automatic connection doesn't work at all. It will just say "Automatic connection has failed" on the navigation screen, and no indication on the phone.
That is what happens when I turn on the car when the phone has Bluetooth already enabled.
If I turn bluetooth off and back on again, it connects.
If I go into the bluetooth menu and tap CAR MULTIMEDIA, it connects.
The only thing that doesn't work is the *automatic* connection.
Like you, I previously had a Samsung Galaxy Nexus. I was running CM 10.2 and CM11 on it, both worked perfectly well with Bluetooth in the car.
Click to expand...
Click to collapse
If you search for "kitkat bluetooth issues" you will find multiple issues reported about different phones. In 4.4 Google went with a new BlueTooth implementation that broke compatibility with some of the devices. My Moto X DE (GSM) is at 4.2.2 and is perfectly compatible with my built-in car entertainment system, so I am probably never upgrading since downgrade from 4.4.2 is not possible.
JoeSchmoe007 said:
If you search for "kitkat bluetooth issues" you will find multiple issues reported about different phones. In 4.4 Google went with a new BlueTooth implementation that broke compatibility with some of the devices.
Click to expand...
Click to collapse
It was actually 4.2 where Android switched from BlueZ to BlueDroid. In 4.3 and 4.4 there were significant developments to "finish" that implementation. On my Nexus, 4.2 was worthless, but 4.3 and 4.4 worked great. It's certainly possible that Motorola botched something with their upgrade to 4.4 - or maybe Motorola had their own Bluetooth stack separate from AOSP.
My Moto X DE (GSM) is at 4.2.2 and is perfectly compatible with my built-in car entertainment system, so I am probably never upgrading since downgrade from 4.4.2 is not possible.
Click to expand...
Click to collapse
Downgrade on a Developer Edition is certainly possible, that's kind of the whole point of a developer edition!
Se7enLC said:
...
Downgrade on a Developer Edition is certainly possible, that's kind of the whole point of a developer edition!
Click to expand...
Click to collapse
I don't think this is correct. See this post: http://forum.xda-developers.com/moto-x/moto-x-qa/flashed-4-4-2-partition-table-gpt-bin-t2657468/post50555443 GPT flash is non-reversible and can prevent downgrade.
Here is another quote from now deleted thread:
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr :thumbup:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
If you have tested and working instructions on how to downgrade from 4.4.2 to 4.2.2 on 1053 I really would like know them.
JoeSchmoe007 said:
I don't think this is correct. See this post: http://forum.xda-developers.com/moto-x/moto-x-qa/flashed-4-4-2-partition-table-gpt-bin-t2657468/post50555443 GPT flash is non-reversible and can prevent downgrade.
Click to expand...
Click to collapse
Huh, that's news to me. Thanks for that link. This is what I get for thinking the Moto X would be just like a Nexus device.
To answer a few questions regarding this:
1: You most certainly CAN flash any ROM you wish to a DE Moto X, you just need to unlock the bootloader. When the BL is unlocked, it allows you to flash whatever you want. Look it up and do your homework, it's essentially a Nexus, without the AOSP out of the box.
2: The if 4.4 had so many bluetooth bugs, then why did my Gnex running AOSP 4.4 (the hacked together one that had driver bugs) work PERFECT, and I mean legit PERFECT with bluetooth on all devices I used? The point is moot with the bluetooth stack being bugged. Obviously Google tested this on MANY of their internal devices before releasing to Nexus devices and the AOSP branch. Y'all have no logic if you believe otherwise. I DO, however, agree that it's possible that Moto is using a non-standard or non-AOSP bluetooth stack, or they have modified the bluetooth config to the point where it doesn't work.
4.4.2 for the Moto X didn't fix my problem, although it supposedly did fix some bluetooth bugs. I can still use the phone with a 2013 Hyundai Sonata Limited's bluetooth, and it pairs perfectly every time. This seems to be a hardware-specific issue, as I see people with older model Pioneer/Kenwood/etc. Bluetooth 2.0 headunits having issues, as well as with some hands-free BT units too. But on newer vehicles, some radios don't have the problem. I'm gonna file another ticket with Moto and see if I can provide proof to the problem.
Guys....aside from keeping your warranty, the DE is no different than any other moto x with an unlocked bootloader. I don't know why people keep saying its any more than an x that gets a warranty.
You cannot downgrade with any less risk of bricking than any other unlocked moto x.
I hope this rumor of the dev edition being special in this regard ends quickly...before there's a tonne of "I'm bricked" threads.
No moto x is a nexus. There is no downgrading the bootloader without heavy risk. The stories you've read here about downgrading bricks WILL happen to the dev edition just like the other unlocked moto's. Mark my words.... please.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------
Careful who's advice you follow here guys....unless you have money to burn.
And yes...totally agree with the above.....do your homework.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 09:42 PM ---------- Previous post was at 09:39 PM ----------
Se7enLC said:
Huh, that's news to me. Thanks for that link. This is what I get for thinking the Moto X would be just like a Nexus device.
Click to expand...
Click to collapse
No. Downgrading is a HUGE brick risk. Trust me.
Moto x's are nothing like a nexus when it comes to the bootloaders.
Dev edition is like the rest....but you keep warranty. That's all!
Sent from my Nexus 5 using Tapatalk
kj2112 said:
Guys....aside from keeping your warranty, the DE is no different than any other moto x with an unlocked bootloader. I don't know why people keep saying its any more than an x that gets a warranty.
Click to expand...
Click to collapse
Because on Verizon, it's the only one that has an unlockable bootloader. Unlocked bootloader USED to mean that you can run any code you want on it, and recover mistakes using fastboot. And unless I'm mistaken, it still means that. The GPT thing is concerning, but there's still nothing preventing executable code from being run, it's just the partition table that is different, and the old ROM images cannot be written to it.
You cannot downgrade with any less risk of bricking than any other unlocked moto x.
Click to expand...
Click to collapse
How is that the case, though? Does fastboot stop working? Can you not re-flash a 4.4.2 image once provided by motorola? Do recovery consoles not flash? Can they no longer write to flash? And the real question - is it just because the older android images and recovery consoles do not understand GPT, or is there something actively preventing it? I know I've painted myself into a corner the last time I switched a drive to GPT and had a hard time finding a LiveCD that could mount it, but that was years ago. I'm crossing my fingers that it's only a matter of time before parted finds its way into CWM and TWRP.
I hope this rumor of the dev edition being special in this regard ends quickly...before there's a tonne of "I'm bricked" threads.
Click to expand...
Click to collapse
Agreed. Personally, I'm disappointed with the Moto X in this regard. I'm glad to now be informed of this, and I hope others look into it themselves as well.
Se7enLC said:
Because on Verizon, it's the only one that has an unlockable bootloader. Unlocked bootloader USED to mean that you can run any code you want on it, and recover mistakes using fastboot. And unless I'm mistaken, it still means that. The GPT thing is concerning, but there's still nothing preventing executable code from being run, it's just the partition table that is different, and the old ROM images cannot be written to it.
How is that the case, though? Does fastboot stop working? Can you not re-flash a 4.4.2 image once provided by motorola? Do recovery consoles not flash? Can they no longer write to flash? And the real question - is it just because the older android images and recovery consoles do not understand GPT, or is there something actively preventing it? I know I've painted myself into a corner the last time I switched a drive to GPT and had a hard time finding a LiveCD that could mount it, but that was years ago. I'm crossing my fingers that it's only a matter of time before parted finds its way into CWM and TWRP.
Agreed. Personally, I'm disappointed with the Moto X in this regard. I'm glad to now be informed of this, and I hope others look into it themselves as well.
Click to expand...
Click to collapse
I can't speak for what dev edition means on other phones....but for the Moto x, Dev edition means you can unlock bootloader, same as many other models....though your warranty is still good......and once unlocked, its EXACTLY the same as any other unlocked Moto x as far as flashing rules and RISKS.
I don't claim to be an expert on precisely why and what causes a brick, but I've read more than enough on here lately to know that downgrading from 4.4.2 is playing with fire. LOL
Funny....I just went to flash a 4.2.2 rom on my Nexus 7 the other day and got an error about incompatible boot loader (I was on 4.4.2 at the time) and I remembered, crap...that's right! So I flashed the previous bootloader version....then the 4.2.2 rom. Done ...10 minutes and zero issues. LOL. Not sure why Motorola had to make things harder/different.
Sent from my Nexus 5 using Tapatalk
Back to the original topic - I took the upgrade to 4.4.2 last night:
- Disabled things like XPosed
- Re-flashed stock recovery (using fastboot)
- Applied update
- Re-flashed CWM recovery
- Re-applied root and xposed
I didn't do anything else, apart from app upgrades that happened to come in. When I got in my car this morning it immediately automatically connected. Could be a coincidence, or maybe that upgrade fixed the bug.
EDIT: I was in and out of the car probably half a dozen times today, works perfectly now, auto-connected every time!
Hello all, I have an XT1063 (Global, single sim) running Lollipop (5.0.2). When I first bought it, it came with Kitkat and everything was working perfectly. I was in the insider program so I got to test drive Lollipop earlier than most people, which was nice and didn't really mess anything up the first few builds. The last build, however, changed that. This is the currently available build to everyone, since the beta program is over. Anyway, the problem is that my GPS will not lock on to satellites, making all map/traffic apps completely useless. As if this wasn't enough, the phone often drops my data connection (H+) and when switching from WiFi to celular data, it can take upwards of 5 minutes to get a data signal.
Could this be a problem with the modem fimwares? What are my options? I've thought about going back to stock, even reset everything from the settings menu once (didn't revert to stock kitkat, just factory settings on Lollipop.) If I absolutely have to go back to stock kitkat, how would I do it?
Any and all help would be much appreciated!
ivikd said:
Hello all, I have an XT1063 (Global, single sim) running Lollipop (5.0.2). When I first bought it, it came with Kitkat and everything was working perfectly. I was in the insider program so I got to test drive Lollipop earlier than most people, which was nice and didn't really mess anything up the first few builds. The last build, however, changed that. This is the currently available build to everyone, since the beta program is over. Anyway, the problem is that my GPS will not lock on to satellites, making all map/traffic apps completely useless. As if this wasn't enough, the phone often drops my data connection (H+) and when switching from WiFi to celular data, it can take upwards of 5 minutes to get a data signal.
Could this be a problem with the modem fimwares? What are my options? I've thought about going back to stock, even reset everything from the settings menu once (didn't revert to stock kitkat, just factory settings on Lollipop.) If I absolutely have to go back to stock kitkat, how would I do it?
Any and all help would be much appreciated!
Click to expand...
Click to collapse
Lollipop has a lot of issues... I have ****ty GPS lock too, but maybe that's because of my region.
I can agree with you on the frequent network drops though... Sadly, i have no solution for that, except to re-save the apn until you get the data working.
However, for the WiFi - cellular data switching, switch on "Aggressive Wi-Fi to Cellular Handover" in Developer Options.... It kinda solves my problem. (Still takes a minute for my data to work)
aditya.upadhyaya said:
Lollipop has a lot of issues... I have ****ty GPS lock too, but maybe that's because of my region.
I can agree with you on the frequent network drops though... Sadly, i have no solution for that, except to re-save the apn until you get the data working.
However, for the WiFi - cellular data switching, switch on "Aggressive Wi-Fi to Cellular Handover" in Developer Options.... It kinda solves my problem. (Still takes a minute for my data to work)
Click to expand...
Click to collapse
I see... It's sort of a relief knowing that I'm not alone in this. I've got a friend who has the same exact model, firmware, baseband, everything as me, but his phone is working without a problem...
Would you know of any guide i could follow to flash stock 4.4.4?
ivikd said:
I see... It's sort of a relief knowing that I'm not alone in this. I've got a friend who has the same exact model, firmware, baseband, everything as me, but his phone is working without a problem...
Would you know of any guide i could follow to flash stock 4.4.4?
Click to expand...
Click to collapse
There are a couple of them in the development section... But I suggest before you downgrade, why not backup your data and factory reset in lollipop itself? See if your problems continue or not... You'll be wiping data anyways when you are downgrading.
aditya.upadhyaya said:
There are a couple of them in the development section... But I suggest before you downgrade, why not backup your data and factory reset in lollipop itself? See if your problems continue or not... You'll be wiping data anyways when you are downgrading.
Click to expand...
Click to collapse
I did perform a factory reset earlier today, but the problems persisted, so I've now downgraded to 4.4.4 and will be on the lookout for these issues for a few days before updating again.
ivikd said:
I did perform a factory reset earlier today, but the problems persisted, so I've now downgraded to 4.4.4 and will be on the lookout for these issues for a few days before updating again.
Click to expand...
Click to collapse
That's cool. And you won't find any issues either... KitKat is rock solid stable.
Lollipop buggy. kitkat stable.
Guys
Which ROM below has the most stable connection to Verizon and also supports simultaneous voice & data?
Thanks
sam008 said:
Guys
Which ROM below has the most stable connection to Verizon and also supports simultaneous voice & data?
Thanks
Click to expand...
Click to collapse
It's all user preference. The most stable obviously is going to be a stock based rom like clean rom. If you want more tweaking options I like Chroma or Terminus(Both seem to be very stable). All those roms work with lte voice/data.
As long as you don't change your radio you should be good to go.
Sent from my Benzo'd Google N6 on VZ
And use Verizon messages if you don't want to worry about MMS and Group messaging working properly. Plus you can text over WiFi.
Lightrom is nice, plus it has app opps. Aosip seems very stable as well, and of course you can never go wrong with Cleanrom.
Right now I'm using Meanpop and I like it.
sam008 said:
Guys
Which ROM below has the most stable connection to Verizon and also supports simultaneous voice & data?
Thanks
Click to expand...
Click to collapse
Try Chroma. Seems stable as stable can be.
Sent from my Nexus 6 using Tapatalk
I'm coming from Shamu where the author simply disappeared. I'll do a wipe clean but after installing chroma, is it okay to do a titanium restore of all apps and data or would that cause performance issues? Sort of a hassle to install every app from scratch
Thx
sam008 said:
I'm coming from Shamu where the author simply disappeared. I'll do a wipe clean but after installing chroma, is it okay to do a titanium restore of all apps and data or would that cause performance issues? Sort of a hassle to install every app from scratch
Thx
Click to expand...
Click to collapse
With user apps, yes. However it is always recommended to not restore system apps when switching ROMs.
one more - with shamu, i had a problem over the last week whenever i rebooted my phone or moved from wifi back to lte data and the phone would not be able to get onto the data or voice network. It'll simply say cellular network not available.
will moving rom's help this issue or do I need to update radios? So far, i'm using the radios that came with the phone from play store
Thx
guys
i placed all the 4 files to install and it's been 30 mins but i still see the green circle and octagon on my screen. How long does the process usually take?
thx
CleanROM seems to fit what you want, although I am mostly testing mine out.
sam008 said:
guys
i placed all the 4 files to install and it's been 30 mins but i still see the green circle and octagon on my screen. How long does the process usually take?
thx
Click to expand...
Click to collapse
More info needed on what files and what you did exactly.
UNOFFICIAL AICP for the Sprint HTC One
Since @superfes is no longer using this phone, I figured I would post some unofficial builds of AICP (Android Ice Cold Project). The previous thread is intended for closure, so we can use this one. To be clear, I'm only compiling this ROM and will not be troubleshooting specific issues. I will do my best to troubleshoot, but no guarantees. Any help on this front is appreciated - I'm new to this and am interested in continuing to learn.
I'm planning on putting together a build once every week or two for personal use and will share that with you guys.
Obligatory disclaimer: I am not responsible for any trouble you may run into with flashing or otherwise using this ROM. Just because it is working well for me does not guarantee that you will have the same experience.
For those of you wondering what AICP is: http://aicp-rom.com
Download link
10/3/2015: Google drive: https://drive.google.com/open?id=0B0lza8kzVL9RSVNnUzdoT0J5QWs
Build notes
10/3/2015
- Fresh build from 10/3
- Tested service / data when moving and no issues
- Remember that I am not troubleshooting specific issues. I'm not a developer. If you wish to post a logcat or anything like that though, feel free and I will take a look but not necessarily be able to provide a solution
- Yes, the digital roaming display is still there. In fact, when you see digital roaming, this is a sign that you are in service. 'Sprint' shows up when you are roaming so it is backwards.
9/27/2015:
- Didn't make clobber so build that hasn't been updated since 9/19 does not show an update (i.e. build will say 9/19 in many places since that was my last full repo sync). For future builds I will do this but didn't feel like waiting that many hours today
- Cherry-picked tdhite's commit from PAC ROM: http://review.pac-rom.com/#/c/13403/
------This has fixed the com.android.phone crashing problem + service being dropped
------ Usable as a daily driver again!
- From a full day on this ROM it's running smoothly and without errors
- 'Digital Roaming' display-only issue persists (been there for a long time now - no surprises here), and it is not indicative of actually roaming. Go into settings / about / sim status to definitively determine what your service status is.
Reserved
Reserved for now
Appreciate any feedback you guys have too
I'll give it a try and let you know.
Sent from my One using Tapatalk
wmatheney said:
I'll give it a try and let you know.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I couldn't get a solid connection. It was roaming and when I toggled the network type to global, I lost connectivity. I toggled back to CDMA/LTE but still no connection. I toggled Airplane mode. Still no go. I then changed it to Global and got a connection finally, but it was still roaming.
I hope this helps.
Sent from my One using Tapatalk
Same issue I've noticed everywhere, no proximity sensor feedback when in dialer!
I'm not pushing the power button every time I get called or I make a call. Only reason I'm still glued to 4.4.4.
Tjis is my 3rd m7 on kk and lp Ota, all 3 on both revisions, same issue.
Sent from my One using Tapatalk
wmatheney said:
I couldn't get a solid connection. It was roaming and when I toggled the network type to global, I lost connectivity. I toggled back to CDMA/LTE but still no connection. I toggled Airplane mode. Still no go. I then changed it to Global and got a connection finally, but it was still roaming.
I hope this helps.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
The digital roaming issue is cosmetic - that one's to be expected (see build notes; you are probably not roaming). As for the connectivity drop, I haven't run into that. If that's happening infrequently and you can deal with the display issue, this ROM should be otherwise fine for service-related actions (calls/texts) in my experience over the last couple of days.
swerff said:
Same issue I've noticed everywhere, no proximity sensor feedback when in dialer!
I'm not pushing the power button every time I get called or I make a call. Only reason I'm still glued to 4.4.4.
Tjis is my 3rd m7 on kk and lp Ota, all 3 on both revisions, same issue.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Yes, that one is pretty annoying. I have also noticed it on AOSP LP ROMs including this one and just deal with it. Sorry to hear that's holding you back. If there's a fix out there and I come across it, I'll be sure post about it and add to the ROM if applicable.
You can port camera stock m7?
http://www.apkmirror.com/apk/htc-co.../htc-camera-7-30-581119-android-apk-download/
Vember31 said:
Yes, that one is pretty annoying. I have also noticed it on AOSP LP ROMs including this one and just deal with it. Sorry to hear that's holding you back. If there's a fix out there and I come across it, I'll be sure post about it and add to the ROM if applicable.
Click to expand...
Click to collapse
Do you need a log cat when doing anything? Sensor programs show the proximity responding as expected.
Sent from my One using Tapatalk
First of all, great ROM! Have used AICP on my Nexus 4 and my TF300T in the past and it's always been a nice, stable ROM. Just got one question about non-market apps. I've been unable to install any, though I do have the option enabled in the Security menu. From what I've been able to tell, I can start the install of non-market apks with no problem but then the install screen closes by itself and once or twice, I've seen a pop-up that says something about Anti-piracy software activated. Is there any way around this?
So I need Gapps with this ROM?
How about MM?
Any aicp work?
Sent from my One using Tapatalk
Just wanted to stop in and say thank you for uploading this to the site. I have had a hard time finding a good daily driver and this is perfect for my needs.
If you are still building weekly for your own personal use i would greatly appreciate you uploading here as well.
Also I like the inclusion of more cpu governors such as smartmax_eps, has been great for pokemon go
I need to convert my xt1095 from Brazil 6.0 to the regular xt1095 release. 6.0 has been around for a week or so, but I can't find the full firmware for it.
It does not exist yet. 6.0 for the xt1095 came out 3 days ago, you just need to have a little patience. The full images usually appear a week or 2 after the release.
AGISCI said:
It does not exist yet. 6.0 for the xt1095 came out 3 days ago, you just need to have a little patience. The full images usually appear a week or 2 after the release.
Click to expand...
Click to collapse
Thank you. Just hoping that the XT1095 version won't have the Bluetooth and LTE issues my phone has since updating. However, it looks like it's issues with marshmallow itself across many devices and manufactures.
supremekizzle said:
Thank you. Just hoping that the XT1095 version won't have the Bluetooth and LTE issues my phone has since updating. However, it looks like it's issues with marshmallow itself across many devices and manufactures.
Click to expand...
Click to collapse
What problem about Wi-Fi and Bluetooth? I'm on stock 6, but not have any issue Wi-Fi and Bluetooth
Lte and wifi
md07 said:
What problem about Wi-Fi and Bluetooth? I'm on stock 6, but not have any issue Wi-Fi and Bluetooth
Click to expand...
Click to collapse
WiFi displays one bar even when I'm a meter away from it. It sometimes goes 2 bars but not more than that.
The same happens with cellular network. Even though WiFi works perfectly with even a single bar, cellular line cuts off and even drops to no signal sometimes.
Inshort the reception is poor. Andditionally the phone has become a bit laggy. Bugs like absence of equalizer sybc with apps etc also exist
md07 said:
What problem about Wi-Fi and Bluetooth? I'm on stock 6, but not have any issue Wi-Fi and Bluetooth
Click to expand...
Click to collapse
A lot of people, myself included, have had issues with phones connecting to car radios via Bluetooth. Connection keeps dropping and phone calls don't work.
Abhiraj4u said:
WiFi displays one bar even when I'm a meter away from it. It sometimes goes 2 bars but not more than that.
The same happens with cellular network. Even though WiFi works perfectly with even a single bar, cellular line cuts off and even drops to no signal sometimes.
Inshort the reception is poor. Andditionally the phone has become a bit laggy. Bugs like absence of equalizer sybc with apps etc also exist
Click to expand...
Click to collapse
Wifi and Bluetooth work ok like same Lollipop on my phone. No issue found.
about laggy, i can see a liite in some app as Chrome, Dial (Phone), but in general, it's still OK
about Equalizer, you mean Audio Effect ? This move to Google music setting, not appear in Setting-Sound.
My Phone: XT1092, Android Marshmallow EU region
md07 said:
Wifi and Bluetooth work ok like same Lollipop on my phone. No issue found.
about laggy, i can see a liite in some app as Chrome, Dial (Phone), but in general, it's still OK
about Equalizer, you mean Audio Effect ? This move to Google music setting, not appear in Setting-Sound.
My Phone: XT1092, Android Marshmallow EU region
Click to expand...
Click to collapse
Equalizer: Its not in google play music settings either.
Cellular network: Any issues at your end?
You can just downgrade your phone to 5.1 and upgrade to 6.0 with the OTA file.
Funnnny said:
You can just downgrade your phone to 5.1 and upgrade to 6.0 with the OTA file.
Click to expand...
Click to collapse
Potential to brick doing it that way.
supremekizzle said:
Potential to brick doing it that way.
Click to expand...
Click to collapse
I downgrade from 6.0 to 5.1 with mfastboot and took the OTA to 6.0 again, no brick.
Gesendet von meinem XT1092 mit Tapatalk
supremekizzle said:
Potential to brick doing it that way.
Click to expand...
Click to collapse
No, because the bootloader is the same in 5.1 and 6.0 version. I thought I will brick my device the same way, but I took the leap and it's fine
Bender1987 said:
I downgrade from 6.0 to 5.1 with mfastboot and took the OTA to 6.0 again, no brick.
Gesendet von meinem XT1092 mit Tapatalk
Click to expand...
Click to collapse
Funnnny said:
No, because the bootloader is the same in 5.1 and 6.0 version. I thought I will brick my device the same way, but I took the leap and it's fine
Click to expand...
Click to collapse
What methods did you guys use to downgrade? Can I flash the whole system downloaded from Motorola?
Yes, I flashed the whole system using fastboot