yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] dzo:
No it doesn't hold the settings after a reboot you need to pass them as kernel parameters in default.txt. If you switch to the console (sym+0) while doing the calibration it prints some numbers, MIN=(minx,miny),MAX=(maxx,maxy),P=maxp. Write down these numbers after the the final calibration then put them into default.txt as:

vogue-ts.XMIN=minx vogue-ts.YMIN=miny vogue-ts.XMAX=maxx vogue-ts.YMAX=maxy vogue-ts.PMAX=maxp

the defaults are:

XMIN=687;

XMAX=3551;

YMIN=335;

YMAX=3823;

PMAX=600;

So only change the ones that you need. I have never tried any of these since obvoiusly the defaults work fine for me. Perhaps it is panel dependent so if people post their panel type and calibration values we could make a set of standard default.txt values.

p.s. sym+6 to get back to the ui and be careful, when in the console the ui is still active so its easy to make phone calls by mistake.
[Touch CDMA Android Development] vilord:
Martin, what would it take to add a couple more kernel commands?

I'm thinking that since 1.5 is working pretty stable, I'd like a vogue-kb=0 (or something) option that causes the cam button to rotate only and not load the keyboard.

Edit: <snip> I guess cal options are already there :)

Thanks!!!
[Touch CDMA Android Development] frad:
Hi DZO,

Just a quick question. Do you plan on migrating to 1.5 in the future? So far I find your 1.1 build the most stable I've tried, but am also a fan of the 1.5 keyboard.

In any case thanks for your build... its solid. :)
[Touch CDMA Android Development] dzo:
Yes, I just want to get the camera working in 1.5 first.

Also, srwalter told me he has figured out the gps rpc calls, so expect working gps some time soon.
[Touch CDMA Android Development] frad:
Phenomenal!

I appreciate you keep us in the loop. Thanks again.
[Touch CDMA Android Development] Ideal2545:
gps rpc calls?

