Database Info

Windows Mobile 6.5 first Screen Shots

It's not much but better than nothing
http://www.smartphonefrance.info/commentaires.asp?ID=4812

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.smartphonefrance.info/news/wm651.jpg

I just wish we 6.1 owners can get this update but that's not going to happen.

well greats...for РРС ed. screens will be?

Dated Sep 26, why wait this long to put the screenshots up ? I wonder.....

We may not get "official" upgrades but the kind folks around here will probably find some use for it.

Looks pretty cool!
I do believe that the odds for a free upgrade to 6.5 is possible. Just like 6.0 was upgraded to 6.1, so should 6.1 be upgraded to 6.5.
The only thing that would stop it would be if the device is too slow to handle the new version. But you shouldn't hope for a free upgrade to WM 7

Not to go off-topic but it is dispointing that we might need another upgrade just to get the new mobile IE 6.0.

Most people are of the opinion that these screen shots are fakes - due to the OSX icons being used.
Also, the 6.5 will probably be required for the new IE because of the HTML rendering engine also being used for Pocket Outlook, XML reading, etc.
I *believe* 6.5 should run fine on the current generation of HTC handsets... but WM7 is designed for the "next generation" of handsets - google nVidia's Tegra chipset to learn about this.

GTRoberts said:
Most people are of the opinion that these screen shots are fakes - due to the OSX icons being used.
Click to expand...
Click to collapse
Well, that's a pretty good reason, isn't it?

GTRoberts said:
Most people are of the opinion that these screen shots are fakes - due to the OSX icons being used.
Also, the 6.5 will probably be required for the new IE because of the HTML rendering engine also being used for Pocket Outlook, XML reading, etc.
I *believe* 6.5 should run fine on the current generation of HTC handsets... but WM7 is designed for the "next generation" of handsets - google nVidia's Tegra chipset to learn about this.
Click to expand...
Click to collapse
Not only that, but the battery and signal strength indicators are transposed on the 2 shots, and it looks nothing like the preview screens of WM7 we've seen. Also, MS like screen layouts to have a logical progression, and that honeycomb layout is rather... chaotic.
It's a photoshop, and not the best on either.

Fake
Fakes for me too
And it's even more simple than that : since when Microsoft put the phone function of these devices in the first place ? Putting Microsoft Media Player in the center of the screen is more correct lol
But there is a lot of other reasons and the first one is : what a new version of Windows Mobile and the first roms are not on XDA ? Impossible, XDA is the best !

I'm making a WAD2 theme based off the second screenshot... it should be done this weekend. (or at least a beta version).

Android on HTC Leo (1GHz Snapdragon) ?

