yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] persmash:
Hi,

I've stock software installed Samsung Galaxy S9 with root. When I try to check updates, It says "The operating system on your device has been modified in an unauthorised way".

Is there any possibility to bypass that error and get updates?

Regards.
[General Questions and Answers] xXx yYy:
Samsung doesn' like it when you tamper the pre-installed Android OS, and that for good reasons: as soon as Android is got rooted the door is wide open for every hacker / malicious software and Samsung understandably doesn't want to have to take responsibility for damages that result from it.
[General Questions and Answers] persmash:
Are you saying that there is no way to bypass it? I've read some topics like fake system status etc. but I'm not sure if they are still working.
[Philips, Sony, TCL Android TV] yuvrajbais:
Hi all,

My Sony tv is kdl-55w800d and I want to connect my headphone or hometheater but not visible in my tv BT list pls help me.
[Touch Pro, Fuze General] thrillz21:
Any new IM that I get from AOL Instant Message (from the built in IM program) does not wake the phone up. how can I change that?

I have the Sprint Touch Pro
[Touch Pro, Fuze General] Brendo:
prob has nothing to do with touch pro. would be application problem
[Touch Pro, Fuze General] thrillz21:
is there anything we can do to make it wake up?
[Moto G7 Power Questions & Answers] lazylovesxda:
I’ve been looking at some Reddit posts of somebody using a Motorola g7 power metro model on lineage, I was wondering if mine was compatible before I brick it, kind of nervous.

Thanks

--

Edit: Just did it, works completely fine. :)
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] revengeramh:
hello guys my camera on curtana [redmi note 9s] crashes after updating EU rom to MIUI 12.5.4

any solutions?
[Android Q&A, Help & Troubleshooting] amn1987:
Google Play Services is causing high CPU usage and massive battery drain( >25%/h) continuously. Battery temps. cross 40°C in no time. The issue persisted upon rebooting the device. Had to finally freeze it.

In FKM, I/O section shows constant 20-25MB/s writes. "com.google.android.gms" and "com.google.android.gms.persistent" are the two processes causing consistently high CPU usage. There's also "jbd2/sda1-8".

After booting into Safe Mode the issue didn't persist. But still no idea what exactly is causing this issue.

Poco F1 running crDroid 7.14. This issue cropped up the first time ever in build 7.7. Only resolved after dirty flashing 7.13. NikGApps Core version.

Temp. fix (thanks to a TG user) : type the following in any Terminal emulator of your choice with the recommendation being Termux

su

pm disable com.google.android.gms/.chimera.GmsIntentOperationService

If not rooted maybe try via ADB.

Issue arises due to spoofing Pixels for the unlimited Google Photos backup hack. Real solution is either removal of the PixelPropsUtils framework or it's suitable modification. It's all in the hands of the ROM devs.
[Android Q&A, Help & Troubleshooting] amn1987:
Bump!
[Android Q&A, Help & Troubleshooting] arunsai123:
I am experiencing exaclty same issue. gms using lot of cpu and writes.
[Android Q&A, Help & Troubleshooting] amn1987:
I had to finally dirty flash the 7.15 build to fix it. Wiping System is necessary as a Poco X3 Pro user also running crDroid 7.x reported that without wiping System the issue persisted. It doesn't seem to be a specific GApps issue as he was using FlameGApps Basic.
[Android Q&A, Help & Troubleshooting] arunsai123:
I tried using flamegapps, nikgapps. it happens even at first boot. I am now using phone without gapps to prevent phone heating.
[Android Q&A, Help & Troubleshooting] amn1987:
It didn't recur at first boot in my case, about a few weeks later all of a sudden. If you did a dirty flash the System partition was wiped, right? If it was a clean flash then I have no idea. Better than using no GApps is to freeze it if rooted or disable it if not I guess.

If this happens after sometime again I will give Open GApps or MindtheGApps a try.

BTW which device and which ROM?

I had posted the log elsewhere as well but unfortunately it received no response.
[Android Q&A, Help & Troubleshooting] arunsai123:
It happened to cause the isssue after few weeks for me too. But at this time, it started do it even after a clean flash with none of 3rd party apps installed.

