Develop Bugs

New kernel of VillainROM 3.0 BETA [Needed]

Hi,
after many failed attempts, I turn to you for something that is normally easy.
I want to compile a kernel for my Hero.
I am currently on this ROM: VillainROM 3.0 BETA
but in the context of a project (serial communication with the phone), i need a specific kernel.
If someone could edit the .config file with these details:
CONFIG_HTC_HEADSET
This entire line should be replaced with the following:
# CONFIG_HTC_HEADSET is not set
CONFIG_MSM_SERIAL_DEBUGGER
CONFIG_MSM_SERIAL_DEBUGGER_CONSOLE
and replace them with:
# CONFIG_MSM_SERIAL_DEBUGGER is not set
# CONFIG_MSM_SERIAL_DEBUGGER_CONSOLE is not set
compile the kernel and repost it would be great.
Thank you very to everyone, this forum is very interesting.
 +

Nymphe said:
Hi,
after many failed attempts, I turn to you for something that is normally easy.
I want to compile a kernel for my Hero.
I am currently on this ROM: VillainROM 3.0 BETA
but in the context of a project (serial communication with the phone), i need a specific kernel.
If someone could edit the .config file with these details:
CONFIG_HTC_HEADSET
This entire line should be replaced with the following:
# CONFIG_HTC_HEADSET is not set
CONFIG_MSM_SERIAL_DEBUGGER
CONFIG_MSM_SERIAL_DEBUGGER_CONSOLE
and replace them with:
# CONFIG_MSM_SERIAL_DEBUGGER is not set
# CONFIG_MSM_SERIAL_DEBUGGER_CONSOLE is not set
compile the kernel and repost it would be great.
Thank you very to everyone, this forum is very interesting.
 +
Click to expand...
Click to collapse
Sorry - I did answer you in the thread yesterday.
Have you attempted to compile it for yourself? If so, what was the outcome?

you won't be able to compile a kernel for a 2.1 rom since the sources aren't released yet. if you want to compile your own kernel you are stuck with 1.5 roms...
btw, where is your problem with compiling the kernel? i can try to do it later when i'm home, but again, we have only the 2.6.27 sources, which won't work for eclair roms (including villain).

nprussell said:
Sorry - I did answer you in the thread yesterday.
Have you attempted to compile it for yourself? If so, what was the outcome?
Click to expand...
Click to collapse
Sorry i didn't see it.
Yes I tried but I think without the right items.
I'm not a pro in kernel and ROM.
Already, it is possible to use the Vilain ROM with a modified kernel?
If yes, anyone could build it with the above specifications?
Thank you

oh boy, i need a new phone...

kendong2 said:
oh boy, i need a new phone...
Click to expand...
Click to collapse
???
Why this sentence ???

Nymphe said:
???
Why this sentence ???
Click to expand...
Click to collapse
I am guessing he means it is a lot of work and will need a dev phone to do it

no, actually a NEW phone. i am a bit frustrated with my hero right now, it has come down to noob talk in these forums. people ask for help "help my phone don't work", you ask them "why exactly, what does it say and what did you do before" and they answer "my phone won't work anymore, please help me". if you analyze this conversation it was like this:
a: i need a custom kernel for 2.1 and if i try myself it doesn't work.
b: you can't have one, the sources aren't out yet. what are your problems?
a: can someone make a custom kernel for 2.1? i tried but it didn't work.
going to ebay looking for a nexus, again...
now go and bash me for trying to help, i deserve it. definitely.

[DEV] LG P350 general dev thread - CM 7 & 9 or kernel development

THIS THREAD IS FOR DEVELOPERS ONLY!
Please do not post your problems with ROM here.
Post your ideas about working on ICS or CM7 and your problems with compiling sources or similiar.
I posted my p350 sources on github:
https://github.com/pax0r
You will find an instruction how to download mine soruces and compile it by yourself at:
https://github.com/pax0r/android_device_lge_pecan
Here we can speak how to improve this ROM ( 7.2 ) and also how to work on ICS. On my github you can find branch "ics" - it is somehow releated to my work on ICS but it's not complete.
So let's make our device EPIC!

For the begining I will post my problems releated to working on P350:
The problem I have with 7.2 release is that BT is not working - drapalyuk fixed it somehow in last release but I don't know how. If any one have idea what was changed from 1910 to 2010 drap release please let me know!
Also I started to port .35 kernel for our phone - but it's not working yet. Kernel boots and console via adb is usable at this moment but Android itself does not start on it. I will post more in this topic later.

now syncing the source