i just came
[Touch CDMA Android Development] vilord:
mssmison tells me he might have some things working for the camera, details soon
[Touch CDMA Android Development] dzo:
The gps hardware is handled by the arm9 so getting it to work involves figuring out the remote procedure calls (rpc calls).
[Touch CDMA Android Development] margosmark:
Hey I tried to get the kernel messages for Bell SMS (as sometimes it work sometimes it don't (majority))but I seemed to fail, i tried finding clearer instructions on how to do this, can some one elaborate or am i just doin it wrong ;)
[Touch CDMA Android Development] oxsolid:
sprint panel 3 htc vogue auto calibrate keyboard settings (vilords hires intrid)

I use panel 3 for sprint (i added the following text right before the ppp.username):

vogue-ts.XMIN=431 vogue-ts.YMIN=351 vogue-ts.XMAX=3727 vogue-ts.YMAX=3759 vogue-ts.PMAX=374

works perfectly for me, this sooo much more accurate than the default , check "dev tools"-> "pointer location" to see if it lines up for you

i'm using vilords hires intrid, i don't know if that makes a difference.

thanks dzo for the info on how to read calibration settings.

_______________________________________________________

EDIT (comparing results to vilords results in the next post):

mine

I use panel 3 for sprint (i added the following text right before the ppp.username):

vogue-ts.XMIN=431 vogue-ts.YMIN=351 vogue-ts.XMAX=3727 vogue-ts.YMAX=3759 vogue-ts.PMAX=374

vilords

I've got a panel type 1 US verizon phone (bought the first week they came out), my settings are

vogue-ts.XMIN=447 vogue-ts.YMIN=383 vogue-ts.XMAX=3743 vogue-ts.YMAX=3791

Our settings are really close (and they probablly are the basically the same), I noticed when i was setting up mine that the numbers incremented by +16 or -16 in any direction. I was never able to get a perfect alignment by tapping the corners, but i was able to manually adjust the settings in the default.txt. infact i was never able to get below YMIN=383 (with the stylus tapping method), but i found that inserting 351 directly into the default had the best results (i manually tweaked the other settings as well)

_________________________________________
[Touch CDMA Android Development] vilord:
I've got a panel type 1 US verizon phone (bought the first week they came out), my settings are vogue-ts.XMIN=447 vogue-ts.YMIN=383 vogue-ts.XMAX=3743 vogue-ts.YMAX=3791

They are close to yours but not the same. It doesn't have anything to do with the panel, because they are totally separate pieces. The panel is attached to the main board, the touch screen is attached to the front shell.

EDIT: Oh yeah, my phone is verizon panel type 1. The touchscreen and casing is from an alltel phone. There is definitely no correlation between panel type and touch screen numbers
[Touch CDMA Android Development] vilord:
Martin, have you considered nilfs for the data partition filesystem? It is log-structured so it won't burn the SD card and also is much more power failure safe. And it supports loop devices! (unlike yaffs, jffs2/jffs, etc)

I read that others are using it on ARM, but I'm having trouble cross-compiling the usermode tools as it is asking for uuid-dev libraries. I have the libraries installed, but it still gets the error.

-----

RE the bell SMS problems...

mark, do you have adb working?

If so, when hook up to your pc, type "adb logcat -b radio > radio.log"

then send yourself some sms's

after about 30 seconds hit ctrl-c, then send me or srwalter the radio.log file (PM me for email). Don't post it on here as it contains your phone number and the sender's phone number encoded in the sms string.

Then I can work with srwalter to get this fixed

-Jesse
[Touch CDMA Android Development] katmandu421:
I tried this with the suggested values and I was unable to swipe my home screen to change "panels". So I rebooted and got my own calibration numbers and got the same results...unable to swipe, and even swipe down my notification bar. Funny thing is, when I go to pointer location, everything looks accurate. I also tried recalibrating but it doesnt seem to take once you've defined it in default.

Anyone? Bueler?
[Touch CDMA Android Development] vilord:
katmandu, are you specifying a PMAX value? Since swiping happens from anywhere on the screen, the left/right/top/bottom bounds should affect it.

Try taking that option out.
[Touch CDMA Android Development] oxsolid:
PMAX Definition?

vilord, i specified a pmax value (374) and it works fine for me; but it is the one setting i don't quite understand, does anyone know what it means?
[Touch CDMA Android Development] katmandu421:
Wow, what an oversight on my part. I bet it works when you state "PMAX" instead of "PMIN"

Meu dios.

Thanks for the heads up, everything looks good now. 3 step boot process (calibrate, max apps and togga) is now down to 0....awesome work guys!!
[Touch CDMA Android Development] katmandu421:
*Crossing fingers for GPS in time for the mid July road trip* :p
[Touch CDMA Android Development] Sublimeinlife:
when gps is enabled would the phones gps need to be unlocked like when flashing new roms or would android bypass this? Im curious because I never flashed a new rom because ive been pretty much exclusively using android since i got the phone
[Touch CDMA Android Development] grktaurus83:
Same here, actually. I'll be driving from the west coast to the east coast in the middle of July.

If you've been using Android, that means you didn't get your phone all THAT long ago and your radio is already upgraded. There shouldn't be anything you would need to flash in that case (but you should check your firmware version to be sure). The gps capabilities are there in the radio, we just can't talk to it just yet. Once we can get Android to issue commands and understand the results we'll be set.
[Touch CDMA Android Development] Sublimeinlife:
Im on radio version 3.37.78 but i was under the impression that in order to use the gps with anything other than verizon navigator(forgot to mention i was on verizon) I need to run an unlocker for windows mobile
[Touch CDMA Android Development] longjohn1980:
Katmandu421 could you post your Default.txt with the screen calibration ect. please? Thanks in advance.
[Touch CDMA Android Development] katmandu421:
I don't think you'd want mine. The performance of my phone at this stage is crap. I dont think it's the default.txt butI also dont want to pass along anything that may be the culprit.

I would suggest just getting your own numbers, because I think it comes down to personal usage and preference. Just open your keyboard then hit Sym and 0 to see the command prompt looking screen, hold down end key (the screen wont change from the command line) and touch the corners as usual for calibration. You'll start to see lines getting written to the command line screen. Once done, close the keyboard and note the values. Each line has it's own, and you'll see variation between them. Either it gets rolling averages of the values or just give one realtime at each interval, not sure, but I noted the last reading and used that for my min,max x and y. You'll have to open the keyboard up and hit Sym 6 to exit the command line screen and get back to the UI. Then just insert your numbers for the values in the default.txt lines from a few pages ago, and someone has in their sig I've seen. Sorry, forgot who :)

Cheers
[Touch CDMA Android Development] hexto:
Shouldn't make a difference with Android. You have a GPS compatible radio which should be all you need.
[Touch CDMA Android Development] hexto:
Any progress on MMS?
[Touch CDMA Android Development] craig0r:
Does this mean we should be looking at the OMAP-Linux tree to get the hsuart driver?
[Touch CDMA Android Development] dzo:
No, definitely not, it will just be a small change needed, I just don't have time at the moment to track it down.
[Touch CDMA Android Development] craig0r:
blast, thought i was onto something.
[Touch CDMA Android Development] prairiefire:
I seem to recall that some people were having issues with "bad sms encoding" happening from time to time while using vilord's 1.5. I have started experiencing this also. Apologies if this has been mentioned but the only time I get it is if the radio is off when the text arrives initially (say while i'm in 'airplane' mode) and then connect with the network again. I can reproduce this every time (i.e. get the bad sms encoding with a text sent while i'm in airplane mode). I have also tried sending a text to my phone while in WinMo (on airplane mode) and then starting up android and get the same result. A proper SMS message is received every time i have the phone on and communicating with a tower when the message is sent.

Oh and thanks everyone for the tips on calibration. I didn't realize i had to hit sym+0 before holding the end call button and pressing the corners of the screen. My calibration numbers are:

vogue-ts.XMIN=431 vogue-ts.YMIN=367 vogue-ts.XMAX=3711 vogue-ts.YMAX=3791 vogue-ts.PMAX=411.

my panel type is 1 and i'm on Bell's network.
[Touch CDMA Android Development] hexto:
After so many times of trying every Android for the Vogue possible my phone started acting weird. Slow and choppy mostly and the power wouldn't always work so I decided to start fresh and delete everything.

After deleting everything I downloaded Android 1.1 from Martin's site but I can't get it to work now. I run haret and it boots up but gets stuck saying "failed to extract Date Image/bin/sh: can't access tty: job control turned off"

Anyone know what's going on with my phone/sd card?

I've tried earlier versions I had used in the past, editing my default.txt (which I never have to do. Data always works for me) and different zImages but nothing seems to work.:confused:
[Touch CDMA Android Development] vilord:
I'm driving from Vegas to Boston in mid-august... here's hoping GPS has stabilized by then, I don't want to have to switch back and forth from WM to Android to get GPS and my emails :)

prairiefire: There is a new initrd.gz for download that includes an option in default.txt set ril.fixsms=1 next to your ppp configuration items and you should be good to go.
[Touch CDMA Android Development] craig0r:
If I were to venture a guess, I would say that you don't have a valid data.gz file on your SD card for Android to extract at first boot. (I'm assuming you made a typo when you said "Date Image") Delete whatever data.gz and data.img files are on your SD card, re-download dzo's files, and copy data.gz to the SD card again. Of course (I would hope I wouldn't have to mention it at this point) make sure all files are in the root of the SD card.

