yashsingh1/xdaforums huggingface dataset:
[K3 Note Original Android Development] daniel_hk:
It is quite easy to assume that people would know what we meant. I just don't know what you meant by flashing a modem. I assume you have a patch zip which contain the modem file. If flashing a file cause reboot. That means there is something wrong with the file or your TWRP, or else?

In any case, you need to provide that file and how you flash. However obvious you think, I just don't know what and how you flash. Are you flashing the image directly, or else? Just can't tell, right?

I don't think guessing would help anyone. I personally hate to guess so normally I would just let it go.

But, there is an obvious way for what you need so I give you a pass this time.

If you have the modem file, you can just replace it with a root browser (eg. ES).

In case, the modems are in /system/etc/firmware. We use the lwg image now. (I'm on the road, I can't remember the exact name.) Replace that file with the one in you stock ROM will do. But, I don't know if it would work.

Next time, if anyone requires help, help yourself by addressing everything clearly first.

Good luck! ;)
[K3 Note Original Android Development] imankerx:
yeah sorry, i thought the only obvious way to install modem is through TWRP by .zip file, anyway this is the modem .zip file i try to use drive . google .com/file/d/0B_pdO3PAMQvlbFZKQmV3UmxEMkE/view

as for TWRP, i installed it using this file through sp flash drive . google . com/open?id=0B_pdO3PAMQvlakFoNWU2M2FZSVE

P.S i still cannot post outside links
[K3 Note Original Android Development] Cpt.mactavish:
[MENTION=4948627]daniel_hk[/MENTION]. Sir,is it possible to provide a patch for hotspot bug.....I know the workaround ...but annoying...it would be helpful....if you provide a patch..whenever you are able to fix that bug.....so it can be used in other Roms.....
[K3 Note Original Android Development] gxthelord:
silly question: How to get ROOT on the latest Carbon 5.1

I tried flashing v2.67 and v2.68 and got stuck at bootlogo. :X

And whats the charging rate like for you guys. :)
[K3 Note Original Android Development] olgutza34:
try flashing Supersu 2.78 either 2.79SR3, just rooted mine couple of days ago. Do not panic if supersu doesn't show up in app drawer, it still works and pop up when requested by apps. Strange behaviour, but nothing else to worry about.
[K3 Note Original Android Development] Strmy:
Can you help me? Youtube video at 1080 is laggy , i dont know what to do, but supper annoying
[K3 Note Original Android Development] gxthelord:
Thanks it worked out well. :D Using 2.79 SR3. There's a root option in settings now. :cheers: Wonder how's battery life for you? It gets me about 2.30-3hours SOT/day for just basic whatsapp,FB,insta. :D Seems fine. Hope to see someone can share how to charge it faster. Current rating is about 5V1.15A up to 80% and above that stays about 5V0.8A.
[K3 Note Original Android Development] olgutza34:
glad you make it. Also my SOT is around 2.5-3 hours. With a standard HTC charger of 1 Ah it charges around 50% in two hours. With original charger, plugged at 110V (AC converter for some US stuff) goes faster, 2.5 hours from 10 to 100%.
[K3 Note Original Android Development] gxthelord:
That's about the same for me too. :D Hope there's someone can have an mod or tweak for it to charge faster. :D