I have wiped everything (system - addon.d and data) before flashing. doesn't help.
[Android Q&A, Help & Troubleshooting] amn1987:
Oh! It's pretty concerning that even a clean flash didn't fix it. Unless someone takes a look at the log I don't think it's possible to ferret out the root cause. I tried by freezing every user app but to no avail.
[Android Q&A, Help & Troubleshooting] amn1987:
@arunsai123 Which Magisk version are you using?
[Android Q&A, Help & Troubleshooting] ImDooMLoRD:
Same is happening to me 😭

Someone help!!

Device - poco F1

Rom - pixel experience Android 12
[Android Q&A, Help & Troubleshooting] amn1987:
Interestingly when the device was unplugged and idle this bug had little to no impact on the idle drain. Probably because when unplugged and the screen if turned off I have set it up in Tasker to enable Battery Saver ( as it seems to help lower idle drain) and GMS Doze is enabled in NikGApps.
[Android Q&A, Help & Troubleshooting] ImDooMLoRD:
Sadly battery saver is not working for me.

I have encountered this thing on the last rom too .. I thought it was a rom issue

So have to change it to this one and Now, after a month of usage it started happening all of a sudden.
[Android Q&A, Help & Troubleshooting] amn1987:
I had posted this issue on Reddit as well but like here it unfortunately didn't attract the attention of anyone knowledgeable enough and/or willing to take a look at the log.
[Android Q&A, Help & Troubleshooting] ImDooMLoRD:
Every night goes like,

Battery usage stats and a screenshot of Franco kernel manager process tab ..

Things I have tried

1. Uninstalling every Gapps updates

2. Cache partition cleaned

3. Removing Google accounts completely turned off sync
[Android Q&A, Help & Troubleshooting] amn1987:
It seems it was the most severe in my case probably due to a second misbehaving process namely "com.google.android.gms.persistent" besides "com.google.android.gms". But idle drain wasn't affected. Only temporary fix other than a dirty flash involving wiping the System partition is to freeze Google Play Services. But it's not viable as paid apps like Tasker, FKM etc. stop working.

If and when this happens next I am gonna try LiteGApps, MindtheGApps or even Open GApps.
[Android Q&A, Help & Troubleshooting] ImDooMLoRD:
I don't think so this version of rom supports a dirty flash .

Last time I have done that my phone got bricked😑.

So, it's out of the question?

other than that I am not trying to again flash clean rom because it's gonna come again, I think.
[Android Q&A, Help & Troubleshooting] amn1987:
I guess it's because of encryption. MicroG should be immune to this issue probably but quite a few apps just don't work.
[Android Q&A, Help & Troubleshooting] ImDooMLoRD:
This rom just not compaitable with dirty flashing I tried it before but goes black screen or sometimes it doesn't even boot up.

Maybe because it's an initial build that's why or so..

I couldn't recall the exact issue that was before with the dirty flashing this rom or the previous one was oofgang poco pixel port.

Btw

I have done the Tasker think you did before it's , I think stable now for the time being.
[Android Q&A, Help & Troubleshooting] amn1987:
Does it help during active usage i.e. when the display is on, though? I hadn't checked.
[Android Q&A, Help & Troubleshooting] mmortal03:
Yes regarding a dirty flash where you're sticking to the same Android version of Lineage. That's basically how official Lineage updates work; they essentially get flashed over what you have.

But you wouldn't generally need to flash a newer version of MindTheGapps, because the apps themselves would be staying updated through the Play Store, and they should still be there when you dirty flash Lineage.

