Hi, all Nightly's not working since the April versions. I cant connect to Playstore, cant create a Google account (after deleting it) and the connections symbols get orange. The 26032014 works fine. Are there some problems with the M5 versions ?
Greets Tim
Tried clean flashing?
Sent from Google Nexus 4 @ CM11
timsxda said:
Hi, all Nightly's not working since the April versions. I cant connce to Playstore, cant create a Google account (after deleting it) and the connections symbols get orange. The 26032014 works fine. Are there some promblems with the M5 versions ?
Greets Tim
Click to expand...
Click to collapse
nightly's of which rom buddy?
Working fine: CM-11-20140326-NIGHTLY-maguro
Not Working: CM-11-20140402-NIGHTLY to CM-11-20140405-SNAPSHOT
Installed with Update Service of Cyanogenmod
timsxda said:
Working fine: CM-11-20140326-NIGHTLY-maguro
Not Working: CM-11-20140402-NIGHTLY to CM-11-20140405-SNAPSHOT
Installed with Update Service of Cyanogenmod
Click to expand...
Click to collapse
You hear me? Try clean flashing? CM sometimes implement changes that break dirty flash (update).
Sent from Google Nexus 4 @ CM11
No, i cant hear you ... did you ever hear a forum ?
Full new install was working (of course), but not the best way, just wanted to use the Auto Updater ... so far so good
Sup guys,
Just flashed the new nightly LineageOS 14.1 on my galaxy s5, everything went fine and smooth but after flashing gapps, the decive works for a few seconds then freezes completely, no thouch screen works and no buttons working, i need to remove the battery to restart it, anyone with the same issue? Already tried 3 gapps versions and reflash the system twice, but it keep freezing...
tyvm
edit:
just flashed AOKP rom and had the same problem...
I had the same issue, I installed an older version of OpenGapps (from the 19th of Jan) and all is well so far.
philberttfrog said:
I had the same issue, I installed an older version of OpenGapps (from the 19th of Jan) and all is well so far.
Click to expand...
Click to collapse
Thanks 4 ur answer, i'll try this now...
I installed the stock rom, but its a awful, so im tryinf lineage again
edit:
wow! it seems to be working perfectly now, tyvmw, love u haha
I also had an issue with the Open GApps but, when i used the Dynamic GApps, it worked great for me.
Sent from my SCH-I535 using XDA Free mobile app
aDDxD said:
Sup guys,
Just flashed the new nightly LineageOS 14.1 on my galaxy s5, everything went fine and smooth but after flashing gapps, the decive works for a few seconds then freezes completely, no thouch screen works and no buttons working, i need to remove the battery to restart it, anyone with the same issue? Already tried 3 gapps versions and reflash the system twice, but it keep freezing...
tyvm
edit:
just flashed AOKP rom and had the same problem...
Click to expand...
Click to collapse
Yes, I had the same problem. Going to wait until the updates stabilize or if someone can help understand which Gapps to use.
Thanks
I was experiencing the same issue. Now I've installed an older version and its working fine.
Back to ground zero
It worked fine for a few hours. Now it's unusable again.
Here's some good alternatives that seems to be pretty stable for the LOS14.1/CM14.1 ROM's (though the Delta GApps are good, i would recommend the Dynamic GApps as the first alternative):
DOWNLOAD LINKS:
Dynamic GApps
Delta GApps
Delta GApps - Latest Release {20170118-1}
XDA GAPPS SUPPORT THREADS:
Dynamic GApps
Delta GApps
Open GApps
Sent from my SCH-I535 using XDA Free mobile app
Hi gueys,
last week i installed Lineage 14.1 on my galaxy s 5, coming from the samsung firmware. After flashing the device always freezed after short time. In a forum I read, that the problem is at the current opengapps-Version. After flashing an older version of the gapps the problem seemed solved. But today the problem is back, i guess there was an Update for the Google Apps. Now I will test the mentioned alternatives.
I apologize to my English, it is my schoolglish and the school is already 20 years ago.
I tried Dynamic Gapps, it worked for about 20 mins; I was able to install apps and everything but then it started to freeze. The only one that hasn't frozen ever for me was: crDroid 7.1, but the disadvantages were that Mobile Data didn't work nor did the camera! Anyone else found a fix, I want to get a good ROM which is blazing fast!
Full dynamic gapps woked for me. Thanx a lot for this post. I was really starting to pull my hair out here!!
If you guys haven't figured it out yet. A Dalwik wipe will fix this issue!
Hi.
Definitely working nothing. I tried every variation which was posted in this an other topics.
After "Google Play Services" upgrade everything going bad, freeze, restart, etc., can't use the phone.
I tried to use "Gapps" before and after 2017.01.19.
If somebody have any useful solution please share with me.
Thanks in advance.
otixi said:
Hi.
Definitely working nothing. I tried every variation which was posted in this an other topics.
After "Google Play Services" upgrade everything going bad, freeze, restart, etc., can't use the phone.
I tried to use "Gapps" before and after 2017.01.19.
If somebody have any useful solution please share with me.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
Finally I found on this webpage the "Official Galaxy S5 Duos Lineage OS 14.1 [klteduos] [7.1.2 Nougat]" lineageosdownloads.com/download-official-galaxy-s5-duos-lineage-os
I downloaded "lineage-14.1-20170503-nightly-klteduos-signed.zip" and with this rom working perfect every new "GAPPS" before and after update too.
otixi said:
Hi,
Finally I found on this webpage the "Official Galaxy S5 Duos Lineage OS 14.1 [klteduos] [7.1.2 Nougat]" lineageosdownloads.com/download-official-galaxy-s5-duos-lineage-os
I downloaded "lineage-14.1-20170503-nightly-klteduos-signed.zip" and with this rom working perfect every new "GAPPS" before and after update too.
Click to expand...
Click to collapse
That's great news you were able to get your klteduos booted. I've been trying since January to get a newer version that will even boot and have been unsuccessful as you've described.
Many of the images I've managed to download from the source you quote above seem to be completely hopeless in terms of doing virtually anything (such as getting beyond the boot screen).
Currently (early/mid July 2017) only the following images are available:
lineage-14.1-20170705-nightly-klteduos-signed.zip
lineage-14.1-20170621-nightly-klteduos-signed.zip
lineage-14.1-20170614-nightly-klteduos-signed.zip
lineage-14.1-20170607-nightly-klteduos-signed.zip
I've tried every single one of these and they all hang at boot time, requiring removal of the battery (god knows I won't be getting any newer Samsung mobiles as one cannot even "remove" the battery from the later models).
An online search for lineage-14.1-20170503-nightly-klteduos-signed.zip reveals several sites that once had the image, but none currently.
May I kindly entice you to upload the image you successfully booted somewhere online?
I've actually been trying to find an image that functions with both SIMs since December 2016, when the second SIM simply stopped connecting to the network (irrespective of which SIM slot they are in - yes, I did connect successfully when using the second SIM in another phone and I have been carrying around two phones since that time, AARGH!).
Non-stop headaches with these mobile devices nowadays...
aDDxD said:
Sup guys,
Just flashed the new nightly LineageOS 14.1 on my galaxy s5, everything went fine and smooth but after flashing gapps, the decive works for a few seconds then freezes completely, no thouch screen works and no buttons working, i need to remove the battery to restart it, anyone with the same issue? Already tried 3 gapps versions and reflash the system twice, but it keep freezing...
tyvm
edit:
just flashed AOKP rom and had the same problem...
Click to expand...
Click to collapse
So Ive flashed 14.1 and instead of not booting it boots and then crashes when I'm using it
To all those who are having issues, and require support, for the the Official LineageOS 14.1 on their Galaxy S5 would receive much better within the following Official LineageOS thread for the S5...
[ROM] [OFFICIAL] LineageOS 14.X for Galaxy S5 | Android 7.X Nougat by haggertk
I wish you all the best of luck!
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Ibuprophen said:
To all those who are having issues, and require support, for the the Official LineageOS 14.1 on their Galaxy S5 would receive much better within the following Official LineageOS thread for the S5...
[ROM] [OFFICIAL] LineageOS 14.X for Galaxy S5 | Android 7.X Nougat by haggertk
I wish you all the best of luck!
Click to expand...
Click to collapse
Thanks much for the referral.
So sad that all this time has gone by and I still have not found the actual image that was reported to function correctly...
[deleted]
Hiya,
I've just flashed PA 7.2.1 and OpenGapps Pico on my hammerhead device. Everything works great, I love the PA ROM. However, I cannot get Google Now cards to work. I suppose there's something missing from Google ecosystem, I've installed Google Search app together with Google News & Weather app, still no luck tho.
Any suggestions, please?
Thx a lot!
moodycz said:
Hiya,
I've just flashed PA 7.2.1 and OpenGapps Pico on my hammerhead device. Everything works great, I love the PA ROM. However, I cannot get Google Now cards to work. I suppose there's something missing from Google ecosystem, I've installed Google Search app together with Google News & Weather app, still no luck tho.
Any suggestions, please?
Thx a lot!
Click to expand...
Click to collapse
Well, in many places we do recommend Open Gapps, but for me, it seems it´s missing some stuff and/or not working good for most devices. My first suggestion, long press the home button to Google window to show up and accept, after that it should work and appears.
If not as an a try, flash Beans Gapps, and be sure you are using our Launcher3 which already includes Google Now cards when you swipe from left to right. Also be sure that you´ve signed up.
So I flashed both AICP and ABC January 8.1 ROMs today (one at a time) using 2 different unofficial OpenGApps packages. After setting up the ROMs (re-install backup from the cloud option), I noticed that I was unable to activate the Say 'OK Google' any time in the Google Now app. When I opened the section in settings<voice the switch quickly moves to the off (left). Underneath it says that this is unavailable in my language (UK English - hence the grey not gray in the heading btw!).
I tried many many solutions from Google, clearing data etc but nothing worked. I have since reinstalled stock January 8.1 firmware and it works fine. I re-installed from backup in the cloud option like before.
What is going on? Has this happened to anyone else? Can you offer a solution?
[EDIT] - I tried a different third GApps package (unofficial BeansGApps). Problem solved.
Hi am2012
I have exactly the same problem. I've tried everything (except changing the gapps).
Which BeansGApps have you installed?
I only found this file to download (BeansGapps-NoGAssistant_arm64-8.1.x-unofficial-December.zip), but "NoGAssistant" is strange...
Could you post the link from you downloaded ???
Thanks...
EDIT - Thanks a lot am2012. It's finally solved!!! I intalled the BeansGapps file ( BeansGappsMini-arm64-8.x.x-unofficial-Feb2018.zip ) from the AndroidHostFile site.
am2012 said:
So I flashed both AICP and ABC January 8.1 ROMs today (one at a time) using 2 different unofficial OpenGApps packages. After setting up the ROMs (re-install backup from the cloud option), I noticed that I was unable to activate the Say 'OK Google' any time in the Google Now app. When I opened the section in settings<voice the switch quickly moves to the off (left). Underneath it says that this is unavailable in my language (UK English - hence the grey not gray in the heading btw!).
I tried many many solutions from Google, clearing data etc but nothing worked. I have since reinstalled stock January 8.1 firmware and it works fine. I re-installed from backup in the cloud option like before.
What is going on? Has this happened to anyone else? Can you offer a solution?
[EDIT] - I tried a different third GApps package (unofficial BeansGApps). Problem solved.
Click to expand...
Click to collapse
i use aroma gappes from nezorflame [GAPPS][ARM][ARM64][8.1] Unofficial OpenGApps builds for Android Oreo.
euler_santos said:
Hi am2012
I have exactly the same problem. I've tried everything (except changing the gapps).
Which BeansGApps have you installed?
I only found this file to download (BeansGapps-NoGAssistant_arm64-8.1.x-unofficial-December.zip), but "NoGAssistant" is strange...
Could you post the link from you downloaded ???
Thanks...
EDIT - Thanks a lot am2012. It's finally solved!!! I intalled the BeansGapps file ( BeansGappsMini-arm64-8.x.x-unofficial-Feb2018.zip ) from the AndroidHostFile site.
Click to expand...
Click to collapse
Sorry, I was at work. Yes, the BeansGApps work well.
Do you have a link to the gapps because I can't find an Oreo 8.1 beangapps.
I have recently updated my operating system to the latest stable by Xiaomi EU (by updated, I mean I have wiped and fresh installed the latest one).
All is well however the official Google Maps app is "not compatible with your device" now in the Play Store.
All other apps install just fine along with some other Google apps I use like Translate.
Does anyone know why this has happened?
I have also wiped and fresh installed previous versions of the Xiaomi EU builds in an effort to get this working but no luck.....Weird because it no longer works on builds it HAS previously worked on..
Thanks for reading, and thank you in advance for any feedback.
Kaji said:
I have recently updated my operating system to the latest stable by Xiaomi EU (by updated, I mean I have wiped and fresh installed the latest one).
All is well however the official Google Maps app is "not compatible with your device" now in the Play Store.
All other apps install just fine along with some other Google apps I use like Translate.
Does anyone know why this has happened?
I have also wiped and fresh installed previous versions of the Xiaomi EU builds in an effort to get this working but no luck.....Weird because it no longer works on builds it HAS previously worked on..
Thanks for reading, and thank you in advance for any feedback.
Click to expand...
Click to collapse
It seems a Google bug affecting chiron. Just change device's fingerprints. I choose Pixel 2, but you can use Mi Mix 2s, as you wish. You should be able to update or install Google Maps.
toneeloco said:
It seems a Google bug affecting chiron. Just change device's fingerprints. I choose Pixel 2, but you can use Mi Mix 2s, as you wish. You should be able to update or install Google Maps.
Click to expand...
Click to collapse
You are awesome, thank you.
Kinda unfortunate about the bug, means no matter what ROM we use it's gonna be the same. Hopefully they fix soon.
I have the same issue... but help, how to change device's fingerprints?
mr2k said:
I have the same issue... but help, how to change device's fingerprints?
Click to expand...
Click to collapse
I just checked the play store and the bug seems to be fixed!
If you still have the issue, download a build.prop editor and change the device's build.prop file.
You'll need to change the parts which state the model of the phone for example "device name: chiron"
By changing this to something like "Polaris" (Mix 2s) instead of "chiron" it will trick Google.
Edit: You will need to be rooted. And I recommend BuildProp Editor by JRummy Apps
It's solved!
Which MiUI.eu version installed on your phone?
0xFast said:
Which MiUI.eu version installed on your phone?
Click to expand...
Click to collapse
Right now, 9.3.28 (beta) but this was a Google issue, not a ROM issue.