hi pax0r,
I'm trying to build CM 7.2 using your guide and source code but I notice a couple of issue that maybe create problems to someone beginner like me:
1) if you run ./extract-files.sh on a phone with CM 7.2 (vivekkalady) the extraction will fail on 3 files: libloc-rpc.so, libloc.so, libcommondefs.so. Maybe they are located in a different path.
2) I think this line of code in extract-files.sh is wrong:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.default.so
it should be:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.pecan.so
to avoid issue later.
I'd like to try to compile ics. What do you think is missing to make it works?
Best Regards,
Gabriele

hi pax0r,
the market crash few times at the begin but after I reboot it seems to be fine.
I attached the logcat.
Gabriele

megasoft78 said:
hi pax0r,
I'm trying to build CM 7.2 using your guide and source code but I notice a couple of issue that maybe create problems to someone beginner like me:
1) if you run ./extract-files.sh on a phone with CM 7.2 (vivekkalady) the extraction will fail on 3 files: libloc-rpc.so, libloc.so, libcommondefs.so. Maybe they are located in a different path.
2) I think this line of code in extract-files.sh is wrong:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.default.so
it should be:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.pecan.so
to avoid issue later.
I'd like to try to compile ics. What do you think is missing to make it works?
Best Regards,
Gabriele
Click to expand...
Click to collapse
Thanks for your contribute
For me there are no missing libs - I was running it on 7.1 so mby Vivek 7.2 is missing them?
About gralloc - there should be two libraries gralloc.default.so and gralloc.pecan.so
About ICS I have no idea yet and now no time to look at it - studies, work and 7.2 rom is everything I can do at once ;P

pax0r said:
Thanks for your contribute
For me there are no missing libs - I was running it on 7.1 so mby Vivek 7.2 is missing them?
About gralloc - there should be two libraries gralloc.default.so and gralloc.pecan.so
About ICS I have no idea yet and now no time to look at it - studies, work and 7.2 rom is everything I can do at once ;P
Click to expand...
Click to collapse
I think the problem about missing libs is related with vivek 7.2 rom.
it's strange but I can't see gralloc.pecan.so. Anyway I'll check it this evening.
I was able to build everything using your tutorial but now I want to try with ICS. I need a bit of searching on internet.
Thank you for your work,
Gabriele

Hm I've checked it and it fact there were no gralloc.pecan in extract - it was obviously a bug, I pulled everything from device, then I was making some refactoring and I didnt check it after that. I will push commit with fixes today.
Thanks for pointing it!

I see a keylayout headset push, how did you make the headset button works? I replaced both keylayout (qwerty with the haptic fix and 7k), but the dammed button still with problems =/
Thanks
PD: The new implementation of gralloc will fix the dammn warning of prelink? (on the log)

I'm not sure if this keylayout will make headset work as I don't have one but it was suggested that it may help but this need test. New gralloc is because it is open source comparing to the original propriety one and I'm testing its speed - it is at least the same so I will leave it
To solve a problem with prelink there should be a prelink.map created but I dont know exatly how to build one. It is not a critical error but with prelink.map the boot process could be faster.
I still didnt fixed copybit ;/
If you have some idea how to help refer to this post:
http://forum.xda-developers.com/showpost.php?p=21592280&postcount=28
EDIT: copybit fixed
hey could some one with the headset use this app:
https://market.android.com/details?id=aws.apps.keyeventdisplay
click headset buttons few times and post output of this app (if any)?
BTW do the headset buttons works on Vivek ROM?

Let me compile it with the new changes and I will try
At least, I'm currently using 7.1.0 (your 7.1.0) and nothing happens. (EDITED)

call\music button problem
paxor can u rectify the call\music button for wired headset

Can you compile ICS with your new files and send it to me ??
I will try to port ICS with your new files

Hey pax0r, are you sure with the fix? Compiled, installed... but I get a weird screen on menu =S
Thanks

I get a minor success at porting .35 kernel for p350. It boots and works but it still to bugged to public release. However if you have any dev experience you can grab it here https://github.com/pax0r/lge-kernel-msm7x27 and help me fix it!

I don't know exactly how Android handles GUI, IDK how to help right now, but I just can told you about the bug when android it's displaying interface.

Can you upload your compiled ICS so that we can tweak it to get it working!

I've removed my built version and now my source code wont even build :/

Hi Pax0r! well, i want to become a dev, i have some kind of linux knowledgement and have a good willing to learn, could you please point me out to some basic tutorials about building from cyanogen source? i've searched myself in the wiki but i didnt saw anything about lg pecan, any information you can give me, I will study it and maybe then become of help in dev community! thanks in advance!!

There is not much info about anything for P350 as it is not very popular device. Everything you need to start building CM for P350 is here, in mine Readme file:
https://github.com/pax0r/android_device_lge_pecan/blob/gingerbread/README.mkdn
Everything else you need to get by yourself =p but I will try answer all your questions
I learned everything by checking avaibale info for similar devices (MSM7227 board, for example: LG P500, ZTE Blade) and source codes.

