yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] mt1976:
YAFFS ECC for old kernel

@clemsyn and scooter1556

Is it possible to add this yaffs ecc to the old kernel 2.6.25, too?

I know you are all working on the new kernel but it would be very nice to have one really stable kernel for our kaiser now. So if it makes sense and if it is not so much work, then I would be very happy if someone add this yaffs ecc to the old kernel, too. Because it sounds really good.

Edit: And if you need someone to make tests with the old kernel and yaffs ecc, then I would do it if it is necessary.
[Tilt, TyTN II, MDA Vario III Android Development] syntax1993:
I've had one today, soft reboot when i turned on mobile data, then tried to sync phone with google account

Had another thing as well, Android not booting, got no idea how to solve this, the only way I know so far is just reinstalling the build.

When it was setting volume of 256 to 5 it started over again at snd_set device thingy, infinite loop.

Anyone's got a solution for this? The mobile data is the least of my worries, just the reboot drives me crazy.

And could anyone explain me what in the heck a Radio is? What does it do/controls?

I know where to find them and use/download them but not what they are for

Thanks a lot! Great Work Clemsyn!!!

There's a chance I'm just doing it totally wrong so don't freak out because your kernel probably is supreme.

Trying it all over again. Hoping it won't fail now, not sof ar with Wi-Fi on, the reboot cycle will come later. I'll let you guys know.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
System in on a Read only Partition unless it was called by userinit.sh to be RW. Looks like data lost still persists..i'll do some more ironing.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Yah, not sure why but system is still mounted under RW permissions, no matter which build is used.

I know the partition is mounted on a RO section, but couldn't the kernel overwrite that permission and remount it as RW?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Our default userinit.sh calls for it to mount in ro so you might want to check your userinit.sh. My device mounts /system as ro.

BTW, Here is another experimental kernel to test. Here are the changes from the previous one

1. Disabled Cache short names in RAM

2. Disabled yaffs2 block refreshing

3. Disabled yaffs2 background processing

4. Added Nand Device Support to Verify NAND page writes

Been trying to enable YAFFS to do ECC checks on tags by default but it crashes androidinstall. Anyways, I was informed by l1q1d that this is useless at the moment so I guess it's fine disabled.

This would require fresh installation of data. I dont think the data backup would work with this kernel.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'll give this kernel a test... Btw, how do I check the userinit.sh file?
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
On it, thanks :]

Question:

Why useless ?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Update. I have noticed that this kernel reboots fairly well (kernel on page 12). I installed so many apps that my phone storage is down to 5mb...I reboot a couple of times and no apps lost :)

Did a battery pull with 5mb left on phone storage...Got my first FC with 1 app, lost a couple of my widgets and 1 app lost in Launcher :( guess not too good with battery pull but pretty good with 5mb left on storage :)
[Tilt, TyTN II, MDA Vario III Android Development] Grandelama:
I tryed to break data on this last kernel in the usual ways but I couldn't, so it feels pretty stable anyway. I have more than 80mb left on storage.

And I keep it on overnight without problems-freezes and that's a difference!

With the last version I've always found the phone frozen after the night. It was freezing 5-6 times a day, black screen and not waking up. I had to pull out battery to reboot, but no data corruption after that, anyway (in almost 2 days).

I'm testing with aceoyame's 4.55 odex. No soft reboot cycles when I turn off gps with this kernel and radio on signature.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Block refreshing is a system which is meant to improve data loss in the yaffs file system. The other changes may improve stability but will also have an impact on speed, although caching short names in RAM should gain a few extra kb in ram for the price of longer search times so may be worthwhile on our devices.
[Tilt, TyTN II, MDA Vario III Android Development] Grandelama:
After 12 hours I began to have some problems, system crashed (black screen not responding to wake up command).

On reboot I had no FC but after few minutes android crashed again and again (white screen, not responding). It auto-rebooteda couple of times too. It could be data corruption, I think.

Older kernel seemed to me less incline to this kind of messed up stuff.

Before it started to give problem system seemed pretty fast, i didn't see any impact on speed with the last changes, anyway.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Flashed the new kernel yesterday afternoon. Had some close calls with near phone crash but recovered from black screen.

It is now morning and I used the naviation app to find a doctors office. First attempt app was up but GPS shut off unexpectedly and without error message. Second time running app, navigation was beautiful with no issues.

Running the Gingerbone 5.1 odexed build :-)
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Glad to hear people are using my 5.1 build. Although I wish more would use my 4.55 release lol. That build just feels much faster then 5.1 did to me.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Thanks for the update..I am currently on my 17th hour with this kernel with no issues at all but I installed it a bit different. Here is how I did my installation.

1. Install kernel

2. Install androidinstall.tar(tgz)

