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)

[Kernel] -fox Vanilla (ext4) for XDAndroid devices

This kernel is based upon the current git tree for 2.6.27 with minor tweaks included, such as ext4. This is suitable for all devices and should work as well as the autobuild. Please note this isn't an autobuild, so there might be a slight delay between a commit and an update to this thread. Also I do not intend to deviate much from the autobuild other than the changes mentioned below, so if you really need a feature, please include a compelling reason why it should be done.
You will need a new 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.
Commit 1348 (8/20): http://db.tt/UnLHCuR
Older version: Commit 1346 (8/16): http://db.tt/RhUlSDd
Changes:
Support for ext4 (You must use a rootfs dated 8/16 or later, and have the option ext4dev in your startup.txt cmdline)
Deadline I/O scheduler as default
Sleepmode 1 set by default (No longer needs pm.sleepmode=1 in your startup.txt cmdline)
Ondemand CPU governor minfreq lowered to 112MHz
Powersave and Conservative CPU governor added
Netfilter Redirect added as module
RNDIS set as default for tethering
Swap notifier patch for compcache included and enabled
Most of these changes are in .config, and can be verified by looking at /proc/config.gz in your running kernel. The swap notifier patch allows compcache to skip certain operations, which should improve performance if you do use ramzswap. Ext4 is still considered experimental in the .27 tree, but has been updated with Ted T'so's backport patches in his ext4 git.
Please again note the following on ext4 support:
1) You must use a rootfs dated 8/16 or later for the proper support
2) You must use my kernel, as it is the only one with the required support compiled.
3) You must have the cmdline option "ext4dev" inside your startup.txt. Otherwise it will still continue on using ext2 data.img.
4) Using ext4 will create a brand new file called data.ext4. This is intentional, as I did not want to have the same file (data.img) with different format to confuse the matter further. This also means that none of your existing app/setting will be preserved. Be sure to back up your data & app with something like Titanium Backup, and have at least 500MB free on your SD card so that the system can create a new store.
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
ti wlan git clone'ed from git://android.git.kernel.org/platform/system/wlan/ti.git
.config used to compile available from within /proc/config.gz
-- Starfox

Just loaded this one up and found something very odd... my ts-calibration was all off... Booted back into WM and deleted and re-calibrated... Still seeing the same issue...
Not sure why a module would do that but just thought I would let you know...
I went back to your 8/15 and 8/16 test kernel and could not even use the slide lock... This one is really wierd... Going to delete my data.ext4 and see if I can resolve that way...
Thanks for all the hard work you've been putting in to come up with these kernels...
Edit: Just saw the update on this page... Thanks...

Sorry about having to pull the file, I've recompiled the whole thing using gcc-4.4 and the touchscreen seems normal again. For those who may have downloaded the first file, please download it again, even if you don't have issues. The correct filesize for the new version is 2460710 bytes.
For the technical-mined out there, the first attempt was compiled using arm-linux-gnueabi-gcc 4.5.2-8 under Ubuntu 11.04 amd64. Certain versions of compiler may introduce bugs where it might over-optimize certain things, and to complicate things, we are trying to make it run under a different architecture. That can introduce unforseen bugs due to endianess, data size differences, etc. that would otherwise not happen. Cross-compiling is a voodoo art at best, and the kernel source tree expands to ~900MB including all the intermediate files produced during the build process.
If you have a Ubuntu 11.04 machine and would like to help me determine if it was actually a cross-compile bug, send me a PM and I'll try to walk you through setting up the build environment and compiling the kernel. Since the bug popped up with the touchscreen, it will be relatively easy to confirm whether the compiler was responsible.
-- Starfox

Hmm - I must be missing something.
It says:
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/loop0 is mounted.
EXT3-fs (loop0): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (loop0): error: couldn't mount because of unsupported optional features (240)
MILFS: Can't find milfs on dev loop0
mount: mounting /dev/block/loop0 on /dev failed: Invalid argument
Failed
Failed to mount /data (/sdcard/)
Anything I'm missing - I've triple checked all the instructions.
* RHOD100 UK
* Running on SD Card with new Haret and amended Startup.txt

