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
Related
Found post about VegaComb being released for Adam on TabletRoms.com. Due to the similarities and the fact that there exists ROMs for G-Tab based on Adam. Do we know if there is an effort to port this ROM to G-Tab? Any info would be appreciated as this looks to be THE ROM, with the possibility of fixing camera and hardware acceleration.
A kernel is being worked on ; on the slatedroid forum. The hardware is different so a kernel has to be made for it to work
[email protected]: Posted Today, 09:31 AM
Unfortunately the Vega is not a hardware match for our beloved g-tab, they are very similar however they are not the same hardware exactly, little things like the wireless controller and the camera are different. They also have a different mainboard in their system. I'm pretty sure that the rom that works on theirs is not going to work on ours until we have a working kernel to work from. They have worked very hard on rewriting the drivers to get their tablet to work as well as it is in 3.2 and they don't seem to be slowing down now that it is working. I know that the group that is working on the kernel is working very hard to get it running as quickly as we can, I don't think that most of us have much experience in kernel coding and so it is taking some time to even get it to boot. However I can tell you that we are working diligently to get through the problems and get a kernel out to the community so that we can join the ranks of the Vega in making Google cry by hacking our way to victory. On a side note I want to say how impressed I am by the level of assistance that everyone in this community has for the new members and old members alike. I don't know of another rom that has this level of support from it's users out there. Thanks to all of you that are helping people overcome their issues and enjoy this fantastic rom.
Click to expand...
Click to collapse
.
[email protected] Posted 14 August 2011 - 09:01 PM
Hello all, Ch3vr0n5 here
The GTab Kernel Dev Team would like to chronicle our kernel development process for everyone to enjoy. The Gtablet 2.6.36 kernel project is based on the work done by Eduardo/RaYmAn on the Adam kernel. The biggest thanks goes out to them and anyone else who works on that project because it has made our work possible.
The Dev team is currently: Myself, Icewyng, Mayday_Jay, WayneMasta, Treznorx
[8/25/2011]
We know that we are hanging on init.rc and have a few ideas one how to proceed. Mayday_Jay (Give him and Icewyng a big thank you because they have made this project viable) is working on getting all the developers a proper update.zip that will help those with out a usb to serial converter get some useful debug information.
Don't fret when it takes a couple days for us to update. If you want bleeding edge news, join us on the kernel dev irc channel which is found further on in the thread. We are still working! =)
[8/23/2011]
Linux (BT5) will boot without Touchscreen working. Work is progressing slowly to get this working with Android. Mayday_Jay, with the use of USB -> serial converter has been able to get some useful dmesg output as well as some other debug information that is giving us new ideas on how to proceed.
[8/19/2011]
Starting to modify the adam files to mach the correct values for our device. Our current config gets us passed the birds and to the second boot image and the usb device registers. Trying to get it connected to adb to get some dmesg output.
[8/14/2011]
The resulting kernel did not boot and this is more than likely due to the fact that there are quite a few new config options that need to be set. I have run a diff to find differences between Pershoot's and Rayman's kernel and will be trying a new config either tonight or tomorrow hopefully. Gotta sift through new and deprecated options as well as any they both have but are set differently (and why)
Part 2
The kernel compiled with the additions from rayman's config in pershoots got it past the birds to the "Android 3.0" screen. Tomorrow I will be able to hookup adb and see where it is crashing from there.
[8/15/2011]
Still running through different configurations. Need to ask pershoot what modifications he made to make the .32 kernel boot on the 1.2 bootloader. IE Which files use the NEWBL config option and what the changes are.
[8/16/2011]
I received the source for the Vega kernel from rebel1. I may not update for a few days as I try out different configs and such but I will still be here.
[8/17/2011]
Decided to go with the Adam kernel because of hardware compatibility. Put up the github repo.
GitHub.com Repo
git://github.com/ch3vr0n5/android-tegra-2.6.36-gtablet.git
-----------------------
All thoughts, idea, comments and criticisms are welcome (Please be kind). Just remember, most of us are not programmers or software engineers by trade. I got my degree in network security so I generally play with routers, firewalls and the like and do this as a hobby. If you find anything wrong with what I or any of the Dev team have written please tell me... just don't point and laugh. LOL
Cheers
Click to expand...
Click to collapse
OK, this is beginning to give me the s**ts. Where are all the sources to the stuff that is being posted up here? I have been trying to build (rebuild) some of the ROMS on here, if for no other reason than to check there is no dodgy code in them, but also to learn from what everyone has done.
This is supposed to be a DEVELOPMENT forum, where source code is shared and discussed. Not a bazaar where the posters do a bit of hocus-pocus putting together roms from binaries of unknown source code. They fall like crumbs from the majestic sages, that do even more unknown hocus-pocus and cast them down to the unwashed masses to oooh and aahh at, as they give homage to the great compilers in the sky. What is this? Job security?
I have no idea what the legals are around this and I don't really care. The point is that the spirit of the GPL is you post sources (or patches against standard sources) along with any binaries. The binaries are only there to save us the bother of recompiling. The source is what is important in this forum. How else are others going to improve on the code if they can't see it?
I have posted on a couple of threads and/or contacted various people on here, most of whose response is "oh I didn't compile the actual source code, I just stuck it together from the binaries". One of them (thanks kevinlekiller) was kind enough to at least give me rundown on what he did (as best as he could remember - bit of a worry!), but even he didn't have access to the source code. Maybe I haven't looked in the right place, but it shouldn't be this frigging hard - it should be front and centre.
If I had my way, I would ban every ROM post that didn't have a clear link back to all the sources. That's what github etc is for!
Please, please, people, post the source first, binaries can be an afterthought. If you don't have access to the source code, then I reckon it shouldn't be here - who knows what in there? One of these days someone is going to innocently distribute some nefarious program with a ROM. It really isn't that hard to compile a ROM - takes about half an hour on my Linux laptop.
This is actually standard xda-developers policy: see http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45 but seems to be widely ignored.
OK, I'll get off my soapbox now.
Edit: I realise this doesn't apply to everyone, some people are great about posting sources.
Wrong section buddy
Sent from my GT-S5830 using xda premium
djsky2011 said:
Wrong section buddy
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Huh? You're joking right? I'm discussing the sources not being available in this section, the source is a development topic. Hmm maybe this is such a common complaint that there is a separate section created for it. Sorry I'm getting crabby.
What section should it go in?
You take 30mins , mine takes 2h - it's different for everyone......
Furthermore , if they're basing a ROM off a ROM , what sources are there to be published ?
Furthermore , the sources can already be found online if you want CM7/AOSP:
http://github.com/teamhacksung/android_device_samsung_cooper
Herpderp Defy.
ok man make a rom then talk to us. most of roms here are like this u got new app,launcher and theme voila new rom is posted(no offense).so they cant give you source code.they make roms from the prebuilt ones like using stock or cm7 as base .most of the developers which made roms from source code had there github accounts link in there username ok i agree there are one or two developer who dont share but that dose not mean everyone here is just like them.ok
1.i can make a rom.
2.but i will not make a one unless i compiled it from source code.
3.sure i will share its source code.
i agree a little bit with you
EmoBoiix3 said:
You take 30mins , mine takes 2h - it's different for everyone......
Furthermore , if they're basing a ROM off a ROM , what sources are there to be published ?
Furthermore , the sources can already be found online if you want CM7/AOSP:
http://github.com/teamhacksung/android_device_samsung_cooper
Herpderp Defy.
Click to expand...
Click to collapse
Finally. Thank you! A link to the source code (actually the config files is just what I looking for).
So, since I have your attention, I see a couple of roms from people like vo-1, what is he doing just compiling the source (I have asked him, no reply)?
On the ROMS based on ROMS thing, while there is technically no source code you put through a compiler - there is still source - it is a list of all the changes made to that ROM.
I also can't believe people don't seem to use any sort of build environment - as in a build script - how else are we going to document what's been done and/or recreate it?
xdaboy122 said:
ok man make a rom then talk to us. most of roms here are like this u got new app,launcher and theme voila new rom is posted(no offense).so they cant give you source code.they make roms from the prebuilt ones like using stock or cm7 as base .most of the developers which made roms from source code had there github accounts link in there username ok i agree there are one or two developer who dont share but that dose not mean everyone here is just like them.ok
1.i can make a rom.
2.but i will not make a one unless i compiled it from source code.
3.sure i will share its source code.
i agree a little bit with you
Click to expand...
Click to collapse
Yes I agree this does not apply to everyone. Some people do post source. I suppose my frustration was the source seemed to be forgotten and it shouldn't be so hard to track it down. Maybe I have spent too much time in the Linux world, where source code is king.
I will kick off a make on the source that EmoBoiix3 linked to (thanks mate) and see where we go from there!
A lot of roms here are based off other roms. So much they don't build it themselves, just some editing of the zip.
Other developers merely want to save the technobabble since most xda users are blind to programming.
divereigh said:
Huh? You're joking right? I'm discussing the sources not being available in this section, the source is a development topic. Hmm maybe this is such a common complaint that there is a separate section created for it. Sorry I'm getting crabby.
What section should it go in?
Click to expand...
Click to collapse
still wrong section
this aint a source
this is a discusion so its supposed to be in general section
Should be in general section IMO.
But I fully agree with the OP. It is true lots of ROMs here are "cooked" from other ROMs and are not "developed" denovo. They are "theme" packs.
But for example we have two groups actively working on builds of CM 7.2, they each seem to be building from source and tweaking fixes in. It would really help if everyone used github. Pull a source, build, fix and commit to your fork. Anyone else can see what you changed, what revision of the tree you used, and can learn from your work and it could perhaps inspire them to fix something else, to contribute back to make *your* build better.
Sharing your code, even if it is just 5 line hack on teamhacksung / cyanogenmod /AOSP source, honours the GPL and helps our community grow stronger.
The GalaxyICS team is a great example, I can see where they've pulled their sources, what (hard) work they've done in what components. They are contributing all their work and knowledge back. And their fixes can be pulled into other projects easily, speeding up development and sharing that knowledge for everyone.
A phone like the Ace continually loses developers as they migrate to "better" phones, and we really need to share as much knowledge as possible to keep our software
Sometimes , changes just cannot be shown.....like framework-res tweaks!
Herpderp Defy.
EmoBoiix3 said:
Sometimes , changes just cannot be shown.....like framework-res tweaks!
Click to expand...
Click to collapse
What sort of tweaks are you thinking of? If it's a replaced image file, then that can be a separate file copied in with a script. If it's a changed text file, that can be done with patch or sed.
Let me give you an example of what I did with kevinlekiller's The End 2.5o rom. He based it on a vo-1 rom and did a fair number of replacing files, odexing etc. I produced this bash script (attached) along with his extra (binary) sources which I think replicated what he did. Self documenting! Everyone can see what is in there, maybe even change it again.
More details towards the bottom of this page: http://forum.xda-developers.com/showthread.php?t=1440396&page=31
I see where you are coming from and I sympathize. I'm not a developer, because I don't have the time and patience to work on source code , compile , debug etc.
The Rom's we have for the Galaxy Ace are already very good, the developers that have worked on them have/had the time and patience to iron out most the issues. So for me to try to come out with something better would seem futile.
I still like customizing these Rom's to a way that work better for me, and it doesn't involve having to spend lots of time, because like I said they are already very good. So it just ends up that a few files are added or changed.
Is that a bad thing? I think those that think it is should just not use those types of Rom's, everyone has a right to their opinion.
At first when you asked me for sources, I thought you meant the source code, since I already listed everything that was used in the first post. But then I realized you wanted direct sources (links) to those files. This is something I will do in the future, post the links of every file, I agree with you , things should be more documented, it would save everyone time instead of trial and error and possibly even giving up.
Anyways, I should conclude here, it is getting a long read.
divereigh said:
What sort of tweaks are you thinking of? If it's a replaced image file, then that can be a separate file copied in with a script. If it's a changed text file, that can be done with patch or sed.
Let me give you an example of what I did with kevinlekiller's The End 2.5o rom. He based it on a vo-1 rom and did a fair number of replacing files, odexing etc. I produced this bash script (attached) along with his extra (binary) sources which I think replicated what he did. Self documenting! Everyone can see what is in there, maybe even change it again.
More details towards the bottom of this page: http://forum.xda-developers.com/showthread.php?t=1440396&page=31
Click to expand...
Click to collapse
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
an0nym0us_ said:
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
Click to expand...
Click to collapse
Actually I only have 1 windows pc, all my other PC's are ubuntu / linux mint installed on them. I use windows on the main PC because most of my games work on it.
Edit: And, I didn't take offense to your post , it is valid, most people have no clue about linux.
kevinlekiller said:
Actually I only have 1 windows pc, all my other PC's are ubuntu / linux mint installed on them. I use windows on the main PC because most of my games work on it.
Edit: And, I didn't take offense to your post , it is valid, most people have no clue about linux.
Click to expand...
Click to collapse
and no offence intended and sorry if anyone feels my post abit too offending
my point is a rom created from previous precompiled rom can be created 100% on windows machine.
in that case the rom also doesnt have sourcecode because it were created from already precompiled rom.
so if the modder just give a valid link to what he put/change it still suites the forum rules to provide source.
let say i've modded a cm rom, i've include ketuts oc kernel, i've include a launcher, and a filemanger, and a theme.
so if i just provide a valid link to the original cm rom, a link to ketuts oc kernel thread, a market link to the launcher, the filemanager and the theme, thats a valid source because the rom were modded from binary precompiled rom/kernel/launcher/filemanager/theme.
so the link to those binary precompiled rom/kernel/launcher/filemanager/theme is a valid "source".
divereigh said:
This is supposed to be a DEVELOPMENT forum, where source code is shared and discussed. Not a bazaar where the posters do a bit of hocus-pocus putting together roms from binaries of unknown source code.
Click to expand...
Click to collapse
I agree. There are two groups of devs:
"Real" developers. They provide repo links and detailed changelogs.
Modders. They should provide repo links and detailed changelogs.
A repo has the benefit of allowing peer review. Peer review improves code quality just like user tests and their reports do. Afterall, this is what XDA is about.
What I like about XDA is how people eagerly send in "works" notes. Not much information, but better than just trying out and telling nobody.
Exactly guys......it seems cyanogenmod has become the only alternative and devs here are only editing it and bringing out new firmware versions. Some also edit stock roms..........but no one here gave a thought of creating a new genre of custom rom right from source.
biswatmak said:
Exactly guys......it seems cyanogenmod has become the only alternative and devs here are only editing it and bringing out new firmware versions. Some also edit stock roms..........but no one here gave a thought of creating a new genre of custom rom right from source.
Click to expand...
Click to collapse
its not as easy as it sounds, thats why the two main dogs are miui and cyanogenmod.
an0nym0us_ said:
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
Click to expand...
Click to collapse
I get that. I essentially built an interpreter and a source file (the build instructions). Way too much for most. However I think it would be great as developers if we provided be packaging tools so that others can use them and provide repeatable builds and automatically documented builds ("read the source luke").
an0nym0us_ said:
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
Click to expand...
Click to collapse
Agreed, it isn't mandatory, however for the purposes of educating and peer-review it would be great. So my challenge is to make this easy for people.
an0nym0us_ said:
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
Click to expand...
Click to collapse
So we need a graphical version for Windows..
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte
Hey guys...hoping someone here who is wiser than I can offer some information on how I might complete the task I am after. I've got limited knowledge in the rom-building department, but would really like to learn at least enough to "get my feet wet" so to speak, and so I'm trying hard to do just that. I would like to build a version of SlimKat based on the latest code available, and have it be compatible with our device (the VS985). I've gotten so far as to set up the Ubuntu build environment and everything, installing repo and initializing the directory with the SlimKat 4.4.4 caf (by doing repo init -u git://github.com/SlimRoms/platform_manifest.git -b kk4.4-caf), and finally repo sync'ing the whole thing.
I'm pretty sure that I need to eventually use the ". build/envsetup.sh" and then "brunch vs985" commands to begin the actual build process itself, but my main question now even after all the tutorials I've read is whether or not there are additional "device-specific" commands I need to run or things need to do or sync in order to make the final product compatible with our VS985. I found a tutorial on building CM11 for our device, and it talked about having to create a local_manifest.xml file and then repo sync'ing again, but this is pretty much where I got lost and where I'm still quite confused. Can anyone with prior AOSP building experience help me out with some idiot-friendly () pointers/instructions and explanations on where to go after repo sync'ing? I would seriously appreciate any help anyone can offer. Thanks!!
ohlin5 said:
Hey guys...hoping someone here who is wiser than I can offer some information on how I might complete the task I am after. I've got limited knowledge in the rom-building department, but would really like to learn at least enough to "get my feet wet" so to speak, and so I'm trying hard to do just that. I would like to build a version of SlimKat based on the latest code available, and have it be compatible with our device (the VS985). I've gotten so far as to set up the Ubuntu build environment and everything, installing repo and initializing the directory with the SlimKat 4.4.4 caf (by doing repo init -u git://github.com/SlimRoms/platform_manifest.git -b kk4.4-caf), and finally repo sync'ing the whole thing.
I'm pretty sure that I need to eventually use the ". build/envsetup.sh" and then "brunch vs985" commands to begin the actual build process itself, but my main question now even after all the tutorials I've read is whether or not there are additional "device-specific" commands I need to run or things need to do or sync in order to make the final product compatible with our VS985. I found a tutorial on building CM11 for our device, and it talked about having to create a local_manifest.xml file and then repo sync'ing again, but this is pretty much where I got lost and where I'm still quite confused. Can anyone with prior AOSP building experience help me out with some idiot-friendly () pointers/instructions and explanations on where to go after repo sync'ing? I would seriously appreciate any help anyone can offer. Thanks!!
Click to expand...
Click to collapse
It all depends. If the source you grabbed does not have anything specific for the vs985, then the build command itself won't work. The build scripts and configuration has to be modified to add that build command and even then, it means going into the source and making whatever changes you need to make it specific to the VS985.
Since it's AOSP, it should work no matter what, but that means anything that requires vs985 specific calls to make it work aren't there.
It's not just a magic command that makes it work. You have to go in and figure out what isn't and is working and make the necessary changes.
I'm assuming you are a programmer? If not, better learn.
iBolski said:
It all depends. If the source you grabbed does not have anything specific for the vs985, then the build command itself won't work. The build scripts and configuration has to be modified to add that build command and even then, it means going into the source and making whatever changes you need to make it specific to the VS985.
Since it's AOSP, it should work no matter what, but that means anything that requires vs985 specific calls to make it work aren't there.
It's not just a magic command that makes it work. You have to go in and figure out what isn't and is working and make the necessary changes.
I'm assuming you are a programmer? If not, better learn.
Click to expand...
Click to collapse
I see. I have had some very basic programming exposure, but I wouldn't consider myself anywhere near skilled and it's been a while haha. Well I do appreciate the info and I'll probably be best off leaving this to those much smarter than I Thanks!
ohlin5 said:
I see. I have had some very basic programming exposure, but I wouldn't consider myself anywhere near skilled and it's been a while haha. Well I do appreciate the info and I'll probably be best off leaving this to those much smarter than I Thanks!
Click to expand...
Click to collapse
I don't want to scare you off. If you feel like you want to learn something new, then don't hold back. I just wanted to let you know that it's not just a simple "grab the source from another phone and compile it for the G3". That's why you'll see different ROMs for each of the different phones. But, in the case of this phone, you all have to add the bump to the ROM in order for it to work and that is specific to each version of the G3. You can't take a bumped D850 (AT&T) ROM and just flash it onto a Verizon G3 (VS985). It won't work.
Now, bumping is not that hard as one of the posts on how to compile a ROM for the G3 gives you the instructions to "bump" your ROM, which is done after you've compiled it. Where it gets more difficult and requires some more tech savy and programming knowledge, is how to modify the ROM to take advantage of the hardware specific to the G3. The AOSP code pulled down for say CM11/CM2 is just that - AOSP. What you were doing was taking a completely different ROM's base source and trying to make that work on the G3. Not impossible by any means, but would require more than just a basic understanding of programming. You also need to understand how the Android OS works, etc. Again, not a trivial task by any means, but also, could end up being something that challenges you to learn more and eventually become a contributor to the G3 dev forums.
I myself am a programmer. I've been learning Android app development but I also wanted to delve into ROM building and was grateful to see the post on how to do so, so I'll be looking into that when I can, but I know it's not an trivial thing to master, but I'm a persistent person and most of my computer programming I learned was self taught when I was in high school on an Apple ][+ and //e. Those were the days when Apple wasn't so closed. Woz had a hand in wanting to keep it open - Jobs didn't. We all know who won on that count.
Any ways, if you are up to a challenge and like solving problems, programming is definitely the way to go.
I've been trying to build my own just for fun as well, but after I brunch, it doesn't create a zip.
I've been following this guide: http://forum.xda-developers.com/lg-g3/general/guide-how-to-build-cyanogenmod-11-d850-t2971538
I feel like it has something to do with my local_manifest.xml, but it's probably because I tried building CM12 and it's not as easy as just changing the branch...
Probably just going to start over from scratch with CM11 and see how it goes.
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