yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
It keeps making a system.img which I don't want, it wont let me use my NAND.

Disregard, using my archived atools 1.0.4 worked. I have my menu again!

EDIT: After testing for awhile with multiple installs I can definately verify it is indeed faster. In a 3d rpg I downloaded that was in beta my fps went from 10-20 to 13-24 so a wee bit faster. Also the phone app is definately more responsive. As for the screen being more vibrant I think it's in your head clemsyn lol I see no difference imo. But yes, this is faster. I also installed some emulators and system utilities and even swapped launcher and have had 0 issues.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'm still getting MASSIVE data corruption with this kernel, and all I did was "Power Off" the phone using the power of function.

*EDIT* After second reboot, I now have corrupted framework and /system... I seriously do not know why I keep getting these extremely massive corruptions occuring, especially when I don't even have any problems with the OS and all I want to do is restart so I have a new LCD Density... -_-

*EDIT 2* After recovering from above, phone crashed yet again overnight, and well you guessed it, full on corruption on framework some of /system, and most of /data... I've reverted back to 2.6.25, since 2.6.32 is extremely unstable to me still and still has massive data corruption for reason I have yet to figure out... The corruption on my phone now doesn't make since... It occurs on reboots (safe or not), or when the phone comes to a screaching halt from a badly executed app, or the app just corrupts itself all by itself.

At least with my phone, on every 2.6.32 distribution I have tried now, whatever everyone's doing to the YAFFS filesystem is going backwards in terms of solving the corruption issue... O.o
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Hmm I get dozens of untracked PID errors using your kernel. I have to admit that Ihaven't used '32 kernel since November '10 so what could be a cause of those errors? I tried data on nand, ext2 partition and even data.img it still won't boot. I have all the new modules included in a build.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
What build are you using? With my barebones with a fresh install with Data on an SD image and SYS on NAND it has been running a lot faster for me with no corruption yet. Then again I have the same exact type of tilt that Clemsyn has been developing on... I almost wonder if there is some minute difference between kaisers were not noticing.
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Ok seems like the problem has been solved - strange.....I completely reinstalled the system and data and it worked. Before that I only wiped data and it didn't boot. Strange I don't get that with latest '25 kernel. Anyways it's working now....testing
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Ok good news and bad news....I definietly feel additional CPU Power it's much more responsive but for some reason I have trouble downloading from the market typical speed 5kb per 30 seconds and it never finishes downloading also the apps on Data are terribly slow to open it takes up to 20/30 seconds to open certain apps(I know it isn't due lack of processing power because I can still pull down the top bar or even exit app pressing home button..on '25 kernel when the processor was fully used I couldn't do anything) I,ve installed data on ext2 partition could that be a problem? The card is class 4.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
The card being class 4 could be why it is slow to open. If you want to see if its the card try data on NAND.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Thanks, I'll check on changing the I/O scheduler to simpler noop and see if it works better
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
@clemsyn: are you using latest initrd for your nbh?
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
JUST TO report my data got corrupted within two hours of installing new build to nand.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Ok, I'll keep an eye out for an update.

I'm back on 2.6.25 for the time being. Despite its slow responses with my keyboard, its stable and usable. :-)
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Quick question Gentlemen how do you deal with white screens? I think I remember reading something about pressing FN button or something like that to get through the white screen??? Also what causes the white screens, the '25 branch is free of that problem.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I hit Fn+ Lft-Soft Button, then Fn+Rght-Soft Button.

The '25 is free of the white screen, but for me it likes to crash while the phone is sleeping (screen will power up and show the garbled screen, and phone will lock up there)
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Not sure if it's related to the kernel and massive data corruption but somehow my phone is in a semi bricked state now while it was just sitting there. It feels like somehow it corrupted my bootloader. It's just speculation though.
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Thanks, will try that out next time I get a white screen.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I don't think so :) I'll git your bootenv and get it from there. Thanks for the updating me. BTW, if I do what toolchain do I need if I want to edit init? I remember getting a massive inird.gz (like 250mb) instead of the 2.5 mb size. LMK. Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Do you have still problems with initrd? You don't need a toolchain for compress initrd.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I got it working :) Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
Brother l1q1d, when I use 2.6.32 with modified keymap (the two soft keys for volume) I get my keyboard disabled. I am using Atools to create androidupdate.tar

If you can create a specific kernel with softkeys for volume (as like in good old 2.6.25s) or atleast create a working androidupdate on this keymap, I will be praying for ya because my phone has faulty side scrolling wheel

Thanks