What exactly is in your startup.txt cmdline, and which rootfs are you using?
-- Starfox

Right. So, I went back to the Commit 1346 (8/16) and that went away.
Now I'm getting "ignored duplicate definition of service" and the "request_suspend_state" loops... it might be due to the new Class 10 SD that I'm using for this testing - Going to find an old Class 2 and try again.
FYI - the startup.txt command line is
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave pm.sleep_mode=1 hw3d.force=1 acpuclock.oc_freq_khz=716800 ext4dev physkeyboard=rhod100_uk-b4HOME"
rootfs is rootfs-20110816-7e04198.zip

StarFox,
Loading this kernel now to test it out... I've been running your 8/16 test kernel for over two days with only the wifi being a problem. The LEDs have working great!
I'll let you know how this kernel goes... Hopefully better than the Cross-Compiled on I grabbed... LOL

StarFox,
Ran with this kernel through yesterday and into this morning... It all seems stable... However, I did notice longer than normal GPS signal acquisition times. When I was running the 1340 kernel I noticed this too. When I went to your Test 8/16 kernel I was getting a lock much quicker. Going to go back to the 8/16 test kernel to verify this.
Thanks...

bughunt said:
Now I'm getting "ignored duplicate definition of service" and the "request_suspend_state" loops... it might be due to the new Class 10 SD that I'm using for this testing - Going to find an old Class 2 and try again.
FYI - the startup.txt command line is
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave pm.sleep_mode=1 hw3d.force=1 acpuclock.oc_freq_khz=716800 ext4dev physkeyboard=rhod100_uk-b4HOME"
Click to expand...
Click to collapse
Okay, first, you're running a class 10 card with 1-bit and 14Mhz freq. Take these ones out: force_cdma=0 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave hw3d.force=1
You can take this one out if running my kernel:
pm.sleep_mode=1
How old is this startup.txt? These are values that have not been used for a while.
-- Starfox

Update to build 1348, the new liblights will require you to have it bindmounted.
I'd appreciate if people would post different machines this has successfully worked on. I know it works on Rhodium, looking for Diamond/Raphael/users. Thanks.
-- Starfox

Starfox said:
Okay, first, you're running a class 10 card with 1-bit and 14Mhz freq. Take these ones out: force_cdma=0 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave hw3d.force=1
You can take this one out if running my kernel:
pm.sleep_mode=1
How old is this startup.txt? These are values that have not been used for a while.
-- Starfox
Click to expand...
Click to collapse
Right - that's fixed. It now boots up and seems a bit more snappy than before.

do you have to format a partition off of your sd card to ext4 before using this?

AkumaX said:
do you have to format a partition off of your sd card to ext4 before using this?
Click to expand...
Click to collapse
Nope, it will create a data.ext4 file that is the data.img, but in ext4 instead of 2.

My Rhodium is rebooting when I turn on Wifi. Radio is 3.44.25.27 running GBX0A (11.3.2011).

bughunt said:
My Rhodium is rebooting when I turn on Wifi. Radio is 3.44.25.27 running GBX0A (11.3.2011).
Click to expand...
Click to collapse
Rebooting to WinMo?
Have you tried on FRX07?
Which RHOD? I'd guess 100 from your carrier.
Edit - logs would be helpful, if you have any. On a reboot to WinMo, /data/system/dropbox logs are the only option (other than ramconsole)

arrrghhh said:
Nope, it will create a data.ext4 file that is the data.img, but in ext4 instead of 2.
Click to expand...
Click to collapse
cool, i'll try out this testing when i figure out where all my microsd cards went...