On Vibe it was able to pull about 5v2A from the wall using the original Lenovo Charger. Ohh well no complains. I'm happy with the performance and all. Grateful to have daniel_hk on creating this rom. :)
[K3 Note Original Android Development] trixter127:
First of all thanks for your awesome work and continues support. You are the only reason my k3 note is still alive. I already installed the previous version of the Carbon rom on my device now can i install this new update without wiping the data? Or should i wipe and start new again? Thanks in advance
[K3 Note Original Android Development] daniel_hk:
I don't know how you know you get 2A in Vibeui. This would be my last answer to similar question. I just don't have time to repeat and repeat again, sorry... :(

This is normal. The charging current would decrease when its almost full. This is to protect the battery from overheat. I can give you the detail on the charging curve but I think only few might understand. I would try to simply it here.

When a battery is almost fully charged, the internal voltage would approaching 3.8V. At the same time, the internal resistance is increasing (V=I*R). We can't use the same current to charge it because it would just waste the energy to generate heat (Power=I*I*R). That would not only harmful to the battery but dangerous to the phone and the user. That's why the current need to drop and we need 2hr+ to fully charged. When the battery is aging, the internal resistance would grow gradually. That's why the charging rate would be slower. ;)

You probably don't need to do factory rest for upgrading to the same Android version of the same ROM. Usually, only switching ROM (eg. cm to carbon) and/or upgrade to different Android major version (eg. 6.x -> 7.x) requires a factory reset. However, wiping the d-cache and cache is a good habit after flashing. It would rebuilt the Dalvik/Art cache and remove unnecessary garbage from the previous versions. ;)
[K3 Note Original Android Development] trixter127:
This clears my doubts. Thanks a lot for quick response [emoji4]
[K3 Note Original Android Development] agdroubi:
Any news regarding official carbon? :D:D
[K3 Note Original Android Development] ziad shawki:
hi daniel hk i used your lineage os 14.1 for nearly month its amazing battery and performance and it was my daily driver but i have a proplem that is anouying me that when using share it apps or apps like that that use hotspot to transfer files it some times works and sometimes not so can u plz say that

its going to be fixed or not i just want to know

and thank you for your effort [MENTION=4948627]daniel_hk[/MENTION]
[K3 Note Original Android Development] trixter127:
He mentioned that hotspot wont work in his roms. So you need use shareit's 'send' option which connects to others hotspot and then ask them to send the files you need. Recieve option wont work as it requires others to connect to your hotspot which is not yet possible on this roms.
[K3 Note Original Android Development] gxthelord:
[MENTION=4948627]daniel_hk[/MENTION] thanks for the in depth explanation. I guess I'd understand half of it. :D I'm just grateful with what you have done for the community :cheers:
[K3 Note Original Android Development] daniel_hk:
TWRP-3.1.1-0

I need to find a way to make the platform changes easier to adopt.

I turned down almost all offers before. I personally adore Carbon and Slim. Official or not, it's more or less the same. It's just a name. Don't bother with it. ;)

You can't imagine how to fix anything if you don't know how it work. I haven't tried ShareIt but I'm quite sure it doesn't use hotspot. As a matter of fact, I see no similar apk would use hotspot. Most of them are using p2p which is not quite reliable. Sometimes, it would even failed in my Nexuses and required a reboot. That depends on the drivers and firmwares at both side.

Actually, I'm very annoyed by similar requests for a long time. I have clearly mentioned a few times. I usually won't/can't do anything for an apk issues. I simply don't have their source. There are millions of apks out there. No way I would try every apk you guys want.

If you want to ask, ask the author of the apk to provide the source first. Should I'm interested, I might take a look. ;)

OK, no more off-topic. :fingers-crossed:

This post is to share my version of TWRP-3.1.1-0. If it doesn't work as you wish, just ignore it. :)

I built it for my other devices earlier so I want to update mine too. With this, the error after flashing in block mode will be gone. :D

I didn't actually built it out. I have a prepared tree and directory for TWRP. I don't want to waste time debugging and patching again. I modified an existing device to make it. Anyway, I have tested for an hour and found no observable issue. Cheers! ;)

Summary of my build:

- latest TWRP-3.1.1-0 official source.

- use Lenovo's official device name "aio_otfp"

- disable the wiping of essential partitions (nvram, protect, etc.)

- enable backup and restore most (all?) of the partitions

- enable most of the available languages from TWRP. (Our recovery partition is almost full. Ja requires another font and there is no room. See if there is workaround later...)

Note:

Official TWRP use the device's serial no. as the BACKUP directory name. Some other TWRP might changed that. If you found that your old backups are gone. You might need to manually rename the directory back to your serial no. (at <storage>/TWRP/BACKUPS/<name>). You can get that no. by making a simple backup (say /boot).

Download link : AFH
[K3 Note Original Android Development] ziad shawki:
thank you daniel for fast replying and i tried your recovery i didnt see any proplems from it but can u plz release your carbon rom tree to see more roms for k3 and plz can u add ambient display its too cool and handy and thank you again for everything you [MENTION=4948627]daniel_hk[/MENTION] do:laugh:
[K3 Note Original Android Development] Cpt.mactavish:
first of all....thanks a lot for new twrp.....this one is great....working just great...

hotspot--plz.... don't take it otherwise..I think there's a little misconception ...I may be wrong...and I don't know much about p2p either...you know better... but I think shareit,superbeam,es filemanager's sharing option

all these work in this way....

1.receiver opens a hotspot(open/pass protected/QR code scanning by other phone)

2.sender opens up wifi..scans and finds that hotspot..gets connected

