yashsingh1/xdaforums huggingface dataset:
[Touch Dual, MDA Touch Plus ROM Development] excogitation:
step up and stop asking others to get stuff done

I ask you (end)users to put in some effort yourself and check the bugtracker

if there are already bug reports on all problems that you currently experience

and feature requests for things that aren't yet working on your machine.

Also please add to the existing bugs information that might be helpful to pinpoint

and the exact facts that cause the problem (e.g. wifi turned on before booting, ...).

To help make progress on the feature requests collect information that might

have been lost because it's so scattered across this thread and others

(or just important specifics you remember - heaps of valuable information might be buried).

If you always wanted to help but lack the knowledge for kernel/userspace

developement here's your chance to contribute.

All you need is some time to search for the pearls (or maybe you know some by heart) and

make them available to future developers who want to join - and therefore can

join/code faster because they don't have to sift through thousands of posts themselves.

To all developers didn't wanting to waste effort because someone might be working on the

same issue - you can now communicate what you're working on using the bugtracker.

Thanks Stefan for pushing,

and of course many many thanks to all the developers in particular Martin.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Thanks, I really think we needed some bugtracking support, but didn't know we already had one up and running :)

Anyway, I still think we would need some kind of device independent forum for android here at Xda. There are 7 active ports on the msm platform, and each one is at one forum, but each thing each dev does alters functionality on the rest of them... I spend more time reading kaiser, polaris and nike threads than coding...

And back on topic, I'm rearranging the vogue_hw.c file so I can clean it a bit and make it more understandable, and try to make the headset work on nike and polaris, if they tell me the detection pin :). At this time sound is sent to nowhere when connecting the headset, but it's a start.UPDATE: Microphone routes to the headset when connecting, and returns to built in on disconnect. LiquidSilver.. are you working on something like this too?

@McLin: I asked on the kaiser forum and dzo said the Android build may not work because of the kernel version (2.6.25 is ours, 2.6.27 is the latest branch for android). What do you think?
[Touch Dual, MDA Touch Plus ROM Development] McLin:
I did compile it with 2.6.25 not with 2.6.27 but it must be working, cos that are standard settings.

Should I use the new one?
[Touch Dual, MDA Touch Plus ROM Development] Liquid-Silver:
I'm not really working on anything at the moment due to lack of time. If I had time I would work on getting a console via USB to make development easier.

Btw I think i know of a way to detect between a 16key and a 20key
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
@McLin: Just compiled a kernel using the config file from 2.6.25 emulator image (you can grab it using adb pull /proc/config.gz ./ and then copying the file as .config on the kernel dir), and the emulator doesn't even start afterwards, so I really don't know what the hell is going on..

@Liquid-Silver: No worries :) dzo just pushed more usb changes to the git. It's supposed to be working on vogue, and more or less working on kaiser. It's not working on the nike anyway (usb gets stucked on xp, it disappears on linux after some time has passed after booting android), but it's a start. I was wondering.. how did you trace the msm_proc_comm_wince call for the mic? I would need the command and data for the earcouple and headset too, but I don't know how to trace it.. I saw the command declarations on proc_comm_wince.h, but I don't know wich value I have to put after the command, and I was wondering if there's a better way to do it than trial and error...

And about automatic detection of nike type... I would be glad to implement that and get rid of a command line value...

By the way, I have disabled the screen rotation. I think it's useless for this phone, and it only gives problems (after a couple of lid open/closes some part of the kernel crashes and doesn't rotate or detect the slider anymore)

Regards!

EDIT: Found the audioparams files (didn't know it was THAT easy ;) will patch vogue hardware file and see if I can get headset to work... hopefully I can make it today if nothing goes wrong... )

Regards!
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
thanks for the updates, biktor!
[Touch Dual, MDA Touch Plus ROM Development] Liquid-Silver:
I can't do any patches for you ATM as I've downsized my HD and I had get rid of my linux install. Anyway, i think address 0x1ffc048 will allow us to detect the nike type. My 16key nike has a value of 4 and I think 20key nikes have a value below 2.

You can trace the wince proc comm commands by watching the address block 0x1ffc100 to 0x1ffc140. I used the haret logging here is an example default.txt where I use GPIO style tracing but if you uncomment the wirq 30 line then you can trace memory accesses.

So you just start haret, press run (nothing seems to happen but logging has started) then do what you want to trace , like plugging in the USB etc. After the haret will automatically close and you'll have a log.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Just so you know... USB is working!

Credits, of course, to dzo, who has done all the job :)

