In my case, flash it with kernel flasher and not using any kernel manager. What manager are you using?Don't mean to have anyone seem like an ameture but are the guys with reboots using latest stable magisk 26.1 and also which flashing app/kernel manager? I had issues with the obvious wrong magisk version but when I fixed this I also had some random freezing when using Franco kernel manager. Both changed for a while now and never had another freeze etc on my Pixel6Pro
hey @Flyview, I didn´t miss the post but I somehow missed replying to your post as there´s currently a lot of "real life" stuff is going on for me and I didn´t want to give just a one word answer when I read it.
So the short answer is no, as this is not handled by the kernel for the largest part. It´s handled by the modem itself.
However there are still some parts impacting this. For example changing the TCP algo might have the slightest influence on this. However, the better the signal, the less impact this will have.
There are a few "interfaces" between kernel and modem, but since those are just interfaces not much can be done there. Those interfaces benefit however from general kernel improvements -> e.g. if scheduler is improved and tasks are handled smarter, tasks from those interfaces will also be handles smarter (hopefully).
I´m very hesitant to change those interfaces directly, for a simple reason. I can´t fully test changing anything there as this opens waay to many angles where issues could creep in. Additional to that the modem is not open source, so I can´t confirm or check how those interfaces interact with the modem. Any changes there might introduce problems with general reception, volte, vowifi, 5g that can be specific to only certain carriers or countries or happen completely randomly.
An easy example: Even tech giants like Google, Samsung, Asus etc can´t provide a working volte, vowifi, 5g configuration for every single carrier in all countries without having to take major hurdles.
One suggestion is to limit the pone to 4g, that might save some power. But generally mobile data will always be a lot more expensive in terms of energy consumption than using WiFi as you correctly pointed out.
The last tip might be to use the CleanSlate battery saver when transfering a lot of data. I don´t know if transfering files takes a lot of CPU power, but restricting it during those times might reduce power consumption.
Read the instructions on post 4 or whatever early post it is and follow them exactly word for word and you'll have no issues. I've done it every month for the past 6 months. Don't deviate from the instructions.Hello everyone, what files I need to flash to back to stock kernel? I mean can I just restore in fkm stock backup, or I need flash files in fastboot?
You may point out the key point - Magisk version.Don't mean to have anyone seem like an ameture but are the guys with reboots using latest stable magisk 26.1 and also which flashing app/kernel manager? I had issues with the obvious wrong magisk version but when I fixed this I also had some random freezing when using Franco kernel manager. Both changed for a while now and never had another freeze etc on my Pixel6Pro
Try a battery stats app of sorts to see what it is exactly mate. Havent had any isues with drain, if anything this has been total opposite and feeling grandPixel 6 here have no reboot issues running april update, but something is wrong with the battery since i updated, something is running in the background and drains the phone when in idle mode, phone was 41% and drained to 2% without i touch it in a couple of hours
So i had random reboots previous but now i am seeing some short of pattern here , seems like when ever i use camera and switches lens it crashes and reboots itself , im on latest test build which is 1.0.2_4 and i am attaching contents of sys/fs/pstoreTest Release 1.0.2_4
Hey everyone,
This is a public test release that might address the crashes some are experiencing. I didn´t face the crash myself a single time so far, so it´s impossible to confirm from my end.
I´d appreciate if as much users as possible could flash and run this. Especially those that suffered crashes before. In case you get a random reboot please zip up and share the contents of sys/fs/pstore once you phone booted up again just like so many did before, which is great for me to see!
Gsam stats says kernel (android os), strange as i never experienced this before, might give v.1.0.2 a try instead of 1.0.2_4Try a battery stats app of sorts to see what it is exactly mate. Havent had any isues with drain, if anything this has been total opposite and feeling grand
Thanks for the log. Is that a special USB c port? Connection set to charge only?@Freak07 Hope I will Help you by this report...
I have get random reboot but Its only happen when I use my phone in charge... ( USB-C computer )
Build kernel : Kirisakura_Raviantah_1.0.2
Android stock release : Oriole TQ2A.230405.003.E1
Log :
Flash the 1.0.3 one. The crash was reported on 4.4.2 as well, but there's a good chance you're not affected by this bug at all, just like myself.Hey Freak, I haven't run this kernel yet. I'm currently on TQ2A.230405.003.E1, should I use 4.4.2 or 1.0.3 that you just put out?
Thanks for getting back to me but I went ahead and flashed 1.0.3 a couple of hours ago and I must say it's running great! No issues at all. I'll be sure to send a log if something does happen.Thanks for the log. Is that a special USB c port? Connection set to charge only?
I'm still unable to reproduce the bug on my own end, that's why I ask.
Please try the test build (1.0.3_1) from the post above yours. That's the same issue I'm already aware of, so i already know 1.0.2 is affected.
Flash the 1.0.3 one. The crash was reported on 4.4.2 as well, but there's a good chance you're not affected by this bug at all, just like myself.
So it's best to run the last one I posted.![]()
Its classic hight speed USB-C - connection set to charge only.Thanks for the log. Is that a special USB c port? Connection set to charge only?
I'm still unable to reproduce the bug on my own end, that's why I ask.
Please try the test build (1.0.3_1) from the post above yours. That's the same issue I'm already aware of, so i already know 1.0.2 is affected.
Flash the 1.0.3 one. The crash was reported on 4.4.2 as well, but there's a good chance you're not affected by this bug at all, just like myself.
So it's best to run the last one I posted.![]()
The main problem is time I have available.The Pixel 7 series received the September update, whereas the Pixel 6 series did not. Considering that Google unified the main kernel tree for both the Pixel 6 and 7 series, I assumed it would be easier for you to provide longer support for the Pixel 6 series as well. Is this simply an oversight, or will we not receive an update ?
Thank you so much for your work anyway, I find myself more excited about your monthly kernel updates than the ROM updates from Google.
I was feeling brave, so jumped ahead anyway....
It´s always recommended to run the latest kernel release combined with latest firmware that´s compatible with the kernel. I can´t update and maintain support for older releases to run on older firmware bases from a time perspective alone.