Develop Bugs

[KERNEL][GPL][SECURITY][I9000] FuguMod (Gingerbread) VoodooSndV10

Included in the image are:
- Superuser
- own busybox 1.18.4
- TUN support
- No more RFS at all (if you want)
- JVB source based
- CWM 3.0.0.5
- security fixes
- low latency
- filesystems: jfs, ext2/3/4 (using ext4 driver), reiserfs, rfs (not on Ultra)
- CIFS support
- Voodoo SoundV10
- Voodoo color (sharpness fix)
- BLN (enabled by default)
- Preemptive RCU (only on Ultra)
- 10 fingers support (on roms that support it)
It has been tested on JVB/JVH/JVO/JV9
Read the whole post (except the changelog) before attempting to install
Thanks to Neldar for BLN
Thanks to Supercurio for voodoo additions
Thanks to zurchpet and js8 for dedicated testing
Thanks to Andro1d for ideas
Thanks to mothatt for the vectorized picture
Thanks to virnik for the new boot logo
For safety purposes /dev/block/stl3 is not mounted anymore but /efs is copied to /dbdata.
Quick table on the versions:
Two branches: Stable (which is stable) and Bleeding Edge (includes latest changes, in testing, consult the changelog)
Two versions in each branch: Normal (without preemptive RCU) and Ultra (with preemptive RCU)
Video
http://www.youtube.com/watch?v=mO-MiKVAzD8
You must flash a normal kernel before Ultra or you will not have phone/modem
Ultra does NOT support RFS filesystem
This kernel can now also be flashed from DOC rom in http://romkitchen.org thanks to Stefunel, choose a non wipe rom.
You can get it at . Normal version is named zImage-rXXX and Ultra is named zImage-ultra-rXXX.
Logs are in /fugumod.log
You can get support on #romkitchen on irc.freenode.net
Unless some unexpected changes occur, I am not going to produce any overclocked kernel anytime in the future as they have proven multiple times to be too unstable.
- All versions are upgradeable to the latest one without any data loss.
- You must have at least 400Mb free on your internal SD card storage for conversions. If you don't have any apps installed. If you have apps already installed, you must ensure that you have at least the same size as you data storage free on the sdcard. Note that upgrades don't really need space on your external storage.
- It is only known to work with international GT-I9000 and the Bell 9000M.
- The cleanest way to revert the mod is to reflash a complete ROM. But now supports reverting to RFS as well.
- If you use another custom kernel, you don't need anymore to revert the lagfix before applying. But it is always a good idea to start from a clean ROM.
Locale/timezone reset when using some filesystems
Some people may see that time zone sometimes reset at boot or even language reset, the easy solution is to edit /system/default.prop with something like:
persist.sys.timezone=Europe/Brussels
persist.sys.language=en
persist.sys.country=BE
Click to expand...
Click to collapse
Chances are that those settings are not in your /system/default.prop, it is safe to append them after the already defined ones.
See [url]http://en.wikipedia.org/wiki/List_of_zoneinfo_timezones for your timezone
How to convert filesystems:
Use FuguApp or FuguAppFree or create a /sdcard/fugumod/fs.convert file. If you don't see the paid version in the market and only see the free one, it may be due to your ROM build prop, just change it with SGS tools (in SGS tools -> prop editor -> build.prop -> Unlock -> ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.3/GINGERBREAD/XWJVB:user/release-keys and leave the rest as is. save, Apply script -> clear market cache, reboot...)
You can also create a /sdcard/fugumod/fs.convert which has the same syntax as /sdcard/fugumod/fs.current
How to specify custom filesystem mount options:
Create a file called /sdcard/fugumod/fs.options
It should contain the FS options like shown below (not specify a fs is equivalent to no option). Options "noexec nodiratime nosuid nodev nosuid" are "enforced".
stl9 noatime,barrier=0
stl10 noatime,barrier=1
stl11 noatime,notail
mmcblk0p2 relatime,barrier=0
Click to expand...
Click to collapse
Root bug with some applications:
Some applications don't properly detect if the phone is rooted, generally because they expect su to be in /system/xbin
Solution: type the following commands as root using adb shell or connectbot or any other shell console:
mount -o remount,rw /system
mkdir -p /system/xbin
cp /sbin/su /system/xbin/
mount -o remount,ro /system
Click to expand...
Click to collapse
What is Ultra version
Ultra version is a version with a preemptive RCU which brings an impressive user experience by having a near realtime response. Interestingly, it also seem to boost quadrant scores by ~15%.
Bleeding Edge can be found here
But it is not compatible with RFS filesystem, so don't flash if
- you still use RFS in any of /system, /data, /dbdata , /cache
- you haven't at last booted once a normal FuguMod edition
- you don't have basic skills of recovering from soft bricking (generally, flashing a normal edition will solve soft brick with Ultra)
Start adbd as root
If you want to start adbd as root and in recovery, you need to create a file called /sdcard/fugumod/debug
The change will only take place on next reboot.
Why is quadrant score so low ~1000 in ext4 but I still feel my phone is really fast?
- Quadrant does no measure latency, but user does it. You could have a completely unresponsive phone with very high quadrant score.
- I use safe mounts for ext4, but if you feel brave enough, you can tweak them using fs.options explained earlier or switch to JFS.
- Some ROMs/kernels set "media.stagefright.enable-player=true" in build.prop, in general this will give you 500+ supplementary quadrant score but but will break playing some videos. This won't make your phone faster or more responsive or whatever, it will only boost your quadrant score and break some videos.
Which filesystem is the best?
This all depends on your perception. I general, having /system on reiserfs and all others on jfs seems to be the fastest.
Random reboots
They are known to happen if:
- you force switch the radio band for example using "band selection" in diagnostic menu from wcdma 1900/2100 to 850 or 900 gsm.
Wifi not working
If your wifi is not working anymore, you probably use a JVH based ROM and have restored your wifi settings via titanium backup (or possibly other backup utilities). Wifi configuration from pre-JVH is not compatible with JVH ROMs. You should be able to restore without reflashing a full ROM by stopping wifi, then doing the following commands in a root shell.
cd /data/wifi
cp bcm_supp.conf bcm_supp.conf.bak
cp wpa_supplicant.conf wpa_supplicant.conf.bak
rm bcm_supp.conf
ln -s wpa_supplicant.conf bcm_supp.conf
cat bcm_supp.conf.bak | head -n5 > wpa_supplicant.conf
cat wpa_supplicant.conf.bak >> wpa_supplicant.conf
rm wpa_supplicant.conf.bak bcm_supp.conf.bak
Click to expand...
Click to collapse
And enable wifi again
WARNING: This may brick your phone, kill your cat or destroy your house (although in theory it should not).
If you like it, remember there are donations which may help me getting a development phone
Repository: http://github.com/renaudallard
Source of other GPL utilities I use: http://faramir.eriador.org/r/
Download
http://faramir.eriador.org/r/Samsung_galaxys/, it is called zImage-rXXX or zImage-ultra-rXXX. Bigger XXX number means it's the most recent version.
Changelog:
https://github.com/renaudallard/kernel-GB-GTI9000/commits/fugumod

