yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] tablatronix:
Messing around with AndroidGlobalTime (The earth thingy)

I figured these commands.

2 - Zoom Out

8 - Zoom In

W Toggle Earth On/Off

A - Toggle Atmosphere

L - Toggle Lights

D Center - stop spinning, toggle 2d 3d

D Left - exit

D Up/Down - rotate Earth Down/Up

Vol UP/Down Spin speed +/-

SPACE - Show/Hide Clock

While clock is open typing will autocomplete citynames.

Arrows will jump cities and timezones

/(?) twice - will bring up some kind of command line or label in the top left corner that you can type into.,no clue what it is.

You can check the source if you feel, there is probably some stuff missed with my hunt and peck method.

have fun

:)

http://code.google.com/p/apps-for-a...android/globaltime/AndroidGlobalTime.java?r=8
[Touch CDMA Android Development] dzo:
The SD driver now works, this means you don't have to run everything from an initrd and your settings will be saved across reboots.

It also means that the titan should boot (though I haven't tried it and the keyboard won't work), titan owners let me know. To use the new version, download the android.zip file from the website.

In it are 6 files, put system.img(128M) and data.img(128M) onto the sd card in your phone (the "\Storage Card" folder), put zImage, default.txt, haret-0.5.1.exe and initrd.gz anywhere you like and then run haret.

The data.img file holds your settings and applications, it's just an ext3 filesystem so on a linux box you can mount it to add applications and import contacts etc..

This should be safe, but there is always a chance that it will corrupt your card so back it up first.

Have Fun
[Touch CDMA Android Development] l33tlinuxh4x0r:
Touchscreen works on Titan/mogul. it boots fine. I can make a phone call but can not hang up. Also the only buttons that work are the power button and the end button but they only work sometimes.
[Touch CDMA Android Development] Dukenukemx:
Awesome, but what do you mean audio input is broken still?
[Touch CDMA Android Development] dzo:
I made some changes to improve the ts sensitivity and put new NBHs (same name, different timestamp) on the website.
[Touch CDMA Android Development] kallt_kaffe:
For Kaiser users, try echo "3072" > /sys/module/tsc2003/parameters/sensitivity

At least on my Kaiser that value works great with the new touchscreen driver.
[Touch CDMA Android Development] lagloose:
I know, this is Kernel Thread for Vogue...

Nevertheless the information for you, that with the actual kernel, Audio on HTC Nike seems to be broken. Ring- and Media tones sound "cracking" and are very silent. Volume can't be adjusted anymore...
[Touch CDMA Android Development] xport:
I get a force close on screen calibration now running:

Myn’s Warm Donut - [RLS 5 - 04/24/2010]

voguimg-240x320-16-06-10.nbh
[Touch CDMA Android Development] Gersonian:
Audio on sleep

Anyone else having issues keeping audio playing when the screen goes off? Had to switch back to 5.29 kernel. Sent a PM to dzo about this, but wanted to check in with everyone else.
[Touch CDMA Android Development] dzo:
I've added an interface to the old calibration mechanism, calibration should work for all devices now.

Works fine for me on Donut, perhaps it's an eclair problem.
[Touch CDMA Android Development] spiritssight:
DZO,

I have a kaiser, I only see a panel 2 on your site for the new NBH how can I change it to 3 if I need to? Also is there any different if I am using eclair or donut for the NBH also ?

Keep up the great work!

God Bless,

Christopher
[Touch CDMA Android Development] dzo:
Use this:

http://xdaforums.com/showthread.php?t=689812
[Touch CDMA Android Development] Heero808:
Hello, I am a new member and I have been using Warm Donut RLS5 and using the 06-17-10 320x480 nbh and I really like the improvements each new nbh brings but one thing I noticed compared to the old releases is that now when I turn on my phone and it hast the Linux boot screen, if I touch the screen it triggers something like a button press would. Is this intentional?

