yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
I've had no yaff's problems lately.

Did you make sure to wipe your data when re-installing froyo?
[Tilt, TyTN II, MDA Vario III Android Development] vallice:
Great work l1q1d (OTTIMO DAVVERO ;))! Only one issue with the battery level. I have two opposite situations:

-when the battery is low (10%), i turn off the phone and then i remove and replace the battery after few seconds. When i turn on the battery level rises to 40-50%!

-when the phone is charging and reaches 100%, I do the same (turn off, remove and replace the battery) and when i turn on the level has dropped to 60-70%!

Kernel: VOGUIMG-320-FROYO-10-4-10

Android build: Thoughtlesskyle's Not So Super Froyo
[Tilt, TyTN II, MDA Vario III Android Development] voyteckst:
I also have problems after installing newest nbh. I even reinstalled whole system. After all, reinstalling system and wiping data helped. Now it seems to be stable.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
try with latest version
[Tilt, TyTN II, MDA Vario III Android Development] immolo:
Yes I have been wiping data also.
[Tilt, TyTN II, MDA Vario III Android Development] h4rdw4r3fr14k:
Thanks, I'll try that
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
Spoke to soon - yaffs tragedies, permentantly un-erased yaffs blocks, just after a hang (in which I couldn't get to my PC to do an adb).

I dida data backup, erase & restore and it's fine for now but if history is a guide it will do it again soon and I will get an adb logcat this time.
[Tilt, TyTN II, MDA Vario III Android Development] waterpolo:
the newest kernel (12.10.2010) have problems with adb.

I have to go back to 10.10.2010 this one is working for me.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
If some has panel 1, please contact me.
[Tilt, TyTN II, MDA Vario III Android Development] sergey1369:
Hello!

I've found out option which causes newer kernel hangs with harret.

It is "CONFIG_MSM7X00A_USE_GP_TIMER=y".

With old DG_TIMER kernel boots in 5 seconds on my TYTN II.

What's wrong with DG_TIMER. Why changed to GP_TIMER?

P.S. Here is latest haret-friendly kernel zImage. (Oct 14 17:34)
[Tilt, TyTN II, MDA Vario III Android Development] illegal2008:
2.6.25 kernel issue...

one problem for me with VOGUIMG-320-FROYO-10-1-10 2.6.25 kernel

working fine except:when listening music with BT headphones phone goes to sleep of death(no complete freez,just not responsive,sound stops)

I like stability of this kernel ,but this issue make he unusable for me.plz help ;-)

system-froyo-01-10-10_16

2.6.25 modules from n2rjt

VOGUIMG-320-FROYO-10-1-10 2.6.25

no overclocking
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
That is the debug timer which i seem to remember having issues with putting the cpu into power save mode to save battery when the phone goes to sleep. So you may notice that battery life is not as good using that configuration, although battery life won't be as good using haret anyway.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Good find!
[Tilt, TyTN II, MDA Vario III Android Development] TuoNonno:
I don't know if this is a bug, but with "VOGUIMG-320-FROYO-10-12-10.nbh" when i'm typing a message and I press the enter key on the physic keyboard, the phone send the message and don't create a new paragraph.

Other than this, with this kernel the phone is working pretty well, with the previous one I used to have a couple of hangs during the day but with this one I had only one in 3 days.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
It is program related (not a kernel issue), if you want a new line press shift and enter...
[Tilt, TyTN II, MDA Vario III Android Development] TuoNonno:
can I modify this feature in any way? cause I continue to send message that I half-wrote xD (dumb me. habits are hard to kill)
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
I think the only way is to modify the source application that deals with SMS. For example pingchat accepts enter key as a new line.
[Tilt, TyTN II, MDA Vario III Android Development] obso:
l1q1d, I see in Atools you can change the button configuration around. Is there a way to keep the menu botton where it is but make it so it doesn't unlock the phone? Right now it makes the slide unlock screen worthless because it gets pressed in my pocket (resulting in probably half my lockups when it tries to start up a million different apps)

