yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] mt1976:
Hi,

first the combination on my Kaiser with kernel "kaisimg-panel2-240x320-2.6.32-tilt-froyo-27-08-10_23.nbh", the new "wlan.ko" and the "system-froyo-26-08-10_12.tar" seems to work well (nand). Market, calls, sms, GPS and camera works well, too. And with the new kernel and the system-froyo-26-08-10_12.tar I have really more free ram and it is a little bit faster I think. Also the power consumption is very good with the new kernel. I loose only 3% in 8 hours during the night and I think this is a good result.

Now I found one small problem, but I am not sure if it is a kernel problem or it belongs to the system-froyo-26-08-10_12.tar:

I use the kaiser to play my mp3s with the music player. With the incubus RLS12 and the older kernel "kaisimg-panel2-320-tilt-froyo-26-07-10.nbh" I had no problems with the player and even after killing the process music player.

But with the new kernel "kaisimg-panel2-240x320-2.6.32-tilt-froyo-27-08-10_23.nbh" and the latest "fresh froyo" I have found a bug:

When I stop playing mp3s in the player and I leave the player, then it stops playing music but the player is already in the ram. But when I kill the process with a task killer later to get more free ram, then it starts playing again in about 5 sec after killing the process music player. It doesn't show the play symbol in the status bar, but it starts playing again. I think it reloads the process music player and starts playing again, when the process would get killed by a task killer.

But when I stop playing the music player and set the music player to "ignore" in the task killer, then the player will be already in the ram and it does not play again after a few sec. So I set the music player to "ignore" in the task killer app and then I have only less free ram but it does only start playing music again when I press play in the music player again. I never had this problem with an older kernel and older release.

But overall the new kernel in combination with the system-froyo-26-08-10_12.tar is fantastic and works well, fast and stable. I am happy with it.
[Touch CDMA Android Development] VladbIka:
Amm... Sorry guys for my nooby! But what have i to do for WiFi working on my Kaiser with FreshFroyo???? It write just Error when i'm turning wifi on.

:rolleyes:

I Think that I have to do something with wlan.ko but i haaven't this file and I don't know what have i do with it :-D
[Touch CDMA Android Development] SuperJMN:
Hi! You should download this file:*

http://xdaforums.com/attachment.php?attachmentid=389254&d=1282909102

It goes into a folder called /system/lib/modules. Since you need to copy it to the file system in NAND, you will have to put it into read/write mode, copy the file and set it to read-only mode. I could do it in the past executing "rwsystem" (read/write) and "rdonlysystem", or something like that. Don't pay me much attention. I don't really use this method. The one I use is to modify the installation of Froyo (.tar or .tgz) and I put the wlan.ko in the required directory. Then, I execute the installation and it's done.

I hope you do it right! :) If somebody knows a better method to manage files in read/write mode to NAND, please, shout here!
[Touch CDMA Android Development] VladbIka:
Thank you man! I had just put it into androidinstall.tgz/system/lib/modules than I reinstalled Froyo, and Yahoo!! It works :)

Thank u very much!!!

Thank DZO for this great build! It works nice! Very fast and stable!
[Touch CDMA Android Development] alinescoo:
How can I reduce the number of home screens ? I can't find anywhere ADW.Laucher settings.

Also, my lock screen, when I press power button looks turned around, the writing is like "egnarO" insead of "Orange". ?
[Touch CDMA Android Development] 79bass:
Hi,

First of all I'm really impressed with latest Fresh Froyo build + last 2.6.32 kernel!

I had any problems with this build... unless I can't record video (never needed.. but we never know :P).

This is by far the smoothest and working build I have ever tried (Better than *Donut or *Eclair), I have almost 50 Mb of memory free with the new kernel...

Anyway... I'm addicted to benchmarks and taking score. I use Linpack and Quadrant standard mostly.

I was happy also with CyanogenMod Port too (RLS5.2) with JIT and Compcache enabled.

With CM and Quadrant standard My kaiser had always score around 340/360...was better than a Motorola Droid and quite like an Xperia X10i. With Fresh Froyo I have always around 220..like an HTC Magic :P, And I've enabled JIT.

Now I know benchmark score is a thing and full/better working is another, I'm not complaining (I'll not go with CM because perform better), but I just wandering if only compcache was able to do this difference, or I haven't enable correctly JIT (I added the line dalvik.vm.execution-mode=int:jit at the bottom of build.prop), or some other improvements in the CM build that we don't have in fresh froyo...

