yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] silasrye:
rss feed

Sweet! so long as it stays up to date it might keep me from checking this thread every 30minutes. Its just a shame that individual threads cant be made feeds.
[Tilt, TyTN II, MDA Vario III Android Development] excogitation:
If you need data for calibrating the Pola160 battery have a look here.

Absolutely!
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
hey... ds2746 does NOT have a temp sensor - but the touchscreen schip does.

Since people all have different batteries, is there a way anyone knows of to read the ID of the battery or so?
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I've added support for powering down the panel. This may help people with displays that don't wake up properly. To try it, get the test kernel from here:

http://cs-alb-pc3.massey.ac.nz/vogue/files/zImage-test

Add board-htckaiser.panel_type=n to the cmdline in default.txt, where n is 0..3

0 doesn't power down the panel.

1 is a sony panel and 2 and 3 are toppoly panels.

I have type 2, I guess the panels that don't work are type 1.

There is a good chance that this won't fix the problem but it should make it possible once the panel init sequence is known.
[Tilt, TyTN II, MDA Vario III Android Development] Pure4Real:
I'm trying this new kernel right now with board-htckaiser.panel_type=1 and pm.sleep_mode=1 and it's working correctly now. The screen is very blurry though, but as i've read that has to do with the new resize stuff. In any case, good work.

<edit> I just tried the kernel from the 23-2 pack hosted on your site and the screen is much less blurry with this kernel. The vertical lines problem exists with this old kernel though so i guess you've found (part?) of the problem. </edit>
[Tilt, TyTN II, MDA Vario III Android Development] tilt1414:
Well guys im useing the newest build and noticed a few things, thought i would give a heads up. Well first i noticed when i get a sms notification in the status bar and have my screen slid up, i try to bring down the notication bar to open the sms and it wont open it. So i have to close it then bring the box down.

Second,my girlfriend sent me 2 MMS, and it shows up with the download button, it starts ..then fails.

Third, im not sure if im the only one experiencing the network signal changes, ill have service then drops for a couple seconds then comes right back. So im curious if im only having that problem..hmm

thanks!!
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
i have all of those issues from time to time. but not always,
[Tilt, TyTN II, MDA Vario III Android Development] tilt1414:
hmm im glad im not the only one.
[Tilt, TyTN II, MDA Vario III Android Development] PhoenixMage:
To my untrained eye it loked like the colour was set too low for what it was trying display.

Interestingly I only have the vertical lines problem when running from battery. If I have it charging and have switched the screen off for extended periods it never seems to happen on the old kernel (21)
[Tilt, TyTN II, MDA Vario III Android Development] andybbtt11:
Just to be clear,

Should I be able to mount my kaiser via usb uing android?