I was reading on the internet and it seems that there are a lots of versions of android that are running on Qualcomm`s 1GHz Snapdragon :
http://androidandme.com/2009/08/new...ones-coming-to-android-sooner-than-you-think/
http://www.engadget.com/2009/06/04/compal-shows-off-android-running-snapdragon-powered-smartbook/
When do you think we will see this, Android on HTC Leo ?(or why not...a similar phone from HTC but with Android ?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Too Photoshop....
I won't rule out the possibility that someone may compile an android that will run in Leo... But given that Kaiser / Diamond port is still an in-progress (as far as I know)... I see it unlikely....

C' mon that is obvious photoshop. Other links are ancient.
I d not see point in paying ms licence for wm, and releasing android on the same device. Don't think it will happen (officialy)

is GIMP..in 1 minute... ..but this was not the idea.....
I am pretty sure that they will release a similar phone with Leo( from the hardware point of view ) but with Android as main SO. Anyway I also think that somebody form XDA will port this for HARET emulator....

It may be easier soon, to get android with HTC sence running on the HTC leo,
android v1.6 supports more screen resolutions, HTC Leo has a capacitive screen, and according to WMPoweruser it appears that it may also have a digital compass, so in theory it does sound like it could be a possibility.

I'm sure there will be some kind of Android port, though I believe that 1.6 or later must be ported, since I don't think the earlier ones supported WVGA displays.
As for Sense running on the Leo, it's probably not going to happen unless HTC releases a WVGA Android device running sense. The biggest problem would have to be the fact that Sense is presently for 320x480 displays, while the Leo is 480x800. So not only would it need to be scaled up, but it would also need to be resized for WVGA from VGA.

As others said, this is a very obvious photoshop.
To get to the point, however, don't hold your breath for a port of Android to the Leo. This is a very common misconception that people need to drop, but simply because it has the same hardware does not suddenly make it simple to port something, especially something like an entire operating system.
Look at the current crop of Android ports: All current HTC phones uses the same hardware, yet a single complete Android port has not been done yet. So far as I know, it's not even close.
If you want Android, then it's best to get an Android phone or wait for a model of the Leo which has Android. To purchase a WinMo device hoping Android gets ported is a lost cause.

It seems that we will have a real 1Ghz Android phone soon...
HTC Dragon To Breath 1GHz Of Android Fire?
http://phandroid.com/2009/10/04/htc-dragon-to-breath-1ghz-of-android-fire/

it seems that we will have one ...LCD 4.3" - 1GHZ....slim design
source :http://androidmobileos.com/?p=338

and some more...
http://www.engadget.com/2010/01/26/htc-supersonic-maybe-rendered-matches-up-with-leaks-so-far/

thank youuu

Holy pointless necropost batman

[PROJECT] OpenGL Framework for games and apps

Hi there!
With a little help from you I'd like to start a little project here. The idea is to create a simple OpenGL framework, that can be used for games and apps on the HD2 (and other devices).
As you might have read, OpenGL is very difficult to get working right on the HD2. But thanks to Chainfire and his modified drivers things look a lot better now
During the past few days I have created a first version of the OpenGL framework. You can download it HERE!!!.
All it does is loading a texture and drawing a few rotating quads on the screen. The frames per second are also displayed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now that's basically everything you need to get started with simple OpenGL apps/games.
But there is one problem where YOU come in
The code is running AWFULLY slow (only 6 FPS!). Since Chainfire's modified drivers don't help here I guess the problem lies inside my code.
So I'd be very happy if we could gather all our knowledge, code samples etc. in this thread to create a fully working OpenGL sample application.
That way we'll hopefully get a lot of people to start developing and creating cool stuff for the HD2.
Anyone interested? Let's get started

What no one's interested in helping VanKurt??

So it seems. If everyone want's to cook his own soup that's fine for me
But it would have been nice to have some open source framework here to get beginners started with game development for the HD2... because what WindowsMobile really needs is some cool, good looking, finger friendly (OpenGL based) applications...
OK then, consider this topic closed!

Hi VanKurt, have you looked into the OpenTK toolkit, I think that has C# bindings for OpenGL ES (1.0 and 2.0 I think?)

Diamond Beer port
I would like to have a framework ready. I did use OpenGL on my Diamond (Diamond Beer and Diamond Cubes for example) and would like to port it to the HD2. But I would like to use OpenGL ES 2 instead of 1.x
I would not mind if it were C# or C/C++, but if there is anybody that could show a minimal project, even if it just display a triangle.
My main problem is that I do not know which DLLs I need to copy to my PC to use inside my VS projects.
I read abit about the open source OpenGL ES but I am not sure if I can just copy their include files for the HD2.
Anybody any advice on this ?
I would not mind to open source some of my projects so that others can learn from it too.

I had a quick glance at the code. You don't need to use glFlush so comment those lines out.. that should pick some speed up.
I tried a couple of quick apps with that same openglesutilities c# framework but I found it overly complicated and annoying compared to just straight calls to opengles in c++

No games for android says illusion labs :(

I'm a huge fan of illusion labs games for the iPhone and I was dissopointed to learn there were no games like TouchGrind or Sway for android, so I emailed illusion labs to see if they had any plans to port these games or something similar to android. This is the response I received:
Hello,
I'm glad you like our games. We have no plans at the moment to port those games to android at the moment. One of the reasons is that the performance is much lower on Android.
Best Regards
Marcus
Click to expand...
Click to collapse
Low performance seems like a lame excuse to me coming from an owner of a beastly Samsung Vibrant. Also, my iPhone 3G under-performs most android phones by a long shot and plays these games perfectly fine. I think performance is a poor excuse with some of the top selling android devices having GPU's capable of pushing more pixels then the iPhone, like the Galaxy S line.
I think illusion labs is seriously underestimating android and the demand for high quality android games on the platform. My proposal? Show them there is damand! Download labyrinth (illusion labs only android port) rate it and leave comments demanding they port the other games! And email illusion labs at: [email protected]
Tell them how badly android needs quality games and how perfectly capable android is at games.
Some screenshots of what we are missing out on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Low performance? What a joke. Let them fall behind then.

Its probably due to iphone being optimized for hardware draws while anything below Gingerbread isn't (we also have JIT unoptimized for Froyo). Makes sense. Also don't forget android is fragmented when it comes to hardware, theres just too many dif configs. You should email the devs back and tell them that your vibrant basicly is a iphone 4 as we have almost the same hardware (but a teeny faster gpu but its basicly a hummingbird cpu/gpu combo) also did you know Samsung makes the cpu's for Apple? we basicly have iphone 4's with a unoptimized os.

Im sure they've seen the latest Ios/Android split for themselves.
Must be nice for them to have money to burn, Leave them to it..
The only app I fancied was the Tech Deck one and even that one I couldn't see myself playing tbh..

[Q] about kernels...

I've been wondering for a while, if linux uses one kernel per processor architecture, why android uses one kernel PER DEVICE?
I mean, I could understand something like, one kernel per manufacturer (since samsung uses their partition format, htc locks it's bootloader... etc)... but ONE per device... I think I'm missing something.
Could someone enlight me?

Not an expert on that topic, but there is no such difference between a desktop and android kernel.
If we make the kernels on android alot bigger (include more driver/hardware support) and the phone manufactors start using the same standardized hardware and mechanics (so code can be reused), we could all use the same kernel.
Maybe a kernel dev can shed some more light on this if i'm wrong.

To make the kernel not so big, only the drivers for the device are build.
A phone doesn't evolve like a pc.
It make no sense to include drivers for cdrom or mouse on a phone who can't have it plugged in.

thankyou very much, then to resume: A kernel has to be small, so only the requiered drivers are bundled.

Faux123 usually posts a useful diagram of how the android underlying system works with his Kernels.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its not only about keeping the kernel size small, but efficient, its what drives the system. As the ARM proc changes, you will need to change the kernel to work with it. Take windows for example, you couldn't install windows on an ARM based pc due to the processor instruction set and how the kernel relays information. You have multiple versions of the ARM proc and different instruction sets used with them. As well as having to include drivers and other tid bits to make the system efficient. The hardware talks to the kernel which inturn talks to everything else such as the ui, as the hardware changes, the kernel usually needs to be changed. They release a kernel for each phone so that you have the kernel that meets your phone's specs.

that leads to another question, why we need ICS kernel and GB kernel?