yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] dzo:
I can't see why that would happen, the initrd and tinboot have nothing to do with the camera. My guess is that it's a timing problem in the adsp irq handler that shows up only on some hardware and then only intermittently. You could try enabling adsp debugging by changing the #if 0 to #if 1 near the start of arch/arm/mach-msm/audio/qdsp4/adsp.c. Then look at /proc/last_kmsg after a crash to see exactly what it's doing.
[Touch CDMA Android Development] dzo:
I put that there because otherwise the ts sometimes starts before the i2c subsystem is ready. I just pushed a fix that keeps the thread running which should fix the initrd menu.

The kaiser ts doesn't power down correctly between samples (and possibly when asleep), I've been trying to fix it but it seems to be different to polaris and kaiser. There needs to be a command that has PD_POWERDOWN

in it somewhere.
[Touch CDMA Android Development] kallt_kaffe:
I'm going nuts on this.

- Your NBH - No freeze

- Your zImage (same builds as the one in the NBH (I have checked)) using HaRET - Freeze

- My NBH using _your_ zImage - Freeze

- My NBH using my own compiled kernel - Freeze

The thing is, it's not intermittent. It freezes every single time unless I use your NBH.
[Touch CDMA Android Development] kallt_kaffe:
Here is my version of this NBH: http://it029000.massey.ac.nz/vogue/files/kaisimg-panel1-320-19-05-10.nbh

I've used this zImage: http://it029000.massey.ac.nz/vogue/files/zImage-19-05-10

My version freeze on camera exit, yours do not.

They are not binary identical. Would you consider posting your initrd.gz so I can try that. If it is the initrd.gz it would explain why it also freezes if you HaRET boot.
[Touch CDMA Android Development] mnjm9b:
did you try the 21-05-10 zImage?

http://it029000.massey.ac.nz/vogue/files/zImage-21-05-10
[Touch CDMA Android Development] kallt_kaffe:
I've tried the latest code but compiled it myself and still no go with the camera freezes... However it does fix the slow installation menu problem.
[Touch CDMA Android Development] kallt_kaffe:
Oh, and by the way. /bin/MAKEDEVS in bootenv, what is it for? It doesn't seem like it's being used. The changes you commited here isn't used as far as I can tell. Not even with your NBH. We would also have a /dev/input/event2 and 3 if the script had been used.
[Touch CDMA Android Development] dzo:
The /dev entries are created by udev in android using /init. Since that isn't running in the installer we have to make them by hand, it's not ideal because the minor numbers may change. Once android starts, it takes over managing /dev so you won't see the entries created by MAKEDEVS.

I've just put the exact initrd I used on my site but I don't think it will help you much.
[Touch CDMA Android Development] mroiler:
Screen Calibration

I recently installed Android HTC on my touch from bell. I got it to boot into android but after I calibrated the screen I would click done and after a minute the screen would go black but the backlight was still on. It won't do anything else. I installed it on my storage card(4 gb)
[Touch CDMA Android Development] kallt_kaffe:
Believe it or not, but with your initrd.gz it works...

EDIT: And btw, the extra debugging in vouge_rpc.c, was it left enabled by mistake or for a reason?

EDIT2: Your initrd.gz contains logo.rle which isn't present in: http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/bootenv.git;a=summary Can't see why that would have any effect but it works perfectly now with your initrd.gz, even when I compile the zImage myself.
[Touch CDMA Android Development] kallt_kaffe:
logo.rle is used in mfm_fb.c and mfm_fb was changed twice between 8th of Mars and the 11th of Mars which was the time frame when the camera exit freeze started to appear. Might still be a timing issue like you suggested erlier where the presence of logo.rle have an effect on the timing?
[Touch CDMA Android Development] Jiggity Janx:
When I updated from 29-4 .nbh to 21-5 .nbh it (see sig block) wouldn't load correctly. It gets most of the way through the boot animation and then goes to a black screen with a cursor on it. Backed down to 29-4 and no issue.
[Touch CDMA Android Development] loserskater:
I'm looking through the auto detect panel type for the vogue and polaris...

How did you find these numbers:

#define GPIO_PANEL_ID0 66
#define GPIO_PANEL_ID1 67

I kind find a GPIO table for the vogue, and the one for polaris doesn't have very much info. The kaiser table has probably the most info, but I don't have anything to compare it to...