When I plug in the USB, I get no notifications or anything.
[Tilt, TyTN II, MDA Vario III Android Development] AXP:
No, u shouldn't
[Tilt, TyTN II, MDA Vario III Android Development] Smultie:
Same here unfortunately :(
[Tilt, TyTN II, MDA Vario III Android Development] andybbtt11:
Also, is anyone getting a problem with it saying your storage is full when trying to download anything?

I can't DL stuff from the market and I thought it was a connection problem, but then I tried to DL something from g1wallz.com and it failed and said my storage is full, when, in reality, I have 3+ gigs of storage and 75mb of storage internal.

I really am loving this android build, but the app downloads are a major important thing, I'd say.
[Tilt, TyTN II, MDA Vario III Android Development] imfloflo:
@Dzo with the lastest zImage-test on the polaris thescreen orientation isn't good and when i plug USB the screen is turn to the right position, when i unplugg the screen rotate again funny feature ^^

The previous camera button to rotate screen don't work anymore
[Tilt, TyTN II, MDA Vario III Android Development] adthor:
Now got the G on top of the screen. Editted the Android APN settings. Correct the MNC & MCC to be right for my provider (234 10). Everything else left the same. 'G' appeared
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
@All the people complaining about downloads: Please check twice, that in the root of the SD card you have /cache folder because taht one is used for the downloads.

At last for the Market, but I guess that it is needed for all downloads, including MMS.

EDIT: By the way, Gmail is down now, do not be stressed by not being able to sync mails, the service is unavailable and it does not work even through the web.
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
That's really nice, powercollapse works, no white lines anymore. But now the screen is disturbed. Looks like not showing all colours or just having some problems with the displayed graphics. All is not blurred but like having a pitch signals that just redraws some points with pale or moved colours, instead of the right one.

Hmms... can you imagine an old tv with bad analogue signal? That seems like kinda that noise problem.. :(

Anyway it is next step forward, so thanx for that, now we should try to get it a bit cleaner. Maybe I'll just test other panel types.

By the way dzo, is there somewhere a place that we can get some HW and Tech specs for our phones? Not like only the chipset and so on, but more detailed description of the hardware? Would you guess that it would be possible to create routine, that would detect the hardware in android to let it automatically do the setup?
[Tilt, TyTN II, MDA Vario III Android Development] slux:
I dont get the coloured lines on power collapse, but I can confirm the screen orientation is upside down and the touch screen is reversed relative to the display when keyboard is slid out. (in other words the touch screen orientation switch appears to be correct but the display is upside down!

Also cant seem to get the soft keyboard to appear on screen at all - it's always worked in the past.
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
Soft keyboard is not included in the SDK 1.1, you might try to look for an apk to install it?
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Hi,

To get the mddi init sequence for this panel can somebody trace it. Here's what you need to do.

Flash the hyperdragon III rom so you are using the same wince dlls as me (may not be necessary).

start haret and connect to it with haretconsole, then type the following:

addlist mmutrace 0x4f669000 0x1000

connect another haretconsole to haret

in the first session, type:

wi 20

in the second session, type:

setlcd 4

wait a few seconds then type:

setlcd 1

there should be a whole load of trace entries like this:

002031: mmutrace 0255e9b8: e7e7130b(strb) 4f669b00 00000001 (00000000)

002031: mmutrace 0255e9cc: e5c70001(strb) 4f669b01 00000000 (00000000)

002031: mmutrace 0255e9d0: e5c73002(strb) 4f669b02 0000000e (00000000)

002031: mmutrace 0255e9d4: e5c70003(strb) 4f669b03 00000000 (00000000)

if not, it hasn't worked.

send me the trace (it should be automatically saved to a file)
[Tilt, TyTN II, MDA Vario III Android Development] Michel82:
The 23-02 package works great with mddi settings to 240x320. Screen is as sharp as before, no more blurry stuff. Downside is that everything is rather big with these settings. The other mddi setting (320x480) is also not the right ratio it makes evything sowhat stretched: 320/240 =1.3334, 480/320=1.5

Is there a way to use 240x320 and make everyhting a little smaller? Like font and iconsize?
[Tilt, TyTN II, MDA Vario III Android Development] assangflexx:
Whatteheck!

started android to show a friend. Screen went off. Screen didn't want to go on :confused:

Then reset with stylus. Winmo was starting. Then i got an notification that my battery was on 1% :eek:

Did reset, to be sure connected power. And now it is 98%. I ran Android with 99% battery...

bug :( or what...
[Tilt, TyTN II, MDA Vario III Android Development] AciDCooL:
Tried to post it here but too much data :P

instead ill attach my putty log
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
I actually changed it to 360x480 which indeed takes out the somewhat stretched bit.. the ratio is perfect like this!

EDIT: tried playing around with it more: setting it to 480x640 actually works, but the screen fliqqers a lot, but everything is nicely placed relatively...
[Tilt, TyTN II, MDA Vario III Android Development] Bimboy:
His girlfriend sends you MMS messages too? I thought I was the only one. ;)

Seriously though, these new builds are getting better and better. I'm almost contemplating using it for a few days as my default OS (if I can keep it charged). It's just about there.
[Tilt, TyTN II, MDA Vario III Android Development] markya23:
Dumb question for the day

It all seems to be working great - thanks!

Dumb question though - how do I either find out which panel type I have, or determine if power collapse is working? I have tried all panel types in the default.txt but they all seem to collapse properly! I'm sure that they can't *all* work!

Keep up the great work guys!
[Tilt, TyTN II, MDA Vario III Android Development] roadhead:
I finally got the Google login to work for me today, the problem was despite the fact data was working, without the correct APN settings it just wouldn't connect.

Also I now have the G icon and the up/down arrows that blink on data transmit/receive.

So to anyone still having trouble with marketplace/google sync despite working data, make sure APN settings are correct :)
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
so, on panel 3, the front keylight actually turns off - who knew it would be tied in (unless I'm crazy, and just forgot that it did that with 2)...

why doesn't the device lock anymore - as in, when you press the red button to put it to sleep, it'll wake up at any press of the touchscreen or any keys - and sometimes randomly - and not even show the lock screen, just go straight to home.
[Tilt, TyTN II, MDA Vario III Android Development] TaC:
It seems that 360x480 is a near perfect resolution for Kaiser. A bit blurry but correct proportion.

I have been using it for work since yesterday, a bunch of calls, e-mails and sms, including web based operations, and it works perfect in everything.

Only bluetooth support, and Android will be my main O.S.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Everything (SMS, Sync, Internet, calls) works for me except the marketplace. Your suggestion made me excited since I hadn't created the /cache folder; unfortunately, I lost my enthusiasm when I noticed that a /cache folder had been automatically created for me. So, I deleted the folder (and the one folder it contained /cache/lost and found) and created a new /cache folder.

No dice. Still fails.

On a side note, the width 360 and height 480 does work nicely, but as mentioned before, is blurry.
[Tilt, TyTN II, MDA Vario III Android Development] Smultie:
Are there any views on wether or not Android will one day be bootable without using Haret/Windows Mobile first?
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
I don't see why not, but we ought to try it out.

I may consider making a .nbh just to see if it would work...
[Tilt, TyTN II, MDA Vario III Android Development] eezak:
Why not?

Because if you boot straight into linux, the hardware won't be initialized.
[Tilt, TyTN II, MDA Vario III Android Development] graftark:
Panel 3 worked for me too, thanks!! Was annoying to always have those keys lit up.

My device however does lock and shows the lock screen.

As for my calls... I can make and receive calls but the speaker and the mic are not working. I also have no volume device-wide. Is there some sort of setting I am missing? Seems to me that many others are having success with their calling. I have the APN setup for AT&T and I do get the G w/ arrows. I am using an AT&T Tilt; KAIS100.
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
like what?

we initialize most of the stuff already... notice that we can make data work without starting it up in winmo first...

I'll give it a try, soon...

EDIT: waitaminnit... we need a bootloader. Any suggestions as to where to find one?
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Yes she does ;) lol j.k

I have no issues with running android full time until i need a feature that it doesnt have yet, camera, gps, etc. I can keep it charged when i bring a battery backpack and a solar charger so it lasts about an hour then. :rolleyes:
[Tilt, TyTN II, MDA Vario III Android Development] milas:
Since this seems to be asked a lot, and I know it's been answered before (including by me), here you go: http://www.androidonhtc.com/kaiser/install#low_on_space_warnings
[Tilt, TyTN II, MDA Vario III Android Development] andybbtt11:
Thank you. I am going to try the Cache folder thing now.

If I need to clear up space, are there certain files I can erase? What would I want to clear out to make it work?
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Good to know milas. I thought it was something to do with that but never really looked into it.

Although I wonder, in theroy is it possible to expand that max?
[Tilt, TyTN II, MDA Vario III Android Development] andybbtt11:
I tried deleting and remaking a cache folder. I also deleted everything that isnt needed inside the android folder, still no luck. Oh well, I can't wait for the next release.

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
I know that for Dream (G1) owners with root access it's possible to get the apps to install to SD, but perhaps cause of the cramfs / fat32 incompatibility we cannot go there yet...

Any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] milas:
I think if you go to the remove programs menu in the settings, the apps have a "Clear Cache" next to them so you can delete all their temp files. It might be somewhere else, but I definitely remember seeing it. (Not booted into Android atm or I'd give you a definite answer)

It should be easy. If you have a Linux system, try using resize2fs. I have NOT tested this, but it should work in theory

Something like: "resize2fs data.img 128M" should do the trick. Keep in mind this will make it take substantially longer to copy the file to your SD card, obviously, so I wouldn't go overboard. (And yes, you could .gz compress it - but then your device will just have to write it out on first boot anyway)

If you get errors, try running "e2fsck -f data.img" after resizing to check for errors.
[Tilt, TyTN II, MDA Vario III Android Development] biktor_gj:
For what I've seen on the G1, the ipl is quite similar to what you can find on Windows Mobile phones from htc, so it may be possible to plant a second bootloader (say redboot, say whatever you'd like) wich starts on the rom entry point for Windows Mobile, and from there jump to an address where the zImage is stored, copy on ram, and keep booting after passing the cmdline. If I'm right, the IPL and SPL start all the main hardware (mmu, lcd and basic stuff), so the screen should be on before a third bootloader comes in...

The problem is... if something goes wrong, will the spl let us reflash something esle? And well a million problems more I guess..

Regards!
[Tilt, TyTN II, MDA Vario III Android Development] Globalrebel:
Don't forget about GPS!! I would love it if my GPS finally started working in Android! GOD that would rock!
[Tilt, TyTN II, MDA Vario III Android Development] wanderso:
Alas, my only public contribution to the Android-on-Kaiser effort so far is this: a ratio.

Use 320x428 and the blurring (mostly?) is gone.

Willie
[Tilt, TyTN II, MDA Vario III Android Development] krisje8:
Hmm, this resolution is quite acceptable and most apps work with it so far.

EDIT: Damn, terminal is unreadable at this resolution, so I'll have to use 240x320 instead. Or is there a way to make terminal fonts larger?

EDIT2: Huh? The orientation is correct? How come the orentation works with 320x428, but opposite with 240x320 ?

P.S.: Does anyone know a good terminal for android? Because the current one doesn't have tabcompletion and I cannot use the up and down arrow keys to scroll through my history. Both these functions would save a lot of time, especially on a phone.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Ok, extremely wierd; I just flashed the 1.71.xx.xx radio, and now my screen rotates the right way.

I was using the 1.65.xx.xx AT&T WM6.1 Radio...

I also switched to the Hyperdragon IV 2.24.2009 ROM, but I think it was the radio that effected the switch.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Ok, so maybe the 'correct rotation' depends on the size of the screen set in Default.txt?
[Tilt, TyTN II, MDA Vario III Android Development] tembares:
With 210209 release from DZO I did not have any trouble with vertical lines. I worked with Android all day and even calls went very well (except volume up/down).

Before I went into bed I connected the power adapter to the unit.

When I woke up and wanted to wake the GKaiser ;), I had the vertical lines again.