edit: now I see that's probably a system function. That's too bad, I can't really find any information about making it stop.
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
"Use Enter to send message" option

Well I am not sure, but I have seen that setting in Messaging app, just uncheck that checkbox on "Use Enter to send message" option ;)

But I am not sure now if it depends on build.
[Tilt, TyTN II, MDA Vario III Android Development] TuoNonno:
I think that it's release related because on thoughtless's froyo I can't find that option... thank you anyway ^^
[Tilt, TyTN II, MDA Vario III Android Development] Abe87:
I can't access my micro sd card on the .32 kernels but can on the .25 kernels. I am using the HTC Tilt. Is anyone else having this problem?
[Tilt, TyTN II, MDA Vario III Android Development] obso:
I've been having frequent lockups with your newest kernel l1qu1d. How do I set permissions on kmsg to let me access it with swiFTP so I can post it here? (I really only know enough about linux filesystems to be dangerous)

Can't access it from the phone or from a computer?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
To capture kmsg after a crash

1) login using terminal emulator or adb shell

2) su

3) cp /proc/last_kmsg /sdcard/last_kmsg.log

Then you can copy it from your sd card.

L1q1d please build kernel with the fix I checked in last week. It eliminated the crashes for me.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
I'll release it tomorrow morning (at 10:00 zulu), i tested it last few days but i still have some hangs.
[Tilt, TyTN II, MDA Vario III Android Development] Abe87:
Can't access it on the phone.
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
Running now; for some reason appbrain thinks it's a different phone and shows a different app list - a bit worrying if my paid-for apps think the same thing.

[Edit]

It could be that I also upgraded to the latest froyo... however it all works fine
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
The newest kernel seems solid so far, haven't had any freezes for the last 5 hours:)
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
@-Arturo-, samjam: which screen have you got?
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
I've got panel type 2 - I think -it's the one I use

I notice that on wake, the screen re-paint is a lot faster... reminds my of when I tried a different screen type (but hung more often so I stopped)
[Tilt, TyTN II, MDA Vario III Android Development] obso:
Also running the new kernel. Smoothly so far.

Panel type is 2 (or 3). I've tried both in the past but didn't notice a difference.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
The new kernel has the new autosensing screen option, i'll add on atool autodetect in next release.
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
I,ve setup mine to panel 2 even though panel 3 also works fine for me. Also i might havejumped the gun as I fnally got my first freeze on the kernel. It happened when the google apps were synchronizing data and I opened color note app. The phone became unresponsive so I left it alone for a while and when i tried to power on the screen it showed the blank screen for about a minute then finally it changed into "dissorted" screen and froze permanently.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
On my Kaiser, auto-detect gives the wrong answer for me.

It says 2, but I am confident now that I have a 3.

The panel_type 2 takes longer to wake up, paints graffiti on my screen before it decides to refresh a clean image, and sometimes crashes.

Not really a crash (kernel panic) but instead doesn't wake from sleep, according to last_kmsg.

I am now using your latest kernel build, but panel_type=3 rather than 0 or 2.

I haven't seen a crash over several days with panel_type=3.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
i noticed that sometime the system go to sleep and doesn't wake up.

The kernel log said nothing, i think that we need to rewrite all the power management part because dzo simply copy the 2.6.29 in 2.6.35.

There are new option about long freeze to add but it's much work. Any help is appreciated.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Maybe my imagination, but this kernel seems a lot slower, like it is swapping a lot more. Is something taking up more RAM?
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
And how about panel type 1 which I have? I've seen you are asking for someone with panel 1. How can I help to improve your work?

Sent from Android on Kaiser using XDA app.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
SDCard slot broke!