I'm just trying to find a way of auto detecting panel type (and possibly keyboard) for kaiser so there's less nbh's to deal with.
[Touch CDMA Android Development] mroiler:
Screen calibration

I recently installed Android HTC on my touch from bell. I got it to boot into android but after I calibrated the screen I would click done and after a minute the screen would go black but the backlight was still on. It won't do anything else. I installed it on my storage card(4 gb)
[Touch CDMA Android Development] loserskater:
You're probably using the tattoo build. Look through that thread and you'll see others are having the same problem. Try a different build for now, and follow that thread for any improvements on the issue.
[Touch CDMA Android Development] mroiler:
Screen calibration

Where can I get a different build I was looking on that source forge page and I couldn't find one with a androidinstall.tar file like tattoo had.
[Touch CDMA Android Development] kallt_kaffe:
Well I can confirm that the touchscreen is way more responsive now. In fact it is responsive that any screen that also reacts to "slides" is close to impossible to use with using the fingernail or the pen. Using the finger 9 times of then is interpreted as a slide. Is there an easy way to tweak the sensitivity?
[Touch CDMA Android Development] loserskater:
HERE or HERE or HERE are just a couple.
[Touch CDMA Android Development] thebulletfromhell:
Actually, if you use a recent kernel and the new tattoo package, the problem is gone.
[Touch CDMA Android Development] Jiggity Janx:
Believe the above statement only refers to nand installs. I and many others are still experiencing problems with the recent kernel and tattoo package when running off sdcard.
[Touch CDMA Android Development] dzo:
I made a few changes to the camera driver for vogue, it should work much better now, especially in low light. The white balance should also be better.

New kernel and NBHs in the usual place.

I also made the same change to the kaiser/polaris drivers but haven't tested them yet.

Let me know if it works for you.
[Touch CDMA Android Development] JM-PDA:
Dzo,

Thank you for the Camera driver update!

Just finished downloading the "voguimg-240x320-eclair-24-05-10.nbh".

Will comeback tomorrow with an update.

Thanks again!
[Touch CDMA Android Development] milanche:
Actually the problem is also gone for SDcard users if you use latest kernel AND initrd-22-05-10.gz which you can find on dzo's site.
[Touch CDMA Android Development] Dukenukemx:
Dzo, have you included kallt_kaffe's GPS fix into the latest kaiser kernel?
[Touch CDMA Android Development] kallt_kaffe:
Yes it is included the in the offical source.
[Touch CDMA Android Development] l1q1d:
@dzo: Could you update the kaiser/polaris nbh with new changes?

Thank you :D
[Touch CDMA Android Development] kallt_kaffe:
For information. The new initrd.gz also fixes the Kaiser Camera freeze when HaRET booting. I've tried it myself.
[Touch CDMA Android Development] SuperJMN:
I second that! Otherwise, I will have to flash Windows Mobile again to run HaRET with the new zImage :P
[Touch CDMA Android Development] dzo:
I don't like putting things on there that aren't tested, but if you insist....

p.s. There are only a few differences between the NBHs, you could always use a hexeditor to make a polaris NBH from a vogue one. Just change the machine type, the cmdline and the load address.
[Touch CDMA Android Development] SuperJMN:
Oops, I didn't think it was so easy! Next time, I will make myself a .NBH with my hex tools. By the way, thanks for this update! I will give you feedback as soon as I've tested it.
[Touch CDMA Android Development] vilord:
What about writing a simple java tool for this? Then you could just distribute one nbh (instead of 30) and the java tool, and folks could just pick their hardware type, screen type, resolution, etc and it'd convert it for them?
[Touch CDMA Android Development] kallt_kaffe:
It has been suggested before and I hope someone make one. Just to support all the variants for the Kaiser requires 90 different NBHs. I don't have the GUI programming skills to do it. I could propably make a command line tool if I really tried but by the time I would have gotten most of the bugs out of it I am pretty sure someone else would make it obsolete with a nice GUI application anyway so I won't bother.

You would then just make one NBH with all the possible kernel parameters present and then a tool (with a hanful decent presets for the newbies) to set it up.
[Touch CDMA Android Development] JM-PDA:
Dzo,

I just went to try the camera for the first time:

- Running Incubus Eclair Lite

- Running System and Data on Nand

I get a "Sorry... the application Camera (process com.android.camera) has stopped unexpectedly. Please try again"