I'm running a kaiser overclocked to 500 Mhz :)

Thanks
[Touch CDMA Android Development] dertester123:
Hey i want to try that. But i dont know how to repack as tgz... Is there a good windows tool? Or what is the command in linux, i could try a virtualmachine for this..
[Touch CDMA Android Development] alinescoo:
To be honest I just did this with Total Commander. Just download the shareware version, in one panel hav the wlan file and in another enter in archive (it supports natively this) and just copy the file in syste/lib/modules. Total Commander takes care of packing it.
[Touch CDMA Android Development] dertester123:
Haha ^^ had to laugh ^^

Total commander can do this? Crazy.. i love this tool, so simple - so good...

It works now thanks!!!!
[Touch CDMA Android Development] VladbIka:
in linux it's in terminal "tar xvf androidinstall.tgz"

in ubuntu u can just open it in archive manager!

than u can pack it to .tar.gz

and just rename to .tgz

it's easy! i'm noob, but i did it ;)
[Touch CDMA Android Development] liquidninja:
Incorrect system time

I have a vogue on Sprint using the latest NBH and build and I'm seeing an issue with the clock where it is consistently faster than the actual time.

Periodically it will resync with Sprint's network (im assuming) as it will correct itself, but for the majority of the time its incorrect.

Is anyone else seeing this?

Thanks
[Touch CDMA Android Development] lerxst_x:
Yes, I'm seeing this with a Kaiser on T-Mobile. I'm using clocksync to sync time via ntp to mitigate this problem.
[Touch CDMA Android Development] dertester123:
Had issues with previous builds too. Sometime clock is totally wrong...

I think setting the time by myself without network worked.
[Touch CDMA Android Development] liquidninja:
Thanks buddy, that helps fix the problem for now.

Hopefully this will be solved in the next revision of the ROM though.
[Touch CDMA Android Development] mrkite38:
take a look at loserskater's nbh editor
[Touch CDMA Android Development] thoughtlesskyle:
hey dzo,

what rom are you running that demo video you posted is that just reg froyo?
[Touch CDMA Android Development] dzo:
Yes it is.
[Touch CDMA Android Development] tiagoclc:
Something wrong

Gameboid and Gensoid are not working with new release.

I think its a memory allocation problem, but i dont know how to fix it.

Any sugestions?
[Touch CDMA Android Development] margosmark:
Hello all,

I am currently using the latest system (system-froyo-26-08-10_12.tgz) and the latest kernel (voguimg-240x320-2.6.32-froyo-27-08-10_23.nbh) on my Bell Vogue.