sounds interesting, I'm keen to hear more about your project

A bit more info would be nice: quadrant score, are apps like newsrob fast.

Install it yourself, and play its the only way to get a feeling on how it preforms.
However:
JPM - Clean
Quadrant Score: 981
default slice_sync (97), slice_async (39)
Write: 12800000 bytes (12.2MB) copied, 2.836737 seconds, 4.3MB/s
Read: 12800000 bytes (12.2MB) copied, 0.222411 seconds, 54.9MB/s
JPM - with jfs
Quadrant Score: 1658
Write: 12800000 bytes (12.2MB) copied, 1.311856 seconds, 9.3MB/s
Read: 12800000 bytes (12.2MB) copied, 0.221596 seconds, 55.1MB/s
Tests done with:
dd if=/dev/zero of=/data/test count=25000
dd if=/data/test of=/dev/null

erased for better timeline

Have you tried with ReiserFS and XFS ?? Because I wanted to test with those even if they might use more cpu they should be faster, but I didn't had the time to,

Yeah this is interesting.
I must admit I hesitated between Ext4 and JFS during original choice for Voodoo and after a lot of reading (and head scratching) I chose Ext4 mostrly because of the ease to get e2fsprogs working, and their maturity.

Hey guys I love the developers society I'm glad to see that our phone has such hard working developers! Looking forward to good news from you

nikademus said:
Hello,
I was not intending to post this at first, but it seems some people are interested in my works on the Galaxy S.
I made a very raw script to convert /data to jfs on the external SD (at the moment).
I am open to all suggestions, so feel free to post
Click to expand...
Click to collapse
By the way, if you want to avoid creating new script (conversion, etc) I suppose you can "port" Voodoo to JFS in a few minutes.
Don't hesitate to ask for details if you're interested in.
I'm curious about this, I feel like I could have underestimate JFS for mobile (about the low CPU utilization part), like, you know, the general underestimation of this filesystem.
On my tests, the battery really used by the filesystem itself is really minimal, but still

supercurio said:
By the way, if you want to avoid creating new script (conversion, etc) I suppose you can "port" Voodoo to JFS in a few minutes.
Don't hesitate to ask for details if you're interested in.
I'm curious about this, I feel like I could have underestimate JFS for mobile (about the low CPU utilization part), like, you know, the general underestimation of this filesystem.
On my tests, the battery really used by the filesystem itself is really minimal, but still
Click to expand...
Click to collapse
I would like to see Voodoo using JFS, I think that it will only be better.

Will be interesting to compare only recently updated to JPM so will have to give this a look..

exadeci said:
Have you tried with ReiserFS and XFS ?? Because I wanted to test with those even if they might use more cpu they should be faster, but I didn't had the time to,
Click to expand...
Click to collapse
I did not try xfs, but reiserfs did quadrant scores of about 1200.
XFS overhead is higher than many others, so battery wise, it may not be a good idea. If you wish to test, I made an xfs.ko module on my site (even a btrfs one).

This page is an interesting read, what's your opinion about this?
http://wiki.archlinux.org/index.php/JFS
btw this remark is very bad for Android usage: http://wiki.archlinux.org/index.php/JFS#JFS_losing_files
I don't how valid it is.

nikademus said:
I did not try xfs, but reiserfs did quadrant scores of about 1200.
XFS overhead is higher than many others, so battery wise, it may not be a good idea. If you wish to test, I made an xfs.ko module on my site (even a btrfs one).
Click to expand...
Click to collapse
I experienced a bad habit that XFS has, it tend to produce garbage in files when not powered down cleanly
XFS was mostly designed to work efficiently with big files.
JFS looks like a more sensible choice

btw this remark is very bad for Android usage: #JFS_losing_files
I don't how valid it is.
Click to expand...
Click to collapse
I know about this, but under android, memory pressure should be sufficient to force writes.
Also it's not very clear how this affects the filesystem. If someones first job is to power the system unproperly, then with whatever filesystem, you will have problems at some point. Also, there is a "discussion" about this here too:
http://wiki.archlinux.org/index.php/Talk:JFS_Filesystem
(this link posting is a little bit annoying, if someon knows how to bypass that, I would be happy to hear)

