Related
all kernel based on arco kernel have this bug
The kworker process use too many cpu when the touch screen is working
is a really big kernel bug. no other phone have this bug (you can also see this bug when you play games)
i have many other android phone (galaxy ace, s3 mini, 2 ideos u8150, motorola defy mini, galaxy next) and only galaxy w use too many cpu when you touch the screen
can someone kernel developer fix this? please?
darix96 said:
all kernel based on arco kernel have this bug
The kworker process use too many cpu when the touch screen is working
is a really big kernel bug. no other phone have this bug (you can also see this bug when you play games)
i have many other android phone (galaxy ace, s3 mini, 2 ideos u8150, motorola defy mini, galaxy next) and only galaxy w use too many cpu when you touch the screen
can someone kernel developer fix this? please?
Click to expand...
Click to collapse
The kworker process is not really a process but a placeholder for other working kernel processes.
However it´s not showing up for me one single time, so not sure what kernels you tested to claim all kernels based on Arcos kernel are having this bug.
response
honeyx said:
The kworker process is not really a process but a placeholder for other working kernel processes.
However it´s not showing up for me one single time, so not sure what kernels you tested to claim all kernels based on Arcos kernel are having this bug.
Click to expand...
Click to collapse
Yes, I concour with you honeyx, kworker is a placeholder and a pool for other processes inside the kernel, but it holds and runs processes like the touchscreen input processing. The process handle the touchscreen input incorrectly and uses too much CPU. I think that the problem is also related to surfaceflinger heavy use. Using the CPU for those tasks is like wasting power and throwing it directly to garbage bin! Also my nexus 7 had this problem, but it ws resolved with Android 4.3 update at the level of kernel!
simone.rolando.1998 said:
Yes, I concour with you honeyx, kworker is a placeholder and a pool for other processes inside the kernel, but it holds and runs processes like the touchscreen input processing. The process handle the touchscreen input incorrectly and uses too much CPU. I think that the problem is also related to surfaceflinger heavy use. Using the CPU for those tasks is like wasting power and throwing it directly to garbage bin! Also my nexus 7 had this problem, but it ws resolved with Android 4.3 update at the level of kernel!
Click to expand...
Click to collapse
Yes, i agree just it´s not happening for me. By googleing a bit about this problem I also found it was always only related to a few people. Others didn´t have this issue though they were using the same device and the same ROM and kernel. So to me this seems to be more a coincidence problably caused by some background processes, apps or for example by the used launcher.
honeyx said:
Yes, i agree just it´s not happening for me. By googleing a bit about this problem I also found it was always only related to a few people. Others didn´t have this issue though they were using the same device and the same ROM and kernel. So to me this seems to be more a coincidence problably caused by some background processes, apps or for example by the used launcher.
Click to expand...
Click to collapse
Or hardware issue, like the one with the white screen flashing when waking up the phone on rev 3 displays. That's a hardware issue and it affects only the users with LCD rev 3 displays. I'm not saying this is the case. I'm just saying this might alao be the case. Anyway, saying that all the kernels have this problem seems indeed a bit exaggerated to me too.
Sent from my GT-I9195 using Tapatalk 4
isn't hardware issue, this bug is appared from the cm9-cm10-10.1 stock the bug is absent
by the way the compass sensor doesn't work...is a known bug?
MMMM
In this world there are 2 kinds of people... people who don't care about a constant crashing interface or application, that uses the phone also if it has the display half broken or if it lags every 2 seconds... on the other side there are people that cares about the smallest lag that a phone does or the smallest imperfection in scrolling.
The last kind of people just download an app fom the play store and checks the cpu usage every millisecond... if they see that the CPU use is excessive there is something that doesn't work properly. Effectively, that's true because a friend of mine has a galaxy w with cm 10 and has the same issue... Also my nexus 7 had this issue, but it was resolved with the android 4.3 update. I noticed that the cpu use on nexus 7 was anomalous when I was touching the screen with a finger or morem and that's not the project butter.
Here is updated Thermanager, which could be flashed in recovery. I have made some changes after I played Asphalt game for about one hour. With this update, on performance governor the temperature never went higher than 58. And we are talking 1 hour straight. I doubt you can have that on stock. What was interesting that performance governor produced less heat than interactive, which supports my claim that when cpu jumps frequencies, it creates additional overhead.
Now, regarding myths and fiction about stock rom not overheating. There are some dudes on this forum who complain that their Z1 overheats to 70+ on custom roms when they play their beloved games; on stock, they say, there is no overheating.
Here is a short answer. You, guys, don't know what you are talking about.
Custom roms (and custom kernels) give you tools that are not available in stock. You just have to learn how to read/use them. Here is one example: some roms allow you to have internal cpu temperature on screen. Now that you have it, you watch. When it hits 70, you panic, but if you touch the back door, it will be barely warm. So, when you are on stock and without temperature reading, you think your phone is not overheating, while it can still have 65-70.
I used a modified version of M5 kernel compiled with GCC 5.2.1 Ubertc; CPU at 2457; performance governor, inteliplug balance with touch boost disabled; GPU overclocked to 600 with msm-adreno-tz idle wait 30 and workload 3; swapiness 10; enthropy 1024 read/write. That was on DU rom, but I bet the result would be the same on Jaguar and some other custom roms.
lol, that dude is Me, and I will try this, in the stock rom I can see an process running as overheat manager or something, I think it might have to do something with it. I'm sure that my device got heated very much, I didn't meant to offense but you seems to got it wrong. btw I will try this. I use Jaguar atm.
Thanks
I don't think that my phone won't reach 60 C on stock, but I like watching YouTube, so I can see how fast it warms. (I have xposed module that shows me cpu temp even on stock). And as much as I can say my phone warms faster on custom roms than on stock. No matter what governor I use.
Also all animations (like status bar showing) are kind of laggy on custom roms. I don't know it it got better in past 2 months, but last time I used custom rom my phone reached 50C even only with chrome.
Interesting thing is that this all (including animations) is not present on 3.10 kernel, but there are no usable roms at the moment with 3.10 kernel, so I have to use stock.
SuperLamic said:
I don't think that my phone won't reach 60 C on stock, but I like watching YouTube, so I can see how fast it warms. (I have xposed module that shows me cpu temp even on stock). And as much as I can say my phone warms faster on custom roms than on stock. No matter what governor I use.
Also all animations (like status bar showing) are kind of laggy on custom roms. I don't know it it got better in past 2 months, but last time I used custom rom my phone reached 50C even only with chrome.
Interesting thing is that this all (including animations) is not present on 3.10 kernel, but there are no usable roms at the moment with 3.10 kernel, so I have to use stock.
Click to expand...
Click to collapse
So, what's the temperature your xposed module shows on stock under stress?
optimumpro said:
So, what's the temperature your xposed module shows on stock under stress?
Click to expand...
Click to collapse
Usually after 20-30 minutes of YouTube it's around 53-54°C
SuperLamic said:
Usually after 20-30 minutes of YouTube it's around 53-54°C
Click to expand...
Click to collapse
Which browser or is it a youtube app? I have similar temps on Firefox and about 44-48 when using Chromium (not chrome).
ScatteredHell said:
lol, that dude is Me, and I will try this, in the stock rom I can see an process running as overheat manager or something, I think it might have to do something with it. I'm sure that my device got heated very much, I didn't meant to offense but you seems to got it wrong. btw I will try this. I use Jaguar atm.
Thanks
Click to expand...
Click to collapse
Overheat manager: whatever it is, all it does is throttling and thermanager does the same on custom roms. So, the trick is to throttle enough without you noticing any lags...
optimumpro said:
Which browser or is it a youtube app? I have similar temps on Firefox and about 44-48 when using Chromium (not chrome).
Click to expand...
Click to collapse
It's a YouTube app. Really? It's weird, maybe I'll try, but I can see the difference on battery time when I come home from school - on stock I have ~70% and on custom roms I have ~50. Anyway I'll try and report after few days.
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
SuperLamic said:
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
Click to expand...
Click to collapse
OK. Nice to hear that about battery life and overheating. With regard to lagging: it is not cpu, but rather animations. Either disable them completely in developer options or in DU you can go to tweaks and pick and choose whatever animation you want. I just disable all animations and have absolutely no lag.
SuperLamic said:
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
Click to expand...
Click to collapse
Oddly enough, I find custom ROMs hae smoother animations than stock, in my phone. But I don't have good battery life when compared to stock..
Dear All,
I´ve managed to build a CM 12.1 with nfs support. Why 12.1? Well, for my D855, that was the only branch I could get working when building a kernel in Ubuntu, using the downloadable snapshot at CM´s site. The nighty´s would give me errors of different kinds during the building process, so the files on the phone needed when building are probably not the exact required version that match with the repo you can download in terminal mode.
Anyway, my experience with marshmellow is that the phone gets so hot that it turns itself off - another good reason to stay with 12.1.
My phone however still gets hot, which happens when using it with my VR headset to watch UHD clips. After 5 mins of watching, it dims down a bit. Then a few mins later a bit more, and so on until it looks like I´m staring at the screen through old cheap shades.
I´ve already disabled automatic brightness control, tried apps which claim to keep the brightness at the desired strength (Lux, the app is called), an app that´s ment to keep the screen always on (Always Awake), an app claiming to patch this exact bug, flashed a hack that´ll throttle only above 70 C. None of this helped. What I do know is that in the secret menu of stock firmware, there´s an option called Thermal Daemon Mitigation OFF, but I can´t access the secret menu through CM - only CM´s secret menu, that doesn´t have this option. Enabling this is said to cope with the problem.
There´s also a file named thermanager.xml in system/etc, which looks like something which can be modified to meet my requirements, but I´m not sure.
Finally, my least prefered option is to install a thermal pad on the SoC, but although I´m experienced with hardware, it´s on desktop level - not with such tiny things as a mobile.
So please, could someone help out here? Is there a way to rebuild the kernel with the stock secret menu or amendments to the throttling? Is there a way for me to get into the stock secret menu in CM?
Other ideas?
PS: I´m posting here because if there´s a way to get Thermal Daemon Mitigation OFF option related parameters set when building kernel in menuconfig, then it´s related to this sub forum.
PPS: Edited thermanager so all brightness values are 255, this seems to fix the problem!
This morning my Pixel C felt slow and sluggish.
Rebooted and removed recently installed apps but no difference.
Installed a CPU monitoring app and see that the CPU stays at 204Mhz even under load.
Any ideas before I try a full wipe?
Full reset seems to have fixed though notice cpu maxes at 1326
This right?
I'm not sure most CPU monitors know what to do with the X1, I know CPU-Z doesn't recognize it beyond a general "Nvidia Tegra" chip. What app are you using?
I switched from AOSP for acbit but yesterday had the same issue. Tablet felt slow and sluggish.
CPU monitor app showed CPU not scaling.
Went back to stock Oreo and still "feels" slow.
Geekbench4 says single core 926 and multi 2561
This is wrong?
My Pixel C performance is strange still the OREO update. I know this going to sound weird but when in splitscreen, the app on the left in landscape or on the top in portrait is lagging a lot. Scrolling, page swiping, etc.. takes a distinct longer time than expected. The app in the other half of the screen is acting normally.
Could this be related to the same issue?
With the pixel C now discontinued, Google is unlikely to fix a bug, especially if nobody reports it.. Bit of a worry, what to do?
I'm facing this issue as well. Already wiped cache and did factory reset, with no results.
It's now a very fancy digital picture frame.
There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
Vartom said:
There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
Click to expand...
Click to collapse
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L
laurentbon said:
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L
Click to expand...
Click to collapse
At the moment I'm using the kernel I've modified, and I have no problem with scrolling on the left side of the screen in split screen mode.
you can try it.
Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.
MrPhilo said:
Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.
Click to expand...
Click to collapse
For what? if the frequency control and so works normally
Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156
AlfreGarcia98 said:
Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156
Click to expand...
Click to collapse
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you
liam_davenport said:
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you
Click to expand...
Click to collapse
I dont know why, but the blue buttons are unclickable for me, so I cant create the issue.
Bringing back from dead.
So if you use Kernel Auditor to turn off some of the cores when this is occurring, the clock speed goes up for the primary core. It's as if they set a total limit, then divide by total core count. When battery charge is above 67%, you get the full max speed. No reboot or anything, just charge it up and you unlock the speed again. I suspect the Oreo kernels have bad throttling algorithm for this CPU.
My Pixel C was lagging quite bad when the battery fell below 67% using stock 8.1 (locked bootloader, everything untouched). I tried reflashing the factory images, but the problem stuck around. I rooted (magisk 18.1) and installed Kernel Adiutor. The problem was obvious, the CPU would heavily throttle (under 67% battery) depending on the amount of core active (with 4 cores, they would all run at ~200 mhz, with 2 cores, about 700 mhz and with 1 core about 1100 mhz). It wasn't so terribly laggy with 1 core running at 1100 mhz, but it was still pretty slow.
To try and troubleshoot the problem I then installed LineageOS 15.1 and followmsi's kernel (https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591). To my surprise the problem remained, despite the custom ROM and custom kernel. I think there is something wrong with the 8.1 oreo kernel and the Pixel C (see google forum post here: https://productforums.google.com/forum/#!msg/nexus/x7izNIUIHeI/VO4n9l_DCAAJ ). So I tried a second solution. This time I did the following:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsi's unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP: (same session, before booting into LineageOS): OpenGAPPS Arm64 Pico package: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (same session, before booting into LineageOS): Followmsi's Android 9 custom kernel: tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
And voila, back to full speed. In fact the tablet seems to run better than ever. After some testing I installed Magisk 18.1 (for root and to pass safetynet), and everything is running great. The CPU's now appear to be managed properly by the 9.0 kernel. I'd recommend anyone experiencing this problem to go ahead with what I outlined above. Alternatively, if you're not comfortable with custom roms, you can install the last Android 7.1 build (ryu-n2g48c-factory-0bc0ee15.zip - guide here: https://mmikowski.github.io/pixelc-revert-nougat/).
Hope this helps.
Purpose
I have been jumping from one UI to gsi's to back to one UI. I just want to know what are yall experiences with different roms and maybe stock one UI and what mods/workarounds or apps do you use to solve problems. Any custom kernel etc. I'll start with mine here
My Current Configuration:
(i edit this op when i switch a gsi or attempt further mods)
OS: YAAP GSI
Device: SM-A325F
Firmware version: A325FXXS4DWD4
Rooted with KernelSU.
Using OrangeFox from here.
Mods:
1. Custom kernel:
I made my own permissive custom kernel from A325FXXS3CWB3 Samsung's source from here.
It has a lot of changes which include removing entire security and knox debloat as it is not used in GSI.
It also has changed default ram compressor to lz4 instead of lzo-rle which should be faster.
I have tested this kernel on A325FXXU3DWB8, A325FXXU2CWA6, A325FXXU2CVK3.
It also boots on one UI.
It was possible all thanks to @KrutosVIP and his amazing work here.
You can download it from here.
Just flash it in twrp with no additional steps required. Make sure to backup boot in case it doesn't boot.
NOTE: i switched to my kernelsu kernel which is available here on a32 threads. it still offers the same features but it has kernelsu
2. Penguin Gcam and FreeDcam:
I currently use Penguin Gcam from here.
It includes needed features. The only thing broken is slow motion.
I use FreeDcam Inorder to get access to all the other cameras including Ultra wide, depth sensor and macro camera. It works great. The only problem as of my writing on this thread is that changing the ISO manually crashes the app.
Fortunately @uluruman has created the files and presets for this app which work amazingly. You can check it out from here.
You can check out FreeDcam on the F-Droid store from here or on github from here.
3. Workarounds in Phh settings
Samsung Features:
1. Enable extended brightness range (fixes brightness issues)
2. Double tap to wake (optional. But you can use it if you like)
3. Enable access to all cameras (Important for FreeDcam)
4. Enable extra sensors
Misc Features:
1. Use alternate way to detect headsets [fixes headphone jack] (Optional in roms built after or during march patch since they already include my overlay.)
2. Force FPS (set to your desired refresh rate) [i use 90] (NOTE: some gsi's have issue with this on android 13 firmware. There is no fix to this. Upgrade to march patch because project elixir seems to have this fixed on march spl. Or try switching to another gsi or downgrade firmware)
3. Force alternative backlight scale, Allow setting brightness to the lowest (needed to fix brightness bar)
4. Force Enable Camera2API HAL3 (To make FreeDcam work)
5. Force Disable AD2P offload (Fixes bluetooth audio for android versions 12 and below.)
6. On newer gsis Bluetooth is broken. To fix Enable Use systemwide bt hal.
Reboot after changing settings is recommended.
4. Magisk Modules
1. Audio Modification Library, Dolby Atmos from Moto G Pro (NOTE: Moto core is required for this.) [Just a dolby atmos port i like]
2. Fullscreen/Immersive Gestures (Q-T) (Removes keyboard space bar at bottom)
3. mindetach, Youtube Revanced Extended (Youtube revanced extended and to detach it from playstore which prevents updating.)
4. Safetynetfix MOD, Shamiko (Dealing with safetynet issues and bypassing root checks in applications)
5. LSPosed - Zygisk (Mostly to get broken face unlock back since broken face unlock on gsi's due to unknown issue with android 13 vendor.)
5. Xposed Modules
The only Xposed module i use is universalauth. Using this module i can get face unlock back on every gsi due to a unknown issue with android 13 firmware or vendor. It works reliably.
Note: It broke in android QPR1 so dev posted a custom xposed link here.
Its broken on QPR2 again. The current workaround is to disable auto dismiss lock screen in face unlock app.
If it happens on QPR updates just remember the workaround.
Since It is unable to download the apks for libraries. You need to download Moto face unlock from here.
Then import it.
To allow restricted settings go to app info of face unlock app. press three dots on top right and allow accessibility. Entered pin if prompted.
Enjoy face unlock.
Over all Experience:
I am happy with using it. Its super smooth. Bugs are of course expected in generic system images. But they are good enough to use daily. Gaming performance in some cases is amazing. Enabling allow higher fps in games in some roms like crdroid unlocks many settings. e.g. i could play cod at 90Fps at medium. The fps hovered around 60-90 fps. It was amazing. If you set the performance mode to performance in game space in roms that have it, It works amazingly. A game restart is required and it works. Actually bumps the fps by a lot. I still do switch from gsi's to gsi's since sometimes i get bored or the gsi lacks some important things. For now In my opinion using a GSI is far better than stock firmware for me. The gsi's i would recommend are crDroid, Elixir, Pixel Experience, EvolutionX, LineageOS (TD based)
you can find more GSI's from here.
Hoping to hear about what you use on your device and how your experience is.
For One UI users. i have a thread on floating tweaks which enable many features and small tweaks to help phone run a lil bit faster check it out from here
Another camera app which can use all the cameras is Open Camera. It is more convenient than FreeDCam, has almost all the same features and even more, for example HDR and panoramas, but unfortunately, like FreeDCam, cannot shoot video from extra cameras out of the box. I tried to edit the settings file manually but it didn't help as it did with FreeDCam, I suppose there should be something else fixed in the app itself, but still I'm going to try again editing the settings in the future.
uluruman said:
Another camera app which can use all the cameras is Open Camera. It is more convenient than FreeDCam, has almost all the same features and even more, for example HDR and panoramas, but unfortunately, like FreeDCam, cannot shoot video from extra cameras out of the box. I tried to edit the settings file manually but it didn't help as it did with FreeDCam, I suppose there should be something else fixed in the app itself, but still I'm going to try again editing the settings in the future.
Click to expand...
Click to collapse
I used it before. i actually got the cameras to work once. i dont know how. I ditched freedcam for it. But idk maybe after i switched roms or an update they broke again? i think if you look in info it says Only 2 cameras present. Our limited camera2api only shows 2 cameras. While freedcam forces to use the camera no matter what.
I may be wrong i saw something abt this somewhere.
Maybe downgrading to an older apk might help. But i sadly dont have enough time for that
I also recommend using No-frills CPU Control CLASSIC to lower the min CPU frequency to 500 MHz and set govenor to "shedutil" (if it's not already). Also set Android System battery usage to "Restricted" (Settings > Battery > Battery Usage > Android System). That should reduce the battery consumption in the doze mode.
Captain_cookie_200 said:
I used it before. i actually got the cameras to work once. i dont know how. I ditched freedcam for it. But idk maybe after i switched roms or an update they broke again? i think if you look in info it says Only 2 cameras present. Our limited camera2api only shows 2 cameras. While freedcam forces to use the camera no matter what.
I may be wrong i saw something abt this somewhere.
Maybe downgrading to an older apk might help. But i sadly dont have enough time for that
Click to expand...
Click to collapse
Open Camera can now shoot photos from all cameras, only shooting video does not work.
uluruman said:
I also recommend using No-frills CPU Control CLASSIC to lower the min CPU frequency to 500 MHz and set govenor to "shedutil" (if it's not already). Also set Android System battery usage to "Restricted" (Settings > Battery > Battery Usage > Android System). That should reduce the battery consumption in the doze mode.
Click to expand...
Click to collapse
i have noticed big cores are alr at schedutil. although some roms report efficiency cores using "null" like no governer at all. But kernel manager says they use schedutil. I mostly set my governer to ondemand.
uluruman said:
Open Camera can now shoot photos from all cameras, only shooting video does not work.
Click to expand...
Click to collapse
idk that small popup for switching cameras is gone. and it cant use the other cameras
So i just installed crdroid 9.2 looks like gms was going crazy in the bg eating my cpu. The fix i found is to run this command.
su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService
this seems to fix it and i dont see anything broken. I searched it and looks like this issue does happen for alot of users.
Captain_cookie_200 said:
So i just installed crdroid 9.2 looks like gms was going crazy in the bg eating my cpu. The fix i found is to run this command.
su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService
this seems to fix it and i dont see anything broken. I searched it and looks like this issue does happen for alot of users.
Click to expand...
Click to collapse
That's only if you're using a gapps version. I am using the vanilla version of LOS, so there are basically only two com.google.android.[something] packages in my system: com.google.android.apps.googlecamera.fishfood and com.google.android.networkstack.tethering.overlay
uluruman said:
That's only if you're using a gapps version. I am using the vanilla version of LOS, so there are basically only two com.google.android.[something] packages in my system: com.google.android.apps.googlecamera.fishfood and com.google.android.networkstack.tethering.overlay
Click to expand...
Click to collapse
yeah i m talking about people who use gapps. they are quite important in my day to day life otherwise i'd get rid of em
Just to update here. I tried magisk v26 and seems like it works fine. Although it had issues with my Dolby Atmos mods so i got rid of it and downgraded to v25.2 again. Otherwise all of my other modules were working fine and i didnt see any issues.
I have lineage os 20, but bro, don't have phhsetings haha
ApiYoshi said:
I have lineage os 20, but bro, don't have phhsetings haha
Click to expand...
Click to collapse
using light i see.
Captain_cookie_200 said:
using light i see.
Click to expand...
Click to collapse
Yep, it was a error hahaha, im now on another lineage gsi which have phh
Bro, you know if on Crdroid, the SD works normal? For me, as the SD is on exFAT, many gsi don't recognize it
ApiYoshi said:
Bro, you know if on Crdroid, the SD works normal? For me, as the SD is on exFAT, many gsi don't recognize it
Click to expand...
Click to collapse
i dont use a sd card. even tho I need one badly. it would save alot of time for me when switching gsi's
Captain_cookie_200 said:
i dont use a sd card. even tho I need one badly. it would save alot of time for me when switching gsi's
Click to expand...
Click to collapse
Oooh, well... Yes, a SD is so useful for that, in the SD I backup almost everything
ApiYoshi said:
Oooh, well... Yes, a SD is so useful for that, in the SD I backup almost everything
Click to expand...
Click to collapse
I will test the gsi, is stable?
ApiYoshi said:
I will test the gsi, is stable?
Click to expand...
Click to collapse
yes. march patch (qpr2) just came out today. give it a go