yashsingh1/xdaforums huggingface dataset:
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
Hello guys, want to have Froyo on your device? i've been testing and amzingly it run on Nike. Although there is a few bug just like the other android for Nike, but at least you can try the FROYO.

Here is what you need to do:

1a. If you haven't try Android before download attached andboot.zip, extract it to your SD card root.

1b. If you already have android build on your device, you can run copy androidinstall you've downloaded to andboot folder than do reinstall your android through haret. Remember to backup before doing anything.

2. Download androidinstall from the original thread Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS13] [8/18/10]

3. Backup! than, clear whatever "android" stuff you have from sdcard (I dont want it to get caught up in the install) especially your andboot folder

4. Extract contents of downloaded zip to temporary directory

5. Copy extracted /andboot folder to the ROOT of your SDCard

6. copy zimage to /andboot folder with this version (credit to mblaster) get in from http://84.23.71.227/kerneloftheday (i'm using zimage with vibration on my nike100 with zimageNike name) or you can use attached one - the newest from mblaster with audio fix (remember to extract the zip :) ).

7. overwrite default.txt with attached default.txt

8. Run HaRET, than hit “run” to launch android

9. Press and hold center of dpad after hitting "run" and follow the directions in the NoMoRootFs menu system

10. Install android system

11. Quit installer

12. Booting into Android

13. After you can see android logo wait about 15 minute

14. then shutdown and open up your phone again (should boot into winmo)

15. start haret and boot again to android

16. your android is ready to use

Working: Call, sms, ring, data (listed apn)

Not Working: Bluetooth, camera

Bug: Very difficult to receive call (maybe kernel problem???)

LEt us ask dzo (kernel inventor for vogue) to make update for Nike kernel to get all that stuff working :)

EDIT: thread author change it name, so i'll follow that too :)

UPDATE: I'm using dzo odex version from androidhtc
[Touch Dual, MDA Touch Plus ROM Development] Maxxd01:
Very good post!

Whats wrong exactly with receiving calls?

I dont believe BT/Camera will work on any Android ROM for nike. This problem come from months since the first release, and never. So, or we buy a really android smartphone or we change for vogue :p

Installing RLS4 + Kernel with vibration 03 June.

EDIT: Now I understand. Receiving calls dont work, its like we have phone turned off. Data connections work (...) Its not fast and ADW Launcher crashs often (or we have to "wait" many times). 2.1 Much faster. Also, screen its very not aligned (sorry, dont know the right word). Many times if I want to press a widget I have to point to the another one on left (annoying using keyboard). Still the same issue with hardware button 1. Three times pressing this key, and my screen goes black. Sometimes, I have ADW Launcher, go to setting, go back, and then I have laucher PRO.

Its a cool ROM, but I think useless for now. Lets hope anyone can solve the problems.

Thank you.
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
yes, useless if our phone can't receive call, so we'll have to waiting for that, hope someone can solve it?

just contact dzo, he don't have time for maintaining a kernel for Nike. he want someone else to do that.

do you know someone who have some knowledge in C and a linux box to compile the kernel?
[Touch Dual, MDA Touch Plus ROM Development] Maxxd01:
I know a lot of people, but no one with a nike. I know some C and linux, but I never programmed a kernel, however I can take a look. Where is the source code? Just found for vogue.
[Touch Dual, MDA Touch Plus ROM Development] mblaster:
Check my kernel thread. You will find the diffs (basically text files that show changes in source) to the vogue kernel source on my download page.
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
yes, maxxxd01 please co-operate with mblaster, both of you is our hope for nike kernel. at least for now. thanks. keep up good work.
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
new zimage from mblaster works for audio, and no touch screen problems on mine, receiving call is also working for me using froyo - at least for now , still testing it -

here is what i did:

1. update newest kernel using mblaster kernel with audio bug free from new zimage from mblaster works for audio, and no touch screen problems on mine, receiving call is also working for me using froyo - at least for now , still testing it -

here is what i did:

1. update newest kernel using mblaster kernel with audio bug free from http://xdaforums.com/showpost.php?p=7021840&postcount=3

2. using phone prioritizer from http://xdaforums.com/showthread.php?t=558822