You can test it by downloading this kernel: http://rapidshare.com/files/219224595/zImage

Note you need dzo's last initrd wich has the telnet daemon. Usb will be working, but without the initrd you won't be able to connect, and you have to input the network address manually through the terminal emulator on dev tools (su ; ifconfig usb0 [address] up)

Get the latest initrd here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D (dzo's page)

PS: Windows asked me for drivers, so use linux on the host pc instead
[Touch Dual, MDA Touch Plus ROM Development] excogitation:
Good news.

I think you can also make it work in Windows.

Don't know if there's demand for that.
[Touch Dual, MDA Touch Plus ROM Development] kulen:
EDIT: wrong threat

sorry
[Touch Dual, MDA Touch Plus ROM Development] matiu:
Released SDK 1.5 :)

News?
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
recent post from biktor regarding the 1.5sdk
[Touch Dual, MDA Touch Plus ROM Development] mlevin:
Can anyone explain how to get yaffs2 support installed on a desktop ubuntu instance? I'd like to be able to create a secondary partition on my sdcard in yaffs2 rather than in ext2, as most people have been doing. I've been googling and not finding much in the way of how-tos.

Thanks
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
You need to recompile the kernel with yaffs support. There are lots of guides out there describing how to do exactly this, but as a little resume, I would say:

Get the kernel source from www.kernel.org

Install gcc, make, ncurses-devel, and maybe some utilities more to be able to compile.

Copy ubuntu's original kernel config from /boot/config-2.6.* (so you don't miss something that was already configured) to your kernel source tree and rename it as ".config" (without the "")

run a "make menuconfig", go to filesystem supports and check the filesystem you want to get support for.

Once you're done, save the configuration and run "make".

After that you'll probably have to make a new initrd if you want your system to boot fine, copy the zImage to /boot, update grub, and reboot.

Anyway, all this is useless as the kernels built for the nike don't have yaffs2 support. It's only useful if you want to mount, for example, android images locally to dump files (wich you can do through the emulator without going into that amount of problems)

Regards!
[Touch Dual, MDA Touch Plus ROM Development] mlevin:
Thanks! I just want to get yaffs2 support on my totally separate, non-android Ubuntu 8.04 desktop instance so that I can try to format the 2nd partition of my sdcard as yaffs2 rather than ext2 and try having my apps there. I currently have them on an ext2 partition but I'm seeing lots of corruption and I frequently have to pop the card out and fsck it.

Any reason my plan shouldn't work?

I'm not sure what nike is! Am I missing something important?

Thanks
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
anyone tried dzos latest tweaks? the screen is much more clear and responsive.

kernel here:

http://cs-alb-pc3.massey.ac.nz/vogue/files/zImage
[Touch Dual, MDA Touch Plus ROM Development] paranoidpenguin:
first time everything works for me (beside messaging...)

- get/ receive calls

- internet

- log in with my google account

- downloads in android market

- keyboard works with special keys, so I can sign in with other email accounts

- usb

seems to me, that this image is very fast and stable
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
The cleaning on kaiser ts and changes on the frame buffer seem to have made things run smoothly :)

