There have been two submissions to CM code review (31787 here and 31039 here) that have not been merged for various reasons. The first allows for sysfs gamma control (at kernel level) and the second provides an additional menu in settings containing RGB display controls and vibration settings. At present there is no support within the CM vanilla system UI settings to modify gamma values (with or without MakoParts), though there are apps (notably Faux123's) that will provide this in concert with a kernel including a sysfs interface that allows it. These are potentially very complex adjustments and not really of interest to the majority of device users, however there does seen to be an appetite for a slimmed down alternative. I (and others) have been cherry-picking the two code commits and using init.d to provide a simple solution, though on top of that it does seem that a GUI setting method would be of value, if only to fiddle with levels prior to settling on values to include in a boot script.
Consequently, I have extended the original MakoParts (MakoParts+ if you will!) in adding a basic 6 value gamma (amplitude) control UI within the existing 'Advanced' menu.
To implement it in your own builds you will need to;
Cherry-pick the two code review commits (see above), if you haven't already (UPDATE 24/05/13 - Use Patch Set 6 for change 31039). Alternatively, you can get them from my repo here for the kernel and here for the device. This gives you the original MakoParts and the gamma support.
Cherry-pick MakoParts+
Cherry-pick hev88's commit here (UPDATED 09/07/13 - redirected link) to allow your settings to stick following reboot.
and then make.
Gamma settings will not stick following a reboot so once you've found some you like you'll need an init.d/ userinit.d script. There's a good guide on _motley's thread here though do make sure that you refer to kgamma_r. kgamma_g and kgamma_b rather than kgamma_red, kgamma_green and kgamma_blue (those are franciscofranco's interface variables I believe).
(UPDATE 04/06/2013 - Thanks to hev88 for spotting my original omission. His commit (now 3. above) will stick your settings following reboot.)
As I mentioned, gamma control can be very in-depth and this is not intended as an alternative to a full blown control app. Saying that, there is valuable reading to be done and user comments in Ngo93's thread here and tested settings in the accompanying spreadsheet (Basic tab) here
Thanks and acknowledgement to all mentioned.
Evaluation Build
I have provided a download link to a (fairly) vanilla CM10.1 build of my own including the modifications - https://www.dropbox.com/s/ebb7iteqo1ov5yn/cm-10.1-20130514-UNOFFICIAL-mako.zip
Have never CP'd from Github before. Using https://github.com/Daniel-GT/android_device_lge_mako/commit/8793e557c1acba7b7f951fced0a4eae25d28a6f4 as an example, after repo sync, would I do the following:
Code:
cd ~/cm10.1/android_device_lge_mako
git remote add https://github.com/Daniel-GT/android_device_lge_mako
git fetch
git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4
Cheers.
CMNein said:
Have never CP'd from Github before. Using https://github.com/Daniel-GT/android_device_lge_mako/commit/8793e557c1acba7b7f951fced0a4eae25d28a6f4 as an example, after repo sync, would I do the following:
Code:
cd ~/cm10.1/android_device_lge_mako
git remote add https://github.com/Daniel-GT/android_device_lge_mako
git fetch
git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4
Cheers.
Click to expand...
Click to collapse
Easiest way is;
Code:
git fetch git://github.com/Daniel-GT/android_device_lge_mako.git && git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4
As Andrew said on Google+ you could also patch with git am... if you get really stuck you could apply the following;
Code:
git apply <your-path-to-the-attached-file>/MakoPartsPLUS.patch
All should be run from a terminal opened in your source "mako" directory. Make sure you have the original MakoParts in your source already or it won't work.
Daniel_GT said:
Easiest way is;
Code:
git fetch git://github.com/Daniel-GT/android_device_lge_mako.git && git cherry-pick 8793e557c1acba7b7f951fced0a4eae25d28a6f4
As Andrew said on Google+ you could also patch with git am... if you get really stuck you could apply the following;
Code:
git apply <your-path-to-the-attached-file>/MakoPartsPLUS.patch
All should be run from a terminal opened in your source "mako" directory. Make sure you have the original MakoParts in your source already or it won't work.
Click to expand...
Click to collapse
needs rebase now to go with new patch set http://review.cyanogenmod.org/#/c/31039/
hev88 said:
needs rebase now to go with new patch set http://review.cyanogenmod.org/#/c/31039/
Click to expand...
Click to collapse
I'll look at it and review. I had thought the original commit was done with changes.
Sent from my Nexus 4 using xda app-developers app
Daniel_GT said:
I'll look at it and review. I had thought the original commit was done with changes.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. So did I. Just a name change really and dropped a few strings. I tried to mod your patch but I keep getting an error on strings.xml
Sent from my Nexus 4
hev88 said:
Yeah. So did I. Just a name change really and dropped a few strings. I tried to mod your patch but I keep getting an error on strings.xml
Sent from my Nexus 4
Click to expand...
Click to collapse
On initial inspection I can't see anything fundamentally "new" in Patch Set 7 or 8. I've asked the committer for his rationale on Gerrit. I don't think there are any conflicts with any/ all recent CM commits so you should be OK if you pick set 6 (or the commits from my repo) for the timebeing until I've looked at it properly - OP temporarily updated.
Daniel_GT said:
On initial inspection I can't see anything fundamentally "new" in Patch Set 7 or 8. I've asked the committer for his rationale on Gerrit. I don't think there are any conflicts with any/ all recent CM commits so you should be OK if you pick set 6 (or the commits from my repo) for the timebeing until I've looked at it properly - OP temporarily updated.
Click to expand...
Click to collapse
I've compared Patch Set 6 side-by-side with 7/8 and the update does nothing more than clean up a bit (which I've already done within MakoParts+), re-base (basically reference it against the current CM repo timeline, the original is from January) and change the package name and a UI heading. I'm not minded to apply the changes to MakoParts+, I see little point in doing so until the committer tells me what he had in mind other than change for changes sake, so please either;
Stick with patch 6 and disregard 7/8 entirely. This will effect the functionality of MakoParts and MakoParts+ not a jot.
Cherry-pick the original commits from my repo as before, and forget all about this.
I've attached the two diffs if anyone wants to have a look and see what I mean.
im sure its not just me but it seems you have to add some code to DeviceSettings/src/com/cyanogenmod/settings/device/Startup.java in order for settings to stick on reboot:
GammaTuningPreference.restore(context);
not sure if more is needed but i just noticed today that settings today that it doesnt stick after reboot and decided i woud take a look.
Just made a fresh build and adding that keeps your settings after a reboot.
Sent from my Nexus 4
hev88 said:
Just made a fresh build and adding that keeps your settings after a reboot.
Sent from my Nexus 4
Click to expand...
Click to collapse
Well spotted, sometimes you get so close to these things you can't see the wood for the trees. Have you added the line via a separate commit on your own repo, and are you still using the MakoParts project name (you mentioned DeviceSettings)? If so I'm happy to update the OP with a link to your work.
Sent from my Nexus 4 using Tapatalk 4 Beta
Daniel_GT said:
Well spotted, sometimes you get so close to these things you can't see the wood for the trees. Have you added the line via a separate commit on your own repo, and are you still using the MakoParts project name (you mentioned DeviceSettings)? If so I'm happy to update the OP with a link to your work.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It was a copy pasta error on my part I still use the patch you made and just now manually added the fix to survive a reboot to source code. I started to make a new patch for DeviceSettings but I got stuck on one part... I am not to great at git Lol, I got stuck on strings.xml and kinda gave up... But it is just a one line fix on top of your patch that you made.
Sent from my Nexus 4
hev88 said:
It was a copy pasta error on my part I still use the patch you made and just now added the fix to survive a reboot. I started to make a new patch for DeviceSettings but I got stuck on one part... I am not to great at git Lol, I got stuck on strings.xml and kinda gave up... But it is just a one line fix on top of your patch that you made. I can send you what I have so far later tonight or tomorrow after I finish catching up on some Dexter
Sent from my Nexus 4
Click to expand...
Click to collapse
OK Don't worry, I'll add the change as a new commit and credit you.
Sent from my Nexus 4 using Tapatalk 4 Beta
https://github.com/hev88/android_device_lge_mako/tree/cm-10.1-var1/MakoParts
i just added the one line to keep settings after reboot... im exploring right now trying to figure out how to git around here lol... but if you dont get to it anytime soon ill try to make your patch play nice with the most recent patch set on CM's gerrit... gotta start learning some time, this will be my new project on my days off. i just stomped out a bug on ubuntu so this will keep me occupied for the time being
#VinoIsEvil
OP updated.
Daniel_GT said:
OP updated.
Click to expand...
Click to collapse
sent you a pull request on github. repo works fine but it wont let me cherry-pick it my commit... might have missed something while adding commit from terminal but it builds fine
hev88 said:
sent you a pull request on github. repo works fine but it wont let me cherry-pick it my commit... might have missed something while adding commit from terminal but it builds fine
Click to expand...
Click to collapse
You have been busy! I'll have a proper look over the next few days... I don't really follow your cherry-pick problem? Are you trying to fetch from the SSH address, not the public git/ HTTPS URL?
Sent from my Nexus 4 using Tapatalk 4 Beta
Daniel_GT said:
You have been busy! I'll have a proper look over the next few days... I don't really follow your cherry-pick problem? Are you trying to fetch from the SSH address, not the public git/ HTTPS URL?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i have it the same as you do on the previous page. if i remember right it said something about cherry-pick failed no HEAD?
idk i gave up on that and just forked cm, cherry-picked latest mako parts commited it to repo edited it based on your patch and just replaced cms device repo with my in my build directory now its two less cherries i have to pick before i build. like i said im still new at this whole github deal so it could just be me not being patient
Daniel_GT said:
You have been busy! I'll have a proper look over the next few days... I don't really follow your cherry-pick problem? Are you trying to fetch from the SSH address, not the public git/ HTTPS URL?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
hev88 said:
i have it the same as you do on the previous page. if i remember right it said something about cherry-pick failed no HEAD?
idk i gave up on that and just forked cm, cherry-picked latest mako parts commited it to repo edited it based on your patch and just replaced cms device repo with my in my build directory now its two less cherries i have to pick before i build. like i said im still new at this whole github deal so it could just be me not being patient
Click to expand...
Click to collapse
Not sure if you're talking about something else but I've been cherry-picking your commit with no problem using
Code:
git fetch git://github.com/hev88/android_device_lge_mako.git && git cherry-pick 17dfcbdc60719bb0147240efcbb906f4987c95fa
Related
Obviously, I am going to be cleaning up some bugs with the CM7 build...
But, for those of you who might be inclined to develop a CM-based AOSP ROM, feel free to check out my github source to see what's involved:
https://github.com/Hashcode
Or you can:
repo init -u https://[email protected]/Hashcode/cm4D3.git
repo sync
To pull the entire set of android files that I use for compiling the current build.
Please note that the Board Config is currently setup to generate Safestrap .zip files.
Great job
Thank you for everything you have done for the droid 3!
Is there a kitchen for DROID 3 roms. Running windows 7
Sent from my DROID3 using xda premium
You need to be running Linux to do this hardcore kind of stuff.
Like Ubuntu I had it set up in VB and detain. Was just wondering if there was some thing for Motorola roms out there. I have had HTC phones this my first moto with android on it.
Sent from my DROID3 using xda premium
I'm starting to tinker with building (learning, actually) ROMs. I'm running Linux Mint Debian - has there been a kitchen built for D3?
Hashcode said:
repo init https://[email protected]/Hashcode/cm4D3.git
Click to expand...
Click to collapse
That should be
Code:
repo init -u git://github.com/Hashcode/cm4D3.git -b gingerbread
or whatever URL you want to use from the access URL box at https://github.com/Hashcode/cm4D3.
And of course "gingerbread" could be "ics" if your excitement about being on the bleeding edge overrides what should be a fairly sensible fear reaction to the term "bleeding edge".
@Hashcode: You don't use your own ALSA repos? (Comparing with my own generated manifest for your project...)
Also, are you planning on pulling newer Gingerbread manifest changes into your tree? I noticed CyanogenMod have gained a u8150 device tree, and I happen to have one of those, but your manifest doesn't list it...
Ooops. I have a u8510. >_< But the question stands...
TBBle said:
That should be
Code:
repo init -u git://github.com/Hashcode/cm4D3.git -b gingerbread
or whatever URL you want to use from the access URL box at https://github.com/Hashcode/cm4D3.
And of course "gingerbread" could be "ics" if your excitement about being on the bleeding edge overrides what should be a fairly sensible fear reaction to the term "bleeding edge".
@Hashcode: You don't use your own ALSA repos? (Comparing with my own generated manifest for your project...)
Also, are you planning on pulling newer Gingerbread manifest changes into your tree? I noticed CyanogenMod have gained a u8150 device tree, and I happen to have one of those, but your manifest doesn't list it...
Ooops. I have a u8510. >_< But the question stands...
Click to expand...
Click to collapse
Thank you for pointing out that my repo init line was wrong. I fixed it for those that were having issues.
Also, for those watching my manifest for ICS, I'm getting an error when syncing:
error: revision refs/heads/master in manifests not found
I'm trying to fix that. Correction: Fixed it and double-checked with a repo sync.
Some quick answers:
- I tried to customize the alsa source to fix some of the audio issues. But it ended up being a bit more complex than just changing ALSA. Motorola added a layer into the audio system for handling HDMI audio and in call audio volume.
When you build stock AOSP Gingerbread using the alsa drivers, the libaudio.so file ends up being all of the ALSA calls. If you examine the libaudio from the D3, you'll see that it is nothing of the sort. It's the customized mixer lib for RDS voice and HDMI audio. There's another lib from the phone: libaudio_ext.so which ends up being the alsa calls.
All of which made customizing just the alsa code risky at best as the further away from the version of alsa that was used on the phone, the less likely that the custom libaudio would work.
I probably still have the unfinished hardware_alsa git out on github, but it's not active in the current build.
- I can occasionally check for updates to the CM7 manifest and add them, or if you fork the manifest and add it in there that works as well.
Side Note: I may need to pick your brain on an EGL 0x0500 erorr I'm getting in the ICS code. I'm fairly certain it's an enum value that our version of the PowerVR drivers aren't set to handle, but I'd like to confirm that for my troubleshooting. And it seems that you might have some knowledge in that area
Where/how does someone begin working on building a ROM once they've downloaded these files? I'd rather dive into code and learn Android rather than using a menu driven wizard. Is there a tutorial somewhere? What tools are needed?
Sent from my DROID3 using XDA App
Phibernaut said:
Where/how does someone begin working on building a ROM once they've downloaded these files? I'd rather dive into code and learn Android rather than using a menu driven wizard. Is there a tutorial somewhere? What tools are needed?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
This would be the starting point that you're looking for:
http://source.android.com/
Hashcode said:
Side Note: I may need to pick your brain on an EGL 0x0500 erorr I'm getting in the ICS code. I'm fairly certain it's an enum value that our version of the PowerVR drivers aren't set to handle, but I'd like to confirm that for my troubleshooting. And it seems that you might have some knowledge in that area
Click to expand...
Click to collapse
Some, but probably not enough. I'm happy to look, but I'm actually moving internationally tomorrow so I may not have 'net access for a week or so. >_< (That's why I've been trying so hard to get backup working. ^_^)
Once I'm settled in I will probably use fdisk to repartition my device or have a poke at hacking sd-ext support into safestrap, so I can start playing with custom ROMs.
Did you see my safestrap-ME863 nandroid patch in the Safestrap thread, BTW? It's got a couple of TODOs, but seems safe and roughly correct to me. http://forum.xda-developers.com/showpost.php?p=19683372&postcount=249
It could also form the basis for detecting when /preinstall can't be used as safe-system although I didn't look to see if there's already code to do that.
Does anyone know of a site where I can peek at reference code for random things (Apps, Kernal etc.)? It'll make it easier to understand how the code works. I haven't look at any code yet so I don't even know what language apps and the os are programmed in. (Java, C, C++, Ruby)
Sent from my D3-CM7-SS using xda premium
tenchi19134 said:
Does anyone know of a site where I can peek at reference code for random things (Apps, Kernal etc.)? It'll make it easier to understand how the code works. I haven't look at any code yet so I don't even know what language apps and the os are programmed in. (Java, C, C++, Ruby)
Click to expand...
Click to collapse
Just pull down the repo as Hashcode describes in this thread - you'll have all of the Android source. To the best of my knowledge, it comprises of mostly C, C++, and Java, but there is probably a smathering of some other things like ASM, perl, BASH, etc.
And to those who are asking if there is a kitchen, there is, it's called make
Because the CyanogenMod developers decided not to switch to the Linaro toolchain, I decided that I would do it myself. This ROM is very similar to invisiblek's nightlies, but has a few more patches from the CyanogenMod queue applied and other changes made to enable building with GCC 4.7 and -O3. I will try to put up a new build at least once every few days if there is much being merged into the CM9 tree.
The main benefit of using the Linaro optimized ROM is that the UI is faster and snappier. Some applications (especially heavy ones like Google Play) are noticeably less laggy. Also, you get higher benchmark scores. (Yay!)
My kernel is included as the stock kernel in this ROM.
As always, if you are in any doubt whatsoever, you should do a Nandroid backup before flashing this ROM.
Changelog:
8/15/2012
No changes from me; just updates from the CM repo
8/12/2012
Revert the patch increasing the number of cached app pages, as this used more memory and made the launcher homescreens lag
8/10/2012
No changes from me; just updates from the CM repo
8/7/2012
Remove the ext4 sdcard patch because it was causing multiple regressions in handling the sdcard, even though it was still fat32
8/6/2012
Apply patch (http://review.cyanogenmod.com/#/c/20061/) to remove videos intended only for the tuna device
Attempt to workaround the lag issues by making the browser kill itself when the last tab is closed
8/3/2012
Apply patch (http://review.cyanogenmod.com/#/c/20654/) to enable HTTPS Google searches in the stock browser for better privacy
Apply patch (http://review.cyanogenmod.com/#/c/19807/) to allow mounting ext4 sdcards
7/31/2012
Update to the Linaro 2012.7 toolchain
Compile the kernel with "-O3 -fno-tree-vectorization"
7/22/2012
Add TCP MSS iptables filter to the kernel as it seems to be used during tethering
Add the Linaro string processing optimizations to the ROM
7/21/2012
Include my "Lite" kernel with the ROM
Update to a new, unreleased-as-of-yet version of my kernel with more optimizations
7/16/2012
Disable WebGL again. It was causing hardlocks on a number of enabled sites
Apply patch (http://review.cyanogenmod.com/#/c/18490/) to allow for the downloading of "unsafe" attachment files in Email
7/10/2012
Apply patch (http://review.cyanogenmod.com/#/c/18319/) to speed up some app starts
Apply patch (http://review.cyanogenmod.com/#/c/17552/) to add more NEON optimizations to pixelflinger
Enable WebGL
7/8/2012
Apply Evan McClain's libskia update (fixes the blacked-out JPEG issue)
Fix some media players like MX Player (an instruction was missing because it was optimized out by O3)
Apply more optimization flags
6/27/2012
Initial release
Apply CM9 patches to fix compile failures with GCC 4.7 and enable O3 optimizations
Switch to libjpeg-turbo
Disable scrolling cache (increases scrolling smoothness for non-hardware-accelerated listviews)
Issues (specific to the Linaro optimized version):
Turning off Bluetooth causes the Phone app to crash. It restarts immediately, so there are no long-term effects.
Bluetooth file transfer (OPP) does not work. The Linaro team experiences this bug too and is currently looking for a solution. I will update as soon as a solution is found.
You can download the source I use to compile this ROM by following these instructions: https://github.com/invisiblek/android_device_htc_inc/blob/ics/README.md
Compiling Instructions:
These compiling instructions are for Linux. They should work on any distro, but I am using the latest release of (K)ubuntu.
Follow all of the instructions from the source link above except for the last one. This will download the source tree and get you set up to build.
Assuming you are already in the root directory of your source tree ("~/cm9" if you followed the above instructions), run the following commands in the terminal. Some of the git pulls will display a text editor screen. When you get this, just press Ctrl-O, Enter, and finally Ctrl-X.
Code:
cd external/skia
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/85/14585/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/86/14586/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/87/14587/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/88/14588/1
git commit -a
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/89/14589/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/10/15810/1
cd ../webkit
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_webkit refs/changes/90/14590/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_webkit refs/changes/91/14591/1
cd ../../frameworks/base
git pull http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/92/14592/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/80/17380/2
cd ../../external/freetype
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_freetype refs/changes/54/12654/2
cd ../../build
git pull http://review.cyanogenmod.com/CyanogenMod/android_build refs/changes/58/17358/4
Follow the instructions here to replace your libjpeg with libjpeg-turbo.
Open the file ~/cm9/frameworks/base/core/java/android/widget/AbsListView.java in your favorite text editor. Go to line 753 and change it to read "setScrollingCacheEnabled(false);".
Open the file ~/cm9/bionic/libc/arch-arm/bionic/libgcc_compat.c in your favorite text editor. Go to line 114 and insert two new lines reading "XX(__aeabi_llsl) \" and "XX(__aeabi_llsr) \" below it.
Open the file ~/cm9/build/core/config.mk in your favorite text editor. Go to line 91 and change it to read "COMMON_GLOBAL_CFLAGS:= -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -Wno-error=strict-aliasing -Wno-error=enum-compare". Go to line 312 and change it to read "TARGET_GLOBAL_CFLAGS += $(COMMON_GLOBAL_CFLAGS) -march=armv7-a -mcpu=cortex-a8 -mtune=cortex-a8". Go to line 315 and change it to read "TARGET_GLOBAL_CPPFLAGS += $(COMMON_GLOBAL_CPPFLAGS) -march=armv7-a -mcpu=cortex-a8 -mtune=cortex-a8".
Open the file ~/cm9/build/core/combo/TARGET_linux-arm.mk in your favorite text editor. Go to line 47 and change it to read "prebuilt/$(HOST_PREBUILT_TAG)/toolchain/linaro-4.7.1/bin/arm-linux-androideabi-". Go to line 149 and change it to read "TARGET_GLOBAL_CPPFLAGS += -fvisibility-inlines-hidden".
Download this file and unzip it to ~/cm9/prebuilt/linux-x86/toolchain/linaro-4.7.1
You are finally ready to build! Open a terminal to the ~/cm9 directory, then run ". build/envsetup.sh" and "brunch inc". This will take a long time.
Great, going to try this out. Maybe the keyboard works better, I've shut down pop up and prediction.
Still lags horribly.
Edit: Is gapps included or do I need to flash them?
Edit: Wow.. Maybe some won't notice it, but I've seen an increase of speed and snapiness. Keyboard lag seems to have stopped somewhat.. its still there but its along better.
Sent from my ADR6300 using Tapatalk 2
withbloodskies said:
Great, going to try this out. Maybe the keyboard works better, I've shut down pop up and prediction.
Still lags horribly.
Edit: Is gapps included or do I need to flash them?
Edit: Wow.. Maybe some won't notice it, but I've seen an increase of speed and snapiness. Keyboard lag seems to have stopped somewhat.. its still there but its along better.
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
You still need to flash Gapps. It would be illegal for me to include them.
The best workaround I have found for keyboard lag is to disable spellchecking. You still get autocorrect like in GB; it just doesn't put a red squiggly under misspelled words.
Good work, I'll have to try it out. Any chance you putting this up on goo.im and/or ROM Manager, to expedite the update process?
Very nice work,Thanks for your contribution .
PonsAsinorem said:
Good work, I'll have to try it out. Any chance you putting this up on goo.im and/or ROM Manager, to expedite the update process?
Click to expand...
Click to collapse
I will look at putting it on goo.im.
One last suggestion (for now) before I'm off to flash it: thought of changing the ROM and zip name just slightly so it's not confused with invisiblek? Maybe throw a linaro in there somewhere or something? Right now, they have the same names (and dates, too, shortly) with just the compile times and machines being different. Now off to flash.
PonsAsinorem said:
One last suggestion (for now) before I'm off to flash it: thought of changing the ROM and zip name just slightly so it's not confused with invisiblek? Maybe throw a linaro in there somewhere or something? Right now, they have the same names (and dates, too, shortly) with just the compile times and machines being different. Now off to flash.
Click to expand...
Click to collapse
I'm not quite sure how to do that. Can you tell me?
mamarley said:
I'm not quite sure how to do that. Can you tell me?
Click to expand...
Click to collapse
You'll have to do some tweaking to the bottom of this file. Hard to explain on the phone. As part of my compile script I wrote for my kangs, it sed/replaced the necessary lines with pons (I'd use linaro for yours). Experiment with it till it looks how you want it to. Any questions, let me know.
https://github.com/CyanogenMod/android_vendor_cm
mamarley said:
You still need to flash Gapps. It would be illegal for me to include them.
The best workaround I have found for keyboard lag is to disable spellchecking. You still get autocorrect like in GB; it just doesn't put a red squiggly under misspelled words.
Click to expand...
Click to collapse
I wanted to point out that I got keyboard lag on ICS even on my gnex. There's not much that can be done. I never did try disabling spell checker. Liquid 1.5 helped with its linaro optimizations but what helped more to me was the interactive governor I was using had input boost which boosts frequency upon using the touchscreen to minimize lag rather than wait for it to ramp up. The other part nay have been the go_high setting of 50% load. I'm not using all the technical terms but to high-speed frequency is user configurable and its the speed it will jump to at a specified load. It may exist in our current interactive governor.
I do know that there is no keyboard lag in jelly bean that I can tell.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
I do know that there is no keyboard lag in jelly bean that I can tell.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Its all that butter
Anyway I used DPI and it works but it makes alot of apps force close. I was on 175, the same thing happens on Evervolv's Roms too.
Sent from my ADR6300 using Tapatalk 2
Can i flash this over invisiblek's Cm9 nightlies?
Or do i have to do a full wipe?
I have all my apps and everything just the way i want it.. I really dont wanna wipe.
Gorilla* said:
Can i flash this over invisiblek's Cm9 nightlies?
Or do i have to do a full wipe?
I have all my apps and everything just the way i want it.. I really dont wanna wipe.
Click to expand...
Click to collapse
You can flash over.
I have been flashing over since the CM7 days and have never had any problems. I even flashed the CM9 ROM right on top of the CM7 ROM and only had to clear the data for 2 apps to get everything working again.
Marley, Im booting up now, I flashed it, flashed your Lite Kernel, and USB fast charge zip.
Heres to hoping for some sexy Linaro Goodness!
Ill report back to how this runs.
Gorilla* said:
Marley, Im booting up now, I flashed it, flashed your Lite Kernel, and USB fast charge zip.
Heres to hoping for some sexy Linaro Goodness!
Ill report back to how this runs.
Click to expand...
Click to collapse
Same here. Just booted up. This is legit. Snappier than the CM9 nightlies so far. I didn't flash the USB zip- what will that give me?
statusqu0 said:
Same here. Just booted up. This is legit. Snappier than the CM9 nightlies so far. I didn't flash the USB zip- what will that give me?
Click to expand...
Click to collapse
That enables USB Fast Charge. It will make your phone charge much faster when it is plugged into a PC or some third-party wall/car chargers.
mamarley said:
That enables USB Fast Charge. It will make your phone charge much faster when it is plugged into a PC or some third-party wall/car chargers.
Click to expand...
Click to collapse
Forgive my noob-ness, but will that damage the battery in any way?
statusqu0 said:
Forgive my noob-ness, but will that damage the battery in any way?
Click to expand...
Click to collapse
No, it just makes it charge in the same way it would if you plugged it into the stock wall charger.
seems good so far. a couple slow-downs at first but seem to have gone away.
Yea, seems snappier than the other cm9 rom..
Im just hoping i dont get phantom touchscreen issues.. like the screen typing for me,.
Hello everyone.
This guide will help you in building a kernel from source for your Nexus 4
Later, when 4.2 hits AOSP, i'll add a guide for building that too
You will need a computer running Linux / OSX to build the kernel, natively, or via a VM.
This guide assumes you’re running any Linux distro.
Getting a toolchain:
You need a toolchain to build the kernel.
The preferred one is Google’s toolchain, the same they use to build AOSP.
In a terminal, type:
Code:
git clone [url]https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/[/url]
export PATH=$PATH:$(pwd)/arm-linux-androideabi-4.6/bin
export CROSS_COMPILE=arm-linux-androideabi-
TIp: paste the export statements in your ~/.bashrc to have them exported each login.
Getting the kernel source:
The kernel source for Nexus devices is available from Google’s servers.
Nexus 4 : https://android.googlesource.com/kernel/msm
Github Mirror: https://github.com/android/kernel_msm
Open the terminal, and type the below commands to get the kernel source on your computer.
Code:
mkdir -p android/kernel
cd android/kernel
For Nexus 4, we get the msm kernel sources.
Code:
git clone [url]https://android.googlesource.com/kernel/msm[/url]
Next, we change our directory to the newly fetched source.
Type
Code:
cd msm
Figuring out what to build:
Now, we need to figure out which revision to build.
You need to be exactly sure about this, otherwise there are chances that the compiled kernel won’t work.
The commit to build upon can be found by a few ways.
To get the kernel sources matching the device tree, type the below in the device tree.
Code:
git log kernel
Next, type the below in the kernel tree
Code:
git checkout <commit>
The commit of the version running of the current review units is 7a47627, which is same as branch android-msm-mako-3.4-jb-mr1-fr .
Compiling:
Name of defconfig: mako_defconfig
cd to the directory of the kernel source, then type the below in a terminal.
Code:
export ARCH=arm
export SUBARCH=arm
Code:
make <name_of_defconfig>
make
The kernel image will be ready at arch/arm/boot/zImage
To flash it, you need to make it into a boot.img, more on that later, when we have more sources.
1) what is the branch "android-msm-mako-3.4-jb-mr1-fr" for?
2) what does mr1 mean? sounds like milestone/alpha/beta. Maybe it's not final? Last commit is 2 weeks ago.
3) great guide
m11kkaa said:
1) what is the branch "android-msm-mako-3.4-jb-mr1-fr" for?
2) what does mr1 mean? sounds like milestone/alpha/beta. Maybe it's not final? Last commit is 2 weeks ago.
3) great guide
Click to expand...
Click to collapse
mr1 could stand for "Milestone Release 1", it might not be final.
That being said, you should never checkout a branch directly for compiling a kernel, but the commit directly.
cdesai said:
...You need a toolchain to build the kernel. The preferred one is Google’s toolchain, the same they use to build AOSP.
Click to expand...
Click to collapse
Could you also use linaro to compile the kernel? I believe it's a toolchain anyway, but I'm not too sure on it's benefits or compatibility...
nice didn't realize kernel source was already available- can't wait to test this zImage and start testing changes noticed they left out kernel compression makes for a big zimage
randomblame said:
nice didn't realize kernel source was already available- can't wait to test this zImage and start testing changes noticed they left out kernel compression makes for a big zimage
Click to expand...
Click to collapse
Are you planning on developing for the N4?
Loved your work on the DHD
espionage724 said:
Could you also use linaro to compile the kernel? I believe it's a toolchain anyway, but I'm not too sure on it's benefits or compatibility...
Click to expand...
Click to collapse
Linaro isn't a toolchain, but they do make toolchains.
Yes, you can use it to compile the kernel, though it may not compile at all with it, or not work well - your mileage may vary.
randomblame said:
nice didn't realize kernel source was already available- can't wait to test this zImage and start testing changes noticed they left out kernel compression makes for a big zimage
Click to expand...
Click to collapse
Nope, LZO compression is enabled by default
cdesai said:
Linaro isn't a toolchain, but they do make toolchains.
Yes, you can use it to compile the kernel, though it may not compile at all with it, or not work well - your mileage may vary.
Click to expand...
Click to collapse
Linaro has proven to increase android performance up 30 - 100% not sure if that is with -O3 optimizations or not. That is all I use on my kernels
Sucks this phone is not coming to Sprint, might be time to change carriers...
randomblame said:
nice didn't realize kernel source was already available- can't wait to test this zImage and start testing changes noticed they left out kernel compression makes for a big zimage
Click to expand...
Click to collapse
-mvectorize-with-neon-quad ---> I use this in my makefile for cflags and drops the zImage size from 5.0mb to 4.4mb.
cdesai said:
Linaro isn't a toolchain, but they do make toolchains.
Yes, you can use it to compile the kernel, though it may not compile at all with it, or not work well - your mileage may vary.
Nope, LZO compression is enabled by default
Click to expand...
Click to collapse
ah I didn't see it - 6+mb still pretty big from what I'm used to at least
I'm going through the mind numbing process of bringing in mainline patches and squashing them all together. I'm up to 3.4.1 ... woot where's the hang me emoticon lol
*finally got smart and cloned mainline and reset the head back to each sublevel and merged into my local n4 source
got it all the way up to date with mainline 3.4.18
Thanks cdesai. I didn't think anything was out yet!!
randomblame said:
ah I didn't see it - 6+mb still pretty big from what I'm used to at least
I'm going through the mind numbing process of bringing in mainline patches and squashing them all together. I'm up to 3.4.1 ... woot where's the hang me emoticon lol
*finally got smart and cloned mainline and reset the head back to each sublevel and merged into my local n4 source
got it all the way up to date with mainline 3.4.18
Click to expand...
Click to collapse
Yea, it's big, but partitions on new devices are big as well.
y u no use git to merge
Just add korg as a remote, fetch, merge.
Each version is tagged, so you can do that incrementally too.
Also, kernel.org hosts patches as well, if you prefer that way.
snowman77 said:
Thanks cdesai. I didn't think anything was out yet!!
Click to expand...
Click to collapse
Google <3
I got it straightened out so it's up to date with mainline and I think I've got overclocking up to 1.89ghz ready lots of more fun to be had but damn I'm just teasing myself till tuesday/whenever the thing comes in the mail. hard to test anything without hardware.
I may need a tip. I have followed your guide - which I find great and simple - but I'm having a problem with the arm binaries when I launch the make command after checking out the remotes/origin/android-msm-mako-3.4-jb-mr1-fr and executed make mako_defconfig:
Code:
/bin/sh: 1: arm-linux-androideabi-ld: not found
I have cloned the toolchain and msm repos, and added to the PATH environment var the location of the bin directory. I can reach arm-linux-androideabi-ld from the command line, but no luck executing it:
Code:
[email protected]:~/android/kernel/msm$ /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld
bash: /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld: No such file or directory
And it is there with execution rights:
Code:
[email protected]:~/android/kernel/msm$ ll /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld
-rwxrwxr-x 1 echedey echedey 3145332 Nov 10 16:32 /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld*
My repos are in these paths:
Code:
/home/echedey/android/arm-linux-androideabi-4.6
/home/echedey/android/kernel
And my $PATH is:
Code:
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/echedey/android/arm-linux-androideabi-4.6/bi
Am I missing anything?
josjator said:
I may need a tip. I have followed your guide - which I find great and simple - but I'm having a problem with the arm binaries when I launch the make command after checking out the remotes/origin/android-msm-mako-3.4-jb-mr1-fr and executed make mako_defconfig:
Code:
/bin/sh: 1: arm-linux-androideabi-ld: not found
I have cloned the toolchain and msm repos, and added to the PATH environment var the location of the bin directory. I can reach arm-linux-androideabi-ld from the command line, but no luck executing it:
Code:
[email protected]:~/android/kernel/msm$ /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld
bash: /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld: No such file or directory
And it is there with execution rights:
Code:
[email protected]:~/android/kernel/msm$ ll /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld
-rwxrwxr-x 1 echedey echedey 3145332 Nov 10 16:32 /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld*
My repos are in these paths:
Code:
/home/echedey/android/arm-linux-androideabi-4.6
/home/echedey/android/kernel
And my $PATH is:
Code:
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/echedey/android/arm-linux-androideabi-4.6/bi
Am I missing anything?
Click to expand...
Click to collapse
You path has a "n" missing from bin at the end.
You could type arm- and try to use tab-completion to see if it's accessible, then the same thing with full path (~/android/arm-linux-androideabi-4.6)
cdesai said:
You path has a "n" missing from bin at the end.
You could type arm- and try to use tab-completion to see if it's accessible, then the same thing with full path (~/android/arm-linux-androideabi-4.6)
Click to expand...
Click to collapse
Sorry, the missing 'n' came from the c&p. I can actually see the file by tabing it from any path but after the auto completing it tells this weird thing:
Code:
[email protected]:~$ arm-linux-androideabi-ld
bash: /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld: No such file or directory
I'm a experienced *nix user but I don't get this. The repos are correctly cloned and all files under bin has exec rights. I'm running ubuntu 12.10. Maybe a problem with the shell? I should try any other environment, but that would be like killing flies with missiles. Thanks for your help.
Do you definitely have the appropriate executable at
'/home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld'?
Can you do an ls -lF of that directory?
Perhaps the arm-linux-androideabi-ld file there is actually just a symlink which has lost its target.
@josjator Yeah, seems I have the same problem as you. I'm also using Ubuntu 12.10 with a bash shell. I think it may be a recursive make/shell issue thing (sorry, I'm not too hot on make files). Will keep plugging away to see if I can resolve the problem.
The device trees have hit AOSP
https://android.googlesource.com/device/lge/mako/
dsana123 said:
@josjator Yeah, seems I have the same problem as you. I'm also using Ubuntu 12.10 with a bash shell. I think it may be a recursive make/shell issue thing (sorry, I'm not too hot on make files). Will keep plugging away to see if I can resolve the problem.
Click to expand...
Click to collapse
@josjator: Using the 4.7 toolchain sorted me out (at least it's building now and past the initial problem).
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7
Click to expand...
Click to collapse
The objdump and ld binaries are much happier now.
BTW, I did download the 4.6 toolchain again (just in case there was some problem in the initial git clone), but I still encountered objdump and ld problems.
Works like a champ on Ubuntu 12.10 exactly as outlined in the OP. Thanks!
Code:
[email protected]:~/Documents/AOSP/kernel/msm$ ls -l arch/arm/boot/zImage
-rwxrwxr-x 1 android android 6314888 Nov 16 23:45 arch/arm/boot/zImage
[email protected]:~/Documents/AOSP/kernel/msm$ uname -a
Linux ubuntu 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[email protected]:~/Documents/AOSP/kernel/msm$ arm-linux-androideabi-gcc -v
[...]
gcc version 4.6.x-google 20120106 (prerelease) (GCC)
Since this has been asked a few times
Multi windows support is not in by default
You need to cherry-pick this to include it in your build
https://gerrit.omnirom.org/#/c/53/
thank you,
I added it into my p5110 build, i'll let you know if it works well.
edit:: working well
I won't lie, I plan to build Omni today as my first-ever Android build. It may go hilariously badly, it may go wonderfully. Is it in the command line that I cherry-pick that piece of code? The rest I think I can figure out myself. Thanks in advance.
dibblebill said:
Is it in the command line that I cherry-pick that piece of code?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
chasmodo said:
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
Click to expand...
Click to collapse
You probably will want to do a "repo start" first, otherwise your commit will be clobbered on sync.
e.g. from the root of the source tree:
Code:
repo start work frameworks/base
for more on repo - http://source.android.com/source/using-repo.html
Thank you both. Very helpful. It's wonderful receiving help from the developers, especially since this will be my first build
Sent from my Nexus 10
dibblebill said:
Thank you both. Very helpful. It's wonderful receiving help from the developers, especially since this will be my first build
Sent from my Nexus 10
Click to expand...
Click to collapse
For everybody there was a "first time"
chasmodo said:
http://forum.xda-developers.com/showpost.php?p=37053013&postcount=7
Click to expand...
Click to collapse
When I execute this using the linked cherry pick, all I get is "fatal: Not a git repository (or any of the parent directories): .git
dibblebill said:
When I execute this using the linked cherry pick, all I get is "fatal: Not a git repository (or any of the parent directories): .git
Click to expand...
Click to collapse
you tried this mate?
Code:
git fetch [url]https://gerrit.omnirom.org/android_frameworks_base[/url] refs/changes/53/53/19 && git cherry-pick FETCH_HEAD
before that u must be inside ~/android/omni/frameworks/base if i im rigth, u get there by
Code:
cd ~/android/omni/frameworks/base
someone correct me if im wrong pls.
makkeonmies said:
you tried this mate?
Code:
git fetch [url]https://gerrit.omnirom.org/android_frameworks_base[/url] refs/changes/53/53/19 && git cherry-pick FETCH_HEAD
before that u must be inside ~/android/omni/frameworks/base if i im rigth, u get there by
Code:
cd ~/android/omni/frameworks/base
someone correct me if im wrong pls.
Click to expand...
Click to collapse
[codegit fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/53/53/19 && git cherry-pick FETCH_HEAD[/code]
Exactly as copied and pated from the cherrypick itself, yep.
I was, however, in ~/android/omni/.repo/projects/frameworks/base, though. Now I got it fixed and inserted. thanks!
on my way to being a ROM hacker/compiler, then later developer
EDIT: Will the sources for this rescync automatically when I repo sync, or will I have to also re-cherry pickk this every few days?
dibblebill said:
[codegit fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/53/53/19 && git cherry-pick FETCH_HEAD[/code]
Exactly as copied and pated from the cherrypick itself, yep.
I was, however, in ~/android/omni/.repo/projects/frameworks/base, though. Now I got it fixed and inserted. thanks!
on my way to being a ROM hacker/compiler, then later developer
EDIT: Will the sources for this rescync automatically when I repo sync, or will I have to also re-cherry pickk this every few days?
Click to expand...
Click to collapse
If you do a "repo start" before cherry-picking, repo will try to automatically rebase when syncing. It will not sync newer patchsets though.
thanks, very useful.
just to know, why isn't it yet merged ?
BENETNATH said:
thanks, very useful.
just to know, why isn't it yet merged ?
Click to expand...
Click to collapse
Because it still has a lot of bugs that need to be worked out?
Unfortunately, since Omni went public, we've had a ton of device support stuff to work with people on, so the more difficult items have temporarily stalled.
Entropy512 said:
Because it still has a lot of bugs that need to be worked out?
Unfortunately, since Omni went public, we've had a ton of device support stuff to work with people on, so the more difficult items have temporarily stalled.
Click to expand...
Click to collapse
sadly i would say.
BBQ was a great timing but people went crazy on omni, which is a good and a bad thing ^^
i've built omni for my device, with the commit, and it's nice, but currently, it's nearly strictly an AOSP, which is a bit frustrating
keep the hard work, courage to all the omni dev !
BENETNATH said:
sadly i would say.
BBQ was a great timing but people went crazy on omni, which is a good and a bad thing ^^
i've built omni for my device, with the commit, and it's nice, but currently, it's nearly strictly an AOSP, which is a bit frustrating
keep the hard work, courage to all the omni dev !
Click to expand...
Click to collapse
Yeah, I would've liked to have polished things a bit more - but the BABBQ was an opportunity we didn't want to miss.
yep,
anyway, great work. what you guys need now is to keep that alive, and to limit the time spent on bringing devices, better enhance the rom.
Rom builders will join the effort for all the rom stuff, especially as it's really easy (i've bring my device in a dozen of minutes, from a CM branch. needs polishing but works)
Does anyone have the last patch set for multiwindow the 4.3 branch? It seems like the past two weeks worth of patches were lost after the Gerrit server hard drive failure, and I just got my first build done yesterday so I'm not sure what I can cherry pick to test out multiwindow. The last comment remaining seems to imply that the last patch set was broken.
https://gerrit.omnirom.org/#/c/1510/
chasmodo said:
https://gerrit.omnirom.org/#/c/1510/
Click to expand...
Click to collapse
That's the 4.4 branch. Time to cherry-pick!
sgt. meow said:
That's the 4.4 branch. Time to cherry-pick!
Click to expand...
Click to collapse
Are you cherry picking back to 4.3 or doing a 4.4 build? Let us know how it goes! I just set up a build this weekend for my N8013 but Gerrit was down so I couldn't get multiwindow, and when it came back the Gerrit ticket was missing two weeks worth of patches as I mentioned so I was feeling like it would be risky to try to apply it.
UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there