maybe you guyz can try it
[Touch Dual, MDA Touch Plus ROM Development] mblaster:
OK, I know it is the third time I am posting this, but I don't want you to miss this...

Kernel service up again with audio patch included. Hope verything works now. Niki100 version is also patched now, touchscreen problems seem to be vibration related on niki100 (thats why there is a vibration free version especially for theat phone).

http://84.23.71.227/kerneloftheday/

PS: Let me know if everything is fine now.
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
looks like this newest build doesn't need any phone prioritizer anymore, it just ring as it should be, so no more receiving call lag.
[Touch Dual, MDA Touch Plus ROM Development] Maxxd01:
I dont think I can help, mblaster works much faster :)

I'm confused, receiving calls problem solved. But, for kernel with or without vib?
[Touch Dual, MDA Touch Plus ROM Development] mblaster:
I did not fix the call recieve bug, but I suspect it not to be in the kernel anyway. Android has a very greedy memory management, which tends to kill the phone app from time to time. On my G1 I have similar problems with some ROMs.

Perhaps it was just fixed in R5 of the ROM?

BTW: Any help is appreciated :)

Booting Froyo on my nike for the first time. Nice CM5 Bootanimation :cool:
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
wow, that mean receiving call problem is related to ROM, should thank dzo for that,

mblaster, yesterday i try to use newest kernel but it seems like sometimes it makes my touch screen not responding (i'm using zimage with vibration), then i revert back to zimage_audiotest, and still haven't find the same bug. anything wrong?

about the audio, it seems like a little larger, maybe can lower it a little thanks.
[Touch Dual, MDA Touch Plus ROM Development] leonardoaraujo:
now yeah! I'm getting anxious, why now in an android niki100 (20 keys) is not just a toy is almost functional.

God bless you Mblaster, dzo you are almost there !!!!!

Vibration and camera are not so important for now, at least for me .. like the headphones because I walk a lot, but I will not ask more for it.

I think that Froio is more functional, but it seems late in the touch screen sometimes, or locking out of memory, not sure, but one question, where do I set the swap Froio? seems to me that with the eclair made work faster, Froio am running with EXT2.

Thanks!
[Touch Dual, MDA Touch Plus ROM Development] abcorp:
Hey guys. I'm trying to use Android on my HTC Touch Dual.

It runs ok, and it is fast now using the froyo. But I got a problem that I don't understand...

I boot up on Android and I have sound. I then make a call and I can hear it well... I end that call and after that I can't get anymore sounds from the system... If I make a new call I can't hear anything from the other side... :( :(

Please help....

Could it be the radio version I'm using!?

Thanks.
[Touch Dual, MDA Touch Plus ROM Development] jiaorong:
I ask, the system did not contain Chinese, where I can download it?:eek::eek::eek:
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
MAybe you can try to flash other version of radio. I'm using 1.65.28. you can get the link at insomnia thread

maybe you lack the input system and language only, i can run ucweb chinese version on mine, for input system try to search on web. sorry i can't help. thanks
[Touch Dual, MDA Touch Plus ROM Development] abcorp:
Thanks for the reply.

Sorry about asking this but I need to HardSPL my device to do that?

I saw a post saying this:

"Note: The USPL is not a "HardSPL" which means it gets overwritten when you flash a full ROM. You have to run the SSPL if you want to flash any ROM again.

The HardSPL is never overwritten which in case of flashing trouble is a great insurance. Should you want to flash another SPL or USPL you must run the SSPL."

Can I use the SSPL method instead? It seem's less dangerous...

I've never did this so sorry about the question. :o:o

Thanks man.
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
do you never flash custom ROM to your Nike?if you never flash you should read the tutorial in the sticky before doing anything further to prevent error on your nike. there are a lot of tutorial to doing that
[Touch Dual, MDA Touch Plus ROM Development] abcorp:
Ok. Thanks a lot.

I already flash other devices but not this one... anyway I will read the tutorials.

EDIT: Thanks a lot youngsien. I already flashed the Radio you indicated and now I can make calls ok in android. :D

Xda Rulez!!
[Touch Dual, MDA Touch Plus ROM Development] Aqrab:
latest version video

http://www.youtube.com/watch?v=zlf5tEpyKGY
[Touch Dual, MDA Touch Plus ROM Development] leonardoaraujo:
after switch on for a while, about 30 minutes my device does not receive more calls, I'm using the latest version.

derepente, it seems that the processes stop working

no sound, nor does voice calls ....

NIKI100

Radio = 165......

Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS8]

lastest Zimage

in SDcard

any idea??
[Touch Dual, MDA Touch Plus ROM Development] andrei.nica:
first of all, try with the latest released froyo to date, RLS9, then make sure you downloaded the zimage for niki100 (no vibration) and renamed it so that if matches default.txt

if this doesn't solve your issue, all I have to say is "good luck" :)
[Touch Dual, MDA Touch Plus ROM Development] andrei.nica:
on niki100 the zImage with vibration makes the touch screen to stop responding within the first unlock of device. however, to get here at least one has to first boot with the non vibration kernel so as to pass the "touch the droid to begin" welcome screen.

still, there is an interesting workaround: with vibrating zImage, if I switch to home screen (pressing twice camera button) and start astro with the dialpad, the touchscreen becomes responsive again, untill next sleep. maybe mblaster could take a look at what exactly could astro call upon as to make the touchscreen work again.

still there is no data connection at least on my niki100 with latest kernel with/without vibration

another issue I came across with latest Froyo is that the system freezes when I try to start the camera instead of displaying an error message..

yougsien, updating the system should consist only of installing the latest froyo build and keeping data or should we also do something else. if that's the case what is the difference between andoidinstall and andoidupdate?

maybe you should write about that in the first post, as a lot of people now have one release and just want to update.

10x
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
no problem with me with the kernel, i'm using that one attached on #1 post, haven't try latest kernel.

yeah, for updating sometimes it need to clear the data, sometimes not. so depending on the build you want to install. To make sure everything is working good, i suggested you to clear data if you change from one build to another one (like from eclair to froyo, from mint's build to incubus's build), but if you just updating your build (dzo froyo dzo froyo with different RLS) maybe you can try without clear data.

androidinstall is the system of android build, androidupdate is just some update or addon to the system (like addon apps)

ok will add some the #1 post
[Touch Dual, MDA Touch Plus ROM Development] andrei.nica:
that was a fast reply, thanks :) I tried with both the default.txt and the zImage in the first post you provided but the touchscreen just won't work.. seems that only non vibrating versions are working on my niki100 20 keys device.. this is a shame. maybe I have to set something differently but I just can't figure out what..

and on the latest build, the astro trick to get the touchscreen responsive just doesn't work

is there anyway to find out where the bug in the kernel with this device is ? (data isn't working, also)

10x
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
on my device both touchscreen and data is working. i have niki100 16key. For data, have you set your APN on setting-wireless&network?do you select it as default after creating?do you tick allowed data connection option?
[Touch Dual, MDA Touch Plus ROM Development] Luks24:
gallery

gallery doesnt show up my pictures it says sd card not mounted.could someone help me out
[Touch Dual, MDA Touch Plus ROM Development] mblaster:
IMO the only difference is that the filename androidinstall.tar tells the script to wipe system partition before copying (and ask for a data wipe), while androidupdate.tar keeps system and just copies the files (overwriting existing ones).

By the way: RLS 9 is out ;)
[Touch Dual, MDA Touch Plus ROM Development] andrei.nica:
i'm wandering if the fact that I didn't partion the SD might have anything to do with this. are the 2 ext2 partitions really changing anything else other then the I/O speed due to double conversion?
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
thanks for the explanation, mblaster, any news on kernel improvement?any news on cameralib?or bluetooth?

try to restart your android, maybe you have mounted it on your computer or somewhat? android seems has mount or unmount sd function, so maybe you get that chosen?

not really, as i know partition only make file more easy to modified and maybe a little I/O speed for the system.
[Touch Dual, MDA Touch Plus ROM Development] Luks24:
ok ill try to reinstall it again,i revert back to myns warm eclair and gallery works fine but there seems to be a problem on voice calls so i really want this built.Thanks
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
newest build is RLS10, download from original thread, on mine no gallery problems
[Touch Dual, MDA Touch Plus ROM Development] Luks24:
i did reinstall rls9 but still no pictures on my gallery,but i can see them on my file manager.oh well,ill try rls10 hope it works
[Touch Dual, MDA Touch Plus ROM Development] leonardoaraujo:
lucks24, test, place your images in sdcard/100andro....não place in many subfolders ....

worked for me .....( RLS9)
[Touch Dual, MDA Touch Plus ROM Development] Luks24:
ok thanks ill try it on rls10
[Touch Dual, MDA Touch Plus ROM Development] leonardoaraujo:
Luks24, if it does not work, try to simplify the names of the image without (%¨&_-), only using letters, and simple names, they procedure did and it worked for me, I have helped ... ahh, noting that very large images (kb ) Can cause problems too .. high resolutions .....
[Touch Dual, MDA Touch Plus ROM Development] therealwheely:
Confused

I'm not sure what to download. On this site there are two different files: NBH and ZImage. I downloaded the most recent versions of both of them (zImage-froyo-07-07-10 and voguimg-240x320-froyo-07-07-10.nbh) and placed them on the SD-card. Do i have to rename them first? I have a T-Mobile MDA Touch Plus (niki200).

After running 'haret.exe' the installation starts. I see some text scrolling and a Linux Logo. But after a few seconds i get an error: 'Failed to reach system.img on SD Card'. Where can i find this file?

I have already installed HardSPL on my phone. And also tried to install voguimg-240x320-froyo-07-07-10.nbh using the ROM Update Utility.

Can you please give me some more details on how to use these files? :confused:
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
nope, you don't need to download zimage or voguimg, scroll lower to find link to download RLS XX. Remember after running haret.exe press and hold the center d-pad. after some second it will tell you to press center d-pad, press it and hold again then you will see installation option. For normal running no needed to press center d-pad for booting to android. Hope you like it
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
it's weird. working gallery on mine, don't have to in andro folder, it will search on your whole card for images. Do you get the waiting/searching text at bottom when you launch gallery?it will take a while to search images on your card before it loaded all, just be patient.
[Touch Dual, MDA Touch Plus ROM Development] Luks24:
nope all i get is " sd card unmounted and then it says you have no item on this collection,worst ive deleted all my android and cant download now the rls10 thanks for your help ill try again tommorow
[Touch Dual, MDA Touch Plus ROM Development] therealwheely:
Thanks

Thanks for your tip! I'm gonna try this and let you know if it worked. :)
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
you're welcome
[Touch Dual, MDA Touch Plus ROM Development] masayume:
Quick question

Hi, My friend had what i thought was an HTC touch - which got me very excited seeing how well supported it is with android. When he gave it to me i realised it's the touch duo (which doesn't even have a link in the front page and is instead in the legacy devices section :().

Having found this thread for exactly the build i wanted i now have a few questions:

1) Using the very latest RLS10 build, how supported is the niki100? What works and what doesn't?

