yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] tuxhero:
Yes SPL is different but we don't need to work on SPL because we first boot wince and then we will be booting Linux kernel.

Actually difference is not SPL it's amss. They Android amss is much more Organized cleaned and regularly updated. Where as our Wince amss is same right from Diamond to Touch Pro 2. Android Developers Changed few thing added few new features and removed lot of features. Now getting Wince Amss in Sync With New Features of Android Amss is our task.

With the Changes in Android Amss Clock,Vreg and GPIO function are missing in Win CE Amss so we have to find some alternative to them. If we are able to find correct and perfect alternatives to this function then i bet our Blackstone will be the first Fully Android Compatible Phone (Like Native Android Phone). Not only Blackstone guys Diamond/Touch Pro/Diamond 2/Touch Pro 2/Blackstone share same hardware and same amss and same problem so if we crack Blackstone then our work will be helpful to all this platforms.
[Touch HD Windows Mobile ROM Development] tuxhero:
All my code, R&D Information etc etc.. will be posted ones i finish clock code.

Why After finishing clock code?

Clock is the core component with out it it's never going to work perfectly so with out clock code other codes are never going to be stable.

Ones i am done with clock i don't need any of the Information (Copyrighted) so that i can truncate all this information be in safe position and Release my code.
[Touch HD Windows Mobile ROM Development] mcdull:
Thanks for your information. I will be keeping my blackstone definitely just for this android project. My Winmo is getting very unstable and generating a lot of heat where I have no idea of what it is doing.... (Guess it is the radio part having the issue).

WINCE 4 is really old technology and hopefully we can use some new technology soon..
[Touch HD Windows Mobile ROM Development] jtwinn:
Hey Tux, how long do you think it will take you to finish the clock code? And just to be clear, the clock codes are really the only thing that is holding the process up? I am too excited about the possibility of Android being on my Blackstone. Good luck and a million thank yous to you for your efforts.! :)
[Touch HD Windows Mobile ROM Development] core7x:
tux is hero.... and +1 to tuxhero
[Touch HD Windows Mobile ROM Development] purec0de:
.....Samsung Galaxy i7500

Hi folks...

there seems to be a lot of talk regarding borrowing code from other HTC android devices to aid this project.

I just wondered does the Samsung Galaxy i7500 use the same processors as the Blackstone...i know its a 528Mhz Qualcomm....not sure which one

i understand this phone is being released some time next week.

is there a chance code from its ROM will help the Blackstone Project??
[Touch HD Windows Mobile ROM Development] tuxhero:
May be if you point me where i can see it's source then i can say how much it helps. Every bit of information is important.
[Touch HD Windows Mobile ROM Development] kva:
Thanks for your job ! This is really right way to go now !

I'm trying to make some research on my own, but my knowledge in winmobile and arm-based devices is not so good.
[Touch HD Windows Mobile ROM Development] mcdull:
Hi, as you see in my other post.. do you think different version of SPL do affects the systems?

Or in other words, is kernel actually SPL dependent?

Thanks for your sharing.
[Touch HD Windows Mobile ROM Development] tuxhero:
No not at all
[Touch HD Windows Mobile ROM Development] purec0de:
just having a quick look while at work...

http://pdadb.net/index.php?m=specs&id=1863&c=samsung_gt-i7500_galaxy

its a Qualcomm MSM7200A

so i suppose thats not much help as the Blackstone is a MSM7201A ???
[Touch HD Windows Mobile ROM Development] Cyclone_storm:
I already bought a Samsung Galaxy 3 weeks ago in Germany. Because they

