Develop Bugs

[DEV] cram that nand - gain space on your partitions

Modifying your nand adress space is okay, but that means that you have to modify your recovery along with the new rom each time you want to flash a new one.
What I propose is a new, flexibile approach (mainly for devs).
This is just a placeholder atm, but once I get some free time, I'll write about making compressed partitions (mainly static data) using squashfs (this has been done to a certain extent in the past for /system/lib/modules), but adding a bit of flexibility with unionfs/aufs.
The advantages are numerous, as are the uses.
For example: no need for complex apps2sd scripts!
Just mount your unionfs in /data and mount-bind that to another folder on the SD partition of your choice, and voila, apps2sd.
;]
This is of course synonymous to modifying the initrd, but a few lines of really simple script and it's done.
I have successfully tested that with /system, and have to further test with /data
I also have to test unionfs / aufs and make a choice. The ideal one without hesitation is aufs, which has practically superseeded unionfs, but there are a few stability issues involved in the 2.6.29 patches.
There are a few knowledgeable (real) devs around (dunno about any in the Hero forum though), so they probably know what I'm writing about.
You know who you are, so just drop in a post in this thread in case you you would have some ideas regarding the implementation.
n.b. I might have to rewrite that post. It's 01:40 and I'm really tired after my training and work.

placeholder and a note:
I have patched the reverse-patched kernel (desirec) for this.
I've run into trouble building the official htc-release 2.6.29 kernel with aufs.
>edit 201008181214<
I've successfully patched the tattoo 3G/Slide kernel to build a healthy Hero kernel with aufs.
It kindda hangs in the beginning, but runs just fine afterwards.
Prolly due to my OC settings.
>leak<
I am also playing around with kernel hacking, since I want to get 2.6.32 on the Hero. Epic wip.

good concept. I'm curious about performance - this would compress read/write on the fly, right? cpu resources etc, no problem there? no major lag issues in real use (startup doesn't matter much which you mentioned).
No I'm not a rom dev, but I AM a full time career developer.
by the way - I never found a workaround for the audio issue I had with your froyo rom. But it was a good project and I'm happy it's working well for you.

dkelley said:
good concept. I'm curious about performance - this would compress read/write on the fly, right? cpu resources etc, no problem there? no major lag issues in real use (startup doesn't matter much which you mentioned).
No I'm not a rom dev, but I AM a full time career developer.
by the way - I never found a workaround for the audio issue I had with your froyo rom. But it was a good project and I'm happy it's working well for you.
Click to expand...
Click to collapse
I am puzzled as well (audio issue).
You might've noticed that I'm no longer as active in the Hero forum.
I'm done with mdpi devices.
;]
In any case:
I have been working these past few days on optimising the kernel (I have based my work on the tattoo kernel) and aufs is working atm.

adwinp said:
placeholder and a note:
I have patched the reverse-patched kernel (desirec) for this.
I've run into trouble building the official htc-release 2.6.29 kernel with aufs.
Click to expand...
Click to collapse
you should use ninpo's repo, most uptodate kernel sources with a lot of fixes/patches included (http://github.com/Ninpo/kernel-hero/). aufs compilation worked at the first try.
I am also playing around with kernel hacking, since I want to get 2.6.32 on the Hero. Epic wip.
Click to expand...
Click to collapse
ninpo works with elemag on porting 2.6.34, they already made a lot in porting the board files.
btw nice idea with overlaying the file system, I think a lot of nand protected device use that already? (Desire, Wildfire..) http://forum.xda-developers.com/showthread.php?t=748025
unfortunately I have nearly no spare time to play around, but I'm very interested to see how the compressed squashfs affects cpu load and thus the overall phone performance.
found an old but still interesting thread, so even cyanogen experimented with it, maybe there are unresolved issues?
http://forum.xda-developers.com/showthread.php?t=523662
http://groups.google.com/group/andr...36603d429a/646a017892783e2b?#646a017892783e2b

As a matter of fact, Elemag PM'd me about his work.
To be frank, I am only playing around with this out of boredom, till I buy myself a hdpi device (I am waiting for the Glacier, hopefully)
;]
Thx for the links.
I can see that I was not the only one. lol
Despite a totally different approach, Maxisma's posts about a bigger data partition got me thinking, and ultimately reminded me of some work I did in the past with linux livecd's, which gave me the idea to try it on android.
To answer your question: decompressing squashfs is very fast, with little additional load/overhead (although, running a lot of running apps/widgets on our poor 528MHz/729MHz cpu in addition to a compressed system is generally a bad
idea)
I have another idea (from my linux administrating experience as well ;]) I would like to implement, but that would only work on newer devices, which have a lot of RAM.
My idea is to modify the init.rc in order to copy over the SYSTEM: partition ENTIRELY into RAM (essentially create a tmpfs mount point), do a switch_root, and let android take it from there.
This would of course also mean redefining the ANDROID_ROOT env variable to point to the new location.
A further modification would be to mount the WHOLE /system and /data into RAM (provided it fits and leaves enough for runtimes), and THEN further mount aufs in order to write to disk - or write to tmps, but, in the case of aufs, no further work is required, but in the case of tmpfs, you just have to #find all newer files than $uptime (taken from uptime, obviously), and recompress it to the original compressed fs.
That WORKS on a few linux systems I tried.
whew. a lot of ideas, but no device to test on.
;]

[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

All important basics about android

Hi friends,
This post is to share the important things,concepts related to android......
In this post, many things like roms,kernels,overclocking,undervolting,I/O shedulars,governars,RAM, swap,differnt swaps ,partitions (ext2, ext3, ext4 )are ported....
If something missing or wrong plz tell me and i will add in this post...
I hope this post will help you to improve knowledge...
So lets start....
[1] ANDROID:
Android is the linux based operating system, designed primarily for touchscreen mobile devices like smartphones and tabs..
Android is an open source and google releases the code under the Apache Licence
Following are the versions of android :::
1) 1-1.5 --- Cupcake
2) 1.6 --- Donut
3) 2.0-2.1 --- Eclair
4) 2.2-2.2.3 --- Froyo
5) 2.3-2.3.7 --- Gingerbread
6) 3.0-3.2 --- Honeycomb
7) 4.0-4.0.4 --- Ice Cream Sandwich
8) 4.1-4.2.2 --- Jelly Bean
After knowing about Android,
Lets move towards deep....
[2] Android Rooting:
Android Rooting is process of allowing users which are using Android system to attain privileged control (i.e. Root access) within Android Subsystem.
Rooting is required for more advanced and potentially dangeorous operations like deleting,modifyig system files etc..
Their are many methods for rooting our galaxy y
Most easy method i found is at the thread
http://forum.xda-developers.com/showthread.php?p=29960454
[3] ROM ::
A file containing the executable instructions (the system image ) of an Android operating system & apps is ROM (read only memory)
after rooting your phone you are free to flash any custom rom
FLASHING ROM: flashing rom means installing the system image into device's internal flash memory...
Their are many custom roms available for our galaxy y..
Cyanogenmod, BeautySense, Creeds Rom, Fusion Rom ,
Repencis ROM, Infected ROM Blazed, COD Rom , U.S.S.R, Thunder ROM , EVO-X, CHOBITSDIGITALIS ROM ,
WeUI by amal das, M.U.R, MySS, emralD, xXxxxX MIUI XxXxXx, WinterMod Evo , WP8-Monochromatic 6.0
ACCEND
Links of all these roms will get from thread:
http://forum.xda-developers.com/showthread.php?p=31329931
[4] KERNELS::
Kernels isn't something unique for android, but all O.S. i.e. Windows, Ios, Blackberry, have kernels..
Android devices uses Linux Based kernels
In simply words, the hardware and the software communicate each other by using kernels...i.e. When software needs hardware to do anything it sends that request through kernels..
Most of the things like brightness of screen, volume, is controlled by kernels...
Kernels decides minimum and maximum frequency of CPU,
Overclocking, undervolting are all done by using kernels....
Some of the kernels available for galaxy y are Savie kernel, Merruk kernel, Hells Fusion Kernel, Kuro kernel, White kernel, Repencis Kernel, Deviant kernel etc.
( their are many other kernels list of all the kernels is impossible)
[5] Governers and I/O shedulars::
For understanding both the above terms please read the following post::
http://forum.xda-developers.com/showthread.php?p=19846276
[6] Overclocking:
Android
overclocking increases the
maximum frequency (or speed)
that your CPU can run, thereby
increasing performance of your
Android smartphone or tablet.
Many kernels for our galaxy y uses overclocked frequency..
By overclocking, overall performance of phone increases, we can play hd games lag free..
Only the disadvantage of overclocking is that mobile gets heated fastly....
Most famous kernel for overclocking galaxy y is merruk kernel...
[7] Undervolting::
Kernels are used to undervolt phone...
Undervolting means force the smartphone to work at lower voltage than normal voltage..
Due to undervolting battery backup of phone increases...
After all such part.....
[8] RAM (Random Access Memory)::
It is temporary data storage that the CPU uses during calculations. The more RAM a device th more calculated results the CPU can store.
Which means less time the CPU has to do the same thing over and over again.
In other words, th CPU can check RAM to see if it has already made a particular calculation in the recent past. If it has, it can use the pre-computed results instead of wasting proccessing time in recomputing the same calculation.
In short , more RAM means more efficient the device....
[9] Swap:
swap is nothing but virtual RAM. Using swap a small portion of hard drive is set aside and used like RAM
The great guide how to increase RAM using swap file and swap partition is given here :
http://forum.xda-developers.com/showthread.php?p=26220059
ZRAM:
To know about ZRAM please click the link:
http://forum.xda-developers.com/showthread.php?p=34877656
[10] Cache:
Many times you read the word cache...so
Cache is general type of temporary and quick access data used by the system or user(third party) applications...
Or any temporary information used or created by app is cache..
[11] Dalvik cache:
This word is also read by us many times..
Dalvik is the process virtual machine (VM) in Google's Android
operating system . It is the software that runs the applications on Android devices. Dalvik is thus an integral part of Android, which is typically used
on mobile devices such as mobile phones and tablet computers
Programs are commonly written in Java and compiled to
bytecode. They are then converted from Java Virtual Machine - compatible .class files to Dalvik-compatible .dex
(Dalvik Executable) files before installation on a device. The compact Dalvik Executable format
is designed to be suitable for systems that are constrained in terms of memory and processor
speed.
[12] JIT ::
JIT stands for
"Just In Time," and we use it to
describe a Dalvik JIT compiler,
which was added to Android with
the 2.2 release. It compiles
bytecode into native machine code at runtime. Essentially it takes the code for an app, analyzes it and converts it into something that runs faster. It does all this while the application is running, and that's where the "just in time" tag comes from. The JIT compiler designed for Android also can do this with a very short "warm up"
time, meaning it doesn't take very
long to analyze the code before it
starts working. It stores information in a cache in your
phone's RAM, which means it's not an ideal solution for devices with low memory.
[13] a2sd or app to sd:
app to sd is nothing but to move the app in external storage instead if internal storage....
Some apps are used to move apps in sd card
Some of the kernels also support a2SD....
[14] Linking app to SD:
their is difference between app 2 sd and link 2 sd ...
Link 2 sd means to create a separate part in external storage by specific linux file system such that it bahaves as internal storage and then move the app to that particular memory...
Following are the mainly used file systems....i.e. Partitions...
Partitions:
ext2, ext3 and ext4 are all
filesystems created for Linux i.e. For android..
Ext2
Ext2 stands for second extended
file system. This was developed to overcome
the limitation of the original ext
file system.
Ext2 does not have journaling
feature.
On flash drives, usb drives, ext2 is
recommended, as it doesn’t need
to do the over head of journaling.
Ext3
Ext3 stands for third extended file
system. The main benefit of ext3 is that it
allows journaling. Journaling has a dedicated area in
the file system, where all the
changes are tracked. When the
system crashes, the possibility of
file system corruption is less
because of journaling. You can convert a ext2 file system
to ext3 file system directly
(without backup/restore).
Ext4
Ext4 stands for fourth extended
file system. Supports huge individual file size
and overall file system size.
You can also mount an existing
ext3 fs as ext4 fs (without having
to upgrade it).
Several other new features are
introduced in ext4: multiblock
allocation, delayed allocation,
journal checksum. fast fsck, etc. All
you need to know is that these new
features have improved the
performance and reliability of the
filesystem when compared to ext3.
In ext4, you also have the option
of turning the journaling feature
“off”.
I hope this thread helpded you if anyone wants more about something then plz post in the thread ...
If anything in the post is wrong ,missing tell me.....
Special thanks to
CarlDeanCatabay,
droidphile,
-CALIBAN666-,
manornjan2050,
Omaxe,
And all other devs........
You can press thanks if it doesn't cost you....
Sent from my GT-S5360

Reserved
Sent from my GT-S5360

Well that is some nice compilation ....
u cud make it more attractive...adding more formattings and stuff :good:

Successful ALL-F2FS CM ROM and Internal storage read/write benchmark

Due to my very wonder of F2FS performance, I finally shifted to CM again.
Doing all-f2fs on cm rom is much easier, success!
Actually I don't feel anything different in real usage yet.
I have do the F2FS internal write speed benchmark of our device on A1 SD Bench.
Can anyone do the benchmark on ext4 on A1 SD Bench to compare?
Right now i am just using an F2FS patched CM kernel without any other modification on a all-F2FS modified CM ROM.
The no real world different feeling make me want to shift back to stock, ha.
(Right now there is typhoon in HK, and I can't upload the ALL-F2FS-rom successfully. Share it later.)
EDIT:
(The rom i will keep myself use. As the benefit of using F2FS on our phone is not much. Original write speed of our phone internal memory seems to be only 1XMB/s. Using F2FS increase the write speed to~20MB. But in real world usage, you won't notice big different. So I decided not to share it.)
Wing

thank you