Port to Xiaomi Mi5s Plus (Natrium)
-
After 2 weeks it makes little but great progress
-
This post is deleted! -
Hey, I 'm also trying to port to this device, and I just saw this thread. I'm having the same issues as you - did you ever get the graphics working?
-
Cool, but bad news, our device is a CAF device and need a special version of mir but at the moment there is no more ppa with a working version... I m waiting on a official answer for this, I think it will be foxed after ota 4, hope so
-
@bluekenny I think that's a different issue. KDE Plasma Mobile has a special CAF rootfs, and graphics don't work on that either.
-
So it is eventuelly a libhybris problem ? I'm in Holiday now for two weeks, so i can't help at the moment
THe android container ist running, all partition are mounted and every thin look, on my port it shows that i can't find the right driver as the loading of the driver failed in a C/C++ file error, if can search the log file if you don't have this error
PS sorry for this bad description
-
@bluekenny I got KDE Plasma Mobile working with this kernel patch! I think Ubuntu Touch is broken with Halium 7.1, and CAF devices atm, though.
To merge the patch, cd into the kernel directory, and run
curl https://github.com/Halium/android_kernel_oneplus_msm8996/commit/3e019b8700b36aef379846a748e3a447a8c3dbe7.patch | patch -p1 -
Today i made great progress !
Wifi is working
Phone doesn't reboot / crach anymore ! -
@bluekenny Cool! How about graphics
My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸
-
@flohack doesn't work : first post is up to date
-
@flohack Yes doesn't work
But I can see the finish line Hope it makes sense in English Mirserver load right driver,
thanks to "TheKit" on Telegram -
https://pastebin.com/EUgabSTY
Its going in the right direction...2 days later and I'm stuck on a grafik error / memory setup error
[ 127.543935] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: loading from 0x000000008fe00000 to 0x000000008fe02000
[ 127.561301] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: Memory setup error -
New day, new error ...
[ 0.265849] i2c-msm-v2 75b7000.i2c: probing driver i2c-msm-v2
[ 0.265999] i2c-msm-v2 75b7000.i2c: error on clk_get(core_clk):-517
[ 0.266016] i2c-msm-v2 75b7000.i2c: error probe() failed with err:-517 -
Are you still going out?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login