Related
Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Dog909 said:
Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Click to expand...
Click to collapse
I can't find folder *data* in folder *d*. I have a separate folder *data*. There is a folder named *bluetooth* in folder *d*. It also didn't work for me.
Hi folks,
I'm trying to keep my Fairphone free of googleApps (because, you know, $reasons), but as usual it's not that easy.
I am struggeling to get NoGApps working. First of all: kudos to @MaR-V-iN - I don't have a paypal account, but I could invite you for a Kölsch next time I'm in the area.
Can anybody review my steps and possibly describe how to get it running properly?
0. installed OI File Manager (to be able to access the internal partition)
1.1. downloaded μg v1.3.2 (NetworkLocation.apg)
1.2. ( tried to copy to /system/app/NetworkLocation.apk - to no avail: "... could not be copied")
1.3. installed NetworkLocation, allowed access in XPrivacy popup, rebooted.
1.4. downloaded cells-world.db, renamed to cells.db, moved it to /sdcard/.nogapps/cells.db
1.5 tried to find any sign of the application. (Found nothing.)
Sadly, Network location does not show up, anywhere. Am I looking in the wrong places?
2.1. downloaded Blank Store 0.6.6 (BlankStore.apk)
2.2. (renamed it to com.android.vending.apk, tried to copy it to /system/app/com.android.vending.apk - no success.)
2.3. renamed again, installed BlankStore.apk, allowed access in XPrivacy popups, rebooted.
2.4. downloaded android-checkin-1.0.jar and bla.bat, copied them to the location of java.exe, generated an android ID.
2.5. went to menu [Settings]{Accounts}
2.5.1 entered (dedicated...) google credentials and android ID,
2.5.2 entered slightly changed credentials that @DSoundso mentioned (SDK should be 17, I think. I also used a German carrier's MCC-MNC).
2.5.3 rebooted.
2.6 opened BlankStore: yay, I can search it. But I can't install any app: it crashes constantly.
I should mention that the Account settings were gone several times, so the BlankStore would close immediately. I had to re-enter them, and tried also exactly the credentials @DSoundso mentioned in the NOGAPPS thread.
I can't "sync" the account under [Settings]{Accounts}{Sync}. It just "says Sync is OFF", "sync now" does not seem to work.
I logged into the google account on a desktop PC, and no devices show up. ("No active devices").
So, the next steps are unfinished:
3.1. downloaded Maps API v1 (nogapps-maps.zip)
3.2. tried to download via Blank store: BusyBox, TWRP, TitaniumBackup. (BlankStore crashes.)
...to be continued?
Can anybody walk me through?
Or at least single out any errors I made above?
Hey, did you have a look at the XDA-Wiki section about installing the Blank Store? Following this step-by-step should hopefully install the Blank Store
I am too avoiding the Google Apps and also installed the maps successfully (didn't try NetworkLocation yet) and your problems with "could not be copied" sound like a problem with the user rights.. I'm not sure how your file manager works but the with the Android SDK (see above link) and the right commands it should work.
As far as the crashes of the Blank Store are concerned: at first mine also didn't start and crashed, which was caused by the missing Store account but as it sounds yours IS starting but then not really functioning, right? :|
arghwhymustiregister said:
Hey, did you have a look at the XDA-Wiki section [...] As far as the crashes of the Blank Store are concerned: at first mine also didn't start and crashed, which was caused by the missing Store account but as it sounds yours IS starting but then not really functioning, right? :|
Click to expand...
Click to collapse
Thanks, I gave that a try yesterday. 1.7 gb download, what a mess... But solved the problem: it was a rights issue. I was under the impression that the OI File Manager had superuser rights. I was wrong. Got BlankStore working now, but it crashes still quite often on download.
I'm still not sure what to make of it. As I said, it *seemd* to be working before as well, but *no* download was finished. Now, *some* finish their dl, and if they don't I get an error notification (was missing before).
However, whenever I try to load a paid app, the BankStore crashes instantly.
I tried to read the whole NOGAPPS thread and realised: it only works for free apps. And I already redeemed a gift card at the Play Store to buy a paid Titanium Backup version. ****e, I'm stupid. :silly:
Still, it would be nice if it would not crash, or at least tell me it would crash when trying to load a paid app.
Also, I still can't see any active device when logging into the account on the web. Any ideas there? Is that supposed to be like this?
(Funny enough, I *can* see which apps I downloaded through BlankStore.)
arghwhymustiregister said:
also installed the maps successfully (didn't try NetworkLocation yet)
Click to expand...
Click to collapse
It seems both are not working properly for me. OSMAnd can find it's position by GPS. Offi is working, but can not find a location (GPS turned on). Also in Offi Stations, 'Acquiring location' never gets finished. The map stays blank in landscape mode. I would very much appreciate it if you would report your status here: if you can get it to work, how - and if not, what $reasons do you assume?
The permissions are not the problem. /system has to be mounted writable.
Sent from my FP1 using xda app-developers app
permissions for Offi / Maps Api access?
elchi1234 said:
The permissions are not the problem. /system has to be mounted writable.
Click to expand...
Click to collapse
Thanks for pointing that out, @elchi1234. I'm not used to work on linux-like systems, but I'm eager to learn.
However, I assume this could have something to do with permissions:
boondiordna said:
Offi is working, but can not find a location (GPS turned on). Also in Offi Stations, 'Acquiring location' never gets finished. The map stays blank in landscape mode.
Click to expand...
Click to collapse
I tried to figure out why Offi is not showing any map. It seems like it's trying to DL / access map tiles and not getting access, which sometimes even causes crashes:
Code:
W/MapsAPI ( 5201): MapTileDownloader: Problem downloading MapTile: /17/65535/65535 HTTP response: HTTP/1.1 403 Forbidden
According to the crash report, this happens with every tile the app is trying to access.
Did I mess up somehere?
Nice to hear that the Blank Store is now working for you.
Hm, that problem with Öffi sounds familiar to me - I seem to recall that I had these problems too.. since you could install those Apps it looks like your installation of the map files was succesful. I think you should try the GPS fix mentioned here. It really helps A LOT (or did you already do that..?)
Report back!
Well, the MapsAPI seems to be installed correctly. (It was never working for me, too. I use it for that apps that require it but don't really need it.)
I would guess that there is a change in the API of the webserver that MapsAPI doesn't know about.
It seems that Google just rolled out version 7.3.28 of their Google Play Services last night, and my Kindle Fire HD 8.9 has been popping up annoying Play Services have Stopped boxes constantly. Edit - confirmed this also is happening with 7.3.29. Also confirmed that this problem and fix works with the 7" Kindle fire HD tablets.
After pulling all my hair out, restoring to factory settings 3 times, figuring out how to re-root version 8.5.1, and then re-installing my old Google apps (from previous downloaded files), I have confirmed that Google will very quickly notice the outdated version and update to 7.3.28. Then the annoying pop-ups start all over again.
1) To fix the problem, you need a working version of Google Play Services. Go into Settings->Applications->Installed Applications and look for Google Play Services. Look for the version number in parenthesis, paying attention to the last 3 digits after the suffix. If it's like my Kindle 8.9, it will be -034. I confirmed that my Kindle did work on the previous version of Play Services (7.0.99), so what you need is to download that version for your Kindle. For the -034 version, the link is at:
(edit: I apparently can't post links, so I've modified the following to make it not look like a link, please edit and paste into your browser).
h t t p : / / www (dot) apkmirror (dot) com/wp-content/themes/APKMirror/download (dot) php?id=7772
2) Once downloaded, turn OFF Wi-Fi. Then, use ES3 file explorer to re-install this version from wherever you downloaded it to, overwriting the current version.
3) Next, create a folder in /data/app with name "com.google.android.gms-2" (not with the quote marks). You may see the actual .apk file already there ending in -1. Change permissions for this folder to rw-r-r. This folder should block the Google automatic update.
NOTE: This assumes your play services app is installed in this folder as "com.google.android.gms-1.apk". If it's not, one fix is to uninstall play services, then repeat the install in step 2. That should make it be named with the -1 suffix.
4) Repeat step 1 to confirm you're still on version 7.0.99. Select Clear data just to be sure the cache is cleared.
5) It should be safe to turn Wi-Fi back on. Launch Google Play Store, do a few things and confirm it works!
Really grateful for this, basically had the same issues as you on a Kindle 7", as Amazon store had popped up a few times with a permissions update I figured I'd suffered a clash/glitch. It wasn't until I turned on a dormant 8.9" and got the same error that I realised it was a wider issue and searched for your post.
Seems to have fixed the 8.9 first time, now back to the 7 and hope I haven't screwed it up too much trying multiple solutions.
Just a couple of notes from a novice, it's files that are located in data/app not folders? (update - confirmed need to create a folder not a file)
And the permissions correspond to Owner - Read, Write / Group - Read / Others - Read, being ticked only.
Another thing to look out for, when you're creating the dummy folder, watch out for autocorrect renaming parts of it to something else, maybe try copying and pasting the name.
:good: It worked perfectly! Thanks a lot!
P.S. i used this procedure in a kindle fire hd 7" (Tate)
This mostly worked, except I needed to create "com.google.android.gms-2.apk" to stop the updates. Worked on a Kindle 7 HD as well.
bobdob123usa said:
This mostly worked, except I needed to create "com.google.android.gms-2.apk" to stop the updates. Worked on a Kindle 7 HD as well.
Click to expand...
Click to collapse
Hi
I have the same issue with Play Services stopping, I downloaded the 7.0.99 -034 version which is correct for my 7 inch Fire HD.
I turned off wifi and installed it (over the existing) using the ES file manager and now have a new error "the processcom.google.process.gapps has stopped".
I read elsewhere this could be associated with the Downloads app but the problem is I cannot navigate anywhere on the device as the error reappears within a second of dismissing it
Any suggestions welcomed as I have a brick at present
There was an occasion when I got the persistent gapps error too, can you persevere and dismiss it enough to get to More/Applications/Installed Applications/Google Play services and Force Stop?
You can then confirm whether the old (working 7.0.99) version installed correctly and see if the error stops?
kinoogle said:
There was an occasion when I got the persistent gapps error too, can you persevere and dismiss it enough to get to More/Applications/Installed Applications/Google Play services and Force Stop?
You can then confirm whether the old (working 7.0.99) version installed correctly and see if the error stops?
Click to expand...
Click to collapse
Hi
Thanks for the response ..... I manages to force stop the Google Play services, 7.0.99 was installed
I have uninstalled the Play Service and the tablet seems to work with no errors but I guess I need to reinstall it again ....... or do I?
VeeMax said:
Hi
Thanks for the response ..... I manages to force stop the Google Play services, 7.0.99 was installed
I have uninstalled the Play Service and the tablet seems to work with no errors but I guess I need to reinstall it again ....... or do I?
Click to expand...
Click to collapse
I guess you need it if you want to use the Google store/synch? Maybe if you did a fresh install using this method the error would go away as it was something to do with the cache?
I have tried to do this method but still not working. It stays on 7.0.99 version but won't even open. I can't get it to open long enough for me to sign in. Any suggestions
---------- Post added at 02:34 AM ---------- Previous post was at 02:30 AM ----------
what folder are you creating the new folder in as well?
frosty1218 said:
I have tried to do this method but still not working. It stays on 7.0.99 version but won't even open. I can't get it to open long enough for me to sign in. Any suggestions
---------- Post added at 02:34 AM ---------- Previous post was at 02:30 AM ----------
what folder are you creating the new folder in as well?
Click to expand...
Click to collapse
I've done this method on both my 8.9" tablet, as well as two 7" tablets. The folder you create is in /data/app (you need to be root). Make sure you clear cache on the 7.0.99 version or things may still be out of sync.
In general, you'll have to fight through the clicking of OK on the annoying pop-ups. It may help to reboot the Kindle (hold down the power button, etc) to see if timing works better, and it may give you a window to uninstall quickly.
I created the folder in the data/app folder but now I'm not so sure I put it on the correct one. Can you tell me what folder exactly it goes into please?
frosty1218 said:
I created the folder in the data/app folder but now I'm not so sure I put it on the correct one. Can you tell me what folder exactly it goes into please?
Click to expand...
Click to collapse
Use ES File explorer. Back up all the way to the "/" directory. Under that you should see a folder called "data". Inside that, you should see a folder called "app". That is the /data/app folder. You'll know you're in the right place, because there should be a lot of installed .apk files in there. If you sort alphabetically, you should be able to find "com.google.android.gms-1.apk" (which corresponds to your installed play services file).
To block updates, make dummy named folders, such as "com.google.android-gms-2", and as another user pointed out it may help to also create "com.google.android.gms-2.apk". See the original post about setting permissions. Also, be careful about the autocorrect trying to change your filename on you. Once you finish, scroll through and compare names versus the installed play services apk (it should be -1, and you should have just made folders that have the same name, only with the -2).
should I download the google apk files from the kindle from apkmirror website or download them on my computer then transfer them to my kindle fire?
Once again,I have done all the steps shown and still, the moment I tap on google play store, it shows stopped error and returns to home screen. Does all the apk files need to change? The google framework apk, vending apk, google login apk, and the play store apk.
Please help
I keep getting the google play services have stopped working message. I would appreciate if someone could give me like a dummy version of this because I don't fully understand. So please make a video and reply it to me. Or just type something just please reply and help me do this.
I have tried this fix on a 7" fire HD tablet and I cannot get the fix to persist. Once I roll back with the correct 7.0.99 version with both a "com.google.android.gms-2" folder set with the correct permissions and a "com.google.android.gms-2.apk" installed in the data/apps folder things work well until a reboot. After a reboot I get upgraded to the .29 version of the apk and have to reinstall the working version again. I have tried every combination of folder/apk possibilities I can think of and I am still stuck. Any ideas?
Is there any update on how to keep the 7.0.99 Play Services version from upgrading? As mentioned above, I can get the 7.0.99 version to work, but only for a couple of days. Has anyone found a permanent solution?
mach76 said:
I have tried this fix on a 7" fire HD tablet and I cannot get the fix to persist. Once I roll back with the correct 7.0.99 version with both a "com.google.android.gms-2" folder set with the correct permissions and a "com.google.android.gms-2.apk" installed in the data/apps folder things work well until a reboot. After a reboot I get upgraded to the .29 version of the apk and have to reinstall the working version again. I have tried every combination of folder/apk possibilities I can think of and I am still stuck. Any ideas?
Click to expand...
Click to collapse
Is your "com.google.android.gms-2.apk" also a folder, or a dummy file? I've had success through reboots with two dummy folders: "com.google.android.gms-2" and "com.google.android.gms-2.apk". Make sure you uninstalled play services and re-installed 7.0.99 so that it takes the -1 suffix.
frosty1218 said:
Once again,I have done all the steps shown and still, the moment I tap on google play store, it shows stopped error and returns to home screen. Does all the apk files need to change? The google framework apk, vending apk, google login apk, and the play store apk.
Click to expand...
Click to collapse
No. You should only need to uninstall the Google Play Services, and that apk is the only one that needs re-installing. If the other files had previously been installed and worked fine, then they should still be ok.
See the note above about the two folders - for some installs, the dual dummy folder names seem to work better, and survive reboots.
I had to use r--r--r-- perms on the dummy file and folder to stop the updates. Otherwise outstanding help, thamks wolverine, kindle has stopped its google play seizures.
UPDATE: I have since added r--r--r-- on the actual 7.0.99 file (the -1.apk file) in order to prevent the updates (it managed to sneak in a damned update without it), so:
- follow ALL wolverine's excellent directions for installation, including turning off wifi, etc, take NO shortcuts
- create the dummy folder AND the dummy file (-2.apk)
- apply r--r--r-- permissions on ALL 3 ITEMS (dummy folder, dummy -2 file, and actual -1 file)
- enjoy a fully functional google play shizznitz on your rooted Fire.
After months of trying I managed to change launcher on RKa701 device.
As owners of this device already know, another launcher can be installed on this device but you cannot set it as default because it will stuck, or wont launch or will not be displayed correctly. It simply conflicts with factory launcher and make unit unusable.
Factory launcher is very ugly but the problem with it is not just that , but unit needs it because radio, music, bluetooth and other apps wont work without it. As you can swap factory music app with another one you cant do that with radio and bluetooth.
Im not responsible if you mess something with your device. Proceed at your own will.
So here we go:
1. Root your device with latest kingroot ( i used latest 5.2 version) . Dont worry we will uninstall it later
2.When rooted it will ask for all kind of permission allow
3. With root explorer or some other app go to system/priv app and make a backup of launcher2.apk-copy it somwhere.
4. Download apk file of some launcher (can be any-we wil install our main launcher later) and put it in system/priv app. I used nova and renamed it to "launcher2" just in case. Install nova.
5. reboot or (if you want to uninstall root for good-choose factory reset) . After boot up nova launcher should be loaded instead main launcher. But WE ARE NOT FINISHED.
If you try to start radio, bluetooth or music app you will find that it cant be done because you removed factory launcher. The good thing is it should be booted, but it is not necessary for it to work in the background all the time.
6. So, install launcher2 that you backed up in step 3. It is now installed but it is not system app anymore.
7.Now. If you dont want to stick with nova launcher install the one you will use. I find car launcher pro best one out there.
8. Now, from google play download "autostart and Stay" app from google play. Install it.
9. Set service toggle of "autostart and Stay" to on.
11. In the app settings check "smart service on boot" and "pooling interval" on 5 seconds.
10. By usign "+" sign add launcher2.apk and launcher you choosed to use. On launcher2 make sure that "autostop" on boot completed is choosed and for the launcher you choosed "autostart" and "stay".
11. If you didnt do it already, using system app remover uninstall kingroot.
11. Reboot.
Thats it.
What we did?
With "autostart and Stay" we loaded but then stopped factory launcher and by checking "stay" we ensured that launcher we choose to use cant be stopped in the background by any other process-If you want you can choose "persist" instead of "stay" and set pooling interval on 60sec. It means that after using any other app more than 60 sec , you will be kicked out on home screen, but other apps you started wont be killed. It means that you can start radio or music, choose your track or tune and it will be working in the background even after you have been kicked to home screen. If you want to watch video, just extend pooling interval. 60 sec is enough for everyday use.
Thats it. Bye
So when I went to Google Play store to down load Android Auto it states my unit is not compatible. Didn't know why it's not compatible so I figured why not load it and try it.
I'm running Android 8 Hal build. It compress with the ability to run/install APKs.
Did a Google search for Android Auto APK using chrome in the head unit. Found a version, downloaded.
Opened that APK install program, opened the folder with the download in it, installed.
Low and behold it worked.
I use my phone as a hotspot and bluetooth connection.
Hope this helps others.
bobodaclownster said:
So when I went to Google Play store to down load Android Auto it states my unit is not compatible. Didn't know why it's not compatible so I figured why not load it and try it.
I'm running Android 8 Hal build. It compress with the ability to run/install APKs.
Did a Google search for Android Auto APK using chrome in the head unit. Found a version, downloaded.
Opened that APK install program, opened the folder with the download in it, installed.
Low and behold it worked.
I use my phone as a hotspot and bluetooth connection.
Hope this helps others.
Click to expand...
Click to collapse
Post the link to what you downloaded?
https://www.apkmirror.com/apk/googl...ging-4-5-592854-release-android-apk-download/
As requested.
Thanks by your info. Just checked and Android Auto installed. But, did ou get using Android Auto built-in phone dialer? In my case I got the message "network not found". It seems device is trying to use built-in 4G line instead phone line from celullar BT. Did you fix this issue?