Related
Hello everyone! This is my 3rd day of tinkering with the phone and since I can't handle it I'm asking for help. I'm a noob who read a lot, tried and apparently messed up.
I bought a new HTC One from T-Mobile in Poland, branded with CID T-MOB101 and Hboot 1.44. Everything worked fine but the phone still had Android 4.1.2 and no update available. I decided to get rid of the brand and get international stock version to be able to receive OTAs. I unlocked bootloader with htcdev.com, installed TWRP 2.6.3.3, achieved s-off using revone, changed CID to HTC___001 and used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed . My phone did not see OTA so I applied updates manually in following order:
OTA_M7_UL_JB_50_HTC_Europe_1.29.401.12-1.28.401.7_release_315849_signedp7vl8dqsvls0h1t0.zip
OTA_M7_UL_JB_50_S_HTC_Europe_2.24.401.1-1.29.401.12_P2_release_324936_signedma8j1sa3e2o09s35.zip
OTA M7 UL JB 50 S HTC Europe 2.24.401.8-2.24.401.1 Release 331108tottoh71qygw07hf
OTA M7 UL JB43 SENSE55 MR HTC Europe 3.62.401.1-2.24.401.8 Release 338160gxmo5sd9337kadux
After each OTA i tried to look for updates in phone's settings and found only two little updates (few MBs) that did not lead to bigger ones; I believe it was after first and third OTA.
After all this I started having WiFi issues. The phone stayed connected to my WiFi the whole time but after few minutes pages would not load, games would not connect. Resetting the connection would help for another few minutes (or less). Factory reset seemed to help a bit, the WiFi was able to keep the connection yet it 'paused' from time to time. By 'pause' I mean lose the connection for a second and regain right after, e.g. I could connect to games such as Hay Day, but after a ~minute I would lose the connection and have to reconnect (in game, without touching phone's settings) and redo last X seconds of game.
Because of that I went and applied ARHD 31.6 custom rom and hoped for the best. The situation remained the same so I flashed ARHD 41.0, yet the problem still remains.
In the end I downgraded my Hboot so it goes back to 1.44 and used the RUU I used the first time, after that I changed CID back to T-MOB101 and applied my full backup I saved by booting (prior to flashing) TWRP before I changed anything in the phone.
I did full wipe every time I changed the system and I did factory reset multiple times.
As of now I am on my backup with
Android 4.1.2
Version 1.29.111.16 CL175271 release-keys
Radio 4A.13.3231.27_10.31.1131.05L
and my WiFi is unstable. I can browse internet, watch YouTube or do things like that, yet I cant play games requiring constant internet connection, such as Hay Day.
So my question is: What do I do to get it to work as it used to at the beginning? I would prefer having the newest Android version, but at this point I simply need a working phone so if anyone has a solution that would work on my current system or by flashing a new one I will be extremely grateful.
I've been having the same issue. Thought it was just me because I've looked for a solution ever since the Jelly Bean update. Mine is a Sprint One and worked perfect with the original firmware. Once updated wifi connected and would randomly drop for a few seconds and reconnect. I've noticed it's router specific. I had a Linksys wrt160 that had a problem at home, but at the office the Cisco E2500 works fine. I swapped my home out with an Asus RT-N12 that has the problem too, but not as bad. Was hoping KitKat would fix the issue, but it didn't. I've worked with HTC support for a while and they said the new rom's have updated wifi drivers so there must be some compatibility issue with it.
Think the best bet is a custom rom that has all the new kitkat features but the old wifi (and BT since the new one doesn't load the contacts in my car) drivers. Someday, I'll take the time to figure out making my own rom.
same boat
1sae said:
I've been having the same issue. Thought it was just me because I've looked for a solution ever since the Jelly Bean update. Mine is a Sprint One and worked perfect with the original firmware. Once updated wifi connected and would randomly drop for a few seconds and reconnect. I've noticed it's router specific. I had a Linksys wrt160 that had a problem at home, but at the office the Cisco E2500 works fine. I swapped my home out with an Asus RT-N12 that has the problem too, but not as bad. Was hoping KitKat would fix the issue, but it didn't. I've worked with HTC support for a while and they said the new rom's have updated wifi drivers so there must be some compatibility issue with it.
Think the best bet is a custom rom that has all the new kitkat features but the old wifi (and BT since the new one doesn't load the contacts in my car) drivers. Someday, I'll take the time to figure out making my own rom.
Click to expand...
Click to collapse
I have tried about every Rom, Firmware, RUU out there and cant get mine to work
robbie09 said:
I have tried about every Rom, Firmware, RUU out there and cant get mine to work
Click to expand...
Click to collapse
For now I'd recommend contacting HTC support and create a ticket so they know this problem is more widespread. That way all the new roms out there would have a working WIFI driver.
thanks
1sae said:
For now I'd recommend contacting HTC support and create a ticket so they know this problem is more widespread. That way all the new roms out there would have a working WIFI driver.
Click to expand...
Click to collapse
that's exactly what ive done on 2 different occasions, the last time this evening and they advised i exchange with my carrier
robbie09 said:
that's exactly what ive done on 2 different occasions, the last time this evening and they advised i exchange with my carrier
Click to expand...
Click to collapse
That's odd, when the first tier support couldn't figure it out they opened a ticket for me with higher level techs and they had me save a bunch of capture logs when the drops happen to email them. The carrier would be useless on this.
1sae said:
That's odd, when the first tier support couldn't figure it out they opened a ticket for me with higher level techs and they had me save a bunch of capture logs when the drops happen to email them. The carrier would be useless on this.
Click to expand...
Click to collapse
I sent them a bunch of logcats as well and they told me to exchange my phone with my carrier
Sent from my HTC One using XDA Premium 4 mobile app
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!
Hi,
New version of AA is in the Play Store! v1.5.100945 v1.6.226040 (2710411-release).
After initial tests, it's seems to be more robust in connectivity with the HU... less disconnections and more fast connection. Even more, more robust with the HeadUnit Android App (thank you, Mike!).
:victory:
Please, post here yours feelings.
manos78 said:
Hi,
New version of AA is in the Play Store! v1.5.100945.
After initial tests, it's seems to be more robust in connectivity with the HU... less disconnections and more fast connection. Even more, more robust with the HeadUnit Android App (thank you, Mike!).
:victory:
Please, post here yours feelings.
Click to expand...
Click to collapse
This version is very old. New version 1.6.209040
Hi
Where can we found version 1.6
on the store there is the v 1.5
No update found
My working condition are moto g titan on Cyanpop 6.2 and vw mib2
Some times working good but some times it's hard to operate.
The problem appears when we have a poor signal on the data connection.
jpnos said:
Hi
Where can we found version 1.6
on the store there is the v 1.5
No update found
My working condition are moto g titan on Cyanpop 6.2 and vw mib2
Some times working good but some times it's hard to operate.
The problem appears when we have a poor signal on the data connection.
Click to expand...
Click to collapse
https://www.apkmirror.com/apk/googl...roid-auto-1-6-209040-2691474-release-release/
I already found this
but it's only for arm64
So not for my device
Thank's
The ARM64 version of 1.6 appeared to work on my Priv. Version v1.5.100945 shows a date of March 23, 2016 on the Web Play Store and December 2, 2015 on the Priv Play store. Go figure.
I also received an email from Google yesterday saying 1.6 would be released yesterday and that it would fix my connection problems. It didn't. The version on the mirrors didn't anyway.
manos78 said:
Hi,
New version of AA is in the Play Store! v1.5.100945.
After initial tests, it's seems to be more robust in connectivity with the HU... less disconnections and more fast connection. Even more, more robust with the HeadUnit Android App (thank you, Mike!).
:victory:
Please, post here yours feelings.
Click to expand...
Click to collapse
Thanks for posting and testing.
I have it running on my Nexus 9 and Nexus 6p, both running most recent Android N dev preview.
The old self mode works reliably again now ! (SP2P on latest released Jan 20 version of my Headunit app).
So Google fixed the Android Auto over Wifi stuff ; perhaps some OEMs are working on AA over Wifi now.
Sadly, didnt fix any issues I had with my 2016 vw and note 4. AA still has alot of work to do
mikereidis said:
Thanks for posting and testing.
So Google fixed the Android Auto over Wifi stuff...
Click to expand...
Click to collapse
Hi Mike,
Can you explain more about "AA over WiFi"?
A new build is available (1.6.226040 (2710411-release)).
manos78 said:
Hi Mike,
Can you explain more about "AA over WiFi"?
Click to expand...
Click to collapse
AA can run over Wifi instead of USB. Google has never announced this. Apple has, for CarPlay, but theirs is still in perpetual beta.
I've done it, but it can lag a bit if your airwaves/wifi is congested.
It also always disconnects sooner or later, but I could probably nake it auto-reconnect with some work.
IMO, the practicality of AA over Wifi (or Apple CarPlay) is limited. Phones usually need to charge, particularly with GPS, Wifi, BT, data and phone calls and multiple apps all sucking up battery and getting the phone warm.
mikereidis said:
AA can run over Wifi instead of USB. Google has never announced this.
IMO, the practicality of AA over Wifi (or Apple CarPlay) is limited. Phones usually need to charge.
Click to expand...
Click to collapse
I know, this is the reason I always connect my phone when driving my car.
However, for 10 minutes or less driving time, why I need to connect the phone for charging? AA is by far, more powerful than the car's MIB head. So, I prefer to have the option of using WiFi when the USB is not connected.
After this discussion, please, can you explain how to run AA over Wifi?
manos78 said:
After this discussion, please, can you explain how to run AA over Wifi?
Click to expand...
Click to collapse
No info?
I like to use a Qi charger with my phone and AA over Wifi. If this possible?
G960U1UES2ARF4 Security Patch Level June 1, 2018
Received 6-25-2018
No new features apparent.
Calls over WiFi still does not work
Live FM via NextRadio still does not work - I stand corrected. Live FM radio via NextRadio does work on this update.
Airstream25 said:
G960U1UES2ARF4 Security Patch Level June 1, 2018
Received 6-25-2018
No new features apparent.
Calls over WiFi still does not work
Live FM via NextRadio still does not work
Click to expand...
Click to collapse
Sad!
Do you know if the 960U roms have this options?
Airstream25 said:
G960U1UES2ARF4 Security Patch Level June 1, 2018
Received 6-25-2018
No new features apparent.
Calls over WiFi still does not work
Live FM via NextRadio still does not work
Click to expand...
Click to collapse
I'm on the g960u1, just updated to ARF4. Calls over WiFi have been working for me since Feb update. Live FM works!! for me on Nextradio.
pbsavages said:
I'm on the g960u1, just updated to ARF4. Calls over WiFi have been working for me since Feb update. Live FM works!! for me on Nextradio.
Click to expand...
Click to collapse
Are you on Verizon?
Airstream25 said:
Are you on Verizon?
Click to expand...
Click to collapse
T mobile
pbsavages said:
T mobile
Click to expand...
Click to collapse
Ok
On Verizon Calls over WiFi still does not work
Live FM via NextRadio still does not work
Airstream25 said:
Ok
On Verizon Calls over WiFi still does not work
Live FM via NextRadio still does not work
Click to expand...
Click to collapse
Wait.. 960u1 is unlocked yes? Isn't the updates from Samsung? I mean we have the same hardware and same software. FM should work, it's not dependent on the carrier while WiFi calling night be.
FM live radio is not carrier dependent and does work on the latest update.
So this update repeatedly caused my GS9 to freeze and reboot, kept getting System UI and Samsung Pay Framework has stopped working messages. Finally it reboot and when it came back up, half my **** has been reset to factory. Nova is back to defaults with no backups (I did have at least one saved for my layout), my navbar buttons were put back to defaults, volume set back to default, brightness back to default, even some apps back to their defaults like Chrome.
I am on Tmobile and I know that they had problems with the May patch so they stopped rolling that out but holy ****. I am so damn annoyed that I now have to set all this **** back up again after a SECURITY PATCH. Not even any new features.
Smfh, just be wary if you are on the GS9 from Tmobile and havent updated yet. Prepare to possibly run into problems and back up what you can. Going to spend around 2 hours setting everything up again and reorganizing my apps.
DrRyder said:
So this update repeatedly caused my GS9 to freeze and reboot, kept getting System UI and Samsung Pay Framework has stopped working messages. Finally it reboot and when it came back up, half my **** has been reset to factory. Nova is back to defaults with no backups (I did have at least one saved for my layout), my navbar buttons were put back to defaults, volume set back to default, brightness back to default, even some apps back to their defaults like Chrome.
I am on Tmobile and I know that they had problems with the May patch so they stopped rolling that out but holy ****. I am so damn annoyed that I now have to set all this **** back up again after a SECURITY PATCH. Not even any new features.
Smfh, just be wary if you are on the GS9 from Tmobile and havent updated yet. Prepare to possibly run into problems and back up what you can. Going to spend around 2 hours setting everything up again and reorganizing my apps.
Click to expand...
Click to collapse
Thanks for the warning. I remember a few years ago on my Galaxy Alpha every device software update used more RAM - the Operating System got larger and a little slower although it was a fast phone.
I am using a TMo S9 which I just got a few days ago ....and noticed the HUGE size of the update.
I have great battery life using a Tmo S9 on Metro PCS - possibly because most of the automatic Apps that load from TMO never loaded because it was never on the Tmo Network [ brand new ].
I noticed one bug that the Phone App is supposed to switch to a pop up [ like Note and Alpha ] if you want while using other Apps or Internet during a call- call turns into an Icon which you can move OR touch again to get full screen- [ it's in the options on the dial screen ] - BUT the update does not fix that or other bugs apparently.
See menu below for' pop up option '.
Great on Note and Alpha for calls when you need to jump on Internet quick during a call..but does not work on S9 ...
One description said the Update aids in' Camera Stabilization ' and security but I think the Camera is just so people will accept download ..lol.
Any decreased battery life or radical differences in Operating System having a much larger O.S. and having less free RAM ?
That's what hapoened with Alpha ..it just slowed down a hair ... less RAM .
Why do they need almost .8 Gig ?
robertkoa said:
I noticed one bug that the Phone App is supposed to switch to a pop up [ like Note and Alpha ] if you want while using other Apps or Internet during a call- call turns into an Icon which you can move OR touch again to get full screen- [ it's in the options on the dial screen ] - BUT the update does not fix that or other bugs apparently.
See menu below for' pop up option '.
Click to expand...
Click to collapse
My G960U1 is on a T-Mobile, still on February update(Just this morning received the following update).
(G960U1UES2ARF4/GG960U1OYM2ARF4/G960U1UES2ARF4 696.28MB) Not yet updated.
WiFi Calling - Works
Minimize App down to Icon - Works
Minimize Call App to Icon - Works
(You just need to know how to do that)
=====================
1•During a call, split the screen.
2•Choose the app you want to use during call.
3•Select a Call App.
4•Press on Split Menu.
5•Place Call App on the top layer
(Now you can move it around the screen).
6•Tap on Minimize Button
(Now you can move the App Icon around the screen).
Or even do the opposite, put another app on top of the Call App(See attachment).
You can do that with most of the apps.
FM Chip is ACTIVATED/UNLOCKED
UPDATE!
I did an update as soon as I got to the WiFi.
The first thing that I checked was the FM Chip using NextRadio. "Listen To FM" appeared and was able to use "Basic Tuner" to tune to local stations.
Some people say here that FM Chip still doesn't work.
Make sure you plug in your headphones. Because without it it will NOT work.
Have not tested anything else so far. Maybe will update this post in the future.
I have t-mobile and updated 2 nights ago and it's been working good for me so far. No hickups or anything that I've noticed. GS9+
Ffs will they ever fix the **** battery life of the exynos chipped phones ?
I'm on Exynos S9 UK unlocked and was happy to see that I now have VoLTE after the update, even get a little "HD" call quality icon when using it. Network is EE.
baraban0 said:
My G960U1 is on a T-Mobile, still on February update(Just this morning received the following update).
(G960U1UES2ARF4/GG960U1OYM2ARF4/G960U1UES2ARF4 696.28MB) Not yet updated.
WiFi Calling - Works
Minimize App down to Icon - Works
Minimize Call App to Icon - Works
(You just need to know how to do that)
=====================
1•During a call, split the screen.
2•Choose the app you want to use during call.
3•Select a Call App.
4•Press on Split Menu.
5•Place Call App on the top layer
(Now you can move it around the screen).
6•Tap on Minimize Button
(Now you can move the App Icon around the screen).
Or even do the opposite, put another app on top of the Call App(See attachment).
You can do that with most of the apps.
Click to expand...
Click to collapse
Thanks- yes I see that and can shrink it to a functional mini dial screen or down to Icon - very good.
Have you noticed any problems with the ARF 4 Update - I am stalling it cause my S9 is very very good on battery - SOT very long and I am afraid ARF 4 will change that.
ALSO - the one user who h.g ad trouble with ARF 4 - there is an even NEWER update now ...go right to that one maybe nefore resetting everything (?).
Anyway - I hope these Updates are efficient so they don't heat up the phone AND NOT add background processes which can't be stopped.
Meaning - don't show up in Battery Stats but increase Device Idle current draw on Battery etc .
Baraban - I have the SAME Tmobile Device but use on Metro and am stalling the Update because:
My performance ESPECIALLY SOT on 4GLTE is very very good .
Are you getting great SOT on your Device and that's why you did not Upgrade ?
750 meg for security patches sounds odd to me...
Not a Dev but somehow I don't think I need it if phone working great now ...lol.
I have no sensitive Info on my phone...
Why no July and August security updates for 960U1 ? even older Nexus 5X have Aug update..
gmp009 said:
Why no July and August security updates for 960U1 ? even older Nexus 5X have Aug update..
Click to expand...
Click to collapse
google devices naturally are always updated first obviously lol typically if u want speedy updates samsung isnt recommended
elliwigy said:
google devices naturally are always updated first obviously lol typically if u want speedy updates samsung isnt recommended
Click to expand...
Click to collapse
Samsung also updated 960U but not U1..
Hi all guys, I've been missing a long time from here, so please be care enough to forgive me if I posted the thread in the wrong place.
I'm currently using Android Auto and enjoying very much the amazing work made from Gabriele (AAAD, of which I payed the PRO version in order to help the developer's job).
I'm running AA version 6.3.611314 (downgraded from 6.4, because otherwise AAAD didn't work, since AA 6.4.... doesnt' let you show the apps installed apart from the official ones); Ford Focus Active with Sync 3 updated to 3.4 version, a Galaxy Note 20 Ultra5G (European) with Android 11.
Everything works fine, even AAAD installed programs.
The only problem is that every time I unlock the phone it disconnects from AA and then it starts again from the beginning. I opened the DEv Options in the phone settings and chose as standard setting for the usb - File transfer / Android Auto.
My question is: Why this disconnections happen and HOW can I fix it? I currently drive with the phone unlocked and, useless to say, it doesn't charge as much as it would if the screen had been off. I alredy tried with other cables, even with a Sam S9+ original one.
Thanks in advantage, any help is appreciated.
Same here, S10+ latest official, AA 6.4.611714-release, Ford Sync 3.x .
Doing so for about a week (or some more). At phone unlock, AA is crashing to Sync interface, and phone is asking for permissions in order to start Android Auto again (need to press Allow, otherwise AA will not start!)
Thx!
Same here , s10
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
gidannifico said:
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
Click to expand...
Click to collapse
I can confirm that the issue is related to the last Sammy update , I have downgraded to may update , now aa works perfect
Guys, Google just updated the discussion thread three days ago:
Thanks for all the reports. We informed the Samsung team and they have applied a fix on an upcoming upgrade as part of the regular July maintenance release to resolve this issue. Please keep checking for system updates on the device.
Click to expand...
Click to collapse