If that fails, try another SD card, as yours may be corrupted.
[Touch CDMA Android Development] hexto:
Can my sd card be corrupted even though it works perfectly in WinMo?
[Touch CDMA Android Development] mssmison:
yes. I have an sd card that works perfectly fine in winmo but does not work in android.
[Touch CDMA Android Development] hexto:
D'oh. Its weird cause it was working perfect until I decided to start fresh with a new data.gz. Would it help if I reformat the card and start fresh?
[Touch CDMA Android Development] vilord:
It might.

Have you tried starting fresh with 1.5 from the "ion" thread? Theres a lot of new stuff beyond just the newer system there.
[Touch CDMA Android Development] cr2:
hi. i see that the GPS rpc driver was committed to the vogue branch at linuxtogo.

can somebody tell about its performance ?

The interface looks similar to MSM7201A, but there are some minor API differences.
[Touch CDMA Android Development] hexto:
I haven't because I wanted to get a working data.img so Google apps would work. Thats why I started fresh. Google apps just stopped working one day and I was using 1.5 Ion and DZO's data.img. All was perfect for about a week then it started acting up.
[Touch CDMA Android Development] mssmison:
you can use the latest kernel from vilord with either mine or his ion build with a fresh data.img and you'll be able to get google apps, without using a 1.1 image first.
[Touch CDMA Android Development] srwalter:
Dunno what you mean by performance. I do know that the code doesn't work as-is on a Kaiser, which is MSM72xx, right? The code is still experimental, but for me I can acquire a lock, close Maps, get a new lock, suspend/resume/etc without problem.
[Touch CDMA Android Development] bangout:
Quick question do I need to fully unlock my gps to get it working on android? I have radio 3.37 on verizon. And thanks for all the wrk
[Touch CDMA Android Development] dzo:
I've just put a 1.5 build on my site. It's mostly the same as vilord's ion build with a few changes, it doesn't auto connect to the network and includes the experimental gps support (thanks to srwalter).

