[K3 Note Original Android Development] daniel_hk:
1. Other than charger type, I don't think [MENTION=7583260]GSandeep[/MENTION] would change the charging currents. Those values are from Lenovo. Should they deliberately released the wrong data, it would have difference. There are a few factors affect the charging current. The most obvious one is temperature. If the temperature reach something like 37C, the current would drop to protect the battery. If we increase this limit, it might burn the battery like Note 7.

I don't know where you get those values. We can get the current value from sysfs but the value is not constant. Charging is not by a constant current but pulses. It also depends on the battery's temp., capacity and age.

I use the same kernel for stock and my existing ROMs now. If Lenovo had hidden some tricks in their proprietary apps or init, we simply can't do anything. My observation is more or less the same. It takes 2 hrs+ to fully charged from say ~10%.

2. For the voltage reported, it's not standard. MTK use different sysfs. Nexus devices us uV but MTK use mV so some apks might report wrongly. It's just the unit that apk chose.

Yes, it can be done. Just multiply the value by 1000 would do but why? It shouldn't be our job to suit an apks. They should take care the MTK devices in the first place. CPU-z would report 4000mV so it's correct. "Correct" it would make CPU-z wrong again.

Hope these might answer your questions. ;)

That AOSP was just a test build. I'm also impressed that it performs quite well. I might consider do it again when new Android version come.

1. Stock AOSP assigned long press home key to Assistance (search). It's in SystemUI I think and it's launcher independent. I think either its not defined or didn't find the target now. Other custom ROMs (eg. new Carbon which I'll release shortly) I tried would work.

2. That is how the MTK RIL blobs reported. Some SIM might have the correct name but others would use the carrier's code. I had tried a few ways but it's ROM dependent. I need to do it again differently every time. It seems not worth to waste such time.

3. HDR was an old issue. It's not really working even in stock ROM. It was slow and the output is fuzzy and useless. I used a different approach in my last LOS but that doesn't work on 7.1.2. I might take another look but it's not my favourite.

4. There are codec issues for that build. I know what's wrong and can be fixed.

5. I have disabled AOSP's recovery update. I don't know why you would stuck at boot again. Anyway, that's why I asked people to flash SuperSU. There are some security issues on things like FM, led, power off charging, etc. I just don't have time to explain to everyone.

I don't know why you bring this "old rumour" up again. Who told you that k3 note support voLTE? I can't find it anywhere in the official spec. sheet. May be someone wiser can but not me. I just don't have that kind of knowledge and skill. :eek:

It's very irresponsible for anyone to release info. that have nothing to backup. Someone like you might blindly believed. I'm now asking the Moderators to ask those guys to provide whatever proof they have.

I accepted to become a Carbon maintainer earlier. They are so kind offering me the chances for a few times. It seems doesn't hurt to discuss with other developers. I'm testing the latest build and will release shortly. I might release MONTHY later. That's the best I can do for the time being. Cheers! ;)