My phone's sd card reader chose to stop working when I had a poorly configured kernel installed. I'll be offline for a few days at least, using my Wizard and WM6.1 until I repair or replace the Kaiser. :(
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
Try removing the battery, it may start working then.

Sam
[Tilt, TyTN II, MDA Vario III Android Development] andre_ars:
Same problem here. Everything keeps on working, but I have no image. I have to shutdown (guessing where the "OK" button is).

With the new kernel (date 10.19.10) the reset button now only shuts down the phone. :confused:

Also noticed that in image galery, if i rotate the images (in full view) the screen get fuzzy. (and only on the galery until now.)

Everything else seems to be working fine. (even the battery status). :D
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
I get the screen weirdness with (2) that you mentioned. As (3) is fine you you, I'll try that for a while.

How do we tell what was auto-detected?
[Tilt, TyTN II, MDA Vario III Android Development] waterpolo:
The camera is not working (green) on my Polaris with your latest nbh from 19-10-2010 and the latest fresh froyo from 16-10-2010. With nbh from 12-10-2010 the camera is working fine.

The battery status seems to work fine on the Polaris.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
You messed up the installation, reinstall all.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
It's quite strange, there are no changes on camera...
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
No, it's a physical problem: I can't push the SD card all the way in. I'll dismantle the phone and try to fix, but will probably need a new phone. Kaisers are cheap now, but it's still a hassle.

Regarding the problems people have been reporting, I would suggest that you try a reinstall of all. I did that just before my SD card reader broke, and all seemed very good and fast.

I still claim that the panel detection gives the wrong answer. To find the answer that it gives, look in the dmesg logs just after startup. You can also find the panel_type parameter as a file in the /proc or /sys filesystem. I can't remember where and can't find it since my phone is broken.
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
Overheated battery issue

Hey pals, I had a strange issue today...

I do not know how or how that happened, but... After some business meeting I took my phone out of the belt pocket and found it totally warm and the battery dained to the zero.

I had to take the baterry out of the phone and leave it out to calm a bit. After few minutes I started phone to WinMo that reported 1% of battery. I am still recharging after almost 3 hours in WinMo.

Anyway... few times before when my Android reported 15% of batery and I switched to WinMo it shown that my battery is dead or 1-5%

Taking battery out and putting back made it back to about 20-30%

What is going on? is it Battery driver issue or my battery just goes to hell?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
As far as I know, the board-kaiser-battery.c code is simply a battery meter. It reports the bad news but doesn't cause it. Yet, something causes it. I have seen the same thing. Maybe a runaway thread, endless looping, pegging the already overclocked CPU at 100%. (We all overclock, don't we?) Whatever causes it, it can't be good for the phone or the battery.

I've been wanting to get the battery temperature code working, so we can add a daemon that reacts to an overly hot battery, perhaps by scaling back the CPU clock.
[Tilt, TyTN II, MDA Vario III Android Development] flinx42:
I installed the 2.6.32 19/10 Kernel together with Thoughtlesskyle's Not So Super Froyo [10/17/2010] to NAND last night

No tweaking in Atools, other than to set panel 3 and hw kb type

I also setup a few apps/widgets, and configured Google+Exchange account

Took phone of charger at 8:30 this morning. Had a 1h phone call at lunch and at 17:00 it reported about 25% battery left.

Pretty good going I thought and rebooted the phone to show off the new boot animation to my son. - BAD move.