3. Boot up and then sync with google

4. Install all my apps

5. With everything installed, I reboot (by turning it off and restarting)

6. Then Backup Data

7. Then Restore Data (this will reformat data and install the backup)

The kernel is stable on clean reboots but not very well will resets and battery pulls. So a backup on installation is a must. The black screen you experienced was most like from the Fake Vsync. I haven't experienced Fake Vsync with this kernel+my build and I am not OC'd. BTW, more input is greatly appreciated.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
I'm trying differently. I will not install many apps. I've downloaded everything i want, made a custom androidinstall.tar based on aceoyame 5.1, flashed your kernel and ther custom tar, odexed data and system (edited odex.sh and monted system/rw), copy all odexed files to sdcard, recreate androidinstall.tar with all odexed.

I'm now installing this. Will report on issues... :)
[Tilt, TyTN II, MDA Vario III Android Development] vinny13:
Could someone upload clemsyn's latest kernel converted for the Vogue, to install on the nand properly? Atools isn't working for me (to install on nand anyways)...
[Tilt, TyTN II, MDA Vario III Android Development] Grandelama:
I repeated your procedure with data backup/restore but I lost one app in the process. I reinstalled that app and now everything seems to be working. Will test stability now.

I'm using Not so fast froyo now, no OC.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
UPdate:

On my 31st hr of testing, if I surpass the 36 hr, it would be the longest 2.6.32 for me :) Noticed my iGo is slow now but everything else seems functional (no OC'd)
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
For me this kernel seems to be much more stable compared to the one before. Lot of data losses, hangups, missing apps and widgets... And it is also much more battery hungry.

I flashed this kernel yesterday, but since now I had about 4 hangups, and had to reinstall from time to time...

What can be the cause if noone else can verify this?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I tried the first Clemsyn-posted kernel ... very good results.

I skipped the second, since I was happy as a clam.

Eventually I did have data corruption, but it was more rare than before.

Then when the kernel git was updated, I built my own and have been running that.

It is, in my opinion, not good. Corruption on bad reboots is guaranteed.

And we are not stable enough yet, so we always have bad reboots.

I will try again first and second posted kernels to see which works best for me.

I think we are on the trail of a solution, but we have not found it yet.

For reference:

Post 36 I had good success with.

Post 63 I did not try yet.

Latest kernel git was worse than post 36.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'm not sure what I'm doing wrong, but I've got massive corruption, just from the phone sitting overnight charging... I go to turn it on, and I get an FC the moment I unlock the screen, then none of the apps work, so I reboot, and almost every app in /system!! is gone. I'm not sure what's going on, but I keep seeing the kernel mounting the partition as RW, then the build mounts it back as RO... I think I'm getting corruption between the points the kernel loads up and it giving control to the build...

Usually on the second reboot onward, the kernel takes considerably longer mounting my system and data, and even getting to the build portion of booting up and showing the screen.

I'm not overclocking (stock 400MHz), no GPU overclock, everything stock. :(
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
On the first kernel, I didn't only enable the yaffs to do ecc..I also enabled something else which I think is on the second kernel. I am having the best sucess with the third kernel since I'm approaching my 36hr use of 2.6.32. BTW, the first kernel was also built in an old arm compiler (2008) so GPS never worked and reboots on wifi happens.

UPDATE:

Just got over the 36 hrs on the third kernel with no reboots, no FC. Still going strong (except for Igo is slow)
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
And would you be so kind and post that one? Cause the one I have is very unstable... At last I gues it is not my phone where the problem is.. :)

I'd really like to try...
[Tilt, TyTN II, MDA Vario III Android Development] drvitorino:
http://xdaforums.com/showthread.php?t=857550&page=7
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
Well there is the Post63 Kernel... But I was asking fot the one compiled from GIT source as the last one that seems to be stable for clemsyn...

After Post63 kernel, there is one on Page 12, which I have now, but that one is fu*ked up and clemsyn knows that, so he did a new one, but did not post...

Or at last, that is what I Thought...
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
The last one is actually in Post63. Sorry it did not work for you but it's doing great for my Tilt. It's been 42 hrs with no reboots. I am not sure if it's a build problem but I will release this kernel with my Froyo soon that I am currently using. I will restart my phone soon so I could test the new atools and try partitioning the new kernel I built (not yet released) but I am happy with the 3rd kernel on post63.

UPDATE:

Just did a manual reboot and everything was wiped out...It's like a fresh installation but my storage size is still the same. It was great running 42 hrs and it could have last longer if I didn't reboot. I guess this is were the backup is good. I will take scooter's advice in enabling block refreshing and see how it goes. For now I'll test ECC on tags and see if it goes well. I will still release this kernel with my Froyo and advise immediate backup after fresh installation.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
I haven't had any real issues but I haven't been using my phone for much either, just running meebo, sending a text message here and there and the occasional call. I did however notice that battery usage seems to be through the roof. I wonder if thats because the kernel you build doesnt include NJ2rt's battery work or if yaffs running ecc is making the cpu work a lot harder.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I didn't include nj2rt's battery work also I noticed that the kernel was set for Donut instead of Froyo...It was working great though until I reboot :) I was able to build a kernel with tags_ecc_on which enables yaffs ECC on tags. Testing it right now.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Alright, i'm not too worried as it is a test kernel after all. Was just curious if the work was included or not. But it is outstanding that we've got this far, the stability is further then it was. I would compare our progress to us having the right ingrediants now, we just need to figure out how much of them do we need.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
OK, releasing another experimental kernel..Here are the changes from the last kernel

1. Enabled yaffs ECC on tags (via init)

2. battery fix by n2jrt

3. Enabled block refreshing by yaffs (recommended by scooter)

4. Enables background processing by yaffs

5. Force chunk writes

and a few things I can't remember (must be the beer)