Move Panel to PLL2 and add 1056MHz Option. If you don´t know how? then ask me
EDIT: What about editing Neopeeks CWM recovery to change Data.ext4 to a real ext4 partition?

BlackRainX said:
Move Panel to PLL2 and add 1056MHz Option. If you don´t know how? then ask me
EDIT: What about editing Neopeeks CWM recovery to change Data.ext4 to a real ext4 partition?
Click to expand...
Click to collapse
You'll have to explain the panel one to me, but not sure what the 1056MHz option would do for this kernel.
Also, this is xdandroid kernel, not CWM. And data.ext4 is a real ext4 partition. It's only ext4dev because .27 was before ext4 was "official".
-- Starfox

BlackRainX said:
Move Panel to PLL2 and add 1056MHz Option. If you don´t know how? then ask me
EDIT: What about editing Neopeeks CWM recovery to change Data.ext4 to a real ext4 partition?
Click to expand...
Click to collapse
Blackra1n,to have a partition in cwm as ext4 you just need to change a few things in rootfs
Starfox said:
You'll have to explain the panel one to me, but not sure what the 1056MHz option would do for this kernel.
Also, this is xdandroid kernel, not CWM. And data.ext4 is a real ext4 partition. It's only ext4dev because .27 was before ext4 was "official".
-- Starfox
Click to expand...
Click to collapse
Panel if run from pll1 gets weird with gpu overclocked,so Blackra1n moved the panel to pll2,from what user reported the panel works well now and there's more speed,if you need more infos,pm me or blackra1n(I'm on #xdandroid in the afternoons)
More infos here

Please describe how panel gets "weird", because this is the first time I've heard of it. Rhodium by default runs at 960mhz pll from what I've seen. And there seems to be no way to conclusively test what freq a pll runs at - from a quick glance of the thread mentioned I saw some "tests" of factors other than a simple freq change - ie, I saw mention of JIT being enabled for the "overclocked" one, which does not help.
-- Starfox

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.

[APP] LagFix (fstrim) v1.5.1 2013.03.04

THIS APP REQUIRES ROOT!
READ FAQ! Read that FAQ BEFORE you try app!
Premium version is now ON SALE! -50% off of the price! Enjoy!
Some Android users suffer from poor performance after some days/weeks of heavy usage. This is due to a well-known TRIM bug affecting these devices (there are reports that some Galaxy Nexus devices also have affected memory chips). Users with -discard mount option are NOT affected!
The source of the problem is that internal storage is not properly TRIMmed when needed. You can find lots of information on XDA - http://forum.xda-developers.com/showthread.php?t=1971852 and http://forum.xda-developers.com/showthread.php?t=1929021 for example. It is also well-known fact that running fstrim Linux tool from time to time fixes the issue until internal memory runs out of free blocks. Other solutions like mounting with -discard or disabling fsync may be slow or dangerous.
LagFix is a user-friendly implementation of fstrim utility. It allows you to select which partitions to trim (you should leave defaults unless you know what you are doing) and run the process easily.
Please note that fstrim output depends on kernel and device. It works fine unless you see errors. You might see big amounts of bytes, zero amount or repeating amount. All are fine! Read fstrim manual to understand why all these outputs are valid.
It is also advised to reboot your device after the TRIM process so that kernel could reinitialize block data.
There are two versions of LagFix:
Premium version (v1.5.1) - no ads + ability to auto-run trimming on specified schedule. The best choise!
Free version (v1.5.1) - trims your memory with one click, has ads, no schedule.
Warning! Premium version comes from different publisher! This is because Google does not allow to publish paid apps from my country. Send your rage to Google Both versions are legit, don't worry.
Release notes:
v1.5.1
+ Added CWM SuperUser support;
+ Added android.permission.ACCESS_SUPERUSER permission;
* Fixed disabling scheduler;
+ New notification icons.
v1.5
Full rewrite, dropped RootTools lib, made my own. No more problems!
v1.4
+ Device compatability detection is now completely reworked
* Fixed a crash
Earlier changelogs:
v1.3
+ New UI
+ Added Info screen
+ Added device compatability detection (looks like it should be improved further)
+ Renamed Donate version to Premium
* Fixed scheduling dissappear after reboot (Premium version)
* Some other bug fixes
v1.2 premium
* Added auto-trim functionality which runs on specified schedule. Click Schedule button and you'll see the options. Setup the way you want and click Install. The button will change to Uninstall to remove auto-trim if needed.
* Added detection if your device supports TRIM - run it once and you will know.
* Fixed some bugs.
v1.1
* Fixed chmod not working on some custom Sense ROMs.
* Added Android 2.2+ support.
* Fixed crashes.
* App is now multi-threaded.
* Updated UI a bit.
* New icon.
* App is renamed.
P.S. If your ROM mounts /data with -discard then this app is NOT needed!
P.P.S. Free version is now attached for those, who do not have market for some reasons.