After the reboot it had lost the Google account completely and the Exchange account was only partially there (didn't show in Accounts, but mail/calendar/contacts re-filled themselves through sync despite that)

Also had a few FCs..

After a second reboot later on it became totally corrupt and started crashing back to the boot loader. Last I saw it up, it was down to 8% battery

Have now got it on charger and reinstalled the build

So to me the battery indicator seems VERY realistic now. Especially given that on older kernels I've seen it die after it saying 42% remaining ..
[Tilt, TyTN II, MDA Vario III Android Development] flinx42:
I've noticed this overheating on various kernel/build combinations over the months, but never found a common external denominator (e.g. only happens when in pocket...)

So runaway thread seems most likely to me

BTW To proof your rule: I do NOT overclock, as I think the battery life is already bad enough without that :)
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
I think this is because (as has been said) that the file systems are not properly un-mounted on shutdown.
[Tilt, TyTN II, MDA Vario III Android Development] obso:
Can you make a widget execute a shell script to use to shut the phones down? That seems like it would be a fairly straightforward fix (altho doesn't help corruption on forced shutdowns/resets)
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
My phone is working again.

I have a kernel mod that executes a script during shutdown or reboot. It totally cures my corruption, or at least the corrupton of my phones /data filesystem.

Now I am working out how to check it in nicely. Currently it is a nasty bit of code.

EDIT: I just shutdown and had massive corruption. I guess I don't have it cured yet.
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
It was mentioned by either n2rjt or l1q1d; I think one of them will just add an unmount to the shutdown scripts in the next froyo build.
[Tilt, TyTN II, MDA Vario III Android Development] thoughtlesskyle:
hey L1Q1D how hard would it be to integrate the Quiet boot from this thread into the newer kernels, we wouldnt have the linux text at the begining and the BSG makes that opening text rather pointless anyway
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
It's possible but i don't know how they did it!
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
So far I am wondering... Somethin weird happens with the battery check. It does not do that strange behaviour between Android and WM only on low battery. It is enough to launch android and reboot to wm to see it complaining about drained battery... Is there any hw check on the battey that gets reset to zero by mistake?

Sent from Android on Kaiser using XDA app.
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
And one more question... how to make android check if there is swap partition on sd and mount it automatically? There is no fstab file or other thing like that...

Sent from Android on Kaiser using XDA app.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
I suggest to use compcache with swap partition.

Edit /system/bin/compcache.sh with correct partition.
[Tilt, TyTN II, MDA Vario III Android Development] waterpolo:
The same problem for my camera on my Polaris with .32 kernel nbh 22-10-2010.

Latest .25 kernel is working fine.

Are you planned to update .25 kernel with the battery fix?
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
To be honest I think we should keep the Verbose boot mode we have until we get the kernel more stable. Every couple of boots my phone complains about a problem with IRQ26 and then I have to reboot it again and then it works. Without the verbose boot I would never know what is going wrong and it would sit there. Not to mention it looks cool and different imo. Also to deal with the corruption issue we would need to use EXT3 or 4 or some other journaling file system. I do find that having my system on nand and data on SD seems to be working nice as far as corruption goes because it scans after every force reboot.
[Tilt, TyTN II, MDA Vario III Android Development] immolo:
Journalism filesystem like EXT3 and 4 aren't designed for flash uses so would cause us far more problems in the long run if we used those.

Does anyone know why the yaffs2 scanner isn't fixing these problems like its designed to do?
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Because the problem is in nand driver and the system doesn't mount correctly the fs on shutdown.
[Tilt, TyTN II, MDA Vario III Android Development] immolo:
Oh from the reading the documentation on yaffs2 I thought the scanner was suppose to fix corruption from unclean mounts but I guess if the nand driver is still at fault it won't help.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Windows Mobile seems to set the battery meter based on voltage, temperature, and current, rather than the charge accumulator used by Android's linux kernel. When we boot from WinMo to Linux, Linux finds the charge accumulator too high by a factor of 2.2, based on my experiments. Maybe that value isn't right for all Kaisers or all batteries, and maybe it isn't even linear, but the value 2.2 works for me.

With the latest kernel, the following parameters are available:

battery_capacity: kernel reads, does not write. SHould be set to battery capacity (mAh) * 1.6 which is 2160 for a 1350 mAh battery.

haret_divisor: kernel reads, and resets to zero. If nonzero, kernel multiplies ds2746's charge register by 1000/divisor. I recommend a value of 2200 in your defaults.txt file.

set_percentage: kernel reads, resets to zero. If nonzero, kernel sets battery capacity to the specified percentage. If we ever write a utility to set the battery level, this is the parameter to change.

adjusted_capacity: kernel writes, does not read. When the kernel resets the charge based on voltage, as it does when voltage is high or too low, it also modifies this parameter. The kernel is not as smart as you are, so take this value as a suggestion, not the absolute truth.

This is what I have tried, and it worked beautifully all times except one, when my /data partition had a catastrophic failure. In the Android code, I found reboot.c, and edited the file to have this line added at the start:

system("/system/bin/rosysdata");

Then, I took l1q1d's shutdown script, extracted only the filesystem remounting logic, and created the /system/bin/rosysdata script.

I want to find a way to run a shutdown or remount script without modifying such a basic file as reboot.c.
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
That will stop file-system corruption but not file-corruption.

File system corruption is like a book with all the pages in the wrong order and coming out.

File corruption is like a book where the pages are fine but some pages only have half the data on them.

If a proper un-mount is not done, then all of the data is not written to yaffs.

The file-system can recover but the apps may not recover from their corrupt DBs
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
On fresh froyo there shutdown script wasn't call so when it shutdown there is a great mess on fs. Someone fix this, i'm working on crash.
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
I've got time today so I'll give it a go.

er... I installed the dev kit a while ago and have used it, but I don't see where to get the "repo" command from

Found it at http://source.android.com/source/git-repo.html

I'm following these instructions, http://xdaforums.com/showthread.php?t=710105 any particular build options needed? I know some people complain about missing languages and such.

... and he's off... (2.5 hours later with a make -j 4) and down at the first fence with JDK 1.6 (darn Ubuntu 10.10) and he's out of play for a while while he tracks down a sane source of JDK 1.5 for 10.10

And... with a temporary dose of hardy repo's he's got JDK1.5 and is off again
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
I release a new version of kernel. Look in git (link in my signature)
[Tilt, TyTN II, MDA Vario III Android Development] andre_ars:
Testing....

Camera Working (Crashed when changed to video mode. Video never worked for me)

GPS Working

Phone/SMS/MMS is Working

Any tests you need me to do?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Build instructions?

l1q1d, can you post build instructions for your kernel, like dzo did for Fresh Froyo? I recently added a post to that thread listing all the steps together since a lot of people were confused.

Also I wonder if we should update the Fresh Froyo repo list to include the 2.6.32 kernel branch rather than the old one.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToCompileKernel

if need merge the fresh froyo with the main branch.
[Tilt, TyTN II, MDA Vario III Android Development] obso:
Have you changed any battery stuff in the last 2 kernels? With the previous kernel my battery would never get past 75% when charging overnight. Newest kernel is topping out at 70%

I am changing the simple battery settings to 1600mah because thats what my battery says on it.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Can you send me a dmesg log?

I'd like to see where the voltage and current tops out for you.
[Tilt, TyTN II, MDA Vario III Android Development] casacristo:
battery

my battery is stuck at 93% was 95% on RLS16 & september kernel

Now with RLS17 and 22-Oct-2010 kernel

Does your image have a built-in ssh server or else how do I get a shell so I can run: (to give you the log)

dmesg | grep ds2746 > /sdcard/dmesg.log
[Tilt, TyTN II, MDA Vario III Android Development] obso:
Here you go. Not sure what part you need so here's the whole thing.
[Tilt, TyTN II, MDA Vario III Android Development] stalban:
I have a Tilt and I'm using a 2.6.25 kernel from July. How do I get an updated kernel for my Tilt? Seems the link in this thread only has Vogue kernels.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
The vogue kernel works with the kaiser,tilt,vogue and another phone. To use the vogue kernel on your tilt like I am you need to get Atools and then open up the downloaded .nbh and tick kaiser and then for keyboard choose the tilt along with whatever rom you are using and any other settings you choose.
[Tilt, TyTN II, MDA Vario III Android Development] obso:
Use the atools program from l1qu1d's sig, it'll download the newest kernel and let you make changes to it before saving it to your computer (you can also use it to convert vogue nbh's to work with kaisers if you want)
[Tilt, TyTN II, MDA Vario III Android Development] stalban:
Super, thanks guys.