@amn1987 mentioned wiping System only, but I don't believe you even need to explicitly do that with a dirty flash in many cases. I believe you can just flash the updated Lineage zip. Now, sometimes it can cause problems depending on the ROM, but often it will work just fine.
[Android Q&A, Help & Troubleshooting] x0xb0x:
Oops sorry :-( but I totally forgot to mention that you cannot restore Google apps or banking apps or anything that uses intrusive system/sim queries/binding using SwiftBackup.

But these are a small percentage of your apps and you could follow the approach suggested by @amn1987
[Android Q&A, Help & Troubleshooting] amn1987:
In the last few Android versions apps switched from using a single device identifier to a unique one for every app. I had tried a few methods in the past but none worked.
[Android Q&A, Help & Troubleshooting] cjdijk:
For me it's a matter of time saving. Not having to reconfigure every single app, so I guess it's going to work for most of the Apps. I have installed Swift Backup, created a backup. Lets see how much time is saved when a clean install is needed. Only time will tell.

Has anyone looked at my uploaded locat.zip, to see which process is draining my battery?

Why is MindTheGapps-11.0.0-arm64-20230812.zip not available, can someone create it?

I honestly think that will solve my battery draining problem, more details in my ealier post:

https://xdaforums.com/t/temp-fix-ro...to-google-play-services.4406617/post-88912153
[Android Q&A, Help & Troubleshooting] amn1987:
I had tried almost every GApps package earlier in my quest to ferret out the culprit and it made no change. Only microG helped but despite using a modded Play Store I still couldn't get my paid apps to work unlike earlier.
[Android Q&A, Help & Troubleshooting] x0xb0x:
Inside your logcat there is a constant barrage of exceptions from gms appearing frozen/dead throwing Exceptions all the time:

08-23 05:51:02.847 660 677 E ActivityManager: Failure starting process com.google.android.gms.persistent
08-23 05:51:02.847 660 677 E ActivityManager: java.lang.SecurityException: Package com.google.android.gms is currently frozen!
...
08-23 05:51:02.847 660 677 I ActivityManager: Force stopping com.google.android.gms appid=10130 user=0: start failure
08-23 05:51:02.848 660 677 I ActivityManager: Force stopping service ServiceRecord{667e5fe u0 com.google.android.gms/com.google.android.location.internal.server.HardwareArProviderService}

Exceptions such as this appear in your logcat more than 5000 times !!!!

Seems as if your gms is totally messed up. In my devices have a lot of intents disabled but my logcat does not look anything like yours mate.

Have you tried clean flashing everything? If I recall correctly LineageOS recommends MindTheGapps but if you are running an unofficial version maybe the ROM developer recommends something else ?

This is latest MindTheGapps for Android 11: https://mindthegapps.com/download/#mind-the-gapps-android-11

You also need I guess the 64bit version.

With such a convoluted logcat as yours with many thousands of exceptions in less than 10 hours it is expected that your battery will be empty very fast.

If I were you I would totally clean flash after backing up with SwiftBackup. I never ever dirty flash anything - neither Gapps nor OTA.

I even format system to be sure and then keep the resulting setup for quite some time.
[Android Q&A, Help & Troubleshooting] cjdijk:
Thanks for the help. I did use a clean flash, exact steps described in my earlier message:

https://xdaforums.com/t/temp-fix-ro...to-google-play-services.4406617/post-88908349

I didn't know it was possible to just install the zip using twrp and nothing else. Also didn't know about Swift Backup, so haven't used that. I did however choose to import settings/apps from my Google Account. Also my hosts file might be edited to prevent mobile data eating, adding these 2 lines:

127.0.0.1 ota.googlezip.net

127.0.0.1 ota-cache.googlezip.net

Also I have used a newer MindtheGApps instead of the one you have provided the link. (See the same earlier message.) So I might want to try installing the old MindtheGApps from your link. Just flash this zip using twrp and nothing else? I do I need a clean flash (like described in my ealier message).
[Android Q&A, Help & Troubleshooting] x0xb0x:
I would just clean flash again everything mate. And download the official build of linegeos for your device from the project's page. Only resort to Sourceforge for old builds.

You have probably done this before but here it goes:

Format cache system data dalvik/art cache. Reboot recovery. Be very careful because with a formatted system you will bootloop without a rom.

Now flash rom. DO NOT reboot before flashing Gapps. Flash Gapps. Now boot system.

Do not flash magisk from recovery. The Magisk author dissuades this and in my case it has at least once caused weird crashes

Boot to your rom and setup magisk as described on the project's Github Readme. Do not flash magisk from recovery do it as described on Github with fastboot and the boot.img, vbmeta procedure.

Then pm disable Chimera as in the first post and put the ota hosts block inside Adaway.

Restore whatever apps can be restored through SwiftBackup. The rest

manually.

I avoid Google backup/restore I do it manually for the apps refusing to work with SwiftBackup.

Sourceforge has LOTS of older roms and all possible Gapps versions. It is very nice but usually these are unofficial builds. Check the project/maintainer's name on Sourceforge ro be sure.
[Android Q&A, Help & Troubleshooting] cjdijk:
Thanks for the help. But I know that if I'm going to flash the latest official Lineage from 2021 (Lineage-18.1-20210107-UNOFFICIAL-potter.zip), then I will get battery draing issue for sure. Same like I had when using the latest official CrDroid (crDroidAndroid-11.0-20221213-potter-v7.25). That worked without battery draining until it was older then about 3 months. I'll try the unofficial Lineage from this month (llineage-18.1-20230808-UNOFFICIAL-potter_security-patch-date_2023-08-05.zip) with the latest official GApps from 6 months old (MindTheGapps-11.0.0-arm64-20230323.zip). Also I'm going to clean flash it, to make sure nothing's left behind from my current install. Time to check out Swift Backup. To be continued.
[Android Q&A, Help & Troubleshooting] amn1987:
In 2021 builds iorap.cmd.compiler was included which caused battery drain. Personally experienced this in an old device of mine. After a long gap a new build was available in which this issue was fixed finally as sometime in 2022 iorapd was removed from AOSP itself.
[Android Q&A, Help & Troubleshooting] cjdijk:
For some reason I wasn't able to backup data, from backup Apps option, using Swift Backup, it says root access needed? All other things have been backup to my external storage. So I guess I'm trying just flashing the old MindTheGApps, without anything else like wiping or formatting. That should work, without the need to reconfiguring all apps (as mmortal03 says). And if it doens't I can do the clean install after that. Installing just the old MindTheGApps went fine. All apps are working including banking apps without having to reconfigure or using Swift Backup. Lets see if the battery draing is solved. Now using llineage-18.1-20230808-UNOFFICIAL-potter_security-patch-date_2023-08-05.zip with MindTheGapps-11.0.0-arm64-20230323.zip To be continued.
[Android Q&A, Help & Troubleshooting] x0xb0x:
Another extra step I also do is either manually erase internal storage or do it it from TWRP "format storage"

The reason is that the "Android" leftover folder on your /storage/emulated/0 from your previous install, contains a significant amount of extra Gapps related configs which could easily mess things up.

If you have photos that you haven't backed up, just remove the Android folder using TWRP terminal via rm command and leave the other folders you need intact.

TWRP is a powerhouse but needs caution.
[Android Q&A, Help & Troubleshooting] x0xb0x:
You need Magisk root and unfortunately the only recommended way is to install Magisk with the fastboot process described in its Github documentation.

No way around that, there is anecdotal evidence of Magisk working via TWRP flashing but the developer strongly recommends against that. Fastboot only for me so as to have working Zygisk.
[Android Q&A, Help & Troubleshooting] x0xb0x:
And the worst issue about iorap.cmd.compiler is it's deeply embedded in the kernel. No disabling approach for this one. Just killing it and it comes back. A mess indeed.
[Android Q&A, Help & Troubleshooting] amn1987:
I have always flashed Magisk via the recovery over the years. Only in case of updates I let Magisk do it's thing.

Edit: Without root Swift Backup can only restore the apps but not their data with the help of Shizuku.
[Android Q&A, Help & Troubleshooting] amn1987:
Yes. Suppressing the issue arising out of Pixel Spoof comparatively is a walk in the park. One fellow had mentioned some build.prop tweaks to disable iorapd and apparently it worked for him but in my case it just led to a never ending bootloop. I had made use of Cool Tools to keep an eye on the processes causing max. CPU usage and everytime iorapd reared it's ugly head I would terminate it with extreme prejudice!
[Android Q&A, Help & Troubleshooting] cjdijk:
Just wondering, in case the old MindTheGApps doesn't make any difference. (I still do think a newer MindTheGApps would work.) If I search my phone on https://wiki.lineageos.org/devices/#motorola it's not there at all? I have a Moto G5 Plus (potter), not Moto G5 or Moto G5S or Moto G 5G plus. See https://xdaforums.com/t/rom-unofficial-10-0-potter-lineageos-17-1.4088253/
[Android Q&A, Help & Troubleshooting] mmortal03:
A lot of people in this thread are dealing with high CPU Google Play Services issue *because* they are needing to use unofficial builds for their devices (official not available), and the unofficial builds for their devices happened to include Pixel spoofing. But this official/unofficial distinction may not hold past LineageOS because there are ROMs that call themselves official but include Pixel spoofing. Is there really still the bug causing this in official, current LineageOS builds after a few months?

It literally says UNOFFICIAL in the filename, just pointing that out. :)
[Android Q&A, Help & Troubleshooting] mmortal03:
Yep, as you know, we have the same phone, and LineageOS no longer supports our phone. We have to use unofficial LineageOS builds if we want LineageOS.
[Android Q&A, Help & Troubleshooting] cjdijk:
One week ago I've switched to llineage-18.1-20230808-UNOFFICIAL-potter_security-patch-date_2023-08-05.zip with MindTheGapps-11.0.0-arm64-20230323.zip, becouse with lineage-18.1-20230708-UNOFFICIAL-potter_security-patch-date_2023-07-05.zip I was having battery draining. It shouldn't have it, becouse it's not older then 3 month's. That's my experience from other rom's like DotOS and CrDroid. So I thought it was caused by the old GApps.