Excellent!
Thanks for this. only a day ago i pushed a load of music to my OneX and have been suffering ever since.
I'll give this a go and report back!
To be clear, should I now be able to fill the phone storage to almost capacity with this running? (not currently possible as it just slows down and heats up, draining the battery)
update: enabled the defaults and it said it was successful with some large numbers trimmed. rebooting now

zombiefly said:
To be clear, should I now be able to fill the phone storage to almost capacity with this running? (not currently possible as it just slows down and heats up, draining the battery)
Click to expand...
Click to collapse
You run this app every time your device becomes SLOW AS HELL. It does not work in background since it would impact performance. Previously I used backup/restore solution once a week to fix lags. So in my case I will now run this app once a week.

Wow, just used this on my gnex, and all I can say is: thanks!
I was originally running with the discard Mount option, but it turns out it wasn't doing anything as your app trimmed a quite big number. (I have since removed said Mount option)
Also, I used to have issues with an app that set settings on boot not actually doing so, but after this app it works again. And my phone feels snappy again.
Thanks for this app.
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
Wow, just used this on my gnex, and all I can say is: thanks!
I was originally running with the discard Mount option, but it turns out it wasn't doing anything as your app trimmed a quite big number. (I have since removed said Mount option)
Also, I used to have issues with an app that set settings on boot not actually doing so, but after this app it works again. And my phone feels snappy again.
Thanks for this app.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm glad my app helped! May I ask to do me a favour and rate app in Play Store? That would be nice

AuxLV said:
You run this app every time your device becomes SLOW AS HELL. It does not work in background since it would impact performance. Previously I used backup/restore solution once a week to fix lags. So in my case I will now run this app once a week.
Click to expand...
Click to collapse
thanks. This is brilliant
the problems i talked of in my earlier post appear to have gone now after running Lagfix. My Phone is back to it's usual speed.
I was also using the emergency restore rom image method, glad I don't have to do that anymore, was a major pain.
I was looking into an app i use called settings profiles as I wanted to run lagfix after every usb dismount, unfortunately it doesn't support running applications, which is a shame. Is there any other way of hooking this in to run automatically after (un)mounting as a usb drive?

zombiefly said:
I was looking into an app i use called settings profiles as I wanted to run lagfix after every usb dismount, unfortunately it doesn't support running applications, which is a shame. Is there any other way of hooking this in to run automatically after (un)mounting as a usb drive?
Click to expand...
Click to collapse
LagFix trims /data partition, it has nothing to do with /sdcard which is mounted/unmounted. I will add scheduler in the future releases.

i'll give this a try on Nexus 4 since it's affected too by the slow down write performance if free space left less than 4GB. well done and thanks for keeping it free!

chrone said:
i'll give this a try on Nexus 4 since it's affected too by the slow down write performance if free space left less than 4GB.
Click to expand...
Click to collapse
I hope to hear your report if it will help in Nexus 4 case since I dont have one to test myself.

