Database Develop

Kovsky Kernel Development [2.6.27]

Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem FIXED 01/05/10 (vdelf)
2. Battery Issue FIXED 11/05/10 (drlucky)
3. Camera
4. USB
5. GPS

Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of

:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do

dexteral said:
:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do
Click to expand...
Click to collapse
It will be great to do this, and stick it

@dexteral,
Anyone can checkout the kernel from the above repo I posted. To do what you require we would need to upload the Kernel everytime someone adds a patch...

vdelf said:
Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of
Click to expand...
Click to collapse
Is data transfer even possible in haret? I mean how would system unmount sdcard if it's running from sdcard itself?

not fast data but normal will work

love it
vietdoan20062006

Hi, Lets add fm-radio to the list

Great idea ... otherwise we are creating such a mess with lots of different kernel versions in different threads.
If anyone is interested in compiling the kernel as well as the wifi modules, I have setup a VMWare debian appliance containing all necessary tools and scripts to compile everything. Since this is a few hundes MB, I haven't got a place to upload ... need to check this first. If you are interested, let me know.

@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas

Can you post your modifications on the microp-module and what you found out until now?

_Sensible said:
Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem
2. Battery Issue
3. Camera
4. USB
5. GPS
Click to expand...
Click to collapse
hey could you post the steps involved for compiling the kernel i am able to comile the kernel but it is not running

Wich toolchain do you use? arm-2008q1 or arm-2009q3?

X1iser said:
Wich toolchain do you use? arm-2008q1 or arm-2009q3?
Click to expand...
Click to collapse
arm-2010q1
could u write all the commands used by you
the way i have written

Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?

X1iser said:
Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?
Click to expand...
Click to collapse
http://www.codesourcery.com/downloa...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
but may be it is not the right one it has got 202 in it insted of 67
ya i read that post only
i was able to compile the kernel but it is giving some errors

_Sensible said:
@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas
Click to expand...
Click to collapse
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...

okay i tried to make the kernel bt following the guide above by fatsal...
but i got stuck at
make htckovsky_defconfig ARCH=arm
htckovsky_defconfig doesn't exist (in the new repo anyway, i believe)
any help? which defconfig to use? :S

drlucky said:
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...
Click to expand...
Click to collapse
Just played with the klt-driver a bit. I always get version 0x0000, which on a hero means "bootloader mode". I have tried to migrate the hero code, but with no luck. It seems that the microp-klt needs a "reset", which shoudl be done by using a magical GPIO (on hero: 76), but this doesn't currently work at all. Kernel boots up, but still gets no valuable version number.

[RECOVERY] [UNOFFICIAL] CWM 6.0.3.0 TOUCH BASED RECOVERY fully working NO REBOOT BUG

Welcome happy campers
Here is a fully working pretty much fully tested port of Clockwork Mod Recovery 6.0.3.0
Big thanks to UTKANOS at #cyanogenmod irc channel for his help in building this for me to test till everything was working
FEATURES
All features in 6.0.3.0 based CWM recoveries are implemented
Touch screen working
Restore/Backup functions
All wipe functions
All Mount functions
Install from sd and Internal storage
Generally all features you expect from working ClockWorkMod recovery
without further ado here is the link to the recovery image: http://d-h.st/nMv
md5 Checksum : 8f7dda170425218f47717a9c9c931bea
source code at utkanos' github: https://github.com/utkanos/android_device_htc_golfu
Thanks goes out to mmmcfc for his initial work on the recovery we worked on to bring you this version, his original thread at :
http://forum.xda-developers.com/showthread.php?t=1785010
to install recovery is same as always for people who already know
for those of you who are new to this and do not know but are at the point of installing a custom recovery through a rom install guide please simply turn off your Desire C device, drop out the battery just in case fastboot is on in your rom settings, replace your battery then hold the volume down key and hold power button till you boot to bootloader.
Ensure phone is on fastboot setting (will have fastboot written in red if you are) plug in the usb cable and it should say fastboot usb now then enter this command from terminal window that is in the directory where you have this image downloaded to
Code:
fastboot flash recovery recovery-clockwork-6.0.3.0-golfu.img
with any joy you should now be able to reap the benefits of touch screen enabled up to date CWM recovery
enjoy
p.s. if you have issues installing this or do not know what our doing either do not install OR search the forums for root guide and recovery install guides and if you cannot find something relevant feel free to pm me
dont forget to come to our irc channel at irc.freenode.net ##HTCDesireCcm9 (dont forget to put two hash signs not one) we are friendly in the channel and are hoping it will begin to grow alongside development for the device
thanks
soon to come wifi fix for CM9, hopefully soon CM10 build and with all the fixes no doubt many custom roms from many users throughout our device section

Reserved this for maybe other information etc...

russell664 said:
Reserved this for maybe other information etc...
Click to expand...
Click to collapse
this is why we get along so well lol, albeit you do take forever to respond to irc chat but hey no one is perfect....

Great job :good:. Reboot is definetly fixed. Btw are you sure that device tree is updated with all the changes? I tried to build TWRP with that exact tree and still seem to have reboots.
Sent from my Nexus 4 using xda premium

nikhil16242 said:
Great job :good:. Reboot is definetly fixed. Btw are you sure that device tree is updated with all the changes? I tried to build TWRP with that exact tree and still seem to have reboots.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Not totally sure dude about your question as this was actually built by utkanos with no device with me and russell testing the builds as they were made till we had it working with no reboots and with fully accessing adb rights when in recovery. i had massive issues when using th TWRP recovery that was posted so it may be TWRP specific that your issues lie. the source code is all available at utkanos github linked in the OP so you can surely tell from that if device tree is correct. if not maybe try to rebuild the trees. i myself have little experience in these matter XD

mehmehmen said:
Not totally sure dude about your question as this was actually built by utkanos with no device with me and russell testing the builds as they were made till we had it working with no reboots and with fully accessing adb rights when in recovery. i had massive issues when using th TWRP recovery that was posted so it may be TWRP specific that your issues lie. the source code is all available at utkanos github linked in the OP so you can surely tell from that if device tree is correct. if not maybe try to rebuild the trees. i myself have little experience in these matter XD
Click to expand...
Click to collapse
Ahh ok Np . Anyway.. good to have a recovery that doesn't reboot itself :thumbup:
Sent from my Nexus 4 using xda premium

A damn of a recovery, great work and thank your for this. Keep up the good work. Thank you again.

Thank u for this ,and thank u for keeping this phone alive , gl on ur cm work guys
Sent from my HTC Desire C using xda app-developers app

no worries guys, amazing to have 200+ views and what 4 users post in the thread lol all thanks is aimed to utkanos for his work making it happen, and mmmcfc for his original version build we worked on. i just tested and provided needed files to utkanos. all thanks is more than appreciated as we spent a whole day pretty much fixing the bloody thing

By the way, we should contact the guys from CWM to get official support like nikihil did.

TheRedHunter said:
By the way, we should contact the guys from CWM to get official support like nikihil did.
Click to expand...
Click to collapse
you need to shoot a mail to koush to get rom manager or cwm support.

Finally a non-rebooting recovery!! Thanks! :good:

your welcome, cant believe there wasnt one for so long, i only got the device around a month ago and found the xda development section lacking in a few areas im not used to seeing and so worked with a cm dev on getting the recovery up to date and stable
any thanks you guys want to click my way are welcomed and would be nice, amazing that over in my general section post to this thread there is a total of maybe 3 thanks per nearly 2,500 visitors to the link
now thats appreciation for ya

Just one question, am i blind, or this one has no clean battery stats?
Is it really needed, and is there a workaround (which file to delete)?

mehmehmen said:
your welcome, cant believe there wasnt one for so long, i only got the device around a month ago and found the xda development section lacking in a few areas im not used to seeing and so worked with a cm dev on getting the recovery up to date and stable
any thanks you guys want to click my way are welcomed and would be nice, amazing that over in my general section post to this thread there is a total of maybe 3 thanks per nearly 2,500 visitors to the link
now thats appreciation for ya
Click to expand...
Click to collapse
You are a great man, and your work is very appreciated. You have my thanks and I'll try to add as many thanks to you as I can.