Yesterday I've installed one year older MindTheGapps-11.0.0-arm64-20220217_100228.zip (but official intstead of unofficial) using twrp, without anything else like wipe of format. To be honest, I didn't think that would fix it, but it seems it's actually working. I have used 12% in 18 hours. Not actively using it during the weekend. But still about half as much as before.

This means: Date of GApps isn't important, but you need an official one. But the rom date has to be max 3 month's old. And the one I'm using isn't official, but working fine. I already knew that, becouse i've tested this rom (lineage-18.1-20230708-UNOFFICIAL-potter_security-patch-date_2023-07-05.zip) also without GApps, and that didn't have any battery drain. (Using same apps as usual, installed apk's from pc to phone with adb).

@x0xb0x: You were right about GApps. You can use an old one, as long it's official. The newer unofficial one was actually the cause of my battery draning problem.

@mmortal03: You were right about just Installing the zip from twrp without aanything else like wiping of formatting. That works fine when switching to another date of the same Rom or GApps. Saving lots of time, no need to re-configure any apps.

@gothicVI: Thanks for still supporting Moto G5 Plus (Potter). I've heard from you, you will put monthly updates on androidfilehost. Keep up the good work, much appreciated.

Thank you all 3 for fixing my problem. Next 3 month's I think I can use my phone without battery drain. And also after that if lineage keeps beining updated. If I'm wrong and battery draining comes back soon, I will put an update here. But for now it looks promising. I'm very happy now.

Small status update. After 36.5 hours, not used my phone very much, but constantly turned on, without any recharging. used only 21%. I will put another logcat online tomorrow. But it seems my battery drain problem is gone for sure.

And another update. I have used 34% (from 100% dropped to 66%) of battery in 60 hours. Constantly turned on, never connected to anything to avoid charging. Battery saving turned on, not very active use of my phone. To campare: When I was using the newer/unofficial MindTheGApps it was 58% (from 100% dropped to 42%) of battery in 60 hours, also battery saving turned on and not active use. Here's the locat.txt just created in about 10 minutes of logging.
[Android Q&A, Help & Troubleshooting] cjdijk:
This weekend I noticed te battery draining was back again. Using lineage-18.1-20230808-UNOFFICIAL-potter_security-patch-date_2023-08-05 with MindTheGapps-11.0.0-arm64-20220217_100228. @gothicVI: Unfortunately still no new version of Lineage available on androidfilehost. @amn1987: So I have installed NikGapps-basic-arm64-11-20230716-signed lets see if that's fixing it. This might work, I still think both of them need to be max 3 months old. I guess if one of them (GApps) is very old, the other one (Lineage) needs to be max 1 month old.
[Android Q&A, Help & Troubleshooting] mmortal03:
I have my doubts about that logic, but you'll just have to let us know.

Btw, gothicVI said probably no more potter builds (e.g. security patch backports) from him: https://xdaforums.com/t/rom-unofficial-10-0-potter-lineageos-17-1.4088253/page-8#post-88898929
[Android Q&A, Help & Troubleshooting] x0xb0x:
@rocker00 Saw your post from ages ago about rebuilding framework.jar without spoofing and tried to do the same but failed spectacularly for Crdroid 7.x Android11. I know the exact smali code to be edited but it seems to not matter...

With any approach followed, i.e. apktool only, apktool+manual baksmali, MT-manager, zipaligned or not etc the resulting framework.jar is non-bootable.

Verified too with simply disassemble-reassemble jar and keeping smali code intact, always bootloop.

Various attempts made with clean flashing for many framework jars and always on first boot 'adb logcat' shows Zygote dying and bootlooping.

If anyone has any hints on disassembly/reassembly of framework.jar on Android 11+ I'd be grateful.