are already being sold in Germany en Great Britain. :D :D :D
[Touch HD Windows Mobile ROM Development] qwerx:
This is nice, but what about not booting wince. installing a "new"? SPL and flashing an image like hero image? (I edited the message so you can understand it better - I want to erase wince forever from my HD, I have a hero and it's amazing and I want to make use of my HD beautiful 800x480 screen and in the same time get rid of wince forever). Is there any hope for a SPL that will allow android install from scratch?
[Touch HD Windows Mobile ROM Development] tuxhero:
We get to in ones we are fully ready with kernel. Some people try it but not success.
[Touch HD Windows Mobile ROM Development] ASK768:
on pocketnow, theres an article about a phone which supposedly can dual boot winmo and android. the article is here

http://pocketnow.com/tech-news/dual-booting-eston-mid-02-sports-android-and-windows-ce

Perhaps we can extract some useful code. Unfortunately, as far as i know, the hardware is rather different (and outdated comparatively) to our blackstone
[Touch HD Windows Mobile ROM Development] tuxhero:
It's Nice ASK786 but we can't use it because it run on XScale processor. But the idea is really good.
[Touch HD Windows Mobile ROM Development] core7x:
maybe after full porting of android on HD and we will think

about dualbooting or bootloader..who knows one day..

we all know about the same spec HD - other native android..

just a piece of code make it diff..

waiting for the tuxhero release matured code from scratch on

HD Android will make other sense from other developers..

im studying android kernel .. and im wait for that ..
[Touch HD Windows Mobile ROM Development] p3ngwin:
nice to see this goal still being worked on.

is the wiki for Blackstone android still the best place for updates or is there another best place for progress?
[Touch HD Windows Mobile ROM Development] lambstone:
tux, i was just thinking. Since most android phones are HVGA res, and our blackstones are WVGA, could there be an implementation of a virtual dpad?
[Touch HD Windows Mobile ROM Development] tuxhero:
Yes we can implement it very easily.
[Touch HD Windows Mobile ROM Development] lambstone:
wow, that will really be awesome. too bad no one made a virtual dpad for our blackstones in winmo. One additional reason to ditch winmo for android! :)
[Touch HD Windows Mobile ROM Development] tuxhero:
We need to mod Display Drivers In Wince For that and it's complicated. In Android We are writing our own Display Drivers so any thing is possible.
[Touch HD Windows Mobile ROM Development] lambstone:
Cool. I wished I knew more about programming now. All i can do is just a bit of actionscript, html and other basic languages :(

So any status updates?
[Touch HD Windows Mobile ROM Development] FabianNL:
Just wait till he post something, please stop posting request about updates :)
[Touch HD Windows Mobile ROM Development] kosworld:
hi

the theme is available for when

as do a long time already

rechercher
[Touch HD Windows Mobile ROM Development] tuxhero:
Thank You for supporting.

Failed in getting proc_comm to work so i decided to implement clock with manual entry's. On my way to finish clock with manual clock values. Expecting to finish it in 1 week. There are lot of thing in clock guys so it will take time to find all values manualy and add them.
[Touch HD Windows Mobile ROM Development] imtiyazee:
We all believe in you, Hope you do it the right way.
[Touch HD Windows Mobile ROM Development] Ethania:
Manual editing always takes time. (and I find it quite boring myselfe)

Actually im not sure about what "Tux" means, but when you are done,

you certenly will be a hero!

Thanks for the effort so far.
[Touch HD Windows Mobile ROM Development] garyjmobey:
"Tux" is the name of the Linux Penguin
[Touch HD Windows Mobile ROM Development] Ethania:
Haha...

Of course the penguin has a name ;)

How come I was the onlyone who didn't know...
[Touch HD Windows Mobile ROM Development] miniterror:
i didnt know that to till now;)
[Touch HD Windows Mobile ROM Development] tuxhero:
http://en.wikipedia.org/wiki/Tux
[Touch HD Windows Mobile ROM Development] NeoS:
Hmm, it seems the Kaiser and Polaris have Android running with SENSE interface through Haret... Once the higher resolution distros start dropping in this project would get a boost, right?
[Touch HD Windows Mobile ROM Development] mcdull:
I think tux is now focus on the kernel part which refers to the very root part of the system. Once it is done, we shall have a very solid foundation to build customized OS on it. We may not use the android as well, we can have our new linux based OS but it will be the next next next next next ^n step.
[Touch HD Windows Mobile ROM Development] brumbrum:
I start to think that we attack these problems from the wrong angle.

Why not start in this angle instead:

Modify or change the internal code/firmware for radio and cpu in the blackstone so we can flash the Dream/Magic internal code, SPL and radio-firmware onto the blackstone, and by doing that use the default kernel that is available from HTC by "just" adding the screen- and touch-code that has been developed already?

The big question here is though: How do we JTAG the blackstone-hardware easy, or find any other way to easy access this firmware/code for reflashing these chip without breaking the device before we can get our new operating system and software onto it? Since the hardware is similar this must be possible... but maybe to hard to be possible to do at home?

Sorry if I am not that good at explaining, but I hope somebody understand what I mean and maybe have the technical knowledge to explain why we are not doing this instead?

// Johan

-- edit --

