Hi all, I'm trying to build DU on walleye, however I keep running into this error
[ 99% 1439/1440] glob vendor/*/*/*/*/*/*/Android.bp
ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/everett/~du/out/target/product/walleye/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it
17:57:10 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
Wondering if anyone has a fix, thanks
What kernel source are you using?
providing the log before that would also help.
gbmasterdoctor said:
What kernel source are you using?
Click to expand...
Click to collapse
I'm using Nathan's Kernel Source based on Linux Stable
munchy_cool said:
providing the log before that would also help.
Click to expand...
Click to collapse
Sorry about that, when I get home i'll provide the full logs from the build
munchy_cool said:
providing the log before that would also help.
Click to expand...
Click to collapse
https://pastebin.com/3ybqZEq4
There are the full logs, sorry for not providing them before.
EDIT: Slightly different failure occurs when renaming Kernel source to wahoo and compiling
https://pastebin.com/bRFEBTTj
TCUofficial said:
https://pastebin.com/3ybqZEq4
There are the full logs, sorry for not providing them before.
EDIT: Slightly different failure occurs when renaming Kernel source to wahoo and compiling
https://pastebin.com/bRFEBTTj
Click to expand...
Click to collapse
the one below
Code:
ninja: error: 'kernel/google/wahoo/arch/arm64/configs/flash-walleye_defconfig', needed by '/home/everett/~du/out/target/product/walleye/obj/KERNEL_OBJ/.config', missing and no known rule to make it
17:59:08 ninja failed with: exit status 1
is because the kernel configuration you want to use is not there. you can check in kernel/google/wahoo/arch/arm64/configs
this one
Code:
ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/everett/~du/out/target/product/walleye/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it
17:47:56 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
is because its not able to find that file.
if you can point me to your device, kernel, vendor trees i can have a look.
munchy_cool said:
if you can point me to your device, kernel, vendor trees i can have a look.
Click to expand...
Click to collapse
Device tree was modified from AICP, I have it here: https://github.com/TCU14/device_google_walleye
The proprietary vendors are also from AICP, here: https://github.com/AICP/proprietary_vendor_google
The kernel source is here: https://github.com/android-linux-stable/wahoo
Thanks for the help, I'm doing my best to fix things on my own and am trying to improve. Unfortunately errors are not my forte
TCUofficial said:
Device tree was modified from AICP, I have it here: https://github.com/TCU14/device_google_walleye
The proprietary vendors are also from AICP, here: https://github.com/AICP/proprietary_vendor_google
The kernel source is here: https://github.com/android-linux-stable/wahoo
Thanks for the help, I'm doing my best to fix things on my own and am trying to improve. Unfortunately errors are not my forte
Click to expand...
Click to collapse
so we need to do it right.
1. fork the repo, then clone it. dont clone and push as a new repo because it's going to be hard to track changes if you get serious about this.
this line below
Code:
TARGET_KERNEL_CONFIG := flash-walleye_defconfig
specifies what kernel config the build is looking for.
https://github.com/TCU14/device_google_walleye/blob/master/walleye/BoardConfig.mk
where does it look for those configs?
well it looks for those configs here
https://github.com/android-linux-stable/wahoo/tree/android-msm-wahoo-4.4-oreo-m2/arch/arm64/configs
so as you can see you dont have that config. so you can use wahoo_defconfig.
Even I am new to this, so i might not be the best guide but i will try my best.
munchy_cool said:
so we need to do it right.
1. fork the repo, then clone it. dont clone and push as a new repo because it's going to be hard to track changes if you get serious about this.
this line below
Code:
TARGET_KERNEL_CONFIG := flash-walleye_defconfig
specifies what kernel config the build is looking for.
https://github.com/TCU14/device_google_walleye/blob/master/walleye/BoardConfig.mk
where does it look for those configs?
well it looks for those configs here
https://github.com/android-linux-stable/wahoo/tree/android-msm-wahoo-4.4-oreo-m2/arch/arm64/configs
so as you can see you dont have that config. so you can use wahoo_defconfig.
Even I am new to this, so i might not be the best guide but i will try my best.
Click to expand...
Click to collapse
Thanks for that, just forked AICP and made my changes, new tree is here: https://github.com/TCU14/device_google_walleye-1
I'll see if I can build or if another error pops up, again thanks for the help
EDIT: Nvm, I am stupid. Back to the kernel headers issue :/
TCUofficial said:
EDIT: Nvm, I am stupid. Back to the kernel headers issue :/
Click to expand...
Click to collapse
make sure to do
Code:
make clean
after a build fails.
Doesn't that do the same thing as make clobber?
TCUofficial said:
Doesn't that do the same thing as make clobber?
Click to expand...
Click to collapse
yes.
munchy_cool said:
yes.
Click to expand...
Click to collapse
Thanks for the help, it's currently building. Fixed some of the issues, haven't updated my repos yet though
TCUofficial said:
Thanks for the help, it's currently building. Fixed some of the issues, haven't updated my repos yet though
Click to expand...
Click to collapse
good luck let us know how it goes.
Ok, the touchscreen appears to have shat itself. Other then that, it booted fine with no hiccups.
Idk what's after the setup because of the touch issue. Grabbing a logcat now, seeing if I can possibly fix it.
EDIT: Can't get logcat because I can't allow debugging... this is ****ing hilarious to me
EDIT: Flashing FlashKernel fixed the touchscreen issue, however Google Services Framework is now force closing. constantly. Going to rebuild with FlashKernel if I can, and use different GAPPS in the build
TCUofficial said:
EDIT: Flashing FlashKernel fixed the touchscreen issue, however Google Services Framework is now force closing. constantly. Going to rebuild with FlashKernel if I can, and use different GAPPS in the build
Click to expand...
Click to collapse
glad you are having more success than i did initially Enjoy
UPDATE: Flash gives me the Kernel headers issue, however I still need to flash the zip for touch. Google Services Framework is still acting stupid, so I'm going to try and build without the PixelGapps vendor. If successful, it should work fine if we flash the Gapps after the first initial boot of the ROM. I'll test MindTheGapps, OpenGapps, BeansGapps, etc and find the most stable out of all of them for the ROM. If the rom works and is stable(Nothing obviously broken) I'll add a Google Plus link in my signature and post another update. For now, I cannot post on XDA as DU is thoroughly against it.
TCUofficial said:
For now, I cannot post on XDA as DU is thoroughly against it.
Click to expand...
Click to collapse
why is DU against posting builds on xda?
munchy_cool said:
why is DU against posting builds on xda?
Click to expand...
Click to collapse
No clue, the closest they have gotten to actually posting was announcing builds were available for Taimen and having users from XDA test the builds. Other then that, they are strongly against it for reasons unknown
Related
This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015
Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!
Quick Change Log
10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
12/19 - Updated my Flo builds to Android 5.0.2_r1
12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot
Additional Downloads
Root by @Chainfire HERE!
Gapps for Lollipop HERE! There may be others so shop around!
Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!
@GROGG88's Special Builds are HERE!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please hit Thanks! It just as easy as hitting Download!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ubuntu 14.04 Set up and Build Guide
Updated 11/05/2014
Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!
This guide assumes the following
Have Ubuntu 14.04 setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processors.
You are not here to ask for help with Linux, only the Android build process!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Synch Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
[url]https://developers.google.com/android/nexus/drivers[/url]
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch
Build it!
Code:
make -j8 otapackage
See Build Notes and ramblings from me in post #3!
Notes
The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.
Changes from Source
Check out @GROGG88 patches HERE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Mindrocket said:
Right on Scott! Can't wait to give it a spin.
---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------
Security settings crashes says"unfortunately settings has stopped" .
Click to expand...
Click to collapse
I think its the same error some other folks are facing. Rascarlo and a few others would release their AOSP builds but it appears this blocks them from releasing. Read this over on a few pages on a few ROMs in this neighborhood.
whoamanwtf said:
I have faith in you making it work
Click to expand...
Click to collapse
Can anyone post a snippet of logcat during the crash? Particular the actually error itself.
Place it in the
Code:
box if you can.
If not I get out of work in a few hours and can look then...
mjwhirly said:
Nice to see you venturing into new projects. Most people start with CM since its not to hard to compile, but you did it the opposite way which will make all the difference in the end
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IMHO: If you dont start with the basics you will end in a mess
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
rocksyjj said:
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
Click to expand...
Click to collapse
Never used archlinux but I used Ubunutu 13.04
Here is where I started: http://forum.xda-developers.com/showthread.php?t=2224142
(I hate nano so used gedit of course. )
But at the last two shell commands i didint use the AOKP tree I used the AOSP base so you want to look here for that: http://source.android.com/source/downloading.html
Then follow the instructions from that page on forward until you have yourself a ROM :highfive:
Also pay attention to the blurb about proprietary binaries
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Click to expand...
Click to collapse
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
You fixed the security settings fc! Mind sharing how you managed to fix that?
Sent from my Nexus 7 using Tapatalk 4
scrosler said:
Also pay attention to the blurb about proprietary binaries
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Click to expand...
Click to collapse
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
vibranze said:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
Click to expand...
Click to collapse
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
scrosler said:
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
vibranze said:
Thanks Scotts, appreciated your fast response. :good:
Click to expand...
Click to collapse
Your welcome!
mpmilestogo said:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its in the OP. Post 1. I just changed the link. Happy downloading!
TheDarkDefender said:
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
Click to expand...
Click to collapse
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
scrosler said:
Your welcome!
Its in the OP. Post 1. I just changed the link. Happy downloading!
Click to expand...
Click to collapse
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
mpmilestogo said:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
Click to expand...
Click to collapse
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
scrosler said:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
Click to expand...
Click to collapse
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place .
Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.
scrosler said:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
Click to expand...
Click to collapse
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?
Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?
I'd be happy to share anything I get to know about this. Been researching about this too. Thanks.
Hi all,
Following advices from the site I successfully compiled a custom kernel from sources, rebuilt boot.img and the ramdisk and flashed it on my S3: it works.
Now I want incrementally upgrade the Linux part using git and the sources at kernel.org, let say to patch the kernel on the disk with the linux online versions 3.0.50, 3.0.51 and so on up to the latest 3.0.100. Never used git before unfortunately
Can someone please point me to an example of the correct command-line to do that? From then on I'll sort the rest by myself, I promise, that would save me a lot of time and unnecessary troubles. Thank you very much.
PU
Look up "git-cherry-pick".
reS28raM said:
Hi all,
Following advices from the site I successfully compiled a custom kernel from sources, rebuilt boot.img and the ramdisk and flashed it on my S3: it works.
Now I want incrementally upgrade the Linux part using git and the sources at kernel.org, let say to patch the kernel on the disk with the linux online versions 3.0.50, 3.0.51 and so on up to the latest 3.0.100. Never used git before unfortunately
Can someone please point me to an example of the correct command-line to do that? From then on I'll sort the rest by myself, I promise, that would save me a lot of time and unnecessary troubles. Thank you very much.
PU
Click to expand...
Click to collapse
Look up "git merge". Also you have to add the tree from kernel.org.
Mine looks like such.
git merge linux/linux-3.4.y
CNexus said:
Look up "git-cherry-pick".
Click to expand...
Click to collapse
Hi mate, I am using your tools to build the images, thanks for that. I'll do
PwnCakes193 said:
Look up "git merge". Also you have to add the tree from kernel.org.
Mine looks like such.
git merge linux/linux-3.4.y
Click to expand...
Click to collapse
Thanks, I'll investigate both of your suggestions! Today it'll be a busy day.
reS28raM said:
Hi mate, I am using your tools to build the images, thanks for that. I'll do that
Thanks, I'll investigate both of your suggestions! Today it'll be a busy day.
Click to expand...
Click to collapse
No problem
You'll probably go with the suggestion after mine, git-cherry-pick is more to add one or a couple commits, rather than a whole mass of commits
Git-merge is for adding larger chunks of commits/merging branches, etc
Just a lil' heads up:
Code:
#include
/*
* I am not responsible for bricked devices, or any problems
* that you might run into when you do these mods.
* Point your finger at me if you goof up and I'll smack you
* over the internet with my handy tennis racket.
*/
SOURCES
Kernel - Here
GPS Fix - Here
Device Tree - Here
Proprietary vendor files can be found linked in the README.md file in the device tree.
Make sure to have an unlocked boot loader before doing any of this: unlockbootloader.sonymobile.com
I've built KitKat for the Xperia L once again, this time with updated sources and a few much-awaited fixes. Most of the procedures remain the same.
I'm going to keep this thread clean and simple. Just follow the instructions and you shouldn't run into any problems.
The GPS fix may not be "complete", so please don't spam the thread with crazy insults, death threats, etc.
DOWNLOADS
boot.img - Download.
userdata.img - Download.
system.img - Download.
GAPPS - Download.
If you want the CRT lock animation, download this and flash with CWM or TWRP -
Download.
INSTRUCTIONS
cd to the directory which contains the downloaded files [ex: cd ~/Downloads] and execute the following commands (assuming you have fastboot and adb set up in your command line.) -
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
COOL STUFF AND NOT-SO-COOL STUFF
What's working?
Code:
- Wi-Fi
- GPS {kinda}
- NFC
- Camera
- Deep Sleep
- Other essentials
What's still smoked?
Code:
- Bluetooth
- Internal storage shows up as 2GB and not 4GB
CREDITS -
@raffaele88 - For the CRT Lock Animation Toggle
@Shivam Kuchhal - For the kernel
Reserved
Reserved.
Reserved
Reserved, yet again.
Does this Rom include the latest fix from Brinly? Is GPS fully working or just via WiFi and mobile network?
And some screenshots would be good.
Good to see a new rom!
what difference is there from other aosp roms ????
freakzapster said:
what difference is there from other aosp roms ????
Click to expand...
Click to collapse
It based on latest AOSP maybe (Android 4.4.2_r2)
Sent from my C2105 using XDA Premium 4 mobile app
Provide proper kernel and device tree sources and not just Sony AOSP ones so that others can see how you fixed GPS.
Also, are you sure GPS works? Brinly's fixes were incomplete, does turn by turn navigation works?
Signal Keeps resetting ???????????
Edit
I found that somethings wrong with my phone
Shivam Kuchhal said:
Provide proper kernel and device tree sources and not just Sony AOSP ones so that others can see how you fixed GPS.
Also, are you sure GPS works? Brinly's fixes were incomplete, does turn by turn navigation works?
Click to expand...
Click to collapse
Brinly's GitHub has the fixes. I am yet to test the turn-by-turn nav. I'll keep updating the OP with the latest info.
kinetic_soul said:
Brinly's GitHub has the fixes. I am yet to test the turn-by-turn nav. I'll keep updating the OP with the latest info.
Click to expand...
Click to collapse
Did you use this fix?
It's working but it's using the wifi/data to locate your location
kinetic_soul said:
Brinly's GitHub has the fixes. I am yet to test the turn-by-turn nav. I'll keep updating the OP with the latest info.
Click to expand...
Click to collapse
Do you understand that you're breaking GPL right now? Brinly's github doesn't have "sources", they're just incomplete docs for fixing GPS and if you used those fixes then I guess GPS is still broken and mobile is using WiFi and mobile network to detect location. I advise you to upload proper and latest sources on "your" git before some MOD takes some action against you.
That's true mate, You shouldn't say that this is a GPS fix because it isn't
Sent from my C2105 using xda app-developers app
All of you calm down. I've updated the OP with the details required.
Shivam Kuchhal said:
Do you understand that you're breaking GPL right now?
Click to expand...
Click to collapse
Sorry for the off-topic, but I don't think he's breaking something.
Android kernel is under GPL, but software is under Apache —meaning the developer chooses whether he/she makes the sources public.
It is just preferred in the custom ROM world that sources are out so others can modify or reuse them.
Or at least that's what I understand from here, correct me if I'm wrong.
nicholas said:
Sorry for the off-topic, but I don't think he's breaking something.
Android kernel is under GPL, but software is under Apache —meaning the developer chooses whether he/she makes the sources public.
It is just preferred in the custom ROM world that sources are out so others can modify or reuse them.
Or at least that's what I understand from here, correct me if I'm wrong.
Click to expand...
Click to collapse
Yes you're right that kernel is covered under GPL but here at xda, a developer needs to provide both kernel source and device tree and that's how power of open source prevails. You can look into any original ROM thread and you'll obviously find a proper source given there and contradictory to my advice, OP still chose not to provide any kernel source and device tree. Anyways, I am no MOD so better let a authorized person deal with this stuff.
Shivam Kuchhal said:
Yes you're right that kernel is covered under GPL but here at xda, a developer needs to provide both kernel source and device tree and that's how power of open source prevails. You can look into any original ROM thread and you'll obviously find a proper source given there and contradictory to my advice, OP still chose not to provide any kernel source and device tree. Anyways, I am no MOD so better let a authorized person deal with this stuff.
Click to expand...
Click to collapse
Nope, I need to correct you there. XDA only requires you to publish the kernel sources due to the GPL. The device tree, however, can ofc be closed source. But you also are kinda right, even though we do allow closed source stuff, we sure encourage people to make their stuff open source so other people can help bug fixing, tweaking, but also use it (if allowed).
As I can see kernel sources are provided in the OP, so there's nothing to do for me anymore, except moving it into Android Development, as this doesn't yet qualify as original dev
Cheers
Link for download removed..:/
Raj joshi said:
Link for download removed..:/
Click to expand...
Click to collapse
Fixed. Sorry about that.
The links for Google drive not work
kinetic_soul said:
Fixed. Sorry about that.
Click to expand...
Click to collapse
is a bit mess there , on first link i got boot.img, second link userdata.img say the file has been removed....nothing, the third link say system.img but you download userdata.img...and the Gapps as well say is been removed...is any chance to fix this?
watch here 1 minute to understand what i am talking about
https://www.youtube.com/watch?v=1EyN9qoEikA
So far I've got the basic A51x/A70x support added to my linux-tegra-nv-3.4 branch.
What works:
- The kernel boots
- Panel (partially?)
- USB
- Android is trying to start
Whatnot:
- everything else
So my first goal is to get display up. Currently, I've got a black screen after the bootloader logo, and the following logs:
dmesg
logcat
If anyone can help with this, hit me on hangouts, my g+ profile can be found on my xda profile. I'd appreciate any help, this would be a huge step forward for these devices.
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Shreps said:
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Click to expand...
Click to collapse
Agree on both
really awesome work
and we're already using hwcomposer.tegra.so from grouper
Shreps said:
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Click to expand...
Click to collapse
Newer ones may be needed for 3.4, dunno... also, I may have just missed something simple...
Code:
W/SurfaceFlinger( 266): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 266): no suitable EGLConfig found, giving up
...
D/NvOsDebugPrintf( 270): NvRmPrivGetChipIdStub: Could not read Tegra chip id/rev
D/NvOsDebugPrintf( 270): Expected on kernels without Tegra3 support, using Tegra2
Anyways, I'm still working on 3.1, refactoring Acer's mess with the kernel files outside the kernel files... minimizing those changes will ease 3.4 development a lot, as it's confusing to watch out for Acer ifdef's all around the kernel
Hi, any news of this project?
chacal1906 said:
Hi, any news of this project?
Click to expand...
Click to collapse
I don't have the device ATM, so I can't do anything related to this.
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Hi, great to see you back. ?
My A510 is still alive. ?
The battery is not the best anymore, but it's is always ready to test your great work.
HornetRider said:
Hi, great to see you back.
My A510 is still alive.
The battery is not the best anymore, but it's is always ready to test your great work.
Click to expand...
Click to collapse
Great, I'm in need of an A510 tester message me on Hangouts
Ziyan said:
message me on Hangouts
Click to expand...
Click to collapse
Done [emoji106]
When will we see a working version?
Hi !
It's nice to see that someone is still working on A700/510 !
I have a A700 and if you need feedback, don't hesitate !
Ziyan said:
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Click to expand...
Click to collapse
Have you abandoned the project?
I found the builds on Jenkins. I even ran them on my a700. If remove checks from the installer, they are flashed.
But the recovery does not work.
Ziyan said:
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Click to expand...
Click to collapse
sir yes sir! ancient tab is ready for reincarnation
i dont check the a700 forum often though, so if something needs eyes please quote, mention, or pm me. ill get an email and know to check back
edit: we may need a newer and functional TWRP version for some of the newer OS versions =/
Sterist said:
sir yes sir! ancient tab is ready for reincarnation
i dont check the a700 forum often though, so if something needs eyes please quote, mention, or pm me. ill get an email and know to check back
edit: we may need a newer and functional TWRP version for some of the newer OS versions =/
Click to expand...
Click to collapse
TWRP3 ready
Kaban4ik86 said:
Have you abandoned the project?
I found the builds on Jenkins. I even ran them on my a700. If remove checks from the installer, they are flashed.
But the recovery does not work.
Click to expand...
Click to collapse
A thread will be opened soon. Until then - feel free to use the aosp-6.0 builds from Jenkins (they're almost fully complete)
Ziyan said:
TWRP3 ready
A thread will be opened soon. Until then - feel free to use the aosp-6.0 builds from Jenkins (they're almost fully complete)
Click to expand...
Click to collapse
is the recovery mirrored somewhere? and what/where is this jenkins repository
Sterist said:
is the recovery mirrored somewhere? and what/where is this jenkins repository
Click to expand...
Click to collapse
jenkins.unlegacy-android.org/view/All/builds picasso2 builds…
But recovery don't work on my a700. Black screen... If press "Menu" button tablet reboots...
This sounds great, I am already running the UA build on my Nexus, time to dust of the A700 !
Kaban4ik86 said:
jenkins.unlegacy-android.org/view/All/builds picasso2 builds…
But recovery don't work on my a700. Black screen... If press "Menu" button tablet reboots...
Click to expand...
Click to collapse
what checks need to be removed?
I tried flashing with twrp 2.7.1 (newest publicly available) and ctr 3.3
twrp failed at unexpected contents (I previously wiped all partitions)
and ctr auto-rebooted in the process when I wasn't looking, and it apparently failed as well.
this was using the newest "stable" 6.0.1 build
Sterist said:
what checks need to be removed?
I tried flashing with twrp 2.7.1 (newest publicly available) and ctr 3.3
twrp failed at unexpected contents (I previously wiped all partitions)
and ctr auto-rebooted in the process when I wasn't looking, and it apparently failed as well.
this was using the newest "stable" 6.0.1 build
Click to expand...
Click to collapse
*.zip/META-INF/com/google/android/updater-script
Code:
if range_sha1("/dev/block/platform/sdhci-tegra.3/by-name/CAC", "36,0,32767,32768,32770,32849,32851,33341,65535,65536,65538,98304,98306,98385,98387,98877,106070,131072,131074,163840,163842,163921,163923,196608,196610,229376,229378,229457,229459,262144,262146,294912,294914,294993,294995,295485,313343") == "afd609f9867238c1cd370d82772817d744182c79" then
if range_sha1("/dev/block/platform/sdhci-tegra.3/by-name/CAC", "50,32767,32768,32770,32849,32851,33341,65535,65536,65538,66050,97792,98304,98306,98385,98387,98877,106070,106582,130560,131072,131074,131586,163328,163840,163842,163921,163923,164435,196096,196608,196610,197122,228864,229376,229378,229457,229459,229971,261632,262144,262146,262658,294400,294912,294914,294993,294995,295485,313343,313344") == "6b72a7b11b65c9ef1bb4c57ab78076d1ccd2e0e9" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
As the title suggests, I am porting lineageOS and keep getting this error
/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by '/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes', missing and no known rule to make it
here is the full log https://paste.myself5.de/JfHg5EA2Je.sql
I have tried re syncing the repo and re downloading the source trees. nothing seems to be fixing this.. :/
Is this problem solved?
How did u solved this issue? @nzzane
Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing
nzzane said:
Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing
Click to expand...
Click to collapse
Sry i didnt get u. What do u mean two different repos?
Sent from my AO5510 using Tapatalk
Raja_12 said:
What do u mean two different repos?
Click to expand...
Click to collapse
If there is a repo named abc at github that supports i.e. FMRadio and another named xyz, that also supports FMRadio, it is neccessary that depending files are coming from the same repo. Actually the repo from LineageOS clashes with the one from SonyLOS and vice versa.
That's, what nzzane wanted to say IMHO...
Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)
nzzane said:
Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)
Click to expand...
Click to collapse
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.
Raja_12 said:
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.
Click to expand...
Click to collapse
It depends what each repo does, and how you want to build it (stock blobs or all device tree)
nzzane said:
It depends what each repo does, and how you want to build it (stock blobs or all device tree)
Click to expand...
Click to collapse
all device tree
Raja_12 said:
all device tree
Click to expand...
Click to collapse
Then one of the repos must be conflicting somewhere :S
nzzane said:
Then one of the repos must be conflicting somewhere :S
Click to expand...
Click to collapse
Yea sometimes I can't make clean or clobber. With one repo it works with other it didn't. So I have to maintain only one repo at a time.
I ran into another issue. Can u help
target arm C: audio.primary.msm8916_32 <= hardware/qcom/audio/hal/voice.c
In file included from hardware/qcom/audio/hal/voice.c:32:
hardware/qcom/audio/hal/voice_extn/voice_extn.h:194:71: error: unused parameter 'adev' [-Werror,-Wunused-parameter]
static int voice_extn_compress_voip_set_mic_mute(struct audio_device *adev, bool state __unused)
Sent from my AO5510 using Tapatalk