Tried several times and got the same message.

I will post a logcat file as soon as I get to work.

Thx...
[Touch CDMA Android Development] Maranevim:
camera works only on Donut
[Touch CDMA Android Development] JM-PDA:
Ahhh!

Thank you for pointing that out.

Don't know what I was thinking.

Had not finished my morning coffee cup yet. :)
[Touch CDMA Android Development] loserskater:
So the camera doesnt work perfect in low light but it seems to work a little better. I cant remember exactly how bad it was with the previous nbh but it looks better none the less.

On another note... Im not sure if it's a fluke but I seem to have tower location... Ive been using vilords tattoo for a few days, and havent had it before. I flashed this new nbh and the weather showed my current location and in google maps tower location seems to be working... But in the browser when I go to google, it says location unavailable. I DO NOT have wifi on (I made that mistake before) and I also have GPS off. Is there anything else that might be giving me false hope?
[Touch CDMA Android Development] mrkite38:
Someone else had reported this in the gps thread previously... I'm sure kallt_kaffe will have some questions for you. :)
[Touch CDMA Android Development] l1q1d:
i test on polaris and it works great!
[Touch CDMA Android Development] kallt_kaffe:
BUMP! Working with the pen works mostly fine but using the touchscreen with the finger on the Kaiser is now close to impossible. A "tap" is 9 times of 10 treated as "slide". Bringing down the notification area with your finger is close to impossible. I suppose there should be some timeout before a "tap" is considered to be a "slide"? Very exact small taps (like with the pen or the fingernail) usually works but tapping with your finger to select something is a real challenge. Don't even think about trying to do something while driving (not that you should anyway).
[Touch CDMA Android Development] loserskater:
I havent had the "slide" problem nearly that much, maybe 1-2 times out of 10 and thats with my finger. I find that sometimes i need to tap and hold for a half second (not long enough to bring up the menu, obviously). When i tap quickly is when it slides.
[Touch CDMA Android Development] krylon:
When connected to USB, I get continuous USB disconnect and reconnect drum sounds. It states "USB Connected" in the task bar every few moments until I unplug the USB. Anyone experiencing the same issue?
[Touch CDMA Android Development] mrkite38:
Using eclair and windows? known issue.
[Touch CDMA Android Development] inertone:
after a while it should connect
[Touch CDMA Android Development] mfpreach:
I tried searching the thread but didn't fin exactly what I wanted.

I just updated my kernel and noticed that the long press of the camera button no longer takes me back to my home screen.

What has this function been changed to, i can't figure it out.

Thanks.
[Touch CDMA Android Development] mfpreach:
I got it, medium press home thanks.
[Touch CDMA Android Development] dzo:
Yes, and now the leds on the call buttons let you know when you can release the cam button to go home.
[Touch CDMA Android Development] kallt_kaffe:
dzo, I know you propably are busy but there are a few loose ends that I've mentioned but I'm not sure if I managed to get your attention or if my posts drowned in the thread.

1. The initrd.gz issue. With your initrd.gz the Kaiser Camera works, both in NAND and with HaRET boot. The one available with the official haretinstall.zip package and the one in the bootenv freezes after using Camera app when it starts redrawing the launcer screen. This is not intermittent. It happens every single time unless I use your initrd.gz. Tried NAND, HaRET, vilords tattoo, Myn's Warm Donut. The results are the same, always. I have not tried adding the logo.rle to the bootenv package but that may be the key.

2. Kaiser (and possibly also Polaris?) touchscreen with latest changes. I'm not the only one having problems with it: http://xdaforums.com/showthread.php?t=660158&page=12

It really instantly assumes a "slide" unless you are really careful. I'm not sure if somethings is broken or if it is just a tuning issue. I've tried to understand the code but I've failed.

Not really important:

(3. The new logging in vogue_rpc.c. Mistake or intentional?)
[Touch CDMA Android Development] dzo:
1. I've no idea why this would happen, the git repo should be up to date, is /init the same in both.

2. In commit 023612a111d7354c9e69c869de62a261a0bece09 can you try moving the enable_irq back and getting rid of the msleep in tsts_thread. If this doesn't work try reverting the entire commit.

3. Mistake, but it can be helpful sometimes.

Hope this helps
[Touch CDMA Android Development] kallt_kaffe:
The git repo lacks the logo.rle that is present in your initrd.gz. That is the only difference I've found. But on the other hand I haven't done any binary compares but I think the files sizes are the same.

