Hello Guys,
I've been looking for the Kernel Source, Device tree and vendor for the XIaomi MI 10 Lite for building LineageOS 17.1
So far no look, found this:
Code:
Kernel Source:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/ce6e246e855271643d5e90bb4c27706749a002e7
Device Tree:
https://github.com/MiCode/kernel_devicetree/tree/vangogh-q-oss
And This
Code:
Vendor:
https://github.com/AndroidBlobs/vendor_xiaomi_monet
Device Tree:
https://github.com/AndroidBlobs/device_xiaomi_monet
But none of those works for building LineageOS
Does anyone know where to find the right ones?
Thanks!!
Corret me it I'm wrong, but isn't monet the codename for the MI 10 lite 5g and vangogh the one for the MI 10 lite zoom?
I guess you are searching for another device tree
Edit okay my fault, seems like there is no mi 10 lite without a suffix
4Style said:
Corret me it I'm wrong, but isn't monet the codename for the MI 10 lite 5g and vangogh the one for the MI 10 lite zoom?
I guess you are searching for another device tree
Edit okay my fault, seems like there is no mi 10 lite without a suffix
Click to expand...
Click to collapse
Yes you are Right, My phone is Monet, been looking for it but looks like Xiaomi haven't released them yet
4Style said:
Corret me it I'm wrong, but isn't monet the codename for the MI 10 lite 5g and vangogh the one for the MI 10 lite zoom?
I guess you are searching for another device tree
Edit okay my fault, seems like there is no mi 10 lite without a suffix
Click to expand...
Click to collapse
Yes you are Right, My phone is Monet, been looking Kernel Sources for it, but looks like Xiaomi haven't released them yet
aceventura82 said:
Yes you are Right, My phone is Monet, been looking Kernel Sources for it, but looks like Xiaomi haven't released them yet
Click to expand...
Click to collapse
According to this article here on XDA the firmware for each device (Mi 10 Lite 5G and Zoom) is different, but the kernel is unified.
Here you should find everything: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/vangogh-q-oss
4Style said:
According to this article here on XDA the firmware for each device (Mi 10 Lite 5G and Zoom) is different, but the kernel is unified.
Here you should find everything: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/vangogh-q-oss
Click to expand...
Click to collapse
Hello, yes, I saw that repo, looks like those are the right ones.
But looks like is not good for building with LineageOS
I still getting thos warning when syncing repo
I will keep trying whit those, Thanks!!
Code:
[hardware/qcom-caf/msm8916/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/msm8952/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/msm8960/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/msm8974/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/msm8994/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/msm8996/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/msm8998/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/sdm845/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/sm8150/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/sm8250/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom/display: Shared project LineageOS/android_hardware_qcom_display found, disabling pruning.
hardware/qcom-caf/apq8084/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/msm8916/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/msm8952/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/msm8960/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/msm8974/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/msm8994/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/msm8996/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/msm8998/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/sdm845/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/sm8150/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/sm8250/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom/media: Shared project LineageOS/android_hardware_qcom_media found, disabling pruning.
hardware/qcom-caf/apq8084/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/msm8916/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/msm8952/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/msm8960/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/msm8974/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/msm8994/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/msm8996/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/msm8998/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/sdm845/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/sm8150/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
hardware/qcom-caf/sm8250/audio: Shared project LineageOS/android_hardware_qcom_audio found, disabling pruning.
/CODE]
https://drive.google.com/file/d/1D1QatSzSnbtIcoxPinoQ069T0zUSxsuq/view?usp=sharing
jonnieitis said:
https://drive.google.com/file/d/1D1QatSzSnbtIcoxPinoQ069T0zUSxsuq/view?usp=sharing
Click to expand...
Click to collapse
This is a test rom? someone try this build?
Test as I cannot at mo
jonnieitis said:
Test as I cannot at mo
Click to expand...
Click to collapse
your build has system img file inside, all phones that comes with android 10 use super partition that make impossibile flash this rom with twrp
Guys, y'all can flash some GSI roms that contain Phhusson patches (AOSP, Lineage, BLESS (Bliss) tested, works absolutely fine without any bugs, except bluetooth/wired headphones, but i already figured out how to fix it so it works absolutely good now.)
T3cheN said:
Guys, y'all can flash some GSI roms that contain Phhusson patches (AOSP, Lineage, BLESS (Bliss) tested, works absolutely fine without any bugs, except bluetooth/wired headphones, but i already figured out how to fix it so it works absolutely good now.)
Click to expand...
Click to collapse
Which GSI did you use? A only or AB
Maish05 said:
Which GSI did you use? A only or AB
Click to expand...
Click to collapse
A/B, our device is System-as-root
T3cheN said:
A/B, our device is System-as-root
Click to expand...
Click to collapse
Thanks now I have courage to try:highfive:
T3cheN said:
Guys, y'all can flash some GSI roms that contain Phhusson patches (AOSP, Lineage, BLESS (Bliss) tested, works absolutely fine without any bugs, except bluetooth/wired headphones, but i already figured out how to fix it so it works absolutely good now.)
Click to expand...
Click to collapse
tried all gsi but i have some audio issues, disable sound effects and enable qualcomm alternate policies in phh settings helps but ringtones, music and system sound makes a lot of strange noise. It's a common vendor problem in mi 10 series
arko7123 said:
tried all gsi but i have some audio issues, disable sound effects and enable qualcomm alternate policies in phh settings helps but ringtones, music and system sound makes a lot of strange noise. It's a common vendor problem in mi 10 series
Click to expand...
Click to collapse
I enabled use alternate audio policy in Qualcomm fetures, then in Misc features Force headset switch (Huawei default), Disable audio effects, Bluetooth workarounds - Huawei, Force-disable A2DP offload and all works fine now, i don't get any strange noises after this.
Also which gsi-s did you use? I want to use Resurrection Remix but all gsi-s that successfully booted up are Bliss, Lineage and AOSP, idk how to fix it yet
T3cheN said:
I enabled use alternate audio policy in Qualcomm fetures, then in Misc features Force headset switch (Huawei default), Disable audio effects, Bluetooth workarounds - Huawei, Force-disable A2DP offload and all works fine now, i don't get any strange noises after this.
Also which gsi-s did you use? I want to use Resurrection Remix but all gsi-s that successfully booted up are Bliss, Lineage and AOSP, idk how to fix it yet
Click to expand...
Click to collapse
all gsi are the same
try to play ringtone sometimes, i heard some pop noises coming from the speaker
arko7123 said:
all gsi are the same
try to play ringtone sometimes, i heard some pop noises coming from the speaker
Click to expand...
Click to collapse
The only thing i hear sometimes is the notification sounds kinda screwed up, but usually it's good. All ringtones and other things sounds good after this fix.
UPD. Re-flashed Bliss, re-applied fix. These sounds work absolutely nice now.
But i still can't boot any other gsi than AOSP, Lineage or Bliss, it just boots up directly to recovery no matter what i'm doing
T3cheN said:
But i still can't boot any other gsi than AOSP, Lineage or Bliss, it just boots up directly to recovery no matter what i'm doing
Click to expand...
Click to collapse
you should flash rom compiled from eremitein
havoc, erfan gsi and others except phh and lineage won't boot up
T3cheN said:
Guys, y'all can flash some GSI roms that contain Phhusson patches (AOSP, Lineage, BLESS (Bliss) tested, works absolutely fine without any bugs, except bluetooth/wired headphones, but i already figured out how to fix it so it works absolutely good now.)
Click to expand...
Click to collapse
I want to try a aosp gsi... it's possible tell me how I do to flash a gsi rom? Thanks
Related
The DTS Port has been released publicly is available from the following link:
https://forum.xda-developers.com/android/software/port-dtsx-ultra-dts-headphonex-t3896233
There are kernel patches still necessary (for both ports) and the new guide is here:
https://gitlab.com/dts_project/intro/blob/master/README.md
Used msm8998 for sdm660. Seems to be working fine so far. Thanks.
How to get it?
How to install on SD821?
Oneplus3T?
Actually we haven't released the kernel and stuff, yet. I'm working with those guys on it and we have a first beta Kernel running on my device, which is also a OP 3t. By now, it will be just for OxygenOS Oreo.
Gauravlonkar said:
How to get it?
How to install on SD821?
Oneplus3T?
Click to expand...
Click to collapse
OP3/T is MSM8996. Just pick the commits into your kernel source.
We are actually changing some stuff to get this fully running. We have already one kernel DTS eagle is fully working. Hopefully more devs will implement the driver.
Thanks for posting and porting this!
I know you guys are still working on fleshing out the commits for this, but as-is on the OP3 I needed to make a change in order for it actually compile the new dts_eagle_drv.o module and work:
https://github.com/holyangel/OP3/commit/c8b84a701fdcf82dc725beaaa40f740b13e84f7a
Basically was missing sourcing the dts_eagle/Kconfig file in drivers/misc/Kconfig, and had to remove the 'depends on CONFIG_SND_SOC_QDSP6V2' as i'm its not seeing that option during build time.
Once that was done it compiles and works great :good:
HolyAngel said:
Thanks for posting and porting this!
I know you guys are still working on fleshing out the commits for this, but as-is on the OP3 I needed to make a change in order for it actually compile the new dts_eagle_drv.o module and work:
https://github.com/holyangel/OP3/commit/c8b84a701fdcf82dc725beaaa40f740b13e84f7a
Basically was missing sourcing the dts_eagle/Kconfig file in drivers/misc/Kconfig, and had to remove the 'depends on CONFIG_SND_SOC_QDSP6V2' as i'm its not seeing that option during build time.
Once that was done it compiles and works great :good:
Click to expand...
Click to collapse
Take a look at the repo. @LazerL0rd force pushed new commits with the fix.
Will this work on SD625??
using this on hima "LineageOS 15.1 Unoffical" and "AICP 13.1 Official". Works great so far!
crian said:
Take a look at the repo. @LazerL0rd force pushed new commits with the fix.
Click to expand...
Click to collapse
yep builds now by itself without my commit :good:
HolyAngel said:
Thanks for posting and porting this!
I know you guys are still working on fleshing out the commits for this, but as-is on the OP3 I needed to make a change in order for it actually compile the new dts_eagle_drv.o module and work:
https://github.com/holyangel/OP3/commit/c8b84a701fdcf82dc725beaaa40f740b13e84f7a
Basically was missing sourcing the dts_eagle/Kconfig file in drivers/misc/Kconfig, and had to remove the 'depends on CONFIG_SND_SOC_QDSP6V2' as i'm its not seeing that option during build time.
Once that was done it compiles and works great :good:
Click to expand...
Click to collapse
sound/soc/msm/Kconfig
14:config SND_SOC_QDSP6V2
It's there alright. I fixed the other issues with a force-push btw.
@Claymore1297 @crian @HolyAngel another update has been pushed - I've joined the normal naming and folder placement scheme of the Linux Kernel and therefore have decided to move the Kconfig and dts_eagle folder to under drivers/misc/qdspv2 (well the Kconfig was added to drivers/misc/Kconfig as there is no child Kconfig for this folder)
shanks125 said:
Will this work on SD625??
Click to expand...
Click to collapse
There's no way you will know except you test it yourself. Pick 8996 commits, btw.
Sent from my Redmi Note 4 using XDA Labs
Do we need any application for controlling it?
NATO66613 said:
Do we need any application for controlling it?
Click to expand...
Click to collapse
Need, not really. Should have, yes. The module for that still isn't public yet because it's in beta. Join the ICESOUND group on TG for an show public version.
Kernel stuff works tho.
I'm on Omnidragon, the devs implemented DTS Eagle in kernel. As this an 'always on feature' I was wondering how this works/interferes with mods like v4a or James DSP?
mvn66 said:
I'm on Omnidragon, the devs implemented DTS Eagle in kernel. As this an 'always on feature' I was wondering how this works/interferes with mods like v4a or James DSP?
Click to expand...
Click to collapse
Works fine, it's just an addition to the many audio effects Android has. The kernel stuff is just a backend and allows it to be integrated deeply into the system.
LazerL0rd said:
Need, not really. Should have, yes. The module for that still isn't public yet because it's in beta. Join the ICESOUND group on TG for an show public version.
Kernel stuff works tho.
Click to expand...
Click to collapse
Can't find it can you please send it link
tested and seem working fine with SD435, really interesting sound enhancement.
Thanks
So is there anyone who can port an AOSP 9 ROM for NEXUS 5, when Google publish the source online ?
Doubt it, not even Oreo is stable enough
Maybe @amaces or @nasty007 can manage to boot it but don't get your hopes up.
edu24lal said:
Doubt it, not even Oreo is stable enough
Click to expand...
Click to collapse
almost all the Rom is stable, with the exception of Bluetooth.
DarkMaxOff said:
almost all the Rom is stable, with the exception of Bluetooth.
Click to expand...
Click to collapse
I agree, except oreo roms are slow even with a custom kernel ... Nougat still faster
edu24lal said:
I agree, except oreo roms are slow even with a custom kernel ... Nougat still faster
Click to expand...
Click to collapse
CrDroid 4.4 with stock kernel very smooth and fast, but I changed kernel to Breakfast, my battery so weak
Android 9.0 Pie on Nexus 5 - it's a matter of time!
edu24lal said:
Doubt it, not even Oreo is stable enough
Click to expand...
Click to collapse
Dirty Unicorns Oreo is quite stable n smooth for me.
So ofcourse Pie is very much possible even if it's not completely stable.
Botty-Ivan said:
So is there anyone who can port an AOSP 9 ROM for NEXUS 5, when Google publish the source online ?
Click to expand...
Click to collapse
I started syncing the source code. But i can't give eta or release, build date etc. My internet connection is slow.
playerkirk1 said:
Oreo is daily driver stable on Nexus 5, has been for a long time. I wouldn't be surprised that with all the extra optimization Google's done in Pie that once we get a fully working rom it'll work just as if not better than Oreo
Click to expand...
Click to collapse
But why there is no lineage os ?
I downloaded 60 percent of Android Pie source code. I hope i will build at evening. Probably it won't boot at first build. I will work on bugs etc. Don't wait me. It can take 1-2 weeks for a stable build.
playerkirk1 said:
Obviously that's not up to me, I'm not a Lineage OS Dev. They probably dropped support cause of the age of the phone unlike other devs.
Click to expand...
Click to collapse
No that's not the reason, please educate yourself on the subject. The reason why the Nexus 5 doesn't have official support/builds of LineageOS 15.1 is because of some bugs that haven't been fixed. As long they don't get fixed there will be no official builds.
playerkirk1 said:
As I said, I'm not an LOS Dev. People shouldn't be asking me why there isn't any official builds. I never claimed to be right, I just made a guess. Also, why does it matter if there's an official version or not? LOS isn't the be all end all for ROMs, there's other ROMs out there that people can use, like RR, or DU. There's also the unofficial version of LOS, but I haven't tried it out.
Click to expand...
Click to collapse
I didn't mean to be hostile in any way I just wanted to get all speculation out of the way. I don't want people to get a wrong idea about why there are no official LineageOS builds. Was getting tired of the "is Bluetooth calling fixed" messages on threads of Oreo ROMs. You are right about the choice of ROMs but it's always nice to see some official support. But I do think Dev's will eventually drop support for this device, everything comes to an end so we will see less and less ROM's available for the Nexus 5 eventually as it get's older.
I started compiling the source code. I am handling errors.
I built it successfully. I will install. I hope it will boot. (folder name is false, don't mind it)
EDIT: Not booted. ROM is very buggy. I will work on it.
metahex12 said:
I built it successfully. I will install. I hope it will boot. (folder name is false, don't mind it)
EDIT: Not booted. ROM is very buggy. I will work on it.
Click to expand...
Click to collapse
Try setting SELinux to permissive!
Also, could you share your build if that's not a problem for you?
ewentualpl said:
Try setting SELinux to permissive!
Also, could you share your build if that's not a problem for you?
Click to expand...
Click to collapse
Okay, i will upload it today for testers but there is no boot anim or adb (you can access partial logs from recovery). I am an Android Developer in a company. I can't work on it everytime. I will do my best in this weekend. (I am starting today)
ewentualpl said:
Try setting SELinux to permissive!
Also, could you share your build if that's not a problem for you?
Click to expand...
Click to collapse
It is already permissive. Problem is probably kernel and some SELinux policies.
I found the problem in logcat.
Here:
Code:
<3>[ 2.598985] init: /init.rc: 65: invalid command 'load_system_props'
<3>[ 2.599110] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
<3>[ 2.599252] init: could not import file '/init.recovery.vold_decrypt.rc' from '/init.rc'
<3>[ 2.599358] init: /init.recovery.hammerhead.rc: 17: invalid command 'ln'
I will try to fix it today. Then it will boot probably.
metahex12 said:
I found the problem in logcat.
Here:
Code:
<3>[ 2.598985] init: /init.rc: 65: invalid command 'load_system_props'
<3>[ 2.599110] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
<3>[ 2.599252] init: could not import file '/init.recovery.vold_decrypt.rc' from '/init.rc'
<3>[ 2.599358] init: /init.recovery.hammerhead.rc: 17: invalid command 'ln'
I will try to fix it today. Then it will boot probably.
Click to expand...
Click to collapse
Please more logs
VENDOR FOR GSI (Generic System Image)
I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Bevice By This Guide here If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Just to Make it clear, Treble Vendor for A8/A8+ is been ported from A7 2018 Oreo. We have tested many Oreo GSI from phhuson generic list and they are booted with this vendor. We have also tested Pie GSI, most of them didn't booted but few did(Phh-AOSP-9.0).
What is GSI?
A Generic System Image (GSI) is a system image. It is considered a "pure Android" implementation with Android Open Source Project (AOSP) code that any Treble device can run successfully. For more info visit here : https://source.android.com/setup/build/gsi
What is working?
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
Fingerprint
All Sensors
2D/3D Graphics + Vulkan
What is not working?
VoLTE
**Important: Vendor attached to this thread is stable, If you find any bugs on GSI, report it to their respective maintainer's with logs.
Instructions
1- Make Sure u Treble your device
2- Wipe System, Vendor, Data, Cache
3- Flash Vendor-Installer.zip (includes Kernel)
4- Flash GSI as system_image on TWRP
5- Reboot and start using your device
Downloads. Changelogs below
Credits
IF you helped in this rom and i forgot you, tell me in a PM or in a reply
@corsicanu for repartition help
@lzzy12 , @TaifAljaloo , @Griffin98 , @somadsul , @ananjaser1211 for lot of contributions and helping to fix bugs
@enesuzun2002 , @neondragon1909 for helping to fix FP and NFC
@587.saboor for testing
XDA:DevDB Information
Project Treble, Vendor for Samsung Galaxy A8 / A8+ 2018
Kernel Source
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: v1.0
Created 2019-02-12
Last Updated 2019-02-12
Download
Vendor-Installer For Android 8.1 / 9.0 GSIs (includes Kernel)
You can download an A only ARM64 GSI from here
OpenGapps
Fix for bugs
Camera Fix
Fingerprint Fix
Changelog
V1.0
-initial release
reserved 2
Massive thanks to all of you guys!
I have just installed it on my device and it works wonderfully. I used the AOSP extended and everything's great so far. Thanks a lot for giving us this opportunity, I've been looking for a stock experience on my A8+ plus for a while now
wayers said:
I have just installed it on my device and it works wonderfully. I used the AOSP extended and everything's great so far. Thanks a lot for giving us this opportunity, I've been looking for a stock experience on my A8+ plus for a while now
Click to expand...
Click to collapse
More is yet to come:highfive: untill i have this device
prashantp01 said:
More is yet to come:highfive: untill i have this device
Click to expand...
Click to collapse
I'm trying to install asop extended from.
I flashed vendors then flashed rom image and show no system installed.
What partition is a ? I through it was system?
I'm new at flashing this .
What I'm I doing wrong?
I have flashed your project treble-rom it works good.
mchlbenner said:
I'm trying to install asop extended from.
I flashed vendors then flashed rom image and show no system installed.
What partition is a ? I through it was system?
I'm new at flashing this .
What I'm I doing wrong?
I have flashed your project treble-rom it works good.
Click to expand...
Click to collapse
If it shows no OS installed.... Just reboot it.. It will boot gsi
prashantp01 said:
If it shows no OS installed.... Just reboot it.. It will boot gsi
Click to expand...
Click to collapse
What do I whipe before install?
Do flash image to system?
mchlbenner said:
Do flash image to system?
Click to expand...
Click to collapse
Yes do flash your gsi to system image and reboot
prashantp01 said:
Yes do flash your gsi to system image and reboot
Click to expand...
Click to collapse
Last question do do do a full whipe data system ECT?
Thanks I got it!!
Dolby works on asop extended rom
No GSI image is working good. Camera is still unstable in Re-commanded GSI images and others. No GSI image is connecting with PC . i have tried every GSI image Mentioned in this post and Other famous Ones as well. In most of them Finger print is also not working. i tried every image for just 10 mints and i fingered out these things may be many more.
ajnajao1 said:
No GSI image is working good. Camera is still unstable in Re-commanded GSI images and others. No GSI image is connecting with PC . i have tried every GSI image Mentioned in this post and Other famous Ones as well. In most of them Finger print is also not working. i tried every image for just 10 mints and i fingered out these things may be many more.
Click to expand...
Click to collapse
I have had them all connect to PC undo USB debugging and select transfer files and the camera works fine.
Finger print only works on Galaxy project rom.
Picture included.
I'm on asop extended rom .
wayers said:
I have just installed it on my device and it works wonderfully. I used the AOSP extended and everything's great so far. Thanks a lot for giving us this opportunity, I've been looking for a stock experience on my A8+ plus for a while now
Click to expand...
Click to collapse
Can you tell us what's broke and what's not in the GSI ?
Also how is the experience @mchlbenner ?
SRIHARI_GUY said:
Can you tell us what's broke and what's not in the GSI ?
Also how is the experience @mchlbenner ?
Click to expand...
Click to collapse
The Galaxy project rom all works.
I'm on aosp extended rom and it has two bugs only.
No volte
No finger print.
Dolly works
The rom is a 9/10.
This rom works really good.
mchlbenner said:
The Galaxy project rom all works.
I'm on aosp extended rom and it has two bugs only.
No volte
No finger print.
Dolly works
The rom is a 9/10.
This rom works really good.
Click to expand...
Click to collapse
I can live without VoLTE but someone has to fix the fingerprint issue. Can anyone who tried fixing it open a issue in AOSP Extended's GitHub or any for that matter. I know it's asking for too much . If there's a dirty fix, I am cool with that as well
---------- Post added at 03:53 AM ---------- Previous post was at 02:57 AM ----------
@prashantp01 Does the fingerprint sensor work in Phh-Treble? I am considering to try both Phh-Treble and AOSP Extended. Afaik the GitHub says Fingerprint works just fine and you made a dirty fix for Phh-Treble Camera issue as well. So what can I look forward?
ajnajao1 said:
No GSI image is working good. Camera is still unstable in Re-commanded GSI images and others. No GSI image is connecting with PC . i have tried every GSI image Mentioned in this post and Other famous Ones as well. In most of them Finger print is also not working. i tried every image for just 10 mints and i fingered out these things may be many more.
Click to expand...
Click to collapse
SRIHARI_GUY said:
Can you tell us what's broke and what's not in the GSI ?
Also how is the experience @mchlbenner ?
Click to expand...
Click to collapse
SRIHARI_GUY said:
I can live without VoLTE but someone has to fix the fingerprint issue. Can anyone who tried fixing it open a issue in AOSP Extended's GitHub or any for that matter. I know it's asking for too much . If there's a dirty fix, I am cool with that as well
---------- Post added at 03:53 AM ---------- Previous post was at 02:57 AM ----------
@prashantp01 Does the fingerprint sensor work in Phh-Treble? I am considering to try both Phh-Treble and AOSP Extended. Afaik the GitHub says Fingerprint works just fine and you made a dirty fix for Phh-Treble Camera issue as well. So what can I look forward?
Click to expand...
Click to collapse
1)Camera is fixed for all gsi....just check post #2
2)phone which cant detect by pc.. are because of magisk....magisk breaks the mtp
3)fingerprint is working...only AOSP by phh have latest implementation....other gsi maintainers didn't updated those phh patches, so most likely u will face FP bug on their gsi. Fingerprint from VENDOR is stable
4)VoLTE well idc about it, on AOSP volte is impossible for exynos
SRIHARI_GUY said:
I can live without VoLTE but someone has to fix the fingerprint issue. Can anyone who tried fixing it open a issue in AOSP Extended's GitHub or any for that matter. I know it's asking for too much . If there's a dirty fix, I am cool with that as well
---------- Post added at 03:53 AM ---------- Previous post was at 02:57 AM ----------
@prashantp01 Does the fingerprint sensor work in Phh-Treble? I am considering to try both Phh-Treble and AOSP Extended. Afaik the GitHub says Fingerprint works just fine and you made a dirty fix for Phh-Treble Camera issue as well. So what can I look forward?
Click to expand...
Click to collapse
One thing on aosp extended only 6.0 they boot fine 6.1 and up will not boot.
Coconut Kernel for LineageOS 18.1 - With Nethunter Support
Code:
***I wont be responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
Just flash the kernel from recovery for supported ROMs.
You can use this kernel for Nethunter functions and other chroot applications like Linux Deploy.
HID and DriveDroid patches are also included.
Note:- The USB Wifi adapter firmware collection is also included with the zip and will be automatically installed. No need to use additional magisk module for installing firmwares.
Source
https://github.com/xpz3/android_kernel_oneplus_msm8996-2
hi, does it work with PE A11? thanks
mohawahba said:
hi, does it work with PE A11?
Click to expand...
Click to collapse
This is compiled from los 18.1 kernel source with modifications for nethunter. I don't use custom rom much, so i don't know about specific features that a custom rom like pe have. If the android version is same, it should work, but if the rom has any special feature that's dependent on the kernel it may or may not work. You can try flashing and see. If it doesn't work, just go back to the old kernel.
Hi!
So i have some problems with getting my wifi-adapter working, can u help me?
So i have Lineageos 18.1 installed om my op3t, latest nt from kali website and your kernel. Using a RTL8811AU, i can see it with lsusb and i cant find any errors in dmesg. I have tried to change otg adapter and i have tried with y-cable. But still no luck... Is there anything else i can try?
thx for help.
jobsdonn said:
Hi!
So i have some problems with getting my wifi-adapter working, can u help me?
So i have Lineageos 18.1 installed om my op3t, latest nt from kali website and your kernel. Using a RTL8811AU, i can see it with lsusb and i cant find any errors in dmesg. I have tried to change otg adapter and i have tried with y-cable. But still no luck... Is there anything else i can try?
thx for help.
Click to expand...
Click to collapse
Whats the issue you're facing?
@fredrickz
Thank you for this kernel
Just a question:
which nethunter version do I have to install?
On the kali.org page are nethunter releases for pie and ten. But not for eleven - this kernel is for eleven.
Do I install a eleven Custom ROM and then the nethunter PIE version and then this nethunter kernel?
fredrickz said:
Whats the issue you're facing?
Click to expand...
Click to collapse
I have the same problem with TP-LINK TL-WN722N (RTL8188EUS) - it looks nice in lsusb, no problems are reported in dmesg, but no wlan1 device ... Do i miss something?
nadastry said:
@fredrickz
Thank you for this kernel
Just a question:
which nethunter version do I have to install?
On the kali.org page are nethunter releases for pie and ten. But not for eleven - this kernel is for eleven.
Do I install a eleven Custom ROM and then the nethunter PIE version and then this nethunter kernel?
Click to expand...
Click to collapse
Flash generic arm64 installer, then this kernel
Which toolchain do you use to build your kernel?
HI
I have flashed your kernel,but when I try to use rucky,it Pop-up ”kernel not supported!“
How can I fix it？
jlock. said:
HI
I have flashed your kernel,but when I try to use rucky,it Pop-up ”kernel not supported!“
How can I fix it？View attachment 5895271
Click to expand...
Click to collapse
fixed the problem，just need to flesh agian
Any solution with missing wlan1 adapter? HID also doesnt work. OnePlus3T + LineageOS 18.1 + NetHunter Lite ARM64 + Kernel
lemongrass1717 said:
Any solution with missing wlan1 adapter? HID also doesnt work. OnePlus3T + LineageOS 18.1 + NetHunter Lite ARM64 + Kernel
Click to expand...
Click to collapse
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
XDrz said:
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
Click to expand...
Click to collapse
Official nethunter requires android 10, last official oxygenOs is android 9 but the only available lineageOs for op3t is 18.1 on android 11. Probably Im doing something wrong but I still couldn't make wifi adapter work
XDrz said:
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
Click to expand...
Click to collapse
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
lemongrass1717 said:
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
Click to expand...
Click to collapse
KernelSu is a new root solution for android kernel, there shows some docs about kernel source compilation and module integration. I've tried several times, not so hard but so messy，lots of trivial details(such as adding lost source, changing argvs for compiler.....) you should search for solutions and solve.
Building Kernels | Android Open Source Project
source.android.com
How to build KernelSU? | KernelSU
A kernel-based root solution for Android GKI devices.
kernelsu.org
lemongrass1717 said:
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
Click to expand...
Click to collapse
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
yesimxev said:
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
Click to expand...
Click to collapse
Followed you guide:
1. Downloaded kernel source
2. Patched it with https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch
3. Getting Error on compile
I also tried to add this drivers manualy to kernel https://github.com/aircrack-ng/rtl8188eus and run compile. Seems it compiled OK but on TWRP I get Unsupported Device Error
yesimxev said:
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
Click to expand...
Click to collapse
Nevermind. I fixed it and re-compiled the kernel. Seems it fixed problem with adapter visiibility. Thanks again for the awesome guide.
lemongrass1717 said:
Nevermind. I fixed it and re-compiled the kernel. Seems it fixed problem with adapter visiibility. Thanks again for the awesome guide.
Click to expand...
Click to collapse
Awesome! I mean if you want to use the same kernel, and just adding some patches, clone the already existing NH kernel source. Nice
I've switched to a GSI, and I have been using GCam just because I liked how the UI and app icon looked. I didn't really like it, doesn't work well, slow, and the photo quality is mediocre while the file sizes were outrageous. I just want to go back to the stock camera on OneUI, without going back to OneUI. It worked well and the photos looked good. Where can I get the APK for it? And would it work just by installing it normally? Also I'm not sure if it's allowed but sharing the file here would also be nice.
I did have the same experience. However the ONEUI APK didn't work on the GSI and gcam also had issues. There seems to be something wrong with the frame buffer.
I am using the stock One Ui 4.1 with Google Camera and photos are really better with Google Cam. I'm using "Shamim's SGCAM_8.4.400.42...V35" from https://www.celsoazevedo.com/files/android/google-camera/dev-shamim/. I've configured a bit the options and pictures are really better than the stock cam. However, I think using the Samsung Camera on GSI is impossible because it uses some closed-source code which is only on the One UI.
Thanks for the answers. I've just been using Open Camera and it's exactly what I need, not sure why I didn't switch sooner.
Can I ask which GSI you’re using?
Hello,
I also use Open Camera on my phones, no bugs, many options and compatibility with all manufacturers
fede2782 said:
Can I ask which GSI you’re using?
Click to expand...
Click to collapse
GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
Script and patches for building PHH-Treble Pixel Experience - GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
github.com
I've another question, are you using the latest version (415) or 414. And have you flashed the VBmeta disabler? Thanks for your time
fede2782 said:
I've another question, are you using the latest version (415) or 414. And have you flashed the VBmeta disabler? Thanks for your time
Click to expand...
Click to collapse
I'm using the Android 13 build (20220929), I kinda regret upgrading from 12 tbh. Yes, I used the VBMeta disabler.
Sorry for the late reply, I'm really busy and don't have as much free time as I used to.
Platypus Enthusiast said:
GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
Script and patches for building PHH-Treble Pixel Experience - GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
github.com
Click to expand...
Click to collapse
Does it work without root? And does disabling VBMeta make phone status custom? Because I still want to get update from Samsung.