Database Users

Annoying bugs with cynogenmod

I have come across a very annoying bug with cm12.1 version for 550m...everytime I reboot the phone gets stuck in bootloop almost all the time...half of the time it keeps optimizing apps and then gets stuck at starting apps and other half it just gets stuck in bootloop...it has made installing xposed modules so difficult since it takes me 4-5 rebbots to get even strted with my phone after downloading a module...can anybody help please...

I have no problem with rebooting on my 550. It sometimes hangs on starting apps on first boot after flashing, but turning off and back on solves this (except with broken 0819 build). Xposed may be the cause of your problem - the devs have said countless times that it is not supported and not recommended. If you want to use xposed, you are better off staying on stock or using super zen.

Xposed causes this on CM. It's not supported.
Sent from my serial terminal

Maybe the MediaScanner is going crazy.
I was having the exact same issue as you.
Try to reboot your phone until cyanogenmod boots successfully and run this command on terminal app or adb.
It will disable media scanning on boot.
su
pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver

if you want to run cm with xposed.... then run the initial (first) build of cm12.1... Xposed is well supported

LG G2 D02 CM 13 Problems

My boss rooted his LG G2-D02 and installing CM 12.1 in the process. Now, after knowing that CM 13 was already released, he downloaded a copy of it and immediately flashed it onto his phone. He got a problem with Gapps and DL-ed a problematic version which caused the notification,"Unfortunately, Setup Wizard has stopped" to pop up repeatedly. We had tried following a few advices from this website but to no avail.
1.) We already tried using Force Stop and Disable under Apps->(Show system apps)->Setup Wizard (CM). I had also tried giving it app permissions, but all app permissions were already available.
2.) The only option is to flash CM 12.1 back again but it can't be done. My boss set the default recovery app to Cyanogenmod's own recovery program, which had limited functions, so I can't
also use TWRP ATM.
3.) My boss also tried something on ADB but to no avail
4.) Factory reset didn't also solve the problems.
I'm almost running out of solutions... Perhaps, I can use a helping hand from brighter minds in this community.
TIA

I'm using cloudyg2 v3.3 because cm13 has got a lot of bug for example
-I can't proceeded to music
-systtem has stopped once a hour
-I can't close touching vibration
I can't remember now but cm13 has got really much bug (yeah my english is very bad,I know this)

Now system is stable and battery is very very good but still İ can't scretch to music

Frequent restarts after update to OxygenOS 5.0.4

Dear community,
I've recently updated my OnePlus 5 to Oxygen OS 5.0.4 from 4.5.15 or so (last 4.x version). I wiped everything, then flashed 5.0, then 5.0.4, then restored data with Titanium Backup. Among others, I am running Magisk 16, Xposed 90b3 and several modules for each of these (Greenify4Magisk, Google lens enabler, OOS call recording, GravityBox, Flat Style Bar Indicators, Greenify etc.).
Almost ever since I made the update I get very frequent restarts (10-20 or more per day). I just noticed that my smartwatch is disconnected and I have to re-enter the pin when unlocking the phone. At times the phone restarts several times in a row. One thing I noticed that it only restarts while the screen is off.
I tooks 7 logcat logs via ADB with warning (and worse) filter, but I am thinking that it might not be a good idea to post them here in the open** (I don't know if I can anonymize them) . If anybody wants to take a look at these logs I'll pass them in private.
Otherwise if there would be a way to wipe the private information out of the logs (like some logcat apps seem to be able to do), please point me to the right information source.
Thanks for all the help!
**If I am mistaken about this assumption, please correct me.
PS: What I noticed as being different from before the update is that this time I installed Greenify4Magisk.

Android Auto: Something Went Wrong (Google Play Services)

I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.

I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.

GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution

GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?

KERNEL Crash on every rom

So I tried flashing LineageOS16 and I keep getting a Kernel Crash at the beginning of the boot animation. It says
Every Single ROM I Flash, A kernel crash happens whether that'd be lineageOS or Ressurection Remix, they always result in a kernel crash the beginning at the boot animation.
It always results with this
Kernel Panic - not syncing: Resetting the SoC - modem crashed.

Possible solution
Howdy, What model Lg v20 are you using example F800L/k/s US995. I have the f800l and I flashed SuperROM By DudeAwsome and it had everything I needed in it unfortunately I was unable achieve root though but the kernel didn't crash when I kept it totally stock.. I hope it helps google search F800-Hybrid on android host, I can't link anything unfortunately as I'm new.