nikademus said:
...(this link posting is a little bit annoying, if someon knows how to bypass that, I would be happy to hear)
Click to expand...
Click to collapse
You need at least ten (or twelve, don't remember well) posts. Since your posts are particular interesting, I hope you will break that limit very soon...
Thank you very much for your contribution.

daigoro64 said:
You need at least ten (or twelve, don't remember well) posts. Since your posts are particular interesting, I hope you will break that limit very soon...
Thank you very much for your contribution.
Click to expand...
Click to collapse
Thanks for finding my work interesting, hopefully, I will break the post barrier soon.

I think you should work with the z4mod team so they can provide a jfs update.zip

http://llorien.org/samsung_galaxys/
i'll help you hyperlink it lol. you can quote it or something idk. go spam some posts in Q&A and you can post links yourself ;p

Adevem said:
llorien.org samsung_galaxys
i'll help you hyperlink it lol. you can quote it or something idk. go spam some posts in Q&A and you can post links yourself ;p
Click to expand...
Click to collapse
Thanks for linking (even if I cannot qupote you correctly)

Krazy-Killa's Kernel Release - RLS 5.9.2.2 Released!

CPUFreq Successfully Installed and Running​
Please visit my website for additional information
After receiving alot of positive results from my Kernel and several releases later. We have arrived at RLS 5.9, a prototype build incorporating CPUFreq for CPU Scaling and Idle control, and a modified version of Power Management. We are at a release stage of this Alpha build, and approaching Beta, where it is as follows:
Each build that is released that has an update to CPUFreq will have an update to the first subversion in the build version (eg. RLS5.9.1.0)
Each build that is released that has an update to Power Management will have an update to the second subversion in the build version (eg. RLS 5.9.0.1)
And of course each upgrade to a specific subsystem of the Kernel will up the version number of that specific subversion.
Current Release: RLS 5.9.2.2​
RLS 5.9.2.2 will mark the beginning of the Beta stage out of Alpha stage. This release is showing far more promising results than my initial CPUFreq release.
I just want to personally thank all who have been supporting me and reporting any and all bugs that have been coming in, as I have been squashing them left and right in preparation to improve our Kernel for our phones to make them more feasible for everyday use.
Currently Being Tested:
Power Management - Reverted some old changes to the power management code, switched too Apps Sleep. Made some minor changes to the original pm.c source code and results are promising. Running VanijlEclair RLS11, and in rare cases the phone still crashes while sleeping, which I believe is related to the phone hiccuping when going to sleep, which in theory could completely blow up the timer that Apps Sleep uses for sleeping. I will investigate this part further, but so far, RLS 5.9.2.2 is much more stable than my previous release.
CPUFreq - No changes to the source code, still attempting to modify permissions so Android can modify the files that are required.
HAReT Users - Thanks in large part to V3rt!g(o) HAReT users can now boot the Kernel. I have made a slight modification to the default.txt file provided in the RLS 5.9 HAReT archive that uses Apps Sleep instead of Power Collapse. From what was reported, the Kernel takes about 2 minutes to initialize from WinMo, but after about 1min30sec to 2min, Android should begin loading.
Radio ROM - Currently Testing Radio 1.71.09.01, and so far it seems very stable and provides better battery usage.
Current Release (RLS5.9.2.2):
Kernel - HTC Polaris support re-introduced.
CPUFreq - Has been installed, and working inside the Kernel only. Android does not recognize CPUFreq correctly.
Processor - MSM-7201 processor increased from 384MHz to 528MHz
Stability - Has been improved further. Phone correctly sleeps and wakes properly. Still occasional crash occurs, but is random. Could go a full day without a crash, or could crash every 4hrs. Issue might be related to how much the CPU is being utilized at the time of wake up.
Power Management - Power Management restored to near WinMo states, still not as good as RLS5.7, but within range. Phone will last a full day of occasional use, and about 80% of the day on moderate use.
Initrd - New BootLogo has been made, and inserted into initrd. Unfortunately boot menu is not accessible. Made install scripts to compensate.
YAFFS2 - Exclusively does ECC checking on it's own without any help from the NAND driver. This should help with data corruption, but is not a permanent solution.
YAFFS2 - Disabled Forced erase chunk checking, slight increase in response time and decrease in read-time.
MTD - Disabled Verify NAND Page Writes
MTD - Disabled GPIO NAND Driver
EXT - EXT2 is currently disabled inside the Kernel. EXT4 has been fully enabled, aside from journaling, and is fully supported in the kernel and install scripts.
System - Switched from DG (High Resolution) Timer, to GP (Low Resolution) Timer.
System - Fully disabled High Resolution Timer -- Provided a decrease in kernel size without loss of performance.
sysfs - Enabled configfs. This will unavoidably increase RAM usage, but allow easier access to sysfs.
MSM - Performance Counter Driver enabled.
FrameBuffer Driver - Decreased fake-vsync delay from 10 to 5. Less times snow effect appears.
Known Issues:
Internal CPUFreq coding is unable to scale the processor, but the hacked msm_cpufreq_* functions are able to control the processor speeds. This will explain why CPUTuner and other Android software is reporting the CPU running at max speed. Will continue to investigate and work out problems with the coding.
JIT Compiler causes issues with framework.acore. Avoid using if possible.
CompCache not the cause of untracked PID errors -- Still investigating cause, though now understanding that it is related to data corruption.
Possibly depending on Radio, GPS takes quite awhile to acquire if not at all. -- Will investigate by flashing an older/newer radio.
Standby code not fully working due to being incompatible with clock code changes. Attempting to re-write power management code to be better compatible with the new clocks code.
CPUFreq Specifics:
Governors - Currently CPUFreq supports the following governors and can be changed while in Android using the Terminal: ondemand, conservative, powersave, performance. Userspace is currently disabled inside the Kernel.
Frequencies - Baseline frequencies the CPU will scale to but not limited too are: 81920 (82MHz), 122880 (123MHz), 245760 (246MHz), 384000 (384MHz). These are just placeholders to control where the CPU needs to scale too base on usage, it will go between lets say 82MHz and 123MHz or use one of the two.
Userspace - Until I can verify CPUFreq is fully operational without any issues, I will not enable Userspace Governor at this time.
Kernel Modules
File Attached to this Post, see below.​
This Kernel has been tested with the AT&T Tilt variant of the Kaiser. Using it on any other Kaiser would in theory produce the same results, but due to minor changes in the hardware of each variant of the Kaiser, I'm still going to stress caution when using this Kernel with any other variant of the Kaiser
Things to note about EXT4: This file system will increase read/write cycles to your SD Card. Use with caution as it will decrease the life of your SD Card. Though since Journaling is disabled, read/write cycles will have decreased, but they are still higher than what they would be if EXT2 was used. If you do not feel comfortable having EXT4 on your SD Card, do not use this Kernel as there is no way to use EXT2. You have been warned.
Things to take note with this Kernel: Do not enable JIT compiler under Settings, as this has produced constant FCs with the acore framework. It is recommended that you enable CompCache and set it to the default 18%, as this provides a significant performance boost, and decreases Home screen closures while running other apps.
USE THIS KERNEL AT YOUR OWN RISK. I TAKE NO RESPONSIBILITY FOR ANY DAMAGES DONE TO YOUR PHONE WHILE USING THIS KERNEL.​

Woohoo ! First Post!
Thank you Krazy-Killa! Will definitely try this now will post after testing!

I am liking what I am seeing. Thanks for putting the effort into creating this. I'm just curious about one thing, you said that Scoot's CM7 RLS1 build has the modules for this kernel included. Is there a separate download of the modules for anyone that might not be using this build?

Hello Krazy-Killa,
Appreciate your effort !
I just installed it on my TYTN II and so far going well -edited .ngh to change the key mapping to normal.
3G works fine. yet to see BT,WiFi &GPS and overall otherwise.
I have tried Scoot's CM7 RLS1 build 2 days ago.is there any major changes you did - i feel some audio notification alerts changed w. r. t. Scoots.
how can i use those audio files if reqd-i mean can copy&dump to a specific folder and repack.
but its not really matter..
At the moment 'push' works fine and eager to see any 'server connection' problem will occur later with the email client.
i have radio 1.70.19.09
Thanks once again for the post.
Cheers !

cerebralgenius said:
I am liking what I am seeing. Thanks for putting the effort into creating this. I'm just curious about one thing, you said that Scoot's CM7 RLS1 build has the modules for this kernel included. Is there a separate download of the modules for anyone that might not be using this build?
Click to expand...
Click to collapse
I will release the modules as a seperate androidupdate file this evening.
@chandra_100,
All my testing shows BT, WiFi, and GPS working. This Scoots CM7 build I released is just repackaged with my built modules for easy install.
Sent from my AT&T Tilt using XDA App

“Removed support for HTC Polaris”
That’s too bad，poor Polaris，555555555555555~

The untracked PID errors are related to froyo only (maybe Gingerbread too). And its related to init.rc provided with each build. Not kernel's fault

dark_prince said:
The untracked PID errors are related to froyo only (maybe Gingerbread too). And its related to init.rc provided with each build. Not kernel's fault
Click to expand...
Click to collapse
Interesting... Well, I had a looping untracked PID this morning, had to reinstall, but that's mainly the only problem I'm now having... If I could I would build a new init, but the bootenv isn't updated.

Krazy-Killa said:
Interesting... Well, I had a looping untracked PID this morning, had to reinstall, but that's mainly the only problem I'm now having... If I could I would build a new init, but the bootenv isn't updated.
Click to expand...
Click to collapse
The bootenv is fully up to date The untracked PID's aren't caused by the init.rc, they are caused by corrupt filesystems or files which mean that the paths that sysinit.rc is trying to mount aren't there or it can't change permissions on a file because it is corrupt.

for me kernel can't find data.img

Ive go some kind of problem. Im using fresh froyo and when I installed your modules update than I got hang in boot. Excatly at "adb_open" line. Without update everything is ok except wifi.
Sorry for my poor english

Neo2SHYAlien said:
for me kernel can't find data.img
Click to expand...
Click to collapse
I'll look into it. Though I may know the reason why, so I'll do some more testing, and will release once I have it fixed.
scooter1556 said:
The bootenv is fully up to date The untracked PID's aren't caused by the init.rc, they are caused by corrupt filesystems or files which mean that the paths that sysinit.rc is trying to mount aren't there or it can't change permissions on a file because it is corrupt.
Click to expand...
Click to collapse
I'll update my local bootenv, thanks.

Good release. Slightly slower than Clemsyn's kernel (tested in quadrant), but good stability. One thing drives me crazy - I have to wait 5-10 seconds after pressing power button to wake device

MaRekRM said:
Good release. Slightly slower than Clemsyn's kernel (tested in quadrant), but good stability. One thing drives me crazy - I have to wait 5-10 seconds after pressing power button to wake device
Click to expand...
Click to collapse
That was mentioned in the known issues, don't worry my next release will fix that (currently testing). Plus it'll add full EXT4 support like with clemsyn's kernel but you can format your SD card with the device now as I have updated initrd.
Sent from my AT&T Tilt using XDA App

Flashing
I'll try... flashing right now.
what about ipv6 support?
*EDIT* nevermind, i just saw that ipv6 is implemented.

Cannot restore databackup.img trough install menu...
I think this kernel canot handle the img fs. Mount is failing.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App

It's because of EXT2 support being turned off... I'm currently testing a new kernel that'll be using EXT4. Running into the same problem you are having with img mounting.
I'm working on isolating the issue why img mounting isn't working.. It's possibly an issue with the init scripts. I'll dig more into it and hopefully get it isolated.

Backup FS
Krazy-Killa said:
It's because of EXT2 support being turned off... I'm currently testing a new kernel that'll be using EXT4. Running into the same problem you are having with img mounting.
I'm working on isolating the issue why img mounting isn't working.. It's possibly an issue with the init scripts. I'll dig more into it and hopefully get it isolated.
Click to expand...
Click to collapse
Probably the script that is generating databackup.img still using ext2.

tiagoclc said:
Probably the script that is generating databackup.img still using ext2.
Click to expand...
Click to collapse
Yep, it was exactly that. Just made the necessary changes, and compiled a new kernel. I'll go ahead and throw it out, but for now I'll point out that I haven't tested it so, please let me know the results.
Init itself is already setup to mount all loopback and SDcard partitions as EXT4 where applicable.
Just use atools to configure the kernel to use /system and/or /data on NAND or SDCard.

Why did you remove polaris support? I think that are plenty of polaris users that want to test your kernel
Thanks

[Test][Kernel] -fox 2.6.27 kernel for RHOD Only!

I pulled the latest kernel tarball, fixed and tweaked a few things, then compiled it on my Rhodium. Although it works well on my Rhodium, I cannot guarantee that it will work on yours. In addition, it is guaranteed NOT to work on any other since I disabled support for it in .config.
You can install this kernel just like the one you would off the autobuild. The kernel is named -fox-YYDDMM where the date is when I pulled the tarball. While suggestions and feature request are welcome, it takes me ~2.5hr to go through one compile, so don't expect a new build very often.
You need the patched haret.exe as well as an additional line in startup.txt to boot this kernel. Instructions for that can be found at http://forum.xda-developers.com/showpost.php?p=14519408&postcount=1.
Latest (8/20) at http://db.tt/OeRyLYu
Changelog:
8/20 http://db.tt/OeRyLYu
microp: Upstream version of LED patch from Detule. Please note the requirement of updated lights.msm7k.so still applies.
8/16 http://db.tt/3UWBs3y
microp: Updated microp LED patch from Detule, now with more blinkenlights goodness (and yes, it even blinks). In order to use this, however, you need an updated liblights from http://db.tt/ZUjymT9. The file should be bind-mounted on startup in your froyo.user.conf, ie: mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so
8/15
microp: Proposed LED patch from Detule, mailing list has instruction on how to play with the blinkenlights.
.config:
Enabled IP_NF_TARGET_REDIRECT as a module because it's needed for certain app.
Started from clean source to get rid of any residuals.
8/11
Compcache: Included 0.5.4, patched kernel to support the swap notify
clock-wince: Added a debug output that shows freq requested, closest set, and the calc, without needing clock_wince.debug_mask=15.
.config notes:
LZOCOMPRESS/DECOMPRESS is built-in to the kernel. Therefore if you want compcache, you just need to insmod xvmalloc.ko and ramzswap.ko.
8/9
Upstream: htc_headset_microp fix
acpuclock: Changed turbo mode+20mhz only when acpuclock.force_turbo=2 is set. Also, overclock by 20mhz for any bus speed >100MHz.
modules: Use strip --strip-unneeded.
8/6
acpuclock: Change turbo mode t->axiclk_khz from 160000 to 180000. AXI clock control the bus freq, and upping it should make overall performance better.
clock-wince: Add supposed support for 48Mhz SD clock from .35. HOWEVER the kernel claims calc_freq is 61.44Mhz according to clock_wince.debug_mask=15. You also need to add msmsdcc_fmax=48000000 in order to use this clock anyway.
proc_comm_wince: Fix long-standing issue with msm_proc_comm_wince_pending_ints & DEX_INT_VBUS check which clobbered pending_int. You should no longer have a SoD during transition changes to/from suspending while inserting/removing the USB cable.
microp-k*: Got rid of the printk spam of backlight/keyled status changes.
.config changes:
1) Change default I/O scheduler to deadline. Our kernel does not do well with noop.
2) Change default AMSS firmware interface to 6125 which is what I have on my RHOD400. You can check yours (which is in the modem) by running dmesg | grep AMSS.
3) Change kernel default sleep_mode from CONFIG_MSM7X00A_SLEEP_MODE_POWER_COLLAPSE_SUSPEND to POWER_COLLAPSE. This is usually overridden but makes pm.sleep_mode=1 unnecessary.
4) Change CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN from 128MHz to 112Mhz. This meant that the kernel never used the 112MHz clock because it was below the ondemand minimum. No-frills CPU can confirm this.
5) arm6k support enabled. Not sure if it makes a difference but the kernel hasn't complained.
6) Conservative and Powersave governor enabled.
7) CONFIG_INPUT_TABLET disabled, nothing was enabled in there anyway and ours uses TOUCHSCREEN.
8) CONFIG_USB_ANDROID_RNDIS_WCEIS enabled, supposedly makes Windows think it's dealing with a NDIS ICS device.
9) Enabled ext4 and disabled yaffs2. Ted T'so backported fixes for ext4 for .27 release. This contains all the patches available on his ext4 git for the 2.6.27 kernel, but still should be considered EXPERIMENTAL.
GPL availability notice:
kernel source as available from http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commits/htc-msm-2.6.27
compcache module+patch from http://code.google.com/p/compcache/downloads/detail?name=compcache-0.5.4.tar.gz
.config used to compile available from within /proc/config.gz
Minor patches to the kernel source can be made against the git tree upon request. Please PM me if you are in need of that.
-- Starfox