I know, if this was possible it isn't possible to use the WM roms that is available. You can't, if this method is possible, use both Android and WM.
[Touch HD Windows Mobile ROM Development] ASK768:
I think if i understood your post correctly, what you are trying to say is that we should just modify android device's ROMs. We cannot do this because of the hardware differences which at a low level make all the difference. Once Kernel is sorted, then we can pull things from the ROM like UIs, but basic functionality cannot simply be ported as our device has too many differences hardwarewise. i think...
[Touch HD Windows Mobile ROM Development] SkyBeat:
Hi,

where we can found any informations about the state of the project? Have you a link to a project page or so?

Thanks,

Nico
[Touch HD Windows Mobile ROM Development] Archoz:
Yeah what's up with the blog, tux?
[Touch HD Windows Mobile ROM Development] Lilith_v2:
It's down.
[Touch HD Windows Mobile ROM Development] brumbrum:
According to this post: http://xdaforums.com/showthread.php?p=3845573#post3845573 it may be possible to JTAG the device to force-flash the chip's on the device to be compatible with other phones.

The hardware is the same as I understand when I read, but the firmware on the chip's in the device is not the same.

Viperbjk have done some more research into this. Would be nice if he could explain this further and telling us if it is possible.
[Touch HD Windows Mobile ROM Development] ASK768:
I contacted Viperbjk in the early stages of this project and his response to my questions relating to progress was:

"Yep, we are updating QMAT regulary. Right now we're doing less jtagging however in order to support other phones we did before as well."

QMAT is the tool/app he is developing.
[Touch HD Windows Mobile ROM Development] itchy8me:
tux,

Do you have any legal documentation/notes on your hands. As in ones you have made yourself while developing. If so can you please PM me some reading material, i'm itching to start helping on the dev.
[Touch HD Windows Mobile ROM Development] zammy:
the kernel linux 2.6.28 :D
[Touch HD Windows Mobile ROM Development] tids2k:
thanks a lot itchy me ;) your support and help will enhance the future development of this project. best of luck to you too. i hope you can ask your friend developers for the vogue dev platform to help with the drivers in this project as well. once again ... thanks for putting a step forward into this project.
[Touch HD Windows Mobile ROM Development] tids2k:
what about it ?:confused:
[Touch HD Windows Mobile ROM Development] Khmer123:
wow even my wife HTC Touch/Elf (GSM) about to have Android too. maybe Admin in sourceforge.net can help you out tux!

http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=3&t=7

http://www.youtube.com/watch?v=1CdZnclLi2A
[Touch HD Windows Mobile ROM Development] tids2k:
well i'm jealous and disappointed to see that other average htc handheld are able to run and port android on them, sighh !! when will we see android on blackstone ... it makes me worry and cry :eek::(:mad::confused:
[Touch HD Windows Mobile ROM Development] audscott:
I picked up a My Touch for my wife last week....amazingly smooth and fast: Alas, I am still a sucker for WinMo. :D
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
MOD EDIT

Please leave all childish behaviour in the playground. If people feel that progress on getting the Android onto the HD is slow, can I ask you one thing. What have YOU done about it apart from b**ching?
[Touch HD Windows Mobile ROM Development] tmzt:
I believe tuxhero's approach is to have all features working to the approximate level of dzo's vogue port before releasingtest image, is this correct?
[Touch HD Windows Mobile ROM Development] tids2k:
hehehehehe .... i have always supported this project mite l( ..

just that the shiny android os on other devices ,... gives us a tight itch.
[Touch HD Windows Mobile ROM Development] tmzt:
2.6.29

tuxhero:

hello again. If you are still interested we would love to know how your 2.6.29 port is going and what you meant by minor modifications to clock.c instead of clock-wince.c

I'm not sure if your 2.6.29 work (just that port, not your new code) is in a public git tree or not.

We are moving forward on 2.6.29 and with cr2 having returned from his long trip we may be able to progress on the rpcrouter and qdsp5 audio problems.

I would suggest doing initial userspace work in something other than android though, it adds far more complexity than is needed.

There is progress on wifi, at least with a new kernel on the G1 with the wl1251 sdio driver. This should translate well onto other devices with acx chipset. What are the current issues with BLAK mmc?

If you have any questions, the channel is still there ;-)
[Touch HD Windows Mobile ROM Development] patp:
Hi tmzt,

