yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
it seems the 1.5 version is very buggy as of right now in our world of development. 1.1 works great but using the 1.5 system and initrd seems to cause a lot of random issues. Can anyone else confirm this too?
[Tilt, TyTN II, MDA Vario III Android Development] NealCCM:
The files are here:

http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
[Tilt, TyTN II, MDA Vario III Android Development] Markinus:
USB on Kaiser

HI!

I have read that the USB should work. But on my Kaiser this doesn't work. If I plug in the USB than there is nothing does. My PC Vista or SuSE does'n show a new USB device. Does this work on our Kaisers??

I'm using the last kernel, the older doesn't work too.

Markinus
[Tilt, TyTN II, MDA Vario III Android Development] joannerve:
Thanks dzo
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
There is a problem with USB on kaiser, it works once after first booting and then disconnects and doesn't work again. It works on vogue and polaris so there must be something different about kaiser. When it does work, it only works with a linux box. I'll try to fix it when I have time.
[Tilt, TyTN II, MDA Vario III Android Development] Markinus:
HI!

I'm attached my dmesg.txt, maybe this can help you to find the error.

Markinus
[Tilt, TyTN II, MDA Vario III Android Development] JeckyllHavok:
Went down from 6.5 to 6.0 wimo roms, but i still can't open opengl apps in 1.1

They seem to start but then my device reboots, this is my default.txt:
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Yep. I tried running 1.5 for about a week with the various updates from dzo. I had to run pm.sleep_mode = 0 for it to even resume out of standby; and even then, sometimes it did not resume. The backlight doesn't respond to dimming, and the front keybad led never extinguishes.

With all the bugs, it didn't make sense to run 1.5 over 1.1; when 1.1 runs very very well, and 1.5 adds very little.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
I'm surprised no one is reporting on this. This is with 1.1. Even with a fresh data file its doing the same thing.

How do i bring up the keypad during a call once the panel has gone dark and the red led starts flashing?
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Yeah, I guess that is a slight bug. When I press the power button to 'wake' the device back up while on a call, it ends the call. I'm guessing this is simply fallout from switching the buttons to do various things like wake the device up AND end calls (red button). Probably need to make the "POWER" button to ONLY wake the device, and the RED PHONE button to ONLY end calls (not wake/sleep the device).
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
You can press home button to get screen on w/o ending call.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
OK, I've changed it so it never suspends while in a call, only the display switches off, this lets the front panel buttons work. The new kernel is on my site, again system.img hasn't changed so just replace zImage.

I've been using the following in default.txt:

clock-7x00.mddi=0xa51 clock-7x00.ahb_div=4 clock-7x00.a11=528

Seems to work well and gives you the same clock speed as a G1 with 26.2 fps in neocore. The mddi parameter may not work for all panels, just remove it to use the default.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
You sir, are a gentleman and a scholar.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
I'm very thankful that Martin is working to port this to our Kaisers.

The latest zImage (which fixed the inability to sometimes (for some people) come back from a (red led) sleep state during a call) is working perfectly.

Also the default.txt strings for the clock speed improvements he provided a few posts back work well.

I do have another request/question:

what can we do (as loyal testers) to help get call-waiting working? dmesg, radio logs, you name it, we'll be glad to provide em.

Personally, I use android full time. The features I really want are only ones that are required to use the device as a full time phone. So bluetooth and Wireless are secondary to me compared to call-waiting.
[Tilt, TyTN II, MDA Vario III Android Development] bravekid20:
Changing Background

Hello Everyone,

First of all great job on the OS. Its really cool and everything works for me. However, I wanted to customize the phone a little and had a few problems. I cant find a way to change the background image. Also I only have 4 ringtones. Also my data connection is not working. And I dont know if any one else is, but I dont even a "default.txt" file in my sd card to boot android. So please if someone could reply that would be wonderful.

Thank You
[Tilt, TyTN II, MDA Vario III Android Development] bravekid20:
Oh I forgot to mention one for thing...

Hello Everyone,

I also wanted to tell that when I try to download the new zimage from dzo's website, it just shows the coding and doesn't download. When I save as target, it just saves as text. I'm using a mac. Please let me know.