Hmm haret freezes with your kernel on my rhod100_de.
(pm.sleep_mode=1 is deleted in startup.txt / no difference with pm.sleep_mode=1 not deleted)

Put sleep_mode back, and if it still doesn't boot, it's possible that the axi bus is too high. I'm looking to make it a kernel parameter in the next compile.
-- Starfox

So far so good.
Couple of things - first, it seems you didn't strip the modules...? There's no way they should be 7+mb .
Second, of all the things you've put in this kernel, one really stood out to me:
Starfox said:
proc_comm_wince: Fix long-standing issue with msm_proc_comm_wince_pending_ints & DEX_INT_VBUS check which clobbered pending_int. You should no longer have a SoD during transition changes to/from suspending while inserting/removing the USB cable.
Click to expand...
Click to collapse
If that's true ^^ (and works) why not submit a patch to mainline? Or is this your testbed for patch submission?
Good work, I'll see what I can make blow up. Only just booted... doesn't seem faster, but it's still settling methinks.

Please use the posted kernel/modules combo from the OP. I support 2 most recent revisions.
-- Starfox

i tried running this. it gets stuck at the HaRET: Booting Linux Dialogue in WinMo. am i suppossed to make any changes to startup.txt because i tried adding msmsdcc_fmax=48000000 to startup.txt and am getting the same response. is there anything I am suppossed to be doing?

