K900 Device Tree project
hi folks, a couple of months ago i decided it was time to create a working device tree at least to build cwm, since lenovo is very bad at opensource with us, it is nearly impossible to build a working cyanogen. Fortunately cwm doesn't need too much to be build so i grabbed the motorola razr i device tree from @hazou and wrote a new device tree for us. But unfortunately we still need a developer firmware from lenovo to flash recovery.img's. However, cwm builds well and i want to share my work to any interested developer who are willing to help.
Click to expand...
Click to collapse
in this github you will find all needed repos and info --> https://github.com/lenovo-k900
Click to expand...
Click to collapse
Its true, thanks for your effort QuBeX. I hope it works. I will follow.
Great job! I am also interested in hacking my K900 to enable kvm kernel module to run VMs on it.
The issue was always their stupid secure boot process which prevent use to put our kernel or even a kernel module into the system.
You refer to a developer firmware. Did you get chance to have access to one of those?
Does that turns off secure boot or you somhow got the signing key?
Please pm me if you know more details on that.
Thanks a lot.
chinabull said:
Great job! I am also interested in hacking my K900 to enable kvm kernel module to run VMs on it.
The issue was always their stupid secure boot process which prevent use to put our kernel or even a kernel module into the system.
You refer to a developer firmware. Did you get chance to have access to one of those?
Does that turns off secure boot or you somhow got the signing key?
Please pm me if you know more details on that.
Thanks a lot.
Click to expand...
Click to collapse
Lenovo hasn't provided a dev firmware yet. And I don't think they will... Anyway we now have working recovery, and we are finding out how to bypass signature check, but it is really difficult.
Talking about the kernel, have you ever tried kexec? I don't know very much of it but you can find a lot of info and stuff in google
Thanks, man. That is a briliant idea!
I have built the kexec executible and have loaded my custom kernel into the memory.
Of course when it ran the new kernel, I got a black screen for now. But it's a good start. I'll debug it and keep you guys updated with the progress.
chinabull said:
Thanks, man. That is a briliant idea!
I have built the kexec executible and have loaded my custom kernel into the memory.
Of course when it ran the new kernel, I got a black screen for now. But it's a good start. I'll debug it and keep you guys updated with the progress.
Click to expand...
Click to collapse
Just a quick update on progress.
Tried all kinds of tricks including modifying kernel code on the fly.
Still no luck on kexec yet.
But I found a loophole in the JB4.3 kernel which I used to have the kernel module signature check disabled.
Now I can load any kerenl module I built.
If anybody has interest on that tool, please PM me.
Now we have AOSP 4.3 branch in our device tree: https://github.com/lenovo-k900/android_device_lenovo_redhookbay/tree/aosp-4.3
Author: MaXxXanter
Can't wait for this. I wish i could do some support too...
Sent from my Lenovo K900_ROW using XDA Free mobile app
can i use this device tree for build cm12.1 rom?
xxx-man-by said:
Now we have AOSP 4.3 branch in our device tree: https://github.com/lenovo-k900/android_device_lenovo_redhookbay/tree/aosp-4.3
Author: MaXxXanter
Click to expand...
Click to collapse
is possible to build cm11 with that source sir?
xxx-man and qubex and any other who is putting time to get some nice roms for our K900 is greatly appreciated.
Related
Hello,
I wanted to discuss means of creating a device tree for the Samsung Galaxy S4 I9500 so the development can start for the ROM, What is putting us off the track ? What do we need to reach a fully working device tree ?
Hope we could reach something out together ..
Look here
Faryaab has already created one. Let's fork the main repo or branch it with individual repository.. Let's create a team and start working on it
I will set up my Linux machine tonight. Hopefully, we can achieve what we want
Rahulrulez said:
Faryaab has already created one. Let's fork the main repo or branch it with individual repository.. Let's create a team and start working on it
I will set up my Linux machine tonight. Hopefully, we can achieve what we want
Click to expand...
Click to collapse
Perfect .. As I want to release for this device and the lack of a properly working Device tree is stopping me !
We can not really start on Faryaab's tree. He has given up on the I9500. He is not willing to develop it further (as far as I know). But I still thank him for kick starting it
We need another complete tree now
There's a hell of a lot more involved than creating the device tree... There is no Exynos5 "Octa" platform support anywhere in the tree.
Each platform almost always requires some degree of customization to the frameworks to support it - the required customizations for Exynos5 "Octa" are undocumented. (search the tree for QCOM_HARDWARE or EXYNOS4_ENHANCEMENTS for some examples.)
Anyone can create a tree. Implementing support for a new platform throughout the codebase is a whole other story - and no one wanting to do THAT so far is why the I9500 has no CM support.
Entropy512 said:
There's a hell of a lot more involved than creating the device tree... There is no Exynos5 "Octa" platform support anywhere in the tree.
Each platform almost always requires some degree of customization to the frameworks to support it - the required customizations for Exynos5 "Octa" are undocumented. (search the tree for QCOM_HARDWARE or EXYNOS4_ENHANCEMENTS for some examples.)
Anyone can create a tree. Implementing support for a new platform throughout the codebase is a whole other story - and no one wanting to do THAT so far is why the I9500 has no CM support.
Click to expand...
Click to collapse
I know, what I am thinking is just try to port framework and other important libraries and see if that works. Exynos is badly documented
maradonaiconboy said:
Perfect .. As I want to release for this device and the lack of a properly working Device tree is stopping me !
Clubvegas999
Click to expand...
Click to collapse
Two posts above yours, He said that it's not going to be easy simply because Samsung just can't document a thing properly !
With lack of proper documentation , It would be extremely hard to create the device tree .. I too want to build my ROM for the i9500 but we need to figure something out to be able to continue ..
Folks just coming by and asking it to get/keep it going - that's not dev talk and plenty of other forums to post that in.
So if your post disappeared... that's why.
Thanks.
Did you guys see ewmno device tree for i9500?
Follow Me on Twiiter @razer1224
---------- Post added at 11:48 AM ---------- Previous post was at 11:45 AM ----------
johnhany97 said:
Two posts above yours, He said that it's not going to be easy simply because Samsung just can't document a thing properly !
With lack of proper documentation , It would be extremely hard to create the device tree .. I too want to build my ROM for the i9500 but we need to figure something out to be able to continue ..
Click to expand...
Click to collapse
Did you check camerawrapper. Cpp of Xperia... Since GT-I9500 uses a Exmor Rs sensor
Follow Me on Twiiter @razer1224
---------- Post added at 11:51 AM ---------- Previous post was at 11:48 AM ----------
I am forking farylaab repo too
Dont we need proprietary files?
Follow Me on Twiiter @razer1224
ill try to work on the vendor tree to
i will push today the basic files
RD's I think you guys can help me
Device Tree (Forked From Faryaab)
https://github.com/KiranSurath/android_device_samsung_i9500
Vendor Tree (Full Experiment)
https://github.com/KiranSurath/android_vendor_samsung_GT-i9500
We Can Work as a Team
razer1224 said:
Device Tree (Forked From Faryaab)
https://github.com/KiranSurath/android_device_samsung_i9500
Vendor Tree (Full Experiment)
https://github.com/KiranSurath/android_vendor_samsung_GT-i9500
We Can Work as a Team
Click to expand...
Click to collapse
I want to work with you as a team but my exams are not allowing me to do so. As soon as my exams gets ,I will join with you.
Sent from my GT-I9500 using XDA Premium HD app
Trying to build with only device tree
Follow Me on Twiiter @razer1224
Sent from my SCH-I545 using xda app-developers app
razer1224 said:
Trying to build with only device tree
Follow Me on Twiiter @razer1224
Click to expand...
Click to collapse
Did it work with you or not ?
johnhany97 said:
Did it work with you or not ?
Click to expand...
Click to collapse
No it didn't.
Status 7 error.
Akhil said:
No it didn't.
Status 7 error.
Click to expand...
Click to collapse
do you replaced folders in google source by the same from opesnsource.samsung com ?
and why in i9500-vendor.mk you wrote
$(call inherit-product, vendor/htc/samsung/i9500-vendor-blobs.mk)
Click to expand...
Click to collapse
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”
You can delete this assert in updater-script to bypass this verification
did anyone brick there device from compiling error ?
S.a.M.e.R_d said:
did anyone brick there device from compiling error ?
Click to expand...
Click to collapse
oh, common.. Why you think device can be bricked by this? It won't. Just don't mess with boot block (and don't use engineering bootloader because it doesn't set boot block hardware write protection) and you always will be able to enter download mode and then flash whatever you want through Odin.
Hello everyone, I'm a complete noob at compiling. I'm thinking about compiling OmniROM 6.0 for XOLO BLACK. So, I wanted to ask how big is the download size of its source code and do we have a need of Kernel while compiling? Although my device does have an open source kernel. Could be found here: https://github.com/hiveinside/xolo_kernel
I'll be grateful if someone could help me with my questions
You will need about 50-100gb for all the source. Yes you will also need the kernel source as well as the device trees. Then it will just be a matter of fixing the bugs that come up. You didn't think it would just work did you?
zelendel said:
You will need about 50-100gb for all the source. Yes you will also need the kernel source as well as the device trees. Then it will just be a matter of fixing the bugs that come up. You didn't think it would just work did you?
Click to expand...
Click to collapse
No no, I meant what would be the download size? You know after doing the "repo sync" command. Also, I think it'll extract the kernel automatically from my device and what is "device tree?" Vendor files?
Well, I know that I have to face bugs but I think awesome people like you will help me fix 'em.
Wish me luck!
So, after destroying a tremendous amount of data and a whole lot of wait, I finally synced the whole OmniROM 6.0 source code via repo. Now I want to compile it for my device XOLO BLACK (Codename: BLACK) so, can somebody tell me how I can and what am I gonna need (I mean files, like vendor files, kernel etc.)?
Also, how can I extract its device tree? Because it's not available online.
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
zelendel said:
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
Click to expand...
Click to collapse
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
NutVolt said:
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
Click to expand...
Click to collapse
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
zelendel said:
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
Click to expand...
Click to collapse
I know it's gonna take long but if I can't even start then I'll feel very bad, all the hard work I've done to just fetch the source.
Anyway, how can I make a device tree? Can you teach me?
The good stuff: https://github.com/jcadduono/android_kernel_lge_msm8996/commits/android-7.0
Fork it!
Update: CAF branch has some problems at the moment, use this one instead for now.
So this is currently the v10d release. It's compatible with V20 Nougat v10d and G5 v20a.
Place toolchain (pick one up from here) in ~/build/toolchain & tar xf.
git clone https://[email protected]/yourname/android_kernel_lge_msm8996.git
If you want to change any config options:
./menuconfig.sh (optional target, ex. twrp or lge)
Ready?
./build.sh h850/h830/h918/us996/any model you want
Models are applied onto the target base defconfig, so your V20 kernels will build for all V20 variants and for all variants of the G5 as well.
Create your own by copying arch/arm64/configs/lge_defconfig to arch/arm64/configs/your-awesome_defconfig!
Grab:
build/arch/arm64/boot/Image.lz4-dtb [or] build/arch/arm64/boot/Image.gz-dtb
build/lib/modules
Place in:
https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
make
You got yourself a magical all-powerful custom kernel installer, complete with your own custom kernel!
Notice that there's a few branches:
opensource is where I merge LG changes, when it's updated, android-7.0 is rebased on it
android-7.0 is a starting off point closest to absolute stock, base off here
android-7.0-security adds security and bug fixes from CAF on top of android-7.0 branch
twrp-7.0 is for Team Win Recovery Project (yes, it's ready, come with an unlocked device and I'll give it to you)
nethunter-7.0 is for the Kali NetHunter project (if you dare, some fun there)
Another issue was their weird build system, I dropped that. Replaced tuxera's exFAT prebuilt downloader with Samsung's GPL'd exFAT drivers instead. Unsure how well it works replacing it like that, we'll have to see.
I also added Qualcomm's Core Control which they just released the sources to somewhat recently. I believe it's already included on the G5 and probably V20 as a kernel module. Their released version doesn't have module support yet but it's fairly easy to add I guess with the leaked proprietary module version out there to pick pieces from.
Have fun!
Great Man !
thanks for this..
I've been following the root process since the beginning and I'm amazed at the relatively short amount of time it took. Huge kudos to @jcadduono! I will purchase this phone. Now, since the kernel needed to have it's encryption support modifed, are the patches added to a branch on your Github fork? I would like to compile a custom kernel, along with patching it with SultanXDA's SafetyNet boot bypass. Which branch will be appropiate to fork to flash on the TWRP/Rooted V20?
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
zabracks said:
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
Click to expand...
Click to collapse
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
I've got an H918, if you need somebody to test a kernel.
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
which branch/repo is the one that boots but messed up display?
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
lightninbug said:
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
Click to expand...
Click to collapse
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:25 PM ----------
Artcrime said:
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
Click to expand...
Click to collapse
There is v10d version for 918. opensource.lge.com forgive me if this is old news. a|c
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
slayerh4x said:
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
Click to expand...
Click to collapse
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
Sent from my LG-H990 using Tapatalk
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Is a kernel the main thing stopping us from a CM rom?
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
jcadduono said:
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Click to expand...
Click to collapse
I'm there.
albinoman887 said:
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
Click to expand...
Click to collapse
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz .Be sure to change the PATH in menuconfig.sh
@jcadduono , thank you. You are truly an inspiration
Wondering if anyone can help me learn how to do this right...
So I was able to compile the kernel, but I didn't get an Image.gz (which im sure is fine). I did get an Image.lz4, Image.lz4-dtb, and Image (no extension). I figure only the .lz4* files are needed. I added all 3 to the lazyflasher, and ran make. The resulting zip flashed, but sent me straight to Bootloader. I then tried to fix by flashing the stock kernel, but this still did not boot. ReFlashed my ROM and it's booting now.
I used this toolchain gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu
Any guidance? My guess is it's flashing at the wrong point?
Here is the ZIP. DO NOT FLASH. This is only for someone who knows what they are looking at to tell me what is wrong with it. No modifications were done. Source was forked from OP, and compiled with default menuconfig, then build.sh h918
INTRO:
I present a new version of my kernel, now for the lg k7, the kernel has patches that will help you get a very good performance, as well as a longer battery life, and better fluidity, is compiled with UbertTC in its version 5.2, in addition to containing patches for a correct stability.
Features:
* Compiled with UberTC
* More coming soon...
Downloads:
Preview version -> Download
Instructions:
* Flash in TWRP
Notes:
* Im only test in MetroPCS variant
Sources:
GitHub
Reserved
....
Worked flawlessly. Flashed with TWRP and rebooted and system loaded up fine. There was a few minor lags as it booted into the system past the MetroPCS logo but that was probably due to the changes made by the zip but after that the system was more fluid than it previously was even after having soo many apps installed. Great work. This is one step closer to completing a custom rom like CM13 or Lineage OS. Good luck with more development.
thepcwiz101 said:
Worked flawlessly. Flashed with TWRP and rebooted and system loaded up fine. There was a few minor lags as it booted into the system past the MetroPCS logo but that was probably due to the changes made by the zip but after that the system was more fluid than it previously was even after having soo many apps installed. Great work. This is one step closer to completing a custom rom like CM13 or Lineage OS. Good luck with more development.
Click to expand...
Click to collapse
Im already working on Lineage
xperiafan13 said:
Im already working on Lineage[/QUO
Hey people don't forget to hit the thanks button.
By the way ty Dev keep up the good work. This phone is def a decent phone surprise nothing been built for it.
Click to expand...
Click to collapse
xperiafan13 said:
Im already working on Lineage
Click to expand...
Click to collapse
Nice. I hope Development is going well. If you need any testers i am up for testing any builds.
thepcwiz101 said:
Nice. I hope Development is going well. If you need any testers i am up for testing any builds.
Click to expand...
Click to collapse
I second that statement... I'll be a test dummy ?? anything for a new ROM!
Im already compile lineage, but this not boot, im need more time
xperiafan13 said:
Im already compile lineage, but this not boot, im need more time
Click to expand...
Click to collapse
Need any help let me know. . I'd love to help!
xperiafan13 said:
Im already compile lineage, but this not boot, im need more time
Click to expand...
Click to collapse
Hopefully it boots. Many of us have been waiting for a custom rom ??? btw, I tried to make help with compiling a custom rom but haven't had time. I'm also a noob in this so Im researching on "How to complie a custom rom from scratch" but its really difficult ?? Thank you for your efforts???
SageTheMage99 said:
Hopefully it boots. Many of us have been waiting for a custom rom ??? btw, I tried to make help with compiling a custom rom but haven't had time. I'm also a noob in this so Im researching on "How to complie a custom rom from scratch" but its really difficult ?? Thank you for your efforts???
Click to expand...
Click to collapse
Yeah I have ported a few ROMs but when it comes down to comp... A ROM that's a whole different ball park for me also.
You could try to Port the LG Leon ROMs. There's 2 I don't have the phone so I can not try.
Good job on the kernel compile i couldnt get mine to boot, good luck on the lineage compile. Ive picked this phone back up so let me know if you need any help.
NASSTYROME said:
Good job on the kernel compile i couldnt get mine to boot, good luck on the lineage compile. Ive picked this phone back up so let me know if you need any help.
Click to expand...
Click to collapse
Hello, i just downloaded LineageOS but everytime i type:
"breakfast m1", i get:
** Don't have a product spec for 'lineage_m1'
** Do you have the right repo manifest?
Any help is appreciated, for better way to reach me is my kik: SageOfSixPaths999
Breakfast wont work u need to manually set variables and make calls like old android.
NASSTYROME said:
Breakfast wont work u need to manually set variables and make calls like old android.
Click to expand...
Click to collapse
Would you please guide me or send link to where i could do this?
At the moment I am not working on this, since I am in school projects, but once I finish with it I will continue with this, both the kernel and the development of rom, the sourves are in my github of the kernel, if they want to modify it or Add improvements
xperiafan13 said:
At the moment I am not working on this, since I am in school projects, but once I finish with it I will continue with this, both the kernel and the development of rom, the sourves are in my github of the kernel, if they want to modify it or Add improvements
Click to expand...
Click to collapse
Ok thank you for your work ether way but i can try to help, i just need info. But i will do and find out whatever i can. I really am exited for a new rom lol. I will continue once i get home.
xperiafan13 said:
At the moment I am not working on this, since I am in school projects, but once I finish with it I will continue with this, both the kernel and the development of rom, the sourves are in my github of the kernel, if they want to modify it or Add improvements
Click to expand...
Click to collapse
Just curious, what version of Lineage OS were you building?
EDIT: I am running the kernel on the T-Mobile K330 variant with no issues. Good work :good:
QuickNET Tech said:
Just curious, what version of Lineage OS were you building?
EDIT: I am running the kernel on the T-Mobile K330 variant with no issues. Good work :good:
Click to expand...
Click to collapse
I know you didn't ask me but if it helps, I'm working on CM-14.1
All i need is to "set the variables manually" but so far no luck in my research and also no one helps me with my questions. I also posted a post on the thread of k7 questions and such but so far no luck.