Hi all,
so yesterday I flashed CM7 on my Legend after having Modaco's Customized ROM installed. However, I have the same issue as some users with GPS. I've tried flashing all different Radio versions available, but I just can't get a GPS fix (neither with Maps nor with GPS Status).
Does anyone have a solution to this?
Thanks!
My Gps only works when i use this radio version 7.08.35.21 from http://forum.xda-developers.com/showthread.php?t=706435
i'm CM7 nightly built 42 to...
hello,
I had problems myself with the cm7 stable. gps was not working. But then wipe data, cache and cache dalvik, re-flash cm7, install radio 7.08, gapps... then boot... made the apps restore reboot again. then turn on gps status and in 20secs had a fix with 7 satelites.
this is my contribution to the comunity.
Edit: I Just wanna say that is working but not 100%. So i believe, that should have some bug fix in the next days. because not every legend respond well with the two radio that people says to install.
[Q] no wifi in TyphooN CyanogenMod 7 Nightly v3.6.4
Having wifi problem with V3.6.4.
Cannot start wifi
status: fault (next to checkbox)
normally I can check the checkbox and it states "inschakelen"
checksum is ok
have reverted to 3.6.3
change your kernel tytung r12 i think your use
flash different
3.6.4 is tytung R12....
have updated through clockworkmod. has already worked several times.
I went back to 3.6.3 (restored clockworkmod backup )
Hello,
I'm currently running Xylon - May 15th build and Franco Kernel 137 and May 15 Banks GAAPS.
I cannot receive phone calls, as soon as the phone starts to ring I get com.android.phone has stopped notice.
I can make calls but the com.android.phone service stops immediately after I hang up.
I tried changing Kernels from Franco M2 to 134 to 135, 136 and 137 but the issue persists
I updated from May 9th Xylon to May 15th and no dice still.
Wipe Dalvik/Cahe and all that stuff.
Changed GAAPS versions.
Nothing seems to fix it. Can anyone point me in the right direction?
All better
Nevermind folks.
I fixed it by doing a factory reset (boo!) , reinstalling newest Zylon, Flashing Newest Official GAAPS and reinstalling newest Franco.
Not the route I wanted to go but if it works, it works.
I just installed ParanoidAndroid, latest build and latest gapps after a clean flash. I've only used stock up until now but figured I'd give it a shot (although I've done plenty of ROM installation, etc. on my last phone).
Everything works great except GPS; I can't get a fix at all. I tried getting assistance data with GPS Status, tried rebooting, no luck. It just keeps waiting for a fix. Any idea what's wrong?
EDIT: THIS WAS RESOLVED IN THE NEW 20171231 NIGHTLY, EVERYTHING WORKS PERFECTLY NOW!
So I have this problem with Lineage OS 13 on my N10, so I flash the following packages:
Super SU 2.78
Busy-box
Open Gapps 6.0 nano
Lineage 13 10/14/17 nightly
The first boot is successful, I install some apps, watch some videos, normal tablet stuff. The problem is when I reboot, every time I reboot it ends in a boot loop. The tablet just won't boot up after I reboot it. The first boot works great, but nothing works after-wards.
Doesn't work on mine either, with CM13 20171017 build. I also made comment on the CM14 build thread here on XDA. I couldn't complete the initial setup using the CM14 build. I'm going back to stock.
I have the same problem with 20171021
I was able to reproduce the Error and attatched a logcat.
The bootloop always started while installing the App "immobilienscout24".
Hope someone can examine my logcat. I attached 2 (split) files, because I don't know, what is relevant.
Best regards
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
BerlinOtto said:
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
Click to expand...
Click to collapse
So basically I have to pick my apps wisely or lineage will reboot? **** that noise I'd rather run stock lollipop, lineage on my N10 is awful.
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
I have the same issue of constant boot loops. I tried several LOS nighly build w/o any success.
Funny thing is, after i rolled back to an old CynogenMod backup (v13.0 snapshot from 21.12.2016) it started to boot loop too, after I started updating my apps with Playstore.
So the bug must be very old, and it must be in CM/LOS, not in some specifiy app...
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Marktplaats causes boot loop
In my case, 'marktplaats', a dutch app, caused the boot loop. At some point I decided to upgrade to Lineage. I never had any issues on Cyanogenmod 13.
There seems to be a solution for this Problem in the newest nightly, See
https://jira.lineageos.org/browse/BUGBASH-1052
I've done a test Installation with my two Problem apps and it works fine for me.
I0tacle said:
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
Click to expand...
Click to collapse
All the problems were fixed in the in 20171231 nightly, running it without hitch no, stable and fast MM with CM theme support, finally