Later I did some tests with and without a power adapter connected to the GK. I could not produce the vertical lines every time, but I think the vertical line issue is 'connected' to the USB (port).

Hope this helps the devs.
[Tilt, TyTN II, MDA Vario III Android Development] AciDCooL:
I've had the same thing only without usb cable, you should try the 23-02 version. no vertical lines but very blurry and wakes up a bitstrange from powercolapse. other then the blurryness its pretty good
[Tilt, TyTN II, MDA Vario III Android Development] tembares:
@AciDCooL: When you started Android for the first time, did you had a cable connected to the GKaiser?

And when you the vertical lines? Was the cable connected or not?
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Thanks for the trace, just what I needed.

I made a few changes, try a new test kernel:

http://cs-alb-pc3.massey.ac.nz/vogue/files/zImage-test

(this only for people with the vertical lines problem)
[Tilt, TyTN II, MDA Vario III Android Development] adamc118:
64 Mb limit

Hey dzo do you think in the future releases the 64 Mb limit will be taken away?

and can you tell us the progress so far with wifi, gps, and the camera

Thanx Devs!
[Tilt, TyTN II, MDA Vario III Android Development] bluenfee:
Another issue (not sure if it was addressed or not)

If I have the phone plugged in and hit the sleep button. The screen will randomly switch on and stay on. Tried uninstalling programs that had background tasks and turning off syncing with no luck.
[Tilt, TyTN II, MDA Vario III Android Development] tembares:
@DZO: I downloaded the test-image. I will test it the next hours/days. I will try to get the vertical lines :)

