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.
Related
No-name CM10.2 nightlies
NOTE: THIS IS A WORK IN PROGRESS. CONTRIBUTIONS ARE WELCOME!
(see build setup detailed below)
With that said: Welcome to the No-name CM10.2 nightlies ROM.
Who is this ROM for?
This is a ROM for people who are so eager to try bleeding edge software that they are willing to test-drive it, all bugs included, while it is being developed.
If you value a stable daily-driver with a minimum of issues over everything else, this ROM is probably not for you. There will be bugs. CM10.2 is still in early phase of development, after all.
What's working:
Wi-Fi
GPS
Headphone
All docking stuff
CM Features
AOSP Keyboard
Bluetooth
Micro SD Card & Internal storage
Launcher
Lockscreen
Auto rotate
Camera (99%)
YouTube HD playback
Unresolved, confirmed issues
Front facing camera in Camera app (works in Skype etc)
CM Focal (OMX Codec issue)
Installation:
If coming from any non-4.3.x/CM10.2-based ROM, a factory reset is very much recommended.
Although CM does have official instructions for just upgrading from 10.1.
(0. Backup your existing ROM)
1. Download latest nightly to device.
2. Download special TF101 4.3 gapps linked below.
3. Boot into recovery. TWRP is recommended over CWM.
4. Flash ROM. (This also wipes /system and any mods you already have.)
5. Flash special TF101 Gapps.
6. Reboot.
Basically, the normal procedure for any ROM.
No-name parts with extra features can optionally be installed from market.
If you feel like donating, you can install Straitjacket which is my paid app with some extra features. Plus it might give you a warm fuzzy feeling for being a good guy.
Downloads
TF101 (Wifi only) ROM is available here:
- nexfiles
TF101G ROM is available here:
- nexfiles
4.3 Gapps available here:
- Special TF101 gapps by dlumberg & josteink.
- dlumberg's mirror
Thanks to:
- The Cyanogenmod team, for all the goodies they keep on delivering, across devices.
- RaymanFX, for a CM-compatible device-tree for the TF101.
- Timduru, for KatKernel which keeps this thing stable and functional.
Issues?
Probably plenty. Help us out by reporting them here in this thread. Leave the github issue-tracker alone for now.
If you think you can fix anything, feel free to contribute. We're nice people and open to contributions.
Sources:
Android is open-source. This is an open-source project.
Cyanogenmod:
https://github.com/CyanogenMod/
Noname projects:
https://github.com/NonameROM
Kat-kernel:
https://github.com/timduru/tf101-katkernel
Build-setup:
https://github.com/josteink/android_multi-build
https://github.com/josteink/simba
Current contributors:
- dlumberg
- TheMrcool212
- ShevT
- Jostein Kjønigsen (josteink)
Changelog:
2013-08-12: Initial (preliminary) thread posted, with preliminary build instructions.
2013-08-17: Added tabletUI mods.
2013-08-17: Added TF101G build to setup.
2013-08-20: Youtube HD and Camera fixes.
2013-08-20: Added Noname top-level project on github.
2013-08-21: No longer considered experimental.
(Preliminary) Build instructions:
If you want to contribute, it's probably a good start to get your own build working.
See the instructions here:
https://github.com/NonameROM/android/wiki/Building-Noname-ROM
TheMrcool212 said:
I'm using Ubuntu 13.04 64-bit too. Maybe you had unmerged commits that causing the error.
EDIT: They had fix it:
https://github.com/CyanogenMod/andr...mmit/9de697245289afc7bb88b8e71301e2fab17a0a31
Click to expand...
Click to collapse
I can second that this issue is no longer present, but now I get things related to bionic/libc (for NetBSD!!!) instead...
Don't think it's really realated, but I just want to make sure we don't have any differences which can affect the result. What version of Java are you running?
This is mine:
[email protected]:/mnt/build/android/tf101/4.3$ java -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
Click to expand...
Click to collapse
Great to see this!! Thx Josteink.
Been fooling around with Katkiss 4.3 on a spare tf101 I have, if No-name will be like that then our beloved tf will keep on living!!!!!
Thx to all devs
Sent from my Transformer using xda premium
josteink said:
I can second that this issue is no longer present, but now I get things related to bionic/libc (for NetBSD!!!) instead...
Don't think it's really realated, but I just want to make sure we don't have any differences which can affect the result. What version of Java are you running?
This is mine:
Click to expand...
Click to collapse
This commit was the cause of the bionic/libc error. I got this before too, so i skipped that commit. I recommend to use my android_bionic repository, replace it with the current CM10.2.
https://github.com/TheMrcool212/android_bionic/tree/cm-10.2
For the java, i got the same version too:
Code:
[email protected]:~$ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.13.04.2)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
What's working (Tested on my own stock CM10.2 build)
Bluetooth
Dock battery & keyboard layout.
USB Dock (Only tested with pendrive) & SD Card
Micro SD Card & Internal storage
Launcher
Lockscreen
Auto rotate
Confirmed issues
AOSP Keyboard crashes on certain time, even when not using it
Camera & CM Focal
Weird window animation bug when going to home screen.
Back button doesn't work, even on keyboard (I used pie instead)
Menu button, even on keyboard too.
What's not confirm yet to be working
Wi-Fi (due to keyboard issue)
GPS (No Wi-Fi access)
The build of mine and him are just the same, since we are using the same repositories.
TheMrcool212 said:
This commit was the cause of the bionic/libc error. I got this before too, so i skipped that commit. I recommend to use my android_bionic repository, replace it with the current CM10.2.
https://github.com/TheMrcool212/android_bionic/tree/cm-10.2
For the java, i got the same version too:
Code:
[email protected]:~$ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.13.04.2)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Click to expand...
Click to collapse
Cool. Fixed it. Uploading build now
TheMrcool212 said:
What's working (Tested on my own stock CM10.2 build)
...
lots of useful info
...
Click to expand...
Click to collapse
Awesome. Copied to FP!
Added this ROM to the general build setup.
Will find out if it works tomorrow
i will still stick with your wonderful 10.1 rom but thank you for your hard work.
The tf 101 community despite some problems is legendary in its character.
Sent from my Transformer using xda premium
karapoutsoglou said:
i will still stick with your wonderful 10.1 rom but thank you for your hard work.
The tf 101 community despite some problems is legendary in its character.
Sent from my Transformer using xda premium
Click to expand...
Click to collapse
+1, but will follow this thread with more than average interest
Note top self/personal reminder:
- try flashing Google keyboard on top of AOSP keyboard.
- try building with non generic cpu variant which is not cortex-a9 from twrp device tree. Might be better than generic and still work.
Sent from my Galaxy Nexus using Tapatalk 4
josteink said:
Note top self/personal reminder:
- try flashing Google keyboard on top of AOSP keyboard.
- try building with non generic cpu variant which is not cortex-a9 from twrp device tree. Might be better than generic and still work.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Google keyboard works perfectly for me using banks gapps.
@josteink Just want to tell you:
I made a branch called " tf101g-jellybean_4.3 " , based on ShevT's TF101G device tree. I've merged all of 4.3 commits from TF101 branch to the TF101G branch as well. We'll start making this ROM for 3G version as soon as the ROM for TF101 version are quite stable.
diogo.sena said:
Google keyboard works perfectly for me using banks gapps.
Click to expand...
Click to collapse
Where's the banks gapps, can you give me the link for it?
TheMrcool212 said:
@josteink Just want to tell you:
I made a branch called " tf101g-jellybean_4.3 " , based on ShevT's TF101G device tree. I've merged all of 4.3 commits from TF101 branch to the TF101G branch as well. We'll start making this ROM for 3G version as soon as the ROM for TF101 version are quite stable.
Click to expand...
Click to collapse
Agreed.
I just think letting @ShevT open up his repo and give us commit access would be "cleaner". We'll see when he discovers this thread and wants in on the action
TheMrcool212 said:
Where's the banks gapps, can you give me the link for it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2012857
Should probably be added to FP. I'll get it done.
I know the original gapps (4.2 no-name ROM version) Google keyboard had some issues, but the newly released Google keyboard from the play store worked fully on the 4.2 no-name ROM. Not sure if there is a newer gapps which now contains that same keyboard or if it needs to be installed from the play store?
Sent from my Nexus 4
diogo.sena said:
Google keyboard works perfectly for me using banks gapps.
Click to expand...
Click to collapse
Can you confirm if wifi or GPS is working then? Will make the list on the first page easier for people to rate
And what version did you use? The 4.3 version?
I just flashed the banks' 4.3 Google Keyboard. Now i can have access to my Wi-Fi and here's the update:
Wi-Fi is working
GPS working too!
All dock functions are working when flashing the banks' Google Kayboard gapps
Back, menu and recents button are working (I'm not sure why this had been fixed, maybe due to the working keyboard)
No AOSP keyboard crashes.
New issue
YouTube doesn't play when HD is enabled, only when it's been disabled.
What's left
Camera & CM Focal
Weird window animation bug when returning to home screen.
YouTube player issue.
@josteink, I think we need to revamp the gapps, since some of the apps are not updated like the keyboard, PlayStore, Google Search etc.
TheMrcool212 said:
I just flashed the banks' 4.3 Google Keyboard. Now i can have access to my Wi-Fi and here's the update:
Wi-Fi is working
GPS working too!
Click to expand...
Click to collapse
Yes, only wifi droped one at restoring all the apps from Google, while loading the app store. After that no problems with wifi.
TheMrcool212 said:
New issue
YouTube doesn't play when HD is enabled, only when it's been disabled.
Click to expand...
Click to collapse
Is same as on KatKiss http://forum.xda-developers.com/showpost.php?p=44274292&postcount=2
Using TWRP 2.3.2.3
I did a cache, and system wipe, factory reset and flashed the rom with the Banks Gapps, just the core.
Main issue: lost root privilages. Otherwise: feels already as a matured rom
---------- Post added at 09:16 AM ---------- Previous post was at 09:09 AM ----------
pinkdot;44604445
Main issue: lost root privilages. [/QUOTE said:
Ah, got root back by changing the settings
Click to expand...
Click to collapse
AOSP 4.3 (JSS15Q) for all S4 Devices!
Always wanted AOSP 4.3 on your device? A clean AOSP with no modifications. Get your chance now and compile it for your S4 device.
If you like the output you can use this AOSP 4.3 base as a custom rom base. (because it's more fun to build your rom on aosp 4.3 then on cm 10.2)
A month ago I started a project to get AOSP 4.3 working on the S4 i9505 (jfltexx), I succeeded and the result is very good The only known bug so far is that HDR pics cannot be taken and possible problems with wifi (general bug of JSS15Q). I just added all other device specs of the S4. I haven't tested it because it simply takes to much time to compile for them all. but I can ensure all S4's with a snapdragon will have pretty few bugs. But the i9500 will be worse of course due its just added to cm10.2.
The only additions done to the build are the advanced device settings (from cm-10.2) and that the kernel is upgraded to latest linux kernel version and it has support for undervolting (because some s4's get way to hot). the rest is all stock! (as far as possible)
I hope you guys enjoy a CLEAN AOSP 4.3 as much as I do
Performance/Battery is most likely better then CM10.2
Check original jfltexx topic: http://forum.xda-developers.com/showthread.php?t=2397511
Devices:
- jfltecsp
- jfltespr
- jfltetmo
- jflteusc
- jflteatt
- jfltevzw
- jfltecan
- jfltexx (main device)
- jfltecri
- i9500 (very alpha)
Download Source:
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u git://github.com/AOSP-S4/aosp_manifest -b jb-4.3
repo sync
Building:
For jfltexx:
Code:
./build.sh
for all other variants:
Code:
. build/envsetup.sh
lunch (choose device)
make otapackage -j5
if you really like this project you can consider donating me to stimulate the development
Important Information
These 2 things are extremely important. don't ignore them!
Camera Pictures Issue:
If your linux username is longer then 9 chars taking pictures with the camera will not work!. You need to have a username that is below 9 chars. this is for build.prop. Why you say? Because due to some flaw in bionic optimization that give errors when "strlen" exceeds a number of characters (this is what it seems)
This will NOT work:
Code:
ro.build.display.id=full_jfltexx-userdebug 4.3 JSS15Q eng.[b]broodplank[/b].20130831.035629 test-keys
ro.build.version.incremental=eng.[b]broodplank[/b].20130831.035629
This WILL work:
Code:
ro.build.display.id=full_jfltexx-userdebug 4.3 JSS15Q eng.[b]brood[/b].20130831.035629 test-keys
ro.build.version.incremental=eng.[b]brood[/b].20130831.035629
Dalvik Cache Issue:
Due to the previous state of the ROM (haven't fixed this so far), it cannot write dalvik-cache in /cache so /data is used instead. There for you need to have this line in build.prop to make it work:
Code:
# temp fix for dalvik-cache
dalvik.vm.dexopt-data-only=1
Reserve just in case
big ups brotha! i know you have been working hard on this.
sa1tine said:
big ups brotha! i know you have been working hard on this.
Click to expand...
Click to collapse
Thank you, yes I have been I was able to do it because I had holiday, I worked approximately 250 hours on it I think. but it was definitely worth it Only real issue left is taking HDR pictures
it is much appreciated! i am placing an order for my s4 tonight. maybe i will be able to help ya out when i get it.
sa1tine said:
it is much appreciated! i am placing an order for my s4 tonight. maybe i will be able to help ya out when i get it.
Click to expand...
Click to collapse
Cool which one are you getting? And I got most things fixed, just need people to try and compile it for their own device
the m919
---------- Post added at 05:42 AM ---------- Previous post was at 05:40 AM ----------
i have a buddy that has an att variant so ill build for that one as well.
sa1tine said:
the m919
---------- Post added at 05:42 AM ---------- Previous post was at 05:40 AM ----------
i have a buddy that has an att variant so ill build for that one as well.
Click to expand...
Click to collapse
which one is that? jflte*** ?
I know the att one is jflteatt but which one is m919?
tmobile
sa1tine said:
tmobile
Click to expand...
Click to collapse
ah idd, see it now.
SGH-M919 (jfltetmo)
twerkin
http://www.muddy.dsskcorp.com/images/screen1.png
sa1tine said:
http://www.muddy.dsskcorp.com/images/screen1.png
Click to expand...
Click to collapse
Cool
Do you encounter many bugs? or the same that I listed in OP?
noop! it built well.
]i also got a good build for the t989, that needs a little work, getting su on it is being stubborn.
sa1tine said:
noop! it built well.
]i also got a good build for the t989, that needs a little work, getting su on it is being stubborn.
Click to expand...
Click to collapse
https://github.com/AOSP-S4/android_...mmit/ad504b5ed439eb1a7503acb8c22958adcec860e3
that enables su, it should be in the kernel
We are working through various little compiling errors with vzw version. If you want we can send you a list of everything once we get it to build properly.
We are trying to get to a clean aosp core to build on top of. Thanks for all your hard work brood!
sent from my Verizon Galaxy sIV
broodplank1337 said:
https://github.com/AOSP-S4/android_...mmit/ad504b5ed439eb1a7503acb8c22958adcec860e3
that enables su, it should be in the kernel
Click to expand...
Click to collapse
i had a sneaking suspicion it was the kernel.
this may sound naive and stupid. during the build process why not install everything that goes into data and move it into cache/dalvik-cache and create a symlink
like here http://forum.sdx-developers.com/index.php?topic=7235.0
sa1tine said:
this may sound naive and stupid. during the build process why not install everything that goes into data and move it into cache/dalvik-cache and create a symlink
like here http://forum.sdx-developers.com/index.php?topic=7235.0
Click to expand...
Click to collapse
The thing is that this is a another workaround. I need to solve the problem at the bone, not adding many workarounds
i hear ya. i started reading around and it became clear this would be redundant
******* Hi all ********I have developed this little tool containing a few utilities that should help anyone do a host of stuff like building Cyanogenmod..Compiling kernels..Play with ADB..GIt tools..etc
DARK_Multitool1.0
My tool is divided into five Modules(More to come in future if people find it useful)
Module 1 : CyanogenMod Tools
- Installing the necessary libraries for compiling Cyanogenmod
- Initializing your repository and getting the Cyanogenmod source code
- Getting prebuilt apps/Device proprietary blobs
- Building Cyanogenmod for your device
Module 2 : ADB tools
- Creating logcat to debug your phone
- Installing apps via ADB
- Push/Pull stuff to/from your android device
Module 3 : Kernel tools
-Sony Kernel
Unpack Kernel Source
Create zImage of various devices(any Xperia)
Extract kernel.sin from ftf file
Unpack kernel.sin(to get zImage and ramdisk)
Make dt.img(For Xperia Z1 and Z ultra)
Make kernel.elf or boot.img depending on device
Test your kernel.elf/boot.img without flashing fully(Test run)
-Nexus Kernel
Getting the source code
Checkout the source code
Building zImage
-Samsung kernel
(Is under development as i develop for Xperia devices and not too familiar with samsung atm)
-Download toolchains
-Unpack boot.img to get zImage and Ramdisk
pearl script unpack or umkbootimg unpack
-Unpack or Repack ramdisk
-Build zImage for a generic kernel(Experimental)
-Take kernel log : Thanks @ricky310711 for the commit
Module 4 : Backup TA partition for Sony or EFS partition on samsung
-Backup TA partition for Sony(By dd Method only)
-Backup or restore efs partition for Samsung(tar or dd method)
Module 5 : GIT tools
-Download GIT package on your linux
-Change directory where you want to initialize git
-Git repository setup(New git setup/Changes to old git setup)
-Update your local and remote git repository
-Commit your additions/deletions
-Push/Pull to/from your github repository
-Automatic push commits to your repository(After git setup is done)
-Download any repository using GIT
Download link
Dark_multitool1.0(With Update 1)
Update 2 added...Will upload soon..You can download this and update via tool to the latest version
Its better to download from XDA DevDB. You can either use the link above or click on downloads on top of the thread to download
How to install??
Download the tar.gz file from the link above..Place it in your home directory and run the following command in your terminal
tar -xjvf dark_multitool1.0.gz
How to run it??
cd to the folder dark_multitool1.0 and type ./menu in your terminal and execute
This tool is only for any linux based distro(Ubuntu,fedora etc) atm and i dont know if it will work in cygwin(Tested on Cygwin by kevinrus123 : Some utilities are working)
You can install vitualbox and install ubuntu or any other linux based distro to use the tool if you are running windows
Credits
-xda and its wonderful devs for teaching me everything
-Doomlord for his exceptional threads and tutorials on Xperia devices
-Rickwyatt and Rekoil for Ta partition backup tutorial for Xperia
-Google.com
If i have forgotten anyone then please let me know
Donations
Running a 512 mb laptop with a semi crashed hard disk.....So any kinds of donations are welcome if you like the tool
>Just donate to my email ID : [email protected]
>I am from India..so personal payment wont work
>Select buy me goods/services and it should work
>You can donate via tool as well.....
Sources
My github source : https://github.com/Smk1989/dark_multitool1.0
Mods : Please Move the thread if its in the inappropriate section
Updates
Latest update = Update 1
-I will keep the thread updated with the latest tool and you can also update the tool through the tool itself
FAQs in the second post
Changelogs in the third post
XDA:DevDB Information
[TOOL][ANDROID]Dark_Multitool-CyanogenMod building.kernel developMent.ADB tool..etc.., a Tool/Utility for the Android General
Contributors
Dark Wraith
Version Information
Status: Alpha
Created 2013-12-11
Last Updated 2014-01-03
FAQs
>Why is it giving errors while compiling zImage for Xperia devices????
Answer : You need to add the various makefile and defconfig fixes for the toolchain to work properly
Please refer to this excellent thread by doomlord for various fixes
http://forum.xda-developers.com/showthread.php?t=2447310
>TA partition and EFS partition backup doesn't work properly
Answer : Please remember to specify the memory block correctly. If you still get an error then please tell me the error so that i can check if the error is from the tool's end
>How to add a toolchain????
Answer : Add it under android_toolchains folder in your home directory
Open the tool and navigate to toolchain_selector script under scripts folder
Add the toolchain name and the correct path as given there in the following format
toolchain_name[the number after the last toolchain name]=
toolchain_path[the number after the last toolchain path] =
>How to clean your kernel or Cyanogenmod work directory?
Answer ; Navigate to the kernel or Cyanogenmod work directory and type in Terminal : make clean
I will incorporate this in the next release
>Download toolchains or update tool doesnt work
Answer : make sure you have the git package installed. You can install from the tool itself under GIT tools
>Libraries missing while compiling kernel or cyanogenmod build errors on 64 bit machine??
Answer : Download libraries from cyanogenmod import libraries option( I will incorporate this in the next release) and for 64 bit compile error type : BUILD_HOST_32bit=1(Fixed and added in update 1)
Bugs and Suggestions
Please let me know
Changelogs
Update 2
>Added Xperia J in the build list of the tool
>Added Take kernel log in kernel options..Thanks @ricky310711 for the commit
>Added dry run option for Sony
-Lets you test your kernel.elf/boot.img(In case the kernel doesnt boot up..just restart phone and try again)
Update 1
>Cm-11.0 branch added while initializing repo(thanks mithun shanoj for the commit)
>Added umkbootimg unpack method
>Added import libraries option
>Added BUILD_HOST_32BIT=1 for 64 bit machines
Last one
No one tried??
Sent from my Micromax A110 using xda app-developers app
Maybe I am blind but where do I get the download?
Download Link?
Dude where is the download link???
I had always been waiting for a tool like this one. Great job :good:
---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------
Dovidhalevi said:
Maybe I am blind but where do I get the download?
Click to expand...
Click to collapse
adityak74 said:
Dude where is the download link???
Click to expand...
Click to collapse
To download, sync this repository
https://github.com/Smk1989/dark_multitool1.0
Thats it. navigate to the local repository and run run menu from terminal
Well well well.:beer: cheers.
Dovidhalevi said:
Maybe I am blind but I'll alwhere do I get the download?
Click to expand...
Click to collapse
rhar**** said:
I had always been waiting for a tool like this one. Great job :good:
---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------
To download, sync this repository
https://github.com/Smk1989/dark_multitool1.0
Thats it. navigate to the local repository and run run menu from terminal
Click to expand...
Click to collapse
adityak74 said:
Dude where is the download link???
Click to expand...
Click to collapse
Guys see the download tab on top of the thread.. I'll also add a download link if u want
Edit: Added a download link to the post
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Sent from my Nexus 4 using Tapatalk
welcome to the world of kitchen creators goodjob!
Nice job man ?
Sent from my Nexus 7 using Tapatalk
Daniel_GT said:
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Dark Wraith said:
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..
i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Click to expand...
Click to collapse
actually i learnt alot by viewing the content of tools, viewing it in raw format and learning how things work.
it encouaged me to find a way to make a kitchen for windows users and noobs.
so i guess im the perfect example
Daniel_GT said:
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Click to expand...
Click to collapse
You have every right to express your opinion, but that being said, your post makes you sound like a real elitist, one who's upset that his elevated place in the exclusive club is about to be disrupted by those "filthy ruffians" who didn't earn their developer's chops by clawing their way up from the gutter. In my opinion, anything that brings in more developers to the community is a good thing. Sure, there are going to be plenty who use this tool as a shortcut to doing any hard work, but there are going to be those who use it as a starting point to further their knowledge of ROM building and modifying. Everyone needs a place to start, after all, but implying they'll never be "one of the boys" without beating their head bloody against a desk isn't at all helpful. Dark Wraith should be commended for creating a tool that will help bring new blood into the community.
Dark Wraith said:
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Click to expand...
Click to collapse
That's one side of the argument, if you re-read the first several pages of @championswimmer's kernel kitchen thread you'll be reminded just how strongly some people feel about this... I'm not in either camp by the way.
My point is that xda is not what it was, if we continue to post toolkits here it will only dilute the pool of serious development further. You just have to dive into an official CM Dev thread (N4 is a good example) at any point and browse, say, 25 pages to see exactly what I'm talking about...
For every one person that takes your tool, pulls it to bits to figure out how it works and goes on to do their own original work and contribute back, I feel sure that there'd be many more that just go ahead without any real understanding of what they're doing, expecting you and I to bail them out when it goes wrong... I hope that's overly cynical but, ironically, from evidence I don't think that is.
Your toolkit might have a place, and again all credit to you for putting it together. Personally I believe it's more hand holding (even more so than ROM or kernel kitchen) which ultimately helps no one.
Sent from my Nexus 4 using Tapatalk
hey dude., i have a question
* (my device doesn't support CM) can i use this tool for building CM for my device?
Thanksssss
Good stuff
Sent from my Nexus 5 using Tapatalk
Marsealdelo said:
hey dude., i have a question
* (my device doesn't support CM) can i use this tool for building CM for my device?
Thanksssss
Click to expand...
Click to collapse
no bro..its not about support. Cm11 can run on ur device and you can build for it provided that you have the kernel source of your device available..For officially supported devices you will have the kernel source in cyanogenmod repository. For a device with no kernel source you cannot build cyanogenmod. What you are talking about is cyanogenmod porting to an unsupported device. Take a look around in cyanogenmod's wiki. I might add porting options in the tool in future but atm you can build only for offcially supported devices
Overview:
Code:
[B]Experimental CyanogenMod 12.1 compiled with [URL="http://releases.linaro.org/14.10/components/android/toolchain/4.9"]Linaro 4.9 (14.10) Toolchain[/URL].[/B]
This is CyanogenMod 12.1 built straight from source with Code Review
cherry-picks and my own custom device trees and kernel.
CDMA carrier setup:
The following only needs to be done once to allow init to properly setup your carrier specific system properties.
This will set ro.boot.carrier to your specific carrier identifier and will persist through future flashes of this ROM.
Code:
From the bootloader issue the following commands depending on your carrier:
'fastboot oem config carrier verizon' (Verizon)
'fastboot oem config carrier pageplus' (Page Plus)
'fastboot oem config carrier reliance' (Reliance Mobile)
'fastboot oem config carrier sprint' (Boost Mobile)
Builds:
CM-12.1 06-08-2015 (MD5: (2414f09586228eb94bcda47c1f149ed0)
MMS Flashable Zip Fix Thanks @starkly_raving @Alberto97
TK Gapps Mini Modular 5.1 (05-30-2015)
Build Archives
Source Code:
codyf86/android_device_motorola_falcon
codyf86/android_device_motorola_msm8226-common
codyf86/android_kernel_motorola_msm8226 (Stock CM kernel Not even stock anymore kernel xD)
Code Review Cherry-Picks: (Latest build)
healthd: Use android blue for charge percentage
PowerManagerService: Fix updating of mUserActivitySummary
Add option to set default custom function to button recents (1/2)
Add option to set default custom function to button recents (2/2)
cmsdk: do not crash system if CustomTileListenerService isn't present
Note: When Items drop off the above list 9/10 they have been merged.
Changelog:
Code:
I don't believe in change logs; I believe in Github.
Please look above at the Code Review and also through
the source code commits to see what's changed.
The proof is in the [STRIKE]pudding[/STRIKE] Github.
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Yummy. Also trying this out for sure.
Edit: Sub'd, Muuahahaha!....Oh.
starkly_raving said:
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Click to expand...
Click to collapse
Feel free to post logs / bugs here. Mainly have time to build after work on weekdays. On the weekends is when I can actually work on fixing things.
For device specific things just post the bugs / logs here. For CM specific bugs I would use JIRA and post a link to the bug here. (More helpful/useful to the CM team to make an actual JIRA bug report.)
3 WORDS: STABLE AS ****!
thanks for the rom, this will forsure be my daily driver. only little problem is the no service icon (xt1031) but data is working. soft reboot fixes it though!
Can anyone please comment on the speed of this ROM since it is Linaro based? The other 5.1 ROMs on my phone are pretty responsive, but if even more speed can be gained with our limited hardware, that will be great.
@CodyF86,
Having a problem with the download link. Rom starts downloading but does not download the whole 251mb. Only partial download. Tried about ten times but still same result. Tried with a different browser but same result.
Edit: Nevermind. Downloaded the rom from my phone and copied it from download folder on phone to internal storage.
Hello there @CodyF86 ! Thanks for you work! One little request. Do you think you will be able to add a mirror or upload your work to another claudbased storage? Like MEGA or Mediafire or AndroidFileHost or whichever you want. This one you are using is insanely unstable for me. It gets interrupted every 5 minutes. I'll be really glad if you could change it or add other(s).
Cheers.
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
CodyF86 said:
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
Click to expand...
Click to collapse
Thank you very much! And sorry for bothering you with this. I really want to test your ROM since al Linaro builds seem gone from this forum. Thanks again. Drive safe
Cheers.
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
CodyF86 said:
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
Click to expand...
Click to collapse
thanks for both: new link and new build Can I dirty flash it over the build before? Just installed the first release lol
Cheers.
I've been dirty flashing; should be good to go.
Update: yes, this ROM is very fast indeed! Thanks for sharing.
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
starkly_raving said:
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
Click to expand...
Click to collapse
Same here. great work! Not as many customizable like other 5.1 based out there, but is enough fast and stable. Thanks.
just wondering what recovery you are using and do partitions need changed from stock?
What models are supported?
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Shawnsch said:
just wondering what recovery you are using and do partitions need changed from stock?
Click to expand...
Click to collapse
CWM 6.0.5.1 I think 6.0.4.7 is the last one posted on CMs website, I'll post the latest one in the OP tonight, but they're basically the same. Nothing needs to be changed from stock.
Orjakone said:
What models are supported?
Click to expand...
Click to collapse
Theoretically they all should work, but I need someone to the GSM version to try it out.
The_Poison said:
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Click to expand...
Click to collapse
Weird, I haven't noticed that, but tbh I haven't actually payed attention to what year my phone shows / I don't even have it set up to show me I'll have to look and see if mine does it also.
Will do another one tonight / it's the weekend can play around with it get some things done now.
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