anish88 said:
i tried running this. it gets stuck at the HaRET: Booting Linux Dialogue in WinMo. am i suppossed to make any changes to startup.txt because i tried adding msmsdcc_fmax=48000000 to startup.txt and am getting the same response. is there anything I am suppossed to be doing?
Click to expand...
Click to collapse
What device, build?

Rhod400, frx07
maybe a sample of the startup.txt would be appreciated too
also where am i suppossed to put msmsdcc_fmax=48000000 maybe im putting it in the wrong spot?

Running 8/6 here on rhod400. It seems just a tad bit faster/smoother.

anish88 said:
Rhod400, frx07
maybe a sample of the startup.txt would be appreciated too
also where am i suppossed to put msmsdcc_fmax=48000000 maybe im putting it in the wrong spot?
Click to expand...
Click to collapse
Did you just assume where the msmsdcc command goes? lol.
It goes in the "cmdline" between the quotes - where pm.sleep_mode is, etc. Make sure there's at least one space between each entry.
I'd imagine that's your issue, as I have the same phone/build and it works great for me.

arrrghhh said:
Did you just assume where the msmsdcc command goes? lol.
It goes in the "cmdline" between the quotes - where pm.sleep_mode is, etc. Make sure there's at least one space between each entry.
I'd imagine that's your issue, as I have the same phone/build and it works great for me.
Click to expand...
Click to collapse
odd, still no dice for me? what does your startup look like in general?