I'll try and report back. How about the ABS_PRESSURE that was calculated before but is now hardcoded to 255.
[Touch CDMA Android Development] thoughtlesskyle:
i must say camera in the new nbh on vogue is much improved
[Touch CDMA Android Development] mnjm9b:
just to add my two cents...

I built my own nbh's using both the zImage from dzo as well as one from source. each time I used the initrd.gz from bootenv. and I have not had any of the freeze issues. camera works great.

I am using 320 panel2 tilt with a couple of custom parameters for no data and battery capacity.

I haven't tried HaRET though...(can't bring myself to flash winmo again)

Edit: just an extra thought... I never changed the hw3d setting when going from eclair to donut. so it is still set to '1'
[Touch CDMA Android Development] kallt_kaffe:
Perhaps it matters what panel you have... It's really wierd but I've spent lots of time trying to get it to work. Different compilers, different kernels etc... But the only time it worked, ever, was when I replaced the initrd.gz with the one from DZO uses (the one with a logo.rle file in it).
[Touch CDMA Android Development] kallt_kaffe:
The enable_irq and msleep changes did not help but I brought back (and simplified) the "p" calculation and it seems to have fixed it.

my htckaiser-ts.c now looks like this:

static int report_event(struct ts_data *d,int x,int y,int p1,int p2) {
int p,penup=0;
int i,vx,vy,key;
if(p1>0)
p=(x*p2/p1-x)>>3;
// p=1;//((((x*256)/4096)* (((p2*256)/p1)-256))>>7);
else p=0;

// if(gpio_get_value(KAISER_GPIO_PENDOWN_INT)==0)
// p=1;
// printk("(%d,%d,%d, %d)\n",x,y,p,gpio_get_value(KAISER_GPIO_PENDOWN_INT));

if(p<PMIN) p=PMIN;
if(p>PMAX) p=PMAX;
p=((p-PMIN)*256)/(PMAX-PMIN);

if( p>0 && machine_is_htckaiser() && !gpio_get_value(KAISER_GPIO_KEY_CAM_DEEP)) {
printk("TS Calibration %d %d %d %d %d\n",x,y,p,p1,p2);
if(x<2000)
XMIN=x;
if(y<2000)
YMIN=y;
if(x>2000)
XMAX=x;
if(y>2000)
YMAX=y;
} else
if (p>0 && p < 256 && x>0 && y>0 && x<ADC_MAX-1 && y<ADC_MAX-1) {
if(x<XMIN) x=XMIN;
if(x>XMAX) x=XMAX;
if(y<YMIN) y=YMIN;
if(y>YMAX) y=YMAX;
x=((x-XMIN)*240)/(XMAX-XMIN);
y=((y-YMIN)*320)/(YMAX-YMIN);
if(machine_is_htckaiser() && gpio_get_value(KAISER_GPIO_KBD_OPEN) && rotate_flips) {
x=240-x;
y=320-y;
}
input_report_abs(d->idev, ABS_X, 240-x);
input_report_abs(d->idev, ABS_Y, y);
input_report_abs(d->idev, ABS_PRESSURE, p);
// input_report_abs(d->idev, ABS_PRESSURE, 255);
input_report_key(d->idev, BTN_TOUCH, 1);
input_sync(d->idev);
} else {
penup=1;
ts_pen_up((int)d);
}
return penup;
}

EDIT: I've attached a test version here if anyone wants to try it out: http://xdaforums.com/showpost.php?p=6591176&postcount=117

EDIT2: Seems to work very well now, at least for me. dzo, do you want me to push the changes I've made?
[Touch CDMA Android Development] 4ultratech:
Latest zImage problems

I just downloaded the latest zImage-24-05-10 and initrd-22-05-10 and installed them.

Was running the provious release with not problems.

Now my phone does not ring with incoming calls, it rings until it goes to voicemail

and never rings on the phone.

Outgoing calls work fine and text work fine.

Have a Vogue VX-6900 on Verizon Wireless running Myn's RLS5

Anyone else having this problem? any ideas?
[Touch CDMA Android Development] 4ultratech:
Text was working now it is not receiving incoming text.
[Touch CDMA Android Development] my2sense:
+1. No more purplish tint to all my photos however the quality is still not that great but I don't know if that's just a limitation of the hardware itself.

Thanks to whomever fixed the color. Great work!
[Touch CDMA Android Development] Dukenukemx:
The touch screen is working normal as well. Also, don't know why but the response time is much faster. About 90% of my actions are nearly instant. Don't know if that has something to do with the kernel or the Kaiser version of Myn's Warm Donut.
[Touch CDMA Android Development] WnG88:
Deleted post...
[Touch CDMA Android Development] mrkite38:
edited accordingly.
[Touch CDMA Android Development] tatnai:
dzo, did we lose the triple camera button function with the last update (24-5-10), or is it just my phone? I can now only use it for back, not home or apps menu. just me?
[Touch CDMA Android Development] dzo:
No, it should work, hold it down until the front leds go on for home, keep holding for apps menu.
[Touch CDMA Android Development] tatnai:
nm, my data file is corrupt. new data file and all is peachy.
[Touch CDMA Android Development] Dukenukemx:
I found a strange bug. When I leave my phone connected to my PC, when it goes into suspend mode, my phone now supplies power to other USB devices.

I know this because my usb mouse has a LED light that is on, but very dim. When I unplug my phone, the light goes away. Of course, if I leave my connected over night, it will be dead or nearly dead by morning.

This occurs with any Android build, so I'm guessing it's kernel related.
[Touch CDMA Android Development] dzo:
I made a few more changes to the camera (vogue only), it should be even better now.

I fixed the problem with adb in recovery mode.

I also noticed that the GPU wasn't being disabled on polaris when not in use. This should save lots of power.

I've made new NBHs for vogue and one NBH for polaris (use loserskater's NBH editor for different resolutions/panel types).

I haven't tested to see if this will really save power on polaris, let me know.
[Touch CDMA Android Development] JM-PDA:
Dzo,

Thank you for update and the "Summary of changes"!

Downloading now...
[Touch CDMA Android Development] kallt_kaffe:
I've pushed the Kaiser touchscreen changes now, I hope you don't mind.
[Touch CDMA Android Development] myn:
Huge!!! Thank you dzo!
[Touch CDMA Android Development] margosmark:
I installed the new kernel, camera works great, but my gps stopped functioning properly. Using Myn's Warm Donut rls 5. GPS was working fine before with the previous kernel, however, in at least google maps, it says its waiting for location, but the GPS symbol at the top shows its locked. This happen to anyone else?
[Touch CDMA Android Development] kallt_kaffe:
It's totally possible that I broke the Vogue GPS code with my recent update.

Try the attached kernel and let me know if it helped.
[Touch CDMA Android Development] margosmark:
I will have to try that a bit later as in a building where I wont get gps signal. will let you know when i do try it.

Edit: also you posted an eclair, i use donut at 240x320
[Touch CDMA Android Development] globber:
I am using donut. Converted eclair NBH to donut using Loser's NBH Editor and reflashed.

GPS updated 1'st time then not again, so I rebooted and the same thing happened again-GPS found my location the first time, but thats it.
[Touch CDMA Android Development] kallt_kaffe:
I'm pretty sure now what I did wrong. Try the attached version.
[Touch CDMA Android Development] globber:
That did the trick!

GPS seems ok now, in my short amount of testing.

Thank-you
[Touch CDMA Android Development] inertone:
if i never had gps working on my vogue will this help with gps?
[Touch CDMA Android Development] dzo:
Great, can you push the change and I'll make new Vogue NBHs.
[Touch CDMA Android Development] mrkite38:
*sigh...* here we go again: did it work in winmo? ;)
[Touch CDMA Android Development] myn:
Not sure if this is related but I just upgraded to zImage 05-28-2010 and now I can't adb shell into my device (tried in both Linux and Windows) however device manager lists an ADB Interface.

I am going to switch back to zImage 05-24-2010 to confirm.
[Touch CDMA Android Development] JM-PDA:
Myn,

Thanks for confirming!

I am running with the same "voguimg-240x320-eclair-28-05-10.nbh" build.

I also used to be able to connect my Vogue using ADB at the drop of a hat.

After the 28-05-10 build, I've tried various different things, including rebooting with no luck.

I will stay tuned to this thread for updates.

Thanks...
[Touch CDMA Android Development] myn:
Confirmed. 05-28-2010 adb is not working.

Works fine with zimage from 05-24-2010.