I am planning on submitting linaro patches, but would appreciate some testing to make sure everything works.
If something is broken that is *not* broken in the latest CM10 nightly please let me know.
MOD EDIT: links removed.
Instructions: Follow the same CM10 instructions for installing: http://forum.xda-developers.com/showthread.php?t=1840414
ROM and kernel built with linaro:
[email protected]:/ $ strings /system/bin/surfaceflinger | grep -i gcc
GCC: (Linaro GCC 4.7-2012.11-1~dev) 4.7.3 20121106 (prerelease)
[email protected]:/ $ cat /proc/version
Linux version 3.0.48-cyanogenmod-g726b6ec ([email protected]) (gcc version 4.7.3 20121106 (prerelease) (Linaro GCC 4.7-2012.11-1~dev) ) #1 SMP PREEMPT Sat Nov 17 23:28:50 EST 2012
ROM with only system build with linaro toolchain:MOD EDIT: links removed.
Changelog:
2012-11-16: CM10 with linaro patches and ROM built with linaro toolchain (gcc 4.7.3)
2012-11-18: CM10 with linaro patches and both ROM and kernel built with linaro toolchain
2012-11-23: The usual + several audio patches to fix speakerphone echo and bluetooth music volume and some display and kernel patches (all in CM gerrit).
2012-12-03: Same with d2 kernel patches in cm gerrit with display hal patches to fix screen not turning on sometimes. Also includes http://review.cyanogenmod.org/#/c/27507/ which may help with data drops.
I'll give this a try, thanks!
Sent from my SCH-I535 using xda premium
Nice to see your work here. I came from the vivow. Looking forward to flashing this. Thanks!
Sent from my SCH-I535 using xda app-developers app
It's always nice to new ROM.
wow
http://www.androidpolice.com/2012/0...e-and-now-parts-of-it-are-being-added-to-cm9/
Wasn't familiar with Linaro, but you can bet I won't forget them after looking at this demo.
bigdad1963 said:
http://www.androidpolice.com/2012/0...e-and-now-parts-of-it-are-being-added-to-cm9/
Wasn't familiar with Linaro, but you can bet I won't forget them after looking at this demo.
Click to expand...
Click to collapse
whoa might have try this out
gonna give this a try later! thanks!
This is aosp correct?? Just confused since its in this forum.
I'm assuming its based off of 4.1.2??
sent from my blue police box flying through time!!!
Will give it a go and report back thanks for this!
Sent from my SCH-I535 using xda app-developers app
Nice work! Flashed and running great, smooth and quick.
Screen rotation maybe bit a little bit laggy, but other than that haven't found anything else.
Sent from my SCH-I535 using xda premium
Not trying to steal your thunder, OP, as any devs/ROMs are appreciated. However, wasn't linaro proven to not do much? I've seen the demo, but didn't CM and everyone ditch it after a week or so and some tests?
Just curious if you could list some benefits and/or improvements with linaro. Just curious. Thanks!
Sent from my SCH-I535 using Tapatalk 2
Is there any way linaro can be used in PA, I want that speed but I don't want to loose my hybrid UI
Sent from my SCH-I535 using xda app-developers app
1ManWolfePack said:
Not trying to steal your thunder, OP, as any devs/ROMs are appreciated. However, wasn't linaro proven to not do much? I've seen the demo, but didn't CM and everyone ditch it after a week or so and some tests?
Just curious if you could list some benefits and/or improvements with linaro. Just curious. Thanks!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
KToonsez uses linaro as well and Evan is a well respected kernel dev as well... I would assume they wouldn't waste time on a project that doesn't show improvement. I think it was quite buggy/unstable when it was originally introduced so it wasn't picked up by CM. I would love to hear some thoughts from a kernel dev though. It's not something you hear/read about a lot and kinda got glazed over when first introduced (IMHO)
Sent from my SCH-I535 using xda app-developers app
I don't know if linaro was buggy before, but I've never had any version of cm run this smooth on my phone. I've always had bugs and archiving when closing apps.
So far its wicked fast and everything is working great!!
One thing I can't find is the option to enable app kills by holding the back button.
sent from my blue police box flying through time!!!
aeroevan said:
I am planning on submitting linaro patches, but would appreciate some testing to make sure everything works.
If something is broken that is *not* broken in the latest CM10 nightly please let me know (a.k.a. I know NFC doesn't turn on, etc.).
ROM: http://goo.im/devs/aeroevan/cm10/cm-10-20121116-UNOFFICIAL-d2vzw.zip
GApps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Instructions: Follow the same CM10 instructions for installing: http://forum.xda-developers.com/showthread.php?t=1840414
[email protected]:/ # strings /system/bin/surfaceflinger | grep -i gcc
GCC: (Linaro GCC 4.7-2012.10-1~dev) 4.7.3 20121106 (prerelease)
Currently the kernel is being built with the AOSP toolchain, but I will try a build with a kernel built with linaro toolchain next:
[email protected]:/ # cat /proc/version
Linux version 3.0.48-cyanogenmod-g726b6ec ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Nov 15 23:02:16 EST 2012
Click to expand...
Click to collapse
Not really sure whats going on, but this is the only AOSP ROM that my NFC has worked. I would like to say thank you.
prenedo said:
KToonsez uses linaro as well and Evan is a well respected kernel dev as well... I would assume they wouldn't waste time on a project that doesn't show improvement. I think it was quite buggy/unstable when it was originally introduced so it wasn't picked up by CM. I would love to hear some thoughts from a kernel dev though. It's not something you hear/read about a lot and kinda got glazed over when first introduced (IMHO)
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Awesome. Thanks for the response. I'll give it a whirl...
Sent from my SCH-I535 using Tapatalk 2
I assume camcorder recording volume is still low?
bL33d said:
I assume camcorder recording volume is still low?
Click to expand...
Click to collapse
Nope! Fixed
Sent from my SCH-I535 using xda premium
bL33d said:
I assume camcorder recording volume is still low?
Click to expand...
Click to collapse
Not sure how NFC works for Twistitup (still doesn't work for me), but if it's broken in the CM10 nightly it's probably no different in this build.
I usually don't use CM, but I'm really digging this. Thanks man
Sent from my SCH-I535 using xda app-developers app
Related
All,
Since we are working as a DEV team now I wanted to share a PM I had with another DEV on the board about our Kernel. I hope this can assist some others that have more experience with the Kernel like b_randon
g60madman said:
subpsyke,
I would love to upgrade our kernel for the Motorola Triumph. How did you go about figuring which Code Aurora vanilla kernel to start with? I took over development for CM7 from Whyzor and would be interested in your methodology.
Thanks in advance,
g60
Click to expand...
Click to collapse
subpsyke said:
1. I unpacked the original Huawei source to one directory, and downloaded the CodeAurora kernel to another.
2. I used the release tags as a reference: https://www.codeaurora.org/xwiki/bin/QAEP/froyo_almond
https://www.codeaurora.org/xwiki/bin/QAEP/froyo
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=tags
3. I reverted the codeaurora repository to tag releases (e.g.: git reset --hard M76XXTSNCJNLYA6010) and compared the result via "diff urN" and meld. I knew I was getting closer when you get a smaller diff in the patch size, and used meld to see if the differences were likely to be Huawei's additions vs. CodeAurora's changes. It was only after going forward and backwards between tags was I sure of the proper baseline.
I performed the same discovery process with the Samsung kernel for my GT-I5500, which used M76XXTSNCJNLYA6040 as a baseline.
Click to expand...
Click to collapse
g60madman said:
Sweet thanks! I will check it out and see what I can do
Click to expand...
Click to collapse
subpsyke said:
No problem
I forgot to mention the last steps:
4. Once you establish the baseline, create a new branch: git checkout -b newbranch
5. Overlay the changes from the vendor to a new commit*:
cp ~/blah/vendorkernel/ . ; git add . ; git commit -m "Initial import of vendor changes".
6. Once you've commited the vendor changes, you can use "git merge origin/froyo_almond" to move from the baseline to a newer revision. The froyo_almond branch is most suitable, as it's locked at 2.6.32, and the development focus seems to be on the msm7k chipset series. You could try updating to the android-msm-2.6.32 kernel, but it has more significant changes that will require adaptations of the board file, and may not be worthwhile, as development focus seems to be on newer chipsets.
7. Inevitably you'll get merge conflicts, as more than likely some vendor commits may interfere with upstream changes. For this, you'll need to use your own discretion in fixing up the code. I use the "git mergetool", with meld configured as my default editor, and manually checked all the conflicts.
Good luck!
*You may also want to fix up permissions etc., if your vendor source comes from a zip tarball. But it's purely cosmetic.
Click to expand...
Click to collapse
g60madman said:
So is almond the best flavor to start with. I have been using MSM/QSD for a while and in when TickerGuy originally created our device files for cm7 he listed in the readme
CAF information:
Branch: froyo_pumpkin
Tag: M7630AABBQMLZA2030
Didn't know if I should start with pumpkin or use almond. Let me know what you think?
Thanks again for the info!
Click to expand...
Click to collapse
subpsyke said:
Hmm... if your phone really has a msm7630 chipset, then yes, you should probably go for the froyo_pumpkin branch. The froyo_almond branch is only for the msm7627 and qsd8650 chipsets.
Click to expand...
Click to collapse
g60madman said:
Well thats the stupid thing, since the beginning we have used always used msm7x30 for our board config, But our stock ROM from Virgin Mobile the config was msm7k in the build.prop. However if you hit the Motorola Dev our pone clearly states Qualcomm MSM8655. I am leaning towards using the almond branch would that be correct?
Click to expand...
Click to collapse
subpsyke said:
According to wikipedia, it's MSM8655.
Look at the table here: https://www.codeaurora.org/xwiki/bin/QAEP/
The froyo_almond supports qsd8650, and froyo_pumpkin supports qsd8650a_st1x. I honestly have no idea what the difference is, but it's within the realm of possibility that your phone's chipset is that odd revision on the pumpkin branch.
If your kernel is using a pumpkin baseline, then you should continue along the same branch.
Click to expand...
Click to collapse
g60madman said:
I will download pumpkin and compare the kernel. I am not sure why TickerGuy started with pumpkin. That maybe what our build is based off of but I am not 100%.
Click to expand...
Click to collapse
subpsyke said:
Ok. When you clone the codeaurora git repository, you'll have all the branches included anyway.
Click to expand...
Click to collapse
....sympathy post...
Sent from my SPH-D700 using xda premium
(The froyo_almond supports qsd8650, and froyo_pumpkin supports qsd8650a_st1x.) Is this the difference between the Photon 4G which has a WiMax radio in it, and the Triumph which does not include a 4G radio? <--- nvm when they came out I had heard they were the same phone except 4G, apparently the Photon is a Tegra 2 device.
Okay so after looking into code Aurora more, as soon as I get my Ubuntu back up I am going to work on a vanilla froyo 2.6.32.9 kernel by using the froyo_pumpkin branch on the tag Karl gave us. Once I do that and have a commit that adds in Motorola changes, I am going to use the gingerbread_rel branch to try to get a 2.6.35 kernel booting on the phone, then use the ics_chocolate_rb7 branch to hopefully get the 3.x kernel.booting. those branches all seem to have the best support for msm7630 chipsets which I believe is the closest to the msm8655 chip only that it is clocked at 800mhz instead of 1ghz. If anyone else can lend any advice or help it would be swell!!
Sent from my Triumph using Tapatalk
b_randon14 said:
Okay so after looking into code Aurora more, as soon as I get my Ubuntu back up I am going to work on a vanilla froyo 2.6.32.9 kernel by using the froyo_pumpkin branch on the tag Karl gave us. Once I do that and have a commit that adds in Motorola changes, I am going to use the gingerbread_rel branch to try to get a 2.6.35 kernel booting on the phone, then use the ics_chocolate_rb7 branch to hopefully get the 3.x kernel.booting. those branches all seem to have the best support for msm7630 chipsets which I believe is the closest to the msm8655 chip only that it is clocked at 800mhz instead of 1ghz. If anyone else can lend any advice or help it would be swell!!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
Swell, I love that word. Here is an email I got from TickerGuy on the Kernel a fe months back
g60madman said:
TickerGuy,
I know you have moved on from the MT. Currently I have taken over development for CM7 from Whyzor and had a question for you.
When you designed the original device files you listed in the readme:
Branch: froyo_pumpkin
Tag: M7630AABBQMLZA2030
Is that really our branch from MSM/QSD? I know the phone has the MSM8655 chip. So I'm just trying to figure out why we use msm7x30 for the board configuration and not say msm7k or qsd8k?
Thanks in advance for any help you can offer
Click to expand...
Click to collapse
TickerGuy said:
I think the reason had to do with some of the peripheral chips -- it was a lot of fun getting this phone to work as it has a number of very odd things about it, especially in the GPS area.
Click to expand...
Click to collapse
So I think it's safe to say the route you are taking the right route. Also when building the Kernel do not forget to merge in the Wyzor fixes for the Video as I am using the new Andreno drivers. Just an FYI.
Yeah I will on the cm7 kernel. As of right now I'm gonna try to get a stock froyo kernel booting off code Aurora sources then go ffrom there.
Sent from my Triumph using Tapatalk
I've got my Linux mint 13 up and running so I'm going to try to get my build environment setup to build kernels either tonight or tomorrow and start pulling in source.
By the way, Linux mint 13 is pretty nice distro so far. I like it alot better than Ubuntu!
Sent from my Triumph using Tapatalk
b_randon14 said:
I've got my Linux mint 13 up and running so I'm going to try to get my build environment setup to build kernels either tonight or tomorrow and start pulling in source.
By the way, Linux mint 13 is pretty nice distro so far. I like it alot better than Ubuntu!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
Also you don't need to download the pumpkin branch simple download the kernel
git clone git://codeaurora.org/kernel/msm.git
git reset --hard M7630AABBQMLZA2030
The M7630AABBQMLZA2030 is the pumpkin branch and that should take us back to the vanilla kernel
Here is the pastebin link for the warning I was getting from the linker during the build of the code Aurora kernel.
http://pastebin.com/GLMBSz26
You can look at the kernel source on my github. Its the froyo pumpkin kernel repo.
The warnings cone from the gcc linker saying that it's trying to link a non executible section in built-in.o
I'm not sure where to start looking for the issue at. If anyone can lend any insight I would be grateful!
Sent from my Triumph using Tapatalk
I switched to the gcc 4.3.1 toolchain included with the cm7 source and it booted up. Worked just as good as the stock kernel. I'm gonna have to see why the newer toolchains are not compiling it right. I use linaro 4.6 on bKernel froyo which is based off motos source. So I don't see why it wont build this code right. But at least I got one to boot! !!
Sent from my Triumph using Tapatalk
b_randon14 said:
I switched to the gcc 4.3.1 toolchain included with the cm7 source and it booted up. Worked just as good as the stock kernel. I'm gonna have to see why the newer toolchains are not compiling it right. I use linaro 4.6 on bKernel froyo which is based off motos source. So I don't see why it wont build this code right. But at least I got one to boot! !!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
Good work brother!
Thanks. Now lets try to move on up to 2.6.35. My idea is to make a different patch between 2.6.32.9 and 2.6.35.7 and maybe that will simplify updating it. I'm not sure which gingerbread branch I'm gonna use for the 2.6.35 kernel!
Sent from my Triumph using Tapatalk
I would think the gingerbread branch, and use the M7630AABBQMLZA404025I.xml version. That is where I snagged the keyboard updates.
g60madman said:
I would think the gingerbread branch, and use the M7630AABBQMLZA404025I.xml version.
Click to expand...
Click to collapse
you can use source kernal .35 for device fih-fbo..we are the same drive only need to change touch driver..
Yeah I would use the fih kernels but we has issues with them rebooting on us.
Sent from my Triumph using Tapatalk
b_randon14 said:
Yeah I would use the fih kernels but we has issues with them rebooting on us.
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
yes you need get a logcat and new baseband for this kernal...I have a file to solve the rendom reboot..but I can't help to get you for the baseband...
The kernel shouldn't have nothing to do with the baseband. Which file is it?
Sent from my Triumph using Tapatalk
b_randon14 said:
The kernel shouldn't have nothing to do with the baseband. Which file is it?
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
yes I know,I mean in rom library need these file,I will give you file when I go back home
Anyone got any ideas to fix the issues with newer toolchains when building from the code Aurora source?
Sent from my Triumph using Tapatalk 2
Have you tried downloading one of the gingerbread repo's from code Aurora? I am not sure if they have a different version of the tool chain or not?
SimplyCM10.1-v1 Kernel
These kernels are basically the stock versions of the CyanogenMod 10 and 10.1 Linux kernels, with the addition of Voodoo Sound and optional Voodoo Color. I've also added a few minor patches to get it to compile with the Linaro 12.09 GCC 4.7.2 13.06 GCC 4.7.4 compiler, which is supposed to make it faster. It uses my new AnyKernelEpic method of flashing, so it doesn't affect the ram disk your rom uses to boot, meaning this can be flashed to a wider varity of roms. For example, the CM kernel doesn't always change when a new nightly comes out, so this will still be flashable to new nightlys without me having to rebuilt it and you having to redownload it. This is also could work on CM9 / MIUI / AOKP / etc, but this is a 3.x kernel and I haven't tested it on any of those, so try at your own risk.
Look's like this isn't likely to boot on any roms other than Cyanogenmod 10 due to a recent change in the display driver there. See this post.
FEATURES
Up to date with CM10.1 stable release kernel as of commit 29b35d26ad13804188f71c6fb148246268579205
Up to date with CM10 stable release kernel as of commit f69938bf027965329ba5b6955760b7fa3af1ed95
Voodoo Sound
Voodoo Color (optional)
Dock audio from CM10 / CM10.1
Default governor: Interactive
Default i/o scheduler: Deadline (CM10) / Row (CM10.1)
Built with Linaro
AnyKernel
Stock modem only!
KNOWN ISSUES
Any and all issues that exist in the CyanogenMod kernels.
Kernel version shows as unknown in CM10.1 settings menu. Workaround: Run `uname -a` in Terminal or use any other app that shows kernel version (like Voltage Control)
DOWNLOAD
All downloads - Google Drive folder
File names with -vc- have Voodoo Color enabled
SOURCE
Kernel - github
Build tools - github
THANKS
All the people working on cyanogenmod
supercurio - voodoo sound / color
codeworkx (Daniel Hillenbrand) - patch to compile with GCC 4.7
marcusant - copied his voodoo color patches from the old nyan kernel
CHANGELOG (CM10.1)
Version 1
Up to date with all changes in the CM10.1 stable release kernel
Cherry-picked all patches from CM10 to enable Voodoo Sound, Color, and Linaro build
Built with Linaro 13.06 GCC 4.7.4
CHANGELOG (CM10)
Version 4 - FINAL CM10 VERSION
Up to date with all changes in the CM10 stable release kernel
Version 3
Added latest patches from CM10 for dock audio
Updated toolchain to Linaro 13.06
Version 2
Update to date with CM again
Changed default governor and i/o scheduler
Added voodoo-color build
Version 1
Voodoo Sound
Built with Linaro 12.09 GCC 4.7.2
First! New kernel again
Btw no voodoo colour?
Sent from my SPH-D700 using xda app-developers app
Ooohhhh 2nd... I may just have to try this out...
Dropple said:
First! New kernel again
Btw no voodoo colour?
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I used to be a big fan of it on ICS and earlier, but stock color looks much nicer on JB to me for some reason so I don't really feel the need for Voodoo Color.
Oh noo!!, doesn't works with NS4G modem
Sent from my SPH-D700 using xda app-developers app
Dropple said:
Oh noo!!, doesn't works with NS4G modem
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I don't think its possible right now for one kernel to work with either modem, so I would have to maintain two branches for that. Since I only use the stock modem, I wouldn't be able to test it so that probably wouldn't end well.
Can it be used on fco9
Sent from my SPH-D700 using xda app-developers app
Sherrillface said:
Can it be used on fco9
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
That's what I'm using it on. It should work on any normal epic modem.
Sent from my SPH-D700 using xda premium
great works
nice to see your work again, I always use your script to extract boot.img
Great work, thank you!
I'd love to try this one but I'm waiting for voodoo color. The other CM10 Kernel here just causes my phone to lockup. I'm hoping one of these Kernel's will eventually work for me!
brickwall99 said:
Great work, thank you!
I'd love to try this one but I'm waiting for voodoo color. The other CM10 Kernel here just causes my phone to lockup. I'm hoping one of these Kernel's will eventually work for me!
Click to expand...
Click to collapse
Nyan doesn't lock up
Sent from my Galaxy Nexus using Tapatalk 2
MДЯCЦSДИT said:
Nyan doesn't lock up
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
....where might this be.....
Sent from my SPH-D700 using xda app-developers app
If there is a SimplyCM10 Kernel version with Voodoo Color in the future, could there please be one without? I can't stand Voodoo Color, personally.
So I Odined FC09, flashed ACSRecovery5-1.0, to flash CM-9.1.0, & I flahed SimplyCM10 & everything seemed cool, but in the end it would not boot passed the Sammy/Cyan screen.
Agent Soap said:
So I Odined FC09, flashed ACSRecovery5-1.0, to flash CM-9.1.0, & I flahed SimplyCM10 & everything seemed cool, but in the end it would not boot passed the Sammy/Cyan screen.
Click to expand...
Click to collapse
Then it doesn't work for cm9 only cm10/JB roms
Sent from my SPH-D700 using Tapatalk 2
Agent Soap said:
So I Odined FC09, flashed ACSRecovery5-1.0, to flash CM-9.1.0, & I flahed SimplyCM10 & everything seemed cool, but in the end it would not boot passed the Sammy/Cyan screen.
Click to expand...
Click to collapse
Here's your likely source of the problem... although it is stated in the OP that the kernel is not guaranteed to work with CM9.
MДЯCЦSДИT said:
Nyan doesn't lock up
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Nyan for CM10 with Voodoo Sound and Color? If so, I'll install it right now! (Just need a link lol)
dohturdima said:
Here's your likely source of the problem... although it is stated in the OP that the kernel is not guaranteed to work with CM9.
Click to expand...
Click to collapse
Once I was using CM-9.1.0 my recovery was CWM6. I only used ACSRecovery because it works for me when I Odin.
---------- Post added at 09:09 PM ---------- Previous post was at 09:04 PM ----------
brickwall99 said:
Nyan for CM10 with Voodoo Sound and Color? If so, I'll install it right now! (Just need a link lol)
Click to expand...
Click to collapse
Dude, it's on the front page
[ICS] Nyan Colonel v5 (Atarashii) Voodoo & No Voodoo
Agent Soap said:
Once I was using CM-9.1.0 my recovery was CWM6. I only used ACSRecovery because it works for me when I Odin.
---------- Post added at 09:09 PM ---------- Previous post was at 09:04 PM ----------
Dude, it's on the front page
[ICS] Nyan Colonel v5 (Atarashii) Voodoo & No Voodoo
Click to expand...
Click to collapse
Isn't that only for CM9?
brickwall99 said:
Isn't that only for CM9?
Click to expand...
Click to collapse
not the one I posted on the last page of that thread with cm10 support
Hi all, so I've been wanting a really nice optimized Linaro recovery and have not been able to find one. So I decided to build my own and have found it to be very nice and stable, and of course to share with all of you xda peps
First off if you don't know what TWRP recovery is the original nexus 7 thread is HERE
Please read all of the original thread before flashing this recovery.
More info on how this recovery was built
Built using Linaro gcc 4.7 toolchain. I also built the toolchain from Linaro's gcc source. The toolchain source is HERE
This toolchain source gets update almost daily from linaro sources, but I don't normally have the time to build new toolchains daily. When I have time I will update it quite frequently.
Built off my own 4.1.2 kernel source. The kernel used to build this recovery was also compiled using the Linaro 4.7 toolchain.
I've added a few linaro recovery patches for interfaces to libpng. Those changes are HERE and HERE.
Built using Linaro bionic string routines optimizations.
Installation
Download the recovery image and flash in fastboot
Initial release 2.3.1.1 touch recovery
10.28.12 release 2.3.1.1 touch recovery
Kernel changes
Removed a lot of bloat from the kernel. I disabled GPU overclocking, user voltage control, cpu overclocking, a bunch of useless debugging stuff.
A short kernel changelog is HERE
Toolchain changes
Not much here. I included a static library to be used in the toolchain libiberty
A short changelog for the toolchain is HERE
Recovery changes
Built as engineering instead of userdebug.
11.5.12 release 2.3.1.1 touch recovery
Final android 4.1.2 linaro recovery version
Kernel changes
Mainline linux kernel upstream changes from linux-3.2.y
Changed kernel compression mode to GZIP and optimization level to -Os
Toolchain changes
Updated to latest linaro changes
Recovery changes
-O3 optimization level
Linaro strict-aliasing compiler flags optimization
Android-4.1.2 (This version is a final release, no more updates)
Size: 6.95 MB
MD5: e0f46f01556156b052b3779c9ed60e01
What? A Linaro recovery? I did not know there was such thing. I am downloading this now very excitedly.
Thank you. Very very helpful and nice.
OK... Now I need more info! I sorta understand the Linaro concept but my knowledge is limited. What's the reasons to base Recovery on it at this point? Any advantages, possible concerns? Will there be any noticeable differences? Just curious & wondering cause you said "you'd been wanting to make a recovery based on linaro".
Thank!
Sent from my Nexus 7 using Tapatalk 2
Hi men!
Thanks for your recovery.
But i experience some strange visual effects like distortion of the image or some lag effects.
---------- Post added at 04:21 PM ---------- Previous post was at 04:16 PM ----------
djd338 said:
OK... Now I need more info! I sorta understand the Linaro concept but my knowledge is limited. What's the reasons to base Recovery on it at this point? Any advantages, possible concerns? Will there be any noticeable differences? Just curious & wondering cause you said "you'd been wanting to make a recovery based on linaro".
Thank!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
There is a discussion on this subject regarding some tests Ezekeel (XDA developper) made with different cross-compiler toolchains and those tests prooved that none of the compilers is better than another.
We heard a lot about linaro because when ICS was released, it was very laggy and linaro and is new compiler version 4.7 made ICS much smoother than before.
But for the pur performance linaro give no improvement if you compare with another one.
EDIT: I found the link of the test for you: http://forum.xda-developers.com/showpost.php?p=19872366&postcount=1
i remember this test,and also in my home test when i tried to build kernel,i don't see improvement using linaro or others toolchains..anyway it's great to have another thing to play on and see if it's best that the ufficial!
sert00 said:
i remember this test,and also in my home test when i tried to build kernel,i don't see improvement using linaro or others toolchains..anyway it's great to have another thing to play on and see if it's best that the ufficial!
Click to expand...
Click to collapse
Agree with you.
It wasn't for discredit the work of sparksco. I'm glad to test his work.
Just answer the question for the cross-compiler.
Thanks for the work sparksco
[email protected]_OC said:
Hi men!
There is a discussion on this subject regarding some tests Ezekeel (XDA developper) made with different cross-compiler toolchains and those tests prooved that none of the compilers is better than another.
We heard a lot about linaro because when ICS was released, it was very laggy and linaro and is new compiler version 4.7 made ICS much smoother than before.
But for the pur performance linaro give no improvement if you compare with another one.
EDIT: I found the link of the test for you: http://forum.xda-developers.com/showpost.php?p=19872366&postcount=1
Click to expand...
Click to collapse
That's one test with one toolchain by one developer. As far as I can tell he tested everything with one of linaro's really old toolchaons when they first released 4.6. So by looking at the dates I would guess linaro didn't add much to the toolchain at that point. There's also the GCC version to consider. This is using 4.7 and not 4.6. And lastly there's rom patches that linaro puts out that have nothing to do with the kernel but are used in the ROM building process when building recoveries. It's all debatable. I find this to be a bit smoother and backups seems to be a little faster but maybe it's just me.
[email protected]_OC said:
Hi men!
Thanks for your recovery.
But i experience some strange visual effects like distortion of the image or some lag effects.
Click to expand...
Click to collapse
Your going to have to provide more info than that. Your method of installing, what bootloader you have ect. Thanks.
Edit: flashing zip in recovery causes issues so I removed that method of installing.
sparksco said:
That's one test with one toolchain by one developer. As far as I can tell he tested everything with one of linaro's really old toolchaons when they first released 4.6. So by looking at the dates I would guess linaro didn't add much to the toolchain at that point. There's also the GCC version to consider. This is using 4.7 and not 4.6. And lastly there's rom patches that linaro puts out that have nothing to do with the kernel but are used in the ROM building process when building recoveries. It's all debatable. I find this to be a bit smoother and backups seems to be a little faster but maybe it's just me.
Click to expand...
Click to collapse
thanks.after give a try to this recovery,i agree with you with fact of possible quickest backup time.the general use is good,don't know if it's real an improvement,but i did a backup and at first look it seemed quicker..possible placebo effect,let's see what others say..
why you pulled cwm install version...bugged?
There's a lot of factors to consider. Just the fact that this is using a kernel I built with 4.7 from my own source code could improve things as well. FYI the kernel includes GPU overclocking.
sert00 said:
why you pulled cwm install version...bugged?
Click to expand...
Click to collapse
Read one post above yours...
Sent from my Nexus 7 using Tapatalk 2
sparksco said:
There's a lot of factors to consider. Just the fact that this is using a kernel I built with 4.7 from my own source code could improve things as well. FYI the kernel includes GPU overclocking.
Read one post above yours...
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
oh thanks,not saw the edit in the post!
New version is up.
Sent from my Nexus 7 using Tapatalk 2
I installed last night using goomanager, so I assume I have the previous version?
Anyway, it works great, so thanks.
stonebear said:
I installed last night using goomanager, so I assume I have the previous version?
Anyway, it works great, so thanks.
Click to expand...
Click to collapse
I am pretty sure you get the Official TWRP version from goomanager not this. Please correct me if I am wrong but I think that is what the Unofficial means.
zedorda said:
I am pretty sure you get the Official TWRP version from goomanager not this. Please correct me if I am wrong but I think that is what the Unofficial means.
Click to expand...
Click to collapse
Yea, I just realised that myself when I saw there were two threads.
What's the difference between this and ClockWorkMod? Is it more stable?
Neo3D said:
What's the difference between this and ClockWorkMod? Is it more stable?
Click to expand...
Click to collapse
Some more features on TWRP I think, especially the queue to flash multiple ZIP files. Flash it and see for yourself
modstorm said:
Some more features on TWRP I think, especially the queue to flash multiple ZIP files. Flash it and see for yourself
Click to expand...
Click to collapse
That, and I like the fact that you have an option to wipe cache/dalvik after flashing something
markj338 said:
That, and I like the fact that you have an option to wipe cache/dalvik after flashing something
Click to expand...
Click to collapse
That and TWRP can also be themed however I never found any themes :/
After trying other ROM's, I would always come back to CM 10.1 for its infrastructure, stability and clean features, however I still wanted experimental bleeding edge optimizations like the Linaro toolchain.
These releases will only feature Linaro toolchain and bionic optimizations and keep CM10.1 unaltered for the most part. I did no work whatsover, just compiled with patches by others. If you want to learn how, there's a tutorial on post #3
Instructions
NANDroid
Wipe/Factory Reset if coming from anything other than CM 10.1 (Seems to be okay to dirty from from non-linaro previous cm nightlies)
Wipe Cache
Flash .zip
Flash custom kernel
Flash gapps if needed
Reboot
Download
www.trailblazerz11.com
Goo.im Also Availible on GooManager
Nexus 4 Thread
Disclaimer: I am not responsible for anything that may happen.
Credits:
Cyanogenmod
Linaro
Google
Eug39 for help with errors
Evan McClain for cm10.1 gerrit patches
codeworkx for patches
bricked for kernel patches
EvoXOhio for helping get this whole thing started
Github
https://github.com/trailblazerz
Changelog (besides cm changes)
5/24- libm: sqrt and sqrtf via ARM vsqrt instruction.
5/13- mvectorize-with-neon-quad
4/24- -mcpu=cortex-a9
4/14- Updated to 2013.04 Linaro Thanks kszaq again
4/4- Arch specific strcmp from Google
4/3- Updated to 2013.03 Linaro Thanks kszaq
3/4-Updated kernel to Googles 4.2.2 tag
2/23-Grouper bluetooth fix, Thanks Eug
2/18-ARMv7 optimized memchar()
A-15 memspy
Change Krait flag value
2/13-Added bionic improvement to memspy from paranoid android
Added vfpv4 flag
2/11-Added bionic optimizations for A-9 from CM gerrit
Added some flags
2/8-All widgets now work in lockscreen
2/6-Added ARMv7 optimizations to bionic
2/5-Initial Release patched to compile with linaro
Tutorial Revamped Feedback please
Tackle_berry was able to compile it and modified the tutorial http://forum.xda-developers.com/showpost.php?p=39567944&postcount=623
Set up CM build environment - CM wiki
Best to compile a build so you know everything is working before adding Linaro
note: My build enviroment is on Arch Linux on latest RC kernel.
Download and set up Linaro toolchain
http://www.linaro.org/downloads/ Components, Android, Linaro 4.7 ICS/JB
Extract and rename the folder to linaro-4.7 and place it in /prebuilts/gcc/linux-x86/arm
"Linarize" Automated now
Start a linaro branch if you are going further add to it otherwise you can skip the following and work off branch and just apply the script every time.
Code:
repo start linaro --all
Download the attached script and run it. It will cherry-pick all the linaro patches (with the exception of bionic which is pulled)
Done
Updating
repo sync to sync from CM then run the script again if you didnt make a linaro branch. If you did repo sync should automatically update your branches
I cannot control repo syncs causing conflicts or new commits from CM (or by you) cause build errors. I will try to fix and upload changes asap.
IMO the most enjoyable part of compiling your own build is banging your head on an error then eventually finding a fix and having everything work as its suppose to. It's about the journey
Re: [ROM] [KANG] Linaro CM 10.1
I'm gonna give it a whirl,I dig the Linaro Kernel, its a monster on the 10.1 nightlies. I'm bummed about the bugs with cifs mounting on 4.2 but Subsonic is awesome so its doing the trick for now.
Re: [ROM] [KANG] Linaro CM 10.1
Using it on Nexus 4 since this morning with Franco #61 kernel. No issues so far but still early.
Sent from the singletrack....
New 2/6 build tested and uploaded. Synced fresh from CM and also added some ARMv7 optimizations to bionic
Re: [ROM] [KANG] Linaro CM 10.1 Nexus 4&7 *2/6*
2/8 nightly uploading
Synced and mako has new pow() optimization fixed.
Sent from my Nexus 4 using Tapatalk 2
2/15 Grouper Uploaded, 4.2.2 merged.
Was too busy to find new blobs(if there are any?) but works fine for me
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/15 Nightly 4.2.2*
trailblazerz11 said:
2/15 Grouper Uploaded, 4.2.2 merged.
Was too busy to find new blobs(if there are any?) but works fine for me
Click to expand...
Click to collapse
Thanks this is awesome
Sent from my SGH-T999 using xda app-developers app
Hi trailblazerz11, I was flashing too many things the past week since I was not happy on the smoothness. So I decided to return on CM and try your ROM. I just started to use but it feels already very smooth. I will feedback more in a few days. However, thanks so far!
trailblazerz11 said:
2/15 Grouper Uploaded, 4.2.2 merged.
Was too busy to find new blobs(if there are any?) but works fine for me
Click to expand...
Click to collapse
HI, as you know I'm building cm-10.1 with basically the same mods you are using. Just wanted to ask you if bluetooth works in this rom, because, since the 4.2.2 update, bluetooth is broken on my builds.,
wonder if it works on nexus 7 3g
Re: [ROM][KANG] Linaro CM 10.1 + Bionic *2/16 Nightly 4.2.2*
eug89 said:
HI, as you know I'm building cm-10.1 with basically the same mods you are using. Just wanted to ask you if bluetooth works in this rom, because, since the 4.2.2 update, bluetooth is broken on my builds.,
Click to expand...
Click to collapse
Flashing this in recovery should fix bluetooth.
https://www.dropbox.com/s/omjuuielei3z5p6/4-2-2BluetooohFix-Fix.zip
Sent from my Nexus 7 using Tapatalk HD
RobertsDF said:
Flashing this in recovery should fix bluetooth.
https://www.dropbox.com/s/omjuuielei3z5p6/4-2-2BluetooohFix-Fix.zip
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks, this fixes it.
Re: [ROM][KANG] Linaro CM 10.1 + Bionic *2/16 Nightly 4.2.2*
This is really great! Thanks
Sent from my Nexus 7 using Tapatalk HD
Re: [ROM][KANG] Linaro CM 10.1 + Bionic *2/16 Nightly 4.2.2*
Will upload 2/18 nightly when I get home.
Didn't know about the Bluetooth issues, hopefully new nightly fixes. Thanks for the fix
Sent from my Nexus 7 using Tapatalk HD
EDIT: Uploaded
R: [ROM][KANG] Linaro CM 10.1 + Bionic *2/18 Nightly 4.2.2*
trailblazerz11 said:
Will upload 2/18 nightly when I get home.
Didn't know about the Bluetooth issues, hopefully new nightly fixes. Thanks for the fix
Sent from my Nexus 7 using Tapatalk HD
EDIT: Uploaded
Click to expand...
Click to collapse
Did you have to use the bluetooth.default.so file contained in the zip posted above to get the Bluetooth to work or It was already working fine in your builds?
Re: [ROM][KANG] Linaro CM 10.1 + Bionic *2/18 Nightly 4.2.2*
eug89 said:
Did you have to use the bluetooth.default.so file contained in the zip posted above to get the Bluetooth to work or It was already working fine in your builds?
Click to expand...
Click to collapse
Not fixed in 2/18 had to flash it too
Sent from my Nexus 7 using Tapatalk HD
R: [ROM][KANG] Linaro CM 10.1 + Bionic *2/18 Nightly 4.2.2*
trailblazerz11 said:
Not fixed in 2/18 had to flash it too
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Does your build for the nexus 4 have the same issue?
bluetooth.default.so gets compiled from external/bluetooth/blue droid but I haven't made any changes from cyanogenmod's source in that repo and in the official nightlies BT seems to work fine. It could be some compiler flag, next time I'll try building without the -03 optimizations.
Re: [ROM][KANG] Linaro CM 10.1 + Bionic *2/18 Nightly 4.2.2*
eug89 said:
Does your build for the nexus 4 have the same issue?
bluetooth.default.so gets compiled from external/bluetooth/blue droid but I haven't made any changes from cyanogenmod's source in that repo and in the official nightlies BT seems to work fine. It could be some compiler flag, next time I'll try building without the -03 optimizations.
Click to expand...
Click to collapse
It works fine on mako. Yeah, probably something with linaro or O3
Sent from my Nexus 4 using Tapatalk 2
FEATURES FOR 4.3:
Code:
-Built with latest CM10.2 sources
-latest linux 3.4.65
-Compiled with Linaro 4.8.2
-Overclocked to 1620Mhz
-Underclocked to 270Mhz
-fast charge support
-faux sound support
-CM cherrypick to prevent battery drain (thanks for finding it pwncake)
-Added Governors
+intellidemand
+badass
+wheatley
+smartassH3
+asswax
+smartmax
-Added IO Schedulers
+sio
+tripndroid
+fifo
-thalmus hot plugging
-frandom support
-undervolting and user undervolting (minimum is 900, anything below this won't change anything)
-modified colors (sort of like trinity but my modifications)
-gpu OC to 480
This rom currently supports the Trickster Mod App - get it here https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
PM me if you need any help starting up your own kernel
Downloads for 4.3:
BionicSheep2v0.7.1_RC2
BionicSheep2v0.6.0_RC1
BionicSheep2v0.5.1
READ THIS PLEASE:
Everyone, sorry to disappoint but this kernel is now dead. Due to a serious serious issue with the git client, me trying to delete 1 repo caused the deletion of my kernels repo instead. There will be no builds anymore, I would have to start from scratch and I do not remember every line of code I have changed for the past 4 months.
My sincerest apologies to you guys, I am still shocked myself right now, I can't believe it did that.
I will keep downloads up for now but I doubt the kernel will work bug free into the future without keeping up with driver updates and such. If there are any GPL concerns from any mods here on xda, please let me know and I will take the links down. I had source up until it got deleted. Thanks for the help, experience, and the times guys. You made this kernel a wonderful learning experience for me. Look out for my app in the next few months guys, its my new project if git doesn't screw me on that too.
My settings:
Gov: asswax
IO: fifo
Read ahead: 1024
Voltages: (stock, I pick them in the first place )
GPU: 480
Powersaving: 0
Mpdecision: its gone so enabling it does nothing
Sources:
https://github.com/BionicSheep/android_kernel_samsung_d2.git
Special thanks to:
ahagersr - for getting me started up and giving me hours of reading material
stratatak7 - for helping with packaging and voltage fixes
gideonX - for his patience and willingness to answer my nooby questions
pwncake193 - for helping me with 4.3 sources and kernel start up for it (send him thanks guys)
ktoonsez - for his patience and willingness to answer my nooby questions
imoseyon - fastcharge
TripNRaVeR - for his IO scheduler
faux123 - for his awesome sound support
the community - help in general
Changelog
Code:
10.07.2013 Release Candidate 2
-cm updates
-linux 3.4.65 updates
-GPU overclocking to 480
-0ms latency deadline scheduler (credits Imoseyon)
10.03.2013 Release Candidate
-cm updates
-asswax tunables adjusted to personal preference. Ramps up slower but also ramps down slower, also focuses on lower
clocks at screen up and deep sleep. Check the git if you're curious
-Linaro 4.8.2 instead of 4.7 used to compile
-Latest linux 3.4.64
-378 clock changed back to 384 (so much more stable and battery friendly)
-voltage adjustments
This is probably my last build for this phone, when the Nexus 5 comes out I will probably get it and sell my gs3, so if the
price is less than $350, this will be it guys. Thanks for testing as I made my first kernel. I learned a lot! If any huge issues
present themselves I will obviously update it.
08.23.2013(4.3)
-vital info for this build is in red in op
-okay so all this torch nonesense is fixed
-linux 3.4.59 updates
-latest cm sources
-voltage tweaks
-smartmax governor added (info on it [URL="http://forum.xda-developers.com/showpost.php?p=38193047&postcount=6943"]here[/URL])
-tweaked sheep colors and colors are whiter than ever!!
08.20.2013b(4.3)
-fixed torch once and for all the cheeky little bugger
08.20.2013(4.3)
-linux 3.4.58 updates
-latest cm sources
-fixed torch
-bionicsheep colors should be implemented on boot (no yellow tint)
-voltage tweaks
Thanks for this! I'll give it a run.
Sent from my SCH-I535 using xda app-developers app
Well I see Imoseyon's name in the thanks section so that's good. Anything from him i'm a fan of. Thanks for another kernel option.
TokedUp said:
Well I see Imoseyon's name in the thanks section so that's good. Anything from him i'm a fan of. Thanks for another kernel option.
Click to expand...
Click to collapse
Haha yeah borrowed his fast charge code so I figured I woild give him credit
Just flashed and got a lot o flicker, im on slim 4.3 beta 1
Sent from my SCH-I535 using Tapatalk 4
juancaperez2000 said:
Just flashed and got a lot o flicker, im on slim 4.3 beta 1
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Read red text in op
aeppacher said:
Read red text in op
Click to expand...
Click to collapse
Sorry about not read, ill be testing as soon slim update them builds thanks for your quick response
Sent from my SCH-I535 using Tapatalk 4
juancaperez2000 said:
Sorry about not read, ill be testing as soon slim update them builds thanks for your quick response
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
No problem. It should work with the official cm10.2 nightlies if you wanted to try
juancaperez2000 said:
Just flashed and got a lot o flicker, im on slim 4.3 beta 1
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I'm in the same boat, tried latest BMS with same results. Can't wait for slim to update so I can try this kernel!
This is my rifle, I am The Gun!
This is pretty chill on notta PA Aug 15
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Maphack said:
This is pretty chill on notta PA Aug 15
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Do me a favor and check if torch is working with pa and this kernel. Gracias
aeppacher said:
Do me a favor and check if torch is working with pa and this kernel. Gracias
Click to expand...
Click to collapse
Using Tesla led it works fine.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
aeppacher said:
Do me a favor and check if torch is working with pa and this kernel. Gracias
Click to expand...
Click to collapse
Didn't even realize torch was a built in app.
It doesn't work, just force closes if I touch the bulb. I've never used the app before though so I might be doing it wrong
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Maphack said:
Using Tesla led it works fine.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Didn't even realize torch was a built in app.
It doesn't work, just force closes if I touch the bulb. I've never used the app before though so I might be doing it wrong
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Nah its the kernel aosp is a mess right now . Just wanted to check if it was cross carrier. Thanks for the feedback.
aeppacher said:
Nah its the kernel aosp is a mess right now . Just wanted to check if it was cross carrier. Thanks for the feedback.
Click to expand...
Click to collapse
Glad I could kind of help lol.
Thanks for a non-tearing custom kernel
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Kernel is running awesome so far, thank you
Sent from my SCH-I605 using Tapatalk 4
aeppacher said:
Do me a favor and check if torch is working with pa and this kernel. Gracias
Click to expand...
Click to collapse
Torch doesn't work on Carbon as well.
Sent from my SCH-I535 using xda app-developers app
Torch works on slim 4.3.
Eat Play Google
bigshotrob22 said:
Torch doesn't work on Carbon as well.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maphack said:
Using Tesla led it works fine.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Didn't even realize torch was a built in app.
It doesn't work, just force closes if I touch the bulb. I've never used the app before though so I might be doing it wrong
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Torch is fixed on latest build that I just uploaded (make sure its v0.4.5b)
Anyone have a mirror to 8/20? Downloads are still down
Sent from my SCH-I535 using Tapatalk 4
dems86 said:
Anyone have a mirror to 8/20? Downloads are still down
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
No mirrors please, if I take the downloads down, I do it for a good reason (it could hurt your device). There has been IMEI issues with all CM based kernels for d2 devices recently. In order to get your IMEI back you have to reinstall rom, gapps, and then the kernel all in one go. I will build with latest fixes and source sometime tonight for you guys.