It also launched the installation menu if I touched the screen and held down on it until the installation screen launches

Yeah, sorry, not to sound like I'm complaining but is this a new feature?
[Touch CDMA Android Development] xport:
Thanks dzo, off to flash....
[Touch CDMA Android Development] mssmison:
It was added some time ago by vilord when he originally released the new installer.
[Touch CDMA Android Development] drewden123:
Hey dzo, I apologize if you have already addressed this but, how come the latest eclair kernels do not support adb/tethering? I am using kallt_kaffe's VaniljEclair and I flashed to the latest eclair kernel and my computer only detects my sd card but not my phone via adb. However, I flashed back to the donut 5-29 nbh and adb/tethering work flawlessly. ADB and tethering are a must for me, but I would like to have hw3d in eclair and more importantly an eclair-optimized kernel. Is there anything I can edit in the eclair kernel to enable adb? Or possibly something I can edit in the donut kernel to have eclair hw3d, etc.? Thanks.

P.S. Running on a Vogue, voguimg 5-29, VaniljEclair, NAND
[Touch CDMA Android Development] kallt_kaffe:
Use a HEX editor or the NBH Editor that loserskater made and edit the donut NBH into an Eclair NBH. It's just a matter of changing hw3d.version=0 to hw3d.version=1.
[Touch CDMA Android Development] drewden123:
Ok thank you. Do you know why adb works in the donut kernel but not the eclair kernel? I'm just curious as to what changes from the donut kernel to the eclair kernel could have done that.
[Touch CDMA Android Development] drewden123:
So, I did this and my adb ability went away. I edited the latest donut kernel to have eclair hw3d and flashed to the edited kernel. My adb was no longer there once I connected to my computer. Why would changing the hw3d affect adb?
[Touch CDMA Android Development] kallt_kaffe:
I haven't got a clue really. Perhaps dzo knows why?
[Touch CDMA Android Development] dzo:
The only thing I can think of is that the extra hw3d devices in /dev will mess up the fixed minor number of the /dev/adb interface, I'll try also giving them fixed values (won't happen today though).
[Touch CDMA Android Development] fldash:
Running JuiceDefender? Anytime 'data' is shutoff, it kills the audio on the phone and won't come back unless you stop the audio and restart. Happens with JuiceDefender doing it, and at the end of calls (at the end of calls, it won't start playing won't you were playing before, it may start but immediately stops)
[Touch CDMA Android Development] WnG88:
Hey dzo,

Any way you can spend some time looking at the Eclair camera issue? I saw you mentioned in another thread you were busy, but getting camera fixed in Eclair would I think basically complete Eclair no?

Thanks for all the hard work so far. I love my vogue, and still telling everyone why android is amazing!
[Touch CDMA Android Development] drewden123:
Awesome. You're the man
[Touch CDMA Android Development] ejlmd:
?Clear type for Android ports

Thank you DZO for your extraordinary efforts, perseverance and talent in bringing Android to the Vogue.

The only reason I haven't switched over completely (via NAND) is that text sharpness just isn't as clear as with Windows Mobile (with Clear Type enabled). My 50 year old eyes have trouble with the small text in the browser in particular. I'm using 240x320 and have tries LCD densities 120, 113, 110, 106.

Is there any way to bring Clear Type or similar functionality to Android on the Vogue?

Thank you in advance.
[Touch CDMA Android Development] drewden123:
240x320 @ 120 is simply the clearest you will get. The only other possible solution would be to try different fonts. These can be applied via androidupdate.tar or, my personal preference, an app called "TypeFresh." One font that looks much better than the stock IMO is called Liberation. I saw it posted somewhere in the android forums and it looks much better than the stock font and it may appeal to your eyes more.
[Touch CDMA Android Development] brunes:
Has anyone noticed that the battery life in the recent kernels has been far less?

I haven't changed anything else I can think of, and my battery life (which used to last 1.5 days with Juice Defernder) is now only around 3/4 of a day - I cant go from AM to PM without plugging in.

I think this started 2-3 weeks ago.
[Touch CDMA Android Development] Dukenukemx:
I noticed this too brunes. Same thing here.
[Touch CDMA Android Development] thoughtlesskyle:
i have noticed a little bit of a hit to battery life but i can still get through a day with it, i also thought it was due to my heavy overclock
[Touch CDMA Android Development] lagloose:
Tried new kernel on Nike again. New Touchscreen Driver seems to work. Also Screen Calibration works very well.

Unfortunately Audio is still broken on Nike. :mad:

Anyone who could fix this for us Nike Users in the future ?... :)
[Touch CDMA Android Development] kallt_kaffe:
I think I've noticed the same thing. I do not have the original charger (I got the phone for free from a collegue that upgraded so I suppose he kept the extra charger). But I do have another wall-socket-to-usb charger but it's rather weak but it has been able to charge the phone overnight, but the charging is way slower now. I'm getting 200-250 with the screen turned off and less than 200 with it turned on. Before I think I got at least 300-400 mA with the screen turned on.

To see your live charge/discharge values open a terminal and type:

$ su

# cat /proc/kmsg | grep charge

Perhaps the new touchscreen driver is more power demanding?
[Touch CDMA Android Development] dzo:
Good news for Kaiser and Polaris, I've spent some time looking at power management on these devices and after lots of work I think I've found the problem. The way the uart is connected on these devices is different to vogue and the sleep settings for the uart gpios were draining power. I've set the gpios to inputs when not in use now and it makes a huge difference for me, overnight my kaiser only used 3% battery. It should also have a similar effect on polaris but I haven't tested that yet.

New NBHs and zImage on my website.

p.s. if you want to see how much power your device is using, do this from adb:

on polaris:

make sure it has resumed from power collapse at least once

echo "171 0 1 1" > /sys/class/vogue_hw/gpio

echo 0 > /sys/class/leds/green/brightness

and switch the display off.

dmesg should show the power usage every 10 secs.

mine uses about 100mA

on kaiser:

echo "157 0 1 1" > /sys/class/vogue_hw/gpio

echo 0 > /sys/class/leds/amber/brightness

my kaiser reports about 120mA (perhaps this can be improved!)

note: doing this stops the device from charging, to allow it to charge again do:

echo "157 0 1 0" > /sys/class/vogue_hw/gpio

or

echo "117 0 1 0" > /sys/class/vogue_hw/gpio
[Touch CDMA Android Development] lunigma:
RSS for Kernel Builds

I've created an RSS for the new Kernel builds using page2rss. For anyone else interested in this, here it is:

page2rss.com/page?url=it029000.massey.ac.nz/vogue/files/?C=M

It saves you from having to check back here for new builds.
[Touch CDMA Android Development] Dukenukemx:
Really, only 3%? I have to really test this out.
[Touch CDMA Android Development] Dukenukemx:
DZO, any chance you can look into why recovery mode must be selected before boot in order for a PC to see the SD card through USB?
[Touch CDMA Android Development] manu33xtro:
Good news...

Hi DZO,

Thank you very much for that very good news : I will install it right now...

I can tell you that I use the CM5.0.8 by Kallt_kaffe (with odexing files) and it's a very good build (I think the better for now) and I haven't any problems that I've said like sometimes lose network, very slow for make call,...

Great, great work !!!...

You're the best for us !

Thanks again.
[Touch CDMA Android Development] dzo:
I've put some new NBHs on my site, they have fixed minor numbers for the eclair hw3d devices which should fix adb on eclair (I haven't tried it). Also, I changed the gpio setup code for Kaiser and switched the i2c gpios to inputs on suspend for all devices. This may or may not save some power. Enjoy.
[Touch CDMA Android Development] ptcfast2:
Anyone have any issues in general with the Vogue's 22nd and 23rd Eclair specific kernel? I can't get it to boot correctly! Sometimes it will freeze at the menu prompt, other times it will actually give me an error message. :confused:

The 6/17 Vogue Eclair kernel does not have this problem (for me at least).
[Touch CDMA Android Development] ebautista:
I get that that same freeze issue in my kaiser too but for 6/22 and 6/23. But it freezes just before it gets to the press d-pad... option. Sometimes it ha garbled texts or Waiting for SD card... message.

So I went back to 06-17-2010 release. :)
[Touch CDMA Android Development] l1q1d:
Now adb works :-)
[Touch CDMA Android Development] dnessl:
Hi dzo,

I am happy to verify that, with this new kernel, adb is now working on my Vogue running myn's Warm Eclair.

Getting ADB working allowed me to do what I really wanted: to run your odex.sh, which seems to make things run a lot faster. FYI, I'm running NoMoRootFS off of SD Card with 500MB ext2 partitions each for data and system, so I had plenty of space. (It feels now like I'm running off NAND.)

Thanks again!
[Touch CDMA Android Development] ptcfast2:
Glad I'm not crazy! Anyone else having the same problem?
[Touch CDMA Android Development] ebautista:
6/22 and 6/23 Freeze Issue

6/22 and 6/23 Freeze Issue. Is this already solved? Anybody have the same problem in Vogue or Kaiser?
[Touch CDMA Android Development] loserskater:
Just got this on my Kaiser during boot:

[ 1.600007] usb_probe() io=c7806000, irq=15, dma=ffc7c000(15cd2000)
[ 1.600070] clk_get usb_hs_clk
[ 1.603165] clk_get usb_hs_pclk
[ 1.610808] usb_function_register() 'adb'
[ 1.617352] usb_function_register() 'usb_mass_storage'
[ 1.620135] msm_hsusb: functions bound. starting.
[ 1.630648] usb_mass_storage usb_mass_storage: Number of LUNs=1
[ 1.637692] usb_ether_setup()
[ 1.640302] hsusb: IDLE -> ONLINE
[ 1.643282] hsusb: reset controller c5cd1c00
[ 1.672523] usb_function_register() 'ether'
[ 1.679562] usb: notify offline
[ 1.680220] hsusb: ONLINE -> OFFLINE
[COLOR="Red"][ 1.700572] No IRQF_TRIGGER set_type function for IRQ 190 (kaisergpio)
[ 12.700065] msm_i2c msm_i2c.0: Error waiting for notbusy[/COLOR]
[ 23.680070] msm_i2c msm_i2c.0: Error waiting for notbusy
[ 23.686468] input: TSC2003 Touchscreen as /devices/virtual/input/input1
[ 23.720592] GPIO Event Driver
[ 23.723870] MSM RTC init
[ 23.726802] RTC probe
[ 23.731065] msm_rtc msm_rtc.0: rtc core: registered msm_rtc as rtc0
[ 23.736513] MSM RTC started
[ 23.739673] s5k3c1fx: probe

As you can see the lines in red take quite some time... after booting my touch screen doesnt work... Now when the phone sleeps the screen doesn't power back on... Unfortunately I'm unable to get adb setup on this comp so i cant get the last kmesg.

EDIT: Also tried reinstalling system and clearing data but same results. Reverting back to 6-22 kernel for now.
[Touch CDMA Android Development] ebautista:
I will try 6/22 but what is the panel type of your kaiser?
[Touch CDMA Android Development] loserskater:
I use panel 3.
[Touch CDMA Android Development] ptcfast2:
Good news everyone! It seems that the 25th Eclair kernel has fixed the freezing issues on boot.
[Touch CDMA Android Development] ebautista:
Yeah, I just tried it and everything went okay. Cool job by Dzo(It is always cool jobs when he does something :D)
[Touch CDMA Android Development] Quanny2000:
Good stuff...

Been awhile since i've been here last, there's been quite the updates on this wow,...

Updated to the newest kernel pretty much broke my old setup (no big deal since i had a feeling it was going to...) so i had to start from scratch..

After setting everything up i had to calibrate the screen since it was off slightly, after calibrating its completely way off (doing the tests inside the calibrate app)...

I sifted through some of these posts and saw that calibrate had to be fixed for eclair (which im running right now, with eclair 320-428, but still does it with 320-480), now with this fix is it possible something broke, causing it to not calibrate properly?
[Touch CDMA Android Development] Quanny2000:
Okay, i played around with a few things today and i fixed it (temporarily) but its still technically broken, but im not entirely sure if it can be fixed...

After downloading Rogue Tools, i noticed my screen density was at 120, i changed it to 160, and tested the calibration, 100% dead on after calibrating, saved the settings, and changed the density back to 120, tested the calibration, way off again even recalibrated with the new density...

What seems to be happening is the calibration tool seems to be hardwired to 160 lcd density, and not changing according to what the current lcd density is...
[Touch CDMA Android Development] dzo:
I think I have fixed audio input on polaris and kaiser. I noticed that the audio routing worked after making a call so I put in an extra snd_set_device rpc call and it works every time now. I also added a timeout to the audio_in/out read/write functions so if something does go wrong it can recover. This may help with vogue too. I haven't tried the new code on vogue so let me know if it doesn't work.

Noew NBHs and zImage are on my site. To test, create an sms message and attach a sound recording.
[Touch CDMA Android Development] SuperJMN:
I'll test it RIGHT NOW! Thanks, dzo. In the Polaris community we're really proud of your work. By the way, the last change to the MDDI has made 2D graphics a pleasure. I've never seen my Polaris with such a great softness!

EDIT: IT WORKS! Audio input not stopping or hanging with Voice Recorder and Shazam. AWESOME!
[Touch CDMA Android Development] osilvan:
It's awesome, now audio input is working perfect. I think it's time to flash android to nand in my polaris.
[Touch CDMA Android Development] kallt_kaffe:
For the first time ever I just made my first successful Voice Search on my Kaiser. Well done, Sir!
[Touch CDMA Android Development] lagloose:
Hi dzo,

i already stated a few days ago, that on newer Kernels Audio on HTC Nike is broken. I noticed that on 11th of June all Nike Audioparams from '....arm/mach-msm/AudioPara.c' have ben removed. Could this be the reason for broken Audio on Nike ? Is there any reason why the Audiparams have been removed ?

Thanx, lagloose
[Touch CDMA Android Development] lagloose:
ooopss, forget it...

looked at wrong place sorry :D
[Touch CDMA Android Development] Gersonian:
Question about updating kernel

I have looked for basic instructions to make sure I am not doing anything wrong, but I am coming up short.

When I update the kernel on my vogue (NAND) i typically get lots of freezing or FCs. Can one just flash the latest kernel or are there other steps that must be done? I am not running this off of an SD card, and I was under the impression that as long as I update my kernel with the proper file provided by DZO, that flashing should be straight forward. Can anyone tell me if I am missing or skipping a step?

Do I need to reinstall the system if I update the kernel?

Thanks!
[Touch CDMA Android Development] WnG88:
One thing I just noticed, and maybe this leads to something:

For some reason my phone was in 2G mode for the last 24 hours, data was connected and everything seemed to be working, I just didn't notice that it was in 2G. The battery dropped to like 90% in the 24 hours. I rebooted the phone hoping the 3G connection would come back, and it did. After about 2 hours the battery went from 90% to 65%.

Does 3G really use that much more power? Or is there something being done in the way 3G connects that is causing a huge power drain?
[Touch CDMA Android Development] brunes:
Actually I had figured this out and it turns out I had somehow gotten into a state where merely tapping the screen would cause the phone to wake up (did not have to use a button). So, all day while in my pocket the phone was constantly waking up. I reflashed and reinstalled everything and the problem went away.
[Touch CDMA Android Development] mnjm9b:
I get this sometimes, all I do is power cycle the phone and all is good again.
[Touch CDMA Android Development] dzo:
I think the important thing is the signal strength, a weak signal will cause the phone to use much more power. When I go to areas with only 2G coverage, I get much worse power consumption because the signal strength is usually also worse. The radio power consumption is handled by the ARM9 so there's not much we can do about it and it will be the same in Android as WinCE.
[Touch CDMA Android Development] kallt_kaffe:
dzo, the bluetooth phone audio seems to be broken in eclair on every kernel after this one http://it029000.massey.ac.nz/vogue/files/kaisimg-panel2-320-tilt-22-06-10.nbh

On all kernels after that one there is no sound except for some clicks when you turn BT on and off so some change between the 22nd and the 23rd seems to have broken it. Not sure if only Kaiser are affected?
[Touch CDMA Android Development] dzo:
I just pushed a couple of changes that might fix it.
[Touch CDMA Android Development] kallt_kaffe:
I'll compile a new kernel and report back asap.
[Touch CDMA Android Development] kallt_kaffe:
It did fix the problem. Thanks!

Bluetooth music is still broken though...(as it always have been with Eclair) Do think that it is a kernel problem or can it be the audio libs that is missing something?
[Touch CDMA Android Development] osilvan:
Wired headset audio problem

Hi everybody

I'm using haret to load latest kernel (zImage-27-06-10) with VaniljEclair RLS7 in a polaris device (pola100), and, I don't know if it is just me, but wired headset audio routing is not working. I've seen it working with previous kernels but I can't remember which works.

Could be a kernel issue? Does it affect to other devices (vogue, kaiser)?

Thanks in advance
[Touch CDMA Android Development] kallt_kaffe:
Try the zImage that is included with RLS7. It's got the latest fixes (added after the 27th) that fixes BT headsets audio so it's possible that it also fixes wired headsets.
[Touch CDMA Android Development] osilvan:
Thanks, i will try asap and tell you if it works.
[Touch CDMA Android Development] osilvan:
I can confirm that it doesn't work with this kernel and RLS7b

Is there any solution?
[Touch CDMA Android Development] mnjm9b:
currently using rls7b with kk's 6-30 zimage

motorola h560 BTheadset works fine.
[Touch CDMA Android Development] osilvan:
I mean wired headset, not bt
[Touch CDMA Android Development] my2sense:
Possibe issue with 01-07-10.nbh

I just tried the latest nbh (voguimg-240x320-eclair-01-07-10.nbh) and my phone is rebooting me in the middle of a phone call. I tested 3 times and same thing each time. It might not be doing a full reboot but only terminating processes since it freezes for a few seconds and then shows the boot animation.

Is anyone else getting this issue?

Edit: I reflashed everything (rom, kernel) and my vogue seems to be working as it should so far. No rebooting during calls. Must be gremlins again.
[Touch CDMA Android Development] brunes:
For some reason with this July 1 kernel I am not getting the option to hold button to upgrade anymore.

EDIT: Nm, I seem to have fried my SD card :/ Ah well.
[Touch CDMA Android Development] weezyfeezy:
07-01 Kernel was giving me tons of problems trying to boot through Haret. I would push run, and it would say "go, go go" just like usual, then just sit there and never boot into Linux. I've been playing with Android on Vogue since before there was a keyboard and I've never seen it do that before. Not sure what was going on. Reverted back to 06-27 and everything is fine running Froyo.
[Touch CDMA Android Development] bbannister0430:
Please excuse me I am extremly new to this. I have been using the zen-hero build thus far. I was having a problem getting into my call settings so I was told to use the androidtar update. I downloaded it, unziped it and I have no idea what to do next. Apparently zen-hero is old so I was told to use Sense Hero Incubus, so i downloaded it, unzipped it and I have no idea what to do now...someone please HELP...