Thank You
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I just had a look at call waiting, it seems to work fine but has no audio when you switch back to the original call, is that what happens for you? I'll have a look at it, it could be a simple thing to fix and just that I have an audio disconnect in the wrong place.
[Tilt, TyTN II, MDA Vario III Android Development] Sheytoon:
just wanted to say the new kernel works great. Good job Martin. Thanks for all the hard work to port android for Kaiser.
[Tilt, TyTN II, MDA Vario III Android Development] gleonard3:
While we're on the subject of phone calls...

I use my Kaiser all the time to stream music while I'm driving. This is via a 3.5mm audio jack to the car radio from a USB adapter I picked up for the phone. Works great. When I get an incoming call, I can answer it and hear the caller talking to me over the car speakers. Trouble is, they can't hear me, so I have to unplug the whole setup and put it to my ear to converse. Would be great to have this working like WinMo did so we can use it like a speaker phone. Hope it's a simple fix.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
I might be confused on what you were originally trying to say, but...

I did this too when i used winmo, except it was on the CDMA cousin of the Kaiser, the HTC Mogul.

However, with the adapter I was using (3-in-1 HTC adapter, pictured here:

I would have to disconnect the adapter to take a call.

So In my experience this is normal.

Now if you use an adapter that has a built in mic, like the one pictued here:

then it might be a phone issue.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
Yes, but more specifically:

Call waiting works fine, you can switch back and forth between the two calls many times, it seems, until one of the parties hangs up. Then when you switch back you can't hear anything.
[Tilt, TyTN II, MDA Vario III Android Development] gleonard3:
@mburris and anyone else who cares...

Pictured below is what I use to accomplish this. I bought it simultaneously with my AT&T Tilt (not CDMA) about a year and a half ago, and it's been very useful. I'll reiterate that the functionality I describe above has been available in a majority of the WinMo ROM's I've flashed, since the Dutty days. I REALLY miss taking calls on the road over this makeshift "speaker phone" setup. Simply put, the phone's own microphone is active and available during a live phone call.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
The simplest (most likely the fastest) solution would be to purchase an adapter like the second one I have pictured above.

You can get one from ebay shipped for less than 10 bucks.

I know its probably not the answer you wanted to hear, but its probably the most realistic solution.

Mb
[Tilt, TyTN II, MDA Vario III Android Development] pixolex:
Hello people!

For the past days I have been trying different buils from DZO and just in one build I could had sound from the speaker in a call. The problem is that I don't remember what build was and I had tried them all since 1st of May (I'm sure it was a build of May :confused:).

Without sound and micro in calls I can't use more android...I need the phone always on :(

Every one have sound in the speaker of kaiser in any build?

Thanks every one for the effort in porting android to kaiser.
[Tilt, TyTN II, MDA Vario III Android Development] audia4dude:
hmmm..i tried all of that.. 3G still not connecting in Android. phone and sms seem to be fine. APN and WAP settings look fine. i connected to the internet before booting into linux, but still not good.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
Follow on report on May 22 kernel

With the latest kernel (tested with existing data.img and viring data.img)

I am having seemingly random freezes.

3 times while it was just plugged in and charging, it froze with just the green led blinking.

Another time, while I was using the browser, it froze, same green led blinking.

I'm going to try and take some of those clock parameters out of my default.txt file and see if that helps.

I should add that the only 3rd party app I'm using is astrid for task list and task sync.
[Tilt, TyTN II, MDA Vario III Android Development] audia4dude:
YOU ARE TH FRIGGEN MAN!!! THANKS!! I FINALLY GOT IT TO WORK. THE ONE STEP I MISSED WAS TO INITIALIZE TOGGA. AFTER THAT, IM ONLINE! ;)

Happy Memorial Day Weekend!!
[Tilt, TyTN II, MDA Vario III Android Development] BlackBsd:
Booting/Stability Issues

Hi,

I believe this is the same issue that i have been reporting. For me sometimes the kernel gets further on than other times, but the hang/freeze/lock inevitably happens. I have tried to run the debug.txt file to gain the output from dmesg so that dzo may be able to figure out what might be happening.

The kernel commit does claim that it may break titan, but i have a AT&T Tilt / Kaiser, don't know if this has anything to do with the situation, the kernel commit log shows:

[Sun, 10 May 2009 10:15:12 +0000]

