same with me its ok , but this applies in stand by position ( without any activity on the screen ) , try using franco kernel manager , check the cpu section , and check if there are similarities with my device?
This issue will be fixed in the next update.Hi, thanks for this rom, it seems to be doing well so far and I upgraded from the last version.
However I can't hear any sound on the phone app, neither the stock phone or google phone that I installed. I was able to get the sound on Google Voice by messing with volume/switching to speaker mid call but I can't figure it out for the phone. i tried the trick for the don't unlock unless screen is on and several reboots and it didn't seem to help. Any help would be really appreciated.
edit: if I connect to the phone once via bluetooth or wired headset during a call, it seems to fix it, not sure if for the whole reboot or just the next call. After reboot the issue is still there until I plug in headphones again.
Awesome thanks for this, sending you a tip now
hi mr @Chippa_aNew build is available!
- June 2023 security patches
- Fixed an issue where the speaker wasn’t working during a phone call
- LineageOS upstream updates and fixes
You can install the new build manually or using the built-in Updater app (requires at least TWRP 3.6.x or LineageOS Recovery).
LineageOS-19.1 will no longer receive any updates, that's why it marked as final.
Mmm...LineageOS-19.1 will no longer receive any updates, that's why it marked as final.
Anyway, this issue is old (present in 20 as well) and hard to reproduce and debug, so cannot be fixed for now.
Btw, I would really like to see specific ROM versions discussed in the relevant threads.
This way to boot TWRP doesn't work on these devices. Please read the installation process in the TWRP thread, there is also information on how to enter recovery mode.Hi!
For me some sensors doesn't work: the screen doesn't rotate (auto rotate is on).
Also I can't boot to twrp. I use command 'fastboot boot twrp.img' , phone in flash mode (blue light), then screen turns to black.
Please help.
adb shell dumpsys deviceidle whitelist +com.android.messaging
(source)Hello, I noticed a lot of users have this strange sound bug, but it never happened to me. I don't know the cause but maybe can be useful to know one of the first things I do is to disable AudioFX just because I don't like it. If someone wants to try, this is the command I used:Dear Chippa_a,
Thank you so much for giving new life to my phone.
Gcam is so much better than the stock app I was using in Lineage OS16. I'm having so much fun taking photos, that actually look decent now! That was the main reason why I upgraded, but of course, Android 13 does a lot of things so much better too, making the upgrade worth it.
The only bug that might seem annoying, which I was well expecting, was the sound randomly (seemingly) turning itself off, solved by a restart. I truly don't mind putting up with this bug for the other benefits this rom brings.
Thank you for your work and dedication to this project, Chippa. God bless.
adb shell pm disable-user --user 0 org.lineageos.audiofx
You are right, I felt the phone was hotter than the stock rom during the usage, so I checked the core status with 3C CPU Manager and I can confirm the frequency is set to maximum every time there is a user input on touchscreen. It seems touchscreen event overrides every setting. But I don't think this is the real problem because also the stock rom (that uses interactive governor instead of schedutil) behaves in similar way, not fixed to 1.4 GHz, but oscillating from 600MHz and 1.3 GHz on touchscreen events. Instead, I think CPU frequency is sticked to high values even when the screen is turned off, I'll investigate about it.same with me its ok , but this applies in stand by position ( without any activity on the screen ) , try using franco kernel manager , check the cpu section , and check if there are similarities with my device?
edit :
image ( example 1 ) stand by position without any activity on the touch screen Low cpu usage in " Minimum CPU frequency "
image ( example 2 ) there is activity on the touch screen max frequency cpu usage in " Minimum CPU frequency "
Use EX Kernel Manager.I am using on Los16.It's great.Can fix this.Sorry,Los20 is in testing for now.Good job @Chippa_a.THANKS!!!You are right, I felt the phone was hotter than the stock rom during the usage, so I checked the core status with 3C CPU Manager ............
Ex Kernel Manager doesn't work in this ROM, but after some tests I can confirm the governor works fine. The phone was overheating because there were some processes acting in strange way comparing them to the stock ROM. I used 3C Task Manager to find the processes consuming CPU and I solved uninstalling the apps I really don't need and enabling battery limitation for ING Bank. Maybe there are some other optimizations I can do but now the phone is colder than before.Use EX Kernel Manager.I am using on Los16.It's great.Can fix this.Sorry,Los20 is in testing for now.Good job @Chippa_a.THANKS!!!![]()
Yes , it's working fine.I am using it right now, v 2.96.I agree, v 2.98 give me fc app and not working.But v 2.96 = OK.
This ROM overheats very much while the camera is active. I think this is why you noticed the battery draining during a video call. But later you said the battery kept discharging, so this could be related to some process running. If you enabled developer feature, you can list running processes using this command: adb shell top. If you don't want to use a PC, you can install a task manager (I like 3C Task Manager).Has anyone experienced extreme battery drainage issues? This was on a fresh install of the latest rom with MindtheGapps and magisk. I noticed the battery draining while charging while on a video call. Turning brightness down to the lowest setting didnt do anything, neither did terminating the call and then turning the screen off. The phone eventually died.
I've wiped cache in recovery and am hoping this won't happen again.
I was using the same rom before with BitGapps, but I found there were a couple of issues that made me change: one was that upon restarting, it took a long time for apps to initalise, and the phone would lag for a good few minutes. This rom with Mindthegapps on the other hand is as smooth as butter! It's awesome, except for this battery drainage thing that just happened.
EDIt: The extreme drainage hasn't occured again, but I found google maps was draining the battery faster than it could charge. I'll keep monitoring.
killall [email protected]
I took the time to try a bunch of gcam's. I tried at least one variant of the gcam's listed on this page (link below), that specifies that it is made for multiple phones (just CTRL + F "multiple" on the following link):It turns out this was occurring because of the charger in the car. Nothing to do with the operating system. Loving this Rom with Mindthegapps so far. I don't understand how a gapps variant can affect how the phone operates so much.
EDIT: Just tried out this version of gcam and it works well:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This issue will be fixed in the next update.Hi, thanks for this rom, it seems to be doing well so far and I upgraded from the last version.
However I can't hear any sound on the phone app, neither the stock phone or google phone that I installed. I was able to get the sound on Google Voice by messing with volume/switching to speaker mid call but I can't figure it out for the phone. i tried the trick for the don't unlock unless screen is on and several reboots and it didn't seem to help. Any help would be really appreciated.
edit: if I connect to the phone once via bluetooth or wired headset during a call, it seems to fix it, not sure if for the whole reboot or just the next call. After reboot the issue is still there until I plug in headphones again.