Now we have only to keep on devel (I haven't done much lately apart from trying to get a more useful keypad driver for polaris...)

Regards!
[Touch Dual, MDA Touch Plus ROM Development] paranoidpenguin:
I just found a kind of workaround for the messaging problem.

Install chompsms and you have a softkeyboard.

From time to time the touchscreen freezes with the new image and the volume during calls can't be changed, it's too loud
[Touch Dual, MDA Touch Plus ROM Development] shinji_73:
Sorry if my question is obvious but ext 3 (or ext 2) partition on sd card is really necessary to boot android?

Thanks for your reply
[Touch Dual, MDA Touch Plus ROM Development] excogitation:
No. Simply put all the file in the root of your SD card (use the default.txt for Nike) and enjoy.
[Touch Dual, MDA Touch Plus ROM Development] shinji_73:
I tried that as reported through this thread but nothing happens after the progress bar has reached its end.
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
what radio and rom are you using?
[Touch Dual, MDA Touch Plus ROM Development] shinji_73:
Since my Niki has just came back home from service repair it features

ROM 1.31.408.09_Ship

RADIO 1.58.16.27_25.61.30.03
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
you need newer roms. try upgrading your radio from the radio rom thread to 1.71

failing that

flash this rom:

http://rapidshare.de/files/41219609/..._Ship.exe.html
[Touch Dual, MDA Touch Plus ROM Development] shinji_73:
Thank you for your reply...hope these "minimum requirements" could be helpful to some others.

(btw http://rapidshare.de/files/41219609..._Radio_NikeMR_1.65.29.22_signed_Ship.exe.html is the correct link? This file reflash the radio 1.65.29.22 as well?)
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
yep thats correct, it will flash the radio too :)
[Touch Dual, MDA Touch Plus ROM Development] joannerve:
With the last android builds I can't see videos. I only can listen but I can't see. I can see videos with an older build but no with more new builds. Someone can help me?
[Touch Dual, MDA Touch Plus ROM Development] McLin:
@biktor_gj

I would say we wait one or two weeks, then the official Cupcake is released, and we can take this build, the repo cup is very unuseable...
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
From what I've read, the cupcake branch was merged into master, so, by now, the master branch is the most up-to-date I think...

Anyway, at this time I'm only fighting against the polaris keyboard, nike's bluetooth and the audio routing for both nike and polaris, so I haven't tried much on the userland. What I've seen (and I find interesting) is the fact that the userspace doesn't even call the kernel rfkill module to enable bluetooth, but my approach starts to get a little bit further (though it still doesn't work) since it now stays trying to enable for some time. But as ADB doesn't work, I can't get the android logs to get to know what is going on...
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
i noticed you pushed some changes biktor. anything new worth compiling a kernel for?
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
From my part, not really. I've been working on the audio, but didn't get it to work through the headset. I also tried some attemps more at the bluetooth and found Android doesn't even call the rfkill module to start, but now it holds the function for a little while until it tells its unable to power it on. I mostly cleaned things so there's a bit less amount of garbage on dmesg (to make it easier to see things), a bit of work on the polaris keypad, and a little bugfix on nike's keypad, but no real functionality improvements on my side.

On Dzo's patches, there's a bit of improvement on battery life (82% -> 62% battery on 1h 45min of testrun), and the latest patches on screen have been included:

Here you have the last up-to-date kernel, previous links no longer work:

http://rapidshare.com/files/224432201/zImage
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
thanks a lot, biktor. i appreciate your work.
[Touch Dual, MDA Touch Plus ROM Development] cunter:
Thank you so much!

There is only one real problem for me now: i can't adjust the in call volume.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Actually, just on the audio part we've got quite a lot of problems :)

Can't adjust in call audio (and it's too loud)

Excessive audio on audiio playback

No standard headset support (microphone gets routed through the headset but audio output doesn't)

No support for multi-key headset (play, next track, prev track etc)

No bluetooth so no bluetooth headset or a2dp

We'll have to look for an alternative approach :)

Regards!
[Touch Dual, MDA Touch Plus ROM Development] joannerve:
With the last android builds I can't see videos. I only can listen but I can't see. I can see videos with an older build but no with more new builds. Someone can help me? It only happen to me? Why I can´t see?
[Touch Dual, MDA Touch Plus ROM Development] cunter:
I can't watch youtube videos with this. I don't know if it worked before.
[Touch Dual, MDA Touch Plus ROM Development] joannerve:
Yes, in an older build you can see youtube videos. In more new builds its not possible
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
think you can port dzo's gpu work to the nike biktor? :)
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
I already have :) But after booting the phone goes completely irresponsive, with lags of about 15-20 seconds, and OpenGL sprite text results show exactly the same speed. But of course I'll try to fix it :)

If you want to give it a try, here you have: http://rapidshare.com/files/226008323/zImage

Maybe it's just the system.img from dzo (I don't think so), but maybe you want to try first with a normal system.img and then with dzo's new one just in case...

Regards!
[Touch Dual, MDA Touch Plus ROM Development] cunter:
Do you think, this will help our battery life too?

http://blog.smartcube.co.za/2009/04/26/android-g1-battery-calibratio/
[Touch Dual, MDA Touch Plus ROM Development] cunter:
The G1 only wakes the display up if you press the Menu button. On my NIKI every button wakes the display up and it seems that especially the left/right buttons get pressed when my NIKI is in my pocket.

biktor, could change the behavior to the G1's ?
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
thanks biktor, i cant get the kernel to work without lagging bad however.

****er, that battery technique is hardware related, not g1 specific, its a general way of building a healthy battery.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Fixed, typo error... :) Anyway, here's the new one (previous has been deleted) without the lag: http://rapidshare.com/files/226135608/zImage

I checked and still get 22ms/frame though, but I don't know how it will deal with games... (just in case, I use 320x480 mddi settings)

Regards!
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
awesome!!!

21.5fps here too

i adopted your resolution too its much better.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi, second test run with the last updates from kaiser: http://rapidshare.com/files/226325730/zImage

Resolution: 320 x 480

Qualcomm benchmark: 17 fps

OpenGL Api Demo (spirte text): 37 ms/frame

Graphics are slowed down, but hey, it's working fine without garbage on the screen, so it's good to me :)

Thanks dzo!
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
thanks a million biktor. im pretty amazed at this new driver, i didnt see it comin.

pretty sweet having 3d accelerated while we cant even get it on winmo. i got the same benchmarks as you..

thanks biktor!
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
ive been running this full time for a couple days, audio isnt a big problem for me since i tend to only text anyway. battery life however is a huge pain, charging up twice a day makes it almost unusable. i do really love it though.
[Touch Dual, MDA Touch Plus ROM Development] rickman2003:
how da hell do you type text messages? thought the messaging app was unsuable because of that hardware keyboard issue. or was it solved at in the last zimage?
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
For messaging you can use chompsms :)

@ducamie: don't know if you follow polaris thread too, but it seems the 3d driver is still not working too well (poor performance compared to Kaiser & Vogue), but I'm still working on it (with dzo's help I might add). Whenever that's working fine, I'll go back for the rest (though I really don't know if I'll be able to keep fixing things, this is starting to get quite complicated for me).

Regards!
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
i just read. poor performance compared or not, it works good enough for me :) all the 3d games i tried ran well enough.. i wouldnt bust your balls on it. you've already contributed way more than most, and im super thankful.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Maybe it runs well enough, but if it can do it faster, why not make it go faster? Another test run, on my phone seems to work quite better, mostly on Api demos, but there's an increase on qualcomms benchmarking app too:

http://rapidshare.com/files/227835391/zImage

before I was getting 37-44 ms/ frame, now 17-22 ms/f on Sprite Text

On qualcomm's app, before I was getting 16-7-17.1 fps, now I got 17.5 fps

How does this work for you?
[Touch Dual, MDA Touch Plus ROM Development] joannerve:
With the last android builds I can't see videos. I only can listen but I can't see. I can see videos with an older build but no with more new builds. So, Youtube application don´t work properly .Someone can help me? It only happen to me? Why I can´t see the videos?
[Touch Dual, MDA Touch Plus ROM Development] Boylen:
Hi Biktor_gj,

I haven't tried it lately, but want to try it again. I saw on the wiki that I need radio RUU Nike Radio 1.71.09.01K (the one with the 'K' on the end should work?)

I bought my Nike in the store, it is without sim-lock, but do I need to do some CID-unlock? Or can I just flash it?
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
@Boylen: Do a CID unlock first (use hardspl 1.15 mfg if you want to unlock as it's the only version that didn't give me problems, otherwise you can use 1.16 or 1.22, didn't see any differences on the phone behaviour besides unlocking). Also you can simunlock (though you don't need it, but I always thought is always better to have an unlocked phone just in case). Any radio higher than 1.65 should work fine. I'm personally using 1.71 radio just fine, so I recommend that. Note that if your radio was a 1.58 or lower, you'll probably have to upgrade the full rom, not only the radio to avoid incompatibilities between radio and OS.

Also remember to disable PIN request if you want to be able to use gsm on linux

@joannerve: I haven't ever seen a video on android, haven't really tried (don't want a huge bill from my carrier), but you can try with 1.5 sdk version and see if it works for you, you can find files on the polaris linux thread

Regards!
[Touch Dual, MDA Touch Plus ROM Development] Boylen:
thanks for your advice!

I have radio 1.65.28.25, so it should work, but it just won't boot. I took the bootkit from the wiki, only changed the 20key keypad interface flag from 0 to 1 (because I have 16 key) and the spanish(?) name for storagecard to the dutch one (as my Win Mobile is dutch), copied it to the root of the storage card, but after the progress bar of HaRET is full and disappears, nothing happens...
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
First try removing the path on default.txt, for example:

set INITRD initrd.gz

Be sure you're using nike's mtype: 1724. If it doesn't work you can also try with 1723 (polaris) and 1553 (kaiser) to make sure it's not a kernel problem, but a lot of things won't work if you use them. They should just start booting.

Remove also the line 'set RAMSIZE 0x...' and 'set RAMADDR ...' if they exist.

If still doesn't get to boot, at least at some further point than haret, you may be dealing with a problem with that particular rom, or with your sd card, or maybe a combination of problems... check this out first!
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
18-25ms/f on sprite text

17.6fps on qualcomm bench

thanks a lot, man
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi, I made some tricks on the touchscreen driver (should have done it loooong ago). I fixed the values, and, at least on my niki100, it's now perfectly calibrated.

Anyway, I put a commandline option to manually calibrate it if it doesn't meet your expectations.

Pick this:http://rapidshare.com/files/228250587/zImage

And test how it works for you. If it doesn't work as expected, you can add this boot parametters to the cmdline to get the min and max X and Y values for the ts:

board-htcnike-ts.calibrate=1

Then boot to android, go to dev tools -> terminal, and run dmesg (or do it from usb, it doesn't matter). you will see some lines saying "TS Current Position: X= whatever Y=whatever". Point on the upper left corner on the screen, and type dmesg again. These will be XMIN and YMIN values, write them somewhere, and then point on the lower right corner of the screen and run dmesg once again, you will see the max values for X and Y. Then reboot, and add these parametters to cmdline (and remove the calibrate param):

board-htcnike-ts.NIKE_TS_XMIN=415

board-htcnike-ts.NIKE_TS_YMIN=383

board-htcnike-ts.NIKE_TS_XMAX=3695

board-htcnike-ts.NIKE_TS_YMAX=3791

Replace the values with the ones you gathered (these values are what I use), and you're set! perfectly working touchscreen :)

Regards!
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
hey biktor, thanks for the update. crashed the touchscreen first time with writing on the chompsms keyboard but i think i was just unlucky, its been great ever since. working like a charm. perfect calibration on my niki100.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
You're welcome :) I hope it doesn't crash anymore, my changes shouldn't make it crash anyway...

@McLin: The problem with our android images were not the images themselves, it was the initrd what was making problems! I've tried again using f00bar's initrd, and they work like a charm :) I'll build a new bootkit soon and post it with the 1.5 version compiled for the g1. I'm trying it right now and it seems to work quite well (even with 3d rotation effects), I'll hold it for a while to make sure it does what it should and post back! Any app preinstalled you might need? Chompsms shouldn't be necessary anymore, as Messaging app lets you write what no matter how the screen is positioned...

Regards!
[Touch Dual, MDA Touch Plus ROM Development] lapy:
on mine works quite fine but hanged up when i tried to mess with widgets..and last i was not able to type the dot (.) with my 16 keys keypad. I need that to edit my carrier's apn.