P.s: my device info is, KAIS130, Panel type 1, keyboard type original HTC TyTn II
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
The keymap in atools is broken, I found the source of the problem, if you follow this link, it'll take you to a thread that explains what causes it and how to fix it, which involves modifying the querty.ko file inside the androidupdate.tar that was created by the keymapper. :)
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
I can extract the file, but how will I be able to put it back into the androidupdate.tar? since winrar only allows to extract the tar files. I am using windows XP

Edit:

Should I just add a space between HOME and WAKE words or do the Spacing too (after removing TABs ?)

Thanks alot for a quick comeback :)

Edit2:

Never mind :) I will overwrite the old file using rootexplorer
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Not a problem, had the same problem when I made my keymap. :)

Glad you got it figured out. :D
[Tilt, TyTN II, MDA Vario III Android Development] ferr2:
Hey guys,

if i compile the kernel myself, i have no data connection. i use the howto in this forum to compile the kernel.

but the good side of my kernel is that i didn't get any yaffs/fc-s for 3 days. after that i changed back to l1q1d's kernel.

l1q1d could you give a try to my yaffs settings? see screenshot. i hope this can solve our nand problems.
[Tilt, TyTN II, MDA Vario III Android Development] cycloid:
Just a quick thumbs up, was on the #63 kernel and today upgraded to the #253 .. or whatever those numbers are :)

This latest build does seem smoother, faster and prettier. But that could be a placebo from reading all the other comments. Am system on NAND, data and swap on SD card partitions.

Main thing is that since Xmas when I put the #63 kernel on I've had zero, zip, nada data corruption, despite almost daily fallovers, lockups, white screens and swapping batteries. (which I'm hoping will all be a lot less now as I think I've finally figured out that I'm panel type 3!)

Keep it up people, thanks for your efforts.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
My Android Kaiser has been eating SIM cards lately. Two SIM cards in the last month totally stopped working. In any phone I have, they say "no SIM card".

I am experimenting now, using Windows Mobile for my phone, and running my Android Kaiser with no data except WIFI. That leads me to an interesting observation.

The Android Kaiser has been rock solid stable for four days so far. No crashes of any kind, whether white screen, black screen, or anything in between. I have carried it in my pocket, with WIFI enabled, sometimes being WIFI connected all day, other times disconnected for hours at a time. I've had the phone on charger, or on battery alone. The one constant is that it is very stable without wireless data.

Is it time to look at the RIL again? I know, RIL isn't kernel, but I post the comment here because the kernel takes the blame most of the time for the crashes that we see.

Next time you get a white screen freeze or black screen death, try getting a logcat of the radio. Something interesting might be happening.
[Tilt, TyTN II, MDA Vario III Android Development] frantisek.sobota:
This is what i can confirm. Data disabled and Kaiser is rock stable.

I was also playing whit this lately.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
I can confirm this as well. With the same kernels, no matter what they are (I stay on the .25 branch) I install, sync, and I've been close to a month without problems. However if I use data a LOT (GoChat, a lot of FB or twitter) I get issues after an hour or so and I need to reset and reinstall.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
I'm going to try it.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Liq1d

I think I have better yaffs driver, it was very stable. I'll. Send it to you soon so you can compile it. I can't do it currently cozy of all the bad blocks on my phone.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
When you say yaffs driver do you mean the NAND driver? If so chuck it over to me too so i can have a look at what you've been trying :)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I meant the yaffs driver, the Nand driver I was working on somehow got better in detecting bad blocks (or it could be an err on my part) :) and is obviously not the way to go.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
No, it didn't sound too hopeful, i take it the NAND chip has had it? I made a change to the initrd the other day which clears another directory on the data partition which is used for dalvik cache. Since then, whenever data has become corrupt clearing dalvik cache in the installer menu has recovered the system and kept data mostly, so i would assume this directory is probably written to frequently so gets corrupt more often than not, or it could be an issue with dalvik that is being overlooked.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
I test that configuration and it seems quite stable (10 power cycle and many apps installed). I think that the bug is caused by the ecc:

- Nand driver doesn't handle the ecc

- yaffs create a new ecc from the data of nand driver

result:

nand corruption

with that configuration:

- Nand driver doesn't handle the ecc

- Yaffs doesn't create ecc list

- the erase chunck avoid problem (hopefully)

the bad news is: it's quite slow!

I will release tomorrow a new kernel with ipv6 and this changes (need some more testing) only for brave testers.
[Tilt, TyTN II, MDA Vario III Android Development] cycloid:
I've been thinking for a few weeks now that cell-data-connection may be related to stability. As a bit of background info i live on a hill surrounded by trees, the connection is generally only 2 bars and if it's windy/rainy the signal can drop, but whenever I have signal it's Edge. Where I work (some 20 miles away) the voice signal is *always* a full 4 bars, but G3/GPRS is non existent.... and this is where it gets really interesting. Some days I have a full data signal, other days there's no data, but on some days there's data at one end of my desk but none at the other! I noticed this before I switched to android and on my previous WiMo phone, it must be atmospheric or something.