I've shot you a few thanks as it's a damn fine cause, even if I strongly dislike cwm. I am afraid I am a Twerp through and through.
Ps I will try and get some extra thanks to you Redhunter as you are such a generous guy with your thanks and you always are upbeat and positive. It's good to see, thank you.
All the best rich
Sent from my Nexus 7 using xda premium

Dead link?
The download link to dev hub seems to be dead/broken ... is it just me?!?

AirCombat said:
The download link to dev hub seems to be dead/broken ... is it just me?!?
Click to expand...
Click to collapse
It works for me

calinorg said:
Just one question, am i blind, or this one has no clean battery stats?
Is it really needed, and is there a workaround (which file to delete)?
Click to expand...
Click to collapse
my ? too.i just updated to current version,and browsing around i noticed it is not there??

Can u make this in colours of mujenu touch recovery and create a guide for building recoveries
Sent from my HTC Desire C using xda app-developers app

[DEV] SM T110 Kernel Port [Suspended Temporally]

Here is the Discussion thread for SM T110 Kernel Port, suspended temporally as few files need to be written from scratch.
Will start after my exams
RULES
1. Please use tags.
[ANS] for answer
[OTH] for others
2. Please quote properly
3. Please don't post unnecessarily
These rules are set just to keep the development area clear.
Notice:
Seems like we will have to port only Display driver, camera driver and the Shared memory driver
Developers who wants to help leave a comment here with green text as " HELP "

thanks god blessed you

Good job if you need help i will always try it
But keep in mind i am not that good in kernels

Hello!
How about this program?
We haven't got a Cm Rom yet.
Stock Rom is too boring.

This one makes no sense anymore we have a working T110 port

[OTH] OTG support will be available ?

Waiting your return. I need a custom kernel in my tab. Thanks
Enviado de meu SM-T110 usando Tapatalk

You could include OTG support?
If you could include whether the driver of the usb modem zte whether type of orange?
Would be great if possible as we could have in our tablet 3g usb modem connecting an application using pppwiget

hello .
is there anybody that has baked a working kernel for the T110 so i can configure the governuer mode or is this Modell out of date ?!? im asking coz i have a very hot table. so hot that the touch is not properly working.

restinpeace said:
hello .
is there anybody that has baked a working kernel for the T110 so i can configure the governuer mode or is this Modell out of date ?!? im asking coz i have a very hot table. so hot that the touch is not properly working.
Click to expand...
Click to collapse
Root your tab and install the trickster Mode.app. With this app you can change the Governore to conservative and Scheduler to cfg or noop.
Take a look to this post
http://forum.xda-developers.com/showpost.php?p=50833415&postcount=426

dead
this project is presumed dead.
it is not even tagged "T110". Also the OP did not state from where towards where he intended to port.
R.I.P. , kernel !

[PATCH][TX][DEV]kexec hardboot port - dual-boot possible