anish88 said:
odd, still no dice for me? what does your startup look like in general?
Click to expand...
Click to collapse
Did you rename the kernel? Have you updated the kernel before...?
My startup isn't anything special, just FRX07 with some additions for me (rel_path, OC, msmsdcc, no_partitions...)
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "msmsdcc_fmax=48000000 acpuclock.oc_freq_khz=714000 lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 rel_path=Androids/Stock07 no_partitions"
boot

i didnt have set initrd_offset 0x00a00000. i changed it, booting as we speak.

anish88 said:
i didnt have set initrd_offset 0x00a00000. i changed it, booting as we speak.
Click to expand...
Click to collapse
Shouldn't need it for .27... I forgot to mention that one tho, good catch. That is for .35/.39/3.0... .27 should work without it (and you'll need a new version of HaRET to use .35/.39/3.0 with that initrd_offset...)

anish88 said:
i tried running this. it gets stuck at the HaRET: Booting Linux Dialogue in WinMo. am i suppossed to make any changes to startup.txt because i tried adding msmsdcc_fmax=48000000 to startup.txt and am getting the same response. is there anything I am suppossed to be doing?
Click to expand...
Click to collapse
STOP.
If you are not getting past the boot scroll, then your phone cannot take the changes I made.
Again, let me make this clear. I do not guarantee that your phone will work with this kernel. I also can guarantee you that no mount of fiddling with startup.txt will change the fact that your phone will not boot.
You can try the updated zImage several post past the OP which should allow you to boot. Do not go blindly changing stuff in startup.txt. If you do not know what it does, ASK first.
-- Starfox

Starfox said:
STOP.
If you are not getting past the boot scroll, then your phone cannot take the changes I made.
Click to expand...
Click to collapse
Welcome to the joys of providing patches to the public...

The new zImage doesn't work for me either.
So my phone can't handle your kernel
Perhaps the AMSS firmware or the arm6k?

No Joy with Rhod500
Just tried this on my Rhod500 and I get a couple of Vibs from phone when Haret is launched, but the screen won't even re-paint... Just thought I would let everyone know...
Thanks...

If you need to know the AMSS version, it is shown during the HTC splash screen as [bunch of letters]-6125 or something very similar. From what I see the GSM users are having most of the issues, so it probaby is AMSS related.
-- Starfox

mgross029 said:
Just tried this on my Rhod500 and I get a couple of Vibs from phone when Haret is launched, but the screen won't even re-paint... Just thought I would let everyone know...
Thanks...
Click to expand...
Click to collapse
Ditto to this on a CDMA Rhod400 also. Vibrates on launching Haret, but does not go any further.

Nook Touch kernel hacking

So i have downloaded the nook touch kernel source and have gotten it to build using the gossamer defconfig. (as described somewhere by jesusfreke)
then as a test i enabled ext4 support and recompiled
then converted my system partition to ext4 while booted into noogie on the sdcard.
i also edited the init.rc to mount /system as ext4 and enable adb over usb support
and it seems like it works as shown in the code below.
Code:
[email protected]: nook_touch$ adb shell cat /proc/version
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #3 PREEMPT Tue Oct 4 14:37:59 CDT 2011
[email protected]: nook_touch$ adb shell cat /proc/mounts
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext4 ro,barrier=1,data=writeback 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
so where do i go from here? how do i start forward porting the kernel to .32 or .35 or do i even need to do that? in general what needs to change to get a cyanogenmod compatible kernel?
also how can we get a serial or UART output from the nook touch. I have been testing some cm builds from the nook color but it doesnt boot far enough for abd to give any output. ive looked at the back of the board but there doesnt seem to be any blatantly obvious serial port connections on it like the nook color has.
ps. uImage and uRamdisk are attached for reference. i try them if you want. but backup yours first!

Help this guy and include a Bitcoin address and I'll send you a coin

This the config you used?
--*removed*--
Edit: nvm, figured it out, and ty!
I ended up in a serious bootloop trying my compiled kernel and I got to test my recovery image in a new setting, it worked

ros87 said:
This the config you used?
omap3621_gossamer_defconfig
Click to expand...
Click to collapse
omap3621_gossamer_evt1c_defconfig

texasice said:
also how can we get a serial or UART output from the nook touch. I have been testing some cm builds from the nook color but it doesnt boot far enough for abd to give any output. ive looked at the back of the board but there doesnt seem to be any blatantly obvious serial port connections on it like the nook color has.
Click to expand...
Click to collapse
Can't find the link but someone thought there was serial pins under/near the sd card. Here is back of NT http://www.zdnet.com/photos/crackin...6244759?seq=32&tag=photo-frame;get-photo-roto
GL with this. I need to get GPS signals into my NT so subscribed

