Okitavera's Kernel for Mi 9 SE - v8.4

Status
Not open for further replies.

shisaya24

Senior Member
Mar 10, 2013
183
41
28
1 day and 1 hour are 25 hours in total!
Yeah that's the total time that the phone runs for at the time at which the screenshot was taken BUT the screen on time is only 2 hours something.

The problem with the phone according to different forums is the standby consumption and that seems pretty high even with this kernel. Must be ROM related I guess... I hope for custom ROMS
 
  • Like
Reactions: sHAKaJaada

denzel09

Senior Member
Jun 28, 2009
4,138
867
243
Teheran
Yeah that's the total time that the phone runs for at the time at which the screenshot was taken BUT the screen on time is only 2 hours something.
Yes, but if he had done half of the total hours then he could have done twice as many screen hours, it's all relative
For the battery we have i think we can not ask more.

The problem with the phone according to different forums is the standby consumption and that seems pretty high even with this kernel. Must be ROM related I guess... I hope for custom ROMS
The problem is caused by modem/baseband, and i think never will change. It's the same on EEA version, same with global, same with chinese version, same with .eu etc..
 
Last edited:

denzel09

Senior Member
Jun 28, 2009
4,138
867
243
Teheran
Yeah that's the total time that the phone runs for at the time at which the screenshot was taken BUT the screen on time is only 2 hours something.

The problem with the phone according to different forums is the standby consumption and that seems pretty high even with this kernel. Must be ROM related I guess... I hope for custom ROMS
Btw i will try this kernel, but i will wait the next version but for standby consumption i think never will change, problem is not in the kernel for me ;)
 

shisaya24

Senior Member
Mar 10, 2013
183
41
28
Yes, but if he had done half of the total hours then he could have done twice as many screen hours, it's all relative
For the battery we have i think we can not ask more.



The problem is caused by modem/baseband, and i think never will change. It's the same on EEA version, same with global, same with chinese version, same with .eu etc..

Btw i will try this kernel, but i will wait the next version but for standby consumption i think never will change, problem is not in the kernel for me ;)
So you two would say that even with better software (kernel, Rom...) the standby consumption will not get better? With other phones this was possible, for example Redmi note 5...
 

denzel09

Senior Member
Jun 28, 2009
4,138
867
243
Teheran
So you two would say that even with better software (kernel, Rom...) the standby consumption will not get better? With other phones this was possible, for example Redmi note 5...
I think that the standby consumption is caused by baseband/modem, previously i had the stock xiaomi EEA then i have flashed last .eu beta with i think a updated baseband. Nothing is changed, seems all like before about stand by consumption. Others with stock global have the same "problem" and so on... I can't be sure that with new kernel, rom, etc., something will change in good but it's what i think now. Will see... :confused: :(
 

okitavera

Senior Member
Jan 6, 2016
436
808
0
Malang
okitavera.me
Hello everyone!

Here's the update notes for v1.5

Changelogs

- Merge Latest CAF tag LA.UM.7.8.r4-01000-SDM710.0
- Enable iptables TTL modification target
- Add more input boost patchsets for snappier app launch
- Memory optimization with lz4 zram and sigkill reaper
- Add accessible vibration adjustment and kcal color control
 
Last edited:

pengus77

Recognized Developer
Mar 10, 2011
2,140
22,971
0
Penguins' Republic of Antarctica
Hello everyone!

Here's the update notes for v1.5

Changelogs

- Merge Latest CAF tag LA.UM.7.8.r4-01000-SDM710.0
- Enable iptables TTL modification target
- Add more input boost patchsets for snappier app launch
- Memory optimization with lz4 zram and sigkill reaper
- Add accessible vibration adjustment and kcal color control
For the details you can check the commit history here : .../commits/v1.5

Download

Go to : Releases Page
Or mirror : Google Drive
Hi there,
is it just me or the proximity sensor doesn't work? During a call the PS doesn't seem to have any effect (screen doesn't shut when answering) and in CIT the PS doesn't even return values.
Have to add that I don't have fingerprints saved and that I'm using the latest xiaomi.eu if that could help.
 

denzel09

Senior Member
Jun 28, 2009
4,138
867
243
Teheran
@yuneharuka

I think there are 2 bugs: proximity sensor doesn't work while calling and screen brightness level is always too high!
Try to go back to stock for now...

Also with okita kernel i have in cpuz 421 dpi instead with stock kernel the right value of 423 dpi, really strange :(
 
Last edited:

ChocoHR

Senior Member
Apr 26, 2019
91
19
0
Thanks for sharing - 2h SOT and 50% battery lost still seems very bad for consumption. I'm definitely not blaming the kernel - but why is the battery of this phone so bad??

I guess I'll have to see what I can squeeze out of the device myself and if it's not good enough I'll have to sell it again...

Here is an update of it.
I forgot to mention that the ambient light is on from 7am to 1am, so that can drain some extra battery too.
Maybe for you is not enough but with this kernel I got 2 days and 4.35hrs SOT with a single charge (still having 9% so it can be a lil bit more)
I think this is pretty much decent !

I didnt turn on the battery saver tho.
Hope this would help:good:



 
  • Like
Reactions: Humpfrey

decayed.cell

Senior Member
Jan 16, 2010
261
30
0
@yuneharuka

I think there are 2 bugs: proximity sensor doesn't work while calling and screen brightness level is always too high!
Try to go back to stock for now...

Also with okita kernel i have in cpuz 421 dpi instead with stock kernel the right value of 423 dpi, really strange :(
If you turn off DC Dimming, this is no longer a problem. WIth DC Dimming on, the minimum brightness gets stuck, it can't go lower than about 30 or 40% of the way down
 
Last edited:
  • Like
Reactions: denzel09

okitavera

Senior Member
Jan 6, 2016
436
808
0
Malang
okitavera.me
Hi there,
is it just me or the proximity sensor doesn't work? During a call the PS doesn't seem to have any effect (screen doesn't shut when answering) and in CIT the PS doesn't even return values.
Have to add that I don't have fingerprints saved and that I'm using the latest xiaomi.eu if that could help.
Oh right , the proximity isn't working.
I'll look into it, thanks!

Sent from my Mi 9 SE using Tapatalk
 

okitavera

Senior Member
Jan 6, 2016
436
808
0
Malang
okitavera.me
@yuneharuka

I think there are 2 bugs: proximity sensor doesn't work while calling and screen brightness level is always too high!
Try to go back to stock for now...

Also with okita kernel i have in cpuz 421 dpi instead with stock kernel the right value of 423 dpi, really strange :(
As far as I know, DPI is adjusted by wm command or SystemProperties either via the .prop files or ramdisk.

But my kernel is not using ANY modifications to the build.prop or ramdisk files.

Sent from my Mi 9 SE using Tapatalk
 
  • Like
Reactions: denzel09

okitavera

Senior Member
Jan 6, 2016
436
808
0
Malang
okitavera.me
Anyways, about the proximity sensor issues,
it may take times because I still have no idea why it doesn't works, apart from the fact that I'm using the stock xiaomi drivers for this sensorless proximity.



Sent from my Mi 9 SE using Tapatalk
 
Last edited:
  • Like
Reactions: denzel09
Status
Not open for further replies.