Related
Hey guys... I just wanted to see if anyone is already working on getting the kernel to compile..
You can find the source here: https://android.googlesource.com/kernel/exynos/ as stated in an earlier thread.
I'm currently getting my computer reformatted and getting my build environment set up. I've built from source before, but never for a kernel. Hoping to get the ball rolling on this! Cheers! :good:
By the way, I think we should all start hanging out in #nexus10 on freenode irc. Collaboration FTW
EDIT:
#Nexus10 already exists....
jdbeitz said:
Hey guys... I just wanted to see if anyone is already working on getting the kernel to compile..
You can find the source here: https://android.googlesource.com/kernel/exynos/ as stated in an earlier thread.
I'm currently getting my computer reformatted and getting my build environment set up. I've built from source before, but never for a kernel. Hoping to get the ball rolling on this! Cheers! :good:
Click to expand...
Click to collapse
Looks like android-exynos-manta-3.4-jb-mr1-fr is the shipping kernel. Will check it out here shortly.
I was unsuccessful my first go around :/ I'm gonna keep trying though!
jdbeitz said:
I was unsuccessful my first go around :/ I'm gonna keep trying though!
Click to expand...
Click to collapse
Yeah, really just need the kernel config off the device. We'll have that soon enough though.
It builds fine for me.
I've mirrored the kernel source on GitHub as well, chirayudesai/android_kernel_exynos
Sent from my GT-P1000
cdesai said:
It builds fine for me.
I've mirrored the kernel source on GitHub as well, chirayudesai/android_kernel_exynos
Sent from my GT-P1000
Click to expand...
Click to collapse
Oh... think I was using the wrong toolchain before. Thanks for the mirror too.
Ubuntu Touch Developer Preview for the Fascinate
// It took me a while to get it right, but here it is.
//Camera works, wireless internet works.
Haven't checked sound.
Don't know if phone or SMS works.
Need testers.
//How to install: DO A BACKUP FIRST!
Get the zip here Then get this. Go to recovery, do a wipe/factory reset.
//Flash the first zip, don't reboot yet. Go to Mounts and Storage, mount /data and then format it or it won't work.
//Then flash the second zip and reboot.
//After you reboot, don't do an apt update. It seems to bork things up for me. Using adb on your computer, type 'phablet-flash -d grouper -b' (to update to the latest).
Enjoy.
The above is the old way. Thanks to UnjustifiedDev the new build is below:
"Ubuntu touch
1. Download bootstrap http://goo.im/devs/Unjust/Fascinate/...scinatemtd.zip
2. Download preinstall http://cdimage.ubuntu.com/ubuntu-tou...blet-armhf.zip
yes it is 300+mb make sure you have space on your sdcard for it
3. Download layout fix http://goo.im/devs/Unjust/Fascinate/...layout_fix.zip
4. Reboot to recovery wipe data etc then flash bootstrap file first the cm-10.1 zip then reboot recovery
5. in ubuntu's purple recovery flash the saucy zip takes a while to flash make sure your battery is charged
6. Flash layout fix right after saucy zip completes then reboot
7. Note this a preview not a daily driver it is pretty cool but it lacks full features. Wifi works idk if sound works or data my phone is not in service
Source https://github.com/Ubuntu-Fascinate I did fix the layout no need for an extra zip next build "
You are the man, Unjust!!
Remember, it's just a developer preview at this point. Not much you can do with it right now.
Redwolves (meandmine)
[
Since the Fascinate is not my daily driver, I have no way to test 3G or SMS. Anyone want to give a try and post your results?
Thanks, Redwolves
I will keep this updated as much as I can. I'll also put detailed instructions an my github page for anyone who wants to compile their own.
I will put up the instructions on my github page tonight. I'll link to it here when I do.
Redwolves
*face palm* good job dude I was just building it was gonna be a surprise for y'all. You beat me to it lol. Nice job.
Sent from my SCH-I500 using Tapatalk 2
Really cool and as far as I know cdma isnt compatible with ubuntu touch but wifi should work. Im just glad yours worked I would really like to see a patch or could you push the source you used to get it working. I tried at least 10 times no luck at all on booting.
edit nvm thanks for this
Unjustified Dev said:
Really cool and as far as I know cdma isnt compatible with ubuntu touch but wifi should work. Im just glad yours worked I would really like to see a patch or could you push the source you used to get it working. I tried at least 10 times no luck at all on booting.
edit nvm thanks for this
Click to expand...
Click to collapse
Is it really can't work for the cdma?
Sent from my SCH-I500 using Tapatalk 4 Beta
ekowanz said:
Is it really can't work for the cdma?
Sent from my SCH-I500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Works fine for cdma it uses cm10.1 source so anythibg cm10.1 has it can use.
Unjustified Dev said:
Really cool and as far as I know cdma isnt compatible with ubuntu touch but wifi should work. Im just glad yours worked I would really like to see a patch or could you push the source you used to get it working. I tried at least 10 times no luck at all on booting.
edit nvm thanks for this
Click to expand...
Click to collapse
No patch needed boots and works fine for me straight from source but I like android better just lack of apps on Ubuntu. And agreed nice job
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
No patch needed boots and works fine for me straight from source but I like android better just lack of apps on Ubuntu. And agreed nice job
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I meant patch as in a diff file to see how he modified things
Unjustified Dev said:
I meant patch as in a diff file to see how he modified things
Click to expand...
Click to collapse
I didnt need to modify anything.
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
I didnt need to modify anything.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Im talking source code you cant just build it like a regular rom there is things you need to modify
Unjustified Dev said:
Im talking source code you cant just build it like a regular rom there is things you need to modify
Click to expand...
Click to collapse
I didn't have to modify anything it just used the cm files. Did you follow the official port guide or some off the wall nut job guide here on xda? Maybe I'm just lucky idk. Who cares.
Sent from my SCH-I500 using Tapatalk 2
I followed the porting guide. Commented out AriesParts and Samsung-something-or-other in a makefile in /devices. Patched /kernel/samsung/aries/fs/proc/array.c and /kernel/samsung/aries/arch/arm/configs. I did some other other patches to a makefile in /build. I played with it for about a month using just the phablet-armhf.zip. I had it booting for about 15 seconds after a while. I was going through logcats and trying to trace them back to any warnings thrown during compilation.
Then I found out it uses the grouper image. Voila, instant boot. I left the changes in the source, though.
redwolves said:
I followed the porting guide. Commented out AriesParts and Samsung-something-or-other in a makefile in /devices. Patched /kernel/samsung/aries/fs/proc/array.c and /kernel/samsung/aries/arch/arm/configs. I did some other other patches to a makefile in /build. I played with it for about a month using just the phablet-armhf.zip. I had it booting for about 15 seconds after a while. I was going through logcats and trying to trace them back to any warnings thrown during compilation.
Then I found out it uses the grouper image. Voila, instant boot. I left the changes in the source, though.
Click to expand...
Click to collapse
I'll put up detailed instructions and the code on my github page when I get the chance. Life has 'a life' in it, you know.
Scott
If anyone is having problems, please see if you can grab a logcat and send it to me.
for some reason wen i install the 2nd zip, i get status 7 error
arqda said:
for some reason wen i install the 2nd zip, i get status 7 error
Click to expand...
Click to collapse
You're the second person who has said that. I can't reproduce it on my phone. I need to find a common thread.
What Baseband version are you running?
Thanks, Scott
redwolves said:
You're the second person who has said that. I can't reproduce it on my phone. I need to find a common thread.
What Baseband version are you running?
Thanks, Scott
Click to expand...
Click to collapse
Ill try to give u as much detai l as possible.
Baseband: i500.04.V.EH03
Tried flashing using CWM4, 6, modified6, and twrp
Using 1gb sd card (class ?) To flash
Finally got around to detailed instructions on my github account. It's here. I'll push the code up shortly.
redwolves said:
Finally got around to detailed instructions on my github account. It's here. I'll push the code up shortly.
Click to expand...
Click to collapse
I did all of that except one thing I forgot array.c also we dont need samsung service mode
Unjustified Dev said:
I did all of that except one thing I forgot array.c also we dont need samsung service mode
Click to expand...
Click to collapse
"While in /device/samsung/aries-common, edit device_base.mk. Comment out AriesParts and SamsungServiceMode under
"# Device-specific packages"."
I thought I had it in there.
Hi folks,
I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
Best regards,
Kalle
First Update:
I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
So long,
Kalle
Update!
There is a new porting guide! See here
I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
Hope you are as excited as I am,
Kalle
XDA:DevDB Information
Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra
Contributors
KalleEatingBrain, Kohelet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2014-05-14
Last Updated 2015-02-24
freaking awesome!
freaking awesome!
i would like to test. maybe i can help with developing/porting
Thank you for your efforts. I will test if needed.
Sent from my C6806 using XDA Premium 4 mobile app
Great this would be awesome if you can make it happen. I'm here for testing if required.
Sent from my C6833 using XDA Premium 4 mobile app
In also here for testing... Ubuntu Touch has intruiged me, I would love to try it out.
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
iBuzman said:
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
+1
Nice.ill be watching out everyday
Sent from my C6833 using XDA Premium 4 mobile app
blueether said:
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
Click to expand...
Click to collapse
Cool, thanks can you give me a hint on how to deal with new targets in Aosp? I mean setting up the files in a way "lunch" is able to find the right target.
Sent from my C6833 using XDA Free mobile app
vendersetup.sh file in vender/ might be what you are looking for?
have a gander at this http://www.kandroid.org/online-pdk/guide/build_new_device.html
How are you doing on this? I've just started working on this as well and am curious to know how far along you've gotten/what issues you've run into.
Sent from my Nexus 7 using XDA Free mobile app
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Kohelet said:
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Click to expand...
Click to collapse
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
KalleEatingBrain said:
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
Click to expand...
Click to collapse
I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).
Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.
At this point I've decided to take a short break from the whole thing because it's so frustrating.
Once I get motivated to work on it again, I'll probably start from scratch.
Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):
If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk
Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.
The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk
I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.
If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]
You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk
You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.
If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk
You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.
You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
Click to expand...
Click to collapse
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
blueether said:
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
Click to expand...
Click to collapse
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Kohelet said:
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Click to expand...
Click to collapse
Yeh carbon and slim were easy to build, and simple fixes. AOSP on the other hand I wish I had kept a build log
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
KalleEatingBrain said:
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch.
Click to expand...
Click to collapse
That could potentially be a major source of my problems. i wasn't aware of that.
I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
All I have at the moment is a fork of the CM repos. Feel free to add me to your repo. My username on Github is Kohelet as well. I can start to look into removing java dependencies as well.
As for the sound, the mailing list made it appear as if it was a simple matter of running
Code:
$ sudo apt-add-repository ppa:ci-train-ppa-service/landing-018
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo apt-get install pulseaudio-module-droid
I could be wrong though.
Q&A for [5.0][AOSP][port][wip] CodeROM 5.0 by LollipopS2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [5.0][AOSP][port][wip] CodeROM 5.0 by LollipopS2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Well, we will try to fix it ourselves, but it would be much faster if some skilled dev help us with fixing boot problems. I was porting this rom yesterday, and i think it is little success that we got to the bootscreen with "ANDROID" logo. Thx for all supports, we are doing our best
Error
This account's public links are generating too much traffic and have been temporarily disabled!
Thanks for good work
Wouldn't it be easier to port the note cm12 alpha build? since it uses the same hardware, would be a matter of fixing configs
Fail
Download link is K.O.
Thanks
Link
Download links is now updated now. Also, we have finished porting of CM12.
Just wanted to know if its getting past the BOOT Animation over gt-i9100 ??
read first post
Please read first post carefully. Rom isnt bootable yet. You can see boot animation, but there is a bootloop.
Thanks
Thumbs up
cm12
Bootloop is in CM12 port too. I will upload it today. We are also starting to build CM12 from sources.
Thanks
ahmedelhofy said:
@jeffreyvh hey, take a look at this.... It's already booting on N7000.. That's mostly a similar phone to the i9100... It will surely help you... Or at least you can contact the guy who made it, he might help you...
http://forum.xda-developers.com/showthread.php?t=2938649
Click to expand...
Click to collapse
THX for link dude, thanks to you and your idea im just building CM12 for i9100 from sources.
I know that you can do it!! Thanks a lot!! :beer:
Sent from my GT-I9100 using XDA Free mobile app
Lenger96 said:
Bootloop is in CM12 port too. I will upload it today. We are also starting to build CM12 from sources.
Click to expand...
Click to collapse
I'm trying to build cm12 from source too, but so far I still can't get past repo sync errors, after that I think the proprietary blobs will be the problem
build
I have passed over reco sync, but specific files copying crashed, because there isnt any files for i9100 in cm12 repo. Im out of ideas....
Lenger96 said:
I have passed over reco sync, but specific files copying crashed, because there isnt any files for i9100 in cm12 repo. Im out of ideas....
Click to expand...
Click to collapse
The breakfast command failed right? Well on the cm git there's only cm11 branch for our device, take a look here: https://github.com/CyanogenMod/android_device_samsung_i9100. Have you tried pushing files manually from cm11 branch? I think it's not gonna work too because we need a proper 5.0 kernel... Building AOSP with cm11 device tree would be even worse... I think the only way to boot some Lollipop on S2 is know what people have done in the kernels of the Note, or the S3 devices, and then do the same on our kernel. But sadly, I'm not xplodwild to do this
Yeah
Lysergic Acid said:
The breakfast command failed right? Well on the cm git there's only cm11 branch for our device, take a look here: https://github.com/CyanogenMod/android_device_samsung_i9100. Have you tried pushing files manually from cm11 branch? I think it's not gonna work too because we need a proper 5.0 kernel... Building AOSP with cm11 device tree would be even worse... I think the only way to boot some Lollipop on S2 is know what people have done in the kernels of the Note, or the S3 devices, and then do the same on our kernel. But sadly, I'm not xplodwild to do this
Click to expand...
Click to collapse
Ive sent PM to dev who built CM12 for N7000. Maybe he can help. Can i ask you to write him too? Maybe if there will be more of us who write him, he will help us sooner.
Lenger96 said:
Ive sent PM to dev who built CM12 for N7000. Maybe he can help. Can i ask you to write him too? Maybe if there will be more of us who write him, he will help us sooner.
Click to expand...
Click to collapse
I'll contact him too and maybe his steps on the Note can help us
Awesome
looking forward o boot up lolipop in our s2
re
Lysergic Acid said:
I'll contact him too and maybe his steps on the Note can help us
Click to expand...
Click to collapse
I got PM from him. All we need to do is manually copy device tree (you can find it on guthub) to /device/samsung/i9100. We can use cm11 tree.
Lenger96 said:
I got PM from him. All we need to do is manually copy device tree (you can find it on guthub) to /device/samsung/i9100. We can use cm11 tree.
Click to expand...
Click to collapse
Are you kidding? Really? Lol, If this works, maybe tonight I can give you guys a working Lollipop
EDIT: If someone here already have a fully synced CM12 source, just git clone this: https://github.com/CyanogenMod/android_device_samsung_i9100 to /device/samsung/i9100 and try building
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.