[K3 Note Original Android Development] daniel_hk:
Yes, I'm not responsive because either there is no detail or the answer is already in my posts or in the thread. If people don't want to waste time searching and/or reading, I also don't want to waste mine to respond, fair enough? :) I seldom promise too. If I can, I would spent my time on the solutions and release something real instead.

[MENTION=5895603]dr_root[/MENTION] I don't have a PHD like you.:D I think you just tried to be modest. You had released something for this device months before me. You know how and probably just don't have time.

Anyway, we can choose 5G band at will but not for preamble. I don't know how many devices you have seen. Even if it's true in your experience, that doesn't mean it's true everywhere. Set it to short permanently would be irresponsible because some devices won't work. I played with open source router firmware briefly early last year. I lost that interest after a week or two because it seems not much to learn. I can't pretend to be an expert. I can only say what I know.

The following is the definition of the flag in the kerenl:

typedef enum _ENUM_PARAM_PREAMBLE_TYPE_T {
PREAMBLE_TYPE_LONG = 0,
PREAMBLE_TYPE_SHORT,
PREAMBLE_TYPE_AUTO	/*!< Try preamble short first, if fail tray preamble long. */
} ENUM_PARAM_PREAMBLE_TYPE_T, *P_ENUM_PARAM_PREAMBLE_TYPE_T;

The word "tray" should be "try". The source is there for a long time. It just can't lie. If it does what it said, even in stock ROM, setting the nvram ONLY limit it to short. Obviously PREAMBLE_TYPE_AUTO should just do the same for you. Why and how behaved differently as you said? I don't know how you measure the performance and which preamble. You might have a logic analyzer and other instruments which I don't or connecting a console to your router/hub and have intensive tests. Either way, sharing those data would be better for everyone. Again, even if it is true for you, that doesn't mean it's true elsewhere. If not, it would increase the chances of dropping connections and performance significantly. Wide channels? That's the same too.

Furthermore, the sources from MTK are common to many devices, it has the flag doesn't mean it really support/use it. You have to verify it before you bring it up. It's a responsibility. VoLTE is the very good example. People would blindly believe and thought there were gold to be dug. They wasted their time because someone had released that rumour. I had over 50 PM's, posts and e-mails asking/begging me for that so I'm a victim too. I was forced to study the spec. and led to confirm it. I hate to argue so it is kinda against my will too. :(

I don't think you know what journaling is for ext4. There are plenty of reading for that. Years ago, there was tweaks. For old devices with old eMMC and slow cpu, it might help. I had those tweaks for my 2012 Nexus but it doesn't help much after 7.0. There are also other alternatives which I used in my Samsung devices (also years ago). Either way, it is just mount flags which you can test easily, nothing special. Yes, I haven't tried it in K3-note myself. I supposed it would be even less obvious since we have newer eMMC and much better cpu. I rather keep the insurance.

There are also custom kernels which seems the better places for tweaks. I only tweak the kernel recently for my personal use. My aim is to make it work for all my ROMs as well as stock VibeUI. Therefore I wouldn't include anything not working generally and I would keep everything the same way as stock. If someone have tried, the kernel in post#275 also fully working for stock VibeUI too, at least for me. :)

I don't know what's your objective. I believe you are not those searching for keywords on the web and posting just for publicity and likes. If you want to help, building a kernel is quite easy. The set up is also simple. You don't really need the device. Why don't you release a custom kernel with all your tweaks? Start your own thread and share whatever you want. I would be more than happy to see new comers rather than another backseat driver. ;)

OK, Let's back to the reason of this post. I want someone like [MENTION=2852265]freegame619[/MENTION] to join us so I had tried Carbon again earlier this week. There were still a few glitches. After a few nights, I finally have a presentable one yesterday. I would clean up the device tree for Carbon when I have time. Hoping it would make others life easier.

The new CarbonROM CR-5.1 is out. For detail, see the change log in post#1 for detail.