So far, I have enabled most of the options to protect the partition. Any recommendations will be appreciated. BTW, don't complain if it's slower than the last kernels :) Its because of all the options to make it stable. I Challenge you to make it fail :)
[Tilt, TyTN II, MDA Vario III Android Development] Grandelama:
I tried third kernel with a couple of different configurations but I have data corruption after first reboot, more than I experienced with first and second version :(

Not so super froyo, kernel with oc gpu only, tilt, screen3.

First try: install system + install all apps I needed through an androidupdate.tar I made, boot, configure, reboot, data backup, data restore, boot = data corruption (many FCs)

Second try: install system, boot, configure and install all apps through market, reboot, data backup, data restore, boot = data corruption (many FCs, first screen reasked me to touch the android to begin)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Please try a different build and see how it goes (scooter's or acoyaeme).
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I will try this new kernel when I get home. Will I be able too restore my data after applying the kernel or do I need a fresh install?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
You should be able to restore from data.

Update:

Alarm went off on my Kaiser..everything seems to be OK. Then decided to reboot...Yup..guess right.. greeted with 2 FC's...would try to tweak it a bit more..
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
My tilt literally had a stroke. Was playing Alchemy then phone crashed, pulled battery but was not greeted by FCs but instead a hot reboot loop everytime I tried to access the phone app. Rebooted 5 times, finally just said to hell with it and rebooted and cleared dalvik cache. Rebooted again, had another loop trying to make a call, then after that I turned on location (GPS), phone hot rebooted again and now on the XDA App which had an FC 2 reboots back and posting this report.

Am not using the latest kernel but the one before it that has issues.

Wow what a morning.....
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Well if it is too slow for them then they need to try my build lol. But yes, I am going to test it here shortly. Just have to send out a few emails then going to load it on my tilt.
[Tilt, TyTN II, MDA Vario III Android Development] Grandelama:
After few hours with aceoyame's 4.55, I have to say that stability is much better! I managed to do a data backup. I did some reboots and a couple of battery removal and it is still running ok.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Trying new kernel now, and one thing I've noticed is that my phone LED is reporting my Bluetooth is on, even though in Android it is shut off...

Still booting up as there is a noticable slowdown in read/write times, so will update when I can verify if it's just a glitch with the new kernel not flipping the switch in Android.

*EDIT* Upon looking at the console inside Android (Fn + Left Soft), it is CONSTANTLY doing something in regards to busybox, like showing it's help screen... Battery drain is pretty high, as instead of getting 370+ mA, but now I'm getting between -68mA and 200mA when charging through a computer's USB port. O.o Something's draining my power.

I'll continue testing and report more once I get into the build and start tinkering... Right now battery is at 31% and charging.

*EDIT 2* Any updates on converting the mounting permissions for /system from RW to RO?
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
That's because the files in /system/xbin/ are supposed to be links to /bin/busybox, but instead they are normal files with 'busybox' written.

Everytime we run, for example, zcat, if its a link, busybox is run, it detetects which link is calling it, and runs the apropriate routine. Because they're not links, it displays the help.

If you run /bin/busybox, you get the same result :)

@aceoyame:

I've fixed this in your latest release, its rather simple, could you please launch 5.2 ?? :D
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Do you have an androidupdate file prepared, cause it's really dogging my kaiser down everytime it runs busybox like that. :(
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
i'll try and make one

please wait.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Not a problem.

Also I found a parameter under /sys/modules/pm, that controls the CPU clock when the android OS is idling... Yet when I look at the parameter, it's disabled?

Is there anyway I can modify the parameter in a NAND installation, at least temporarily? Or if anyone has a HaRET installation care to test this out for battery life?
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Perhaps its compiled not as a module. I noticed we don't have cpu scaling enabled on the kernel. Perhaps our MSM doesn't support it (ence, ondemanD is not running).

I don't know what it does, googleing might be usefull.

As for the androidupdate.tar, this is not kernel related.

I'll post on the Gingerbones thread.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
After doing some quick googling, I found that the Qualcomm MSM-7200 (which is the Kaiser's CPU), supports dynamic processor speed scaling, AND Intel's XScale technology. Now why it's not enabled is the question.

Plus the processor which is the exact same as my Palm Treo (albit MSM-7201), can be clocked up to 528MHz, and run fine (as most people are running now anyways).

My Palm Treo Pro's 7201 processor is downclocked to 400MHz but is designed to run at 528MHz.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Even among the 7200... there are differences, example, 7200a

Yet, perhaps the scaling is not benefical, perhaps it creates other issues. Dunno.

Liquid or Clemsyn could probably answer this one.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Well I just attempted to adjust the idle_sleep_mode, which is apparently disabled (set to -1), and I was presented with a full on freeze on my phone, so I'm guessing the module that controls the cpu scaling is not present. I am making adjustments to the sleep_mode as it's set to 1, and will set it to 0 and see how much power I save at that setting.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Uhm... you're not from the time of Haret only and the cupcake...

pm.sleep_mode

The mode used when the phone is in standby

[edit] Values

* 0 - Power Collapse Suspend

* 1 - Power Collapse - __Provides best power savings__

* 2 - Apps Sleep

* 3 - Slow Clock and Wait for Interrupt (default)

* 4 - Wait for Interrupt
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Well if anyone's interested in improving the power management functionality of the Kaiser, I found a what I believe to be a module for the 2.6.32 kernel for the Qualcomm PM7500 chip, maybe it'll give some insight on improving power management and battery time.

If this has been presented before, my mistake. :P
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Xscale isn't really a technology but intel's old line of ARM cpu's. Now what they did bring was wireless MMX as well as the integer instructions from SSE. If we have that enabled that should help a lot. That is what the Omnia did for its 3D driver was use an SSE optimized driver. So yeah, that brings a big boost to performance which may bring us up to par if we have it disabled.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Something is amiss. If intel only brought INT instructions from SSE, then they should have no effect on 3D. 3D is mostly floating point. The 'software acceleration' or CPU acceleration must come from somewhere else.

Anyhow, i saw the module source. Its a bunch of enums and GPIOs... don't know if we don't have that already, or if it would be profitable to incorporate into our kernel. Perhaps Liquid an Clemsyn can provide more info... i'm clueless. i can't even compile my own kernel yet :D
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I wasn't quite sure what I was looking at either, but I saw references to clock idling, which is something we need while we're using the phone, cause as it stands the CPU runs at full speed regardless of what the build is doing (sitting at the home screen, or just responding to SMS messages).

If clock idling can be implemented, then it'll solve the most troublesome problem we've had with Android on TyTN II .... battery life.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Well it was full mmx + integer SSE. MMX could definately be used to quicken rendering functions but I believe the biggest advantage for us... if we have those instruction sets. That we would get 128 bit registers available for use from SSE. Not to mention I think most of android uses integer instructions besides the floating point ones used for 3D. Anyone check what our cpu supports officially?
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Details are scarse... I wouldn't even know how to implement that module on the kernel, or make it use it. I've seen the settings for scaling, namely ondemanD, which i've seen working on XDAndroid running on a Diamond. It actually scaled from 128 to 528 on demand. Very effective. Of course... no one is saying it will run well on our qualcomm.

OFFTOPIC:

Has anyone been greeted by this while compiling the kernel ?

Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gz
CC arch/arm/boot/compressed/misc.o
AS arch/arm/boot/compressed/piggy.o
LD arch/arm/boot/compressed/vmlinux
arm-none-linux-gnueabi-ld: cannot find libgcc.a: No such file or directory
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Hi, did you use the latest arm compiler (2010)? Also did you export PATH before building the kernel? Hope this helps.
[Tilt, TyTN II, MDA Vario III Android Development] object3d:
Page12 kernel

Hello

Just thought I should give my feedback on Clemsyn's page 12 kernel. I am on the forth day of using this with Barebones build with number of apps that I use like K9 and others. My battery is 2800 mAH.

To my very utter surprise, I am amazed by the behavior. It is just too stable and not even one restart. Single battery recharged easily lasted for 2 days with Wifi and gprs used at regular intervals.

Everything just seems to be going great with this combination. Btw no OC so it's amazing stuff really!

Thanks Clemsyn.