The MOG Mobile Music App gives me a message complaining about no internet connection, or the fact that it can't connect to servers, and it doesn't get past the initial startup splash screen for me to log in or do anything. I've tried forcing it into offline mode several ways, but the app simply will not launch completely. I have perfect internet connection with everything else. It is working just fine on the October 14th Nightly, but is unusable past this, most notably on October 16th and beyond. This is an issue on ALL CM-Based ROM Nightlies dated past Oct 14 such as Beanstalk, Carbon, PACman, etc. So I know it is an issue with a CM patch/update past Oct 14. Is there any way I can resolve this? Running it on a Motorola Atrix HD on the kernel that came with a ROM, I could try another kernel but I doubt it would help anything. Is anyone else having the same issue on other phones? Originally I thought it was a JB 4.3.1 issue but seeing as Oct 14 runs on 4.3.1 it is not. I always clean flash.
Same Problem
Neighbor808 said:
The MOG Mobile Music App gives me a message complaining about no internet connection, or the fact that it can't connect to servers, and it doesn't get past the initial startup splash screen for me to log in or do anything. I've tried forcing it into offline mode several ways, but the app simply will not launch completely. I have perfect internet connection with everything else. It is working just fine on the October 14th Nightly, but is unusable past this, most notably on October 16th and beyond. This is an issue on ALL CM-Based ROM Nightlies dated past Oct 14 such as Beanstalk, Carbon, PACman, etc. So I know it is an issue with a CM patch/update past Oct 14. Is there any way I can resolve this? Running it on a Motorola Atrix HD on the kernel that came with a ROM, I could try another kernel but I doubt it would help anything. Is anyone else having the same issue on other phones? Originally I thought it was a JB 4.3.1 issue but seeing as Oct 14 runs on 4.3.1 it is not. I always clean flash.
Click to expand...
Click to collapse
Seems like I'm not alone in trying to figure out why MOG hasn't been working for my phone. I came from a Google Play Store ROM of 4.3 on my Samsung Galaxy S4, which was working fine but wanted to test out CM 10.2. However, since switching to CM 10.2 a few days ago, I have not been able to get on MOG. I thought it might been an issue with MOG until I restored from the backup prior to CM 10.2 and it's working fine. I'm not sure what patch is in CM 10.2, but I would agree with Neighbor808 that something is causing an issue with MOG.
Fuzzums said:
Seems like I'm not alone in trying to figure out why MOG hasn't been working for my phone. I came from a Google Play Store ROM of 4.3 on my Samsung Galaxy S4, which was working fine but wanted to test out CM 10.2. However, since switching to CM 10.2 a few days ago, I have not been able to get on MOG. I thought it might been an issue with MOG until I restored from the backup prior to CM 10.2 and it's working fine. I'm not sure what patch is in CM 10.2, but I would agree with Neighbor808 that something is causing an issue with MOG.
Click to expand...
Click to collapse
Same issue for me on a Verizon Samsung GS3. Had to go back to 10.1 because I use MOG all the time. Hope someone addresses this.
Me too on galaxy s3 att - either with CM 10.2 or task650. I've had to revert to 4.2. Then you can at least download a bunch of music for offline use and then restore a tibu (as long as you don't disturb the MOG folder in the sd card) and play like that. It sucks, but MOG won't help you since they're committed to beats audio only.
Mog locat
I really hope this thread hasn't died. I have been digging for about a week and i'm at a loss. It seems something changed with cm around oct 14 and ever since then (already stated) that mog doesn't connect. If I stay at the mog startup screen I get the connection was lost message. And also I can get into settings, I get all the usual options but whats weird is at the top it says i'm not logged in and the only option I get is to sign out. I also was able to speak to mog tech support for a couple of days before they figured out I was rooted, at wich time they stated they cannot help me, but they stated all problems with androud 4.3 have been resolved so i'm pretty sure the problem is cm 10.2 and not 4.3. I pulled a logcat of my phone sitting at idle, opening mog, sitting some more and then closing the app. I'm not very experienced at coding or reading logcats but I did run across this
I/SELinuxMMAC( 615): package (com.mog.android) installed with seinfo=default
I/ActivityManager( 615): Process com.cyanogenmod.lockclock (pid 15208) has died.
I/ActivityManager( 615): Force stopping package com.mog.android appid=10099 user=-1
W/PackageManager( 615): Not granting permission android.permission.READ_LOGS to package com.mog.android (protectionLevel=50 flags=0xbc44)
W/PackageManager( 615): Not granting permission android.permission.BIND_WALLPAPER to package com.mog.android (protectionLevel=18 flags=0xbc44)
W/PackageManager( 615): Unknown permission android.permission.START_BACKGROUND_SERVICE in package com.mog.android
W/PackageManager( 615): Not granting permission android.permission.DEVICE_POWER to package com.mog.android (protectionLevel=2 flags=0xbc44)
W/PackageManager( 615): Unknown permission com.verizon.vcast.apps.VCAST_APPS_LICENSE_SERVICE in package com.mog.android
Like I said I dont really know what any of that means but I tried to do research of what w/packetmanager and i/activitymanager are but I am unable to figure anything out.
If anyone is able to decipher any of this I would be very grateful. Also if it helps I have posted the full logcat below
I appreciate any and all help on this problem and I really hope someone can figure this out and get mog working for people running 10.2
http://www.2shared.com/document/1GgfAm9f/mog_launch_and_run.html
new development
I don't remember where but in passing I read that another carrier blocked streaming music. I found that when I tried to use Google play much I got an error similar to the one in Mog. I'm not sure how but I guess you have to dial into the phone and change settings to allow streaming. Going top do more research and hopefully figure something out.
Edit
must have been a temporary problem with Google play, looks like music is working. I really don't want to switch but might be the inky way.
Related
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again
Q&A for Lollipop 5.0 runs on our msm8960s on kkbl
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Lollipop 5.0 runs on our msm8960s on kkbl. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery Life
derpyherp said:
I think its odd how there is no deep sleep state i put a screen shot of the cpu times at each cpu speed... Its odd but somehow battery life is amazing
Click to expand...
Click to collapse
I switch back to cm11 because i have 6%/hr of battery drain, (7hr/41min Screen on time, 65% left), that is for me horrible battery life.
I did not look the cpu states, but, if there is no deep sleep, it sould explain mi experience about battery.
I have the same mensage when I was in f2fs. I have to go back to ext4 to work.
Does anyone know if the AOSP Camera will be made available? I don't like the Google one since it doesn't allow me to choose the external SD card as a storage option.
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Cubkyle said:
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Click to expand...
Click to collapse
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
iBolski said:
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
Click to expand...
Click to collapse
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
The first time , I flashed 11/15 version, everything seems to work fine ,then I flashed gapps, then I got no signal anymore,but everything else seems to work, so I did a factory reset, the gsm signal came back again, today when I trying to flash 11/18 version, the signal gone again, this time I don't want loose my data , what should I do to get a gsm signal? *#*#4636#*#* seems not working on 11/18, sorry for my poor english
Cubkyle said:
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
Click to expand...
Click to collapse
Ah, I'm familiar with those errors as well as the ID10T error as well.
Works just fine, very smooth. Had no troubles with the signal at all.
However, I can't receive a call, the dialer just stops. It is possible though to make a call. Anyone had this problem?
yes had that error many times "dialer has stopped", this is work in progress man. I hope that dhacker checks this and the other thread and try to remedy some of the prob.
For that dialer has stopped error, a reboot can cure it. But again i cant rely on a phone that is going to quit when you need to make or receive a call.
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
I had an odd issue on 11/22 build:
When I connect my car via bluetooth, when a call comes in, pressing the answer button does nothing and the call keeps ringing forever.
Also,
Is Anyone having issues with restoring on TWRP 2.8.1.0? I tried restoring a backup I made and my phone won't boot. It just gets stuck at the cyanogen mod screen.
Edit: I restored a previous backup, installed TWRP 2.8.2.0 and then restored the backup I was trying to. It worked.
dvgb173 said:
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
Click to expand...
Click to collapse
On my 11/25 build data wasn't working at first, I just turned it on and off from settings and it started working.
11/25 build is working for me as far as being able to receive phone calls. I was previously getting FCs on it when an incoming call was coming, but I was also running f2fs. I've gone back to ext4 and things seem to have stabilized at this point.
This build is the dhacker? I found nothing in his link. Many changes over the previous build?
When open 3g ,call comein can not.
How to fix it?
Thank.
soowijux said:
When open 3g ,call comein can not.
How to fix it?
Thank.
Click to expand...
Click to collapse
Now, I install 30/11 it OK.
Thanks.
SMS issue
Is the sms issue (can't receive sms, although the phone I'm sending from receives the delivery report) still present in this new build (12-02)? I've tried the 11-25 build and BlissPop and none of them allowed me to receive sms... It's the one real issue that's keeping me from jumping into Lollipop
Razr HD (XT925, KK bootloader)
My device does not come out of the boot with this version.
I'm currently on the latest CM12.1 Sultan-Mod. Last week I got a new car which supports Android Auto (Volkwsagen Columbus Headunit), at the beginning I got a connection a few times, but all the time with frequent connection losses ("Error: USB Device" shown on Headunit), the longest period it worked was about 1 hour. Today on my phone I got the message "Communication Error 7", now it's not possible to get a stable connection at all.
I've tried removing the car from the auto app and removing the auto app but without success. Has anybody been able to get a working connection between a CM12.1 device and a car?
Missing features after resetting mobile
Hi,
I am using OPO with CM 12.1. Yesterday i have reset my mobile and few apps and features (Screen Pinning,Screenshot,Menu button ) are missing after resetting my mobile. Please let e know the solution.
I've tried different CM13 Nightlies and CM12.1 without success now. Seems like Android Auto won't work with the OPO at the moment.
For future notice, I was having this same problem all of a sudden on my Nexus 6P, found how to fix it.
Uninstall updates for Google Play Services, it's a buggy install that is doing it. Found a few other forums talking about it, did it myself, and even after it re-updated, everything is working fine. I had to plug it in and unplug it several times, and it finally gave me all of the prompts again to start like new.
I was having some issues with my Galaxy s6, so I figured if they stopped supporting my phone, I might as well get a new OS on it myself.
I rooted and installed 9.0
https://forum.xda-developers.com/ga...20x-5x-nexusos-9-0-samsung-galaxy-s6-t3843199
At first I tried to install previous versions of Lineage, but kept having issues with registering through google, but this one worked pretty easily. I am now using Nova launcher.
The issues I have with it are:
Slower GPS location, like much slower. I am now traveling in Toronto, and it's ridiculously slow to find where I am compared when i was in NYC. I'll continue testing though, maybe it was just a temporary bug
Battery drain seems faster. I was hoping to get an improvement on this issue.
I get no notifications when I get messages through "google voice' I have to open the app to look at it
There is no number in a red circle next to the app to tell me number of messages for it
Substratum not working, keep getting "could not fall back to rooted mode" although according to root checker, I'm rooted. I have no experience with this app, but it seems like it's worth checking it out lol
I think there may be more 'issues' but those are the main ones right now.
I use the latest OFFICIAL LineageOS 14.1, these works fine for me.
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Lagarde said:
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
nasch007 said:
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
Click to expand...
Click to collapse
Appreciate you looking at that. I haven't tried 18.1 yet, as I'm a bit gunshy after how bad 17.1 went for me. I'm strongly suspecting most of my issues go back to Project Fi...but it's not the SIM. I've actually bought 2 extra SIMs over the years trying to resolve this very issue. They all do the same thing on LOS.
Hadn't seen the splitting of gapps. That's news to me. Will look into that, as Project Fi requires the largest of the gapps...which is too big to fit into the system partition.
Lagarde said:
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
shaunoleary said:
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
Click to expand...
Click to collapse
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
AsItLies said:
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
Click to expand...
Click to collapse
Not using TWRP, I'm just using LOS recovery. Sadly, it doesn't allow for doing backups, but it does the job otherwise.
Just an update BTW - currently running into issues with Google Pay/SafetyNet, but it's due to Google playing silly buggers with GPay again, not the fault of LOS.