works great! :good:

Hey,
Work great on Nexus 10 AOKP
But not work on HOX on Renovate rom with Trip Kernel. I think Sense kernel is the probleme or other.Root acces is OK
# fstrim -v /data
sh: <stdin>[32] : /data/data/com.grilledmonkey.lagfix/files/fstrim : can't execute : Permission denied
# fstrim -v / cache
sh: <stdin>[35] : /data/data/com.grilledmonkey.lagfix/files/fstrim : can't execute : Permission denied
Thanks for your work

AuxLV said:
I hope to hear your report if it will help in Nexus 4 case since I dont have one to test myself.
Click to expand...
Click to collapse
Just updated my post above. It works! I chose all /system, /data, and forgot the other partition.
Much appreciated dude!! :good::good:
Care to adding fstrim for Nexus devices to your app name?

Doesn't work on Bindroid Sense 4+ ROM. Access denied and doesn't ask for root acces.

AlexNne said:
Hey,
Work great on Nexus 10 AOKP
But not work on HOX on Renovate rom with Trip Kernel. I think Sense kernel is the probleme or other.
# fstrim -v /data
sh: <stdin>[32] : /data/data/com.grilledmonkey.lagfix/files/fstrim : can't execute : Permission denied
# fstrim -v / cache
sh: <stdin>[35] : /data/data/com.grilledmonkey.lagfix/files/fstrim : can't execute : Permission denied
Thanks for your work
Click to expand...
Click to collapse
Thanks for report, looks like chmod was not executed successfully. I'll look into this issue and add a fix in next version.
You can try to fix it manually if you are familiar with Linux console:
Code:
# su
# chmod 777 /data/data/com.grilledmonkey.lagfix/files/fstrim

Kroutnuk said:
Doesn't work on Bindroid Sense 4+ ROM. Access denied and doesn't ask for root acces.
Click to expand...
Click to collapse
Does not ask for root? This is very strange... I'll look into it too. Sorry for such problem - I don't have Sense ROM so I couldn't test...

AuxLV said:
Thanks for report, looks like chmod was not executed successfully. I'll look into this issue and add a fix in next version.
You can try to fix it manually if you are familiar with Linux console:
Code:
# su
# chmod 777 /data/data/com.grilledmonkey.lagfix/files/fstrim
Click to expand...
Click to collapse
Thanks !
I forgot the chmod
Fix manually with terminal emulator with chmod 777 and is OK.
Renovate Rom with Trip kernel 002 and Sense + are OK for fstrim

Nexus 4 16GB Storage Performance Over Time & TRIM
Before and after filling up the storage (coming from 5GB and filling it up to 1.2GB space available):
SW from 10 MBps to 4 MBps ~ 60% loss
RW from 1 MBps to 0.39 MBps ~ 61% loss
Did a reboot and the performance is getting better (1.2GB space available, deleted some files left with 2.2GB space available but the performance is more less the same):
SW from 4 MBps to 9.89 MBps ~ 147% gain
RW from 0.39 MBps to 0.51 MBps ~ 31% gain
Using the fstrim app (LagFix for Nexus 7 and HTC One X) and reboot (2.2GB space available):
SW from 9.89 MBps to 9.9 MBps ~ 0.1% gain
RW from 0.51 MBps to 1.07 MBps ~ 110% gain
:good::good:
i see a future request is in order, daily/weekly midnight crontab?

Odp: [APP] LagFix for Nexus 7 & HTC One X
Looks like it works on OrDroid 12.5.1, which is Sense Rom, no errors...
Wysyłane z mojego HTC One X za pomocą Tapatalk 2

It's working on ViperX JB, which is a sense based rom. It brings some smoothness, or Its a placebo effect, Im not sure )

tried it manually and then the app and now it worked i tried and in antutu the I/O is still at 896....and i get only 12828 points in antutu :/ ...hm i try it again with the trimming...