So my T-Rex finally arrived yesterday.. and I figured I'd get it set up quickly and start playing with it.
Phone: Galaxy S9/VZN/Android 10.
Watch: Amazfit T-Rex.. firmware 0.0.1.41
Loaded up the Amazfit software and it paired just fine.. and it immediately saw the new firmware (0.0.1.77) an attempted to update. At this point it starts.. gets partially through, locks up and the watch reboots. Upon reconnecting.. it generally tries again.. and again.. and again. I eventually got it to stop trying to upgrade for a bit, and saw some other weirdness.. but it wasn't stable long enough to really mess with it.
So.. I pulled out an old phone that had been factory wiped.. Galaxy S7 running Android 8. This time the update seems to succeed.. but it doesn't see the newer firmware when you check for updates. Also, I don't want to switch to an S7 on Android 8.
I tried Notify & Fitness.. and I have downloaded the latest firmware (0.0.1.79, I believe).. I'm tempted to try updating it from the S7 manually.. then seeing if it works better with the S9.
Any bright ideas? I'm surprised that this is the only place that has anything CLOSE to a support community for these watches - so thanks for existing!
I'm dangerously close to putting it right back in the box and sending it back.. because their support emails say 'average 2 days to reply'.. yikes.
Update - used Notify and Fitness on the older S7 to manually update it to 0.0.1.79.. which took.
When connecting it back to the S9 (the actual phone I need it to work with!), it showed the correct firmware but still keeps trying to update SOMETHING (resource library, I believe).. which causes the crash/loop again.
Went back and updated the resource library from the S7.. and when connecting back to the S9 it got stuck in some 'open app and check for updates' screen. Connected back to the S7 and it's happy.
Connecting back to the S9 keeps triggering an attempted (and failed) update. I can't get the thing stable enough to even see if it's worth keeping
Also - when I had it functioning enough to play with it for a few.. it listed almost all my apps for notifications EXCEPT my actual SMS program of choice.
This thing is a mess.
biggator6 said:
Update - used Notify and Fitness on the older S7 to manually update it to 0.0.1.79.. which took.
When connecting it back to the S9 (the actual phone I need it to work with!), it showed the correct firmware but still keeps trying to update SOMETHING (resource library, I believe).. which causes the crash/loop again.
Went back and updated the resource library from the S7.. and when connecting back to the S9 it got stuck in some 'open app and check for updates' screen. Connected back to the S7 and it's happy.
Connecting back to the S9 keeps triggering an attempted (and failed) update. I can't get the thing stable enough to even see if it's worth keeping
Also - when I had it functioning enough to play with it for a few.. it listed almost all my apps for notifications EXCEPT my actual SMS program of choice.
This thing is a mess.
Click to expand...
Click to collapse
Hi , I’m facing a same problem with brand new trex with 0.0.1.77. What should I do if IPhone?
I decided to use the workaround to scrap the amazfit app and just use notify and fitness. No more issues on the S9
I followed the directions at freemyband.
No idea about iPhones
biggator6 said:
I decided to use the workaround to scrap the amazfit app and just use notify and fitness. No more issues on the S9
I followed the directions at freemyband.
No idea about iPhones
Click to expand...
Click to collapse
Mine is hardware problems maybe, now sending back to manufacturer to replace a new one....
biggator6 said:
Update - used Notify and Fitness on the older S7 to manually update it to 0.0.1.79.. which took.
When connecting it back to the S9 (the actual phone I need it to work with!), it showed the correct firmware but still keeps trying to update SOMETHING (resource library, I believe).. which causes the crash/loop again.
Went back and updated the resource library from the S7.. and when connecting back to the S9 it got stuck in some 'open app and check for updates' screen. Connected back to the S7 and it's happy.
Connecting back to the S9 keeps triggering an attempted (and failed) update. I can't get the thing stable enough to even see if it's worth keeping
Also - when I had it functioning enough to play with it for a few.. it listed almost all my apps for notifications EXCEPT my actual SMS program of choice.
This thing is a mess.
Click to expand...
Click to collapse
Hi,
Can you share where did you obtain a copy of the firmware?
Related
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
jc_hwz said:
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
Click to expand...
Click to collapse
My wife got hers a week ago and has till this Friday to take it back. This started happening a few days ago Also. Random. I know she also got that security update just a couple days ago
Sent from my HTC One_M8 using XDA Free mobile app
jc_hwz said:
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
Click to expand...
Click to collapse
I have been having the same issue. I have had the phone since release and haven't had any problem, until about a month ago. It has rebooted a few times randomly. I am completely stock non-rooted.
I got one time today when I opened the YouTube app. I uninstall the update for the YouTube, and see what is going on
So I've noticed this happening for a few weeks now. Thought something was wrong with the phone and did a warranty replacement. New phone (not referb) does the same thing, just not as often. I think maybe it's an app running in the background now that had a bad update. I'm in the process of removing apps to see if it still happens.
1sae said:
So I've noticed this happening for a few weeks now. Thought something was wrong with the phone and did a warranty replacement. New phone (not referb) does the same thing, just not as often. I think maybe it's an app running in the background now that had a bad update. I'm in the process of removing apps to see if it still happens.
Click to expand...
Click to collapse
It has happened last mid night again. In today moring, I found my phone restart one time, because I saw the popup notice for reminding the back cover that means the phone restart already. Please tell us what happen after you remove the apps. I think it is the software problem rather than the hardware problem. I don't want to get replacement phone because it is refurbished phone.
jc_hwz said:
It has happened last mid night again. In today moring, I found my phone restart one time, because I saw the popup notice for reminding the back cover that means the phone restart already. Please tell us what happen after you remove the apps. I think it is the software problem rather than the hardware problem. I don't want to get replacement phone because it is refurbished phone.
Click to expand...
Click to collapse
Well I'm still trying to determine which app is causing it. For all I know, it could be the firmware T-mo pushed out prior to the latest one. T-mo says they haven't had reports on this issue so I don't want to blame the FW right off the bat. I have ruled out about 70% of my apps and right now have about 5 uninstalled and phone hasn't restarted in 3 days. Below is are the apps I have yet to try and the ones currently removed.
Current Removed:
Code:
'Disable Increasing Ring'
'netflix'
'uber'
'hbo go'
'battery widget'
'2x rdp client'
'pandora'
Yet to try:
Code:
Google Maps
Facebook
Chrome
chromecast
hangouts
tinder
lookout security
Touchpal Keyboard
Reuters
Beep'nGo
Might help if you let me know which ones you have in common above. FYI, I also tried removing my sd card like I saw in a few forums. Also, Tmobile says they don't give you referb phones. They give new phones that were returned to the store within a few days. So openbox, mine looked perfect.
1sae said:
Well I'm still trying to determine which app is causing it. For all I know, it could be the firmware T-mo pushed out prior to the latest one. T-mo says they haven't had reports on this issue so I don't want to blame the FW right off the bat. I have ruled out about 70% of my apps and right now have about 5 uninstalled and phone hasn't restarted in 3 days. Below is are the apps I have yet to try and the ones currently removed.
Current Removed:
Code:
'Disable Increasing Ring'
'netflix'
'uber'
'hbo go'
'battery widget'
'2x rdp client'
'pandora'
Yet to try:
Code:
Google Maps
Facebook
Chrome
chromecast
hangouts
tinder
lookout security
Touchpal Keyboard
Reuters
Beep'nGo
Might help if you let me know which ones you have in common above. FYI, I also tried removing my sd card like I saw in a few forums. Also, Tmobile says they don't give you referb phones. They give new phones that were returned to the store within a few days. So openbox, mine looked perfect.
Click to expand...
Click to collapse
I just do some research online. Many articles are talking about that the android 4.4.2 has randomly reboot bug. I think this the common bug for the 4.4.2. Hopefully, the 5.0 is rolling out for international version. I think t-mobile will update the s5 to 5.0 soon.
Its the 4.4.2 firmware. Its because of all the apps updating to the new lollipop 5.0 but where still on kit Kat. Remember now these apps are set to run on art now so i believe there conflict between the dalvik thats the norm. On 4.4.2. I noticed if i run my SM-G900T 4.4.2 in art mode the rebooting stops. So at the end of the day this means when 5.0 is released to our S5 the reboots should stop. If your bothered by the reboots just run the 4.4.2 in art mode. Good day☺
Sent from my SM-G900T using XDA Free mobile app
beachbum40 said:
Its the 4.4.2 firmware. Its because of all the apps updating to the new lollipop 5.0 but where still on kit Kat. Remember now these apps are set to run on art now so i believe there conflict between the dalvik thats the norm. On 4.4.2. I noticed if i run my SM-G900T 4.4.2 in art mode the rebooting stops. So at the end of the day this means when 5.0 is released to our S5 the reboots should stop. If your bothered by the reboots just run the 4.4.2 in art mode. Good day☺
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
I just turn off the VoLTE, and the phone runs for 10 days without any reboots. Do you think it is the problem of the VoLTE?
jc_hwz said:
I just turn off the VoLTE, and the phone runs for 10 days without any reboots. Do you think it is the problem of the VoLTE?
Click to expand...
Click to collapse
Could be.? I'm just making an educated guess that it's the fact that when our apps like YouTube, Gmail ,ect.. updated it seems that's when my reboots started. Volte could be a cause to. Your guess is as good as mine. But I truly believe it's the fact that the updated app where modified to art and 4.4.2 is dalvik. ?? I'm sure when the 5 update comes this will be resolved ☺
Sent from my SM-G900T using XDA Free mobile app
Will stock 4.4.2 unrooted run art? How would I enable that?
chazel3 said:
Will stock 4.4.2 unrooted run art? How would I enable that?
Click to expand...
Click to collapse
1.) Go into Settings, and About Device. Where it says: Build number press on this over and over again until it gives you the Toast message: Developer Options Turned On (something to that effect).
2.) Go back into Settings, and just below Security and above About device, you will see Developer options. Open this.
3.) 4th Item down is: Select runtime system. It should say: Use Dalvik. Change this option to: Use ART. It should work for a little bit, then Reboot your phone.
4.) All done!
Note: If you plan to Root your phone, and use Xposed, it is NOT compatible with ART runtime. If you plan to stay unrooted, or not use Xposed if you do root, then you are fine. You can always switch back if you decide to do this.
My phone received android wear 1.1.1.1901499 last night but my lg g watch still has 5.0.2
I have tried the 'system updates' in the watch settings-about, but still not getting 5.1.1 to watch. Also restarted the watch. Are these the correct versions for the update?
Just wait a few days, the update to 5.1.1 is comming and some of us already have it.
In my case (and yours) we will have to wait for the next batch (usually a few days if no crash were found for the first few users).
If you don't want to wait and are not afraid of doing potentially dangerous stuff on your watch, there are many threads that explains how to force the update.
Be sure to read everything before starting to do something, you don't want your watch not to boot again ^^
supermamie said:
Just wait a few days, the update to 5.1.1 is comming and some of us already have it.
In my case (and yours) we will have to wait for the next batch (usually a few days if no crash were found for the first few users).
Click to expand...
Click to collapse
So doesn't the phone android wear app update to version 1.1.1.1901499 cause the watch to update to 5.1.1?
Those are two compeletely different things.
Your phone got the update of the app from the play store, you can have the update on the phone even if you don't have a watch.
The watch is updated via the application on the phone (I don't know if the app have to be up-to-date to be able to update the watch, maybe, but you'll always have the app update before the watch updates are released so no worries).
your situation is same as mine
yesterday i mis-touched the reset
after my watch reset and i got the update!!
hope this will help
I received the update onto G Watch last night
I like it, nice update.
-The menu/app launcher is better organized now that there are 3 sections (apps, contacts, actions/menu), swipe left/right to go between.
-Draw emoji worked well on simple test (takes several menu taps to get through the process, which is probably good so I don't send the wrong emoji).
-Screen did not lock when I took watch off (after setting pattern). There was a menu to lock now, that worked however. Pattern then shows on top of my watchface(Watchmaker), unlocked with correct pattern as expected.
-enabled priority notifications. Now I get a star on top my watchface which I assume means there is a notification but I cannot get it to show. swipe up from bottom edge did not work for me
-wristflick through notifications works (after sending several test notifications from phone)
Everyone but me probably understands this, but...
I'll just risk ridicule and ask:
What is the relationship between Android Wear 1.1.1.1901499 and so-called Android Wear 5.1.1? The issue baffles me.
Is it Lollipop for smartwatches, or Android Wear? Or does one need both? If so, why?
Yes, I understand the Lollipop update cycle as I have a phone with 5.0 (Moto X2) and a phone with 5.1 (Nexus 6), and my Moto 360 is running 5.0.2. So, that's clear enough. But then my Android Wear app updates and announces under "what's new" all the features that people are talking about, (wifi, etc.) as if I should be able to use them right away. But I can't as of today, and people are still all over the threads talking about the LG Urbane, and the Asus Zen Watch getting "the update." But WHAT update?
So, even if the answer begins, "Well, duh..." I'd still like to understand the issue if someone has the time and patience to explain it. Thanks.
For the phone to know how to communicate with the watch under 5.1.1, you have to have an up to date android wear app on your phone.
On an old version, you will not have the options to configure the new features from your phone.
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
metalslug53 said:
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
Click to expand...
Click to collapse
You will need to modify your build.conf to prevent the update screen from prompting you.
Change the build number to something else....
/system/build.prop
Change the build to something like: ro.build.display.id=AKOT49HA
and do the same to the rest of them in the file.
Hello,
I have tried the steps described in post #212 in the how to pair with non Samsung device topic, however the app can now detect that build.props have been tempered and won't connect to it. After I used the trick to click the watch icon I was able to active the watch, however connecting to my Nexus 5 proves to be not so easy task
If anyone has connected the phone can you post a short guide on how to connect it(which version of the Host Manager, Gear Manager and the Stub are you using will be enough).
Ty
I'd also like information about this. I have a Nexus 5 and just got a Gear S, and all of the tutorials for making them compatible, here and elsewhere, are out of date and broken by Marshmallow. In any case they don't work for me. Is it possible now? Could a new tutorial be put together?
I am seriously thinking about reverting back to 5.1.1 as waiting for Samsung to update their apps for Android 6.0 would take some time as even their S6 Edge frontman phone has not received Marshmallow, yet ;(
android wear with Gear S
until then ..maybe android wear for Gear S? any news on that part of dev ?
2g4u said:
I am seriously thinking about reverting back to 5.1.1 as waiting for Samsung to update their apps for Android 6.0 would take some time as even their S6 Edge frontman phone has not received Marshmallow, yet ;(
Click to expand...
Click to collapse
Can you give me solution in 5.1.1 how paired ?
I've used the BlissPop Rom with the solution in this post:
http://forum.xda-developers.com/showpost.php?p=60263721&postcount=252
No need to change your build.prop if you preactive your watch.
However the thing that annoyed me most was that it doesn't matter if I pick up the call on my phone or watch, the call always gets transferred to the watch. So you have to manually transfer the call to the phone each time you get one....
Not to mention that I got contacts synced somehow, but the messages and any other app's notification, did not get send to my watch, even when the app is selected in Gear Manager notification settings....
So I ended up buying used S5 and tbh after removing some of the bloat I enjoy the S5 more that I did my Nexus 5.
Hello ladies and gentlemen,
This is my first looong post here. This is my journey with the new Mi5. I own it for 3 days now and I desperately need help with Android Auto.
After 2 weeks of waiting, I finally received my White Mi5 Pro from AliExpress. I love everything about the phone, the design, the build, the weight, the ceramic glass... For your information, I have been a fan of OnePlus and I'm currently using OnePlus 2 as my daily driver. It runs Hydrogen, because I hate the OxygenOS. In the past I flashed MIUI6 into my OnePlus 2 and I absolutely love the UX. I think this is the how all Android ROM should go for. So I didn't want to buy the OnePlus 3 when it came out, and ordered a Mi5 Pro instead.
My Mi5 Pro came with a Chinese stable ROM of course with loads of useless Chinese bloatware. After booting it up, I immediately checked for ROM update and did upgrade to the latest version (MIUI 7.5 | Stable 7.5.6.0 MAACNDE). Then I realized I need Google Play Store to download all my apps. As an Android developer, my life has been with Google since forever.
So of course I searched everywhere on the internet for ways to install Google Play Services. I did find the package that would allow me to use Google Play Store. The package is at http://en.miui.com/thread-285420-1-1.html. I managed to install it successfully and got all my regular apps downloaded from the Play Store. So far so good. The ROM still has the some Chinese in there but that's OK, as long as I have all the apps I want.
Did I mention I'm an Android developer? I need to go to work to pay for this wonderful device if they come out with another model next years right? I can't live without Android Auto and this is the main reason I bought the Civic. So I got in my car, a new 2016 Civic EX-T (T is for the Turbocharge FYI) and wait for the ANDROID AUTO to come up. It never came. OK, maybe the permission issue? I granted all permissions to Google Play Serivces, Android Auto, Maps etc. Didn't work. I turned off Permission completely. No hope too.
To debug more, I notice that Android Auto works with the OnePlus 2 when the device is connected in the USB MTP mode. By default, when I plug my phone to my laptop, the default connection mode is USB charging only. I knew I needed to change the default USB connection mode. I searched around and found this wonderful app MIUI USB Settings https://play.google.com/store/apps/details?id=co.vincze.usbsettings&hl=en as it is highly suggested by a lot of people. Plugged in the phone to my Mac, launched the app, it showed a white screen when it's supposed to show a Setting page for me to select the USB connection mode. Nice, I guessed MIUI7 changed this page to another URI so the app couldn't find it. I searched again and found that for Android 6 device, the USB Configuration is inside the Developer mode. I went in there and changed it to MTP protocol. But after I selected if from the list, it came back to charging only. Is this the bug right there??? I tried to select PTP, and it came back to Charging only too. Looks like MIUI7 likes to be charged so much. This is why everytime I plug the phone to my car, Android Auto can't launch because it's always in charging mode, meaning no data communication between my phone and the car. Why are we not able to set the default USB connection mode to MTP?
I then decided to manually change to MTP after connecting to my car. The car shows "Loading...' (yes! it recognized there's an Android Auto device connected) but that's it. Android Auto was not loaded in my car's touch screen. I looked back to the phone and saw "Google Play services has stopped".
Being an engineer, I did not give up. I thought it's due to the ROM issue. I went back to the download sitehttp://en.miui.com/download-299.html#435 and downloaded the Developer version (which is MIUI 8). Re-installed all the Gapps and restored all data. Everything worked. However I Android Auto didn't show up in the car touch screen when connected. I saw the "Android Auto connected to car" notification on the phone but that's it. I thought the cable had problem so I tried with the OnePlus 2 and the car show Android Auto after 1 second.
Again, I refused to give up. In the past I flashed so many ROMs onto the OnePlus 2 so I wanted to flash the global version onto Mi5 to use the gapps coming with it with the hope Android Auto would work. I researched more and knew that my Mi5 Pro came with a locked bootloader therefore I can't flash anything nor root it. So I searched more and knew that the only way to unlock bootloader is to apply for it and wait for the approval. Seriously Xiaomi, why do you make the process so hard? I applied a few days ago and now I had to wait for the approval? Why can't you automatically approve it and not manually? If the Xiaomi team is reading this please could you approve my request? My UID is (catennacio UID: 3262109).
So I'm stuck now, can't do anything with the locked bootloader. All the Gapps I tried (including the ones with Google Installer v2) crashed when connecting to the car. Then I searched more and found this http://en.miui.com/thread-299790-1-1.html . Huraaayy! I can still flash Global ROM to a bootloader locked device? Nice. I read the article just to know that I need a god darm Engineering cable!!!! Where can I get it? On AliExpress! When will I get it if I order? Another 3 weeks!!! Oh god why!! Why do you make my life so miserable?
So I'm really stuck now! I go back to my OnePlus 2 and it still works with the car. The Mi5 is not bricked but it's sitting on my table as a brick to keep my papers from flying. I can't use it without Android Auto working. All I can do is to wait (which I hate) for the bootloader to be unlocked, flash the global ROM and pray that Android Auto work.
With the new MIUI 8 Global Public beta coming out on Jul 11, I hope the dev team could take a look at this before releasing it, because I can't wait for another 1 month for the Stable release:
1. Please fix the USB default connection mode to be MTP, or at least allow people to change to. In MTP it's still charging. For a developer like me it's very annoying to see ADB doesn't recognize the phone because it's in the wrong mode and I have to manually change it to MTP.
2. Please really take a look into the Gapps you are puting in. I've been through a hellish experience trying to find a good Gapps package that has proper contact sync, supports multiple Google accounts well, and has PlayStore download apps on LTE. I have an unlimited package data but somehow the Gapps I use "Waiting for LAN to download because of the package size". More importantly, could you please test and assure that Android Auto will work? Because if not, after my bootloader is unlocked, I will have to install another ROM that supports Android Auto properly.
I'm sorry if this is too long, but my original excitement with the new device is now gone. I have to go back to my OnePlus 2. If you want to help, please approve my bootloader unlocking application so I can still keep trying...
If anyone knows a way to make a locked Mi5 work with Gapps and Android Auto please let me know!
Thanks for reading. Peace!
I haven't tried Android Auto (and don't have a car anyways) so I can't confirm if my Gapps work with it. Some people on the MIUI forums claim that it works on their phones here: http://en.miui.com/thread-249360-1-1.html, so it may be a Gapps issue. I personally downloaded an auto-installer off the Mi App Store, which seems to work fine with the exception of my Google Calendar facing sync problems.
However, I have unlocked my bootloader, and if memory serves it took less than 10 days for the request to be approved. Check the MIUI unlock application page--if it redirects to http://en.miui.com/unlock/download_en.html, you'll be able to download and use their unlocker. You could also download the application first and try your luck, it will have you log in to your Mi account then verify if your account's been approved.
Additionally: the "Waiting for LAN..." message appears because MIUI's download manager has a limit set for mobile data downloads by default. Go into the downloads setting page and switch the download size limit to unlimited.
littlecaten said:
Hello ladies and gentlemen,
This is my first looong post here. This is my journey with the new Mi5. I own it for 3 days now and I desperately need help with Android Auto.
After 2 weeks of waiting, I finally received my White Mi5 Pro from AliExpress. I love everything about the phone, the design, the build, the weight, the ceramic glass... For your information, I have been a fan of OnePlus and I'm currently using OnePlus 2 as my daily driver. It runs Hydrogen, because I hate the OxygenOS. In the past I flashed MIUI6 into my OnePlus 2 and I absolutely love the UX. I think this is the how all Android ROM should go for. So I didn't want to buy the OnePlus 3 when it came out, and ordered a Mi5 Pro instead.
My Mi5 Pro came with a Chinese stable ROM of course with loads of useless Chinese bloatware. After booting it up, I immediately checked for ROM update and did upgrade to the latest version (MIUI 7.5 | Stable 7.5.6.0 MAACNDE). Then I realized I need Google Play Store to download all my apps. As an Android developer, my life has been with Google since forever.
So of course I searched everywhere on the internet for ways to install Google Play Services. I did find the package that would allow me to use Google Play Store. The package is at http://en.miui.com/thread-285420-1-1.html. I managed to install it successfully and got all my regular apps downloaded from the Play Store. So far so good. The ROM still has the some Chinese in there but that's OK, as long as I have all the apps I want.
Did I mention I'm an Android developer? I need to go to work to pay for this wonderful device if they come out with another model next years right? I can't live without Android Auto and this is the main reason I bought the Civic. So I got in my car, a new 2016 Civic EX-T (T is for the Turbocharge FYI) and wait for the ANDROID AUTO to come up. It never came. OK, maybe the permission issue? I granted all permissions to Google Play Serivces, Android Auto, Maps etc. Didn't work. I turned off Permission completely. No hope too.
To debug more, I notice that Android Auto works with the OnePlus 2 when the device is connected in the USB MTP mode. By default, when I plug my phone to my laptop, the default connection mode is USB charging only. I knew I needed to change the default USB connection mode. I searched around and found this wonderful app MIUI USB Settings https://play.google.com/store/apps/details?id=co.vincze.usbsettings&hl=en as it is highly suggested by a lot of people. Plugged in the phone to my Mac, launched the app, it showed a white screen when it's supposed to show a Setting page for me to select the USB connection mode. Nice, I guessed MIUI7 changed this page to another URI so the app couldn't find it. I searched again and found that for Android 6 device, the USB Configuration is inside the Developer mode. I went in there and changed it to MTP protocol. But after I selected if from the list, it came back to charging only. Is this the bug right there??? I tried to select PTP, and it came back to Charging only too. Looks like MIUI7 likes to be charged so much. This is why everytime I plug the phone to my car, Android Auto can't launch because it's always in charging mode, meaning no data communication between my phone and the car. Why are we not able to set the default USB connection mode to MTP?
I then decided to manually change to MTP after connecting to my car. The car shows "Loading...' (yes! it recognized there's an Android Auto device connected) but that's it. Android Auto was not loaded in my car's touch screen. I looked back to the phone and saw "Google Play services has stopped".
Being an engineer, I did not give up. I thought it's due to the ROM issue. I went back to the download sitehttp://en.miui.com/download-299.html#435 and downloaded the Developer version (which is MIUI 8). Re-installed all the Gapps and restored all data. Everything worked. However I Android Auto didn't show up in the car touch screen when connected. I saw the "Android Auto connected to car" notification on the phone but that's it. I thought the cable had problem so I tried with the OnePlus 2 and the car show Android Auto after 1 second.
Again, I refused to give up. In the past I flashed so many ROMs onto the OnePlus 2 so I wanted to flash the global version onto Mi5 to use the gapps coming with it with the hope Android Auto would work. I researched more and knew that my Mi5 Pro came with a locked bootloader therefore I can't flash anything nor root it. So I searched more and knew that the only way to unlock bootloader is to apply for it and wait for the approval. Seriously Xiaomi, why do you make the process so hard? I applied a few days ago and now I had to wait for the approval? Why can't you automatically approve it and not manually? If the Xiaomi team is reading this please could you approve my request? My UID is (catennacio UID: 3262109).
So I'm stuck now, can't do anything with the locked bootloader. All the Gapps I tried (including the ones with Google Installer v2) crashed when connecting to the car. Then I searched more and found this http://en.miui.com/thread-299790-1-1.html . Huraaayy! I can still flash Global ROM to a bootloader locked device? Nice. I read the article just to know that I need a god darm Engineering cable!!!! Where can I get it? On AliExpress! When will I get it if I order? Another 3 weeks!!! Oh god why!! Why do you make my life so miserable?
So I'm really stuck now! I go back to my OnePlus 2 and it still works with the car. The Mi5 is not bricked but it's sitting on my table as a brick to keep my papers from flying. I can't use it without Android Auto working. All I can do is to wait (which I hate) for the bootloader to be unlocked, flash the global ROM and pray that Android Auto work.
With the new MIUI 8 Global Public beta coming out on Jul 11, I hope the dev team could take a look at this before releasing it, because I can't wait for another 1 month for the Stable release:
1. Please fix the USB default connection mode to be MTP, or at least allow people to change to. In MTP it's still charging. For a developer like me it's very annoying to see ADB doesn't recognize the phone because it's in the wrong mode and I have to manually change it to MTP.
2. Please really take a look into the Gapps you are puting in. I've been through a hellish experience trying to find a good Gapps package that has proper contact sync, supports multiple Google accounts well, and has PlayStore download apps on LTE. I have an unlimited package data but somehow the Gapps I use "Waiting for LAN to download because of the package size". More importantly, could you please test and assure that Android Auto will work? Because if not, after my bootloader is unlocked, I will have to install another ROM that supports Android Auto properly.
I'm sorry if this is too long, but my original excitement with the new device is now gone. I have to go back to my OnePlus 2. If you want to help, please approve my bootloader unlocking application so I can still keep trying...
If anyone knows a way to make a locked Mi5 work with Gapps and Android Auto please let me know!
Thanks for reading. Peace!
Click to expand...
Click to collapse
Lol... Sell your civic and buy a real car[emoji23]
Or
Sell your Mi5 and buy a real phone?
Do you have any update, I have the same problem.
Hi there. I'm using MIUI 8 global developer with Gapps preinstalled on mi 5. I tried everything you tried on a CLA 250. LOVE IT BTW. I'm suspecting it could be the cable. I will try and let you know.
TheDriller said:
Lol... Sell your civic and buy a real car[emoji23]
Or
Sell your Mi5 and buy a real phone?
Click to expand...
Click to collapse
Wrong answer! I have them both a Civic and Mi5
Sent from my MI 5 using Tapatalk