[Discussion] Latest Kernels - Touch Pro2, Tilt 2 Android Development

Feb 22nd, 2011 Announcement: Now that Glemsom's auto-build system is back up, I will no longer be posting kernels to this thread. Kernel 1260 is the last that will be posted here. I encourage everyone to use the auto-build service from this point forward. Feel free to continue using this thread to discuss new kernels as they're released.
Feb 14th Update: 2nd kernel today fixes bugs introduced in 1st kernel.
Feb 10th Update: Glemsom's autobuild service appears to be back up, and he's finally gotten around to building the Jan 13th kernel (1253), which he's named 20110210_213850.
Original Dec. 12th, 2010 Announcement: I've received a request to post the latest kernel since the auto-build service was down between Dec. 5th or so and Feb. 10th. Thus I've linked the latest kernel and its modules file below for those who aren't into compiling their own kernels. This kernel was built from the source code available at the linux-msm repo on Gitorious that pretty much everyone (with a rhodium, topaz, raphael, diamond, blackstone & kovsky at least) including Glemsom's auto-build site has been using.
Additional Packages: As of Dec. 26th, compat-wireless & compcache 0.5.4 are fully integrated into these builds, just as they were in Glemsom's builds. 802.11e QoS support has also been enabled in compat-wireless. The modules file for kernel 1245 has been rebuilt to include the modules from these packages. Going forward, all future builds will include these as well. I am considering the possibility of creating a test kernel that includes the "swap free notify" patch and I'm interested in hearing back from anyone who has already looked into this possibility.
Latest Kernel
Glemsom's auto-build site
Older Kernels
Instructions - Note: These instructions are for the kernels I've posted here, not for Glemsom's kernels.
1) Download both the zImage and modules files below if you use wifi, otherwise you only need the zImage.
2) Rename the zImage file to simply: zImage
3) Drop that along with the modules file into your android boot directory (usually /sdcard/andboot).
4) Restart.
Commit# 1260 (includes 1259)
Commit Date: Mon Feb 21 18:19:45 2011
Commit ID: g11945d1
Pushed by: bzo (1259 on behalf of jbruneaux)
Commit Messages:
1260 - Merge branch 'htc-msm-2.6.27' of git://gitorious.org/linux-on-qualcomm-s-msm/linux-msm into htc-msm-2.6.27
1259 - adsp : fix the adsp drivers for camera (missing IOCTL, offsets, modules parameters, IDs fixup for QDSP messages).
F22's Notes: Some, but not all, of the code needed to make the camera work has been committed. This kernel is the same as Glemsom's 20110221_192424.
Kernel: zImage-2.6.27.46-01260-g11945d1
Modules: modules-2.6.27.46-01260-g11945d1.tar.gz
Commit# 1258 (includes 1256 & 1257)
Commit Date: Mon Feb 14 18:22:45 2011
Commit ID: g77a00c3
Pushed by: mweirauch (on behalf of bzo for 1256 & WisTilt2 for 1258)
Commit Messages:
1258 - Rhod Panel collapse and panel detect
1257 - Merge branch 'htc-msm-2.6.27' of gitorious.org:linux-on-qualcomm-s-msm/linux-msm into htc-msm-2.6.27
1256 - merge jbruneaux's amss clock implementation
F22's Notes: Bug Fix for 1255. Adds in missing definition and macro. Also known to fix the screen calibration bug that appeared in 1233 for rhodium only. This kernel is the same as Glemsom's 20110214_200559.
Kernel: zImage-2.6.27.46-01258-gf9e4956
Modules: modules-2.6.27.46-01258-gf9e4956.tar.gz
Commit# 1255 (includes 1254)
Commit Date: Mon Feb 14 06:32:17 2011
Commit ID: g77a00c3
Pushed by: ACL (on behalf of WisTilt2)
Commit Messages:
1255 - Rest of keyboard caps/fn leds
1254 - Rhod Caps/FN keyboard leds
F22's Notes: This kernel fails to compile. The committed code required a constant definition and a macro that weren't included.
Kernel: -
Modules: -
Commit# 1253 (includes 1251 & 1252)
Commit Date: Thu Jan 13 09:12:17 2011
Commit ID: gd53ddf6
Pushed by: ACL
Commit Messages:
1253 - Merge branch 'htc-msm-2.6.27' of [email protected]:linux-on-qualcomm-s-msm/linux-msm into htc-msm-2.6.27
1252 - Enable headphone amp on Rhod for 11pin headset. Still need 3.5mm jack to be enabled. Gpio values should be moved to rhod.h file.
1251 - Correct missing braces and add fix printk.
F22's Notes: snd.force_headset in startup.txt no longer necessary for rhodium due to 1251. Commit #1252 enables/disables extUSB headset jacks properly. 3.5mm jack on CMDA handsets isn't yet addressed. This kernel is the same as Glemsom's 20110210_213850.
Kernel: zImage-2.6.27.46-01253-gd53ddf6
Modules: modules-2.6.27.46-01253-gd53ddf6.tar.gz
Commit# 1250 (includes 1247-1249)
Commit Date: Fri Jan 7 21:02:39 2011
Commit ID: 8f8207c
Pushed by: mweirauch
Commit Messages:
1250 - Merge branch 'topa-panel' into htc-msm-2.6.27
1249 - topa: panel: drop the waits on init
1248 - topa: panel: some more register documentation + drop redundant one
1247 - topa: panel: convert init and deinit sequences to obsolete reg-offset shifting
Kernel: zImage-2.6.27.46-01250-g8f8207c
Modules: modules-2.6.27.46-01250-g8f8207c.tar.gz
Commit# 1246
Commit Date: Wed Jan 7 11:16:28 2011
Commit ID: 5ce0119
Pushed by: ACL (on behalf of WisTilt2)
Commit Messages:
1246 - Keyboard Backlight
F22's Notes: Keyboard Backlights for Rhodium from WisTilt2's test kernel.
Kernel: zImage-2.6.27.46-01246-g5ce0119
Modules: modules-2.6.27.46-01246-g5ce0119.tar.gz
Commit# 1245 (includes 1243 & 1244)
Commit Date: Thu Dec 23 01:58:42 2010
Commit ID: d9d77f2
Pushed by: ACL
Commit Messages:
1245 - Missed a define.
1244 - Merge branch 'htc-msm-2.6.27' of [email protected]:linux-on-qualcomm-s-msm/linux-msm into htc-msm-2.6.27
1243 - <Alex> Update clock code
F22's Notes: This kernel is thought to have introduced an issue that causes issues with some SD cards. See this post for more info.
Kernel: zImage-2.6.27.46-01245-d9d77f2
Modules: modules-2.6.27.46-01245-d9d77f2.tar.gz (Updated Dec. 26th - Now Includes Compat-Wireless & CompCache)
Commit# 1242 (includes 1241)
Commit Date: Tue Dec 22 22:56:16 2010
Commit ID: 51a9760
Pushed by: mweirauch (on behalf of bzo for 1241)
Commit Messages:
1242 - wakelock: fix build w/o CONFIG_WAKELOCK_STAT
1241 - fix for sleep mode of 1 when overclocking PLL2
F22's Notes: 1241 fixes bug that prevents handset from waking up when overclocking if pm.sleep_mode=1.
Kernel: zImage-2.6.27.46-01242-51a9760
Modules: modules-2.6.27.46-01242-51a9760.tar.gz
Commit# 1240
Commit Date: Tue Dec 21 22:43:26 2010
Commit ID: 137e247
Pushed by: mweirauch
Commit Messages:
1240 - topa: panel: move EXIT_SLEEP_MODE and document some registers
Kernel: zImage-2.6.27.46-01240-137e247
Modules: modules-2.6.27.46-01240-137e247.tar.gz
Commit# 1239
Commit Date: Tue Dec 21 06:32:11 2010
Commit ID: acf4596
Pushed by: ACL (on behalf of WisTilt2)
Commit Messages:
1239 - Speakerphone syntax correction
F22's Notes: Fixes hiss introduced in 1238.
Kernel: zImage-2.6.27.46-01238-gacf4596
Modules: modules-2.6.27.46-01238-gacf4596.tar.gz
Commit# 1238
Commit Date: Sat Dec 18 20:44:32 2010
Commit ID: 43f0a96
Pushed by: ACL (on behalf of WisTilt2)
Commit Messages:
1238 - Speakerphone mic fix.
F22's Notes: Speakerphone microphone now works in call.
Kernel: zImage-2.6.27.46-01239-g43f0a96
Modules: modules-2.6.27.46-01239-g43f0a96.tar.gz (Updated Dec. 19th: wlan.ko update)
Commit# 1237 (includes 1236)
Commit Date: Fri Dec 17 22:33:36 2010
Commit ID: 8c0ce38
Pushed by: mweirauch
Commit Messages:
1237 - mddi: novatek: drop vsync setup (by Alex) and update rhod+topa panels
1236 - mddi: simple: bring in line with [android,ca]-msm-2.6.35
Kernel: zImage-2.6.27.46-01237-g8c0ce38
Modules: modules-2.6.27.46-01237-g8c0ce38.tar.gz (Updated Dec. 19th: wlan.ko update)
Commit# 1235 (includes 1234)
Commit Date: Fri Dec 17 20:54:36 2010
Commit ID: 66a01da
Pushed by: mweirauch
Commit Messages:
1235 - mddi: epson: vsync setup to board files (taken from Alex)
1234 - raph+diam: fix toshiba mddi client name and setup vsync gpio (taken from Alex)
F22's Notes: 1234 fixes the Diam/Raph breakage caused by 1233.
Kernel: zImage-2.6.27.46-01235-g66a01da
Modules: modules-2.6.27.46-01235-g66a01da.tar.gz
Commit# 1233
Commit Date: Fri Dec 17 13:28:27 2010
Commit ID: 5b44660
Pushed by: ACL
Commit Message:
1233 - Update Framebuffer to .35
F22's Notes: Known to break Diam/Raph. Fixed in 1234. This kernel also introduced a second bug affecting all xdandroid handsets, causing them to appear to hang during boot if the ts-calibration file isn't already present. See the top of this page for more info.
Kernel: zImage-2.6.27.46-01233-g5b44660
Modules: modules-2.6.27.46-01233-g5b44660.tar.gz
Commit# 1232
Commit Date: Sat Dec 11 12:59:03 2010
Commit ID: b7033df
Pushed by: mweirauch
Commit Message:
1232 - mddi: novatek: improve topa+rhod 2D performance
Kernel: zImage-2.6.27.46-01232-gb7033df
Modules: modules-2.6.27.46-01232-gb7033df.tar.gz (Updates - Dec 14th: File Size Reduced to 806 kB - Dec 12th: TI Wifi Support for Non-Rhodiums Added.)
Pre-Dec. 11th 2010 Kernels
Glemsom's auto-build site