[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 ]

AOKP ICS preprepre alpha

This is a very pre-alpa build of AOKP ROM.Known serious issue are h/w buttons,not all are working correctly,use onscreen ones.More functional update will be very soon
Credits
Goes to everybody working on ICS for hero and heroc
P.S I took updater-script from HeroICS ROM,hope guys wouldn't shot me
http://www.mediafire.com/?2qb7fk2w8dyiibw

:/
ported from where? more details..

1ceb0x said:
:/
ported from where? more details..
Click to expand...
Click to collapse
This one is ported from WFS,now compiling new wersion from sources

not bad few issues\recommendations after installing:
Max speed of 710 is a bit keen (default of 691 ?)
Recommend latest Nova Launcher (1.2 - lots of bug fixes)
SuperSU rather than SuperUser
Remove pointer following boot-up
Updater script saying installing CM 4.0.3 needs edit as 4.0.4 is installed ...
Advise that gapps are not included
Please dont take this as criticism, I certainly couldn't do this (tho i might have a bash somepoint)
I'd be happy to be guinea pig for testing further builds if you'd to pm me.

awesome! glad to see you guys have an aokp port now.
about the hardware buttons, wouldnt that have to do with the /usr folder? try to replace key layout related stuff with ones from heroics, and it should work.
if you need any help let me know

Download link not work correct..and one question if i understand good this is new port from new HTC Desire C ROM....ICS 4.0.4?
Thanks
P.S.Good will be to make your tread with more exact info like ROM version images from phone,change log and e.g

What works and what not?

jogai said:
What works and what not?
Click to expand...
Click to collapse
Hardware buttons except for menu, home and back (correct me if I'm wrong) don't work. However Keynrtracker (or check here for more information and keynrtracker.apk) resolves all the buttons. The problem doesn't seem to rely in /system/usr/keylayouts, but somewhere else.
Haven't had time to try this ROM out any further.

Build now maintained under:
http://forum.xda-developers.com/showthread.php?t=1795990

[Q] Kernel: usbhost + multitouch + norefresh for 1.2.1?

Hi,
I'm looking for a kernel (uImage) with usbhost + multitouch + norefresh for my NST firmware 1.2.1.
Thanks

me too actually. Altough i would not have to be a uImage. Zip files would also be awesome

Have you tried this one?
http://forum.xda-developers.com/showthread.php?t=1906507
I know there is a version with no-refresh and USB Host, not sure about multi-touch,

I'm also looking for one. Have USB host with keyboard working but would like kernel for 1.2.1 with drivers for audio, multitouch, etc

David0226 said:
Have you tried this one?
http://forum.xda-developers.com/showthread.php?t=1906507
I know there is a version with no-refresh and USB Host, not sure about multi-touch,
Click to expand...
Click to collapse
posts on that thread said that only version 166 works on 1.2.1
but only last version (174) of this kernel has usbhost support.
Maybe I misunderstood

jeff_kz has kernel config code here:
https://github.com/doozan/NookManager/blob/master/Buildroot/kernel-config

dnordquest said:
jeff_kz has kernel config code here:
https://github.com/doozan/NookManager/blob/master/Buildroot/kernel-config
Click to expand...
Click to collapse
Thanks for the information about the kernel but I don't have the skill to compile a kernel.
And I don't know which options to turn on in kernel-config to have usbhost, multitouch and no refresh at the same time.

The following two sources for uImage contain the identifier: Linux-2.6.29-omap1.
http://nst-recovery.googlecode.com/files/uImage_usb_audio_test.zip
http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip
That is the same identifier as the uImage I am using with 1.2.1. Whether either of the above will work with 1.2.1 I do not know & I am hoping someone with experience will say. Also, I am not sure if changes to any other file will be needed to get either running. The first file is said to have been deprecated, though why I know not.
I also do not know what drivers each contains besides those indicated in the name.

dnordquest said:
The following two sources for uImage contain the identifier: Linux-2.6.29-omap1.
http://nst-recovery.googlecode.com/files/uImage_usb_audio_test.zip
http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip
That is the same identifier as the uImage I am using with 1.2.1. Whether either of the above will work with 1.2.1 I do not know & I am hoping someone with experience will say. Also, I am not sure if changes to any other file will be needed to get either running. The first file is said to have been deprecated, though why I know not.
I also do not know what drivers each contains besides those indicated in the name.
Click to expand...
Click to collapse
I actualy use http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip on my nook 1.2.1. Usbhost and multitouch works but I can't enable norefresh on this kernel.

I've tried both uImages above & both work on my 1.2.1 but no-refresh unsolved here, too.