Develop Bugs

[Kernel] .29 Alpha for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient

[Kernel] .29 Alpha for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient
Here's a quick and dirty kernel compile with bluetooth and SetCPU OC both working for this ROM (and any Cyanogenmod based Hero ROM really). Should not be overclocking on boot.
Uses koush anykernel format to make it compatible for any CM based ROM.
I don't plan to update this. I had no intentions of making a Hero kernel so I probably wont be updating this. It was kind of an accident. I don't even have a GSM Hero. Anyways flash and enjoy! Devs can take what I did on my .config and make it good. There's some weird stuff in it.
If this eats your phone please do not hunt me down.
jaymac407 said:
Boots, testing more now..
Update: Wifi works, bluetooth works, OC seems to work (I THINK)
Good work.
Click to expand...
Click to collapse
I copied the netfilter options too. If someone can try to see if Wifi-tether works that would be awesome.
So apparently my kernel boots this aHero and fixes bluetooth. It's a .29 kernel based on the new source code.
Mind you that I might be missing some things. I took around 20 minutes comparing the existing .config and making one that is more similar to the Cyanogenmod .config by eyeballing differences and copying pasting code (yes really). I got really lazy toward the end because the .config was so damn long.
I at least enabled squashfs so the .sqf files decompress for sure now. Set localversion to cyanogenmod. You can see what I did to it in the download link as well, where I have a pastebin of what I did before I disabled perflock.
I also disabled a crap load of debug options that were enabled for some reason.
credits:
cyanogen for CM5. Based .config off his ROM
toastcfh for the kernel source code and being the father of all MSM7K overclocks
koush anykernel
.config here:
http://forum.xda-developers.com/showpost.php?p=6548814&postcount=53

how do i use this on ahero ? just flash it over the rom ?

Is this applicable to VanillaEclair?

Just flash this zip over my aHero?

Re: [Kernel] .29 Beta for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient
Dont work for me om cyanogen mod, runs so slow it freezes. Cant get in set cpu and look
Sent from my HTC Hero using Tapatalk

going to test this now. I will update.

it sseems to freeze at boot (aHero 1.0 with JIT)

mine freeze at hero screen

Does it need a wipe and reflash first, or should it be ok to try over current CM ROM ( Vanillain 3.0 test version) ?

furrypotato said:
Does it need a wipe and reflash first, or should it be ok to try over current CM ROM ( Vanillain 3.0 test version) ?
Click to expand...
Click to collapse
There specific patches for the villain roms, theres one for Vanillain 3. There is a thread with them on xda
I tired it on Vanillian but cant seem to get past the lockscreen

I downloaded toastcfh's kernel source, but I didn't have time to compile..
anyway thanks for compiling, and I'll test it and report back soon..

Demologic said:
There specific patches for the villain roms, theres one for Vanillain 3. There is a thread with them on xda
I tired it on Vanillian but cant seem to get past the lockscreen
Click to expand...
Click to collapse
And me. Best wait I guess for a fix later.

Heh, awesome.
Be advised that this sometimes freezes randomly, that's the only bug I can see so far. Especially during going from and to sleep. That's the only issue that needs to be resolved. Apart from that, everything seems to work.

jaymac407 said:
Heh, awesome.
Be advised that this sometimes freezes randomly, that's the only bug I can see so far. Especially during going from and to sleep. That's the only issue that needs to be resolved. Apart from that, everything seems to work.
Click to expand...
Click to collapse
Try in setcpu to make the governor performance, if not msm7k
the ondemand governor code was broked in HTC source in .27

can i download the zip and flash it on ahero 1.0????

xaueious said:
Try in setcpu to make the governor performance, if not msm7k
the ondemand governor code was broked in HTC source in .27
Click to expand...
Click to collapse
Only options are performance and ondemand. Neither option seems to help with the crashes.

i have downloaded the zip on first page and flash over ahero 1.0 without JIT my phone boots and come to lockscreen and then i cant anything

[kernel/rom] cm9/ics build with fixes [02/09/2012 flash.zip update or full rom]