F22 said:
I've received a request to post the latest kernel since the auto-build service is currently down. Thus I've linked the latest kernel and its modules file below for those who aren't into compiling their own kernels. This kernel was built from the source code available at the linux-msm repo on Gitorious that pretty much everyone (with a rhodium, topaz, raphael or diamond at least) including Glemsom's auto-build site has been using.
Instructions
1) Download both the zImage and modules files below if you use wifi, otherwise you only need the zImage.
2) Rename the zImage file to simply: zImage
3) Drop that along with the modules file into your android boot directory (usually /sdcard/andboot).
4) Restart.
Latest Kernel
Commit Date: Sat Dec 11 12:59:03 2010
Commit# 1232
Commit ID: b7033df
Commit Message: mddi: novatek: improve topa+rhod 2D performance
Kernel: zImage-2.6.27.46-01232-gb7033df
Modules: modules-2.6.27.46-01232-gb7033df.tar.gz
Click to expand...
Click to collapse
thank you very much. you awesome. thanks

Thanks for the compile F22

Wifi can't enabled with this kernel on Topaz, says "Error"
It's only for Rhodium?

Hi, what do i use to unpack the .tar file. i tryed winrar but that does not keep de dir structure intackt. Im guessing that there is suposed to be a dir strukture, but i might be wrong. If not where should i put the files from the .tar file?

DmK75 said:
Wifi can't enabled with this kernel on Topaz, says "Error"
It's only for Rhodium?
Click to expand...
Click to collapse
it is normal.this current kernel don't have wlan.ko build into it.Missing wlan module to start wifi

Tar Files
flippy said:
Hi, what do i use to unpack the .tar file. i tryed winrar but that does not keep de dir structure intackt. Im guessing that there is suposed to be a dir strukture, but i might be wrong. If not where should i put the files from the .tar file?
Click to expand...
Click to collapse
There's no need to unpack anything. When you boot android, the init script will automatically untar the contents of modules-2.6.27.46-01232-gb7033df.tar.gz into /data/modules for you. Just leave it as is in your android boot directory (usually /sdcard/andboot).

wlan.ko
xUmaRix said:
DmK75 said:
Wifi can't enabled with this kernel on Topaz, says "Error"
It's only for Rhodium?
Click to expand...
Click to collapse
it is normal.this current kernel don't have wlan.ko build into it.Missing wlan module to start wifi
Click to expand...
Click to collapse
Hmm...as xUmaRix has noted, wlan.ko isn't part of a stock kernel build. It was apparently added in as an extra. I can look into adding it in too for the non-rhodium users. Check back later today.

Thanks so much for posting this! The last few kernels have not treated my Rhod400 so well...I hope this one does the trick!

Hi, just installed the new kernel, everything seems to work fine like before.
I can say the performance in 2d has increased.!!
thx to devs im looking forward..

Additional Modules Now Included for Topaz & Rhobuntu WiFi
F22 said:
Hmm...as xUmaRix has noted, wlan.ko isn't part of a stock kernel build. It was apparently added in as an extra. I can look into adding it in too for the non-rhodium users. Check back later today.
Click to expand...
Click to collapse
I've repackaged the modules file to include an extra 6 drivers that were present in Glemsom's modules file but weren't built in the stock linux-msm kernel compile. They include:
ramzswap.ko
rfkill_backport.ko
wl1251.ko
wl1251_sdio.ko
wlan.ko
xvmalloc.ko
Wifi for topaz should now work. I believe wifi on rhobuntu should work as well. I've updated the link in the 1st post of this thread so that it points to the new modules file.

For me this new kernel is unstable - I have Rhod400 but using in europe (gsm) , phone freezes few minutes after boot, sometimes when I use Opera. Few times there was no service error after boot (waited few minutes - nothing changed).

Just installed the first posted kernel. Working good here on my Rhod400. Boosted my FPS2D to 29 fps. Got 18.7 fps on Neocore. Wifi works fine too.
11.26 driver, 11.29 gralloc, 12.02 build.prop, no overclock.

Stability Issues
Raul^ said:
For me this new kernel is unstable - I have Rhod400 but using in europe (gsm) , phone freezes few minutes after boot, sometimes when I use Opera. Few times there was no service error after boot (waited few minutes - nothing changed).
Click to expand...
Click to collapse
XDANDROID itself isn't entirely stable. On occasion, and especially after you've changed something significant like the kernel, the rootfs, or even just your startup.txt, android's system_server process may go berserk and cause a host of issues including lack of service, timeout messages, sluggishness, etc... A reboot should fix it. If it doesn't, and you're overclocking, lower your overclock by 1 notch (19.2 MHz) and see if that helps.
I had a similar issue too the first time I booted the new kernel, and only the first time. After that it was fine. I've also experienced the same issue while making other tweaks to my handset that had nothing to do with the kernel. So it's a known problem that while extremely annoying, is probably unrelated to the new kernel aside from the fact that system_server can get cranky at times right after you change something.

F22 said:
I've received a request to post the latest kernel since the auto-build service is currently down. Thus I've linked the latest kernel and its modules file below for those who aren't into compiling their own kernels. This kernel was built from the source code available at the linux-msm repo on Gitorious that pretty much everyone (with a rhodium, topaz, raphael, diamond, blackstone & kovsky at least) including Glemsom's auto-build site has been using.
Click to expand...
Click to collapse
Thanks very much! us newbies appreciate it
Everything seems to be working (including wifi). I actually moved the old zimage and modules file to a temp directory that android doesn't even see, so I know I am running the new software, but when I look at the build information, it says:
Android version: 2.2
Kernel version: 2.6.27.46-01323-gb7033df
Build number: full_msm-eng 2.2 MASTER.eng
mjg.20100813.141358 test-keys
I guess I was expecting version 2.3...
Also partially working is the USB connection: When I connect the phone to my computer, I am notified (this is a first!)

Working well so far on my Sprint TP2...although it wasn't in the release notes I was hoping for the "voice call speakerphone mic" fix but mic still does not work...I think I heard that was fixed but just not commited yet?

there is a workaround - start a speakerphone conversation (i.e. voicemail) before launching haret

No Speakerphone Mic Fix
pdawg17 said:
Working well so far on my Sprint TP2...although it wasn't in the release notes I was hoping for the "voice call speakerphone mic" fix but mic still does not work...I think I heard that was fixed but just not commited yet?
Click to expand...
Click to collapse
I know WisTilt2 has speakerphone mic fixed because I helped him test it. I have no idea when it will get committed however. Unfortunately we haven't seen him online since Thanksgiving.

F22 said:
I know WisTilt2 has speakerphone mic fixed because I helped him test it. I have no idea when it will get committed however. Unfortunately we haven't seen him online since Thanksgiving.
Click to expand...
Click to collapse
Hopefully he'll be back at some point...I know about the workaround but sometimes I forget so it'd be nice to not have to think about it

Also partially working is the USB connection: When I connect the phone to my computer, I am notified (this is a first!)
Click to expand...
Click to collapse
Is this supposed to work now?
When I plug the phone into my windows 7 box, I now get an "H" drive. When I click on it, it asks me to insert a disk.
When I click the "Turn on USB storage" button in Android, nothing seems to happen (the spinner icon just goes around and around.)

Related

[Nov. 8, 2012] (Kernel 2.6.32) tytung_gb_r16 (for Froyo and Gingerbread)

