Hey everybody, i get the error: Unfortunately, Google Play services has stopped. about 4 times a minute and my phone is unusable! i tried the following but it didnt fixed the problem for llonger than 2h. I'm using a gs3 (i9300) with 4.4.4 kk Archidroid 3.0.2 and boeffla kernel.
for everybody still struggeling with g.p.s. fc's:
ok best would be a clean system(cache,dalvik,system, data, inertnal storage).
if the error occurs,
1. go to settings-->apps-->g.p.s. (google play service)
2. write down the last 3 numbers (example: 7.5.71_(1955121-034)--> 034
3. uninstall updates + clear cache+ manage space-->clear all data
4. restart phone
5. reinstall g.p.s. update from google play store.
IF THAT FAILS:
1. go to http://www.apkmirror.com/apk/google-inc/google-play-services/
2. download the newest version with your 3 letters in the end: example: i have 034 --> i download:
Google Play services 7.5.74 (1997312-034) ||| please compare with the attached guide if the numbers are right (see end of my post)
3. install the apk
4. go to settings-->apps-->g.p.s. (google play service)
5. clear cache+ manage space-->clear all data
6. restart phone
Important: you need the right version or it will show up a error while installing. You can find out the right version with this tut:
To figure out the right version of Google Play services for your Android device, go to Settings -> Apps -> Google Play services, and look at the last 3 numbers in the parentheses. You'll see something like -XYZ where:
* X defines Android version:
0 for Android <5.0
4 and 7 for Android >=5.0
8 for Android TV
* Y defines CPU architecture:
1 for armeabi
3 for armeabi-v7a
4 for arm64-v8a
7 for x86
* Z defines DPI:
0 for universal
2 for 160
4 for 240
6 for 320
8 for 480
Notes:
It seems that -7YZ builds became -4YZ with Google Play services 6.5. If you were on -7YZ before, you should now install -4YZ.
Looks like -8YZ builds are for Android TV.
Examples:
-014 for Android <5.0 armeabi CPU 240 DPI device
-438 for Android 5.0+ armeabi-v7a CPU 480 DPI device
-876 for Android TV x86 CPU 320 DPI device
Click to expand...
Click to collapse
Moreover the following solution is not working for me, i need my gps on high accuracy most of the day.
Set the location to "Device only" instead of "High accuracy", this stops the error completely until google fixes the issue...
Click to expand...
Click to collapse
Is there another solution out there? IT looks like they fixed that problem for lollipop builds, so why its not fixable for kk?
push*
oh and if i turn off gps google play service is causing a massive wakelock
BOYS I GOT IT!!!!!!!!!!! HERE IS THE FINAL SOLUTION FOR G.P.S. FC'S!!!
The problem is caused by libjavacore.so Arter released a fix for (what i think) lollipop releases only for info, DONT FLASH!. it forces a bootloop for 4.4.4.
BUUUUUUT Markox89 released this issue fixer but i was scared of destroying all optimzed libs and data from archidroid. so i copied Markox89s libjavacore.so aaaaaaaand it works!!!!
So step by step now:
1. download attached libjavacore.rar AND EXTRACT!!!!
2. Put the libjavacore.so somewhere on your phone
3. restart to TWRP (recovery)
4. make a nandroid backup (to be save if bootloop) --> full backup
5. open up mount and mount system
6. go to advanced and open file manager
7. now copy the new libjavacore.so (press on it and copy)
8. go to /system/lib
9. paste it
10. not sure if necessary but i pressed on libjavacore.so and sed chmod 755
11. reboot problem solved!!!!!!!!!!!
12. wipe data and cache from gps to avoid wakelock!
13. install myandroidtools from playstore
14. reboot.
15. open myandroidtools --> services --> system
16. go to Google Play Services and google-services-framework and enable (make a tick at) at "System update service". (this will stop the google play services wakelock)
17. reboot. and your done
Wohoooooooo iam pretty happy and running late for a party, but i needed to share hf guys
Useful fixes for LineageOS 14.1
I am very glad that you are here!
It may be helpful to you:
__________________________________________________
Rollback to the official Android 4.1.2 without a PC
Today, we will roll back to the official android 4.1.2 without a PC, through custom recovery.
You need a phone S2-i9100 with the ability to enter into the recovery and installation of the zip file.
__________________________________________________
Restore the firmware on Samsung GT-I9100 Galaxy S II.
More detailed instructions on firmware with Odin.
__________________________________________________
[Guide/Tutorial] Installing LineageOS 14.1 + TWRP-3.1.0-0 for Samsung Galaxy S2 i9100
More detailed instructions on firmware with Odin.
__________________________________________________
Script remove the superuser indicator "#" !
Hello, I noticed that many of you don't like the superuser indicator ('#')
in the status bar and that some of you even flash SuperSU or Xposed, just to get rid of it.
Well, that's not necessary, because there is a much easier way.
__________________________________________________
Script fix Dialer for LineageOS !
- Has large photo of the caller
- Improved the display speed of the caller
- Enable call record (in test mode)
- In order to improve the quality of the recording of telephone conversations,
use a headset (headphones with microphone) !
__________________________________________________
Script fix CMFileManager for LineageOS !
If you have such a problem in the LOS!
"CMFileManager: not see the internal memory or it says that I need elevated rights to do..."
Root rights are recommended.
__________________________________________________
Script fix LockClock for LineageOS !
Weather widget clock with two assembly suppliers (OpenWeather and Yahoo weather).
__________________________________________________
Script fix Ril for LineageOS !
If you have such a problem in the LOS of 02/08, 02/13, 02/16 !
"Each time when I end a phonecall (no matter if it's incoming our outgoing calls)
I get a popping message that there is no reception, and the antenna shuts for about half a minute and then returns ..."
__________________________________________________
Root Addon Packages for Lineage OS!
Fixed the error 4, when installing addonsu-arm-signed.zip !
"addonsu-arm-signed.zip can't flash via recovery. Gives an error : Updater process ended with signal: 4 ..."
__________________________________________________
Download the scripts here__________________________________________________
Reserved...
Great job mate, thanks for the awesome fixes :good:
MigoMujahid said:
Great job mate, thanks for the awesome fixes :good:
Click to expand...
Click to collapse
Mutually, you also do many useful things!
You can also post useful fixes and additions here, just be sure to test them first!
LOS is constantly evolving, but with the advent of Innovations - appear flaws and inaccuracies!
I think our "Useful fixes for LineageOS 14.1" will serve for a long time and help all those who need it !
Thank you all...
@toy_story: Hi, can you please post the source code that need to be changed to enable call recording?
ale5000 said:
@toy_story: Hi, can you please post the source code that need to be changed to enable call recording?
Click to expand...
Click to collapse
Hello, I will write about the standard application Dialer.apk in CM and LOS.
In many countries, the recording of calls is prohibited by law. Google, SM, LOS and others, just protect themselves from trouble:
- They in the Dialer.apk application have installed filters for countries and mobile operators, who can be recorded and who can not.
- Changed the libraries and again the problem kernel.
Okay the lyrics aside, go to work, what needs to be done:
1) Unpack the firmware or copy from the already installed, but we have the file Dialer.apk.
2) Decompile Dialer.apk.
3) On the path: Dialer \ res \ values \ look for the file bools.xml
4) Using a text editor (preferably using Notepad ++ or something similar) open bools.xml
5) We search and check the line:
<Bool name = "call_recording_enabled"> true </ bool>
If instead of true it is written false ,change to true
6) Save the changes.
7) Next on the path: Dialer \ res \ values-mcc202 \ open the file bools.xml and edit the line:
<Bool name = "call_recording_enabled"> false </ bool>
Replace false with true
8) This line should be changed in all, from "values-mcc202" to "values-mcc505".
How many "values-mcc" , in so many countries is prohibited from recording a call!
Only after correcting all "values-mcc" , in the phone during the call to appear a choice for recording.
9) Compile (collect back) Dialer.apk
10) What to do with properly configured Dialer.apk, I think you know.
@toy_story: Thanks, do you know also a method to change the country detected by the phone?
Does it use the CSC?
If yes, can it be changed without change the ROM?
ale5000 said:
@toy_story: Thanks, do you know also a method to change the country detected by the phone?
Does it use the CSC?
If yes, can it be changed without change the ROM?
Click to expand...
Click to collapse
Hi, you could have done that before.
The record could be included by writing only 2 lines to the file "build.prop" or to install a suitable module for "Xposed"
Now if you take the application "dialer.apk" from LOS and from CM 13, it will be almost two different applications:
- change system libraries
- Enhance application security
- structure, location, and standard behavior
The control (check) is in 5 places, us for the time being limited to the easiest filter for the "MCC" country code.
And I think that a proven and well-working "Xposed" on android 7.1.? We will not see soon!
toy_story said:
Hi, you could have done that before.
The record could be included by writing only 2 lines to the file "build.prop" or to install a suitable module for "Xposed"
Now if you take the application "dialer.apk" from LOS and from CM 13, it will be almost two different applications:
- change system libraries
- Enhance application security
- structure, location, and standard behavior
The control (check) is in 5 places, us for the time being limited to the easiest filter for the "MCC" country code.
And I think that a proven and well-working "Xposed" on android 7.1.? We will not see soon!
Click to expand...
Click to collapse
I mean another thing.
I'm not sure but there should be another memory somewhere to flash.
Correct me if I'm wrong but doesn't CSC survive a format of the /system partition?
When you flash LineageOS it should read the country somewhere in the phone (I think) since the ROM is the same for all countries.
ale5000 said:
I mean another thing.
I'm not sure but there should be another memory somewhere to flash.
Correct me if I'm wrong but doesn't CSC survive a format of the /system partition?
When you flash LineageOS it should read the country somewhere in the phone (I think) since the ROM is the same for all countries.
Click to expand...
Click to collapse
Hi! No, you're wrong.
Yes, the disk is the same for all countries, but it already has different settings and behavior for different languages. Now when installing "LOS Pom" , the system automatically determines where we are (installation language), before this was not.
Behavior for countries is recorded in the form of a blacklist, according to the qualifications of "MCC" and "MNC".
MCC (Mobile Country Code) - the mobile country code in combination with MNC is the unique identifier of the cellular operator of GSM, CDMA, iDEN, TETRA and UMTS networks, as well as some satellite communication operators. ITU-T Recommendation E.212 defines mobile country codes.
MNC (Mobile Network Code) - the mobile network code in combination with MCC is the unique identifier of the cellular operator of GSM, CDMA, iDEN, TETRA and UMTS networks, as well as some satellite communication operators. ITU-T Recommendation E.212 defines mobile country codes.
Example:
Next on the path: Dialer \ res \ values-mcc202 \ open the file bools.xml and edit the line:
<Bool name = "call_recording_enabled"> false </ bool>
"Mcc202" - country code Greece
"Bools.hml" - with the parameter > false <
If we do not change to > true <
Then with this "POM" in the territory of Greece, the recording of the call will not work.
Previously, without modifying the "POM" workaround, the "modules" for "Xposed" were made.
toy_story said:
Hi! No, you're wrong.
Yes, the disk is the same for all countries, but it already has different settings and behavior for different languages. Now when installing "LOS Pom" , the system automatically determines where we are (installation language), before this was not.
Behavior for countries is recorded in the form of a blacklist, according to the qualifications of "MCC" and "MNC".
MCC (Mobile Country Code) - the mobile country code in combination with MNC is the unique identifier of the cellular operator of GSM, CDMA, iDEN, TETRA and UMTS networks, as well as some satellite communication operators. ITU-T Recommendation E.212 defines mobile country codes.
MNC (Mobile Network Code) - the mobile network code in combination with MCC is the unique identifier of the cellular operator of GSM, CDMA, iDEN, TETRA and UMTS networks, as well as some satellite communication operators. ITU-T Recommendation E.212 defines mobile country codes.
Example:
Next on the path: Dialer \ res \ values-mcc202 \ open the file bools.xml and edit the line:
<Bool name = "call_recording_enabled"> false </ bool>
"Mcc202" - country code Greece
"Bools.hml" - with the parameter > false <
If we do not change to > true <
Then with this "POM" in the territory of Greece, the recording of the call will not work.
Previously, without modifying the "POM" workaround, the "modules" for "Xposed" were made.
Click to expand...
Click to collapse
I have installed it without SIM.
Before installation I have wiped system, data, cache (almost everything).
How can it detect country?
How can I verify what country is detected?
ale5000 said:
I have installed it without SIM.
Before installation I have wiped system, data, cache (almost everything).
How can it detect country?
How can I verify what country is detected?
Click to expand...
Click to collapse
Yes, I agree. Without a SIM card and without an Internet connection, applications will not determine in which country you are.
But you still insert a SIM card and will be connected to the Internet!
As soon as you insert the sim, the cellular operator will immediately tell your phone which country you are in.
Hi,
I just made a test with a fresh install of lineage-14.1-20170322-nightly-i9100-signed.zip, gapps pico with TWRP.
I installed Fix_addonsu-arm-signed.zip without errors, but the phone is still not rooted.
Any ideas what is going on?
As far as i remember last time i rooted it i had to use CWM-SuperSU-v0.97.zip too.
Thanks!
Edit: Please, ignore the above zzzz - i simply forgot to assign root rights to adb+apps in developer settings.
s2l9100 said:
Hi,
I just made a test with a fresh install of lineage-14.1-20170322-nightly-i9100-signed.zip, gapps pico with TWRP.
I installed Fix_addonsu-arm-signed.zip without errors, but the phone is still not rooted.
Any ideas what is going on?
As far as i remember last time i rooted it i had to use CWM-SuperSU-v0.97.zip too.
Thanks!
Click to expand...
Click to collapse
Follow the path:
Settings - Developer options - Root access - choose Apps and ABD
Check root access.
Restore the firmware on Samsung GT-I9100 Galaxy S II
More detailed instructions on firmware with Odin.
Script remove the superuser indicator "#" !
Script remove the superuser indicator "#" !
Hello,
I noticed that many of you don't like the superuser indicator ('#') in the status bar
and that some of you even flash SuperSU or Xposed, just to get rid of it.
Well, that's not necessary, because there is a much easier way.
So here is the "right way" to remove the "#":
Set in TWRP: Hide_SU_Icon.zip - Download
P.S. After the first power-up, you may need to reboot!
Disliked Returned back !
Set in TWRP: SU_Icon-REVERT.zip - Download
Script fix Dialer for LineageOS !
Script fix Dialer for LineageOS !
- Has large photo of the caller
- Improved the display speed of the caller
- Enable call record (in test mode)
- In order to improve the quality of the recording of telephone conversations, use a headset (headphones with microphone) !
Set in TWRP: Fix_Dialer.zip - Download
Be sure to "Wipe Cache / Dalvik"
If you see the message "Failed to start call recording" - do a reboot!
Disliked Returned back !
Set in TWRP: Dialer-REVERT.zip - Download
P.S.After installation, the phone briefly be slightly hotter than usual, this is due to the optimization of application.
Script fix CMFileManager for LineageOS !
Script fix CMFileManager for LineageOS !
If you have such a problem in the LOS!
"CMFileManager: not see the internal memory or it says that I need elevated rights to do..."
Root rights are recommended.
Set in TWRP: Fix_CMFileManager.zip - Download
Be sure to "Wipe Cache / Dalvik"
When you first start it may not see the folders, you need to reboot!
P.S. In nightie LOS from 02/26 before 03/29 deleted CMFileManager!
But the script still works well!
Script fix LockClock for LineageOS !
Script fix LockClock (version 3.5) for LineageOS !
Weather widget clock with two assembly suppliers (OpenWeather and Yahoo weather).
Set in TWRP: LockClock_LOS-mod.zip
Disliked Returned back !
Set in TWRP: LockClock_LOS-REVERT.zip
Wipe cache/dalvik after flash do not necessarily.
P.S. If you have installed my script "LockClock_LOS-mod.zip!" .
after upgrade LOS, even after the OTA,
it is necessary to again set in TWRP: LockClock_LOS-mod.zip!
Script fix Ril for LineageOS !
Script fix Ril for LineageOS !
If you have such a problem in the LOS of 02/08, 02/13, 02/16 !
"Each time when I end a phonecall (no matter if it's incoming our outgoing calls) I get a popping message that there is no reception, and the antenna shuts for about half a minute and then returns ..."
Set in TWRP: Fix_Ril - Download
Mi 9T, MIUI 11/Android 10 (11.0.4.0 QFJEUXM), rooted Magisk), installed Adaway (ofc, must use systemless hosts)
I found that I was unable to connect to the public hotspots - it was not opening the hot-spot accept conditions/login page
By examining a logcat I found:
-ActivityTaskManager(1598): START u0 {act=com.miui.action.OPEN_WIFI_LOGIN dat=http://connect.rom.miui.com/...
...
-OpenWifiLogin(30894): IOException: java.net.ConnectException: Failed to connect to connect.rom.miui.com/::1:80
Upon whitelisting connect.rom.miui.com, phone successfully opens the login page again and I can connect to the public hot-spots
You may or may not have this login to hot-spot problem (with AdAway, DNS66, Blokada...) depending on which hosts sources you use
However, if you don't block connect.rom.miui.com (or you don't use an ad blocker), be aware that MIUI sends some data to its server every time you are connecting to a public hot-spot (?!)
Btw, http://connect.rom.miui.com is valid site (Welcome to nginx! - see a screenshot), and I found a similar report on the Net:
https://www.reddit.com/r/Xiaomi/comments/bk6viy/redmi_note_7_issues_with_public_wifi_networks/
zgfg said:
Mi 9T, MIUI 11/Android 10 (11.0.4.0 QFJEUXM), rooted Magisk), installed Adaway (ofc, must use systemless hosts)
I found that I was unable to connect to the public hotspots - it was not opening the hot-spot accept conditions/login page
By examining a logcat I found:
-ActivityTaskManager(1598): START u0 {act=com.miui.action.OPEN_WIFI_LOGIN dat=http://connect.rom.miui.com/...
...
-OpenWifiLogin(30894): IOException: java.net.ConnectException: Failed to connect to connect.rom.miui.com/::1:80
Upon whitelisting connect.rom.miui.com, phone successfully opens the login page again and I can connect to the public hot-spots
You may or may not have this login to hot-spot problem (with AdAway, DNS66, Blokada...) depending on which hosts sources you use
However, if you don't block connect.rom.miui.com (or you don't use an ad blocker), be aware that MIUI sends some data to its server every time you are connecting to a public hot-spot (?!)
Btw, http://connect.rom.miui.com is valid site (Welcome to nginx! - see a screenshot), and I found a similar report on the Net:
https://www.reddit.com/r/Xiaomi/comments/bk6viy/redmi_note_7_issues_with_public_wifi_networks/
Click to expand...
Click to collapse
its same with every vendor, like apple does it to captive.apple.com
anirudhks said:
its same with every vendor, like apple does it to captive.apple.com
Click to expand...
Click to collapse
Probably most send some data one way or another (btw, I don't use iPhones for that and several other reasons), but it is good to know for some who encounter a similar problem with ad blockers, when trying to connect to the public hotspots
Btw, some hosts sources for AdAway/DNS66 also block miui.com or update.miui.com, but update.miui.com is repository for downloading firmwares - eg, open (enable Desktop site):
https://c.mi.com/oc/miuidownload/detail?guide=2
and try to download some firmware - if you cannot, whitelist:
update.miui.com
EDIT:
Also, for Mi Account, to login and sync (backup/restore) the following two must not be blocked:
api.micloud.xiaomi.net
sgpac.account.xiaomi.com
Hey. I had the same issue. Make sure your DNS is set to automatic.
For some reason Xiaomi does not let you access DNS settings directly. You have to install quick shortcut make and access com.android.settings.Settings$NetworkDashboardActivity from the setting.
I didn't take into account your rooted phone. You may have the option right away or it may be one of the apps you installed.
tkiafar said:
Hey. I had the same issue. Make sure your DNS is set to automatic.
For some reason Xiaomi does not let you access DNS settings directly. You have to install quick shortcut make and access com.android.settings.Settings$NetworkDashboardActivity from the setting.
I didn't take into account your rooted phone. You may have the option right away or it may be one of the apps you installed.
Click to expand...
Click to collapse
As described above, access was blocked due to one of host source lists for AdAway (and solved as described above)
Im not using Private DNS, but you can set Private DNS (easier than by shortcut maker apps) through Hidden Settings for MIUI app, available from Playstore, root not required
To login and use Mi Account two more URLs must be whitelisted:
api.micloud.shaomi.net
sgpac.account.xiaomi.com
All together, I white-list four of them, i.e. these two also (as in the above posts):
update.miui.com
connect.rom.miui.com
This is needed (only) if using a particular hosts source blocking Xiaomi/MIUI analytics:
https://raw.githubusercontent.com/j...ter/Extension/GoodbyeAds-Xiaomi-Extension.txt
This maybe old thread, but if you are rooted/ just use adb from PC, you can change the default captive portal back to original/stock :
adb shell settings put global captive_portal_https_url https://google.com/generate_204
adb shell settings put global captive_portal_http_url http://google.com/generate_204