yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
Ok, so testing zImage.usbfix. I'm not 100% sure what was goal behind that kernel except for fixing boot issue w/o USB cable, but one other thing I've noticed is change in LEDs behaviour. From what I understand there was frequency scaling enabled and left LED supposed to indicate frequency, am I right? It's green when CPU supposedly under full load and orange when not so loaded. Seems to be red when idle and off when sleeping; then right LED starts blinking orange in sleep mode also. But sometimes it doesn't go to sleep when screen is turned off and left LED stays orange almost all the time. Haven't yet found what keeps it from sleeping, working on it.
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
I've been having a problem in Android that my incoming text messages have incorrect times noted. I also have the same problem in WiMo. Any thoughts? The clocks are all set correctly. It started happening shortly after daylight savings but I'm not sure how to correct the issue.
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Yeah, the usbfix was only for people whose Kaiser wouldn't start up without USB cable connected. The add-on for the light is: green: no idle, amber: idle, red: deep idle, GPS light blinking: device sleeps. Soemtimes it just takes a while to sleep, it's checking mails then or something.

But the usbfix is in git now, so you can have a "normal" kernel from the nightly builds.

Here's another exerimental build for you: http://gigatron.de/.android/zImage.fkl

There is a lot of experimental stuff in, but the important thing to look out for is the light of the front keys. I did it for my panel type (topology), but I need others to test it. The lights should light up when you press a key and after a while go out again.

Thanks for testing.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
Thanks for explanation and sure thing you welcome. BTW, I'm thinking within couple next months upgrade to newer device, not sure yet whether it will be Kovsky/Venus or Raphael. I may upgrade to Dream, but I would like to help port Android to other devices, that's why thinking more about former. Sheer power of Kaiser is more than enough for me, but screen resolution becomes a little bit too small, especialy with Android apps tendencies, and I don't like blurry image. So, anyways, when I do upgrade it's highly possible that I will agree to sacrifice my Kaiser to testflash Linux/Android bootloader if someone will come up with code.
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
I was using default panel (0) so far. Front keys light up when pressed if phone is unlocked. If locked they won't light up at all if pressed separately from each other, but they light up if with locked but turned on screen you press quickly EndCall key and then any other including keyboard and hardware buttons but excluding D-Pad and cursor keys. Front keys also turn on with three consecutive EndCall presses from turned off screen. Also once after some wild chaotic keypresses I got comlpetely locked all keys except for D-Pad until I restarted device, but so far I fail to reproduce this glitch. Keyboard lights up always when screen turned on after sleep with open keyboard, even before unlocking. So far I consider to be a minor bug only issue with two and three key sequences that light up front keys. Other than that - awesome work, now no need to wait for keys to go off before booting android with haret that was put on HW button :D

When I switched to Topoly (3) then front keys always light up when screen turnes on then turn off after timeout, keyboard stays off always. Same with Topoly (2), except that keyboard changes it's state synchronously with front keys.

From what I understand panel type was meant to deal with graphics corruption, which I got only with Sony panel (1) in a way of some pixels that looked like dead and some color distortion. Also I got very short timeout for keyboard in this mode and keyboard was lighting up only when slided open or right after unlock, but not on keypress. Front keys are behaving same way as with default panel (0).

Switched back to default panel for now.
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Ok, since some posts here got lost, I will post again:

- power button works now, same function and red "end call" button. There is a "POWER" button definition in Android, but it doesn't do anything - so we cannot have the same functionality as with WinMo here.

- jog dial - I think MooNWalker voted for Volume Up/Down

the other option would be to make it behave like the cursor up/down keys, which could be used for reading long texts or so.

For the panel init sequences - I think I need to take out some. Probably someone just wrote down everything he saw when the panel was switched on/off and some are not important/relevant/have other functions (like the key light).

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
I ran this over the weekend, Ran beautifully made calls, data works great, did have browser just shutdown onced but it happens sometimes, battery life was excellent and it didn't cause the problems when going back to winmo. The only problem I have is when It goes to sleep, after a few hours in sleep state I cannot wake the phone back up. The left LED is solid green, I have to soft reset to get it to work. WHen I had it set to not shut off screen while charging the screen woud go solid white. What is this patch for and how is it used I got no idea how to do this stuff, I just install these builds and images.

Also how do I use the zimage stuff when I click on the mirror links on androidonhtc.com I've not fiqured this one out yet
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
The patch is just for developers who want to apply the changes I made into their own local kernel tree.

The zImage files you can just download onto your SD card, replace your older one and off you go. I think my mirror ( gigatron.de/.android/builds ) is the most reliable at the moment.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
I think it was me giving you feedback on zImage.fkl. I can repost, but not today - my girlfriend is complaining that I became unreachable with this kernel-merry-go-round, so I already promised - no reboots today :o
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
Funny you should mention that. My wife has also complained for the past week that I can't be reached, and I should get my phone fixed. :)

My feedback with the zImage.fkl image is that the phone doesn't wake up from deep idle (the wifi led blinks orange)

I've tried it 1/2 dozen times, and every time it goes into deep idle (after a few minutes) that's the end of that session, and I have to soft reset.
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Well, mine knows and usually tries a couple of times until she finally reaches me in minute where I don't reboot ;)

@outsider: did you happen to press the power key at some time? I think this kernel there hasn't got the power key fix, so I too couldn't wake the phone up once I had pressed the power key. Maybe I'll rebuild one or just commit the front key light fix. Did the backlight of the front keys work for you?

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] DhaMajoR:
WOWZERZ

This is Great​
[Tilt, TyTN II, MDA Vario III Android Development] adamc118:
wifi

any luck with the wifi or camera yet want to test out the torrent apps that use the camera!
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
did some mod just pick at this thread or am I insane?

not that I'm complaining, but I want to affirm I'm not doing something wrong :P

I followed two post-specific links in my history, and it says they didn't exist... couldn't find the posts when I looked...

meh...
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Well the forums were hacked and posts/topics were deleted or moved, then the entire forum had to be restored from a backup so a lot of things were lost. so in short. you are not crazy.
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
No, wifi does not work yet, but I've been reassured that it is being worked on.

Also, two random questions:

1. There a file on the Gigatron site called system-keylayout.img. I presume this is to fix the keyboard layout, as it doesn't work correctly on my Kaiser. How do I use this file? Do I just have to put it on my storage card, or do I also have to edit default.txt or something?

2. Is there any way to make Android come out of sleep when a call or text is received?

And thanks for all the hard work you guys have done on this thing once again. I'd love to help out as I want to see this project continue to mature, but I really don't think I would be much help as a developer.
[Tilt, TyTN II, MDA Vario III Android Development] catchfire:
i got this too after pressing the power button. but managed to turn the screen back on by randomly bashing buttons around for a minute.
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
See http://xdaforums.com/showpost.php?p=3482440&postcount=4321

But I wouldn't bother about the putting the system.img with the modified keylayout on, because I will change it soon in the kernel so that it will work with the usual system.img.

Anyway, maybe you're just looking for http://www.androidonhtc.com/troubleshooting#fn_keyboard_mappings_are_wrong

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
Hey Stefan,

Yes I did press the power key. I'm running Android now, and it's in deep idle, and I can easily bring it back with the hang up button. However, like you said, as soon as the power button is pressed, the phone will not wake up anymore.

And yes, the backlight on the front keys works like a charm, just like advertised.

Adrian.
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
Regarding the builds in http://gigatron.de/.android/ can you explain what the different versions are?

I see you put up a fresh version yesterday (30March09). Anything good in it?
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
Just curious; who's working on the wifi issue?
[Tilt, TyTN II, MDA Vario III Android Development] drofmij:
Excellent

Great work DZO I've been waiting for headphone support.

HOLY CRAP ringer volume is crazy loud through the headphones! :D I almost jumped out of my seat on the train. Would it be possible for ringer / alarm volume to be turned down while headphones are plugged in? If not I can turn it on silent mode while on headphones.
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
I've put an explanation and a link on the site.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
I did notice that my power button works now. It appears to function identically to the Red Phone button on the front of the phone (call end).
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Think this might have gotten lost in the whole xda-dev-hacked-backup-restored hassle.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
Which site?
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
This site ;)

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
Thanks Stefan. Found it.

Some feedback:

With the newest build (31March09) I was still able to somehow lock myself out of android. Pushed the power button, and the phone just didn't come back no matter what keys I pressed. I haven't been able to repeat it, but if I will, it'll be posted.

Also, it seems that when using the "hang up" key to turn the screen off, and back on, the screen comes back to the pre-set brightness.

When using the power button, 9 times out of 10 (seems almost random) the screen comes on at full brightness. The odd time it comes back at normal (pre-set brightness).

Also, I just called myself and answered the call on the android OS. The phone was in deep idle (red blinking led)

I answered the call, but could not hear any audio on the android OS phone or the land line from which I initiated the call from.

I also could not hang up the call.

After a reboot, there was still no audio, but was able to hang up the call on the android OS.
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
Well I wouldn't know who is working on it specifically, as I'm just a user/tester and not a developer. But I was told in an earlier post in this thread that a lot of work is being done on it.
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
Okay, so you are saying you are working on fixing the keyboard layout so that the usual files will fix the layout for the Kaiser?

Also, I haven't tried the boot options that the wiki site mentions, but that actually might fix the problem.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
What is the latest working build that includes all files, I need to start from scratch
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
The March 31st build gives me red and green artifacts all over my screen!

EDIT: Actually, it's not the March 31st build that's causing the problem; the March 30th build does it as well even though it was working just fine yesterday. Since then, the only thing I've changed is my keyboard layout value on my default.txt, which I changed from a 0 to a 1. Does this seem strange to anyone?
[Tilt, TyTN II, MDA Vario III Android Development] milas:
It's listed on the latest builds page on the Wiki. However, it doesn't include the newest kernel, which you can get by scrolling down on that same page to the kernel/zImage section, or by just going to http://gigatron.de/.android/builds/. I'll throw together an up to date bundle tonight.

Try checking your board-htckaiser.panel_type value in your default.txt. (Try the different values and see if that solves your problem)
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Ok, here are some issues I have too:

- brightness: it is very strange, seems to be a timing problem. When I set a panel type (2 or 3), the brightness is almost (!!) always wrong (maximum). Without panel_type, it seems a bit better

- calls: I have it reproducible now, and I think it has been reported before: I first have to make an outgoing call in Android, then all the other calls work just fine. But when the first call in Android is an incoming one, no go. I can't hear anything and sometimes it had happened to me too that I could not end the call -> had to reset.

- screen doesn't come on - this has not happened with the first builds of March, somewhere in between a subtle change must have slipped in

Well, let's hope we can fix all this...

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] joel2009:
I have also noticed the screen issue (not coming back on) and think it may just be hanging. Pressing enough buttonns and waiting long enough will usually eventually bring it back to life. I think it may occur when the phone falls into "deep sleep" (although it doesnt happen everytime?)
[Tilt, TyTN II, MDA Vario III Android Development] joel2009:
you have to change your keyboard layout in default.txt to reflect that you have the tilt variant of the kaiser.

"board-kaiser-keypad.atttilt=1"
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
That's exactly what I did to cause red and green artifacts to be all over my screen.

To be clear, what I did was change "board-htckaiser.panel_type=0" from 0 to 1 since I have the AT&T Tilt.
[Tilt, TyTN II, MDA Vario III Android Development] molesaied88:
im sorry, i know questions arent supposed to be posted here but i cant find where they should be. Has anyone been able to load android from a wm 6.5 rom? haret loads all the way to the end but the phone just freezes up. any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] joel2009:
When Haret hangs its pretty much always a ROM problem.
[Tilt, TyTN II, MDA Vario III Android Development] joel2009:
Which build and kernel? I have the tilt with the keyboard fix in default text and i have never had a problem like that.
[Tilt, TyTN II, MDA Vario III Android Development] devonian69:
I just booted into Android from my 6.5 (Anryls) installation. No problems at all.
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
EDIT: I figured out my keyboard. I was editing the wrong thing in my default.txt.

Also, a minor bug: if the phone is in sleep and I flip my keyboard open, the phone comes out of sleep, but first it displays code (like the code you see at bootup). That's a minor thing though, so I probably wouldn't worry about it now. Note: it doesn't always do this, but it sometimes does.
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
I run Android on top of the January 26th build of HyperDragon IV, which runs on WM 6.5.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I too run it on Anryls latest 6.5. Runs great really on every rom I have been using as of late.
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
Also, I have to say that in general the March 31st build is much better even than the March 30th build. I love how the button lights turn off automatically when the phone is put to sleep; I didn't see that in any previous build (though I am still mostly a newbie with this Android thing).
[Tilt, TyTN II, MDA Vario III Android Development] molesaied88:
sooo, is it just me or does anyone elses Google maps my location follow someone else?
[Tilt, TyTN II, MDA Vario III Android Development] tilt1414:
Yea im also interested, i still use 3/1 build. Where can i find the newest ones mention? thanks
[Tilt, TyTN II, MDA Vario III Android Development] ajclai08:
i installed open home trial and it looks clean
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
If you only plan on using the stablest builds, 3/1 is indeed the latest version. But if you scroll down more, you'll see the sections labeled "Experimental" and "zImage." The 3/12 version under Experimental is the latest version containing ALL the necessary files, and if you click on the mirror #1 link under zImage, you can get the absolute latest kernel. These kernels are compiled nightly.

Note: The files you'll get from the Experimental and zImage sections are technically less stable than the ones in the Bundles section, but I've never had any major problems with them. Plus, even though the bundles are the stablest, they still technically aren't "stable," so bundles will have bugs as well.
[Tilt, TyTN II, MDA Vario III Android Development] tilt1414:
Okay, well ill stick to 3/1, im using it as a daily OS,but whats this open home cupcake theme?
[Tilt, TyTN II, MDA Vario III Android Development] lanwin:
Interesting: My sim card dose not have the feature to disable the pin. Ive put it into the Sony handy of my colleague and the option is not visible as it is with his card. Ordered a new.
[Tilt, TyTN II, MDA Vario III Android Development] wornbat:
Its a Demo as Android does not have GPS capabilities as yet. Your not looking at someone else's GPS.. Take the tinfoil off your head now :)
[Tilt, TyTN II, MDA Vario III Android Development] BombaMyte:
That threw me off too...
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Why not start reading after all :eek: :rolleyes:

Stefan

P.S.: Sorry for being nasty :o
[Tilt, TyTN II, MDA Vario III Android Development] Smultie:
Has anyone got this (http://www.junefabrics.com/android/index.php) program working on the TYTNII?

Can't get it to work here @ work, but that might be because i'm at.... work.
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
I don't think the USB connectivity to the android OS running on tytnII is functional. Hence your lack of results when trying to use the software.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
I have this problem with anything past the 3-1 build, it seems to happen if the phone has been inactive for long periods of several hours, mine was hung up this morning at 5:30 but was just fine when I looked at it at 1:30am? I also get file errors on bootup and have to reinstall data.img after it has been shutdown and restarted.

I personally don't like the remapping of the keys mainly the volume and menu keys. I do like the addition of the power button functioning. I also liked the led light show that I think seidler had done in one of his zimages, but that build was not stable enough for me to keep. just my thoughts
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
What was it that you didn't like? Do you have a better suggestion?

Also, I use this opportunity to reiterate my question: if the jogwheel would be working, what would you like to have it do? Volume Up/Down or Cursor Up/Down or someting different?

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] Dark-Side:
I think Volume Up/down is the better choice

Thanks for your good job ;)

Fab
[Tilt, TyTN II, MDA Vario III Android Development] molesaied88:
yes, in my opinion id say have the jog wheel be volume with push in switching to vibrate, if possible. I never understood why that wasnt originally done even with WM. also one other question please, does the marketplace not work for anyone else? When i pick something to download it brings it up to the notification bar and says download unsuccesful. thanks in advance
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
I would vote for volume up/down
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
Just my 2 cents but I would like to see the start button work as the menu button, OK button is fine, the left and right soft keys I didn't mind as the volume keys I actually got quite fond of them but, if possible I would like to see the Browser button open the browser and the message button open messaging. and then maybe remap the button under the scroll wheel to use as a terminate button for the app that has the focus. My fat thumbs did not work very well for the menu buttons being the softkeys.

One other thing I would like to see working I know you all are working out the audio issues but I use speakerphone alot especially when making calls with a lot of prompts.

Thanks
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
I really like to use it to navigate in a page, but at the same time it's useful to turn the volume up and down. Can it be done like it is in WM, in that the wheel behaviour changes depending on the context? So during a video playing or music app the wheel is used for controling the volume and on browser it is used for navigating up and down and click?

regards

Emerson
[Tilt, TyTN II, MDA Vario III Android Development] lanwin:
+1 for Up/Down - i really like scrolling large texts with it.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Apparently I'm different from everyone else, but I'd vote that the jog wheel works as a cursor up/down.

Perhaps it can be application specific as it is in Windows?

1. Volume up/down when in call, or in a media player, press to mute, play/pause

2. In all other programs: Cursor up/down in all other applications, press to select.

I mainly use the jog wheel for navigating with one hand, so I would thing the jog dial would retain its usual functionality of cursor control at least.
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
Anyone having the issue where your Tytn's screen turns on when the phone is finished charging? My screen is turning on several times a night. I turn it off and sometimes it turns itself back on, up to three times before it remains off for several hours. I've even changed the setting in the Dev Tools/Development Settings and deselected "Keep screen on while plugged in."

Any thoughts?

Thanks guys

Sharpie