3.then shares file via... p2p...or like a file server...

so...to get these working we need hotspot working.....yep....hotspot does work....but...due to the bug(cant connect wifi at first try) apps get confused...doesn't scan.... or some issues arises....with hotspot workaround..it works sometimes... but...sometimes it is needed to open app again...actually it is annoying when these problems arise...when we need to share with other people....
[K3 Note Original Android Development] agdroubi:
Thank you for your hard work.

Please let new rom updates be only carbon (u like it :angel:), so that we can update from the current version easily. Shifting to different roms is a bit confusing and requires clean installation. :) [MENTION=4948627]daniel_hk[/MENTION]
[K3 Note Original Android Development] Costa001:
is engineering mode present in this rom????
[K3 Note Original Android Development] bansuk5:
Thanks
[K3 Note Original Android Development] Costa001:
Daniel

Your latest twrp 3.1.1 is not stable it is not able to format any partition like cache or system

it currupted these and brick device.
[K3 Note Original Android Development] trixter127:
If you can't wipe your cache just wipe the cache partition and remount it. Then you should be able to format the cache
[K3 Note Original Android Development] Strmy:
Can I update carbon with old twrp?

Also, which rom is the best? RR,LoS,Carbon?
[K3 Note Original Android Development] derickeys:
I don't understand why do we have to use share it just for the hotspot to work. I don't know but My only workaround is just open hotspot then go to hotspot settings then choose setup hotspot and don't change anything just press save and that's it. Hotspot will be detected.
[K3 Note Original Android Development] kemoumar1:
You're right ! Hotspot will ne detected but it do not share internet.

Envoyé de mon X80 Plus(H5C5) en utilisant Tapatalk
[K3 Note Original Android Development] derickeys:
Please do correct me guys if I'm wrong, but to my knowledge, hotspot is not tethered by default. Bluetooth and USB I think are the tethered ones. I use pda net for hotspot tethering.
[K3 Note Original Android Development] daniel_hk:
There are some major updates from Carbon so I built another one yesterday.

Tested for a day and I share it now. ;)

A much lighter carbon Browser is the default browser now.

The security patch is also update.

Cheers!
[K3 Note Original Android Development] agdroubi:
Thank you so much for the update, hotspot was fixed on other roms why it is still not solved in this one.

Is ambient display available now?
[K3 Note Original Android Development] bedoedeyne:
Can u create Resurrection Remix rom for K3 Note. I love that rom and I love your work. It's the best if you do it.
[K3 Note Original Android Development] tanish2k09:
Doesn't it already exist? By other devs
[K3 Note Original Android Development] bansuk5:
Permissive kernel please, audio mod not working properly on enforcing
[K3 Note Original Android Development] chris-mm:
Hello daniel_hk,

thank you very much for your professional work. It´s awesome!

I want report a small bug in your latest Carbon Rom (CARBON-CR-5.1-MOO-UNOFFICIAL-aio_otfp-20170602-1704.zip):

GPS is working in general, but GLONASS satelites are not detected.

I have checked with YGPS and with my favourite navigation app (Locus pro).

In your opening thread you´re stating that your HAL is fully supporting GPS, GLONASS and BEIDOU.

So maybe it´s just a little glitch in your latest update.

Is there hope for a GLONASS patch for Carbon?

Meanwhile i will test if GLONASS is working with your other or older roms.

I will report back my findings.

And again: Thank you very, very much for your excellent work :good:

This is only a small bug report to give you a usefull feedback for your hard work.

Best regards from germany,

Chris
[K3 Note Original Android Development] chris-mm:
Hello again,

I´ve now checked the GPS reception with your latest LinageOS and unfortunately it´s the same as with Carbon:

GLONASS satelites where not received (with stock rom ROW S433 GLONASS is definetively working).

I´m so sad because your roms are really excellent.

But I´m using my K3 Note mainly as a trekking navigation device, so GLONASS is a must have feature for me. :crying:

But the hope dies last. Maybe it´s possible to fix GLONASS in the future.

Meanwhile im going back to stock ROW S433.

But I´m patiently waiting :fingers-crossed:

And if you can fix it, I will pay you a delicious XXL bavarian beer!!! :silly:

Cheers,

Chris
[K3 Note Original Android Development] daniel_hk:
hotspot is not my priority. I might take another later. I rather spend time on o-preview or new things first.

I don't have plan to add/remove any feature from Carbon. Flash other ROM if its essential for you. ;)