I thought your wrote somewhere that the resolution 480x320 did not work for you, because the font in the terminal was to small to read. Did you know you can change the font size? In terminal you have to click the menu button and choose Preferences. There you can set some settings.

More and more I hit the menu button on some moments, just to see what happens.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
The latest kernal zImage-test linked above breaks my data, and as before, when sliding the keyboard open/closed, the screen first flips 180, then corrects itself. The screen 'indecisiveness' isn't too much of an issue since it ends up working correctly.

For reference, I'm using 1.71.09.xx Radio, Hyperdragon IV ROM 2.24.2009 and my default.txt string looks like this:

set cmdline "ppp.apn=wap.cingular pm.sleep_mode=1 mddi.width=320 mddi.height=427 msm_sdcc.msmsdcc_fmax=20000000 no_console_suspend board-kaiser-keypad.atttilt=1"
[Tilt, TyTN II, MDA Vario III Android Development] hova killer:
can someone give me some advice i am using the new 1.71.09.xx radio but when i get calls i can hear the person but thy cant hear me any sugguestion on how to fix this problem....by the way using the new 2/23 build
[Tilt, TyTN II, MDA Vario III Android Development] biktor_gj:
The 64 mb limitation is just because data.img is that size. You should be able to make it bigger using dd or resize2fs...
[Tilt, TyTN II, MDA Vario III Android Development] TaC:
Hey, good one! Now resolution is perfect. Still have to try some other apps, but it looks pretty nice.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
With that resolution the blurring is at a very minimal. But some applications made for a specific size are cut off or do not work well.
[Tilt, TyTN II, MDA Vario III Android Development] devonian69:
Do you get the verticle lines problem with the new zImage?
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
Gee, I bow my head down to the grownd oh Lord.... :D:D:D