Am I right in thinking that if sound (mic, earphone at least) gets working, then the device becomes usable as a handset for day to day use? I think GSM was working (at least I was able to make a landline ring by dialing a number!), and if ppl can make and receive calls and sms, it's a phone. At that point it starts to be worth people getting involved in Android ports like the lively Vogue community; this will likely get much more interest in solving the remaining hardware probs.
[Touch HD Windows Mobile ROM Development] simranjits:
it is even more childish to pretend that he can port it , when in reality he isn't no where near yet. He is just getting peoples hopes up.
[Touch HD Windows Mobile ROM Development] tuxhero:
At least i am getting peoples hopes up and keeping this project alive. What are you doing?
[Touch HD Windows Mobile ROM Development] tuxhero:
It's nice to see cr2 back. It's been a very busy week for me tmzt i will come to irc this weekend there we will talk. I already switch blackstone code to G1 code currectly i am working on 2.6.29 donut code. SD Card is trying to set SD Bus clock with vreg set level and it is not working on blackstone.

I am just trying to make core platform code (IRQ,GPIO,Clock) stable and full featured.
[Touch HD Windows Mobile ROM Development] nizzon:
Yes you must be right since we can make calls and send SMS with the current Android found in wiki.
[Touch HD Windows Mobile ROM Development] tmzt:
Hi patp, you are essentially correct. Unfortunately vogue is not a good analog to blak because it's radio firmware is much simpler. I missed the second part of tuxhero's reply earlier, but seems to be saying that the lowest level components are not funcyioning on te blak. If this is the case that would need to be corrected before things like the audio drivers can be worked on. I did believe the linuxtogo git tree had at least some of that functioning so I'm not quite sure what issue tuxhero is having.

The audio driver should be very similar to the one for the Diamond, Touch Pros, Xperia, etc., and we should wo k together when Blak reaches that point.

One other thing. The images on the wiki you keep referring to might be months old and don't neccessarily reflect n the state of the http://git.linuxtogo.org/ tree.

If you want help building from source, and have a Linux-based computer, please visit irc.freenode.org, channel #htc-linux
[Touch HD Windows Mobile ROM Development] brumbrum:
But the version on the wiki is not stable. It freeze after minutes of usage and it drains battery as ****. It may be usable if you plug the device into a nuclear plant for electric power and if you find ways to fix the total-freeze-issues.
[Touch HD Windows Mobile ROM Development] nizzon:
What im saying is that if the basic phone-functions (making a calls, sending SMS) allready are working on the old image, then if they get hardware working (speaker, mic) on the new image it shouldnt take them long to get it working all together, stable or not.
[Touch HD Windows Mobile ROM Development] tuxhero:
cr2 from irc is working on speaker, mic.
[Touch HD Windows Mobile ROM Development] kawino:
Guys, if there is already a system ANDROID on HTC Blackstone? Someone help?
[Touch HD Windows Mobile ROM Development] kosworld:
Tux salvation is available in how long?
[Touch HD Windows Mobile ROM Development] kosworld:
t'aurait need money for her or not because I can give if you must
[Touch HD Windows Mobile ROM Development] 1337_V1k1n6:
I really hope there is some real development goling on and that the sceptics are plain wrong.. Having Sense on our blackstone would be awsome.. It looks way better than Hero, and with the same OS it would be unbeatable..

keep up the good work guys
[Touch HD Windows Mobile ROM Development] Ethania:
And way shouldnt there be any "real" development going on? Are there really any resons for concern?
[Touch HD Windows Mobile ROM Development] nizzon:
Dont drag this up again.
[Touch HD Windows Mobile ROM Development] imtiyazee:
Hope its going on well with manual clock values, if u find some free time kindly update us.:)
[Touch HD Windows Mobile ROM Development] EmilianM:
Guys what is the status ?I was looking on wiki and it seems that the advance for the last 6 month is visible for the large public :).

Here on XDA FVorums, thanks to darkstar62, they succeeded to install Android on 5 or 6 other mobiles with OMAP 200mhz....you can see the videos here :

https://sourceforge.net/apps/trac/wing-linux/wiki/Videos?version=4

the project page is here Wing Linux :https://sourceforge.net/apps/trac/wing-linux/wiki

This is pretty functional on this phones, the only big problem is the voice. I know that the hardware is completely different but ,I can only imagine how this should run on HTC HD with that screen and with that processor.
[Touch HD Windows Mobile ROM Development] sudo_x60s:
Sorry OT but this is T H E device:

http://www.​youtube.com/​watch?v=tKr8​tscoOKI
[Touch HD Windows Mobile ROM Development] nizzon:
sudo_x60s: url is wrong :confused:
[Touch HD Windows Mobile ROM Development] BlastOS:
http://www.youtube.com/watch?v=tKr8tscoOKI
[Touch HD Windows Mobile ROM Development] sudo_x60s:
Sorry, BlastOS posted working URL. Thank You!
[Touch HD Windows Mobile ROM Development] sevensheaven:
nothing to do with blackstone or android..so stay on topic please

regards stef
[Touch HD Windows Mobile ROM Development] NeoS:
Anyone tried to boot the X1's Android port?

On my HD the boot procedure hangs on msmfb_probe() installing 480x800 panel.

I've got Android running on an old Artemis thanks to the Wings project. Figured it would be cool to have it running on HD also.
[Touch HD Windows Mobile ROM Development] kubeb:
kaiser has Android!!!

why does kaiser users succeeded in making android work on their device but we can't?

http://xdaforums.com/showthread.php?t=547264

http://www.youtube.com/watch?v=8xVYcFZiYgE
[Touch HD Windows Mobile ROM Development] ASK768:
Its an older device, so chances are that more people will have one, or by now, have one lying around the house that they dont mind bricking. With our blackstone, many people opted for a diamond or touch pro and many blackstone users have even upgraded to a touch pro 2 or diamond 2. So, if you think about it, far less people have a blackstone. Lets not forget how expensive the blackstone is; people arent going to want to risk their investment so much.

Also, im sure there may be some hardware differences which would also contribute.
[Touch HD Windows Mobile ROM Development] sny2ksa:
Very Good

:D Nice job:D
[Touch HD Windows Mobile ROM Development] imtiyazee:
I hope at-least this time when Tux respond there will be a +ve note to read, rather an answer which everyone is not waiting for. All the best..:D
[Touch HD Windows Mobile ROM Development] :
Thats not the case here, as the htc msm kernel apply's to all msm7201a devices, e.g xperia,tp,diamond,blackstone etc.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
rafyvitto: not quite.

The CPU is the same, but a lot of the hardware has minute to major differences that do stuff from panicking the kernel to just giving no or garbled screen.

The screen, which is a major factor to getting things to work, is completely different then any other device. We do have the complete documents for it and in the previous iteration of a Blackstone on HD project it was working fast and seemingly correct. But the implementation was still a complete hackjob which had as much chance of busting the screen then working correctly.

The touch filter wasn't 100% but nearly there.

There's more ram, more rom, apparently a different SD interface (which is annoyingly slow compared to other devices and has problems with many SD cards we tested), other then power and volume, there are NO hardware buttons. The bottom row buttons are software buttons.

Android did boot on the previous android project with certain radio's and over certain roms and did have nice screen and correct touch in certain situations, but as you can see, you had to have an overlapping luck of having the exact and correct mix of the right radio, rom, SD and other components to get anything working.

So, back to what you said, not quite and not even close ...
[Touch HD Windows Mobile ROM Development] dzo:
Kaiser has a working kernel because I ported it (though vogue is more mature with all the hardware working to some extent).

It's actually harder to port the kernel to 7x00 based devices rather than 7201a because the interrupt controller is very different as well as the version of AMSS and lots of other things. It's just that your device is relatively new and still expensive.

tuxhero: the 7201a clocks are mostly identical to the 7500 clocks so you don't need to do anything, just use the clock driver from the vogue tree.

I'm planning to get a 7201a device soon (probably a diamond because they're cheap) so I'll be able to contribute.
[Touch HD Windows Mobile ROM Development] andrewpmoore:
That's great news, it'd be great to have you on board.
[Touch HD Windows Mobile ROM Development] dwaradzyn:
Blackstone is much better than diamond. Maybe XDA could donate one to you - what do you guys think? I think he deserves a nicer device for his hard work on porting Linux to HTC. I also think that this is the most trustworthy and fastest way to get Android working on blackstone.
[Touch HD Windows Mobile ROM Development] imtiyazee:
I totally agree with you.
[Touch HD Windows Mobile ROM Development] Celeborn_81:
I'd be willing to make a small donation, together we should be able to finance a Blackstone quite easily.
[Touch HD Windows Mobile ROM Development] superseagull:
plus 1

same here :rolleyes: