[KERNEL] Moxie N7 / M12

[bedalus]

I think it's a kernel feature, maybe it's different in moxie because of upstream patches and workload stuff?

Right now, I'm on ElementalX and it looks like this

Ah, that's something else. It's not a standard kernel feature, it's something flar2 came up with:

https://github.com/flar2/android_ke...mmit/ba0040ae167bce32408e49ee40a12fa4e670e367

https://github.com/flar2/android_ke...mmit/a2b70865948a7c1bc5e1a2a69797aa865c96d45e

 

[crzykiller]

Well seems like I was wrong regarding the battery inside the OP3T. It's the same size but the chemistry has been slightly changed and it is actually a 4.4V battery instead of 4.35V which would bring around a 10% increase in battery capacity. Now I've never seen a 4.4V lithium battery in my life before and I seriously hope they've completely redesigned the battery itself so that charging it to 4.4V won't damage it.

 

[core_x]

Ah, that's something else. It's not a standard kernel feature, it's something flar2 came up with:

https://github.com/flar2/android_ke...mmit/ba0040ae167bce32408e49ee40a12fa4e670e367

https://github.com/flar2/android_ke...mmit/a2b70865948a7c1bc5e1a2a69797aa865c96d45e

Is touch boost active in the stock kernel and flar2 only made it possible to disable?

 

[bedalus]

Well seems like I was wrong regarding the battery inside the OP3T. It's the same size but the chemistry has been slightly changed and it is actually a 4.4V battery instead of 4.35V which would bring around a 10% increase in battery capacity. Now I've never seen a 4.4V lithium battery in my life before and I seriously hope they've completely redesigned the battery itself so that charging it to 4.4V won't damage it.

Thanks for following up on this. So it will last longer but it's not physically bigger. They are charging it to a higher voltage, but this isn't something we can apply to our own battery because the chemistry is not the same.

 

[bedalus]

Is touch boost active in the stock kernel and flar2 only made it possible to disable?

That's right

 

[rafciowis1999]

That's right

No, You can disable it, set ms of input to 0 and its disabled.

 

[Antsu]

It's pretty strange. I m following this kernel since beginning. Never tried to play with bluetooth . Just tried playing a song via my bluetooth speaker - Xiaomi Cannon. It couldn't play the file. After connecting to the speaker phone becomes very laggy. I have had few crashes with default music player. After pressing play buttons phone seems hanged for a few seconds. Flashed V3, and got same result. I'm on stock 3.2.7 rooted, without xposed and any other mod. Anyone else having this issue?

Hi, did you find help for your problem? I noticed the same when using viper4android with guitardedhero zip, the phone is encrypted and selinux enforcing...
The problem went away by flashing magisk v9 and viper4android as a module, to clean rom with no audio mods.

 

[viper001]

Check First post


That's right

Hello again. Another suggestion?. Is it possible to push a battery capacity value every time the charge parameters are changed?

Ex. If you set 5 which is around 90% capacity, set 2800mah as max cap to the battery life indicator instead of 3000mah.

Sent from my ONEPLUS A3003 using XDA-Developers mobile app

 

[bedalus]

Hello again. Another suggestion?. Is it possible to push a battery capacity value every time the charge parameters are changed?

Ex. If you set 5 which is around 90% capacity, set 2800mah as max cap to the battery life indicator instead of 3000mah.

Sent from my ONEPLUS A3003 using XDA-Developers mobile app

I already considered this, but it would only be a cosmetic fix that disguises what is truly happening with the battery.

 

[abhibnl]

Is anybody else experiencing weird battery drains on the latest build? Charged my phone to 100(technically 90 as per blx mechanism), used it for like 30 minutes, only YouTube nothing else. Both SIM turned on and using 4g. And within 30 minutes, it dropped to 75.

 

[fcisco13]

Is anybody else experiencing weird battery drains on the latest build? Charged my phone to 100(technically 90 as per blx mechanism), used it for like 30 minutes, only YouTube nothing else. Both SIM turned on and using 4g. And within 30 minutes, it dropped to 75.

Need to read instructions, you need to change values 0-10 to get different charging percentages (capacities) just flashing and charging to 100 does nothinng

Sent from my ONEPLUS A3000 using Tapatalk

 

[viper001]

Is anybody else experiencing weird battery drains on the latest build? Charged my phone to 100(technically 90 as per blx mechanism), used it for like 30 minutes, only YouTube nothing else. Both SIM turned on and using 4g. And within 30 minutes, it dropped to 75.

That what it's supposed to happen. Since the actual charge is lower.

ie. If 100%=3000mah=3.35V then charging it to 90%=2700mah=3.3V approximately.

Btw, Incase anyone is wondering. Lipo batteries are "drained" @3V and should not go lower than 2.7, unless you want a bonfire.

Sent from my ONEPLUS A3003 using XDA-Developers mobile app

 

[abhibnl]

Need to read instructions, you need to change values 0-10 to get different charging percentages (capacities) just flashing and charging to 100 does nothinng

If u can go thtough my previous posts here in the thread, I have already set it to 5 to limit charging to 90%. But the thing is, dropping 100/90 directly to 75 within 30 minutes just watching YouTube video is totally weird and unusual.

 

[viper001]

PS. Don't use this mod on a new phone. There are chemicals which help in keeping the batteries "fresh" when new. You need to cycle charge and use it from full to empty for a few times to get rid of these chemicals.

Sent from my ONEPLUS A3003 using XDA-Developers mobile app

 

[fcisco13]

Keep coming back to this! Great job!!

Sent from my ONEPLUS A3000 using Tapatalk

 

[bedalus]

Keep coming back to this! Great job!!

Sent from my ONEPLUS A3000 using Tapatalk

Cheers buddy I'm really happy with it to.

I'm just doing some work to bring it up to 3.2.8. Franco's always produced high quality work, so I'll have a trawl through his commits to see if there's any goodies.

 

[bedalus]

Here we go: seven is a magic number

- updated to oneplus source for 3.2.8
- trawled through franco's git and came up with some cypher updates
- linux 3.18.45
- patch kernel exploit 'CVE-2016-8655 Linux af_packet.c race condition (local root)', thanks to @Haggster66 (see this post and here's the patch if other devs want to use it)

 

[Shuvo_bd]

Hi, did you find help for your problem? I noticed the same when using viper4android with guitardedhero zip, the phone is encrypted and selinux enforcing...
The problem went away by flashing magisk v9 and viper4android as a module, to clean rom with no audio mods.

Nope. Could not find any workaround. Flashed Stock kernel and tried other Kernel too. Bluetooth connection became laggy and refuse to play any songs. I clean flashed, the rom and right now i m on Franco's R3. No issues here anymore. Btw, i was not using any mod then. I wonder, what might have cause the issue.

 

[Haggster66]

Hi, probably you already know, but just a quick heads-up:

there's a 7day exploit in the kernel:
https://git.kernel.org/cgit/linux/k.../?id=84ac7260236a49c79eede91617700174c2c19b0c (apparently not in the stable-queue yet)
background: http://seclists.org/oss-sec/2016/q4/607 (can be exploited on Android)

 

[bedalus]

Hi, probably you already know, but just a quick heads-up:

there's a 7day exploit in the kernel:
https://git.kernel.org/cgit/linux/k.../?id=84ac7260236a49c79eede91617700174c2c19b0c (apparently not in the stable-queue yet)
background: http://seclists.org/oss-sec/2016/q4/607 (can be exploited on Android)

No, I wasn't aware, thanks for the heads up. I've patched the kernel and rebuilt v7:

http://forum.xda-developers.com/showpost.php?p=69901500&postcount=317

I've also patched up to 3.18.45. This is a minor update, but users of v7 might want to re-download if they want to be sure of avoiding the exploit.