The display works well with the stock firmware
Oh, seems that I misunderstood 
because the Normal version has a TV-ish launcher as well.
Anyway it is yet the best rom for the VIM3L. The only things I would probably change is to remove the screenshot button from the bottom navigation bar and give the user a screen to select default launcher (TV or native) during the first boot. Fantastic job!
By the way. is the SipManager library supported in this rom?
Ye i know is a hybrid launcher, i used that one because is very customizable ( you can see here in the forum some pics of what users made with it).
I will only include one, i do not like my roms to be to “clunky” with lots of apps.
Anyway you can always install another and choose your default one in settings.
Yes SipManager is supported, at least i think i enable it lol it was a few months ago i can’t remember all. (to many other projects in my head)
1 Like
Great! Can’t wait till I am able to use the rom with the TS050 display. New projects coming!
Hi @superceleron hope you are doing well.
Could you please provide an ETA for the new version with the fix for TS050 touchscreen and VIM3L?
He posted a head’s up of the new release here:
I think you need to wait for a while…
it still has vim3L problems and the good news is the Superceleron has a TS050 display
Ye you need to wait, khadas just sent me today the new Vim3L, mine died… to much abuse lol ( Many thks @Terry and @lilysun for the new Vim3L )
So should be here in a few weeks i think, maybe less…
2 Likes
hello Superceleron, you keep the entire Khadas community in suspense with statements like this 
hmm why? its normal not all devices going to be 100% you need to count that there is always some who going to dye, but you expect it to be low in volume of course.
Anyway my devices get real abuse, i flash him like on average 70 times, on some even more than that.
USB and HDMI ports hear out of so many times you connecting and disconnecting… etc etc…
Some devices will last longer others dont.
See this, i still have my 1º original vim1(2017) and it was abused for real that one, it as like 300 plus flashes and it still goes strong, of course the HDMI port is a bit flaky but that is normal.
So do not be warn, its normal that to happen
2 Likes
you sound like you want to be the official durability tester of khadas products… 
1 Like
LOL na no way, i already have to much work
No problem…, you already did the job of testing it 
Hey SuperCeleron
Thanks for the great work on smooth ROM
I am curious if you use the Khadas official Uboot source? I am asking because their GO version seems to have more resolutions available but also is lacking some key android features i need for my project. I am VERY familiar with building kernel source and if I can build uboot separate against the device properties for this device to enable more resolutions that was essentially my goal.
If Android doesnt handle resolutions in the uboot image then i will keep hunting 
yes i use khadas official, with some little changes i did to best fit my needs.
Anyway, last time i have “sync” my stuff with khadas tree was like 2,5 months ago, i know they added a few more stuff to uboot, but i still need to check it.
1 Like
looking deeper it appears to be in their kernel source called out in
arch/arm/cpu/armv8/g12a(b)/hdmitx20/***
I tried to pull down their kernel build locally and flash over your rom but I got no logcat no kmsg and no boot 
This patch is the part I am missing on your ROM
Are you running just patched version of their source or did you pull down the device into AOSP official code?
ye i know, you have to wait until a merge all the changes with mine and then do a build.
I do not know how long, since im busy with work.
2 Likes
I have gotten normal AOSP not khadas source compiled for this board and it is working how I wanted. I will use that until your update thank you so much for your time
i already merged it last night, just need to fix some merge conflicts.
3 Likes
Hi there guys, im sorry i still did not rls my build i have it like 90% done, just lack time this past month to do any more work on it, very busy with work at this moment. ( @Robert knows what i have been working to be so busy, maybe he can show you guys if he has the time!)
I did test one of the issues that was the khadas touchscreen not working ok, now it works just fine… but i can’t do more test on it, one of my kids when i was testing pull the screen and rip off the ribbon cable (ouch…) ye i know… lol
Anyway just to give some news to you guys.
4 Likes