Related
Hi all,
i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me?
I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do
some nice things
I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2
### EDIT
As long as no one has found to help, here a short description of current progress:
- Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio)
- Device is bootable (no other boot.img required anymore)
- Bootanimation is working
- Mount of partitions is working
- Deodexing is working
- adb, debuggerd and root access is working
Not working: a lot
- Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM)
- Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver)
- Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs)
- USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process)
- RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony)
Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting
Sent from my GT-I9300 using xda premium
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
hop3l3ss1990 said:
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
Click to expand...
Click to collapse
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
andy572 said:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
Click to expand...
Click to collapse
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?
I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it
Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool
Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom
PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.
They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.
Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
slaphead20 said:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
Click to expand...
Click to collapse
Thank you, it would be nice if you can contact him
andy572 said:
Thank you, it would be nice if you can contact him
Click to expand...
Click to collapse
Ok, will mention it to him
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Good Luck Dude~
I haven't tried AOSP yet.
Hope someday i can give it a go.:silly:
hop3l3ss1990 said:
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Click to expand...
Click to collapse
current state:
- patched android/build so we can compile the kernel within the main compile process
- patched android/build main.mk file so we can use OpenJDK or Oracle JDK
- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)
- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP
- modified android/frameworks/native/include so a OMX Plugin header can be found
- modified android/libhardware and patched gralloc module
currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem
to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like
a bug in android/build too.
For only 2 days trying to compile to the end without errors its a very good cut
here we go: it compiles to the end and a flashable "JOP40" zip could be created
tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.
do we need a new or patched kernel instead the CM10 smdk421x one?
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
b-eock said:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor
is red blinking (the one to the right of the speaker.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
Sent from my GT-I9300 using xda premium
I know it's not as simple as it looks, otherwise everybody could do it, but at least can someone point me in a vague direction?
Just out of interest, how do you upgrade a device tree to support newer Android versions? Anything in particular which might prevent Android from functioning correctly?
I've acknowledged SELinux as a problem already.
I'm new to running device trees and kernels but I do know my way around Linux (I know how toolchains works, and I can build Android and kernels, for example) and I know C++, C and Java.
I've 'Google-d' the matter, but to no avail – there appears no clear way to do it.
+1 this question
i want its answer too:good:
I have the idea for an unified build from quite some time, but only now I'm trying to bring it to life.
Looking at LineageOS github and gerrit you can see that other devices (klte, m8) have the same stupid amount of variants, but they have merged them into one device repo.. So why can't this happen for the Note4?
Following their steps I've created an unified android_device_samsung_trlte (that includes SM-N910F/trltexx, SM-N910G/trltedt, SM-N910T/trltetmo, SM-N910W8/trltecan, SM-N910P/trltespr, SM-N910R4/trlteusc and SM-N910V/trltevzw), this proprietary_vendor_samsung and added this commit to the android_device_samsung_trlte-common that I'm currently using.
For now I'm able to use those repos to build a LineageOS-14.1 build that boots up, but w/o sim and camera being recognized.. For what I've tested (on trltexx) wifi and (strangely) bluetooth are working. Something is probably wrong with specific device blobs not being recognized/used properly.
It needs some work but I think this is a good base to start with.
trltexx/trltedt blobs are from here;
trltetmo/trltecan blobs are from here;
trltespr/trlteusc blobs are from here;
trltevzw is using trltespr blobs for now (there are no guaranteed working blobs repos for it at the moment, the only (WIP) way is to establish which are needed and extract them from hsbadr's builds).
The kernel is the same that I'm using for the not unified builds (android_kernel_samsung_trlte), at the moment testing if the klte's way of using the international variant defconfig works for us too.. other options are to add something like this commit to remove the need of a variant defconfig or merge the different defconfigs into one and use that instead.
Source:
unified_android_device_samsung_trlte
unified_android_device_samsung_trlte-common
unified_proprietary_vendor_samsung
android_kernel_samsung_trlte
I was going to share this anyway, but I'm sharing it now (even if there are still major problems) because I have a very limited free time where I can work on it, so, maybe, someone of you will join/fork/clone this project and help me out, finalizing it earlier and better (the support of experienced developers is needed and much appreciated).
I'm now going to mention the SeniorMembers/RecognizedContributors/RecognizedDevelopers that, maybe, have interest in this project.
@fattire @hsbadr @SaintZ93 @SferaDev @TheBr0ken @ZION959
If you get it to work, @_mone, I'll switch my daily builds to this unified one.
On a related matter, there seems to be a typo in the name of one of your repos: unified_andorid_device_samsung_trlte.
Let me also add @lilferraro to the list of devs, as I use his device tree to build for trltespr.
I built this and it boots, with the same issues you have (no SIM detected, camera is busted). Took a bunch of of logs. Getprop shows ro.build.fingerprint is trltetmo (which is right), ro.bootimage.build.fingerprint is trlte. Wifi and bluetooth are working. Mediaserver/libcameraservice service crashes repeatedly. I agree with you that having a unified tree for the entire Note 4 line is the way to go. I tried manually copying the blobs from /system/blobs/tmo/ to /system/lib and /system/vendor/lib but it didn't help.
what proprietary blobs did you use for sprint?
All device trees for the note 4 pie builds are up at
GitHub.com/tripLr-dev
User forum at Telegram
https://t.me/triplr_dev_users
Thanks to @_mone
And @ripee
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
tigerpro357 said:
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
Click to expand...
Click to collapse
Let us know what you need
Source code
GitHub.com/triplr-dev
Contact me on telegram t.me/telegram to get you in touch with testers and developers. .
I am EXTREMELY interested in a touch port.
Thanks
Also GitHub.com/underscoremone for all the older stuff
I actually have my work on github already, I am also on telegram in the ubports groups, and if you would like to help my repo is probably the best place to start (unless you prefer duplicating work) I only have sensors and the stylus left for hardware (both of which I have been trying to get working) the stylus is an issue on the ubports side but I dont understand the code enough for mir. I haven't had a chance to test the unified repo yet, but I will once I have a few minutes to actually do it.
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
tripLr said:
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
Click to expand...
Click to collapse
I agree, as all I really see on xda as far as Ubuntu Touch goes is prebuilt downloads which is good for letting people try it, but when I started I initially looked into xda but found no help. I do hope to see that change in the future though
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
doubledragon5 said:
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
Click to expand...
Click to collapse
Same here
We have several developers for note 4 snapdragon and exynos
T.me/triplr_dev_users
See you there
Roms
Tiny.cc/triplr
Tiny.cc/ripee
And many links in XDA for ROM threads
Post comments in XDA, and bug reports and logs in telegram
Android 10 in progress
Thanks @_mone
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
Is there a custom kernel patched for Nethunter available for the v30?
A moderate browsing suggests that there isn't one already available. How difficult would it be to do this on my own? Im decent on a command line, I've got the time to teach myself how it is done, and Im not too afraid of borking my phone.
Are there guides, kitchens, or the like for doing this? Is there anyone who can point me in the right direction, and doesn't mind the occasional question or two (I don't really want someone to do it for me- I'd like to learn a skill I can use in the future as well)?
Thanks.
This is leading nowhere
First you guys asking for kali nethunter "custom kernel" need to clarify what Nethunter even is (the differences from e.g. a LineageOS 15.1 or dot os 2.6 Android Oreo custom ROM build) and what it would require to get it running in the V30
Also: why changes or features are needed from the kernel side
otherwise it's like turning in circles and the dog chasing its tail ...
zacharias.maladroit said:
This is leading nowhere
First you guys asking for kali nethunter "custom kernel" need to clarify what Nethunter even is (the differences from e.g. a LineageOS 15.1 or dot os 2.6 Android Oreo custom ROM build) and what it would require to get it running in the V30
Also: why changes or features are needed from the kernel side
otherwise it's like turning in circles and the dog chasing its tail ...
Click to expand...
Click to collapse
being flippant certainly will get you the answers you are looking for.
furthermore your reading ability is a bit sub-par, to be honest. I asked for a couple pointers on how to begin going about patching a kernel, myself.. Just pointers, or someone willing to let me bounce a couple questions off them. Being a **** is pointless here. I literally cannot tell you what is needed to get it up and running. Im starting at square one, chief.
Nethunter is Linux that runs in a chroot on top of android. It'll run as-is with a unmodified kernel, but to be able to put an external wifi adapter into monitor mode, you need a kernel patched to allow this.
If you don't have something constructive to offer, maybe next time g-g-go kick rocks dude. It takes soooo much *less* time to just not respond, than it does to fire off some half-assed reply because your reading context sucks eggs.
elijah420 said:
[snip]
Nethunter is Linux that runs in a chroot on top of android. It'll run as-is with a unmodified kernel, but to be able to put an external wifi adapter into monitor mode, you need a kernel patched to allow this.
[snap]
Click to expand...
Click to collapse
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
zacharias.maladroit said:
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
Click to expand...
Click to collapse
no problem. I understand. tone doesn't carry well via text sometimes, so things can get muddled.
I have a couple wifi adapters that support monitor mode. One uses the ath9k driver, and the other uses the rtl8812 driver. I had intended to use one of them (I use them currently with Kali in vbox on my desktop/laptop, so they are known good/working), whichever works best. one is a 11ac, the other 11n.
Does the stock kernel need recompiling with built in support for the wifi adapter/s? Is this the desired end result- a recompiled kernel with support for my particular wifi adapter?
Im going thru the links you posted, currently.
zacharias.maladroit said:
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
Click to expand...
Click to collapse
Im willing to learn how to do this, first. Are there some decent up to date guides that I can follow? Is there a subforum here for this, that I can follow/subscribe to for this?
elijah420 said:
no problem. I understand. tone doesn't carry well via text sometimes, so things can get muddled.
I have a couple wifi adapters that support monitor mode. One uses the ath9k driver, and the other uses the rtl8812 driver. I had intended to use one of them (I use them currently with Kali in vbox on my desktop/laptop, so they are known good/working), whichever works best. one is a 11ac, the other 11n.
Does the stock kernel need recompiling with built in support for the wifi adapter/s? Is this the desired end result- a recompiled kernel with support for my particular wifi adapter?
Im going thru the links you posted, currently.
Click to expand...
Click to collapse
thanks for understanding, agreed - solely text can be pretty prone for misunderstandings
yeah, that's the gist of it
however from the looks of it e.g. SYSVIPC is deprecated and not sure if relay fs (config_relay) is really needed, also options below CONFIG_QCA_CLD_WLAN probably don't need changes at all (might break the wifi of the phone itself)
also CONFIG_USB_G_ANDROID isn't selected in the new config and the f_hid.o and usb_f_hid.o might clash/broken with the patched up state without that config entry being selected
besides that the other config changes might be okay ( OP5_elementalx_kali_defconfig.diff )
elijah420 said:
Im willing to learn how to do this, first. Are there some decent up to date guides that I can follow? Is there a subforum here for this, that I can follow/subscribe to for this?
Click to expand...
Click to collapse
dotfiles that include needed mkbootimg and unpack_bootimg
copy over to ~/bin/
build_lunar.sh
lines out the steps to build a kernel as standalone
Sample steps for lineageos:
https://wiki.lineageos.org/devices/cheeseburger/build
steps are valid until "Download the source code" (including repo sync)
needed git repos for "joan" (V30) have lge in their name:
https://github.com/SGCMarkus?tab=repositories
mostly up to "Updated on May 27" (from the top = newest)
the repos below shouldn't be needed
Those need to be added to .repo/local/manifest.xml (or so, hope that is correct path & file name)
in xml syntax
XDA Y U NO MERGE POSTS ?
edit:
steps for current LineageOS 16.0 related source are:
Code:
export USE_CCACHE=1
export CACHE_DIR=~/.ccache
export KBUILD_BUILD_USER=zacharias.maladroit
export KBUILD_BUILD_HOST=BuildHost
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
export PATH=~/android/toolchains/gcc-arm-8.2-2018.08-x86_64-aarch64-linux-gnu/bin/:$PATH
fakeroot make lineageos_h930_defconfig
fakeroot make -j8
Code:
mkbootimg --kernel arch/arm64/boot/Image.gz-dtb --ramdisk ~/android/final_files/ramdisks_V30_8.0/boot_lineage-16.0_20181118_h930_unpack_b/ramdisk --second /dev/null --cmdline "androidboot.hardware=joan user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 rcupdate.rcu_expedited=1 swiotlb=2048 androidboot.configfs=true androidboot.usbcontroller=a800000.dwc3 androidboot.selinux=permissive buildvariant=userdebug" --base 0x00000000 --kernel_offset 0x00008000 --ramdisk_offset 0x02200000 --second_offset 0x00f00000 --os_version 9.0.0 --os_patch_level 2018-11 --tags_offset 0x00000100 --board "" --pagesize 4096 --out ~/android/final_files/ramdisks_V30_8.0/test/H930_lineageOS-16.0_18.11.2018/boot
ramdisk from "stock" (LineageOS default) kernel was extracted via unpack_bootimg , mkbootimg is used to re-assemble the kernel
both are from dotfiles: https://github.com/luca020400/dotfiles/tree/master/bin
zacharias.maladroit said:
dotfiles that include needed mkbootimg and unpack_bootimg
copy over to ~/bin/
build_lunar.sh
lines out the steps to build a kernel as standalone
Sample steps for lineageos:
https://wiki.lineageos.org/devices/cheeseburger/build
steps are valid until "Download the source code" (including repo sync)
needed git repos for "joan" (V30) have lge in their name:
https://github.com/SGCMarkus?tab=repositories
mostly up to "Updated on May 27" (from the top = newest)
the repos below shouldn't be needed
Click to expand...
Click to collapse
thanks for the starting place. I've got plenty to chew on now for the time being.
elijah420 said:
being flippant certainly will get you the answers you are looking for.
furthermore your reading ability is a bit sub-par, to be honest. I asked for a couple pointers on how to begin going about patching a kernel, myself.. Just pointers, or someone willing to let me bounce a couple questions off them. Being a **** is pointless here. I literally cannot tell you what is needed to get it up and running. Im starting at square one, chief.
Click to expand...
Click to collapse
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
ChazzMatt said:
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
Click to expand...
Click to collapse
idk, that's a bit extreme
XDA is/was made for developers and thus it's supposed to be fun (if you remember the previous threads where devs were scared off by people with a salient arrogant attitude)
however in this discussion it just seemed that we both might have taken things a bit too personal - so it's fine.
Also - I might not be the only custom kernel dev anymore - jollaman999 is working on a great custom kernel (each custom kernel is unique with its own goals)
not sure if he's ready to release it already though or if it's for personal use.
There are also other devs or users working on the V30 which might not have released their stuff (or are not willing to release it [again] for whatever reason - such as tattedup, etc. )
zacharias.maladroit said:
idk, that's a bit extreme
XDA is/was made for developers and thus it's supposed to be fun (if you remember the previous threads where devs were scared off by people with a salient arrogant attitude)
however in this discussion it just seemed that we both might have taken things a bit too personal - so it's fine.
Also - I might not be the only custom kernel dev anymore - jollaman999 is working on a great custom kernel (each custom kernel is unique with its own goals)
not sure if he's ready to release it already though or if it's for personal use.
There are also other devs or users working on the V30 which might not have released their stuff (or are not willing to release it [again] for whatever reason - such as tattedup, etc. )
Click to expand...
Click to collapse
Well, I wasn't saying you were arrogant. I was saying even if you seemed that way (you didn't seem that way to me, you seemed to be asking legitimate questions about how much detailed information he could handle), still why would he call the person names like "****" or other offenses -- who just might be extremely important resource?
It's all straightened out now, I was reading from beginning of thread.
ChazzMatt said:
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
Click to expand...
Click to collapse
I understand *exactly* who I was conversing with. I also understand the questions I asked. He/she can certainly be as flippant as they want. It's within their rights to be. Likewise, I can tell him/her to pound sand. To be perfectly blunt, it doesn't bother me.
He is a great dev. I've used his stuff on my v20. Doesn't change the fact that he made some incorrect assumptions and acted on them. Dont attempt to chide me for someone else's goof. It's not correct, and you aren't contributing anything relevant to the actual question. Besides, it was obviously put to bed well before you decided you have to chuck in your two pennies.
elijah420 said:
Besides, it was obviously put to bed well before you decided you have to chuck in your two pennies.
Click to expand...
Click to collapse
As I've said at least twice. So you're not adding anything either. Or you can't read.
Sent via open market LG US998 V30/V30+
zacharias.maladroit said:
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
Click to expand...
Click to collapse
The last two including
"sched/core: Allow __sched_setscheduler() in interrupts when PI is not..."?
I've never built a kernel but I'd like to have the option of mobile pentesting. If you find yourself with the time and inclination I'd be interested. I'm still learning Java, struggling with recursion, so custom kernels is probably out of my reach.
tooandrew said:
The last two including
"sched/core: Allow __sched_setscheduler() in interrupts when PI is not..."?
I've never built a kernel but I'd like to have the option of mobile pentesting. If you find yourself with the time and inclination I'd be interested. I'm still learning Java, struggling with recursion, so custom kernels is probably out of my reach.
Click to expand...
Click to collapse
nope - I moved the commits to a dedicated branch:
pie_I_6_WIP9_11_kali
so it's
HID patch
Wireless packet injection & selinux patch
the related wifi drivers from the kernel diff need to selected though - since specific wireless adapters are needed which support packet injection functionality