No matter who build, there are only very minor differences. I have no interest repeating others work. It's just a waste of resource.

I don't know where you get the idea of "permissive kernel". And who told you it's not permissive now.

A kernel might or might not support SELinux.

If it does, SELinux can be enabled, disabled or set to permissive, enforcing etc.,

As a matter of fact, the majority of MTK stock ROMs and most of the custom ROMs (including my carbon) are permissive.

Some apks, especially those system performance apks, might have issues if it is not permissive.

You may easily check it in About.

The support I meant was the HAL which can process the messages from GLONASS. The GPS data (messages) are gathered by the proprietary daemon blobs from MTK. We can't control whether or not it can receive data from GLONASS. If it does, you would found sat. with channel (id) 66 to 96.

MTK use channel (id) 1..32 for GPS 66..96 for GLONASS and 201..232 for BEIDOU now.

However, most of the GPS apks only show the first 12 (or some 21) effective locked sat., the strongest sat. might dominate the result. The rest might be ignored.

I don't know if I can reliably connect GLONASS locally. I might disable GPS in the HAL to test later but that wouldn't be on the top of my list...

Anyway, if you found stock ROM can receive data from GLONASS and mine can't, that means there are some issues in the daemon working in Nougat.

Let me know with screenshots. ;)
[K3 Note Original Android Development] chris-mm:
Hello daniel_hk,

thanks for your fast and interesting reply.

Here are my 2 screenshots.

FYI: I have two K3 Note phones and both phones where laying side by side for the screenshots.

Your latest LineageOS:

https://drive.google.com/file/d/0B_KaN3Hq_hDOVmZadnFVR0dQXzA/view?usp=sharing

Stock S433 ROW:

https://drive.google.com/file/d/0B_KaN3Hq_hDOZ2x0dVJiZWM2ZEU/view?usp=sharing

The used GPS app is called Locus Map Pro. There´s a free version also.

I can highly recommend this app for GPS testing! It will give you very detailed information of the GPS status.

And it will show the GLONASS satelites absolutely reliable!

So please compare the pictures in terms of available satelites:

Its not only no signal or no data from GLONASS, it looks like GLONASS is absolutely not supported (=completely disabled).

FYI: It looks exactly the same when using a Lenovo firmware without GLONASS support (Only the Lenovo ROW firmwares have GLONASS enabled by default).

A lot of MTK devices have GLONASS disabled by default.

I guess it´s all about licenses - so MTK can disable GLONASS in software for some countrys or for cheaper devices.

So maybe your used MTK deamon blob has disabled GLONASS by default???

BTW I´m absolutely shure you can receive GLONASS satelites in HK with an GLONASS enabled device!

The GLONASS satelites are in a worldwide orbit.

Have you access to Playstore apps in HK?

If so please try Locus Map for testing the GPS / GLONASS status.

Thanks again for your efforts!

If there´s something more to test to help you, I shure will do!

Now after trying your Carbon rom I really want to use it as my daily driver. It´s such a fine rom :laugh:

I really hope you will find a way to activate GLONASS :fingers-crossed:

Best regards,

Chris
[K3 Note Original Android Development] nihadxperiarcs:
Camera does not work. Force closes. It is same in every 7.1.2 rom. Only working one is Pixel Farewell edition. Anyone knows how to fix?
[K3 Note Original Android Development] locolyric:
thanks for the continuous support for k3 note device. Previous rom is perfect for me and again , this patch also help all guys to catch up with latest update.

Recommended to everyone who still have k3 note with them.
[K3 Note Original Android Development] bansuk5:
Yes it was in enforcing when i boot up after flash but now i have it to permissive (screenshots below)

Aso i encounter a strange bug that in cal volume was slightly less than what it used to be can someone confim this or is it just me
[K3 Note Original Android Development] sdkone:
it seems to me that this twrp 3.1.1 can't wipe ext4 partition (/data/), just froze up when tried to wipe. I just forced reboot and reformatted the partition as ext2, works great so far. Same with /cache.
[K3 Note Original Android Development] Costa001:
ext4 is better than ext2
[K3 Note Original Android Development] daniel_hk:
GPS GLONASS patch

I had an idea while in traffic. I have tested it after dinner and it works.

Here is the View attachment mt6752-glonass-patch.zip patch. Flash in recovery will enable GPS+BEIDOU+GLONASS. I think it would work for all MTK device with MM daemons. ;)