"Rewrite vogue cpld code, may break titan."

I also don't know if it was this commit that or *maybe* the one before, but i have not been able to use any kernels since that date.

@dzo, is their any other information that i maybe be able to grab that may be able to aid in debugging? As i said, sometimes the process gets further than other times. At one time when i got into the gui, i was going to grab a copy of my dmesg using the terminal application but I don't have a pipe, "|" symbol on my kaiser keyboard so i was not able to pipe it to a file. This is very weird because all your other kernels has work very well for me, and without others reporting the issue, I was unsure what was going wrong.

I am still always trying out the new kernels, as to aid in testing. :-)

Thanks

Bj
[Tilt, TyTN II, MDA Vario III Android Development] JeckyllHavok:
FOR ALL WITH REBOOTS IN OPENGL APPS:

Flash the HyperDragon IV Iolite from 5 (or 4.) of february

With this rom i can open all opengl apps in android like the API Demos, Neocore, World Clock or Droid Player. All the Roms i tried before won't work with the android OpenGL support.

By the way, the last to kernels from dzo are excelent, it's the first time that my device will always wake up from power collapse, even if it was there for several hours.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Is that suppose to be in a specific section of the default.txt?

Mine looks like this:

set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd "\Storage Card\initrd.gz"

clock-7x00.mddi=0xa51 clock-7x00.ahb_div=4 clock-7x00.a11=528
set cmdline "board-htckaiser.panel_type=0 ppp.apn=wap.cingular ppp.username=none ppp.password=none pm.sleep_mode=1 no_console_suspend board-kaiser-keypad.atttilt=1"
boot

And when I hit RUN in Haret, I get the following error:

