i dont know why but both little and big clusters just locking speed below 1100mhz,whatever i do, it never changes on pie rom,installed every rom,installed radon 6.3 modified[it change for sometime but reverts back randomly then locking in same speed]
is this android pie bug or kernel issues?
P.S: miui,nougat roms are normally working ,no issues with them,i dont like oreo roms ,so i dont use them
Do you try with kernel adiutor?
go to vendor/etc/thermal-engine.conf <-- delete this file or backup incase u want it back or u can just edit the value of device limit
Related
I don't whats the exact cause for this issue. But When i use the stock ROM or LeanA9_v3 or Mystique ROM, i get a lot of device restarts but when i use another ROM based on MiUi i.e. Inverse ROM i dont get the restarts but some other issues.
Is there any way out by which i can choose the best out of all these ROM and modify it depending upon my wish and use it.
Hello guys
I would like some help to make a kind of "Camera-survival-fix" for my GS3, while running the back to noot. I tried most of the roms available, but i keep ending with Back to n00t or QS i9300, but the last one is a mix of Note 2 + S3, and i would like to keep the "Stock-state" of the phone, i mean, maintaining it as a real i9300. back to n00t (as QS i9300) are stock, not heavily customize, they are faster than stock and runs the latest official android for the S3 series (4.4.4). There are a lot of apps that requires this API 19 KitKat as minimun OS, like Google Clock, and even, omg, Pokemon Go, so basically this is a heavy difference if we compare to Samsung's 4.3. Now, to the problem...
I've tried most of the roms, as i said, but back to n00t, my lovely one, destroys the camera after the flash, always, and i have to flash JustArchi's Camera Fix Everything to make it work again, otherwise it will forever give me a error "Camera error/black camera". I've looked into it and discovered there's something about the camera firmware which makes this disgrace happens. My CAM FW ver is ZHFJ02 and i noticed that almost all the other roms have a folder "/data/cfw/" where contains like All the camera firmwares, while back to n00t don't have this folder containing the SlimISP.bin files. I think this is the difference, which make my camera work on the customs, but not this one. I want to keep the ROM to survive cache cleaning and factory resets, without the need to use the Archi Camera Fix Everything thing... Basically, i would like to implement the fix in the ROM. I tried to edit the updater-script.bin on META-INF folder, however it doesn't seems to work, it flashes, but i'm afraid that if i overwrite the ROMs update-binary.bin it may not work at all, please help... any help is much appreaciated...
replace from stock or change rom,
i have problem with sms (proces stop working, when i nothing have installed too, its was random for me) and now change to latest cm13 - much better
How to get GOVERNOR CONTROL settings to stick with stock kernel?
I have set specific parameters (sampling_rate, up_treshold, hotplug_freq, etc) for each CPU core. But, it last only for couple minutes or until i lock my device. I don't know why but it's reverting back to default settings after i unlock it.
I know i can flash custom kernel, but i want to make it work with stock.
Any help 'bout this?
ROM used: Resurrection Remix 5.8.3
Not possible. You MUST have a custom kernel to change any aspects. Although you might think you are making changes until it reboots, it is a placebo. Stock kernels are set for life and cannot be changed.
Beamed in by telepathy.
Everytime when I leave my phone Idle just like for 10 minutes, when I return and tried to use it, the device seems to be turned off. Cannot be turned on unless I will force shutdown and reboot (Long press Power button and double vibrate feedback)
I've never encounter this issue since when using stock rom or SyberiaOS, HavocOS and LineageOS build 20190307. I am on latest Nightly build of LineageOS. I will try and contact one of the devs to try and check on about this.
LineageOS Build 20190310
eXtremeKernel v9.1 69HZ
I will try changing custom kernel. From eXtremeKernel to Sphinx and others. Then test them if one of them has no random system shutdown
The last time I used Lineage OS with a custom kernel it was pretty common to have major issues(black screen, shutdowns). There's a very high chance that it's a kernel issue causing the shutdowns. Either try a different kernel or revert back to the default kernel, Lineage OS works great with the stock kernel and if you want to keep the reliability then you'll have to stick with it.
TheGrade said:
The last time I used Lineage OS with a custom kernel it was pretty common to have major issues(black screen, shutdowns). There's a very high chance that it's a kernel issue causing the shutdowns. Either try a different kernel or revert back to the default kernel, Lineage OS works great with the stock kernel and if you want to keep the reliability then you'll have to stick with it.
Click to expand...
Click to collapse
Yepp.. Found an issue in eXtremeKernel. Will test and analyze it before sending it to the devs on both Kernel's devs and LOS16 I think.
But it works well with Sphinx Kernel, no random shutdowns and errors were found.
Hi everyone. this is my very first post. I'm an Owner of a Redmi 6a (Cactus) Running Lineage OS 17.1 Unofficial (20200727) and I'm having some issues with the from so. first, I would like to know which Custom ROM Its better for this model now in 2022. more stable and updated. and also. if I can change the custom ROM to another without problems, just wiping some things ( I have TWRP and Bootloader unlocked already), or I have to get back to MIUI again.
I'm seeking something with the highest android version available for this model without problems like slow charging. camera stops or issues with daily usage, I would like to get my phone a little more powerful again.
Any suggestions, and comments, are well received by me.
Thanks to everybody
welcome to the dark side
so at the beginning i just tested some of the available costom roms, each for a few days (like go shopping) to get to know the functions and to see if they are stable (stable enough - because you can't find all bugs in short time). i am now using LineageOs but this is a personal preference. maybe i should go "shopping" again to see how the other costom roms have evolved over the past two years. as long as i did this testing i flashed all the roms "dirty", this means as you said, just wiping/formatting in twrp and flash new rom but as soon as i left testing and decided to use a rom for a longer period of time i did a "clean" flash. this means flash stock rom again (be careful to don't lock your bootloader again, its preselected in miflash unlock tool), then boot system, enable adb debugging, flash twrp, flash costom rom. i would say from experience that if you do a dirty or even clean flash, lets say you do it 10 times in a row, you will not always get the same result. maybe sometimes in LineageOs (at some devices) the radio is missing, sometimes it's not. sometimes you have a bug with a camera, sometimes you don't. flashing clean should reduce the error rate. this in the first place and the different region versions make it hard to help someone who has a device specific - rom specific - one in a hundred times bug - they need some help with.