My kernels are based on Hastarin's r8.6 SD kernel sources which are based on Markinus' EVO kernel sources.
I have modified them to be compatible with NAND ROMs and added a lot of new useful features since January 2011.
I mainly developed and tested them on my NexusHD2-Gingerbread and NexusHD2-Froyo ROMs.
If any feature doesn't work for other ROMs, I won't fix it.
My git repository: https://github.com/tytung/android_kernel_htcleo-2.6.32-ics/tree/gingerbread
The source code is released under the GNU General Public License version 2 (GPLv2).
So you must release your modified source code (it's better to use git for sharing purpose) if you would like to release a modified kernel based on my source code.
Primary features:
Default CPU governor: Interactive
Default CPU frequency: 245-998 MHz
Support underclocking to 128MHz (via SetCPU or shell script) (Credits: tytung)
Support overclocking to 1190 MHz. (via SetCPU or shell script) (Credits: hastarin)
Support undervolt/overvolting via sysfs interface. (800-1350mV) (Credits: snq-)
Default I/O Scheduling: CFQ
Patched with G-Sensor freeze fix (Credits: mdebeljuh and jdivic)
Patched with Bluetooth 60mA battery drain fix (i.e. support Low-power mode Bluetooth) (Credits: trilu and charansingh)
Patched with wakeup lag fix for AUO panels (Credits: mdebeljuh and jdivic)
Patched with "Low Speakerphone Mic Gain & High Background Noise" (Credits: mdebeljuh and jdivic) (Thanks to memin1857 for collecting the related info.)
Patched with "No Sound/ libaudio.so issues" (Thanks to drizztje who found the cause, ph03n!x who collected the related info and tested them, and all other testers.)
Full cLK bootloader support (Credits: cedesmith)
Two-way call recording (Credits: avs333 and snq-)
T-Mobile Wi-Fi Calling (Credits: tytung)
Wi-Fi IEEE 802.1x/EAP authentication (Credits: tytung)
Native USB Tethering (Credits: tytung)
Native Wi-Fi Tethering (Credits: tytung)
Official HTC extended battery support (HTC EB 2300mAh) (Credits: arne)
File systems support: Yaffs, Ext2/3/4, CIFS, NILFS, ReiserFS, BTRFS. (NLS_UTF8 is compiled into the kernel) (Credits: tytung)
ALSA sound driver as kernel modules (alsa-pcm-htc-leo.ko and alsa-mix-htc-leo.ko) (Credits: Cotulla)
Real WiFi and Bluetooth MAC addresses. (Credits: Franck78, Rick_1995 and Marc1706)
Credits: Markinus, Cotulla, TYTung, Hastarin, NetRipper, Dcordes, Letama, Rajko, Dan1j3l, Cedesmith, Arne, Trilu, Charansingh, Mdebeljuh, Jdivic, Avs333, Snq-, Savan, Drizztje, Marc1706, Franck78, Rick_1995, other devs, and testers.
Click to expand...
Click to collapse
Downloads:
Mod edit: Links removed
Issues:
WiFi issue:
If you flash my kernel in Gingerbread 2.3.3 and the earlier versions, you will have DHCP issue when using WiFi. (i.e. Cannot connect to a wireless router and get an IP successfully.)
This issue is related to Gingerbread's initrd.gz, not the kernel (i.e. zImage).
Gingerbread 2.3.4+ must use the following setting in /init.htcleo.rc or /init.leo.rc or ... depending on your ROMs.
Code:
service [B][COLOR="Red"]dhcpcd_eth0[/COLOR][/B] /system/bin/dhcpcd -ABKL
Gingerbread 2.3.3 must use the following setting.
Code:
service [B][COLOR="red"]dhcpcd[/COLOR][/B] /system/bin/dhcpcd -ABKL
Sound issue:
If you feel that the maximum sound volume is still not high enough so that you cannot hear the sound (e.g. call, ringtone, alarm, etc.) clearly or your caller complain your in-call voice is a little low.
The candidate solutions are as follows:
Go to a quiet place.
Go to see a doctor.
Modify the mic gain value by editing /system/etc/init.d/10mic_level (reboot to take effect or execute the below command manually).
Content of 10mic_level: (You may need to enlarge the values below.)
Code:
#!/system/bin/sh
echo '0 400' > /proc/mic_level
echo '1 600' > /proc/mic_level
Install HD2 Mic Control (GUI for 10mic_level) or Volume+.
Click to expand...
Click to collapse
Installation for NexusHD2 ROMs:
Place your downloaded file in the SD card.
Enter CWM (ClockworkMod) Recovery
MAGLDR 1.13: Hold "Power" button during boot to enter MAGLDR, and then select "AD Recovery" or "Boot AD SD" (if ever copied CWM's initrd.gz and zImage to SD) to enter CMW.
cLK 1.4.0.1: Hold "Home" button during boot to enter CMW.
Choose install zip from sdcard and navigate to your downloaded file to finish the installation.
All done.
Click to expand...
Click to collapse
Installation for other ROMs:
For MAGLDR users, please delete initrd.gz from kernel_tytung_rX_update.zip before flashing it.
For cLK users, it's better to use initrd.gz from your ROMs for best compatibility. The steps are as follows.
Download kernel_tytung_rX_update.zip to get zImage and system folder.
Download and uncompress cLK_kernel_installer.zip to a temp folder, e.g. cLK_kernel_installer, and put zImage, system folder, and your ROM's initrd.gz to cLK_kernel_installer folder.
You can unpack boot.img of your cLK ROM to get initrd.gz.
Or download and unzip your MAGLDR ROM to get initrd.gz directly.
Plug your phone to your PC via USB cable.
Run cLK_kernel_installer.bat to install new kernel and the related stuff.
Content of cLK_kernel_installer.bat:
Code:
adb remount
adb shell rm /system/lib/modules/*
adb push system /system/
adb shell chown 0:2000 /system/bin/wpa_supplicant
adb shell chmod 755 /system/bin/wpa_supplicant
adb shell chown 0:2000 /system/etc/init.d/*
adb shell chmod 750 /system/etc/init.d/*
adb shell sync
adb reboot bootloader
fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz
echo Press any key to reboot.
echo Press any key to reboot.
pause
fastboot reboot
Click to expand...
Click to collapse
Changelog
Changelog:
Nov. 8, 2012: tytung_r16
Fixed broken USB Tethering in r15.
Nov. 8, 2012: tytung_r15
Merged r14 and r14_callrec.
Added InteractiveX governor.
Added Smartass2 governor.
Added Real WiFi and Bluetooth MAC addresses.
Added Fast charging.
And more.
Nov. 10, 2011: tytung_r14 (For new/desire camera libs and HTC extended battery.)
Fixed the color banding issue. (Credit to marc1706)
Included a branch r14_callrec too.
Nov. 5, 2011: tytung_r13 (For new/desire camera libs and HTC extended battery.)
Added HTC auto white balance calibration driver.
Added ALSA sound driver and compiled as kernel modules (alsa-pcm-htc-leo.ko and alsa-mix-htc-leo.ko). (Credits to Cotulla)
Included a branch r13_callrec which means the Two-way call recording is enabled. (It may cause the "No sound bug". Use at your own risk.)
Oct. 1, 2011: tytung_r12.4 package v3 (For new/desire camera libs and HTC extended battery.)
Based on r12
Fixed "No sound bug" (Disabled "call recording" in kernel config) (Thanks to drizztje who found the cause, ph03n!x who collected the related info and tested them, and all other testers.)
Enabled 128MHz CPU frequency support. (Default is 245~998 MHz)
Included Gpc's libaudio.so v2.8e in the kernel package again for remembering adjusted in-call volume and supporting mic gain fix.
Removed /system/etc/init.d/10mic_level when flashing.
Replaced default.acdb with letama's htcleo.acdb (113,910 bytes) (CRC: C3CDDB54) in the kernel package. (Thanks to kcfong2 who tested this new approach.)
Oct. 1, 2011: tytung_r12.4 package v1 (For new/desire camera libs and HTC extended battery.)
Based on r12
Fixed "No sound bug" (Disabled "call recording" in kernel config) (Thanks to drizztje who found the cause, ph03n!x who collected the related info and tested them, and all other testers.)
Enabled 128MHz CPU frequency support. (Default is 245~998 MHz)
Included Gpc's libaudio.so v2.8e in the kernel package again for remembering adjusted in-call volume and supporting mic gain fix.
Included Desire Gingerbread's stock default.acdb (129,346 bytes) (CRC: B0DCA53A) in the kernel package for fixing echo voice.
Sep. 30, 2011: tytung_r12.3 (For new/desire camera libs and HTC extended battery.)
Based on r12
Fixed "No sound bug" (Disabled "call recording" in kernel config) (Thanks to drizztje who found the fix, and ph03n!x who tested and collected the related info.)
Included Drizztje's libaudio.so v5 in the kernel package.
Sep. 12, 2011: tytung_r12 (For new/desire camera libs and HTC extended battery.) and tytung_r12_oldcam (For old/N1 camera libs and HTC extended battery.)
Added proc file interface /proc/mic_level to fix low speakerphone mic gain (Credits to mdebeljuh and jdivic)
Included /system/etc/init.d/10mic_level (Set to '0 400' for Handset and '1 600' for Speaker)
Removed support for specific htcleo.acdb file to improve the booting speed when htcleo.acdb is not present.
Loaded the real WiFi MAC address from SPL if running SD build on WinMo 6.5. (Not for MAGLDR and cLK bootloaders) (Credits: savan and tytung)
Added HTC official kineto_gan.ko kernel module for T-Mobile Wi-Fi Calling.
Included Gpc's libaudio.so v2.8e in the kernel package.
Included N1 Gingerbread's stock default.acdb (122,442 bytes) (CRC: 2A51EA54) in the kernel package. (It may cause echo voice.)
Aug. 22, 2011: tytung_r11 (For new/desire camera libs and HTC extended battery.) and tytung_r11_oldcam (For old/N1 camera libs and HTC extended battery.)
Used the same initrd.gz for MAGLDR and cLK (for Gingerbread 2.3.4 and above versions, otherwise no Wi-Fi.)
(removed libhtc_ril_wrapper.so parameters from init.rc and added the required info to /system/default.prop if using cLK ROM)
Added RNDIS (Remote Network Driver Interface Specification) for supporting native USB Tethering.
Added wakeup lag fix for AUO panels. (Credits to mdebeljuh and jdivic)
Cleaned up during camera opening failure.
Changed unique WiFi address to IEEE Standards 00:23:76:XX:XX:XX for HTC. -- http://standards.ieee.org/cgi-bin/ouisearch?00-23-76
(Caution: WiFi address has changed. Remember to update the white list of your wireless router if you ever enabled filtering feature.)
May 04, 2011: tytung_r10_oldcam (For old/N1 camera libs and HTC extended battery.)
Included my modified initrd.gz (removed libhtc_ril_wrapper.so in init.rc)
Added kineto_gan.ko module to support T-Mobile Wi-Fi Calling.
Fixed RIL on NAND boot in kernel, so we don't need ril wrapper library (libhtc_ril_wrapper.so) for MAGLDR anymore. (Only cLK needs ril wrapper library to support PPP.)
May 03, 2011: tytung_r10 (For new/desire camera libs and HTC extended battery.)
Included my modified initrd.gz (removed libhtc_ril_wrapper.so in init.rc and modified init.htcleo.rc to support Wi-Fi change in Gingerbread 2.3.4) (Don't use it in Gingerbread 2.3.3 and the earlier versions, otherwise no Wi-Fi.)
Added kineto_gan.ko module to support T-Mobile Wi-Fi Calling.
Fixed RIL on NAND boot in kernel, so we don't need ril wrapper library (libhtc_ril_wrapper.so) for MAGLDR anymore. (Only cLK needs ril wrapper library to support PPP.)
Apr. 12, 2011: tytung_r9 (For new/desire camera libs and HTC extended battery.) and tytung_r9_oldcam (For old/N1 camera libs and HTC extended battery.)
Supported two-way call recording. (Thanks to avs333, snq-, and skvalex.)
Supported unique Bluetooth MAC address.
Supported Bluetooth PAN (Personal Area Network) using android-wifi-tether. (Tested on v2.0.7)
Included my modified initrd.gz (modified init.htcleo.rc to support unique Bluetooth MAC address)
Added audio boost in another source file. (It seems to make the BT call quality clear than before.)
Mar. 27, 2011: tytung_r8.3 (For new/desire camera libs and HTC extended battery.) and tytung_r8.3_oldcam (For old/N1 camera libs and HTC extended battery.)
Updated Bluetooth stack.
Reverted all patches from the latest kernel 2.6.37 in r8 to make sure the video recording is stable.
Mar. 25, 2011: tytung_r8.2 (For new/desire camera libs and HTC extended battery.) and tytung_r8.2_oldcam (For old/N1 camera libs and HTC extended battery.)
Fixed Bluetooth 60mA battery drain (i.e. support Low Power Mode) (Big thanks to Trilu and Charansingh)
Included my modified initrd.gz (add --enable_lpm and mkdir /cache/recovery) for NexusHD2-Gingerbread (tytung_r8.2) and NexusHD2-Froyo (tytung_r8.2_oldcam).
Mar. 24, 2011: tytung_r8.1 (For new/desire camera libs and HTC extended battery.) and tytung_r8.1_oldcam (For old/N1 camera libs and HTC extended battery.)
Enabled universal TUN/TAP device driver support in the kernel to support opening a VPN connection.
Reverted some patches from the latest kernel 2.6.37 to fix video recording issue in r8. (See commit log for details.)
Mar. 23, 2011: tytung_r8 (For new/desire camera libs and HTC extended battery.) and tytung_r8_oldcam (For old/N1 camera libs and HTC extended battery.)
Updated to wpa_supplicant v0.6.10ah which supports Ad Hoc WiFi.
Added kernel reboot reason for cLK. (i.e. reboot into recovery, patch file from Cedesmith)
Added some patches from the latest kernel 2.6.37. (See commit log for details.)
Enabled BTRFS file system support from the config file.
Mar. 12, 2011: tytung_r7 (For new/desire camera libs and HTC extended battery.) and tytung_r7_oldcam (For old/N1 camera libs and HTC extended battery.)
Added all the new commits from the "official" EVO kernel git repository. http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc
Added cLK bootloader support. (Patch files from Cedesmith)
Added the official HTC extended battery support. (Integrated source code from Arne's Extended Kernel. All credit goes to him.)
Compiled RMNET (for 3G network) as a module. (Loaded it via /system/etc/init.rd/01_modules when booting)
Enabled ReiserFS file system support from the config file.
Improved the WiFi driver.
Fixed WiFi "When screen turns off" battery drain issue.
Feb. 23, 2011: tytung_r6 (For new/desire camera libs and HTC standard battery.) and tytung_r6_oldcam (For old/N1 camera libs, HTC standard battery and partly support HTC extended battery.)
Updated the WiFi driviers to AOSP version for supporting IEEE 802.1x/EAP authentication and fixing native WiFi Tethering.
Thanks to Charansingh's raiderx_htcleo AOSP kernel source.
Included Gingerbread's wpa_supplicant to match the latest AOSP WiFi drivier. (The oldcam kernel also works with NexusHD2-Froyo.)
Feb. 18, 2011: tytung_r5 (For new/desire camera libs and HTC standard battery.) and tytung_r5_oldcam (For old/N1 camera libs, HTC standard battery and partly support HTC extended battery.)
updated the LED related driviers to fix the LED Notification issue.
Feb. 16, 2011: tytung_r4 (For new/desire camera libs and HTC standard battery.)
added all the new commits from the "official" EVO kernel git repository. http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc
changed default governor from smartass to interactive
added NILFS file system support requested by someone
Feb. 15, 2011: tytung_r4_oldcam (For old/N1 camera libs, HTC standard battery and partly support HTC extended battery.)
reverted the robot voice and frozen Phone app fix in r3 to solve the call quality issue (static sound).
You may need to enable Audible touch tones in Sound settings to avoid the frozen Phone app when dialing.
Feb. 13, 2011: tytung_r3_oldcam (For old/N1 camera libs, HTC standard battery and partly support HTC extended battery.)
added all the new commits from the "official" EVO kernel git repository. http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc
fixed Robot voice and frozen Phone app when dialing. (Feb.15 update: it seems to cause the call quality issue (static sound). Please report detail if you use this kernel. Thanks.)
changed default governor from smartass to interactive
added NILFS file system support requested by someone
Jan. 29, 2011: tytung_r2_eb (For new/desire camera libs and HTC extended battery.) (No HTC extended battery to test, please confirm its working or not.) (Not working)
based on hastarin's r8.6 eb branch
added normal RMNET driver
added unique Wi-Fi MAC address
supported CIFS UTF-8, Yaffs, Ext3, and Ext4 file system using modified build config.
added some commits from the "official" git (Please see my git repository for detail.)
added audio boost (With this you'll have large range of volume but may have worse sound quality.)
Jan. 29, 2011: tytung_r2 (For new/desire camera libs and HTC standard battery.)
based on hastarin's r8.6 master
added normal RMNET driver
added unique Wi-Fi MAC address
supported CIFS UTF-8, Yaffs, Ext3, and Ext4 file system using modified build config.
added some commits from the "official" git (Please see my git repository for detail.)
added audio boost (With this you'll have large range of volume but may have worse sound quality.)
Jan. 19, 2011: tytung_r2_eb_oldcam (For old/N1 camera libs and HTC extended battery.) (No HTC extended battery to test, please confirm its working or not.) (Not working)
based on hastarin's r8.6 eb_oldcam branch
added normal RMNET driver
added unique Wi-Fi MAC address
supported CIFS UTF-8, Yaffs, Ext3, and Ext4 file system using modified build config.
added some commits from the "official" git (Please see my git repository for detail.)
added audio boost (With this you'll have large range of volume but may have worse sound quality.)
Jan. 18, 2011: tytung_r2_oldcam (For old/N1 camera libs, HTC standard battery and partly support HTC extended battery.)
added some commits from the "official" git (Please see my git repository for detail.)
added audio boost (With this you'll have large range of volume but may have worse sound quality.)
Jan. 08, 2011: tytung_r1_oldcam (For old/N1 camera libs and HTC standard battery.)
based on hastarin's r8.6 oldcam branch
added normal RMNET driver
added unique Wi-Fi MAC address
supported CIFS UTF-8, Yaffs, Ext3, and Ext4 file system using modified build config.
All Downloads
All Downloads:
cLK_ppp_tytung_r14_update.zip. (for cLK and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb, Gpc's libaudio.so v2.8e and Cedesmith's libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r14_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb and Gpc's libaudio.so v2.8e.)
cLK_ppp_tytung_r14_callrec_update.zip. (for cLK and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb, Gpc's libaudio.so v2.8e and Cedesmith's libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r14_callrec_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb and Gpc's libaudio.so v2.8e.)
cLK_ppp_tytung_r13_update.zip. (for cLK and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb, Gpc's libaudio.so v2.8e and Cedesmith's libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r13_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb and Gpc's libaudio.so v2.8e.)
cLK_ppp_tytung_r13_callrec_update.zip. (for cLK and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb, Gpc's libaudio.so v2.8e and Cedesmith's libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r13_callrec_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb and Gpc's libaudio.so v2.8e.)
cLK_ppp_tytung_r12.4_update_v3.zip. (for cLK and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb, Gpc's libaudio.so v2.8e and Cedesmith's libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r12.4_update_v3.zip. (for MAGLDR and Gingerbread 2.3.4+ only) (Included Letama's htcleo.acdb renamed as default.acdb and Gpc's libaudio.so v2.8e.)
cLK_ppp_tytung_r12.4_update.zip. (for cLK and Gingerbread 2.3.4+ only) (Included Desire's stock default.acdb, Gpc's libaudio.so v2.8e and Cedesmith's libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r12.4_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only) (Included Desire's stock default.acdb and Gpc's libaudio.so v2.8e.)
cLK_ppp_tytung_r12_oldcam_update.zip. (for cLK) (Included Cedesmith's libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r12_oldcam_update.zip. (for MAGLDR)
cLK_ppp_tytung_r12_update.zip. (for cLK and Gingerbread 2.3.4+ only) (Included N1's stock default.acdb, Gpc's libaudio.so and Cedesmith's libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r12_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only) (Included N1's stock default.acdb and Gpc's libaudio.so.)
cLK_ppp_tytung_r11_oldcam_update.zip. (for cLK) (Included libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r11_oldcam_update.zip. (for MAGLDR)
cLK_ppp_tytung_r11_update.zip. (for cLK and Gingerbread 2.3.4+ only) (Included libhtc_ril_wrapper.so v8.0b4.)
kernel_tytung_r11_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only)
cLK_ppp_tytung_r10_oldcam_update.zip. (for cLK) (Included libhtc_ril_wrapper.so v8.0b5.)
kernel_tytung_r10_oldcam_update.zip. (for MAGLDR)
cLK_ppp_tytung_r10_update.zip. (for cLK and Gingerbread 2.3.4+ only) (Included libhtc_ril_wrapper.so v8.0b5.)
kernel_tytung_r10_update.zip. (for MAGLDR and Gingerbread 2.3.4+ only)
cLK_ppp_tytung_r9_oldcam_update_v2.zip. (for cLK)
cLK_ppp_tytung_r9_update_v2.zip. (for cLK)
kernel_tytung_r9_oldcam_update.zip. (for MAGLDR)
kernel_tytung_r9_update.zip. (for MAGLDR)
kernel_tytung_r8.3_oldcam_update.zip.
kernel_tytung_r8.3_update.zip. (Not for NexusHD2-Froyo, otherwise camera FC)
kernel_tytung_r8.2_oldcam_update.zip.
kernel_tytung_r8.2_update.zip. (Not for NexusHD2-Froyo, otherwise camera FC)
kernel_tytung_r8.1_oldcam_update.zip.
kernel_tytung_r8.1_update.zip. (Not for NexusHD2-Froyo, otherwise camera FC)
kernel_tytung_r7_oldcam_update.zip.
kernel_tytung_r7_update.zip. (Not for NexusHD2-Froyo, otherwise camera FC)
kernel_tytung_r6_update.zip. (Not for NexusHD2-Froyo, otherwise camera FC)
kernel_tytung_r6_oldcam_update.zip.
kernel_tytung_r5_update.zip. (Not for NexusHD2-Froyo, otherwise camera FC)
kernel_tytung_r5_oldcam_update.zip.
kernel_tytung_r4_update.zip. (Not for NexusHD2-Froyo, otherwise camera FC)
kernel_tytung_r4_oldcam_update.zip.
kernel_tytung_r3_oldcam_update.zip.
kernel_tytung_r2_eb_signed.zip. (Not for NexusHD2-Froyo, otherwise camera FC) (Not working for the HTC extended battery)
kernel_tytung_r2_signed.zip. (Not for NexusHD2-Froyo, otherwise camera FC)
kernel_tytung_r2_eb_oldcam_signed.zip. (Not working for the HTC extended battery)
kernel_tytung_r2_oldcam_signed.zip.
kernel_tytung_r1_oldcam_signed.zip.
Works perfectly on latest stable miui, GREAT!
Thank you tytung
@tytung
Regarding the real wifi mac on NAND boot, can i have the address you probe for the mac address string so i could see if it is available in bootloader or not. If it is, provide it as a part of the cmdline to the kernel.
Also if possible, how exactly you probe that area as this said feature has not been committed to your gitorious repo.
thank you chief!
are you plan to update to 2.6.35?
Rick_1995 said:
@tytung
Regarding the real wifi mac on NAND boot, can i have the address you probe for the mac address string so i could see if it is available in bootloader or not. If it is, provide it as a part of the cmdline to the kernel.
Also if possible, how exactly you probe that area as this said feature has not been committed to your gitorious repo.
Click to expand...
Click to collapse
Here you are.
http://pastebin.com/pnpPE23S
Please visit [Dev] Real WiFi MAC address thread for more info.
Code:
static int parse_tag_msm_wifi_from_spl(void)
{
uint32_t id1, id2, id3, id4, id5, id6;
uint32_t id_base = 0xFC028; //real mac offset found in spl for haret.exe on WM
id1 = readl(MSM_SPLHOOD_BASE + id_base + 0x0);
id2 = readl(MSM_SPLHOOD_BASE + id_base + 0x1);
id3 = readl(MSM_SPLHOOD_BASE + id_base + 0x2);
id4 = readl(MSM_SPLHOOD_BASE + id_base + 0x3);
id5 = readl(MSM_SPLHOOD_BASE + id_base + 0x4);
id6 = readl(MSM_SPLHOOD_BASE + id_base + 0x5);
sprintf(nvs_mac_addr, "macaddr=%2x:%2x:%2x:%2x:%2x:%2x\n", id1 & 0xff, id2 & 0xff, id3 & 0xff, id4 & 0xff, id5 & 0xff, id6 & 0xff);
pr_info("Device Real Wifi Mac Address: %s\n", nvs_mac_addr);
return 0;
}
Hi,
I read the first post and as i understand i have to delete initrd.gz in order to update my rom's kernel.
So i extract the zip file, delete initrd.gz and re zip it but when i want to install in cwm it said installation aborted, what i have to do?
PS i have typhoon rom version 3.6.2 and cwm 4.0.1.4
I have installed on my BOYPPC Gingerbread Stable.V2 ROM and have some issues while i make a call. It seems that the proximity sensor have a fault by activation, when the screen shuts off the call will terminated.
Is there a possibility to fix that?
So long thank you so much for your great work...
tytung said:
Here you are.
http://pastebin.com/pnpPE23S
Please visit [Dev] Real WiFi MAC address thread for more info.
Code:
static int parse_tag_msm_wifi_from_spl(void)
{
uint32_t id1, id2, id3, id4, id5, id6;
uint32_t id_base = 0xFC028; //real mac offset found in spl for haret.exe on WM
id1 = readl(MSM_SPLHOOD_BASE + id_base + 0x0);
id2 = readl(MSM_SPLHOOD_BASE + id_base + 0x1);
id3 = readl(MSM_SPLHOOD_BASE + id_base + 0x2);
id4 = readl(MSM_SPLHOOD_BASE + id_base + 0x3);
id5 = readl(MSM_SPLHOOD_BASE + id_base + 0x4);
id6 = readl(MSM_SPLHOOD_BASE + id_base + 0x5);
sprintf(nvs_mac_addr, "macaddr=%2x:%2x:%2x:%2x:%2x:%2x\n", id1 & 0xff, id2 & 0xff, id3 & 0xff, id4 & 0xff, id5 & 0xff, id6 & 0xff);
pr_info("Device Real Wifi Mac Address: %s\n", nvs_mac_addr);
return 0;
}
Click to expand...
Click to collapse
Yes, accessing 0x0 + id_base + 0x0 is causing segfault in lk. Will dump memory and go through for address of mac in magldr and clk.
Hello @tytung any change that you work on the cm-on-wince-htc from markinus repos? cm .35 kernel base.
Hi tytung,
You have inclued libaudio.so but did we always need default.acdb of 122 442 octets ?
Thank for your job
awesome, we have a 99% android native experience!!!
next step is audio lib and bluetooth fix? now we can only choose between high drain fully working BT or low drain but 50% compatibility BT
thank you
Thank you for all your great work...
If our HD2 is become so important, fast, stable, smooth, appreciated...
most of the credit is your!
THANKS TYTUNG
hey tytung
nice to see a dedicated thread for your kernels; thx!
can somebody help how to install r12 for sd card build...
thx
pirlano said:
awesome, we have a 99% android native experience!!!
next step is audio lib and bluetooth fix? now we can only choose between high drain fully working BT or low drain but 50% compatibility BT
Click to expand...
Click to collapse
can you please elaborate....which kernels / setup offers which scenario? thanks
Sent from my HD2 using xda premium
I have an HTC official extended battery. Any plans for full support? (e.g. accurate battery readings and use of full capacity) We are so close to perfection!
Thanks for all the hard work!
Sent from my HD2 using xda premium
djsolidsnake86 said:
thank you chief!
are you plan to update to 2.6.35?
Click to expand...
Click to collapse
No.
I will keep this kernel 2.6.32.

[KERNEL] is Tiny-shmem good for android?

Hi fellows,
I have made a patch to enable the use of Tiny-SHMEM instead the full SHMEM filesystem in android kernels. I think we can gain some performance here. It seems to be working, but I have some thoughts to share with you.
1) It seems that android uses /dev/ashmem rather than /dev/shm, and the only two functions of mm/shmem.c needed by mm/ashmem.c is available on tiny-shmem.
2) Android also needs to mount filesystem as tmpfs. If we use tiny-shmem, than tmpfs will use ramfs code. So, we will support online growing, but we can not limit sizes. I have just one partition (/app-cache) that has size limits. The question is: we actually need size limits?
If anyone like, I can release the patch after some testing I'm doing.
Thanks,
Ronan
I can help u test on, well you know!
Hi diz!
So, I'm attaching a patch for GT-P1000 kernels. It should be fine on every version.
It just modify the Init/Kconfig file since the tiny-shmem is already on source code and you just need to adjust the configuration to define CONFIG_TINY_SHMEM.
If you want to test, apply this patch into your kernel tree, execute 'make menuconfig', go to section:
General Setup -> Configure standard kernel features (for small systems) -> Default shmem filesystem implementation -> Tiny shmem filesystem
and then compile.
Any updates in this project??
Sent from my GT-P1000 using XDA App
jadmask3rlm said:
Any updates in this project??
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Still need people to test it... RAMFS could induce some problems...
My latest unstable kernel version has this patch applied and tiny-shmem is selected. If anyone wants to test: http://forum.xda-developers.com/showthread.php?t=1274855
But, it is just for LATIN models!
Ronis_BR said:
Hi diz!
So, I'm attaching a patch for GT-P1000 kernels. It should be fine on every version.
It just modify the Init/Kconfig file since the tiny-shmem is already on source code and you just need to adjust the configuration to define CONFIG_TINY_SHMEM.
If you want to test, apply this patch into your kernel tree, execute 'make menuconfig', go to section:
General Setup -> Configure standard kernel features (for small systems) -> Default shmem filesystem implementation -> Tiny shmem filesystem
and then compile.
Click to expand...
Click to collapse
Hello
I have, and then someone else (just to make sure) applied the patch, but the "default shmem filesystem implementation" option is not available in general setup, after running 'make menuconfig'
dizgustipated said:
Hello
I have, and then someone else (just to make sure) applied the patch, but the "default shmem filesystem implementation" option is not available in general setup, after running 'make menuconfig'
Click to expand...
Click to collapse
yea the same happened with me too(on another device too)
so what i did
in .config
add this:
CONFIG_TINY_SHMEM=y (it should be 'is not set')
Hi diz,
This option is under Configure kernel features (for small systems). It is the last option in the menu and you can select two values. Yesterday I applied the patch in my kernel tree and it works properly.
Sent from my GT-P1000L using xda premium
AH! Btw, you must enable:
CONFIG_MMU (System type)
CONFIG_EMBEDDED (General setup)
to see the option. So, if you haven't enabled CONFIG_SWAP, than you can choose CONFIG_TINY_SHMEM, otherwise just CONFIG_SHMEM will be available.
FYI, I'm using this with tiny-shmem for 8h and nothing weird happened yet
Thanks,
Ronan
working on it now,
up to the compile part,
its a little different working with my source, than stock
quick q
how do we show users this is working or even added in their kernels?
Well, you can execute:
busybox zcat /proc/config.gz | grep SHMEM
If you see:
CONFIG_TINY_SHMEM=y
Then tiny shmem was selected and is activated.
I'll wait your results! Thanks for the help!!!!
Ronan
Sent from my GT-P1000L using xda premium
Now, when trying to compile (mine and teks way)
It says, kernel tree not clean, please run make mrproper in kernel directory.
So I do, and it erases the tiny shmem, and goes back to default p1cm7 configuration.
Lol, kernel work makes porting a rom from basecode a walk in the park!
When typing make, or make zimage, in same directory as make menuconfig, it errors and says /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
and
make
make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
scripts/kconfig/conf -s arch/arm/Kconfig
init/Kconfig:957:warning: choice value used outside its choice group
init/Kconfig:958:warning: defaults for choice values not supported
make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
Generating include/generated/mach-types.h
CC kernel/bounds.s
/bin/sh: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2
below is my .config file, zipped because xda cant load hidden files
Hi diz,
First,
kernel tree not clean, please run make mrproper in kernel directory.
It is because the kernel directory has a git repo and it is not clean. When you use 'make mrproper' it will remove the patch because it probably wasn't commited yet.
The easiest way to solve it is:
mv .git .gitold
<Compile the kernel>
mv .gitold .git
If you do this, this problem should be gone.
The second error seems that you are pointing the gcc cross-compiler to a wrong path in Makefile. Check where you installed the compiler and set it accordingly in Makefile by changing the value of this variable:
CROSS_COMPILE ?=
Hope it helps!
Thanks,
Ronan
By the way, your config file seems to be ok!
Change the tool chain prefix to arm-none-eabi- and compile (after doing the steps ron told)
SUCCESS!!!!!!!!
I've posted it here,
http://forum.xda-developers.com/showpost.php?p=19128294&postcount=2205
Good! Let's see what will happen now
Thanks!
Cyanogen 7 tiny_shmem kernel
I have decided to move the kernel here.
So as not to "invade" another's thread
This is only for unofficial beta cm7 port
* FILE SYSTEM
TINY_SHMEM enabled
* LCD Voltage
down to 260000 from 300000
* I/O scheduler default
"no-op"
type: busybox zcat /proc/config.gz | grep SHMEM
in your terminal emulator
you will see:
CONFIG_TINY_SHMEM=y
(means tiny shmem is activated."
dizgustipated said:
I have decided to move the kernel here.
So as not to "invade" another's thread
* FILE SYSTEM
TINY_SHMEM enabled
* LCD Voltage
down to 260000 from 300000
* I/O scheduler default
"no-op"
type: busybox zcat /proc/config.gz | grep SHMEM
in your terminal emulator
you will see:
CONFIG_TINY_SHMEM=y
(means tiny shmem is activated."
Click to expand...
Click to collapse
THIS KERNEL IS Making my WIFI Hotspot activate on MIUI for SGT
- I just have issue with the Mobile Network being broken?
- The touchscreen also broken but i'ved fixed that one
- usb tethering error = ive'd fixed it too
Can you do something on the mobile data being broken on the kernel side?
Because if i use angel666 zimage , cm modded, mobile data work but hotspot broken
If i use this its the other way around. Lol

Kernel Appreciation Thread

I've scavenged the forums for kernel images in circulation and gathered a rather considerable collection of them. Here's the whole list, also including stock kernels for comparison (starting with 1.0.1, as this is the earliest version I have access to). I don't have direct links (didn't save them as I went on my collecting spree) but I renamed the files by the poster's name and the date of their post so each file should be easy to find through search. I also removed any duplicates (reposts).
The list is not by any means complete, and updates are most welcome but hopefully it's a good starting point, and others will find this summary helpful.
Using this thread you can identify if a kernel found somewhere else is the same as one of the "well-known" ones. The best way for this is to check the MD5 sum unless the file sizes obviously differ. Along with the kernel image list, there is also a comparison of other boot-related files (aka "the missing changelog") below.
Kernel Images (uImage)
All images in circulation seem to be based on Linux-2.6.29-omap1. The format of the data is as follows: the first column is the normalized filename (post date in YYYYMMDD format followed by the poster name). The second column is the creation date as recorded in the kernel (pulled from the image with mkimage -l). The third column is the image file size in bytes, and the ultimate, fourth column is the MD5 sum of the file.
Code:
uImage-20120122-verygreen Sun Jan 22 02:21:22 2012 1871536 4df25ed3887ded06e4894f31cc591767
uImage-20120326-mi100-multitouch Tue Mar 27 00:37:51 2012 1949768 35ae84d06b2397c3b1c3a18cf8489ddc
uImage-20120328-RenateNST-recommended Wed Mar 28 20:51:09 2012 2674768 2f30e452286187b4fd39a607ee08b460
uImage-20121002-guevor Tue Oct 02 23:57:28 2012 1922624 5389693e484ae478dba1ddd599af35f8
uImage-20121006-guevor Sat Oct 06 15:36:45 2012 1928808 117c33343bad9acc68642eaa0abca6cf
uImage-20121006-guevor-usbhost Fri Oct 05 02:12:02 2012 1927204 82e967e2b46401df642b803f386cbeec
uImage-20121014-guevor-166 Sat Oct 13 16:35:31 2012 1927292 6c4534cf34c3209cac23707de9bcd858
uImage-20121118-guevor-174 Fri Nov 16 21:30:24 2012 1929356 329b229f17fe08c235d352881c8bafa5
uImage-20121205-guevor-176-usbhost Wed Dec 05 19:36:24 2012 1929652 c9f649640131f1afa0e8a5b54883464e
uImage-20130525-waynesi Sat May 25 20:11:19 2013 1824476 67b0edb6bef76d119b60bd4ab86a525b
uImage-20130703-latuk Fri Jun 28 20:30:11 2013 2630460 15780cc3e9a8593627fd1c9608b068c9
uImage-20130703-latuk-nopowercheck Fri Jun 28 20:26:23 2013 2630736 18541b6fb9f2abd84daea77f3340d129
uImage-20130721-latuk-sd10 Mon Jul 15 18:21:51 2013 2630560 f43e6d9767e0d3dab18162b78a6fb7e3
uImage-20140813-Nookie-recommended Tue Apr 24 20:31:04 2012 2674584 69688487b17f6fa1202efba87aec3558
uImage-recovery-NookMgr-0.5.0 Sat Dec 08 11:46:06 2012 1827124 9366da88d7fc22b5019423b644e0fa6d
uImage-recovery-noogie Thu May 26 12:09:29 2011 1839448 0db7b475ef4dad39af21aa6af7619383
uImage-stock-101 Fri Jul 22 10:32:07 2011 1839824 a2408888c24986ec9ee9fac28bce08a4
uImage-stock-110 Sat Oct 29 15:45:55 2011 1841908 455700f060d49977da4adcce8e5516e8
uImage-stock-112 Tue Feb 28 05:38:36 2012 1841904 e056b6734c0420f3c1798f57fe4eb761
uImage-stock-121 Sat Dec 08 06:35:10 2012 1848944 a6a8bfa18ea3e7c74e87526881b980fd
The same list sorted by kernel build date:
Code:
20110526 uImage-recovery-noogie 1839448 0db7b475ef4dad39af21aa6af7619383
20110722 uImage-stock-101 1839824 a2408888c24986ec9ee9fac28bce08a4
20111029 uImage-stock-110 1841908 455700f060d49977da4adcce8e5516e8
20120122 uImage-20120122-verygreen 1871536 4df25ed3887ded06e4894f31cc591767
20120228 uImage-stock-112 1841904 e056b6734c0420f3c1798f57fe4eb761
20120327 uImage-20120326-mi100-multitouch 1949768 35ae84d06b2397c3b1c3a18cf8489ddc
20120328 uImage-20120328-RenateNST-recommended 2674768 2f30e452286187b4fd39a607ee08b460
20120424 uImage-20140813-Nookie-recommended 2674584 69688487b17f6fa1202efba87aec3558
20121002 uImage-20121002-guevor 1922624 5389693e484ae478dba1ddd599af35f8
20121005 uImage-20121006-guevor-usbhost 1927204 82e967e2b46401df642b803f386cbeec
20121006 uImage-20121006-guevor 1928808 117c33343bad9acc68642eaa0abca6cf
20121013 uImage-20121014-guevor-166 1927292 6c4534cf34c3209cac23707de9bcd858
20121116 uImage-20121118-guevor-174 1929356 329b229f17fe08c235d352881c8bafa5
20121205 uImage-20121205-guevor-176-usbhost 1929652 c9f649640131f1afa0e8a5b54883464e
20121208 uImage-recovery-NookMgr-0.5.0 1827124 9366da88d7fc22b5019423b644e0fa6d
20121208 uImage-stock-121 1848944 a6a8bfa18ea3e7c74e87526881b980fd
20130525 uImage-20130525-waynesi 1824476 67b0edb6bef76d119b60bd4ab86a525b
20130628 uImage-20130703-latuk 2630460 15780cc3e9a8593627fd1c9608b068c9
20130628 uImage-20130703-latuk-nopowercheck 2630736 18541b6fb9f2abd84daea77f3340d129
20130715 uImage-20130721-latuk-sd10 2630560 f43e6d9767e0d3dab18162b78a6fb7e3
RAM Disk Images (uRamdisk)
The missing changelog:
uRamdisk-stock-101 (Size: 185256, MD5: 054897f36c588b714f60bf41ebf7cbdf)
Initial version I have access to
uRamdisk-stock-110 (Size: 185298, MD5: ef473d179db2bf72bf6bd4cd3fd01dca)
/init.rc: Added:
Code:
# change permissions for calibration
chmod 0666 /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/forcecal
uRamdisk-stock-112 (Size: 185298, MD5: 5f3c7e2ffffd870454614a94ac4e33e5)
No changes
uRamdisk-stock-121 (Size: 185650, MD5: 6c2db57a6b9426ce10544fd9c8dc6f40)
/init
/init.rc: Added:
Code:
setprop_fromtoken ro.product.model /rom/devconf/ModelNumber
setprop_fromtoken ro.serialno /rom/devconf/DeviceID
Code:
chown system system /sys/class/leds/lcd-backlight/dim_brightness
chown system system /sys/class/leds/lcd-backlight2/dim_brightness
chown system system /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0040/dim_start
Code:
# Set default dim speed to 500ms
write /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0040/dim_time 500
Code:
[STRIKE][COLOR="Red"]on property:sys.settings_system_version=3[/COLOR][/STRIKE]
[B][COLOR="Green"]on property:dev.bootcomplete=1[/COLOR][/B]
start bootcnt
Code:
service copyassets /system/bin/copyassets.sh
user root
oneshot
Non-Stock Changes to RAM Disk Images
Excluding the obvious meddling with ADB.
/init.rc: Governor change for uImage-20121118-guevor-174:
Code:
# Enabling DVFS with conservative governor
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor [STRIKE][I][COLOR="Red"]conservative[/COLOR][/I][/STRIKE][B][COLOR="Green"]smartassV2[/COLOR][/B]
/init.rc: Adding -f to omap-edpd:
Code:
service omap-edpd /system/bin/omap-edpd.elf [B][COLOR="Green"]-f[/COLOR][/B] -n --timeout=2 -pV220 --fbdev=/dev/graphics/fb0 -s /system/lib/dsp/subframeip_snode_dsp.dll64P -w /rom/devconf/EpdWaveform,/system/etc/default_waveform.bin
/system/bin/omap-edpd.elf --help said:
--fastupdate (-f) : fast update algorithm ON
Click to expand...
Click to collapse
Init Binaries inside the RAM Disk (uRamdisk:/init)
init-101-110-112 (Size: 127964, MD5: 738a02210409fd9e31837053cd3c9b29)
Stock init
init-121 (Size: 128000, MD5: 72e5c0d66e8fcb070fb67a004045b012)
Stock init updated for 1.2.1
init-20120122-verygreen (Size: 107344, MD5: 1243d422e4f0532ffdf12f21b6632902)
Alternative init that allows the use of USB keyboard
Recovery Kernel Images (uRecImg)
The recovery kernel is always the same as the main one, unless you use a custom recovery. Among custom recoveries, Clockwork RC2 uses uImage-stock-110. For Noogie and NookManager 0.5.0 it seems to be something else than the other images I discovered (see above).
Recovery RAM Disk Images (uRecRam)
For obvious reasons I am limiting myself to stock images here. The missing changelog:
uRecRam-stock-101 (Size: 1508577, MD5: ce1d033d97953051fc59012a4335bc96)
Initial version I have access to
uRecRam-stock-110 (Size: 1514136, MD5: 16379c824c1a2bd823cba9690d0a3edc)
/etc/dsp/baseimage.dof
/etc/dsp/subframeip_snode_dsp.dll64P
/sbin/omap-edpd.elf
/sbin/recovery
uRecRam-stock-112 (Size: 1514134, MD5: 530b055737a01694dd1ce30bfae3531b)
No changes
uRecRam-stock-121 (Size: 1517774, MD5: 7b6af9319f5543cdab853672f3a70dff)
/etc/dsp/subframeip_snode_dsp.dll64P (again)
/res/images/icon_installing.png
/res/images/icon_installing_factory.png
/res/images/icon_installing_rom.png
/sbin/recovery (again)
/build.prop: Added:
Code:
persist.nook.cust.region=US
/init (as in the main image, see above)
Wrap-up
I started collecting this information in particular to reach some conclusion which kernel would be best for my purposes [for the record: (i) looking to squeeze as much as possible from the display with NoRefresh or FastRefresh, (ii) performance optimizations if stable and without impact on battery life, (iii) no need for USB host but OK if not a drain on batery, (iv) GlowLight support not a factor as my device doesn't have one, (v) SDXC Class 10 support also not a factor]. At this point I don't see a strictly dominating choice. I'll edit the post when or if this changes.

[DEV] Building a custom kernel and kernel modules for stock kernel

Since fire phone doesn't have a bootloader unlock at the moment. There is no point in building a custom kernel. But By building a kernel we can build kernel modules which work on the stock kernel. And yes you can load unsigned kernel modules without a problem since fire phone doesn't use tz apps to verify kernel modules like Samsung does.
Setup
Source
Download the fire phone sources for firmware 4.6.1 from here. And extract the platfrom.tar inside the archive to somewhere(KERNEL_DIR).
toolchain
You can use the android ndk from google, But it requires some setup. I'm using linaro toolchain from here. You can use compiler version 4.7, 4.8 or 4.9. Kernel I'm using (Firmware 4.6.3 - Linux 3.4-perf-g280c96c) is built with gcc-4.7. But I'm using this gcc-4.9. Download it, extract is somewhere(TOOLCHAIN_DIR) and add the $TOOLCHAIN_DIR/bin to your PATH. Theoretically you would be able to build the kernel on windows using Cygwin or MSYS tools but using Linux is better.
config
Connect your phone trough adb and run
Code:
adb pull /proc/config.gz
zcat config.gz > $KERNEL_DIR/kernel/qcom/3.4/.config
With this config you will run into some problems because of a missing "trapz_generated_kernel.h". I don't know if this is an auto generated file when they build android as a whole or amazon removed this explicitly(can they do that without violating GPL?). Anyway It looks trapz is some low level kernel debugging function(comment here if you know more about it). We can safely disable it. Open $KERNEL_DIR/kernel/qcom/3.4/.config in a text editor and change the lines
Code:
CONFIG_TRAPZ=y
CONFIG_TRAPZ_TP=y
CONFIG_TRAPZ_TRIGGER=y
CONFIG_HAVOK=y
to
Code:
#CONFIG_TRAPZ=y
#CONFIG_TRAPZ_TP=y
#CONFIG_TRAPZ_TRIGGER=y
#CONFIG_HAVOK=y
building
Now edit the $KERNEL_DIR/kernel/qcom/3.4/Makefile and add this changes
Code:
EXTRAVERSION = -perf-g280c96c
This is at the top of the makefile. If we don't add this, vermagic for the modules will differ from stock kernel and they won't load.
ARCH=arm
CROSS_COMPILE=arm-linux-gnueabihf-
Click to expand...
Click to collapse
Here arm-linux-gnueabihf- is my cross compiler frefix. Look in $TOOLCHAIN_DIR/bin/ to find it.
Now cd into $KERNEL_DIR/kernel/qcom/3.4/ and do
Code:
make
The build will fail a few times complaining about missing headers. Most of the time it's just
Code:
#include <myheader.h>
instead of
Code:
#include "myheader.h"
Edit the source file where the build fails and change <>s to ""s. (maybe android ndk ignores the difference and include the headers anyway)
After kernel compiles, we are good to go. We can use this kernel sources to build kernel modules for stock kernel.
Kernel modules
To build the kernel modules, we basically need two things. An approximate kernel source and the Module.symvers file from the original kernel. We can get the Module.symvers file by building the complete kernel as explained above or Just extract it from our stock kernel.
To extract the Module.symvers from the stock kernel, extract the boot.img file from firmware update image. Get mkbootimg tools from here compile it and run
Code:
unmkbootimg --kernel zImage ---ramdisk ramdisk.cpio.gz -i boot.img
After you get the zImage. Download extract-symvers script from here and run
Code:
python2 extract-symvers.py -B 0xc0008000 zImage > Module.symvers
place this file in $KERNEL_DIR/kernel/qcom/3.4/ (You still have to do the changes mentioned above in kernel config and building section run make in the $KERNEL_DIR/kernel/qcom/3.4 and intrupt it after few seconds)
Now you can build loadable modules against this source. Here is a hello world kernel module.
Code:
//hello.c
#include<linux/module.h>
#include<linux/kernel.h>
#include<linux/init.h>
static int __init hello_start(void)
{
printk("hello to the world from module");
return 0;
}
static void __exit hello_end(void)
{
printk("heloo exit");
}
module_init(hello_start);
module_exit(hello_end);
Code:
#Makefile
KERNEL_DIR=<your kernel dir>/kernel/qcom/3.4
obj-m := hello.o
PWD := $(shell pwd)
default:
$(MAKE) ARCH=arm CROSS_COMPILE=armeb-linux-gnueabi- -C $(KERNEL_DIR) SUBDIRS=$(PWD) modules
Put this files in a folder and run make in it. Change the paths and cross compiler prefix according to your setup. and run make.
After the build push the hello.ko to the phone.
Code:
adb push hello.ko /sdcard/
adb shell
su
cd sdcard
insmod hello.ko
run dmesg and you'll see the message.
I'm currently trying to build kexec module from hashcode's sources and USB OTG modules.
I'm attaching a few thing helped me do this.
since they have released this version of the fire os they have to provide the source code
see
http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic
you have just shown that the source code they releases for the kernel does not match the one used to build the kernel. This means it is a clear violation of the gpl and amazon is in breach and can be sued.
on another note.
are the drivers for the nfc and camera compiled as a module or into the kernel?
They have yet to provide 4.6.3 and 4.6.4 kernel sources too.
I don't know exactly but in order for NFC and camera to work drivers are required and they are in fact compiled into the kernel.
The problem we currently have with NFC and camera is proprietary hal (hardware abstraction libraries) They are a part of Android and does not subject to GPL. Amazon changed the original android way how hal works and didn't release the sources!
by looking at the kernel drivers maybe we would be able to implement hal from scratch. But I don't see that intense dev support for fire phone. If you are up for it camera sources are at $KERNEL_DIR/kernel/qcom/3.4/drivers/media/platform/msm/camera_v2/
Major MAJOR respect for all of you making the Fire Phone even better!
@madushan1000
Could we do something like this to install a custom boot.img?
http://forum.xda-developers.com/optimus-l9/general/guide-install-custom-roms-locked-t3249828
I don't own this device but has anyone tried to see if kexec works?
spudowiar said:
I don't own this device but has anyone tried to see if kexec works?
Click to expand...
Click to collapse
Nope, I was working on it. But then I got a job. It will be sometime before I can start working on it again.
Could someone please provide the config extracted from /proc/config.gz?
I can't find this on CM11 rom for some reason.
Building the kernel now.
Some bugs are in the code and -Wall and gcc-wrapper.py escalate the warnings.
I wonder if those errors are there on purpose XD
helloworld.ko loaded successfully
I was able to execute kexec without anything. Just the binary.
Will keep you posted - this hacking might take a while to figure it all out.
I already have 3.4 kernel from the amazon sources.
I have the kexec userland program.
What is left is a loadable kexec kernel module (if that is possible at all).
removed
Okarin said:
Are we even sure those Amazon Kernel Sources are correct?
Those errors caught by the wrapper scripts are giving me the creeps.
Git the kexec_load.ko build.
Currently hands on insmod.
Phone doesn't do a reboot any longer:
insmod kexec_load.ko
init_module(0xb6e6c008, 408241, "") = -1 ENOENT (No such file or directory)
write(2, "insmod: init_module '/sdcard/kex"..., 79insmod: init_module '/sdcard/kexec_load.ko' failed (No such file or directory)
) = 79
munmap(0xb6e6c000, 409600) = 0
mprotect(0xb6f8c000, 4096, PROT_READ|PROT_WRITE) = 0
mprotect(0xb6f8c000, 4096, PROT_READ) = 0
close(0) = 0
close(1) = 0
close(2) = 0
futex(0xb6f6cd74, FUTEX_WAKE_PRIVATE, 2147483647) = 0
munmap(0xb6f8c000, 4096) = 0
exit_group(-1) = ?
First goal is to get module loaded.
Goal reached:
kexec_load 27813 0 - Live 0x00000000 (O)
procfs_rw 12770 0 - Live 0x00000000 (O)
wlan 3793980 0 - Live 0x00000000 (O)
Shouldn't be functional at all..
I disabled some function calls just to get the module loaded.
The missing symbols are:
soft_restart
arch_kexec
machine_shutdown
And the version I use does some insane function hooking ..
More rework is needed.
[email protected]:/data/local # ./kexec /sdcard/vmlinux
kernel: 0xaf12d008 kernel_size: 7e1354c
unrecoverable error: could not scan "/proc/device-tree/": No such file or directory
<6>[ 97.681256] Kexec_load: Replacement... :
<6>[ 97.681344] kexec_load : my_syscall_table : c0106244
<6>[ 97.681405] kexec_load : kexec_load before replacement : c01b346c
<6>[ 97.681480] kexec_load : kexec_load after replacement : bf3a5650
<6>[ 97.681546] kexec_load : reboot before replacement : c01a83f0
<6>[ 97.681616] kexec_load : reboot after replacement : bf3a6348
<6>[ 97.681675] Kexec_load: End replacement... :
<6>[ 202.694691] Kexec: - Starting kexec_load...
<6>[ 202.694849] Kexec: - ---- kexec_load - result : '0'
It gets better:
255|[email protected]:/data/local # ./kexec --dtb=/sdcard/zImage-dtb /sdcard/vmlinux
kernel: 0xaf1b1008 kernel_size: 7e1354c
kexec-zImage-arm : dtb.img BEFORE CUT : Start : '0xae66f008' - Length : '0xb411e9' - End : '0xaf1b01f1'
Segmentation fault
More tomorrow.
Click to expand...
Click to collapse
Where are you getting your kexec module sources from? BTW try using the original amazon kernal binary the phone is shipped with (we are sure it works). Don't use the custom kernel for the kexec tests (We don't know the custom kernel actually works)
madushan1000 said:
Where are you getting your kexec module sources from? BTW try using the original amazon kernal binary the phone is shipped with (we are sure it works). Don't use the custom kernel for the kexec tests (We don't know the custom kernel actually works)
Click to expand...
Click to collapse
Here is the thread I used as a starting point.
I will put up my "fork" on github after I get permission to do that
The userland part build like a charm once I took the compiler you recommended.
The kernel-module was tricky because the whole thing is modded like hell.
To be able to load I had to comment out some hard coded addresses and the calls to unresolvable symbols.
removed
Okay the kernel gets loaded.
But
kexec -e shuts off the device.
strace doesn't help.
On the plus side:
Devices are shutdown
Look promising
I need a way to tail dmesg ...
Okay a lot of digging around and I found out that the reboot syscall doesn't work properly..
It doesn't look like it hits the kexec_module it looks more like it hits the actualy sys_reboot
Okay reboot syscall hits my reboot-hook.
But the softreboot doesn't work now.
Okay there is some kind of watchdog runnig which doesn't like my kexec.
I need to kill it - that should happen tomorrow.
removed
I hit the same wall when I tried to isolate the kexec code from the kernel itself to a module. I stopped working on it because I lacked the time. BTW the error you are facing now
<3>[ 80.580644] BUG: scheduling while atomic: kexec/4067/0x00000002
Click to expand...
Click to collapse
is because memory allocator is trying to switch threads while you are in a syscall. it's because of lines like this
image = kzalloc(sizeof(*image), GFP_KERNEL);
Click to expand...
Click to collapse
Try changing GFP_KERNEL to GFP_ATOMIC. Other than that, I have another suggestion. Try to get the kernel to run in a single core mode before running kexec code. This might simplify things. I don't know how to do this though.
madushan1000 said:
I hit the same wall when I tried to isolate the kexec code from the kernel itself to a module. I stopped working on it because I lacked the time. BTW the error you are facing now
is because memory allocator is trying to switch threads while you are in a syscall. it's because of lines like this
Try changing GFP_KERNEL to GFP_ATOMIC. Other than that, I have another suggestion. Try to get the kernel to run in a single core mode before running kexec code. This might simplify things. I don't know how to do this though.
Click to expand...
Click to collapse
The atmic error is gone now. It went away after I disabled the watchtog.
smp_disable() is what you are looking for - but this causes the system to hard_reboot ATM XD
what happens if you kill every userlevel program before smp_disable()?
removed
#define tomorrow
Okay .. I worked out the preemption thing.
At least it does something.
Still a black screen and the MSM_WATCHDOG is a ***** again.
It needs to be suspended .. at least that what I get from the code I read here.
If I remove the driver too early the output in /proc/kmsg stops ..
If I try to remove it too late ... well it causes a resched while atomic.

HFP Android Nougat

Hi!
At the moment I' trying to make HFP working
For now I install the APK found in the lbdroid Github code for Android HFP Client
I also did this command:
1: adb root
2: adb remount
3: adb shell
4: setprop persist.service.bt.hfp.client true
5: getprop persist.service.bt.hfp.client (this should return true now)
6: turn OFF/ON bt once.
But I'm not able to activate the HFP on my Samsung S8
I try this
(01-21-2019, 04:02 AM)lsb Wrote:
Do you have these two patches in source code ?
These two patches fix bluetooth HFP not working. One is for pcm config and another is to enable hfp.
My skype works. Smile
1. In folder hardware/realtek/ and git log
===========================
commit 4a84dd0ccf040cfb300fc05dadebf1ebbb54b658
Author: Lyle_Lin <[email protected]>
Date: Mon Sep 3 16:31:17 2018 +0800
Bluetooth: update rtl8723bs_config for pcm config
Fix no sound on bluetooth hfp.
Change-Id: I19db11cadc4c919180553ad45335ac6b9d1104b6
============================
2. In folder device/rockchip/common and git log
============================
commit f00fb6b0225b409e7074aff7cc6ff2e3925c38ea
Author: Lyle_Lin <[email protected]>
Date: Mon Sep 3 16:34:30 2018 +0800
Bluetooth: enable hfp profile
Change-Id: I5ffdebdf7829324e075fc8b4fd0ad2bc43cf0c5e
============================
But I never found the folder:
device/rockchip/common
or
hardware/realtek/
I'm wotking on a tinker board S anf the community seem to be thin
Please HELP!!!

Categories

Resources