Theory:

Stock ROM from Lenovo check the country code and set the GNSS mode accordingly. For some unknown reason, custom ROMs can't access that part (I think its in nvram, similar to RIL). The default in our daemon set it to mode 1 (GPS+BEIDOU) so GLONASS is disabled. There is a property file never been used. I added an override property setting it to mode 2 (GPS+CLONASS+BEIDOU) and it works. ;)

It's quite odd. I think you are from dirty flash. You better check what cause that.

Anyway, you may type the following command in a terminal or via adb:

setenforce 0

It would set back to permissive. If it is not persist after reboot, you can add this command to the SHELL command in PerformanceControl. It's under TOOLS. It will issue this command automatically right after reboot.

Official TWRP mostly use LP5.1.1 to build. I had set up that environment a few years ago. TWRP are more or less the same for all devices. I needed to build over 10 models then. To save time, I had written a pearl script to repack and replace a few things (kernel, fstab, default.prop, etc.). It would automatically generate all my requiring variants after I build it out once. It works for my Nexus', OnePlus and Samsung devices. So Tegra, Qualcom and Exynos don't have problem.

Most of the MTK devices use 32bit recoveries so I add K3-Note to my pearl script's data file. It appeared working then.

For some reason, it is not fully working for MTK. The first wipe would take much longer and cause a few errors. It would recover itself after you wipe it again.

May be the kernel or ext utils need to update. Anyway, it's no point to find out why. I'll build another one from source with Android 7.1.2 later. ;)
[K3 Note Original Android Development] chris-mm:
daniel_hk YOU ARE MY HERO!!!

Your GLONASS patch is working!

You make my day, really!

And as promised:

Here´s your delicious german beer together with the proof of your work (a PayPal donation is on the way of course) :silly:

https://drive.google.com/file/d/0B_KaN3Hq_hDOMURLT0VXR25wbGM/view?usp=sharing

And my personal please to all users out there:

Please donate a little bit when you are using other mens hard work.

Just to make the world a bit more friendly again!

Cheers Daniel and my best regards,

Chris
[K3 Note Original Android Development] bansuk5:
Yes i did dirty flash l, maybe this was the problem, anyway thanks for your time , i will try to clean flash now and thanks for making such a great Rom thanks
[K3 Note Original Android Development] agdroubi:
I am getting performance control app has stopped working, it is not even opening. Is it a common problem?
[K3 Note Original Android Development] olgutza34:
if you flashed a new release over the previous one, you've lost supersu. Performance control needs it in order to work. Check Supersu, and if you can uninstall it like a regular app, you know what to to next.

PS I always lost superuser access when flashed a new release over previous one.
[K3 Note Original Android Development] Sir_psycho12:
Audio output

Hey…

I have a question, I don’t if you have noticed this but every Nougat ROM for the K3 Note seems to have an issue with audio playback, the max volume is way too loud and causes the speaker to sound like crap.

So, I was wondering if you know a way to fix this?? You know, like editing some system files to reduce the maximum volume output the speaker maybe?
[K3 Note Original Android Development] bansuk5:
Max audio volume is ok with me, try using poweramp set preset to bass extreme then see the diffence
[K3 Note Original Android Development] daniel_hk:
TWRP-3.1.1-1

This is the TWRP-3.1.1 build from 7.1.2 source, I promised. :)

For some unknown reason, the splash screen doesn't show as expected. After reboot, the screen would blank for ~10 seconds before the main screen started. It doesn't affect normal operation. I have tried for a while but I don't want to waste time for this. Any idea is welcome.

Mediatek/Lenovo just refuse to spare our poor K3-Note for a single moment.... :eek: If you think that's not acceptable, just ignore this. ;)

In this TWRP:

1. 64bit kernel is equipped.

2. The fstab is rewritten. All related partitions can now be backup/restore/wipe as expect now. The list is rearranged putting the common entries to the top.

3. Support both old and new partition by-name.

New stock ROMs/blobs use /dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name to address the partitions

while old recovery/ still use /dev/block/platform/mtk-msdc.0/by-name. That make two sets of standard and its quite misleading.

To make zip(s) flashable, ROM builder need to adjust the recovery fstab accordingly.

Now, backward support is added so that both addressing method are supported. ​

4. Wiping for cache is fixed (I did nothing, just use the latest source to compile)

5. All languages are included now.

6. Support triple frame buffers for MTK.

Download AFH Link