Anyway, I have had quite a few lockups or restarts, and I've been thinking that the sheer stress of inconsistent data connections - and my attempts to use them while at work, where we have a mean firewall so I have to use my phone for email/facebook - is messing with Android. I.e. one second the phone checks the data connection and thinks all is good, the next second the data connection is gone but the phone is now attempting to sync...Other times the phone can be stubbornly convinced that there's no data connection but if I pull the battery and reboot it finds the one I know for a fact is there (because I'm somewhere else and can see the mast) as soon as it wakes up.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I do agree, the nand driver gives 10 bytes of ecc but I think yaffs gives 12 bytes of ecc. When I changed the nand driver to 12 bytes, all hell broke lose and found all kinds bad blocks. If you look closely at the nand driver, I think it has the software ecc disabled. Another way to go around this is to enable software ecc in the nand driver and let yaffs do its own ecc.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
If you are putting data on SD, I suggest you try my new kernel with Ext4 support in SD partition. I will update it soon to use barrier=1 for better data security while keeping the speed reasonable.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
i added also the support for ext4 but i need the changes to the initrd, could you please send me them?

The new changelog will be:

- ext2/ext4 support

- adb working on windows

- ipv6 support

- bluetooth modules

- nand stable

i wait for your changes on ext4.
[Tilt, TyTN II, MDA Vario III Android Development] ferr2:
hangups

Hi there,

another hint. i noticed if i have data connection enable constantly, i have to reset the phone 2-4 times/day. if the data is turned off, it can alive days.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Ril problem
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
L1q1d, pls try these yaffs2 drivers.

Here is the link for my initrd

http://rapidshare.com/files/447222591/initrd.lzma

http://rapidshare.com/files/447223644/initrd.gz

Also with this initrd, I am unable to format the third partition with ext4 via installsys. The command I used were /bin/mke2fs -F -t ext4 *** it gives "could not invalid blocks count: error
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
sure, send me also the changes of initrd.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
OK, posted it with yaffs2 drivers.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
How old is the yaffs driver, is it from an old .2x kernel?
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
You didn't solved the mke2fs problem :-)

busybox haven't the support for ext4 so we need to create mke2fs from the original sources.
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
"Googling" for yaffs2 nand ecc, I found this:

Title:NAND + YAFFS2 - bad blocks

Link:http://lists.infradead.org/pipermail/linux-mtd/2009-May/025462.html

(UC Browser)

I think that might be useful...
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
probably the nand issue is solved.

Test the latest version from here:

http://xdaforums.com/showthread.php?t=949387
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Thanks!

But I have bad news...

Lost my contacts after reboot using soft reset button.
[Tilt, TyTN II, MDA Vario III Android Development] msichal:
The main issues I have:

-sometimes can't wake from sleep

-is the backup/recovery even working? It never worked for me

-battery usage, of course.

Is the CPU frequency changed when going sleep? I think it should, maybe it should be compiled in kernel or something? Maybe a smart roguetools-like app to dynamically change the freq?
[Tilt, TyTN II, MDA Vario III Android Development] masteryoda:
is this working with ipv6?
[Tilt, TyTN II, MDA Vario III Android Development] Heiligkuh:
I think you guys may be on to something suspecting the data connection having something to do with the data corruption. I have been running Not So Super Froyo on a Kaiser for the past 4 months or so and noticed something. As with everyone else I have suffered with the corruption of the data partition on NAND every couple of days.

I switched to Clemsyn's 2.6.32.9 kernel from post 61 a couple months ago and it was better but still corrupted the data partition a little more often than I like although I learned to live with it by backing up important info regularly.

Anyway, recently I was able to get my phone to go a whole 12 days without corruption by turning off background data and disabling backup my data in privacy settings. I always disable the cellular data connection because the sim card I use does not have a data plan (company phone).

I'm thinking maybe Android is trying to do backups or send data in the background when there is no data connection and it is corrupting the data partition somehow.

It may be related to the problems we have with this kernel not wanting to wake up from standby at times and requiring a reset.

I did notice that with background data and automatic backups disabled the phone would recover from a lockup with little if any corruption. Over the 12 days it ran without corruption I would say I rebooted the phone on average twice a day due to lockups.

Before this a reboot would almost certainly mean loss of data if not total corruption of the data partition.

Anyone else notice that the Kaiser tends to lock up more on cloudy/rainy days or when you are in an area where cell coverage is poor, especially if you use GPS?

How about issues with bluetooth especially when disconnecting and re-connecting?

Does turning bluetooth on/off mess with your WiFi connection?

At any rate keep up the good work, you guys have done a great job breathing new life into the old Kaiser.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Data corruption is because of a buggy NAND driver, not because of something in Android. We know of the issue, we just don't have spare phones to break to attempt fixing the NAND driver. Also we've been working on temporary work arounds to help with data corruption (ECC checking, filesystem ECC checking, etc), but so far they've yielded minimal help because the actual NAND driver is not reading/writing data properly, even though it

thinks

it is.

As far as everything else. I believe is just coincidence, as the kernels are still buggy, and there will be crashes, so the fact that it "crashes more on cloudy/rainy days" is just superstition.

Bluetooth, at least with my kernel is because the phone sleeps it shuts EVERYTHING down including Bluetooth when it's suppose to stay on. Like I said, most of the issues we are aware of, and we are fixing them, and the only one I believe won't be fixed anytime soon is the NAND driver as it's buggy, and anytime one of us attempts to fix, we corrupt our NAND chips to the point our phone's are not even usable.
[Tilt, TyTN II, MDA Vario III Android Development] SpeedySurfer:
Didn't someone around here have a stockpile of Kaisers they could mess around with? Maybe they could donate a few?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
No, we don't have a pile of spare phones.

But, we do have a handful of smart people.

Perhaps we can identify which source files to concentrate on, do some research, and then start an online collaborative review of the source code. I don't want to blow up my NAND by trying experiments, but I'd be down to work with others to approach this problem like professional software engineers.

I'd even be willing to test-drive the resulting changes.

What source files are the heart of the problem? What NAND part do we have? What ideas have been tried or considered so far?
[Tilt, TyTN II, MDA Vario III Android Development] leona:
Rather than using our phones to test and potentially breaking them, is it possible to use a NAND simulator to run tests, like NAND Simulator or something similar so you can poke around and play without the risk of breaking things? Just a thought.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'm no expert but even with an emulator program we need the exact memory mapping of the NAND chip, which I mean we have but I myself have no idea how to decipher it.
[Tilt, TyTN II, MDA Vario III Android Development] jeimyoliveira:
good

it's good...
[Tilt, TyTN II, MDA Vario III Android Development] habysk:
I have problem with this error: Waiting for sdcard.... Formating fat or ntfs... nothing happend. I need flash kernel from PC is it possible ? :confused: :(

Thanks
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Does your SD card port work? If not I'm afraid you're out of luck because the install files require that the SD card be working in order to install.
[Tilt, TyTN II, MDA Vario III Android Development] habysk:
Yes it work, recognize if i put in sdcard. I know. :(
[Tilt, TyTN II, MDA Vario III Android Development] habysk:
I find this:

Put these two commands in the 'cmdline' section of your startup.txt and try again: msmsdcc_1bit msmsdcc_fmax=14000000

And didnt work it! :(
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Wifi problem

Wifi doesnt work on kaiser using latest kernel and donut (dzo's odexed).

Before you people ask, i've already put 2.6.25-dirty folder on /system/lib/modules

Also tried to put wlan.ko from 2.6.25-dirty folder on /system/lib/modules and /system/etc/wifi

Any clue is welcome

(Everything is installed on nand)
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Next time use the search button or i'll burn your phone!

http://xdaforums.com/showthread.php?t=848921

this is the kernel bug thread so. Before posting here

you must search
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
I'll give his phone to the nearest toddler to play with instead lol. I think they could do worse then burn it.
[Tilt, TyTN II, MDA Vario III Android Development] kgooris:
Kernel 2.6.25_voguimg-320-froyo-11-29-10.nbh does not work on kaiser

Hi,

fyi I think following

If you are using atools using the latest stable kernel it will fail starting your kaiser in android. (it downloads 2.6.25_VOGUIMG-320-FROYO-11-29-10.NBH)

You should use 2.6.25_VOGUIMG-320-FROYO-11-27-10.NBH in stead (by loading it manually in atools)

The start-up of android install will freeze @ following line:

Failed

Install module for this kernel

_

I did not change the android install. Only the kernel. (I have downloaded latest modules from the atools)

I did not find any other post related to this so I suppose I can inform everybody with this

greetz
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Look here http://xdaforums.com/showthread.php?t=848921.

You must update...
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
This I have to agree :)
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Sorry lord of lords kernel developers

Sorry sir!

I thought if it worked before and not now, this was defined as bug, considering that I only changed the kernel.

I forgot that insect must have six legs.

Whats your real name? Fidel Castro?