[ 02/09/2012: Screen Flicker / Brightness is an issue. I'll be looking at it. ]
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time and built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Moving forward into CM9/ICS, some changes need to happen to the kernel over time. The migration kernel is found in a branch: "L27.13.1-ICS". The END result of this will be a kernel / source that fully support hw codecs for ICS.
[02/08/2012] FLASH ZIP FOR THOSE RUNNING NIND'S BUILDS: http://bit.ly/xYOf0V
The following ROM is built from the sources at GitHub under the KFire-Android org. Many of those files and configurations are the result of countless hours of development by JackpotClavin. I don't want there to be any confusion as to who put in a ton of time getting this to work.
[02/09/2012] FULL ROM INSTALL: http://bit.ly/ygVvQB
Changelog:
- Screen flicker IS an issue right now. Digging into it
- Touchscreen "Slop" set to 16. This should help touches register on the touchscreen.
- Working Data usage stats (xt_qtaguid / xt_quota2 kernel modules)
- TUN, CIFS support
- USB mounting fixes

Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...

nind said:
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
Click to expand...
Click to collapse
If you want to follow a very good step by step guide for setting this up the same way TI (the CPU maker) intended, then follow this:
http://www.omappedia.com/wiki/PandaBoard_L27.12.1-P2_Release_Notes#Setting_up_build_environment
Obviously, that's for PandaBoard, but the Toolchain source and setup are very good.

It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.

Hashcode said:
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time nd built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter2_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Tonight, I'll go back to both of my in-progress kernels and do some testing to see if they'll boot.
EDIT:
Current issues being looked at with this kernel:
- Power off doesn't really power all the way down. It goes to a black screen, but requires long press to turn off.
- Deep sleep isn't happening. The backlight is on a tad while the screen should be off.
But this config is still MUCH better than trying the original.
Click to expand...
Click to collapse
So does this boot cm7 or anything? My kernel builds boot stock kindle but not cm7
Its something to do with netd/dnsproxyd. Just finding a fix that works is a PITA common issue, but then people dont say how they fixed it..

Right now ive only tested this with CM9
Sent from my DROID RAZR using XDA App

touch points
Any chance you're looking into enabling more than 2 touch points in this kernel?

foxdog66 said:
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Click to expand...
Click to collapse
I'm running nind/sitic's cm9-02-04 build with this kernel baked in. I, too, have Stay Awake disabled in Developer Options, and my Kindle is going into deep sleep. I am experiencing the power down issue, though.
It's something I'm absolutely willing to live with for the time being. This is good stuff. Thanks Hashcode!

jabdo79 said:
Any chance you're looking into enabling more than 2 touch points in this kernel?
Click to expand...
Click to collapse
Thats really the future of this kernel. I needed a solid base to start from.
Sent from my DROID RAZR using XDA App

Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.

death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Right now the difference between this kernel and stock is:
- About 8 ip6 netfilter modules were added
And that's about it.

death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet

wdfowty said:
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
Click to expand...
Click to collapse
ill look into insectraven's cm kernel thanks!
Edit: That worked! Thanks!
he starts the dnsproxyd differently than what I've seen. But it works!

So I noticed that /mnt/ is mounted read-only which causes issues with apps installing to the sdcard and probably the issue people are having with mounting the sdcard to the computer. Some apps insist on installing to the sdcard (I hate that)
Edit: or do I have this all wrong? Lol I'm no dev remounting it r/w gets the job done.

Is there any websites or anything that you guys would recommend to learn about the Linux kernel and development of it?

Tonight, I went back through and cleaned up my config some more. Removed extra power controls, usb mtp settings and omap mmc host controller (for sd card slot boards).
From my tests, everything deep sleeps correctly and the power off issue is fixed.
https://github.com/KFire-Android/kernel_omap

will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please

foxdog66 said:
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
Click to expand...
Click to collapse
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App

Hashcode said:
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
Yeah that's cool.

foxdog66 said:
Yeah that's cool.
Click to expand...
Click to collapse
Here's an updated boot.img for nind's 2/5 build:
[ UPDATED OP W/ FLASH.ZIP FILE ]

[ROM][Unofficial/Experimental][Android 4.3] CyanogenMod 10.2 for SGS4A (int'l)

-------------------------Warning!-------------------------------------
This ROM is for SGS4A (int'l) ONLY. Does not work on SGS4 from AT&T as it has a locked bootloader.
Please refer to this thread for a bounty on the bootloader.
-------------------------Please note---------------------------------
This is an experimental build of CyanogenMod 10.2 running Android 4.3.
Meaning there's a couple of known issues with the camera. It is my hope these will be sorted out over time.
If anyone has any interest in helping out, please PM me. Or simply fork the code if you want.
-------------------------Instructions---------------------------------
Install CWM recovery from here.
Download most recent ROM from here.
Download most recent Google Applications for Android 4.3 from here.
Boot into recovery by holding the Volume Up button as the phone is booting.
Back up your current ROM inside CWM recovery.
Flash CyanogenMod ROM to your device using CWM recovery.
Flash Google Applications to your device using CWM recovery.
Do a wipe data/factory reset from within CWM recovery.
Reboot system
---------------------------Known issues-----------------------------
Several camera functions such as HDR don't work.
---------------------------Build from source------------------------
Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
when you initialize the CyanogenMod repository so you get the source for CM-10.2.
Download roomservice.xml (see below) and put in ~/android/system/.repo/local_manifests/.
Run 'repo sync' and compile with 'brunch jactiveltexx'. You can get the proprietary files from the ROM.
As always, I take no responsibility in case your phone blows up.
And thanks to the CM team for all their hard work.

Downloads
---------------------------CM-10.2 ROM (Android 4.3) -------------------
---------------------------cm-10.2-20130917-----------------------------------
CyanogenMod 10.2 - 20130917
CyanogenMod 10.2 - 20130917 (mirror - thanks to mrvovven)
---------------------------cm-10.2-20130910-----------------------------------
CyanogenMod 10.2 - 20130910
CyanogenMod 10.2 - 20130910 (mirror - thanks to mrvovven)
---------------------------CM-10.1 ROM (Android 4.2.2) ----------------
CyanogenMod 10.1 - 20130810
----------------------------Google apps -------------------------------
Download the official Google apps. Need to download this in order to have apps like Google Play.
For CM-10.1 choose Android 4.2 apps.
For CM-10.2 choose Android 4.3 apps.
http://goo.im/gapps
------------------------------------- KERNELS ---------------------------------
- SGS4A android 4.2.2 kernel for CM10.1
https://www.dropbox.com/s/oo1hr2n6evp3zu9/sgs4a-cm10-1kernel.zip

----------------------- Changelog--------------------
-------CyanogenMod 10.2 - 20130917----------
- Fixed video preview resolution
- Disabled zsl for slightly more stable camera app.
-------CyanogenMod 10.2 - 20130910----------
- Updated kernel to most recent version of cm-10.2 for SGS4.
- Replaced all sensor drivers with SGS4A kernel sources.
- Replaced several camera blobs in /system/lib/* with SGS4A versions enabling basic camera functionality.
-------CyanogenMod 10.1 - 20130810----------
Initial build.

Good job.
Sent from my Nexus 7 using Tapatalk 4

hello
anyone tried this out ?
feedbacks ?
thanks in advance

pdf5 said:
hello
anyone tried this out ?
feedbacks ?
thanks in advance
Click to expand...
Click to collapse
This is not something you should install unless you want to be compiling and debugging yourself. It's far from usable as day to day rom. I hope I'm clear on that.

Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help

LeJay said:
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
Click to expand...
Click to collapse
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.

aurelm said:
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
Click to expand...
Click to collapse
Honestly, not exactly sure how the setup is. I assume it's mostly in some proprietary libs separate from the kernel, but it's hard to find good information on it.
Sent from my GT-I9295 using xda premium

Thank you for you work!!
But search another File hoster!! DropBox close your account if the trafic is to big!!

So S4 Active Original is the intl i9295 ?
EDIT: oh ok the real dev thread
Sent from my GT-I9295 using xda app-developers app

I've a MicroSD in my SGS4A and i can't choose the external_sd in the CM File Explorer.
Is there any solution?
For example creating symlink or mounting in /sdcard
I've never tried anything of that!

It's working really well Wifi works yay, well done! Hopefully you can get the camera working too.

Building from source
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.

snadge said:
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
Click to expand...
Click to collapse
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.

Are you going to try to make CM 10.2?

LeJay said:
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Click to expand...
Click to collapse
I had a chat with noobnl about it, and he pointed out a patch on gerrit: http://review.cyanogenmod.org/#/c/44552/
I spent hours manually merging it with cm jf kernel, to finally end up with a kernel that gives me. You guessed it, a black screen. After investing about a days worth of effort into it, I ended up with a buggy unstable CM10.2 build, that will boot if I flash LeJay's kernel zip, but its unuseable. It's going to take some serious effort to come up with a functioning CM10.2 kernel for the International S4 Active. In the meantime, a CM10.1 build with a non functioning camera, is still way better than the stock TouchWiz rom, so I'm happy. :laugh:

Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.

snadge said:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
Click to expand...
Click to collapse
You probably forgot to add jactivelte to the list at the bottom of device/jf-common/Android.mk. I didn't want to fork their repo just to add one word on a line, so you have to do this manually. It's probably also a good idea to extract rom files from a cm.10.2 rom for something like jfltexx.

LeJolly said:
Are you going to try to make CM 10.2?
Click to expand...
Click to collapse
I have cm10.2 running. The problem is really the camera.

any good news for cm11?

if cm11 out i will buy one
Sent from my Moto G using Tapatalk

I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.

Riyal said:
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Click to expand...
Click to collapse
Not CM11, but still very exciting =)

TheQwertiest said:
Not CM11, but still very exciting =)
Click to expand...
Click to collapse
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel

Riyal said:
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Click to expand...
Click to collapse
We wait for CM11!
Xperia V, T doesn't have official 4.4 ROM too, but they have CM11.
Also, I think it's possibile developing CM11 or other CM11 based (KitKat) AOSP ROM.
Unfortunatelly I can't develop it...
I just will use it :fingers-crossed:

u guyz are lucky...u have munjeni wid u now. just be patient.. his hardwork brought cm11 novathor devices... which were abondoned on ics.
two reason i see z1compact as my next phone is that i dont like large phones and master munjeni has z1c also...

We can use CM11 from Z1 since Z1 CM11 on Z1C is working but there is no display available since CM kernel on MSM8974 need some changes related to the Z1C display Bad news is we can not use stock kernel since gralloc, copybit ..etc is not working than. I started working on CM kernel but hmmm CM kernel and stock kernel is a lot diferent so hard work is needed If we get CM kernel working we will get CM11 working with no big modifications
Edit:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded https://github.com/CyanogenMod/android_kernel_sony_msm8974 branch cm-11.0 . Maybe these kernel not working on Z1 too ???

Can't wait to try CM

kernel config from boot.img
munjeni said:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded{removed} branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Click to expand...
Click to collapse
Hello,
I am not sure if this is helpfull, but I'll give it a try: You are right - there is absolut no difference between the two kernel configurations, beside that one line. Since there are already nightlies available for the Z1(honami) I thought there might some helpfull informations inside that nightly. Of course there was a boot.img inside the nightly and I found that script to extract the kernel.config from that boot.img. Using the extract-ikconfig from my xperia z(yuga) kernel located in ./kernel/sony/apq8064/scripts/extract-ikconfig.
If the extracted config is reliable, there are indeed many differences.
I attached the extracted config. Maybe you remove the Lines starting with # and the blank lines for a better compare.
Let me know if I can help in some way.
Kind Regards

I don't know whats going on or why CM kernel is working on Z1 and not on Z1C but I think these fails on Z1C is related to the baseband and bootloader? Just asking, DO NOT FLASH THEM!!!
And another thing is maybe dtbs is a thing related to the fail since I can see some things in dmesg related to the pingpong command in mdss_mdp_intf_cmd.
Error log -> http://pastebin.com/9zgcWd4a

Thanks to the developers who are trying to make CM11 working on this phone. I will buy this phone if CM11 is available

@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.

Riyal said:
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Click to expand...
Click to collapse
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img

Nope, doesn't seem to boot :/

munjeni said:
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Click to expand...
Click to collapse
Yeah but I just relocked my bootloader yesterday. I won't be unlocking it till I get more time in development.
crytic said:
Nope, doesn't seem to boot :/
Click to expand...
Click to collapse
Weird then... The patch I applied to port z1 kernel to z1 compact made a fully working stock kernel. But when I applied it to CM kernel it doesn't even boot. Can you by chance get a copy of /proc/last_kmesg and upload it somewhere or here?

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # ←[6nuname -r
uname -r
3.4.0cyanogenmod-g77098c0-dirty
~ # ←[6n
Click to expand...
Click to collapse

munjeni said:
Click to expand...
Click to collapse
Woot! There it goes Now I don't have to port CM haha!

Sweet, with or without display?

crytic said:
Sweet, with or without display?
Click to expand...
Click to collapse
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.

munjeni said:
Click to expand...
Click to collapse
munjeni said:
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
Click to expand...
Click to collapse
git bisect to the rescue Well, if you need any help, just drop me a line!

[Q] Compile kernel

I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app

I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.

Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app

How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app

Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.

Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?

hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.

jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!

hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.

jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?

hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.

Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V

hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0

I'm ready to do that work only if i knew how to...
Sent from my One V

hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.