51

Fundamental issues within kernel source code… | Redmi K20 / Xiaomi Mi...

 4 years ago
source link: https://forum.xda-developers.com/mi-9t/how-to/fundamental-issues-kernel-source-code-t3951597
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

Fundamental issues within kernel source code: need to address problem to Xiaomi

  • If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.

  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

Fundamental issues within kernel source code: need to address problem to Xiaomi

Zenkrey

Senior Member
Jun 14, 2015
Hi everyone.
I'm the developer of the 75Hz display overclock for Mi 9T. I'm working on a better / cleaner way to enable this mod, however, with sadness, I discovered that the kernel source code for Davinci (K20 / Mi 9T) is fundamentally broken. The section I'm talking about is the device tree, an important component which is used to control peripherals on boot. The source code provided by Xiaomi, once compiled, produces a binary that doesn't contain the information necessary to manage the Samsung display. This results in a boot with black screen. If you really desire a future for the custom development of this device, it's important to raise the matter to Xiaomi itself, in a public manner.

Let me know what you think of this and if you had a similar experience after compilation of the kernel source.

Thanks

# Edit: update
https://forum.xda-developers.com/showpost.php?p=79961451&postcount=6
Last edited: Jul 25, 2019

HelpMeruth

Senior Member
Aug 29, 2015 Sweden
That's sad to hear, planning to buy they mi9t in a couple of weeks ill be sure to compile the kernel and check if the issue is still present by then.
Thanks for bringing this up

nesherben

Senior Member
Dec 17, 2015
we need to make know to xiaomi then

hmuny99

Member
Jan 7, 2015
We as a community Need to step up and use social network to let Xiaomi know

dencel007

Senior Member
Jul 19, 2016 Kattappana

Zenkrey

Senior Member
Jun 14, 2015
Made a breakthrough:
Unpacked dtbo.img from global firmware 10.3.6. Decoded the .dtb into .dts. Taken the 13 .dts relevant to the device (check Makefile). Re-encoded and repacked in a new, smaller dtbo.img.
I flashed this new dtbo.img through fastboot, booting successfully the device.
By taking the .dts provided by Xiaomi in the Mi 9T / K20 repo and compiling them, then packing them into a dtbo.img, and then flashing said .img through fastboot causes an unsuccessfull boot and a black screen.
So, I took the first .dts (from the source) and compared it to the correspondent .dts (from the decoded global firmware) and got this interesting diff (green one is the one working, red one is from the source that doesn't work):

https://pastebin.com/wNu0mVy0

So, there is obviously something wrong going on.

flubba86

Senior Member
May 7, 2010
Made a breakthrough:
Unpacked dtbo.img from global firmware 10.3.6. Decoded the .dtb into .dts. Taken the 13 .dts relevant to the device (check Makefile). Re-encoded and repacked in a new, smaller dtbo.img.
I flashed this new dtbo.img through fastboot, booting successfully the device.
So, there is obviously something wrong going on.
Have you tried taking the decoded .dts files and placing them in the kernel source tree to see if it builds a working kernel? (Or is that irrelevant, is it only used for building the dtbo.img?)

Zenkrey

Senior Member
Jun 14, 2015
Have you tried taking the decoded .dts files and placing them in the kernel source tree to see if it builds a working kernel? (Or is that irrelevant, is it only used for building the dtbo.img?)
They would compile, of course, but that is not the best way to fix the issue. The problem, here, are the wrong commands used to control the display.
Reactions: shaon121
How this can be reported to mi team. i tried to post on mi community using mi community app. But other should also bring this forward.

hmuny99

Member
Jan 7, 2015
How this can be reported to mi team. i tried to post on mi community using mi community app. But other should also bring this forward.
Twitter

Dev Dezigns

Senior Member
Jan 2, 2015
I tweeted looping mi team how they fix it soon.
give me a link to your tweet to retweet it.

shaon121

Senior Member
Aug 8, 2012
Thank you so much for raising awareness

report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK