Related
Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.
I have been building a custom LineageOS 14.1 for a few Moto phones (G4, G4 Play, G5 Plus) with the intention of including the MicroG Project to replace Google Play Services. So far, I have successfully built this ROM the for G4/G4 Play, using the patches on github: ( microg/android_packages_apps_GmsCore/tree/master/patches - sorry, can't post links with my account yet ) to integrate seamlessly into the system. However, when I build for the G5 Plus, MicroG is not registering the location services properly to the system. ("Your system does not support this UnifiedNlp package")
I am building with the latest boulzordev sources on github for the device tree, kernel and vendor blobs.
(Thanks @vache, @fAIyaZ, @SJR (Sam), @Alberto97, @Mandy $ingh and everyone else for all your hard work on this device!)
I'm completely stumped as to why this device would be having issues with MicroG. Any ideas out there?
elisam98 said:
I have been building a custom LineageOS 14.1 for a few Moto phones (G4, G4 Play, G5 Plus) with the intention of including the MicroG Project to replace Google Play Services. So far, I have successfully built this ROM the for G4/G4 Play, using the patches on github: ( microg/android_packages_apps_GmsCore/tree/master/patches - sorry, can't post links with my account yet ) to integrate seamlessly into the system. However, when I build for the G5 Plus, MicroG is not registering the location services properly to the system. ("Your system does not support this UnifiedNlp package")
I am building with the latest boulzordev sources on github for the device tree, kernel and vendor blobs.
(Thanks @vache, @Faiyaz,@SJR (Sam), @Alberto97, @mandy $ingh and everyone else for all your hard work on this device!)
I'm completely stumped as to why this device would be having issues with MicroG. Any ideas out there?
Click to expand...
Click to collapse
That's interesting, personally I have not used MicroG so not sure where to direct you to for help. You could try taking a logcat and posting it so that other devs could check it out and try and help you! Good luck mate!
Sam
Great news! I finally figured it out - based on issue #55 in microg's Github repos - https://github.com/microg/android_packages_apps_UnifiedNlp/issues/55
I'll post my resolution here for reference.
The basic issue was that in the overlay included in the device tree, there is a config that is blocking network location services from working:
In the file device/motorola/potter/overlay/frameworks/base/core/res/res/values/config.xml, starting on line 204, I removed the following code
Code:
<!-- Enable overlay for all location components. -->
<bool name="config_enableNetworkLocationOverlay" translatable="false">false</bool>
<string name="config_networkLocationProviderPackageName" translatable="false">com.qualcomm.location</string>
<bool name="config_enableFusedLocationOverlay" translatable="false">false</bool>
<string name="config_fusedLocationProviderPackageName" translatable="false">com.qualcomm.location</string>
The build compiled smoothly and my issue was gone.
Was this included in the code intentionally, @vache, @SJR (Sam), @Mandy $ingh or @Alberto97?
elisam98 said:
Great news! I finally figured it out - based on issue #55 in microg's Github repos - https://github.com/microg/android_packages_apps_UnifiedNlp/issues/55
I'll post my resolution here for reference.
The basic issue was that in the overlay included in the device tree, there is a config that is blocking network location services from working:
In the file device/motorola/potter/overlay/frameworks/base/core/res/res/values/config.xml, starting on line 204, I removed the following code
The build compiled smoothly and my issue was gone.
Was this included in the code intentionally, @vache, @SJR (Sam), @mandy $ingh or @Alberto97?
Click to expand...
Click to collapse
I'll let the others speak, but it was probably setup just for Lineage to build. You got it working though! Good on you mate!
I'm using @SJR (Sam) LineageOS 14.1 builds and I'm very interested to use the MicroG GPS/Map Services (UnifiedNlp, LocalGsmNlpBackend) but was not able to activate them by installing from F-Droid repositories. So I think either a ZIP install or modified LineageOS 14.1 is needed. @elisam98 could you may help by sharing with the userbase?
Hello there!
I tried to use MicroG (and NanoMod) with AOSP Extended and Validus, both 8.1. It looks like qualcomm location service is preventing nlp from work So I would like to ask: is it any way to fix this issue without recompiling all the system? Or, maybe, anyone here have made builds with this issue fixed?
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in it
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
What is Project Treble
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition.
About
Weijianism did not build any verdor image of new version because he does not own this device. Although I am not familiar with android source and android build, I am very happy to learn it so that we natrium owners can use project treble.
So I message to Weijianism to know how to do it and have learnt it for a few weeks. Now I am trying to build vendors. Cause I still know a few about it, It is really very hard for me to solve problems in myself. So if you have any advice, please tell me or push you code in github. THANK YOU!
What is NOT WORKING
Camera
Let's test it together.
Download
ALPHA 0815 (boot.img + vendor.img)
How to
1. wipe everything using TWRP
2. flash boot.img + vendor.img
3. flash system.img
4. reboot to system
Sources
Kernel for msm8996 (lineage-15.1)
Configuration for natrium (lineage-15.1)
Configuration for msm8996 (lineage-15.1) (Minor patches)
Proprietary vendor (lineage-15.1) (Minor patches, forked from Weijianism , credits MZO)
XDA: DevDB Information
Project Treble for Mi 5s Plus
Contributors
Justin_hill
Weijianism
Thanks to
LineageOS
Mi 5s Plus devs
@Weijianism
ROM OS Version: 8.x Oreo
Rom Kernel: Linux 3.x
Version Information
Status: Testing
Created: 2018-08-13
Last Updated: 2018-08-16
Anyone try ?
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
1. bootloop problem solved when using rr gsi. (code from hacker1024)
2. bluetooth service stoped problem solved.
QuiseShampe said:
Well, Bluetooth & Camera won't work on any gsi. Bluetooth service has been stopped. Can't connect to camera.
:c
Click to expand...
Click to collapse
The camera's problem seems very hard, I will try to use GCam later. Now I do have no idea about how to solve it.
You may help me solve it if you like!
pote2639 said:
Bluetooth working, but wifi is always dropping. did you take the drivers from los? also very laggy compared to old treble.
Click to expand...
Click to collapse
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
justin_hill said:
Yes, I used code and drivers from los totally.
And I really don't know what happened on your device cause you didn't tell me any useful information (such as what gsi and which version). I only find this kind of problem when using gsi of Android P Developer Preview.
Click to expand...
Click to collapse
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
pote2639 said:
I used this version sgsi ones. Build PR1.
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Click to expand...
Click to collapse
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
justin_hill said:
emm, maybe you should not use version of developer preview there is an experimental build of Android pie.
And I am so sorry that I would not like to spend time on version of developer preview.
Click to expand...
Click to collapse
I guess I'll wait for android p stable sgsi build then.
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
rhp_engcoy said:
Good day sir!
Is there any chance that this rom will be available to Mi 5s (Capricorn) soon?
Click to expand...
Click to collapse
Hope for me get a new natrium and I'll do for capricorn and natrium too.
Ofc, as justin did for natrium already, I'm gonna just ship it on my custom ROMs projects, not separated things like capricorn should get it too.
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
theOriginalSuperl2 said:
@justin_hill
This is interesting, thanks for taking this up!
I'd like to mention that my last RR build has more recent vendor files than @Weijianism's treble builds.
I'm not sure why bluetooth only works with an RR GSI... That's weird. We need logs, of course.
I've never ported Project Treble to a device before, but I'm happy to help.
With the camera - I think this old branch of the kernel may work. I have no idea why, though.
P.S. I'm hacker1024 on GitHub.
Click to expand...
Click to collapse
Yeah, your code have inspired me a lot when I saw your repositories.
Maybe I fixed the bluetooth problem when I add back the libbtnv.so to /vendor/lib/ since it was deleted in this commit.
For the camera problem, I don't know how vendor module relates to kernel. But I will try it afterwards.
Actually I almost know nothing about lineage source code, system build skills and things like this. If you can help, it will be grateful!
any news on the development?
Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
About treble support I can tell that I'm gonna include in my ROMs, and maybe I'll give some vendor zips too, if @justin_hill doesn't care about that.
Crescendo Xenomorph said:
any news on the development?
Click to expand...
Click to collapse
Sorry, I am trying to do something about Treble for Android Pie, But there are still several problems unsolved. Cause I'm not familiar with those code, so maybe I can't solve it by myself. It will be so grateful if anyone can contribute to it.
So we will expect @Hlcpereira WORK, Thank you so much!
Hey, is the camera problem solved?
It can't be booting on any sgsi so what should i
do
Coconut Kernel
Just a fancy name. Don't bother...
Please read the last post for pie kernel update.
Code:
***I'm not responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
This kernel is only for stock Oxygen OS Oreo 5.x.x or any rom that supports stock kernel
This kernel was made for my own use as i could not find any working kernel with USB Wifi Adapter drivers supporting packet injection and monitor mode or simply Nethunter support.
I've been using ZaneZam's kernel for my nougat OOS. Since the Oreo version wasn't working for whatever reason, i tried to compile one my own.
My sole intention was to create a kernel with USB Wifi drivers and monitor mode/packet injection working. So this kernel doesn't have all those tweaks/options like other great kernels.
People who want upstreamed kernel with nethunter, drivedroid, android auto and stock features working can use this kernel on OOS Oreo.
Kernel has been upstreamed to 3.18.134(current)
Whats working?
- Stock features
- DriveDroid(CDROM Patch)
- USB Wifi adapters with monitor mode/packet injection
- AndroidAuto
Tested Working Wifi Adapters
1. TP Link WN-722N v1 (ath9271 chipset) - all ath9271 chipset should work
2. Alfa card AWUS036NHA (Atheros ath9271 Chipset)
3. Alfa card AWUS036NH (Ralink RT3070 Chipset)
Untested adapters
All adapters on nethunter support page have been added but not tested.
Installation
Download from attachment and flash the kernel zip file from recovery.
It is recommended to flash stock boot.img before flashing the zip.
Using USB Wifi Adapters
1. Reboot the device after flashing the zip
2. Goto Settings-->Advanced and turn on OTG Storage
3. Plugin your USB Wifi card and type ifconfig wlan1 up to test.
Keep in mind that OTG Storage turns off automatically after 10 mins on idle.
You don't need to insmod any modules as all drivers are built inline with the kernel.
Credits
Google
@ZaneZam for his support
Anykernel author
My friend @OscarAkaElvis (author of the great airgeddon tool to audit wireless networks), who tested the beta versions for me.
@nathanchance for his kernel compile and upstream guide
@flar2 for his source that i used to learn compiling at first
All others whose commits i've used
Source
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996
https://github.com/android-linux-stable/op3
Additional Note - I would like to mention that you can use tools like LinuxDeploy or other chroot supporting apps and the wifi adapters will work fine just like nethunter.
If you guys prefer ZaneZam's version, you can flash my kernel and then flash his kernel for oreo. Then everything will work on his kernel too. There is a small fix needed which will be applied on flashing my kernel.
Hi, I worked as beta tester for this kernel compilation and I must say is the best kernel ever for Oneplus3 I tried (in my opinion). All the standard functions are working flawlessly (wifi, camera, flashlight, etc...). No errors, no glitches. Gestures are working in order to enable camera or flashlight.
I tested the kernel also using Kali Nethunter, it works like a charm. I also installed a Linux using Linux Deploy app on which everything also was working fine.
Android Auto is fully working. Tested plugging it into real car (not emulators). Drive Droid is also working allowing to mount the drives without any problem. This is a feature that many custom kernels are not bearing in mind but for some people is an important stuff to be working. I use it every day.
And regarding the external usb cards. Yes, I tested it using a OTG (On-The-Go) cable. I can confirm that these two chipsets are working. In my case it was not a TP-Link card for Atheros chipset. I tested it using AWUS036NHA (Atheros ath9271 Chipset) Alfa wireless card and it worked very well supporting monitor mode, etc. I also tested it with another Alfa card AWUS036NH (Ralink RT3070 Chipset) and it worked fine too.
So congratz to de creator. This last month was a hard work. Good job. All the Oneplus3 users (like me) will be very grateful to you because of this.
Bro can you compile kernel for los based custom roms pie and oreo plz with nethunter support?,
ayanroy said:
Bro can you compile kernel for los based custom roms pie and oreo plz with nethunter support?,
Click to expand...
Click to collapse
I think ZaneZam has already done that. He builds for stock and lineage os. Did you check?
ayanroy said:
Bro can you compile kernel for los based custom roms pie and oreo plz with nethunter support?,
Click to expand...
Click to collapse
I thought there was a version already available for LOS oreo.
Since i was wrong, i compiled one. You can find it in the following thread.
https://forum.xda-developers.com/on...nel-coconut-kernel-lineage-15-1-oreo-t3902479
Pie version - maybe later
fredrickz said:
I thought there was a version already available for LOS oreo.
Since i was wrong, i compiled one. You can find it in the following thread.
https://forum.xda-developers.com/on...nel-coconut-kernel-lineage-15-1-oreo-t3902479
Pie version - maybe later
Click to expand...
Click to collapse
Thanks alot bro, will be waiting for your pie version
ayanroy said:
Thanks alot bro, will be waiting for your pie version
Click to expand...
Click to collapse
Did you check the oreo version? Or are you just waiting for the pie release?
For those who had this working can post here as a feedback.
very nice job! My TP-LINK WN722N is working just fine with nethunter!
Do you think it would be possible to add HID support to this kernel? To be able to execute HID/Bad USB attacks, that would be super cool!
hokyjack said:
very nice job! My TP-LINK WN722N is working just fine with nethunter!
Do you think it would be possible to add HID support to this kernel? To be able to execute HID/Bad USB attacks, that would be super cool!
Click to expand...
Click to collapse
I'll add that in the next version
I can confirm working monitor mode & injection on my Oneplus3 OOS Oreo with TP Link WN-722N v1 (ath9271 chipset). Nice work @fredrickz !
Limitscrw said:
I can confirm working monitor mode & injection on my Oneplus3 OOS Oreo with TP Link WN-722N v1 (ath9271 chipset). Nice work @fredrickz !
Click to expand...
Click to collapse
Can you suggest me a guide to install kalinethunter? i'm using magisk as root thx
scorpion90 said:
Can you suggest me a guide to install kalinethunter? i'm using magisk as root thx
Click to expand...
Click to collapse
u maybe can try to use one of my provided nethunter packs from here: https://www.androidfilehost.com/?w=files&flid=151160
which where done with this: https://github.com/zanezam/kali-nethunter and which has a little troubleshoot section in Readme at the end
for starting
Excellent kernel. Super performance and good battery life. I hope you make one for oxygen OS stock pie when it releases.
Didn't have one problem, aside from the horrendous Mtp-procedure install on this device(just got a Op3 recently).
Runs smooth, don't drain the battery like many Nethunter kernel from official side.
I hope this will expand in more then just a one-days development, because we need more of user who are beginning to programm etc.
I appreciate your effort and wanted to state that this kernel works without one single flaw whatsoever.. :silly:
UsPdSr said:
Didn't have one problem, aside from the horrendous Mtp-procedure install on this device(just got a Op3 recently).
Runs smooth, don't drain the battery like many Nethunter kernel from official side.
I hope this will expand in more then just a one-days development, because we need more of user wgo are beginning to programm etc.
I appreciate your effort and wanted to state that this kernel works without 1 flaw whatsoever.. :silly:
Click to expand...
Click to collapse
Thanks for the appreciation. Btw, I've already posted a pie version of the kernel with nethunter support built from holydragon sources. But it's not for OOS. It's for AOSP based roms. I'll try to compile a pie version when the official OOS sources are available.
Got my hands on an Alfa AWUS 036 NEH last week, and I am happy to report that monitor and injection are working just fine.
@fredrickz
Will u release one for pie?
metaspook said:
@fredrickz
Will u release one for pie?
Click to expand...
Click to collapse
I can compile from holydragon pie source.
fredrickz said:
I can compile from holydragon pie source.
Click to expand...
Click to collapse
Bro check your inbox...
metaspook said:
Bro check your inbox...
Click to expand...
Click to collapse
Hey i saw the message. But now I'm out of town. I'll message you when i return@metaspook
Build for SM-T800 (chagallwifi) this is a SELinux enforced build, signed with Lineage test keys.
It is untested by me as I don't have this device.
It may boot or it may bootloop - IDK.
lineage-17.1-20230218-UNOFFICIAL-chagallwifi.zip
drive.google.com
Use at your own risk.
Please if you cannot use ADB and provide logcat files of issues - do not use or at least don't complain.
If you cannot use ADB/ODIN to flash back to a working version - do not use.
Backup everything before using.
Use TWRP and wipe before installing.
What works - I don't know.
What doesn't work - I don't know.
Donate me a device and you might get better support
Incorporates latest patches:-
https://review.lineageos.org/c/LineageOS/android_build/+/347094
This build replaces default Lineage camera with Aperture.apk camera application from Lineage-20 ( which saves video on a SM-T805 ).
Kernel source from exynos5420 at
GitHub - exynos5420/android_kernel_samsung_exynos5420
Contribute to exynos5420/android_kernel_samsung_exynos5420 development by creating an account on GitHub.
github.com
Exynos 542X
Android Development for Exynos 5420-Based Devices. Exynos 542X has 63 repositories available. Follow their code on GitHub.
github.com
Thanks, will try it! Does it have encryption working?
Hi, I've tried Your build and tab was unable to boot unfortunately. It got stuck on LineageOs logo and didn't pass that.
zboq said:
Hi, I've tried Your build and tab was unable to boot unfortunately. It got stuck on LineageOs logo and didn't pass that.
Click to expand...
Click to collapse
Its a pity... Have you tried resetting Data partition and flashing without gapps?
porcino said:
Its a pity... Have you tried resetting Data partition and flashing without gapps?
Click to expand...
Click to collapse
Yes, I did factory reset and wipe data just before flashing and after flashing did wipe cache/dalvik. This metod works for LOS 17.1 by 8224Freak from another thread.
zboq said:
Yes, I did factory reset and wipe data just before flashing and after flashing did wipe cache/dalvik. This metod works for LOS 17.1 by 8224Freak from another thread.
Click to expand...
Click to collapse
Thanks. I'll wait with this ROM then.
I'm running good old LOS 14.1 at the moment, selinux, encryption, very responsive Brave, all sorts of car diagnostic software.
bluess57 said:
Build for SM-T800 (chagallwifi) this is a SELinux enforced build, signed with Lineage test keys.
It is untested by me as I don't have this device.
It may boot or it may bootloop - IDK.
lineage-17.1-20230218-UNOFFICIAL-chagallwifi.zip
drive.google.com
Use at your own risk.
Please if you cannot use ADB and provide logcat files of issues - do not use or at least don't complain.
If you cannot use ADB/ODIN to flash back to a working version - do not use.
Backup everything before using.
Use TWRP and wipe before installing.
What works - I don't know.
What doesn't work - I don't know.
Donate me a device and you might get better support
Incorporates latest patches:-
https://review.lineageos.org/c/LineageOS/android_build/+/347094
This build replaces default Lineage camera with Aperture.apk camera application from Lineage-20 ( which saves video on a SM-T805 ).
Kernel source from exynos5420 at
GitHub - exynos5420/android_kernel_samsung_exynos5420
Contribute to exynos5420/android_kernel_samsung_exynos5420 development by creating an account on GitHub.
github.com
Exynos 542X
Android Development for Exynos 5420-Based Devices. Exynos 542X has 63 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
Hi @bluess57, your Lineage 18.1 build for T805 works great on T800, better than 17.
zboq said:
Hi, I've tried Your build and tab was unable to boot unfortunately. It got stuck on LineageOs logo and didn't pass that.
Click to expand...
Click to collapse
Are you prepared to be a tester for me ?
bluess57 said:
Are you prepared to be a tester for me ?
Click to expand...
Click to collapse
Sure, why not. Just to note that It's been a long time since i've been flashing roms and taking logcat so I may need some help with that .
foolone stated that LOS 18.1 works on T800, so maybe it's better to already swtich to that build ?
Thank you @bluess57 for your support, is there any chance to this rom to work on Samsung Galaxy Tab S 8.4” T700?
zboq said:
Sure, why not. Just to note that It's been a long time since i've been flashing roms and taking logcat so I may need some help with that .
foolone stated that LOS 18.1 works on T800, so maybe it's better to already swtich to that build LOS
Click to expand...
Click to collapse
His LOS18.1 is for T805. To install it on T800, you need to unzip the package, find the install script, and take out the first line. (which check for device). See the 18.1 thread.
foolone said:
His LOS18.1 is for T805. To install it on T800, you need to unzip the package, find the install script, and take out the first line. (which check for device). See the 18.1 thread.
Click to expand...
Click to collapse
Thanks, will take a look at that. bluess57 is looking for a beta tester so maybe he will make a build for T800
bluess57 said:
Build for SM-T800 (chagallwifi) this is a SELinux enforced build, signed with Lineage test keys.
It is untested by me as I don't have this device.
It may boot or it may bootloop - IDK.
lineage-17.1-20230218-UNOFFICIAL-chagallwifi.zip
drive.google.com
Use at your own risk.
Please if you cannot use ADB and provide logcat files of issues - do not use or at least don't complain.
If you cannot use ADB/ODIN to flash back to a working version - do not use.
Backup everything before using.
Use TWRP and wipe before installing.
What works - I don't know.
What doesn't work - I don't know.
Donate me a device and you might get better support
Incorporates latest patches:-
https://review.lineageos.org/c/LineageOS/android_build/+/347094
This build replaces default Lineage camera with Aperture.apk camera application from Lineage-20 ( which saves video on a SM-T805 ).
Kernel source from exynos5420 at
GitHub - exynos5420/android_kernel_samsung_exynos5420
Contribute to exynos5420/android_kernel_samsung_exynos5420 development by creating an account on GitHub.
github.com
Exynos 542X
Android Development for Exynos 5420-Based Devices. Exynos 542X has 63 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
LIKED ! I will test immediantly I missed this Build , welcome to Tab T800 World brother Blues !
If anyone wants to try an 18.1 build for chagallwifi SM-T800
I don't know if it will boot/work etc...
use at your own discretion and backup
have twrp recovery ready etc and a working rom to go back to
lineage-18.1-20230312-UNOFFICIAL-chagallwifi.zip
drive.google.com
Hello
I tested ! no boot. stay on logo lineage
thanks
logo111 said:
Hello
I tested ! no boot. stay on logo lineage
thanks
Click to expand...
Click to collapse
Came here to post this. Same thing here. No go, infinite lineage loading logo
I need someone who can obtain a logcat
from this looping image.
Likely you'll need to have installed a working T805 image to turn on developer options and adb debugging, then dirty flash this looping image
Or I'll need to give you people an engineering build to get a logcat
Or I give up on T800
bluess57 said:
I need someone who can obtain a logcat
from this looping image.
Likely you'll need to have installed a working T805 image to turn on developer options and adb debugging, then dirty flash this looping image
Or I'll need to give you people an engineering build to get a logcat
Or I give up on T800
Click to expand...
Click to collapse
I have a working T800 lineage 14.1 image.
But I have absolutely no idea how to do any of this
Give up? Never! lol
Im also interessted in this as well, as I stubled across my good old chagallwifi and would love to use it as a homeAutomation screen with LineageOS 18.1
Boot loop issue tracked down to missing consumer IR library , thankyou @zboq , who provided logcat and quick turnaround testing.
So for chagallwifi this boots:-
lineage-18.1-20230318-UNOFFICIAL-chagallwifi.zip
drive.google.com