yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] tatnai:
http://en.wikipedia.org/wiki/Dzo

googled dzo, did you know:

A dzo (Tibetan མཛོ་ mdzo) is a hybrid of a yak and domestic cattle. The word dzo technically refers to a male hybrid, while a female is known as a dzomo or zhom. Alternative Romanizations of the Tibetan names include zho and zo. :eek:

:p

with eclair, reverted to 22-3 nbh, can activate bluetooth without freeze.
[Touch CDMA Android Development] dzo:
Yes, and it's a very useful scrabble word.

I've just reverted the ll bt changes, this should help with bt on eclair.

Thanks for the kmesgs, I also changed the dma timeout to 1s which should fix the last two panics you had, let me know if it doesn't. I don't know if 7200 devices even need the dma timeout fix, it seems to be caused by a hardware bug on 7500 that doesn't share the nand dma correctly.

New NBHs for all devices are on my site.
[Touch CDMA Android Development] kallt_kaffe:
I've posted a customized kernel for Nordic hardware keyboards here: http://xdaforums.com/showthread.php?t=655512

DZO, is this something that you are interested in having in the official branch? If so, then the tilt parameter perhaps should be renamed to something more generic, like "keymap" and it could be used to switch between more than just tilt and non-tilt keymaps. It will be a pain with all the NAND versions though.
[Touch CDMA Android Development] dzo:
Sounds like a good idea, send me a patch or ask to join the mobile-linux group on ltg to be able to push to git. Probably best to add a new parameter to keep compatibility.

Thanks.
[Touch CDMA Android Development] kallt_kaffe:
May I also suggest adding a pipe "|" to the normal and tilt layout. For example on Fn->Space.

The first thing I did after adding the pipe was to open a terminal and type "dmesg | more". A linux terminal without an easily accessible "|" is like a car without a steering wheel. (The source code mentions shift+camera for a pipe but that doesn't for me)

I also wanted to add "<" and ">" or at least ">" but they are both "shifted" and the only keys I have left to sacrifice are pageup and pagedown (which doesn't seem to be useful anywhere in Android asfaik) but as I understand I can't add "shifted" keys to those.
[Touch CDMA Android Development] polyrhythmic:
Pipe is Fn + Left Soft Key ;) (I seriously spent my first 9 months of Android not knowing that shortcut!)
[Touch CDMA Android Development] kallt_kaffe:
I've changed the code so that nordic keyboard is selected when atttilt is set to 2 and I've mailed the whole board-kaiser-keypad.c to you.
[Touch CDMA Android Development] kallt_kaffe:
No, it's not... Fn + left soft key is F1 and shows text console (boot screen), Fn + right soft key brings GUI back.

However, I just realized shift + left softkey would give a pipe as it is assigned a non shifted backslash and pipe is shift+backslash on an US keyboard.

With my nordic mapping however shift left softkey gives a { and the right gives a } as I have mapped [ and ] to those keys.

Whith this new information I need to rethink my mappings. It would propably be more useful with < and > than []{}.

EDIT: DOH! This totally explains why KEY_BACKSLASH and KEY_DOT is mapped to the softkeys. Shifted it gives | and > which are two of the most useful things to have in a linux terminal. I really have to rethink my nordic keyboard mapping.
[Touch CDMA Android Development] kallt_kaffe:
Wierd... Mapping KEY_DOT to softkey and pressing shift and that softkey prints a colon on my Kaiser. The same thing happens if I map KEY_DOT, SHIFT_BIT to any other key. I've also tried the normal keymap and shift+right soft key and I get a ":" instead of the expected ">".

Now would be normal on a swedish keyboard as ":" is shift+"." but in all other aspects the keymapping seems to be based on an US keyboard (like for example KEY_2, SHIFT_BIT produces a "@" which is not what happens on an swedish keyboard. I'm confused. :confused::confused::confused:

EDIT: Also KEY_COMMA, SHIFT_BIT produces a semi-colon just like it would on a swedish keyboard instead of "<" as I would expect it to do.
[Touch CDMA Android Development] kallt_kaffe:
I've posted an azerty enabled kernel (for Kaiser) here http://xdaforums.com/showthread.php?t=654441

I'll send the code to DZO as soon as someone with a real Azerty keyboard can confirm that it works OK.
[Touch CDMA Android Development] dzo:
Happy birthday.

Happy birthday, Vogue android.

I just noticed that it was exactly 2 years ago that I started this thread and, 5000 posts later, here we are.

We've come a long way since then, in the first post almost no hardware was working, now everything works and its being used by lots of people every day, in fact I'm writing this on it. We've built a great community of people too.

I'd just like to thank everybody who's been involved in this project, the people who helped with documentation, wrote drivers, ported code, wrote libraries and installers, reverse engineered strange protocols, made new themes, packaged everything together, reported bugs and put up with the barely working early versions.

Thanks to you all, and lets see how many more tears we can get out of this device.

Martin.
[Touch CDMA Android Development] incubus26jc:
Its because of you man. Happy Birthday to you. Thanks for everything!!
[Touch CDMA Android Development] jamezelle:
yep thanks DZO and everyone happy 2 years!!!
[Touch CDMA Android Development] mssmison:
Wow, has it been that long already?

To echo what everyones said this wouldn't have been possible without you Martin. In fact I've no doubt the only reason there are ports on ANY win mo devices is because of what you've done on the vogue.

To all of the people who aren't around, or barely involved as well, steven walter(first GPS drivers), foobar (modem app) this wouldn't have happened without you guys :)
[Touch CDMA Android Development] polyrhythmic:
Incredible, thanks so much to everyone for your countless hours. I've learned an amazing amount -- especially about Linux -- and it's made me a better programmer.

Cheers to all!
[Touch CDMA Android Development] srwalter:
Two years already? Here's to another two years!! :D
[Touch CDMA Android Development] incubus26jc:
HAPPY BIRTHDAY VOGUE ANDROID!!!

Here's a birthday cake for you all to share

WATCH THIS VIDEOhttp://www.youtube.com/watch?v=yHl8j4XuJY0
[Touch CDMA Android Development] tatnai:
happy birthday android on vogue. thx dzo for starting it all, we owe this to you.
[Touch CDMA Android Development] cp0020:
cross out (dead zone outdoors) lol
[Touch CDMA Android Development] slow88lx:
I've never had a phone this long. I don't have a reason to get rid of it yet..... as long as Skyfire delivers on their promise of flash.
[Touch CDMA Android Development] cp0020:
i wish kate hudson was my vogue :( even better...jessica alba! :)
[Touch CDMA Android Development] incubus26jc:
aww my video link didnt work. I fixed it.

WATCH THIS VIDEO
[Touch CDMA Android Development] zenulator:
Thanks dzo!! Some of the things you've done still boggle my mind. Hardware acceleration on 2.1 even before the G1.The list goes on. Simply amazing stuff. I still have my Vogue even though it's out of service I loaded it up with a bunch of games for my son to play on. He loves it. Thanks to you and everyone thats contributed to this great project.
[Touch CDMA Android Development] cp0020:
oh my god dude! i havent seen that movie in forever!!! lol
[Touch CDMA Android Development] hexto:
This month it'll be two years since I've had this phone and like I've said before, never in my life did I keep a phone so long. That would have never happened without DZO's Android port. I remember not being able to touch the screen for fear it would crash, then getting a virtual keyboard (which DZO created before Google did), calls, data, etc. The excitement of being able to use Android on a WM phone and watching it mature into a build I can use exclusively has made owning this phone very fun. When other devs like Zenulator, Myn, Srwalter, Vilord, and Mssmison started churning out builds and updates faster than WM ROM's I knew I was gonna keep my phone even after VZW released an Android phone. And since November's NAND update I've not used WM for even a moment nor do I miss it. Othen than MMS, my phone does it all.

Thanks
[Touch CDMA Android Development] egzthunder1:
Happy B-Day for A-Users on th V-phone!!

Thanks for everything dzo!
[Touch CDMA Android Development] dzo:
I found a problem with the gps driver, it was creating new thread each time it was opened. It seems to be better now. New NBHs and zImage in the usual place.
[Touch CDMA Android Development] JM-PDA:
DZO,

Thank you so much!

Downloading now.
[Touch CDMA Android Development] dnquark:
Just wanted to say thanks to DZO and the gang for giving me an awesome new phone :) I played with it, was duly impressed, but was about to go back to WinMo due to buggy bluetooth audio, when I noticed a fix, barely 10 days old! Now there's no going back. (Getting working AVRCP will be icing on the cake, though :) ).
[Touch CDMA Android Development] manu33xtro:
Hi DZO,

Is the correction available for Polaris ?

Thanks again.

Cheers.
[Touch CDMA Android Development] berardi:
Hmm I'm still having trouble with my bluetooth audio. The problem is less often than before, but sometimes, especially if Bluetooth has been turned on for a while, I will be able to connect bluetooth and bluetooth audio, but when I start playing music (usually in default android music player) it appears to be playing at an accelerated rate - like for every second the song moves forward two seconds. No sound is produced in the bluetooth device. To fix it I must reboot the phone - cycling bluetooth alone does not fix it. No biggie, just wondering.
[Touch CDMA Android Development] jnadke:
Didn't notice that!

Looks like they forgot a:

thread_started = 1;

in vogue_gps_open. Though, that could introduce a (rare) race condition.

I noticed you moved it to vogue_gps_probe. Won't having the thread running constantly put an extra load on the CPU? Does msm_rpc_read_command block efficiently?
[Touch CDMA Android Development] sshark:
I have installed latest kernel for Vogue/Eclair and GPS performance was very good, I did not loose signal once in my ride of over 3 miles.

I have also updated ril based on what you have uploaded to the website and calls seem to come in quicker on Eclair. Have you made any changes specifically to affect that?
[Touch CDMA Android Development] jnadke:
Also, it looks like the Kaiser suffers from the same issue.
[Touch CDMA Android Development] ckl_88:
I have noticed this problem too. I also notice that the root of all my bluetooth problems starts when the phone goes to sleep (screen off). When I have the phone plugged into a charger, bluetooth works for what I need it to do.
[Touch CDMA Android Development] berardi:
That's a possible source of the problem... maybe if the phone sleeps for X amount of time it shuts off a bluetooth audio service? I dunno.

I'm applying for a masters in computer science, so maybe I will be able to help soon :D
[Touch CDMA Android Development] jnadke:
Experience, experience, experience. Always best. A Masters in Computer Science won't help you any more. Heck, I have a Bachelors in Electrical Engineering.

Dzo, vilord, and I all work in these types of fields. I haven't been able to help much lately due to a lack of free time.

I used to work for a company that ported Linux to PowerPC and MIPS processor boards. It's really not hard, but it takes a lot of debugging and some low-level hardware knowledge.

Linux on the Vogue would literally take about a month if I had all the hardware documentation. That's the problem, we're reverse-engineering everything, which takes significantly longer.

Dzo seems to have more experience in that respect.

Start here: http://lwn.net/Kernel/LDD3/

Best Low-Level Linux Book. And it's free.
[Touch CDMA Android Development] berardi:
sweet I'll definitely check that out. thank you!

actually I only have a BS in Finance, trying to change over to computer field since its what I really love. The reason I'm trying for the ms is to move forwards instead of back or sidestepping with a second bachelors, if that makes any sense.

I definitely understand experience and skills are paramount, but since this is like my new beginning, I need somewhat of a base to work from so that employers will consider me for entry level.

This forum has reminded me of what I really love doing - tinkering with technology!

Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
[Touch CDMA Android Development] dzo:
Yes, rpc_read_command will block so it doesn't cause any extra load, some people don't like having lots of kernel threads but it's not going to hurt performance. I guess a better way to do it would be to have a single rpc thread that wakes up the actual drivers but this it the way google chose to implement rpc servers so I just left it as it was.

berardi: With regards to MScs etc, I'm a bit biased but as long as it's not just a purely taught masters (i.e. it has a thesis) then you'll probably get a much more rounded idea of what Computer Science is than the equivalent time spent writing code (especially without an undergraduate CS degree).
[Touch CDMA Android Development] berardi:
Thanks DZO! They do have a course, a thesis, and a project option. You would recommend the thesis option?

Here is the program I'm going for:

http://cs.njit.edu/academics/graduate/mscs.php

Sorry I won't derail the thread anymore, but you guys are an inspiration. Seeing what you accomplished here was inspirational! made me remember my days in the computer business, I miss them and want them back! I'm 28 so hopefully it's not too late!
[Touch CDMA Android Development] dnquark:
I'd like to confirm the bluetooth A2DP bug that berardi and ckl_88 mention. When A2DP breaks, the phone reports a connection "to phone and media" whether or not the bluetooth device is on; the playback appears accelerated, and there's no actual sound going to the bluetooth device. The only way to fix it is to reboot the phone.

This is the same behavior that was happening before the March 26 commit -- except for before, it used to happen all the time; now it happens occasionally. To reproduce reliably: toggle BT off and on on the phone. Turn on BT headphones. They will connect, but with no sound and accelerated playback.

Another (possibly related) bug is that after power-cycling the BT device, the phone doesn't pick it up until I go into settings and manually connect by tapping on the device's name in the list. In order to reproduce this, you need to wait for the phone's screen to turn off, otherwise the phone picks up BT connection after the BT device has been turned off and then on. This suggests that some low-power setting is screwing with Bluetooth on the phone.

I use my Bluetooth headphones all the time with my phone, so I'd love to see this fixed for good... I wish I could help with the code -- my embedded systems experience is rather lacking, though. I could probably compile and test stuff and maybe poke around with the debugger if told exactly where to look... I give props to berardi for wanting to go into the field; I wish I had the resolve to do this :)
[Touch CDMA Android Development] kallt_kaffe:
Hold on... does this mean that this change only affects Vogue users? Will my Kaiser still suffer?

Do I need to make the same changes to board-kaiser-gps.c?

EDIT: Did the changes and made a new kernel (NAND). I'll report back when I've tried it out.

EDIT2: Didn't work, didn't get a fix at all.

EDIT3: Just noticed that DZO have posted a new version of the Kaiser gps code.
[Touch CDMA Android Development] dzo:
I made some changes to the polaris usb code and figured out that it uses a completely different mechanism for usb detection. It should stay connected when charged now.

I also had to change the pm code to get this to work.

I fixed the kernel threads for kaiser and polaris, i got a fix on polaris but haven't tried kaiser yet.

NBHs and zImage are in the usual place.
[Touch CDMA Android Development] incubus26jc:
will this effect vogue users? Do I need to flash if im using 3-06?
[Touch CDMA Android Development] dzo:
No, don't bother. It shouldn't affect vogue.
[Touch CDMA Android Development] kallt_kaffe:
Does this also affect the Kaiser? The USB icon for me always goes on and off but I thought it had to do with me running Windows 7 so I have ignored it as I only use the USB when flashing and that works fine.

I tried it yesterday (compiled my own kernel and NAND once I saw that you commited the new kaiser GPS code) and I got a fix while taking the dog for a walk. The most obvious change is that the GPS seems to keep running when I exit (for example) Google Maps and if I later starts another program that uses the GPS it has a fixa almost instantly. In my world this is a good thing.

However I'm having other issues like that Android seems to reboot (not the the whole phone, just android it seems) when running GPS applications. Google Maps seems fine the short period I tested but GPS Test and GPSTest (two different applications) makes it reboot. GPS Test goes black screen and reboots after 15-20 seconds if I press menu->settings or even menu->about. This was however occuring before the new kernel code and I'm currently investigating if it only happens in mssmisons Eclair build (both v7 and v8) so I'm going back to polymod 2.1g for some tests. I'm sure I could enter the settings menu in GPS Test with both polymod and Myn's warm donut.

EDIT: With polymod 2.1g the GPS Test application does not have the above issue so it seems to be a mssmison eclair issue.

EDIT2: Also with polymod 2.1g the GPS is turned off if I quit a program that uses the GPS, but with mssmison eclair it does not. I just started GPS Test with mssmison eclair (and and kernel using the latest sources), quit it, GPS icon still flashing, menu a bit sluggish, starts GPS Testa again. Screen goes black and Android restarts (not the whole phone).
[Touch CDMA Android Development] mblaster:
Hi DZO,

first I want to thank you for your efforts for the vogue/kaiser/polaris/nike community! You really helped making android usable on those devices!

Second I have a question. I try to get bluetooth working on nike and have a problem with the vregs here in htc_rfkill.c:

static int bluetooth_set_power(void *data, enum rfkill_state state)
{
printk("Bluetooth %d\n",state);
switch (state) {
case RFKILL_STATE_ON:
...
if(is_msm7500())
msm_proc_comm(PCOM_PMIC_REG_ON,0x02000020); // vreg enable
else
[B]msm_proc_comm(PCOM_PMIC_REG_ON,0x00100000);[/B]
...
case RFKILL_STATE_OFF:
...
if(is_msm7500())
msm_proc_comm(PCOM_PMIC_REG_OFF,0x02000020); // vreg disable
else
[B]msm_proc_comm(PCOM_PMIC_REG_OFF,0x00100000);[/B]
...

The second bold function call disables sdcard on nike -> android doesn't boot anymore as bluetooth_set_power is called on system bootup. I guess 0x00100000 is just the wrong data.

Is there information available on the vregs anywhere or a possibility to find out what would be the right settings? I tried serching for it, but without results.

mblaster
[Touch CDMA Android Development] dzo:
The only way to find out is to trace it with haret. Start haretconsole, type

addlist mmutrace 0xb5100000 0x100000

wi 20

then enable/disable bt

You'll probably also need to find the gpios to enable the bt chip.
[Touch CDMA Android Development] mblaster:
Thanks, I will try it later. I think i already have the gpios. I will report back if i solved it.

€: Strange, but i don't get a proc_comm on bluetoth start/stop? I did:

HaRET(1)# show IRQS
HaRET(2)# addlist mmutrace 0xb5100000 0x100000
HaRET(3)# show IRQS
HaRET(4)# show mmutrace
HaRET(5)# wirq 60
HaRET(6)# wirq 6
HaRET(7)# wirq 30
HaRET(8)# wirq 20
HaRET(9)# wirq 20

All in one session. While the wirq was running I switched BT on and off. Afterwards I parsed it with your kaiser haret parser (that I found by chance as i googled for b51fc100:)) here is the output:

012182: proc_comm(184,38ef66cc)
018199: proc_comm(184,38ef66cc)
004268: proc_comm(184,38ef67f9)
004925: proc_comm(184,38ef67f9)

The proc_comms happened definitely while starting the htc comm manager. No further proc_comms while enabling bt. Also not when I use the windows mobile settings to enable bt.

Could this be a strange rom/radio related thing? That the vreg is turned on on boot and never shut down? Or am I doing something totally wrong?

€2: Same with htc stock rom/radio, so not a rom issue. It calls a proc_comm twice when starting the comm manager, with command 184 and a changing number (address?) as data.
[Touch CDMA Android Development] kallt_kaffe:
Suggestion, even do you make donut NBH's include hw3d.version=0. That way it can easily be hexedited into an eclair NBH. I've tried changing both resolution and keypad with a hexeditor and it works fine. I was worried that it would have some checksum and refuse to flash it but it works fine.

In fact it would be possible to create a configuration tool to change the paremeters within an NBH so that you wouldn't have to create zillions of versions every time.

Btw, did you get my mail with the board-kaiser-keypad.c that also adds qwertz and azerty support?
[Touch CDMA Android Development] manu33xtro:
Hi DZO,

I tested the new file (polaimg-panel1-320-08-04-10.nbh) but one big problem : I stay with the first bootscreen and nothing else... I try to reboot but same thing.

I hope you know why ;)

Cheers.
[Touch CDMA Android Development] mssmison:
That is a great thought! I hadn't thought about hex editing the nbh before.
[Touch CDMA Android Development] mrono:
So I just found an issue, don't know if this has been addressed in posts previously but my BT A2DP stopped working after i flashed either kernel after april, just flashed back to 3-31 and it works again.
[Touch CDMA Android Development] dnquark:
That's strange. I'm running a setup very similar to yours (only difference is that I'm running from SD card), and my A2DP is much better with April 6 zImage compared to 3/26 (with the exception of bugs I described in a post above; one of the bugs is that A2DP breaks if you turn BT off and on on the device, but a reboot helps).
[Touch CDMA Android Development] JM-PDA:
I am running Myns' Donut with 2 EXT2 partions and zImage-06-04-10.

My A2DP works really well. I usually turn my Vogue BlueTooth off when away from my car speaker phone, so I have not yet experienced the "break" issue above.
[Touch CDMA Android Development] kallt_kaffe:
Someone with windows programming skills should be able to put together something with a GUI to do this pretty easily. I could propably manage to put together a commandline utility but that wouldn't be much more userfriendly than a hexeditor so it wouldn't be worth the effort.

The number of NHB's needed for the kaiser if you would compile all keypads (5 of them if DZO includes my latest update), panels, eclair vs non-eclair, resolutions would be insane. One NBH and a utility would be enough. Well actually one NBH and a hexeditor is enough right now but maybe not that userfriendly. On the other hand, if you are going to flash your phone you should be able to handle a hexeditor or else you propably shouldn't flash your phone anyway.