Don't you get incredible battery drain on the KKM1 during phone calls? This is what simply kills the phone for me. I could get used to all the other minuses, but to lose 25-30% over one hour on the phone is terrible.After a few weeks trying to revive both KKM1 and 2 without any advance and, given that there isn't anything equivalent to this form factor, I finally decided to get another KKM1.
So far so good. Flashed CAOS 11 v308_gapps on top of latest stock and everything is working fine, including BT audio.
Thanks. I have a Sony XZ1c with about 1900mah battery left after years of use and an XZ2c with around 2000mah (to the extent that months of AccuBattery use can give an accurate estimate). One hour on the phone eats up about a third as much. I realize these were old flagships etc., but I find the difference huge. After 3-4 longer (but not very long) calls I basically have to recharge the KKM1.It's only a 2000maH battery, I wouldn't expect much more from any other device, and it depends heavily on how far away you are from a mast.
Both of them stopped booting overnight on their own. First was a KKM1 which I had for about a year and never flashed out of stock ROMs. After trying to factory reset it and reflashing with SP flash tools it even stopped responding to USB. It still shows the boot screens and sometimes can access recovery, but it looks like the partition table is damaged.How did you kill them? I've killed one KKM2, immediate bootloop and ignores all buttons.
I'm compiling lineage 17.1 without su, primarily for the KKM2 which can't edit /system, see the GSI thread for a binary. It's my daily driver and working great.
Don't you get incredible battery drain on the KKM1 during phone calls? This is what simply kills the phone for me. I could get used to all the other minuses, but to lose 25-30% over one hour on the phone is terrible.
That too. But I could live with a hot terminal consuming less battery.... but I do find annoying how hot the terminal gets after a 10-15 minute conversation.
I'll test this myself in a moment. Curious, how did you modify it?The lk.img attached to TWRP earlier in the thread didn't work for me with the A061C_V07_20201113 ROM for the KingKong Mini 2. I modified the lk.img in that ROM, at first to get rid of Orange State notification but got it to pass SafetyNet as well after also selecting the SafetyNet feature in Phh settings (on CAOS 11 308 but it should be universal).
Edit: Also, something I didn't see mentioned anywhere is that you have to allow unlocking in developer options before you can unlock the bootloader. I struggled with a "unlock failed" error for way too long..
Thanks. I have heard it's not a problem with the kkm2, just kkm1 it seems (it was in fact reported on this thread in its early days).I've just had a 22 min conversation, phone up to ear. KKM2. Lineage 17.1 (my rom).
Battery loss - 3%. Screen a little warm but probably a lot from my ear. Back top section (motherboard) luke warm.
I haven't a problem with this performance.
I looked up the Orange State message part, zeroed that (and the Red State message) out and underneath that is a flag (forgot what it's called) that gets set to the different states, I changed that to always report green.I'll test this myself in a moment. Curious, how did you modify it?
sed -i ':a;N;$!ba;s%<route type="mix" sink="voice tx"\n[ ]*sources="Voice Call In"/>\n[ ]*%%g'
sed -i ':a;N;$!ba;s%<mixPort name="voice tx" role="sink" maxOpenCount="1" maxActiveCount="1">\n[ ]*<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"\n[ ]*samplingRates="8000,16000,32000,44100,48000"\n[ ]*channelMasks="AUDIO_CHANNEL_IN_MONO,AUDIO_CHANNEL_IN_STEREO,AUDIO_CHANNEL_IN_VOICE_UPLINK,AUDIO_CHANNEL_IN_VOICE_DNLINK"/>\n[ ]*</mixPort>\n[ ]*%%g'
I looked up the Orange State message part, zeroed that (and the Red State message) out and underneath that is a flag (forgot what it's called) that gets set to the different states, I changed that to always report green.
Also, this seems to fix the bluetooth microphone echo for me. I made a crude little Magisk module to do it for me, I'll see if I can get a proper regex together..
Edit: the flag is called androidboot.verifiedbootstate and it's probably possible to modify it without lk.img..
Edit2: with regards to the bluetooth echo, the following regex's work for me:
If someone smarter than me can make a Magisk module out of this.. I´ve got no clue where to start, I think post-fs-data.sh but I don't have time for it right now.Bash:sed -i ':a;N;$!ba;s%<route type="mix" sink="voice tx"\n[ ]*sources="Voice Call In"/>\n[ ]*%%g' sed -i ':a;N;$!ba;s%<mixPort name="voice tx" role="sink" maxOpenCount="1" maxActiveCount="1">\n[ ]*<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"\n[ ]*samplingRates="8000,16000,32000,44100,48000"\n[ ]*channelMasks="AUDIO_CHANNEL_IN_MONO,AUDIO_CHANNEL_IN_STEREO,AUDIO_CHANNEL_IN_VOICE_UPLINK,AUDIO_CHANNEL_IN_VOICE_DNLINK"/>\n[ ]*</mixPort>\n[ ]*%%g'
The lk.img attached to TWRP earlier in the thread didn't work for me with the A061C_V07_20201113 ROM for the KingKong Mini 2. I modified the lk.img in that ROM, at first to get rid of Orange State notification but got it to pass SafetyNet as well after also selecting the SafetyNet feature in Phh settings (on CAOS 11 308 but it should be universal).
Edit: Also, something I didn't see mentioned anywhere is that you have to allow unlocking in developer options before you can unlock the bootloader. I struggled with a "unlock failed" error for way too long..
sudo fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system SYSTEM.img
fastboot flash boot magisk_patched_boot.img
fastboot flash recovery magisk_patched_recovery.img
fastboot reboot fastboot
adb reboot bootloader
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash system SYSTEM.img
fastboot flash system lineage-17.1-20210114-UNOFFICIAL-treble_a64_bvS.img
Sending sparse 'system' 1/10 (131068 KB) OKAY [ 4.898s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
fastboot flash system lineage-17.1-20210114-UNOFFICIAL-treble_a64_bvS.img
Resizing 'system' OKAY [ 0.004s]
Sending sparse 'system' 1/5 (262140 KB) OKAY [ 19.088s]
Writing 'system' OKAY [ 4.061s]
Sending sparse 'system' 2/5 (262140 KB) OKAY [ 19.596s]
Writing 'system' OKAY [ 4.036s]
Sending sparse 'system' 3/5 (262140 KB) OKAY [ 19.943s]
Writing 'system' OKAY [ 4.048s]
Sending sparse 'system' 4/5 (262140 KB) OKAY [ 20.290s]
Writing 'system' OKAY [ 3.721s]
Sending sparse 'system' 5/5 (177556 KB) OKAY [ 13.090s]
Writing 'system' OKAY [ 2.879s]
Finished. Total time: 110.773s
adb reboot bootloader
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash product product_gsi.img
fastboot flash system SYSTEM.img
adb reboot bootloader
fastboot flash lk lk_patched.img
I have moved the posts relating to the Pocket HERE. You can continue the conversation there. As and when development takes place for this device, you can make a request for a new forum as described by my colleague @Timmmmaaahh! above.Note to moderators : we have been polluting the Kingkong Mini / Kingkong Mini 2 thread with news, speculations and comments on the Cubot Pocket since April 23rd.
I think, both KKM / KKM2 and Pocket lovers would benefit from a split of the thread…
Cobus.