!!!!!! NOT FULLY TESTED !!!!!!!
This patch is based on Tasssadar's hardboot patch for mako. And I borrowed some code (hardboot page address usage) from alvinhochun's Xperia M port. The kernel source is 9.2.A.0.295 from Sony. Thanks all of above!
Here is Tassadar's original thread which explains what is kexec hardboot and what it does. Apply this patch to your kernel source and it will be capable of booting another kernel/system without reflashing.
Note: KEXEC_HB_PAGE_ADDR doesn't need to be a certain value. In my tests, 0x88000000 and 0x88A00000 both work. However, I don't know if there are significant side effects... There is no ram_console entry in /proc/iomem... The default address calcuated by original patch is 0x88CE0000,which doesn't work, so I removed the calculation code and hardcoded the address (thanks alvinhochun)
Click to expand...
Click to collapse
Usage can be seen in the sh file attached. Sh file is modded on Tasssadar's. Kexec binary is also taken from his github. Thanks again!
Parameters:
--load-hardboot : load the kernel with hardboot request
--initrd : ramdisk path (For 2012 line, that's the ".cpio.gz" file)
--mem-min : where the kernel should be loaded to (lowest address). This is not certain,either. 0x82000000, 0x85000000 both work. You can try different values. (Is there any limitation to this? Plz tell me...) Normally 0x82000000 will be okay.
--command-line : command line for the guest kernel. Note that the arguments appended by bootloader (semcandroidboot.babe1324 etc)need to be added here manually.
Click to expand...
Click to collapse
Now I have successfully dual-booted stock 4.3(205) and OmniROM 4.4 (homemade):
1. re-partition external sdcard to 4 parts. 1 for regular data storage(mmcblk1p1), 1 for /system (mmcblk1p4), 1 for /data (p2) and 1 for /cache (p3).
2. mount /dev/block/mmcblk1p4 to USB storage in TWRP and "dd if=(9.2.A.1.205 system.ext4 extracted from FTF) of=(USB storage)" on computer. You can use a card reader also.
3. modify the fstab files in stock 205 ramdisk to change the devices for /system, /data and /cache. If you want to add recovery, edit their fstabs also. (PERMISSIONS FOR THESE FILES ARE REALLY IMPORTANT! All .rc and fstab should be 644, root:root. Otherwise it won't boot)
4. repack the ramdisk. Push the zImage and ramdisk to the phone and execute the sh file. The phone reboots and stock 4.3 loads.
5. rebooting the phone will go back to host ROM.
Click to expand...
Click to collapse
But there is one problem: in stock 4.3, Baseband is shown as "Unknown" and the phone gets no signal. On the host ROM, it works properly. It seems to be related to TA reading, but I can't think of anything wrong with this...Logcat shows three TA units were missing. But in host ROM, they are shown as missing too. Full logcat attached in zip. I didn't touch any file other than fstab, fstab.qcom and init.target.rc in 205 ramdisk. Stock 4.1 works like a charm though.
Anyone knows? Thanks in advance~

You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app

alanc.1996 said:
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
New build arrived (2014/05/21). See the separate thread. Following is the old message.
==================
At least it won't reboot ramdomly..but there may be some minor bugs.
Link: http://pan.baidu.com/s/1i3Hq4ip (Password: kpnn)
Internet connection is not very good here so uploading to devhost/mediafire is nearly impossible...
You need to flash the kernel first, then use the recovery to flash the ROM, then flash the kernel again. After system boots, push the modules file to /system/lib/modules
This is based on tital's port. Thanks a lot~
Later I will open a thread to introduce this ROM...

Cool! Will try it out!
Sent from my LT29i using XDA Premium 4 mobile app

Months ago, when I restored an Nandroid backup of 9.2.A.0.295, the same problem appeared. But at that time only mobile service was dead, while WiFi worked. Now mobile service and WiFi are all dead. The screen stops at "Turning on Wi-Fi". However, in dmesg & lsmod, I can see that WLAN driver module has been loaded, with MAC address changed correctly...And in Service Menu(*#*#SERVICE#*#*), Configuration in Service info is dead. Tapping on it will cause the app to stop responding. What is the point?

OK I tried 9.1.B.1.67 firmware. Everything works, including baseband, Wi-Fi and *#*#SERVICE#*#*... However, it's not so attractive as stock 4.3...

Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?

RpRAUC said:
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
Click to expand...
Click to collapse
As long as the kernel matches the ROM (phone operates normally when you install the custom kernel as usual), it should be okay...

Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app

Galcactus said:
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This patch may work on T without any modification, except for the macro name in memory.h

Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app

Galcactus said:
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
It's already perfectly working...

In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app

Galcactus said:
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This is a little bit complicated... but I'll try to make a post about this in a few days.
The kernel commits should be the same for TX and T :
https://github.com/updateing/androi...mmit/3d4950e7d3a0cc1549e82fda6c1d961f83e04f4a
https://github.com/updateing/androi...mmit/8843e01fb1b6752768056589a510a2f8985c0884

[Q&A] [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24

Q&A for [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

You created two scripts?
adrianom said:
I made some scripts to clean (remove stock apps) and optimize the ROM, instead of modifying the main ROM, I created these scripts that must be run in recovery.
For download go to post 2.
...
Click to expand...
Click to collapse
I packed your recoverys and made a zip flashable recovery, but never said I made a recovery. When a new version appears I pointed to your work.
http://www.htcmania.com/showthread.php?t=907314
You have used my script. I'm not a developer as you are, but I don´t think you like that people use your work and say nothing about your effords.
http://www.htcmania.com/showthread.php?t=909354
Regards.

elperroderoke said:
I packed your recoverys and made a zip flashable recovery, but never said I made a recovery. When a new version appears I pointed to your work.
http://www.htcmania.com/showthread.php?t=907314
You have used my script. I'm not a developer as you are, but I don´t think you like that people use your work and say nothing about your effords.
http://www.htcmania.com/showthread.php?t=909354
Regards.
Click to expand...
Click to collapse
Yes, indeed I use some lines of your post, but to be clear, the script that is in the zip is not what is in your post, it has a lote more, and yours don't work on this device, yes a grab some delete lines to simplified the list of apps, but that was it, and I have not mentioned, simply by forgetting it.
I put the reference now:
http://forum.xda-developers.com/showpost.php?p=56221065&postcount=2

scripts
I saw the lines you included and I hope you don't mine I will use some of them to improve my script for X1068.
If you be so kind to solve a question about deleting some files I would thank you.
Is there any way to delete the updates apk in /data/app?
As you know some of them are in /system and in /data once they are updated, but the name changes if is update again.
For instance:
Books.apk is in /system but, com.google.android.apps.books-1.apk is in /data and if is updated again it will be com.google.android.apps.books-2.apk
I tried using
delete("/data/app/com.google.android.apps.books*.apk");
or
delete("/data/app/com.google.android.apps.books-*.apk");
instead of
delete("/data/app/com.google.android.apps.books-1.apk");
delete("/data/app/com.google.android.apps.books-2.apk");
bud didn't work. Is there any way to delete the files that that have similar name.
Thank you for all your work.
Regards.

Any custom rom or rom adapted for xt1069?

Error
Hello man, I'm brazillian, sorry for my english.
I tried to flash a rom from this website: sbf.droid-developers.org/phone.php?device=36 , the last rom, because my Moto G 2 is Duos TV. When I flashed the rom, my camera stopped, just the frontal camera function, my flashlight too stopped... I really like to know, if you can help me with it... How you know, the cam of Moto G 2 has a button to change between Frontal and main camera, but this button doesn't appears, and the options in the configuration is blocked(some of them).
Please help me, I paid R$799,00 (money of Brazil), thanks a lot for everything!

xdaVTU said:
Hello man, I'm brazillian, sorry for my english.
I tried to flash a rom from this website: sbf.droid-developers.org/phone.php?device=36 , the last rom, because my Moto G 2 is Duos TV. When I flashed the rom, my camera stopped, just the frontal camera function, my flashlight too stopped... I really like to know, if you can help me with it... How you know, the cam of Moto G 2 has a button to change between Frontal and main camera, but this button doesn't appears, and the options in the configuration is blocked(some of them).
Please help me, I paid R$799,00 (money of Brazil), thanks a lot for everything!
Click to expand...
Click to collapse
You are using the Motorola app or the Google camera app? The button to change are in different places.
About the firmware, you have to flash the correct one? Has to be the with dstv in the name. If you flash the wrong one try flash the correct.

help
adrianom said:
You are using the Motorola app or the Google camera app? The button to change are in different places.
About the firmware, you have to flash the correct one? Has to be the with dstv in the name. If you flash the wrong one try flash the correct.
Click to expand...
Click to collapse
Adrianom, thanks for answer my question, but yes, I made the correct download, in the name was wrote DSTV, and about the app.. I don't know what the app that I'm using, is the factory app of the device, probability of Motorola. And all the apps that has the function of camera, neither of them work with me... Thanks for everything, and.... What do you think about my english? Is good or not?

Restarts before finalizing the installation
Friend, did the procedure to install this ROM , already have the unlocked Bootloader and Flash Recovery CWM , however when are installing the phone restarts and crashes in toot screen. Has suggested to solve this?

Using scripts can usually upgrade?
If I install the Rom Stock and use the scripts before the OTA update, I can upgrade later without the applications of Motorola?

Perfect installation
Did all the installation process and everything was perfect, just a detail that installed only by CWM recovey at TWRP was not.

Root is stable? No bootloops? I turn back to kk from 5.0 because link2sd not working in 5.0 rooted and unstable root.

Not W
Its not working on me, i'm getting a black screen at boot time.

Update bootloader
If I flash this rom my bootloader will go to version 46.87?