Resolution set to 360x480, used second test kernel:

the noise in the screen disappears, picture is sharp and clear, even through it is a bit small... but I do not realise any blurrness anymore, perhaps i just get used to it :D

No Lines after power collapse, but data connection is not working anymore :(
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Ok, after messing around with a few different screen resolutions, I have to recommend not changing them at will to any values you think sound 'nice'. I tried a combination which seemed to be ok for the 4:3 ratio, but I think you really need to pay attention to a 4, 8, and to be safest, 16 bit number combo.

I made a quick excel sheet of resolution combos which should work well.

I'm currently using: 336x448. It gives a nice resolution, non-blurry, and yet small enough fonts/icons where you can move them around successfully.

Try some of these:

240x320 <-- Screens native resolution.

288x384

336x448 <-- This is is my resolution. Good mix of size and clarity.

384x512 <-- This appeared to make the Unit freeze. Gets to Waiting for SD Card

432x576 <-- Doesn't quite work correctly. Will boot, but screen lags.

480x640 <-- Doesn't quite work correctly. Will boot, but half the screen is finicky. This may be a video memory issue. Seems that the lagging and refresh becomes progressively worse as you increase the resolution.

Note, these are all on 16bit even increments. By dropping to an 8 or even 4 bit increment, you can come up with much more options, but I'm not sure if they are 'safe'. For example, I tried a resolution that was NOT support (garbled text, crazy lines), and after restarting, it had blown away a bunch of my settings!

If you are really bold, here is the full list of 4bit spacings:

240x320

252x336

264x352

276x368

288x384

300x400

312x416

324x432

336x448

348x464

360x480

372x496

384x512

396x528

408x544

420x560

432x576

444x592

456x608

468x624

480x640

Also, the only resolution which correctly configures the splash screen I believe is the incorrectly ratio'ed 320x640
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
I've honestly never experienced the vertical lines problem; I use android with usb, non-usb, power on, off, sleep, wake, ac/adapter no vertical lines.
[Tilt, TyTN II, MDA Vario III Android Development] Pure4Real:
Using this kernel i have no vertical lines problem and the blurryness is reduced to the level of the people with the other screens ( i think )

<edit>As it now appears, after changing the screen resolution to make it less blurry the vertical lines problem returns. After removing the screen resolution lines from default.txt the problem was still there, even after removing everything on the sd card and starting over...</edit