2) This being a stock model what steps would i need to take? It's locked to Orange so I'm going to first run the cid unlock which will also remove the sim lock (via hxxp://xdaforums.com/showthread.php?t=395945), then flash with hardspl.

3) Can i flash Incubus26Jc's RLS10 build of froyo 2.2 directly to the device (and not via haret)? If so what's the best method? What's the best radio rom to update to for this?

Or am i better off trading this down the local CEX for the older Vouge model (I'll probably get cashback too :P). Aside from the sliding keypad there doesn't seem to be any difference between them. Neither has wifi (well I'm not interested in the gsm version of the touch :P) and neither have gps (how crappy). So i guess i wouldn't be missing much. Then again if the hardware is the same shouldn't the rom from the vogue work as perfectly on the dual? I really wish there was a nice shiny 2.2 rom for the toshiba tg01 which i also have lying around :( WM renders the device useless to me.

I'm a developer and this is far from my first phone I've flashed/patched/unlocked/modified so please feel free to be technical with me. This is my first android though :o
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
yeah, sad to see that touch dual move to legacy device, but it's better than other legacy :)

1. with android, you can making call, receiving call, sending sms, working data connection, a few thing left is bluetooth, camera, n in-call volume. The lack of developers in kernel make this hard to accomplish. running android also sucking your battery power more than with wm.

2. yes, unlock then flash hardspl and your WM build

3. you can't flash android to the phone, the only way to run it is via haret.exe.but you can have android UI feel with this.

If you want fully working android, it is better to be with vogue since the android kernel maker dzo and incubus come from vogue, with vogue you have wifi, bluetooth, camera working and all thing is working with android, you can also flash android directly to the phone so running android is faster than via haret on sd card.

But if you know some C maybe you can help us in developing Nike/Touch dual Android kernel?maybe help mblaster who is the only guys behind nike android kernel?

hope this answer your question.
[Touch Dual, MDA Touch Plus ROM Development] masayume:
Thank you for your answer youngsien.

Yes i do indeed know C (not the strongest of the languages since i havnt spent much time with it and pointer arithmetic makes me unhappy :() however i have no experience in either embeded, kernel or driver development so i'd need a pretty large crash course. I specialise in server side logic and userland software.

I'm really confused with the HTC touch. According to HTC there's the GSM and CDMA version. One has wifi and a slower processor and from what i can tell support for 3G networks (for UK). The other is CDMA with a faster processor, more memory and no wifi. Neither have GPS, but according to Incubus's build it does :/

So there are actual hardware differences between the vogue and niki then. Grumble grumble grumble.

The funny thing is that CEX values the touch gsm the same as the touch dual

Update:

So i've installed hspl 1.15 via sspl and then ran Niki SuperCID and Security Unlocker.

Next i reflashed to hspl 1.22 and updated the radio rom to RUU Nike Radio 1.71.09.01K

I now have an unlocked and updated Niki100 and in just waiting for Insomnias v4 wm6.5 rom which he will be posting a link up after he wakes up (so for me that's before i go to bed :P).

The fact that we probably will never have wifi on this device (even though apparently the chipset supports both wifi and gps) means that it's sadly useless to me. I want to play around with the Insomnia build a bit and have a poke at android via haret but ultimately i see myself trading this in for a vogue and flashing it with froyo. I'd be willing to have a stab at anything i can help out with on the android side in the meantime since this would actually be a nice low end droid phone and i hate seeing hardware that's perfectly usable go to waste.
[Touch Dual, MDA Touch Plus ROM Development] youngsien:
sad to hear it, i think i found another man to incooperate with mblaster to develop the kernel.

what you mean maybe is htc elfin or touch3g? yes there are a few device with almost the same look with touch dual and vogue with different spec, and for the best for android is vogue because all android developers comes from them.

and with nike you don't have wifi and gps but with this you can use wm and android and it is cheap to show off both of this to your friend what you've got :)
[Touch Dual, MDA Touch Plus ROM Development] masayume:
Well like i said. I'll hang on to it for a little while.

The thing is that i can take a vogue, overclock it to 520MHz, GPU to 200MHz and run 2.2 on it. With wifi and GPS i could see this as being a practical replacement for my ****ty symbian phone. As much as i love the e71, symbian is so bad that i only use it as a phone and nothing else. Seeing how it has a fast data plan i wanted a phone i could actually use it on. Plus i've wanted an android phone since i got my hands on the initial SDK pre-release :cool:

All these multi models confuse the hell out of me. It actually scores minus points for HTC in my book (htc do a lot of things i don't like them for). Their site lists vouge as being touch gsm and touch cdma. The cdma model has a 4xxMhz processor, more memory and no wifi and the gsm one has wifi, less memory and a 2xxMhz processor. So i'm going to go out on a limb and guess that the one i want is the gsm one (or is cdma == 3g? there more abbreviation in the mobile market then in the military :/).

In short, unless my provider will give me an upgrade to the galaxy s (which i've fallen in love with when i used it the other night) or there's a stable finished version of android for the iPhone 3G or if nokia's upcoming n900 successor is as good as all my friends in r&d keep telling me (I'm pissed at Nokia anyway for being so useless when it comes to providing a seamless consistent experience and more or less total lack of support or competence of support) I'm planning to go the vogue way. I like the slide of the touch dual and it's a nice device (touchscreen is a little annoying - im spoiled by newer shinier phones :p), but windows mobile needs to die. If it needs help I'll be more than happy to pull the trigger. Twice.