Unknown keyword: `clock'

I hit 'ok' to the error, and Haret continues to boot with seemingly no errors, but I'm not sure if the 'clock' command actually gets set.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Well, maybe I'm retarded. I think those commands are probably suppose to be part of the set cmdline line.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
I am running Anryls WM 6.5 21232 and cannot run the Neocore program (restarts immediately after reaching the menu)

Perhaps I'll try the HyperDragon IV Iolite you suggested.
[Tilt, TyTN II, MDA Vario III Android Development] jmcbrother:
You're right! Check Martin's default.txt (from his Git):

#alloctest 0x2000

set RAMSIZE 0x07000000

set RAMADDR 0x10000000

set FBDURINGBOOT 0

set MTYPE 1553

set KERNEL zImage

#set initrd "initrd.gz"

set initrd "\Storage Card\initrd.gz"

#set initrd "\Storage Card\initrd-console.gz"

#set initrd "\Storage Card\android.bin"

#

# The following kernel parameters are useful

# ppp.username - The username used to connect to the network when dialing #777

# ppp.password - The password used to connect to the network when dialing #777

# 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 1, use 0 for best power savings

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

# 0=Don't power off the panel (Default)

# 1=Hitachi 2=Topoly 3=Samsung

#

#set cmdline "ppp.apn=www.vodafone.net.nz ppp.username=\"\" ppp.password=\"\" pm.sleep_mode=3 msm_sdcc.msmsdcc_fmax=20000000 no_console_suspend board-kaiser-keypad.atttilt=1"

set cmdline "board-htckaiser.panel_type=2 ppp.apn=www.vodafone.net.nz ppp.username=none ppp.password=none pm.sleep_mode=1 mddi.width=320 mddi.height=428 msm_sdcc.msmsdcc_fmax=40000000 no_console_suspend board-kaiser-keypad.atttilt=1 clock-7x00.mddi=0xa51 clock-7x00.ahb_div=4 clock-7x00.a11=500"

boot
[Tilt, TyTN II, MDA Vario III Android Development] BlackBsd:
These are kernel parameters, as such they need to go inside of the quotation marks of the set cmdline argument like such:

set cmdline "clock-7x00.mddi=0xa51 clock-7x00.ahb_div=4 clock-7x00.a11=528 ..."
[Tilt, TyTN II, MDA Vario III Android Development] biktor_gj:
About the clock thing... I was wondering... is this something specific for kaiser? It's totally not working on the Nike, but I can't see an obvious reason for it... I put a printk to see if it was getting to the acpuclk_set_rate, but it doesn't show up anywhere on dmesg. As I wasn't sure, I even tried a nonsense cpu clock (700 mhz a11 value on the board file) just in case, and it booted the same way, and took exactly the same time to boot, and the same performance, so I'm sure it's not working, or at least, it's not using the clock-7x00.c file.

I've checked the makefile, the board definition files, and both kaiser and nike have the same includes, and the same declarations, but there's no change on speed, on OpenGL performance, or on anything at all...

Any ideas on where to look?

Regards!
[Tilt, TyTN II, MDA Vario III Android Development] AngryUndead:
The audio routes are not properly set up to work when taking/making calls with the headset adapter. As near as I can tell more work would need to be done in that area to ensure that the proper route was open.

I'm not using this feature and have no way to test any fix I might (try to) make. I also am not really using android anymore... but the above is the problem not the adapter he bought.
[Tilt, TyTN II, MDA Vario III Android Development] gleonard3:
Going from my own experiences, I'm thinking it is NOT normal behavior to have to disconnect the adapter in this case.

I firmly believe, anything WinMo can do, Android can do better. Can I get a hell yeah?

Anyway.. we'll all get there eventually.
[Tilt, TyTN II, MDA Vario III Android Development] jmcbrother:
Outgoing calls issue

Are there any updates on the outgoing calls issue?

I'm just not comfortable with using old versions because of this problem, and newest versions aren't really usable if I can't make calls.

Thanks, guys!
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
With 1.1, I have had no problems with Outgoing calls specifically, 1.5 on the otherhand, I've had issues with calls not 'hanging up', freezing, etc.

I have noticed that in the recent zImages, I have heard some of the 'echo' problem, where I hear myself 'echoed' every once in a while. It is not soley on outgoing calls; but calls in general.

I am using an older radio, so that may be the issue:

Radio 1.65.24.36
[Tilt, TyTN II, MDA Vario III Android Development] jmcbrother:
You're lucky, man! Neither 1.1 or 1.5 works for me. The calls just drop after I hit the send button.

My Radio version is 1.71.09.01.
[Tilt, TyTN II, MDA Vario III Android Development] Markinus:
USB and Camera

Hi Dzo,

I tested in the last time the camera. I have a problem with the i2c communication. There is every time a Error "msm_i2c msm_i2c.0: Error during data xfer (-5)". Do you have a Idea? I tested different gpio configurations but nothing helped. The Address is 11.

I started today android with the polaris configuration, set MTYPE 1723.

In this Configuration the USB on Kaiser is worked. Vista find a "android phone" device. I think there is somesing different to kaiser configuration.

Maybe can this help you to find the USB Error on Kaiser.

Markinus
[Tilt, TyTN II, MDA Vario III Android Development] bravekid20:
Need Files Please

Hello Everyone,

Great job on Android porting! But I am soooo confused on which files to download that I need help. I basically want to know how I can get Android 1.5 on my Tilt. I've tried upgrading but the resolution isn't right. I just need link on downloading cause there are so many that i'm confused now. Please let me know.

Thank You
[Tilt, TyTN II, MDA Vario III Android Development] mikentucson:
Still Doesnt Find SD Card!

i've been searching and can't find a solution. i've used the following method to install 1.5

http://xdaforums.com/showpost.php?p=3780741&postcount=5163

everything works except that it doesnt find anything on my SD card. pics, music, video.. can someone point me in the right direction to fix this?
[Tilt, TyTN II, MDA Vario III Android Development] Viper12821:
Hi,

here is the link to the latest 1.1 system.img that i have rebuilt to contain the old RIL, Both openGl and calls seem to work but i have been unable to test the internet.

http://uploading.com/files/8S5PSJEV/system.img.html
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
First, 1.5 is really buggy for me whereas 1.1 is almost 100% stable.

Second, back on 1.1 if I enable the cpu clock as per the latest update, at some point the system will lock up. but disabled on the same setup, just without the command, everything is fine. anyone else care to confirm?
[Tilt, TyTN II, MDA Vario III Android Development] gleonard3:
@shadowline

I will echo your experience, although I'll add that with dzo's latest zImage, even without adding the new clock settings to the default.txt, there still seems to be some instability and/or freezing, though not as severe as when running with these settings in the default.txt.
[Tilt, TyTN II, MDA Vario III Android Development] okibi:
Are you running dzo's, f00bar's, or my 1.5 build?

With mine, even using the clock settings I don't have any issues other then needing the power setting to be 0, which still gets me around 6-8 hours of battery life.

http://ratedo.com/android
[Tilt, TyTN II, MDA Vario III Android Development] bravekid20:
Please can sombody let me know?!?!

Hello Everyone,

I wanted to know where I can get the files to run Android 1.5 for Att Tilt. I'm so confused with all the links. I did try upgrading but the resolution isn't right. So somebody could maybe create a zip or something that has 1.5 on it that would be great. Someone gave me a link before however it is not working for me. Please let know soon.

Thank You :o
[Tilt, TyTN II, MDA Vario III Android Development] yiyang12345:
Hi, i have a new phone, Motosurf A3100... Currently running on Window Mobile 6.1...

I wonder that i could upgrade to google android os on my phone?

Thx for the help...
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Ive been using your upgrade kit, but it is just unstable period for me, lots of lockups, network issues, and strange corruption. But only on 1.5, 1.1 only acts up with the cpu stuff enabled.
[Tilt, TyTN II, MDA Vario III Android Development] Niscandia:
Ok, got an intersting bug. Possibly one that has manifested for others.

Basicly it looks like Android 1.5 (not sure about 1.1 with the newer images, will test that out in a bit) will only charge the battery on my Kaiser to 30%. At that point Android says it is at 100%.

Now the reason I know this isn't true, is for one, getting roughly 3-4 hours of life from the phone before it starts crying to be plugged in, instead of 7-8, which I get if I power off the phone (or charge it in WM).

I have completely charged it outside of Android and started Android with 100% battery. Then I did let it run completely down. After that, recharged in Android, and rebooted into WM6 once Android said 100%. Only to find out the battery is only 30% full...

I don't mind the battery being off in Android... but if the battery isn't getting completely charged, it makes it harsh on the battery... Any ideas of what might be causing this?

Niscandia
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
I can confirm the randrom lockups with the latest kernel when you have configured the clock speed in the default.txt file.

However, since removing the extra commands about the clock from the default.txt, my phone has been running stable with no freezes for almost 4 days now.

running 1.1 of course.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
OK, I think I've fixed this problem can you try system-test.img in the files section on my site. It seems to work but I haven't tested it much. The only change is in the ril, it now only switches off the audio when there are no current calls.
[Tilt, TyTN II, MDA Vario III Android Development] BlackBsd:
i am wondering why some ppl are getting lockups more often than others, I am experiencing them from a couple of kernel check-ins ago. Is their any other way to get better debug info in addition to dmesg? I am having lockups but i dont know if it is related to the cpu clock check-in or not, could there be minor chip differences?
[Tilt, TyTN II, MDA Vario III Android Development] ajclai08:
http://www.engadget.com/2009/05/24/htc-lancaster-is-a-qwerty-slider-with-android-for-atandt/

AT&T android phone with 240X320 2.8 screen...looks like our kaisers are gunna be around for longer than we thought.
[Tilt, TyTN II, MDA Vario III Android Development] jmcbrother:
Thanks a lot, Viper! This should do for a while! ;)

Are you having the same issue? Got any idea about it's source?

I'll test the file and leave some feedback tomorow.

Thanks again!
[Tilt, TyTN II, MDA Vario III Android Development] Xcloud1990:
Awesome!! it will be a little easier port android on our kaiser!! :D
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
AT&T is going to d*ck around with it and make give the UI its own crappy treatment, so the actual phone won't be release until they are done, and who knows how long that might take.

On the bright side, I bet the HTC rom will be released long before the phone actually is, and it won't smell of ATT at all.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
Resolution solution

Is there a way to make the resolution of 1.1 work like the resolution of 1.5 without looking like crap (blurry) or having the wrong rotation?

I read somewhere (but cant find/remember where) that fubar did something special inside the code to make the screen res different, not just changing the mddi values of the default.txt file.

Can this change be applied to 1.1?

PS thanks for the call waiting test image, I will test it shortly and report back.
[Tilt, TyTN II, MDA Vario III Android Development] mburris:
Thank you for the test image.

Call waiting works flawlessly now!

Mb