And I have noticed (perhaps ever since I have moved to the 2.6.32 kernel, the time on my device goes fast. It starts at the correct time, but after like 10-20 minutes it will be 50 minutes ahead, and every so often it goes back to the proper time, but then continues to go faster. Has anyone else noticed this? I have a brand new install, nothing installed (just brut maps removed as I do not need it)?

Also noticed that it does not always (reliably) go to sleep.

Any ideas?

Thanks,

Mark

Edit: I just reinstalled when i initially posted this, now it is 4 minutes ahead (actual time 12:17 EST, phone reports 12:21) this seems to be the pattern ( i have noticed it jump 4 minutes ahead all I have done since installing is put in my Google account credentials).

Edit: 12:23 actual time phone reports 12:30
[Touch CDMA Android Development] dertester123:
I have this problem too now that i looked for IT.

Manually Set my clock to 2am and now its 7:45am and the clock shows 8:33am

Could thus be a Problem with overclock in nbh?
[Touch CDMA Android Development] margosmark:
I have not overclocked anything (unless it was automatically set in the kernel by default)
[Touch CDMA Android Development] muppetman:
I also have this problem on my Polaris! I'm thinking of reverting back to previous versions of things until it's fixed
[Touch CDMA Android Development] dzo:
Here's a new system image, it has the JIT enabled and hasn't crashed on me yet.

https://sourceforge.net/projects/androidhtc/files/system-froyo-02-09-10_17.tgz/download

The time problem is a kernel issue, it might be fixed in the latest kernel (from today). Let me know if it's not.
[Touch CDMA Android Development] 4ultratech:
New kernal

New kernal zImage-2.6.32-froyo-02-09-10_16 still does not load with haret.

set sdce vdd to 17 is the line it hangs on if that helps.
[Touch CDMA Android Development] scooter66:
new install starts up with chinese!

Hi there. I have two Kaisers and installed the latest kernel and FroYo (as of 2-Sep-10) on both.

Wi-Fi works!

One phone is PERFECT in every way!

However, the other phone, physically the same, seems to have the default language set to Chinese! Why on earth does this happen?! I have installed the SAME kernel and Android image on BOTH phones. I've tried the Odex'ed and Deodex'ed builds for each. I get the same behavior.

I also tried Incubus' build too.

Can someone please explain why this is happening, and why one phone should behave so oddly?

I really don't want to revert to an older version, which would solve the language issue.
[Touch CDMA Android Development] dzo:
Yes, this is nand only and not tested on kaiser or polaris (but does include a new wlan.ko)
[Touch CDMA Android Development] samjam:
The new wlan.ko (posted last week) does not work on my kaiser.
[Touch CDMA Android Development] -Arturo-:
Yes unfortunately wifi doesn,t work on the latest kernel.
[Touch CDMA Android Development] dzo:
It will only work on the new kernel, check the version you are running, it should say 2.6.32.8.
[Touch CDMA Android Development] Dark-Side:
All work "out of box" on my kais130@550

Stock livewallpaper (like "grass") stop working for one month ago.

Neocore install eject SDcard and fail :confused:
[Touch CDMA Android Development] margosmark:
Thanks dzo, I'll try it out and let you know, so far no problems :)
[Touch CDMA Android Development] f_hugh:
New kernel doesn't like to sleep, or maybe it does too much? When restarted, came up in landscape. Also seeing the screen reversed at the unlock screen quite a bit...
[Touch CDMA Android Development] thoughtlesskyle:
does it flash the backwards text before it displays the lock screen?

if it does that its perfectly normal its only the reverse text and a lock up that's a problem, the reason it shows that text before the lock screen is the way our android port works
[Touch CDMA Android Development] loserskater:
I can report that the time issue is fixed with latest build/kernel. And I'm also not experiencing any sleep issues. However, when installing certain apps I get SD Card removed notifications. It says application installed but it doesn't show up, but if I keep trying to install it eventually will.
[Touch CDMA Android Development] VulpesFoxnik:
I cannot seem to get this to boot on the HTC Kaiser running your kaisimg-panel2-240x320-2.6.32-tilt-froyo-02-09-10_16.nbh

It just sits there at the launch animation.

I might try out my brew again to see if it launches.

-update-

Wait I think I might have found the problem. My applications aren't in the 'app' subfolder.

-update-

No change. :/

I'm not sure what to do, but I do have ADB and the entire SDK installed. If there's anything I can do t help, I would.

-update-

Seems Debian doesn't want to detect my HTC Kaiser when I lsusb.

-udpate- And nothing in the Dmesg. :/

I think I might need to set up a dedicated system to debugging.

-update-

My cyanogen port boots, so it's not the kernel...

Your new wlan.ko works though. A+

-update-

Turns on, however I cannot connect to wpa2 yet... I think this might be something I've done though.

-update- Yep. It was something I did. The endless booting stopped after I removed the battery for a while, and I maged to get Fresh Froyo to boot.
[Touch CDMA Android Development] garringm:
I think wifi tethering is broken on the latest setup. in the wifi tether log I get NAT rules enabled FAILED.
[Touch CDMA Android Development] samjam:
Silly me. I really thought I had 2.6.32, but it was 2.6.28

I'm on 2.6.32 now with latest froyo.

WLAN works - although seems to loose the access-point more often.

However, more seriously it always thinks my SD card is not inserted.

When I insert the sdcard, dmesg notices, and it creates the block device nodes:

brw------- 1 0 0 179, 11 Sep 2 20:58 mmcblk1p3

brw------- 1 0 0 179, 9 Sep 2 20:58 mmcblk1p1

brw------- 1 0 0 179, 8 Sep 2 20:58 mmcblk1

But none is mounted as /sdcard

On adb shell I typed:

mount /dev/block/mmcblk1p1 /sdcard

it mounts, but that doesn't seem to be what was needed, apps still think it isn't there

Sam
[Touch CDMA Android Development] spiritssight:
Hello all,

I am sad to say my TILT died about a month ago, I would like to get another one does anyone have any ideas or know of place that selling for good price in USA?? is the kaiser the best phone to get for the AT&T network? I want one with keyboard as and hope ofr HTC brand

Anyhow any help would be great, if there is another forum that I should post this question to please also inform me

God Bless,

Christopher
[Touch CDMA Android Development] alexanderbruns:
Hi,

one question to fresh froyo system in this thread.

Is the tiwlan.ini under /etc/wifi used in this release? I read a lot about "check this wlan.ko" or that one.

Perhaps all the tweaking on this module makes it not use the tiwlan.ini.

Because I want to try if I could disable WME in it to get froyo get and stay connected to my wlan-access-point (gentoo-linux with madwifi-ng and hostap)

Thanks for all the good work done here!
[Touch CDMA Android Development] 4ultratech:
New kernel with haret

Posted before that the new kernel zImage-2.6.32-froyo-02-09-10_16

still did not load with haret.

I am running a Vogue CDMA.

Just wondering if you need someone to test getting this running on haret.

If so reply with any links to updates and I would be glad to test and tell you the results.

What are the benefits of the 2.6.32 kernel over the old one.

Thanks for all of the hard work the last couple of builds are almost perfect.
[Touch CDMA Android Development] shanbh:
with the latest kernel kaisimg-panel2-240x320-2.6.32-tilt-froyo-02-09-10_16.nbh and the system-froyo-unodex-02-09-10_17.tgz, the google talk can send message but can't receive... is it only happen to me?
[Touch CDMA Android Development] dzo:
It's not a problem with the kernel but with haret, since the kernel has grown a bit it now overwrites the initrd.

Here's a version of haret that loads the initrd a bit higher in memory.

http://it029000.massey.ac.nz/vogue/files/haret-for-kernel-2-6-32.exe

No guarantees that this will work but it should boot.
[Touch CDMA Android Development] 4ultratech:
That worked!

I will play around with it and see if I find any other problems.

Thanks....
[Touch CDMA Android Development] 4ultratech:
Update: Got it running but everything run's dog slow.

Overclocked to 500 Mhz and it takes minutes to load programs and

everything is in slow mo with alot of FC's. may have something to do

with new LauncherPro v7.7.2.

Here is a copy of my default.txt do you see any issues here.

set RAMSIZE 0x07100000

# Set to 0x073 if any problems

#set RAMSIZE 0x08000000 ** Old original value

set MTYPE 1667

set KERNEL zImage

set initrd initrd.gz

#

# The following kernel parameters are useful

# ppp.nostart	- Set ppp.nostart=1 to disable starting the ppp connection on boot

# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller

# pm.sleep_mode - The mode used when the phone is off

# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,

# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt

# Default is 3, use 0 for best power savings

# board-htcvogue.panel_type - Panel type used to power the panel off and on

# 1=Hitachi 2=Topoly 3=Samsung

# clock-7x00.mddi - MDDI clock (try 0xa51 or 0xe2c)

# clock-7x00.ahb_div - Advanced Host Bus divider, default is 4

# 2 is faster but uses more power

# clock-7x00.a11 - ARM11 clock speed in MHz, best to leave this alone

# lcd.density - Defaults to 160, 128 shows more on screen

# vogue-ts.XMIN - xmin value for the touchscreen calibration. Also YMIN, XMAX, YMAX, PMIN, PMAX.

#

# Probably the only one of these you will need to change is the panel type, NZ Vogues seem to all have type 1

# US Sprint vogues usually have type 2 or 3 I think.

# Make sure you add these between the quotes on the following line and that your editor hasn't split the line up.

# set cmdline "ppp.nostart=0 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 no_console_suspend hw3d.version=1 board_htcvogue.pmem_size=4 board_htcvogue.pmem_adsp_size=1"

# Above commandline is for Froyo old kernel ----

set cmdline "ppp.nostart=0 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 no_console_suspend hw3d.version=1"

boot
[Touch CDMA Android Development] samjam:
ebay often has plenty of choice for such things. I have a spare kaiser but the keyboard e is a bit dodgy.
[Touch CDMA Android Development] citrit:
Bummer, my tilt just died yesterday. Started rebooting and then simply won't start. No charge light, no hard resets, no nothin. I have to admit I had a great time working with Froyo and Android and it was a load of fun.

Maybe I'll try and find a new one somewhere. Thanks to DZO and all the developers who made this possible. It was fun showing off my 3 year old device with the latest OS running. Sniff, sorry...
[Touch CDMA Android Development] samjam:
I note that although the atest kernel and froyo don't mount my SD card, when I remove the card it "knows" I've just removed it and says so on the status bar- but when I insert it can't mount

I'm just backing up my card now, then I'll blank it and see if Android offers to format it.
[Touch CDMA Android Development] samjam:
Yep, it offered to format it and then could mount it. Just restoring my data know.

The new partition type is c, before it was b. Maybe that has something to do with it
[Touch CDMA Android Development] samjam:
After restoring my backup, the SD card mounted just fine!
[Touch CDMA Android Development] n2rjt:
Many people complain that WIFI doesn't work, when of course they just need to put the right wlan.ko into the right place. Nobody has mentioned it, but compcache doesn't work either unless its modules are similarly updated.

Perhaps we should have an androidinstall.tgz on SourceForge that is updated with 2.6.32 modules? I build my own, but for people who run what they find on SF, it would be good if they could get something that would work "out of the box".
[Touch CDMA Android Development] vinny13:
I'm havin' a mass issue with the clock and its gettin' really annoying lol

It always ends up like half an hour off. This has been happening since I updated to the latest build. The clock is set to update automatically and it gets off, so I set it to manual and its good for a while but then it goes off again and I set it to automatic and all is good, for a little bit :/

Any solution to this?

**

Oh yea, and also when I wake it from sleep, everything is inverted sometimes until I unlock. This is also new to me.
[Touch CDMA Android Development] immolo:
Hi,

I've been using the new kernel on my Kaiser and for the most part everything is fine but the Internet Explorer button no longer acts as the home button and it really annoying without it.

Does anyone know a fix for this?
[Touch CDMA Android Development] mrkite38:
Should be better in the newest kernel I think.
[Touch CDMA Android Development] channer:
sorry I just wanted to know where we can get that wlan.ko file and where to place it to get wifi working? thanks
[Touch CDMA Android Development] immolo:
Also needed the latest fresh group release.

Thanks
[Touch CDMA Android Development] samjam:
I and someone else had this a long time back. The only fix was to re-install and then it worked right away.
[Touch CDMA Android Development] alexinc:
just wanted to shout out a big hoooray and thx, as of today i noticed, that i'm able to connect and freespeech via bt with my pioneer 800bt! not sure if its the latest froyo or kernel - maybe both! ;) now if only camera would work with this kernel on pola200 and fb-sync, then win mobile is far ahead for this device... thx again!
[Touch CDMA Android Development] j2sun:
Problem in Kaiser (using latest radio and kernel):

Radio signal is intermittent, I don't have this problem with the donut builds. I don't know if this is a Froyo problem though...
[Touch CDMA Android Development] endersm:
Dzo when do you plan to push the .32 kernel code to git?

Is it already there under a different head than htc-vogue?

Thanks!
[Touch CDMA Android Development] mrkite38:
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
[Touch CDMA Android Development] samjam:
I think it is here:

http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
[Touch CDMA Android Development] endersm:
Great! Found the source, but I'm having some trouble with NBHCreator refusing to make an NBH on account of zImage being too big (from what I can tell...)

How are y'all creating the NBH's? Is there some tool other than NBHCreator http://www.xda-developers.com/android/make-your-own-android-vogue-nbh-with-nbh-creator/ that I should be using?
[Touch CDMA Android Development] mrkite38:
in that same repository, check out the tinboot git, which contains some shell scripts & tools to create the nbh
[Touch CDMA Android Development] dzo:
You need to use a lzma compressed initrd for the 2.6.32 kernel and initrd to fit in the nbh, there's one on my site and in the bootenv git repo on sourceforge.
[Touch CDMA Android Development] mnjm9b:
I will be updating the nbhcreator to use the new lzma initrd.

Although I am sure this will break compatibility with older zImages.

not sure yet if I will integrate backwards compatibility in the next version or just

offer two versions.
[Touch CDMA Android Development] dzo:
USB ether was working with the old kernel, I haven't tried it on 2.6.32, you'll have to enable the function in arch/arm/mach-msm/common.c (line 111) too. This will only work to a linux box since windows needs the rndis driver instead. To get the rndis driver working you would need to port msm_hsusb.c to the gadget driver.