Related
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.)
Since the European genuine HTC ROM
Code:
# uname -a
Linux localhost 2.6.35.10-g60b2609 #1 PREEMPT Sun Apr 17 01:15:33 CST 2011 armv6l GNU/Linux
has tun support disabled according to the /proc/config.gz I got with scp from my marvel,
Code:
# CONFIG_TUN is not set
I just build one
using the wildfire S kernel source code from htcdev
and
http://marakana.com/forums/android/examples/111.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
but with arm toolchain from http://www.emdebian.org/crosstools.html
Code:
$ gunzip config.gz
$ cp -vp config .config
$ make xconfig -> enable tun, set CONFIG_CROSS_COMPILE="arm-linux-gnueabi-"
or use the patch in zipfile.
Code:
$ make modules_prepare
$ make modules
$ make modules_install INSTALL_MOD_PATH='../install'
Module Binary is attached, please test. Copyright is GPL >= V. 2,
md5sum
10fd212186ee8506d72d14b00aa15bf5 tun.ko.zip
a8f6e2bd1f7bab19f02371955b9eda0d tun.ko
I got problems dependency checking without building the whole kernel:
Code:
$ /sbin/depmod -ae -b ../install/modules -E ./Module.symvers 2.6.35.10
WARNING: ../install/modules/lib/modules/2.6.35.10/kernel/drivers/net/tun.ko needs unknown symbol register_netdevice
... dozens more...
$ /sbin/depmod -n /usr/local/src/htc-kernel/install/modules/lib/modules/2.6.35.10/kernel/drivers/net/tun.ko
/usr/local/src/htc-kernel/install/modules/lib/modules/2.6.35.10/kernel/drivers/net/tun.ko:
# Aliases extracted from modules themselves.
alias devname:net/tun tun
alias char-major-10-200 tun
# Soft dependencies extracted from modules themselves.
# Copy, with a .conf extension, to /etc/modprobe.d to use it with modprobe.
# Aliases for symbols, used by symbol_request().
alias symbol:tun_get_socket tun
# Device nodes to trigger on-demand module loading.
tun net/tun c10:200
No questions or Support par PM or E-Mail. Report and ask here, pls.
Or tell me an IRC channel where android devs meet.
Thanks, but I suggest preference of stability and integrity before performance at experimental state kernels
Well, I start my Android world with smaller steps.
And as a conservative engineer I wouldn't overclock.
Ok, thanks.
BTW: Noone has been chasing me with an axe yet, so I assume the tun.ko module works?
Thank you for your work.
I try to load this tun.ko on Wildfire S, but module don't load.
Code:
insmod: init_module '/system/lib/modules/tun.ko' failed (Exec format error)
When I check magic number of module, here is only '2.6.35.10', but maybe right is '2.6.35.10-g60b2609'.
Please, is it possible to fix it?
(I need tun.ko because openvpn...)
Thx
Hmm, thx, I've expected the emdebian gcc is not compatible with armv6l.
You need to use the toolchain from the android sdk or the one from the CM guys site.
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.
A couple of questions:
1 . Has anyone had any success hooking up a webcam? If so what model? So far I have tried an HP webcam 3100 and a Logitech C270 and neither seems to be detected.
2. Any success in side-loading Skype? The apk installed however since my webcams were not detected there was no mic/cam picked up. Doesn't look like I'll be doing much in its current state.
I ran "adb bugreport" in case it contains anything useful. Attaching to the post 7zipped.
Pertinent info:
Build: bueller-user 4.2.2 JDQ39 51.1.5.0_user_515030720 test-keys
Build fingerprint: 'qcom/bueller/bueller:4.2.2/JDQ39/51.1.5.0_user_515030720:user/release-keys'
Bootloader: unknown
Radio: apq
Network: (unknown)
Kernel: Linux version 3.4.0-perf-gf191309 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Apr 2 18:55:49 PDT 2015
Command line: androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 androidboot.emmc=true androidboot.serialno=70900114511706N2 androidboot.baseband=apq
Didn't find anything useful doing a google search. No mention of using webcams at all with Fire TV.
Thanks all.
Wow your post is from today!
Todo for today was to check that out.
I am on root with the 51.1.5.0_515020820.
I try later this day Skype app from amazon store, from gp-store and perhaps the xda-mod version. But of course at first my Microsoft Studio HD Webcam should work
Greetings by I_did_it_just_tmrrow
I tried once mine, I think it is a Microsoft one, the model that is sold for Sony TVs, but I am on an older firetv firmware and Skype didn't even recognised the camera. So, out of the box, in the past it didn't work. Let us know how it is now.
Did I just understand that right:
The FireTV OS (FireOS) is based on the linux kernel Monolithic.
Does the kernel Monolithic support webcams?
Did I just understand that right that under linux there where no driver-files like in win-os, so if the kernel does not suport the device you have to update/change the kernel?
Code:
[email protected]:/ # cat /proc/version
cat /proc/version
Linux version 3.4.0-perf-gf191309 ([email protected]) (gcc version 4.6.x-g
oogle 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Mar 12 21:58:15 PDT 2015
[email protected]:/ #
the same output with or without connected MS Studio HD Wecam , see here:
Code:
lsmod
adsprpc 6735 0 - Live 0x00000000
wlan 450113 0 - Live 0x00000000 (O
eth 66936 0 - Live 0x00000000 (O)
Greetings by I_did_it_just_tmrrow
EDIT:
SUCCESS!
Got a picture with this app called "
Externe USB SnapExWebcam" and enabled super-User request.
Hi
Could you explain how you got this to work? Just sideload Skype & Externe USB SnapExWebcam and it will work? or is there more to do? I am rooted.
Thanks
I_did_it_just_tmrrow said:
Did I just understand that right:
The FireTV OS (FireOS) is based on the linux kernel Monolithic.
Does the kernel Monolithic support webcams?
Did I just understand that right that under linux there where no driver-files like in win-os, so if the kernel does not suport the device you have to update/change the kernel?
Code:
[email protected]:/ # cat /proc/version
cat /proc/version
Linux version 3.4.0-perf-gf191309 ([email protected]) (gcc version 4.6.x-g
oogle 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Mar 12 21:58:15 PDT 2015
[email protected]:/ #
the same output with or without connected MS Studio HD Wecam , see here:
Code:
lsmod
adsprpc 6735 0 - Live 0x00000000
wlan 450113 0 - Live 0x00000000 (O
eth 66936 0 - Live 0x00000000 (O)
Greetings by I_did_it_just_tmrrow
EDIT:
SUCCESS!
Got a picture with this app called "
Externe USB SnapExWebcam" and enabled super-User request.
Click to expand...
Click to collapse
Hill16 said:
Hi
Could you explain how you got this to work? Just sideload Skype & Externe USB SnapExWebcam and it will work? or is there more to do? I am rooted.
Thanks
Click to expand...
Click to collapse
At first: Skype did not work correctly. Perhaps because he had no mic&video but I think there is more to do then enable the webcam for skype.
At the moment I use the mod version v4.7, here from xda. But when I open the exdended menu he told me that there is no webcam device found. I think it has something todo with the rights (chmod) of /dev/video0 because SnapExWebcam bring it to work and change it to 666 with chmod.
Anybody knows a solution?
Is there a way to give the Skype app More rights if they dont ask for More rights?
Greetings by Idijt
The new 4k Fire TV with OS 5 - anything change that we can now get Skype and USB webcam to work?
thanks
usb web camera app and dashcam connected at fire tv.works.but not with sk
I_did_it_just_tmrrow said:
At first: Skype did not work correctly. Perhaps because he had no mic&video but I think there is more to do then enable the webcam for skype.
At the moment I use the mod version v4.7, here from xda. But when I open the exdended menu he told me that there is no webcam device found. I think it has something todo with the rights (chmod) of /dev/video0 because SnapExWebcam bring it to work and change it to 666 with chmod.
Anybody knows a solution?
Is there a way to give the Skype app More rights if they dont ask for More rights?
Greetings by Idijt
Click to expand...
Click to collapse
usb web camera app and dashcam connected at the usb of fire tv..works.but not with skipe.
any app video chat can works.now that you can use a usb cam?
Github repo: https://github.com/kernel-killer/android_kernel_huawei_h30u10
All changes I made since last commit are in my private repo.
Install packages (Not sure if it's right):
Code:
sudo apt-get install build-essential
Note: Please run ./mk ckeck-env to verify your build enviroment (Newer GNU MAKE will fail but the code compiles the same with new or older version)
Build:
Code:
./mk bm_new k
Testing your new kernel:
Download both attachments (KernelSwapper and BootimgRestore).
Append headers from stock kernel to zImage (which can be found at ./out/target/product/huawei82_cwet_kk/obj/KERNEL_OBJ/arch/arm/boot/zImage)
In KernelSwapper update 'kernel' with your own generated zImage rename it to 'kernel' and replace it inside zip.
In BootimgRestore replace 'boot.img' with your current ROM's boot.img in case that something goes wrong (e.g.: Phone not booting).
Copy the two new zips into phone's memory (or SD card) and flash KernelSwapper.
===== Reserved #1 =====
Thanks for the awesome work KK. I am on CM 13 3.4.67 kernel. Can i use this or do i have to be in stock rom for testing the kernal?
Sent from my Honor 3C using Tapatalk
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
Update : Flashed the kernel, phone booted but felt laggish while using. I am still testing, will let you know what happens
Sent from my Honor 3C using Tapatalk
karkeankit said:
Thanks for the awesome work KK. I am on CM 13 3.4.67 kernel. Can i use this or do i have to be in stock rom for testing the kernal?
Sent from my Honor 3C using Tapatalk
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
Update : Flashed the kernel, phone booted but felt laggish while using. I am still testing, will let you know what happens
Sent from my Honor 3C using Tapatalk
Click to expand...
Click to collapse
Yes, I'm sure that the kernel has multiple bugs. The phone may feel laggish because there is enabled low-level kernel debugging over UART.
Thank you for testing...
kernel.killer said:
Yes, I'm sure that the kernel has multiple bugs. The phone may feel laggish because there is enabled low-level kernel debugging over UART.
Thank you for testing...
Click to expand...
Click to collapse
You are welcome, wishint you good luck for further development
Sent from my Honor 3C using Tapatalk
Hi, tnx for The kernel
if i Update my kernel VPN bug in CM12.1 will fix?
hamadk said:
Hi, tnx for The kernel
if i Update my kernel VPN bug in CM12.1 will fix?
Click to expand...
Click to collapse
Nope, it's ROM bug not a kernel bug plus I have released only development preview version which has enabled many debugging options and it may be quite buggy.
Thanks, but can this process led to a suitable kernel for CM13?
Does this kernel fixes the video playback problem and the recording problem?(Can't play or capture 720p videos, screen recorder works fine, just the camera.)
Sent from my Huawei Honor 3C using XDA Labs
Lumpbloom7 said:
Does this kernel fixes the video playback problem and the recording problem?(Can't play or capture 720p videos, screen recorder works fine, just the camera.)
Sent from my Huawei Honor 3C using XDA Labs
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=67848925&postcount=8
mhxygh said:
Thanks, but can it this process led to a suitable kernel for CM13?
Click to expand...
Click to collapse
Aim of this project is to make stock kernel sources stable for KitKat ROMs (It is originally for KK) but somebody else may patch them for CM 13. I am not working on this nor I'll do.
Will you be adding extra CPU governors and IO schedulers along with kernel level wakeups for double tap waking?
I was wondering who else is developing kernel 3.10.XX for this device ?
Ms_Julia said:
I was wondering who else is developing kernel 3.10.XX for this device ?
Click to expand...
Click to collapse
Actually, nobody is working on 3.10.X kernel. And I'm rather focusing on LineageOS for now.
What is the defconf for our device in kernel source
imranpopz said:
What is the defconf for our device in kernel source
Click to expand...
Click to collapse
This should include most configs
Code:
/* Mediatek common */
./mediatek/config/common/autoconfig/kconfig/AEE
./mediatek/config/common/autoconfig/kconfig/USER
./mediatek/config/common/ProjectConfig.mk
/* MT6582 common */
./mediatek/config/mt6582/autoconfig/kconfig/platform
./mediatek/config/mt6582/ProjectConfig.mk
/* h30u10 device specific */
./mediatek/config/huawei82_cwet_kk/autoconfig/kconfig/project
./mediatek/config/huawei82_cwet_kk/ProjectConfig.mk
kernel.killer said:
This should include most configs
Code:
/* Mediatek common */
./mediatek/config/common/autoconfig/kconfig/AEE
./mediatek/config/common/autoconfig/kconfig/USER
./mediatek/config/common/ProjectConfig.mk
/* MT6582 common */
./mediatek/config/mt6582/autoconfig/kconfig/platform
./mediatek/config/mt6582/ProjectConfig.mk
/* h30u10 device specific */
./mediatek/config/huawei82_cwet_kk/autoconfig/kconfig/project
./mediatek/config/huawei82_cwet_kk/ProjectConfig.mk
Click to expand...
Click to collapse
Replace Device Name with the configuration file found at:
Source/arch/arm/configs
It's written in this way something_DeviceCodename_user_defconfig
I need for the above step.. ☝☝☝
imranpopz said:
Replace Device Name with the configuration file found at:
Source/arch/arm/configs
It's written in this way something_DeviceCodename_user_defconfig
I need for the above step.. ☝☝☝
Click to expand...
Click to collapse
Well... This is Mediatek, DO NOT expect the sources to look nice. The configs are scattered through ./mediatek subdirectories, *.mk files are parsed and configs are assembled during build. Unfortunatelly, even if you manually assemble .config you will NOT be able to build the kernel. It is full of dirty hacks (Mediatek) and just typing "make" won't work, build will break.
Build:
Code:
$ git clone https://github.com/kernel-killer/android_kernel_huawei_h30u10.git
$ cd android_kernel_huawei_h30u10
$ export ARCH=arm && export ARCH_MTK_PLATFORM=mt6582 && export TARGET_PRODUCT=huawei82_cwet_kk
$ export CROSS_COMPILE=/path-to-your-toolchain/.../bin/arm-linux-androideabi-
$ ./mk n k
Code:
$ ./mk -h
Usage: (makeMtk|mk) [options] project actions [modules]
Options:
-t, -tee : Print log information on the standard-out.
-o, -opt=bypass_argument_to_make
: Pass extra arguments to make.
-h, -help : Print this message and exit.
Projects:
one of available projects.
Actions:
listp, listproject
: List all available projects.
check-env : Check if build environment is ready.
check-dep : Check feature dependency.
n, new : Clean and perform a full build.
c, clean : Clean the immediate files(such as, objects, libraries etc.).
r, remake : Rebuild(target will be updated if any dependency updats).
mrproper : Remove all generated files + config + various backup files in Kbuild process.
bm_new : "new" + GNU make's "-k"(keep going when encounter error) feature.
bm_remake : "remake" + GNU make's "-k"(keep going when encounter error) feature.
mm : Build module through Android native command "mm"
mma : Build module through Android native command "mma"
emigen : Generate EMI setting source code.
nandgen : Generate supported NAND flash device list.
codegen : Generate trace DB(for META/Cather etc. tools used).
drvgen : Generate driver customization source.
custgen : Generate customization source.
javaoptgen : Generate the global java options.
ptgen : Generate partition setting header & scatter file.
bindergen : Generate binder related information
sign-image : Sign all the image generated.
encrypt-image : Encrypt all the image generated.
update-api : Android default build action
(be executed if system setting or anything removed from API).
check-modem : Check modem image consistency.
upadte-modem : Update modem image located in system.img.
modem-info : Show modem version
gen-relkey : Generate releasekey for application signing.
check-appres : Check unused application resource.
sdk : Build sdk package.
win_sdk : Build sdk package with a few Windows tools.
banyan_addon : Build MTK sdk addon.
banyan_addon_x86 :Build MTK sdk x86 addon.
cts : Build cts package.
bootimage : Build boot image(boot.img).
cacheimage : Build cache image(cache.img).
systemimage : Build system image(system.img).
snod : Build system image without dependency.
(that is, ONLY pack the system image, NOT checking its dependencies.)
recoveryimage : Build recovery image(recovery.img).
secroimage : Build secro image(secro.img).
factoryimage : Build factory image(factory.img).
userdataimage : Build userdata image(userdata.img).
userdataimage-nodeps
: Build userdata image without dependency.
(that is, ONLY pack the userdata image, NOT checking its dependencies.)
dump-products : Dump products related configuration(PRODUCT_PACKAGE,PRODUCT_NAME ect.)
target-files-package
: Build the target files package.
(A zip of the directories that map to the target filesystem.
This zip can be used to create an OTA package or filesystem image
as a post-build step.)
updatepackage : Build the update package.
dist : Build distribution package.
Modules:
pl, preloader : Specify to build preloader.
lk : Specify to build little kernel.
md32 : Specify to build DSP md32.
tz, trustzone : Specify to build trusted execution environment.
k, kernel : Specify to build kernel.
dr, android : Specify to build android.
NULL : Specify to build all components/modules in default.
k <module path>
: Specify to build kernel component/module with the source path.
dr <module name>
: Specify to build android component/module with module name.
Other tools:
prebuilts/misc/linux-x86/ccache/ccache -M 10G
: Set CCACHE pool size to 10GB
Example:
./mk -t e1k emigen
: Generate EMI setting source code.
./mk -o=TARGET_BUILD_VARIANT=user e1k n
: Start a user mode full build.
./mk listp : List all available projects.
./mk e1k bootimage
: Build bootimage for e1k project.
./mk e1k bm_new k
: Build kernel for e1k project.
./makeMtk e1k c,bm_remake pl k
: Clean & Build preloader and kernel for e1k project.
./makeMtk e1k n k kernel/xxx/xxx
: Build(full build) kernel component/module
under the path "kernel/xxx/xxx" for e1k project.
./makeMtk e1k r dr Gallery
: Rebuild android module named Gallery for e1k project.
./makeMtk e1k mm packages/apps/Settings
: Change Directory to packages/apps/Settings and execute "mm"
./makeMtk e1k mma packages/apps/Settings
: Change Directory to packages/apps/Settings and execute "mma"
Edit:
I fixed the sources, so menuconfig can be used.
Apply patch:
Code:
$ git am 0001-Fix-build-using-make-command.patch
Build:
Code:
$ cd kernel && export ARCH=arm && export ARCH_MTK_PLATFORM=mt6582 && export TARGET_PRODUCT=huawei82_cwet_kk
$ export CROSS_COMPILE=/path-to-your-toolchain/.../bin/arm-linux-androideabi-
$ make -C $(pwd) O=output h30u10_defconfig menuconfig
$ make -C $(pwd) O=output
Append MTK headers:
Code:
$ ../mediatek/build/tools/mkimage output/arch/arm/boot/zImage KERNEL > output/zImage
*Note: I recommend using AOSP arm-linux-androideabi-4.9 toolchain.
Getting cp: cannot stat 'out/target/product/huawei82_cwet_kk_kernel.log
Make [1]: [kernel ] error 1
Make: *** [remake] error 2