If you don't want to try gps make sure you switch it off before starting google maps.

I used my 1.1 data image and it upgraded fine but you may have to start with a clean data.img so make sure you sync your contacts first.

I'm still working on the camera support for 1.5 so that doesn't work yet.

If you are already using the vilord ion build then you probably don't need to change. My build won't boot with his initrd though.

Get it here:

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

Martin
[Touch CDMA Android Development] Ideal2545:
dzo release 1.5! excited to try it out!

dzo, are you planning to assist with the gps support or are you mainly focusing on getting other functionality working?

edit: sorry last question, does your 1.5 release have the gps changes from 45 minutes ago that srwalter updated?

have i mentioned your the best :P
[Touch CDMA Android Development] vilord:
my initrd has been updated with the missing file, your build is basically identical to mine. I guess I'll take that as a compliment!

I also updated my initrd to correctly dial on a gsm phone (using ppp-on-dialer, not setupmodem.sh) and it also will create its own data.img, so no need for a data.gz anymore.

And it now is capable of creating backups of you data file at boot!
[Touch CDMA Android Development] dzo:
Yes, I have been helping Steven with the GPS though I don't want to take any credit for it, it's all his work really. I'm working on the camera when I get any spare time.

Yes, my 1.5 does include the latest GPS changes now (it didn't 5 mins ago).
[Touch CDMA Android Development] vilord:
New initrd posted. Smaller and makes its own data.img files if there isn't one there.

Supports built-in backup (push a key during startup when prompted)

Supports gsm dialing (in ppp-on-dialer)

Supports systems that point at initrd for libcamera.so and libgps.so.

Includes the latest libgps.so from srwalter's page.

Get it here: http://code.google.com/p/vogue-android/downloads/list
[Touch CDMA Android Development] vilord:
got an crash...

Martin, I'm not sure if this is old or new, but the rpc server seems to have died during boot up on this kernel... dmesg log attached.

The phone kept booting after the error, it didn't seem to mind, and it is now running great.
[Touch CDMA Android Development] Michel82:
Sorry to ask my question over here, but earlier builds were always compatible with multiple phones. What would be the chance of this vogue build to work on my polaris?
[Touch CDMA Android Development] mburris:
autobackup option during bootup

Hey I didn't see that Vilord had already posted an initrd with the autobackup script init. Please disregard this message.
[Touch CDMA Android Development] frad:
Great build... love 1.5.

I noticed that while I have internet access, I can't seem to sync with Google.... so no contacts or market place. Anything that requires my official google sign on. When I go to sign on nothin happens... no window pops up or anything. Any one notice this?

One other thing. And I've noticed this consitently... I can't ever seem to get the data image to extact fine the first time I run Haret. I always copy the files to my SD card... run haret... the data file partially extracts and then hangs.

I then restart... delete the partially created data image, and repeat the process. And the second time it always works.

Any clue on that issue? Thanks.
[Touch CDMA Android Development] foci:
I am using 1.5 that I just downloaded today, love it... however I cannot get internet to work.

I tried loading IE on WinMo before loading up android, and this does make a 3g icon appear at the top (without loading IE first, no 3g Icon appeared) but I still no not have internet access. I use Sprint, is it possible the text in my default.txt needs to be edited?

This is what I have (I did not changed anything from the .zip i downloaded)

set RAMSIZE 0x08000000

set MTYPE 1667

set KERNEL zImage

set initrd initrd.gz

#

# 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 3, 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

# mddi_client_vogue.vsync - Use hardware vsync, default is 1 but should be 0 if

# panel_type is 0

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

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

# 2 is faster but uses more power

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

#

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

# US Sprint vogues usually have type 2 I think.

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

set cmdline "ppp.username=focisname@sprint.com ppp.password= mddi.width=320 mddi.height=428 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=0 mddi_client_vogue.vsync=0 no_console_suspend"

boot
[Touch CDMA Android Development] jdemar:
did you run the modem app? In 1.1 you run togga, but in 1.5 you run the modem app.
[Touch CDMA Android Development] foci:
and that solves it lol, thanks for the help.
[Touch CDMA Android Development] suanccd:
I am having difficulty booting the new version. I have tried both android-1.5-25-06-09 and android-1.1-18-06-09. Most of time, it stop when extracting the data.gz. After I tried to extract the data.gz in my pc and copy the data.img file to sd card, it will go further and stop at the "android" logo.

I was able to use the android-1.1-28-04-09 very smoothly. I saw in previous post dzo mentioned changing sd driver around end May. I am not sure whether that might be the reason.

I have also tried with msm_sdcc.msmsdcc_fmax=20000000 as suggested by dzo and got the same error.

Any ideas? BTW, I have a 2G sd card by Kingston.
[Touch CDMA Android Development] vilord:
New initrd.gz posted to http://code.google.com/p/vogue-android/downloads/list

This will repair any broken /data/app permissions

This will do a filesystem checks on your SD card, so no more wiping out everything

Suggestion to anyone having problems with google apps, delete your data.img and delete data.gz and just run it, it will create a blank data.img for you...

If that doesn't work, use all stuff from google code above.

EDIT: Reuploaded at 1:15pm pacific time, now will check for a ppp.nostart=1 option in your default.txt file, so if you don't want to automatically start up the ppp connection, set that option.
[Touch CDMA Android Development] vilord:
Delete data.gz and data.img and use the android-1.5.

It will create a data.img for you without extraction errors.

Please note that it will take about 5 or maybe even 10 minutes to start up the first time.
[Touch CDMA Android Development] cr2:
Kaiser is msm7200, and may use another rpc PROG number, which depends on the AMSS version (like it is already the case for ADSP)

I have documented the GPS PDSM API used on RAPH100 (AMSS 52XX, CPU MSM7201A) at http://www.htc-linux.org/wiki/index.php?title=MSM_RPC , PROG=0x3000005b.

There are some differences in the structure order and number of members, but i

think we can unify the GPS driver, so it does not depend on the AMSS version.
[Touch CDMA Android Development] suanccd:
Thanks for the suggestion. I tried your 1.5 release and waited 10 minutes during the first time boot. I then rebooted to winmo and found a 16M data.img file. Could it be possible my sd card is not fast enough?
[Touch CDMA Android Development] vilord:
That could be the problem... it is trying to create a 128M file...
[Touch CDMA Android Development] vilord:
Try downloading everything off your SD card and formatting it, then put back just the android stuff (don't use a data.gz) and see if that goes faster
[Touch CDMA Android Development] hexto:
I downloaded DZO's new 1.5 and reformatted my card and now when I run haret it starts to run the gets stuck on "Please wait... extracting Data Image" which is different than the previous errors I've gotten but it still won't boot up. Guess I ought to get a new card

Update: I tried running thedude's complete file and it ran just fine so I guess my card is good. Still can't figure out why I can't run this new 1.5
[Touch CDMA Android Development] vilord:
Okay the initrd.gz on google code has been updated yet again.

This time is a major update with repaired bell SMS (thank you Martin), new libgps (thank you Steven), and statically linked filesystem checks (that was me).

On my phone, it took about a minute to create a new data.img (*don't use data.gz!!!*)

You'll want to use martin's new zImage from here
[Touch CDMA Android Development] Ideal2545:
whats updated with this gps?
[Touch CDMA Android Development] moekind:
works perfectly

thanks alot for the hard work!

2 small requests

1.) can we get a program that rotates the screen

(because sometimes it gets stuck in landscape mode)

and

2.) An auto calibrater program ( im having a hard time calibrating my screen

to make it perfect )

Thanks

Tc
[Touch CDMA Android Development] vilord:
It is just bringing in Steven's updates. Here is his post from another thread: