yashsingh1/xdaforums huggingface dataset:
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Sweet :) lots of thanks, I'm going to do a test build and post it here, you guys will tell wether it works or not, as I still haven't got my nike

btw, this is what dzo told me:

I did the dump, but apart from at commands, part of my sim's phonebook and somethings more I didn't find much :)

EDIT: It seems like the rx,tx,cts, and rts pins are the same as the g1, so I only had to patch enable and clock :)

Anyway, I need at least one person who can test this out:

Grab this kernel: http://rapidshare.com/files/206582222/zImage

Now copy it to the storage card, boot android. You can try to power it on from the menu, but I guess that won't work since the images don't seem to have the firmware file loaded and stuff, BUT the kernel shouldn't crash when setting the initial bluetooth state.

So, boot Android, then reset the phone and connect it through usb and run haret. Instead of booting android again press on "listen to network connection" and hit Start -> Run -> cmd. From there, do "telnet 169.254.2.1 9999" and press enter. You should get the haret console. Once you're in there, run the following command:

pwf dmesg.txt 0xe0000 0x20000

This will create a file called dmesg.txt on your storage card, containing the kernel bootlog. Please post that file so I can check if the thing crashes or it simply works now :)
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
here you go biktor

http://pastebin.com/f3ba98e24
[Touch Dual, MDA Touch Plus ROM Development] Liquid-Silver:
Information removed as it was wrong.
[Touch Dual, MDA Touch Plus ROM Development] excogitation:
I'm sure you've seen this page...
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Ok, then it looks like it didn't work :)

Will keep looking on to it a bit and post another build to see if I can make it (at least) stop crashing...

EDIT: I've traced a bit and think that some git changes broke part of the bluetooth thing on the nike. Good news is... it seems like my nike is back at business :) Going to pick it up now. They say they replaced the main board... that for a bad radio flash! guys be careful with what you flash to the phone... Will keep you updated!
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
aha! my nike is back!

They say they had to change the complete rf board, so guys, really, don't try to flash strange things :)

Now back to work, let's see if in the following days I can get bluetooth to work :)

Regards!
[Touch Dual, MDA Touch Plus ROM Development] rickman2003:
oh baby!

i was waiting for this day! i`ve checked 10 time a day this thread! :-)

cant wait for developement and future releases.

glad youre back in business ;-)
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
awesome news biktor!! im glad you got it sorted
[Touch Dual, MDA Touch Plus ROM Development] joannerve:
Speakerphone don´t work. Maybe stupid questions but .... how I close an open application and how I go directly from open application to menu?
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
@joannerve: Speaker has worked so far, try with a clean boot on windows mobile, and before you attempt to call, and with no headset plugged in, boot android again and check it out, it really should work. About the other one, there's no key mapped to "Home", sou you can't go directly to homescreen, at least for now

@all: Updated the git a bit with some changes on the bluetooth (it doesn't work, but doesn't crash either). I think there might be a problem due to the lack of the firmware file on the system.img, and maybe also a problem with a library, but not too sure anyway. It supposedly powers on bluetooth now, according to the code, but can't find the device, and it's not detectable by other phones. Maybe with a bluetooth sniffer we could get to know if at least something is working, but I assume the chip has to load the firmware to be able to do that... anyway if someone wants to take a look, the code is there for you to play with :)

Regards!
[Touch Dual, MDA Touch Plus ROM Development] joannerve:
Tried but no, the other people who I call don't listen me
[Touch Dual, MDA Touch Plus ROM Development] rickman2003:
hey guys,

hope you enjoyed this weekend.

just wanna ask about the progress.

hope I´m not pissing you on with my question... ;-)
[Touch Dual, MDA Touch Plus ROM Development] JohnOffline:
sorry mates

Im sorry I have to ask that - I havent found a solution yet. Whenever booting it with Harem it hangs showing "Booting linux" and the progress bar (90%). I have copied all the files onto the FAT SDHC, root directory and closed all applications. Tried it 5 times.

radio 1.58xxx. And I wouldnt like to flash it. I mean I would like to have a look at android - i dont care about gsm or audio.

thnx a lot
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Please guys read the wiki, these questions are already answered there. You need at least 1.65x radio for Android to boot right, if you use an older radio version you will have random results, from not booting to getting stucked on init.

For the microphone, two or three pages back you can read that it's not working since the beginning, because we (or I) can't find the parametters to activate it. That's on the wiki too.

About the progress, everything is quite the same as it was, except for a few fixes. I'm working on the bluetooth, dpad backlight, leds communication with android, and polaris touchscreen, and port back some things from the g1. At this exact time I'm trying to understand why the f*** 128+10 is not the same as 136+2 and that's not the same as 138 for the linux kernel and the cpld code. Not kidding, it's driving me nuts :(
[Touch Dual, MDA Touch Plus ROM Development] rickman2003:
thx for status report.

hope you`ll get it work bevor your nuts a falling off ;-)

wish i could help but i got no experience with that stuff... im not a noob ... it is beyond beeing a noob in this things ;-)

thx for your hard work anyway.
[Touch Dual, MDA Touch Plus ROM Development] Liquid-Silver:
Here's an experimental kernel of mine. I think i've got the microphone working. I not quite got all the configuration so please make a call in windows mobile first then start android.

Oh and I think there isn't a particular GPIO for a particular led. I think our gpios 136 -138 are used as a value from 0 to 7. So to have a solid green led with a blue led flash you write the value 7 i.e gpio 136, 137, 138 high. I think a value of 1 i.e. gpio 136 high, 137 low, 138 low is a solid green LED but don't quote me on that one.

Can you let me know how well this kernel works for you. Thanks
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi! and welcome back ;)

I've traced the gpios for charging control over usb, and I just started working on our own battery driver. I also traced all the pins for the camera, and I'll be including it all on the next git.

Will check your kernel now, and see if it gets to call from android, if it does, I'd be glad to know what do I have to patch to make this persistent... or do you have an account on the git?

EDIT: Im going to buy you a house ;) Mic is working without initialization on Windows Mobile. Tried three calls. Three worked (on different reboots) Great work man!

EDIT2: I've been adding information to the wiki (and more to come), but I'm veeery bad on formatting and I'm unable to make a working table.... Could anyone fix it a little bit?

EDIT3: Again, you're right with the leds too :) 136 green, 137 red, 138 enable.
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
badass

thankyou!
[Touch Dual, MDA Touch Plus ROM Development] cunter:
You rock!

I edited the wiki, i hope it fits your needs. Tell me, if you wanted something else.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
@****er: front page looks better thx :)

I took a few photos in high resolution of the main board of the htc nike. You can see the cpu, the power management ic (Qualcomm PM7540), the brf6300 bluetooth module (mounted at the right of the camera sensor), a Xilinx cpld, an Avago FEV776C (don't know what is this for, and the brand makes a lot of different things, anyway I guess is something related to the gsm) and few things more.

I took a look and can't find information about the camera module, and I think we would need that to implement it... any idea of wich could be?

LiquidSilver, any traces you found got a model or something like that for any of the cameras? It could be samsung like the vogue, could be an mtxxx... I'm blind with this... and of course I tried vogue's camera driver and no go...

Regards!

EDIT: Rapidshare: http://rapidshare.com/files/210484243/100KV803.rar
[Touch Dual, MDA Touch Plus ROM Development] Liquid-Silver:
Main camera is a s5k4b1fx (Samsung) and front camera is a OV6680.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
man you have to tell me how do you know all this stuff :) then I just have to use the vogue driver! (and get it to work btw)

thanks! :)

and thanks to dzo for his driver too! :)

EDIT: I have been having some troubles with charging the battery since the last android builds. If you are in windows, you plug the charger and the orange led blinks instead of staying on, and reboots, taking out battery and stuff don't work, simply shut down the phone, take out the battery, and connect the charger. The red led should light. Then put the battery back on and boot with the charger connected. It fixed it on my phone (when led was blinking it didn't charge)
[Touch Dual, MDA Touch Plus ROM Development] Liquid-Silver:
Sorry this took so long. I've attached some patches which should allow working mic. I'm not great at using git though so they might not apply cleanly but you should get the idea from the contents of the patch.

I'd like to make an important point though. I've changed the proc_comm to a wince version I found on the branch used for the blackstone work. The reason is that the AMSS in our radios are designed to talk to windows mobile. It seems the hailbut phone (G1) uses a special android AMSS. That's partly why biktor_gj bricked his phone after flashing a G1 radio, that radio probably doesn't have any nike specific code in it at all.

Anyways, basically as we have a windows mobile radio we have to talk to it in a windows mobile way and we can't use some of the android AMSS specific kernel code.

You can dump the windows mobile dmesg log by typing: task 38 into the SPL bootloader - that's how I found how the camera versions. By the way I only know task 38 works on nike - that command could be dangerous on other phones.

The KS20 service manual is also very useful in understanding how the MSM7200 chipset works although not everything is the same as our phones, a lot is.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Thanks LiquidSilver, my git tree is completely messed after trying some things with the camera, but when I have it all working again I will push your changes to the git so everyone can have it :)

BTW, tonight there have been a lot of changes on the git, I'm taking a look while I download a new tree, and I see dzo has started usb support, will see if it works out of the box (he didn't change a thing on the board files, so it may do, or at least I hope it so :)

Also saw task 38 on the bootloader... 1000+ lines of output! I saw what you said about the camera, but the poor mtty can't handle those buffer sizes, will have to try with another program...

PS: I've been doing a little research on the sdk images we're using, and we have a little problem. Bluetooth is not working, but it's also missing half of the files the android roms have for dealing with it. There's no firmware, no hciutil, no nothing. I'm copying things back, and testing some things with no real effect by now. I hope when we have usb I can open a shell instead of typing to the keypad, and be able to try some new commands. If anyone needs it I have a little list of programs that are missing, firmware files and such.

Regards! Biktor
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
hey biktor i assume youve seen this

http://hackaday.com/2009/03/11/android-app-scans-barcodes-downloads-torrents/

pretty handy :)
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
yeah saw it some time ago, I've been reading hackaday everyday for the last three years :) definitely handy, when we can get something stable to work with...

btw, just a comment in case anyone's working with the last git tree: PHONE WILL NOT BOOT UNLESS USB IS PLUGGED IN AT BOOT TIME. Dzo made some changes to start usb. The kernel crashes if usb wasn't active on winmo, but if it is at the time of the jump it resets usb fine. It's a start, but I thought I'd let you know.

Other issues, mic patch works, but sometimes calls gets dropped now. It didn't happen to me with liquidsilver's kernel. Im trying to figure out if vogue-hw is making something strange, but with the last three commits it can be anything...

As always, when I get something stable I'll post a new bootkit with the last images from march (the last I posted is quite old now)

EDIT: After power collapse and resume the mic stops working, and it drops the call most of the times, we'll have to look onto it and patch a little bit more :)

EDIT2: I think I might have fixed the power collapse and resume thing, and calls don't seem to drop by now, anyway, the phone may need some time between calls (it rejects them some times, I guess the modem needs some time to terminate before being able to handle a new one). While I'm writing I have a call in progress and didn't break after 2 minutes, so I think it's a bit fixed now.
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
thanks a lot. i appreciate it. im trying to keep up and learn, its a shame i dont really know enough to help hands on right now. keep up the good work.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Want to test an image?

Rapidshare: http://rapidshare.com/files/211069314/zImage

Remember to boot with the usb connected!

About the changes since the last builds, not too many, but:

mic patch by liquidsilver

start at usb (not ready yet)

start at charging detection (disabled for now to get the calls stable first)

some cleanups and fixes here and there

funky leds on start :)

What I would want to know is if mic works for everyone with/without initialization on winmo, and after suspend/resume on android. It works for me, but that doesn't necessarily mean it will work for others...

Forgot to say, battery meter seems to read the values right now, 10% battery on winmo, 10% battery on android too :)
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
no problems here! everything working flawlessly! hung the first time during a call and had to soft reset though, but every other time after everything is perfect both with/without init calls on wm.

the funky leds put a big smile on my face

any ideas on battery drain? the phone gets real hot and only lasts a few hours on a full battery. is that a power management issue? solvable?

great work guys.
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Power management doesn't work too well for now that's true... by now I'm more concerned on trying to make things work, but we definitely need to take a look at it, 6hours of battery life isn't good for anybody else...

EDIT: I've built another bootkit so you can test out how the battery goes. System.img is dzo's 03/01 version, so if you already have it you don't need to copy it back. I noticed on my files that my default.txt pointed to sleep_mode=1 instead of 0, let's see if it makes a difference. I also added the battery capacity value that seems more correct on my phone. When it's 91% on winmo, is 91% on android. I hope it's the same for the rest of the battery capacity..

Rapidshare: http://rapidshare.com/files/211389157/Bootkit_03_20_2k9.rar

PS: 89%on Android, 89% on Windows Mobile :)

EDIT2: Phone is a lot cooler than before, and battery percentage seems to be accurate. (now on 76% battery on both OSes after 5 reboots and listening to music, good enough for me :))
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
this is great! much better clarity with the new resolution!

just a note, if you remove the slideaction landscape feature in default.txt it disables the keypad backlight in android (would be nice to still have the keypad illuminated without the landscape feature).

im really impressed. great work. phone does run a lot cooler! i'll keep playing and testing.
[Touch Dual, MDA Touch Plus ROM Development] rickman2003:
hey guys! i`ve noticed a bug or something like that in the newer releases of your bootkits.

i cant type an sms!

when i click on "new message" i cant write anything with my hardware keyboard and software keyboard wont open. when i klick on the " to" textfield to add a receiver it blinks orange one time and thats it..

same at the textfield where i suppose to write.

hope you can help me out! an hope you understand my english^^... cause I´m german. sorry for any grama mistakes etc. ;-)
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
That's.... starting to be a problem for me too, but with no easy fix. The problem isn't on the kernel, but on Android. If you close the keyboard, when the screen rotates you'll be able to type, but when you open it back it will tell you to slide the keyboard to type. EDIT: I was wrong, we're using g1 devphone images, that's why it does that.

Anyway, I have the android sources, I'll take a look and let you know if I find a way to disable that (maybe recompiling the sms application removing the sliding options...) (weren't there an option on Spare Parts on older images?)
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
great update, man.

as you probably already know, with #3 kernel, i noticed the OK key was not mapped. i guess this shouldnt be too hard to fix with it already working fine in #1.. touchscreen is a lot better but still kinda buggy compared to with the vogue driver.

awesome work!
[Touch Dual, MDA Touch Plus ROM Development] jerpelea:
i forgot to map the ok button //we have the key code :d

BR
[Touch Dual, MDA Touch Plus ROM Development] Boylen:
I'm unable to run it with the	nike_march_key_TS_1852.zip.

Replaced the startup.txt and zImage, but after the 'booting linux' dialog, the dialog disappears and it hangs...

Do i have to update something else?
[Touch Dual, MDA Touch Plus ROM Development] Demostrike:
I have some linux and C experience. I don't have much time to develop but I'll gladly test for you guys if you need it. =]

@ Boylen: How long do you wait after the freeze? mine takes a while before changing to the linux boot screen. Also which haret.exe are you using?
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi, I can try to help developing android for the htc Nike. I just need my phone to get to me (it's shipping), and some sources to begin... where could I get a diff or a tar.gz with the progress so far? (I mean in sources so I can take a look at the drivers...)
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
hey, biktor, im hoping jerpelea will post his patches. if not, he will probably send you them if you ask nicely lol.

a bit of news;- the guys in the kaiser forum are buying a kaiser for 'dzo' (the guy who ported to the htc vogue) and hes gonna fix the sd driver (and a bunch of other things).. this is great news for us nike owners since theres a good chance the fix will work for us too.

lets keep our fingers crossed.
[Touch Dual, MDA Touch Plus ROM Development] Boylen:
I wait about half a minute. Not sure which version of Haret.exe I'm using. Didin't know I needed an other one for newer builds?

how can I check the version?
[Touch Dual, MDA Touch Plus ROM Development] sethp:
any progress lately guys?

hi everyone,

any news on the android front? i've been playing around with the current working version that seems to be derived from the polaris one. As far as i can tell we're mainly waiting on SD card drivers and some keymaps. Is this the case or is there more to do? Can anyone point me in an interesting direction? Long-time Unix developer here...
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Hi, I'm waiting for jerpelea to upload the source or some diffs elsewhere to start with this...
[Touch Dual, MDA Touch Plus ROM Development] jerpelea:
the files are waiting on the 1 st post till 10.11.08:))

BR
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Didn't see that! Thanks man!

By the way, yesterday I saw that GSM is already working on the kernel, even if it has no sound... will have to play a bit...
[Touch Dual, MDA Touch Plus ROM Development] jerpelea:
gsm works,mic is working , speaker not

BR
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
is mic working?on my htc it isn't... wich radio are you using?
[Touch Dual, MDA Touch Plus ROM Development] jerpelea:
i have tested with my oher phone and it works

1.65.28.25

BR
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
Jerpelea, I'm curious... your touch dual is 16 key or 20 key? Niki or neon?

Mine is a niki100, with a 1.58.21.23 radio and Mary rom. Phone works, though some keys are screwed (L is the DEL key, for example). I've seen on your code that the keyboard driver supports 30 keys (wich is what my phone has) but has some of them disabled, I assume you're running a 16 key phone?

Power management doesn't work for me either. With windows mobile's power management features set (30 second light time out, power down on 1 minute) the phone stays with lights on for anytime. And it doesn't get stucked. I guess this is normal since kernel is not fully developed, but as someone has previously said that his phone went off after a while, just so you know in my case it doesn't do that.

Got the git tree from linuxtogo, patched it... but not compiling yet... could I get your config file please?

Regards, Biktor

EDIT: Forgot to say, phone WILL NOT BOOT when there's no sim, it will just get stucked before HaRET says "Go Go Go", and with the progress bar uncompleted. With SIM installed works just fine.
[Touch Dual, MDA Touch Plus ROM Development] jerpelea:
i have 16 keys device

:d
[Touch Dual, MDA Touch Plus ROM Development] biktor_gj:
haha mmc gets detected if you keep holding the power button! Missed pin floating around!
[Touch Dual, MDA Touch Plus ROM Development] nixu:
Required files....

Hi Guys..

I have been trying to make use of the zimage that is found on the second post of this thread, but did not have luck.....

Could some one upload ALL the required files including the HaRET, initrd-android, startup etc.... As there are to many different files running around and do nit know which are the correct ones to get Android running on my NIKI100 (Radio 1.74.OliNex).

If I manage to get it running I will setup mu Ubuntu to give a hand in the development. Got loads of C experience and some good Linux background too.

Hope to hear from someone soon

Nixu
[Touch Dual, MDA Touch Plus ROM Development] kvstrien:
Isn't there a SVN-repository or something alike? That would ease up participating a lot...

btw I would like to participate. I'm studying computer science - have C and Linux-skills..
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
if you guys can wait a week or two, till the new kaiser kernel is released by dzo it will make everything so much easier for us.. i'll set up some files to make things more accessible for you. im praying the sd is exactly the same which will require no driver tinkering at all and we can work from there.

i'll keep you notified.
[Touch Dual, MDA Touch Plus ROM Development] ohookins:
Hi, I've only just started trying to use Android on my Niki100 that I got about a week ago, I know very little about the whole thing - mostly through a colleague at work so bear with my ignorance.

So far I've only been able to boot Android successfully about 2 or 3 times. The weird thing is that nothing changes between boots. It worked once last night, and once today but I then shut down and power the phone up again and it won't boot.

When it doesn't boot, HaRET loads the kernel and the bar graph goes to the end but there is no activity on the screen after that point. Is there anything I can do to provide more information which will help diagnose the random booting issue?