BTW, the memory is sadly only 256MB, not 512 as written in that article,
the K4X2G323PC-8G part number is mentioned here www .samsung .com /global/business/semiconductor/support/brochures/downloads/memory/SamsungPSG_july2010_final.pdf on page 10 as
2Gb MDDR 64Mx32 K4X2G323PC-8G(1) 90-FBGA 1.8V
That explains why the device reports MemTotal: 233024 kB in /proc/meminfo :-(

texasice said:
so where do i go from here? how do i start forward porting the kernel to .32 or .35 or do i even need to do that? in general what needs to change to get a cyanogenmod compatible kernel?
Click to expand...
Click to collapse
Hi,
nice to see that someone tries to get CM to the N2E.
I'm not really familiar with the process of porting CM, but I think the next step would be trying to build a working kernel from the Nook Color CM kernel sources.
It looks like most are in the /arch/arm/configs directory where a lot of definitions for the gossamer-board are missing.
Whats also missing is the touchscreen-driver drivers/input/touchscreen/zforce.c (and the according headers/configs), and the GPU/Epaper-driver (i think it is in drivers/video/omap3ep/, headers and configs have to be added too).
A good way to see what differences between the two kernels exist, is to get the version 1.1 original source for the nookcolor (Kernel version 2.6.29, same as the N2E kernel) and make a diff. http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor_1.1.tgz
At least thats what I will try, as soon as I find some time and get my nook.

CM should be possible. As the nook color and nook touch shares the similar hardware (at least same CPU board).
But at least we need some developer to build ClockworkMod for Nook Touch so we can copy the CM build to the device.
The bad side of the CM build is... we can't use the default Nook application anymore (unless we are going to modify the CM framework).
I guess Nook Touch is just a Android device running the "Nook" launcher, which the device should only run default book software. I wonder if it's possible to put a Nook Touch default reading software shortcut to "Go Launcher"?
mali100 said:
Hi,
nice to see that someone tries to get CM to the N2E.
I'm not really familiar with the process of porting CM, but I think the next step would be trying to build a working kernel from the Nook Color CM kernel sources.
It looks like most are in the /arch/arm/configs directory where a lot of definitions for the gossamer-board are missing.
Whats also missing is the touchscreen-driver drivers/input/touchscreen/zforce.c (and the according headers/configs), and the GPU/Epaper-driver (i think it is in drivers/video/omap3ep/, headers and configs have to be added too).
A good way to see what differences between the two kernels exist, is to get the version 1.1 original source for the nookcolor (Kernel version 2.6.29, same as the N2E kernel) and make a diff. http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor_1.1.tgz
At least thats what I will try, as soon as I find some time and get my nook.
Click to expand...
Click to collapse

winstonma said:
CM should be possible. As the nook color and nook touch shares the similar hardware (at least same CPU board).
Click to expand...
Click to collapse
I described in my last post what hardware is different, and what has to be changed in the kernel. But now I think we could also try the standard Nook-Touch kernel, but we have to put all the userland files in place.
But at least we need some developer to build ClockworkMod for Nook Touch so we can copy the CM build to the device.
Click to expand...
Click to collapse
CWM-Recovery would be nice, but isn't necessary for CM. We could start with a bootable SD like it was done with CM for the Nook Color.
I guess Nook Touch is just a Android device running the "Nook" launcher, which the device should only run default book software. I wonder if it's possible to put a Nook Touch default reading software shortcut to "Go Launcher"?
Click to expand...
Click to collapse
Take a look at XorZones work http://forum.xda-developers.com/showthread.php?t=1289894

As we have the full source of Nook Touch, is it possible to get Nook Touch as Official CM port?
I have the gut feeling to follow the Nook Color: Full Update Guide and install CM. So I believe it's nice to have ClockworkMod Recovery on Nook Touch.
By the way this is the Nook Touch 1.1 Source from B&N.
I am still waiting for my Nook Touch. It'll arrive 2 weeks later.
To be honest I don't need the B&N service. I just treat this device as e-ink Android Tablet. So I really enthusiastic to make CM port as official.
Is it possible to join as a team and work together?

Is it only me thinking that undervolting this overpowered ebook, would make us get that extra inch in battery life we all (I) want?
I'll look into making this kernel overclockable when I have a bit of free time.
If someone looks into it before I do better

Now, before we go on about kernel hacking, can someone actually provide a fully working kernel compiled from sources?
I spent a few hours on it (1.1.0 sources) tonight and this is how far I got:
dmesg:
http://pastebin.com/VUv74LFV
logcat:
http://pastebin.com/cGpkAz3n
Basically it's running and I can access it, but I have some trouble with the SGX (no graphics)
This is omap3621_gossamer_evt1_defconfig btw.

Wikipedia tells me NST uses an OMAP3611, there's very little diference between the two (OMAP3621) but something must screw up the output.
http://en.wikipedia.org/wiki/Texas_Instruments_OMAP#OMAP_3
---------- Post added at 01:25 AM ---------- Previous post was at 01:19 AM ----------
Allthough our NST works at 800mhz, so maybe wiki is wrong.
Here it's reported as an OMAP3621 so forget what I said.
http://forum.xda-developers.com/showthread.php?t=1251209

eded333 said:
Wikipedia tells me NST uses an OMAP3611, there's very little diference between the two (OMAP3621) but something must screw up the output.
Click to expand...
Click to collapse
NST uses Omap3621 as I can tell you from my opened NST laying in front of me
If you need more proof:
http://www.techrepublic.com/photos/...34&tag=thumbnail-view-selector;get-photo-roto
Most likely the gossamer evt1 config is the wrong one, but the edp1 (epson digital paper) config doesn't compile at all..
Weekend and GF-time is coming up so I won't be continuing this until Sunday evening.
---------- Post added at 01:36 AM ---------- Previous post was at 01:32 AM ----------
Anyway, it's close as everything is running, including Dalvik
Will figure it out next week

f*****g wiki, they must allways have something wrong.
Good work! It'll be done when it's done but didn't expect to see so much progress in so little time

ros87 said:
Now, before we go on about kernel hacking, can someone actually provide a fully working kernel compiled from sources?
I spent a few hours on it (1.1.0 sources) tonight and this is how far I got:
dmesg:
http://pastebin.com/VUv74LFV
logcat:
http://pastebin.com/cGpkAz3n
Basically it's running and I can access it, but I have some trouble with the SGX (no graphics)
This is omap3621_gossamer_evt1_defconfig btw.
Click to expand...
Click to collapse
Hi,
building from the 1.1 source with the omap3621_gossamer_evt1_defconfig configuration works great for me. The kernel runs perfectly, no problems with the display, touchscreen or wifi. Can't notice a difference between the stock and self-built-kernel.
I used arm-eabi-4.4.0 to build it.

Great! Which means we can build CM and get official build-bot.
But back to the point. But it'll be great if we can load the new Android ROM into our device.
So back to the basic question. Should we build recovery like CWM?
Sent from my Liquid using Tapatalk

winstonma said:
Great! Which means we can build CM and get official build-bot.
Click to expand...
Click to collapse
No it doesn't! Thats just the kernel. Getting CM running is a much harder task.
So back to the basic question. Should we build recovery like CWM?
Click to expand...
Click to collapse
If you can build CWM for the N2E than please do it. I tried, but had no success.

mali100 said:
No it doesn't! Thats just the kernel. Getting CM running is a much harder task.
Click to expand...
Click to collapse
I agree that CM would be tougher than building a kernel. But there are guides. Teaching us how to grab a built CM, swap the kernel, and it boots. So we can try that. But still, we need the recovery to "install" our build.
If you can build CWM for the N2E than please do it. I tried, but had no success.
Click to expand...
Click to collapse
I know it's not easy. But we have no choice but to get this step done if we need full access (like installing custom ROM). I will start trying once I grab my N2E.

mali100 said:
Hi,
building from the 1.1 source with the omap3621_gossamer_evt1_defconfig configuration works great for me. The kernel runs perfectly, no problems with the display, touchscreen or wifi. Can't notice a difference between the stock and self-built-kernel.
I used arm-eabi-4.4.0 to build it.
Click to expand...
Click to collapse
Hi
That post got outdated quite quickly as I managed to figure it out the day after posting it.
There was no problem with my build, but there's something really important missing in the Kernel sources, kernel modules for the PowerVR graphics.
So yes, you can build that config and push the kernel to a working NST and it will work as expected, but as we don't have the source code for the modules there's a limit to what we can actually do.
From my experience there only so much you can change in the Kernel before having to recompile the modules..
To be continued..

NST-Kernel v0.1 USB-Host and Multitouch enabled (for software versions 1.1 and 1.1.2)

Hi,
after the great work from verygreen, wheilitjohnny and arkusuma I decided to build a kernel with both of their improvements included.
Features:
based on the BN kernel for the software versions 1.1 and 1.1.2
USB-Host by verygreen http://forum.xda-developers.com/showthread.php?t=1457971
Multitouch by wheilitjohnny and improved by arkusuma http://forum.xda-developers.com/showthread.php?t=1563645
Additional USB related drivers (usb-storage, usb-serial ...)
This is just the kernel, you still need to perform additional steps to get this features working, please look into the corresponding threads.
Howto install the kernel:
Download the file with the kernel and extract it, you should get a file called UImage
Use Noogie or adb to replace the uImage on the /boot partition
Reboot
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data, fried USB-Devices. Make a backup before you try anything described here!
USB-Host support is still WIP (work in progress), the battery drain is noticeable higher. If you don't plan on using the USB-devices you should use a kernel without USB-Host support.
Downloads:
NST-Kenel_v0.1_uImage.zip
github repository for the sourcecode
Thanks to:
verygreen for the USB-Host support
wheilitjohnny for the initial Multitouch support
arkusuma for the improvements to the multitouch support
Renate NST for testing

Great work! Thanks mali100!
by the way, this is the kernel for 1.1, right?
just better state that avoid asking XD
P.S.: I didn't look at the kernel for previous versions, is the kernel actually changed?

wheilitjohnny said:
Great work! Thanks mali100!
by the way, this is the kernel for 1.1, right?
just better state that avoid asking XD
Click to expand...
Click to collapse
Thanks, totally forgot to mention this. It is for 1.1 and 1.1.2
P.S.: I didn't look at the kernel for previous versions, is the kernel actually changed?
Click to expand...
Click to collapse
The kernel changed from 1.0 to 1.0.1 and also with the update to 1.1. But no changes for the last update from 1.1 to 1.1.2

mali100 said:
Hi,
after the great work from verygreen, wheilitjohnny and arkusuma I decided to build a kernel with both of their improvements included.
Features:
[*]Additional USB related drivers (usb-storage, usb-serial ...)
[/LIST]
Click to expand...
Click to collapse
Very nice! I haven't been able to make proper use of usb-serial converters yet because the permission of the created device (eg /dev/ttyUSB0) is always set to 0600 when the device is connected. From what I've read, usually an entry in ueventd.rc solves this. Unfortunately ueventd seems to be omitted from the B&N image..

How are you trying to open the device? It worked fine when I tried directly from the terminal or with this app https://play.google.com/store/apps/details?id=android_serialport_api.sample

My USB keyboard does not work with this kernel. Multi Touch works so I uploaded the file right (Noogie). It worked before with the original "USB-Host" kernel.

Just to be clear, what's the difference between:
usb-host-mt-pack_0.1.zip
&
NST-kernel_0.1_uImage.zip
?
The mt-pack update should go over the uImage or can it be applied direct?

The mt-pack includes this kernel, and all the other stuff mentioned there. It's not necessary to use both. If you want an automated way of installing multitouch and usb-host support, just use the mt-pack, if you want to do everything manually take the uImage and figure out what else you have to change.

Hi
Have anybody such kernel for nook with Glow 1.1.5?

up

pasha4ur said:
Hi
Have anybody such kernel for nook with Glow 1.1.5?
Click to expand...
Click to collapse
Hi, I'm also wondering if somebody with a Glow has already tested this?
Thanks in advance!

OK, so I'm an idiot - I've searched high-and-low, and I can't find a solid method for easily moving this kernel over to my touch. I'm building a survey tablet for a non-profit, and the e-ink screen would be awesome for them - having a multitouch keyboard even better.
Any pointers? I tried CWM SD card, and can't mount /boot, ADB doesn't show /boot.
Is it as simple as connect via adb and:
mkdir /boot
mount <some point> /boot <some flags>?
profit!
?

Code:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot

Renate NST said:
Code:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
Click to expand...
Click to collapse
Thanks, that did it. 2 years of .Net and my Linux has just about evaporated!

Hi,
I already have multitouch enabled for a long time using another tutorial.
Does yours fix the problem with the screen sometimes locking up (where you have to slide with two finger to release it again)?
Or does this version also have that problem? Thanks!

rhhd said:
Hi,
I already have multitouch enabled for a long time using another tutorial.
Does yours fix the problem with the screen sometimes locking up (where you have to slide with two finger to release it again)?
Or does this version also have that problem? Thanks!
Click to expand...
Click to collapse
It's based on the other kernel and has the same problems.