So, what do u know about wm 7? share what u've read somewhere .
I've read which Microsoft is trying to realease its own mob they bought danger as a sample...
Also, I found some pics but I've no idea if is wm7 or what!!!...
Next unlocking system will be move your phone in the correct way . Crazy !.
So, here are the pics don't get to excited because nothing is confirmed .
Tell us what do u know
Full images and source HERE
WM7 Hardware Requirements
WM7 Chassis 1 Specification
Core requirements:
Processor: ARM v6+, L2 Cache, VFP, Open GL ES 2.0 graphics HW (QCOM 8k, Nvidia AP15/16* and TI 3430 all meet spec)
Memory: 256MB+ DRAM, 1G+ Flash (at least 512MB fast flash – 5MB/s unbuffered read @4K block size)
Display: WVGA (800×480) or FWVGA (854×480) 3.5” or greater diagonal
Touch: Multi-touch required
Battery: Sufficient to meet Days of Use LTK requirements.
Controls: Start, Back, Send and End are required (soft controls allowed as long as they are always present).
Peripherals:
Camera: 3MP+, flash optional, 2nd camera optional (VGA resolution sufficient)
GPS: aGPS required
Sensors required: Light Sensor, Compass (3 axis, 5 degrees, 100 Hz sample rate), Accelerometer (3 axis, 2mg resolution, 100 Hz sample rate)
USB: High speed required, 20 MB/s transfer rate.
BlueTooth: BT2.1 required, must run MSFT BT stack, CSR BlueCore6 or later recommended.
Wi-Fi: 802.11B/G required, must run MSFT Native Wi-Fi stack, Atheros 6002 or Broadcomm 4325 recommended.
Connectors: Micro USB and 3.5mm Audio required.
Options:
FM tuner: If tuner HW is present it will be detected and supported by the Media application.
Haptics
SD Card (Micro SD recommended)
DPAD, qwerty or 12/20 key keyboards all optional
Apparently
Looks like X1 is disqualified from WM7 based on these specs. I guess when WM7 hits, it'll be time for a new phone anyways...
WhyBe said:
Looks like X1 is disqualified from WM7 based on these specs. I guess when WM7 hits, it'll be time for a new phone anyways...
Click to expand...
Click to collapse
Why, X1 got most of the specs? But I think you're right, when wm 7 hits the public we all will have a phone like that lol
definitely x1 is out this
comeradealexi said:
Click to expand...
Click to collapse
Don't think that roadmap is up to date since wm 6.5 final also haven't been released yet.
The most important of this "roadmap" is the "All dates are subject to change".
Is this Office for mobiles, down/right corner??
Such small icons?
doministry said:
Is this Office for mobiles, down/right corner??
Such small icons?
Click to expand...
Click to collapse
Looks like the picture is photoshopped. Doesn't look genuine.
Related
FYI, I recently received an e-mail from some guy at O2 Data Support.
Hi Andy,
Thank you for your email,
As regards your queries below -
The HTC Universal - we are branding the device as the 'O2 XDA Exec', and we will be launching at some point in the near future, unfortunately we don't have any confirmed date for this as yet. I have also attached a file with some FAQ's regarding the device which I hope will help quench some of your gadgetry needs! (I myself also love gadgets).
As regards the XDA 2s, we are aware of issues with the device at present, and advise customers to hard reset the device and go into Corporate mode (with a pin number of 0506). Within Corporate mode, the clock is present in the top right corner, and the O2 Active software does not install. We will be releasing a new ROM for the device, but again, we can't advise of any release date as we don't know any as yet, and also cannot confirm what software will be in the new release. I assume with new releases for the XDA 2s, that there 'should' be WMP10, but again, we can't confirm or deny that as yet.
As regards WM2005 for the other XDA series, this question is answered in the attached file.
If you have any further queries, do not hesitate to contact us again.
Regards,
Paul
O2 Data Support UK
Click to expand...
Click to collapse
And it also seems that a few people are confusing the spec. So this is the attached file he was talking about in his e-mail. It's an o2 XDA Exec FAQ:
Xda Exec & Windows Mobile 5.0 - FAQ's
Q. When will O2 launch devices running Windows Mobile 5.0?
A. The Xda Exec (HTC Universal) will be the first Windows Mobile 5.0 device although a launch date is yet to be confirmed.
Q. Will any of the current Xda range receive a ROM upgrade to Windows Mobile 5.0 operating system?
A. There is currently no planned upgrade for O2 Xda II, IIs, IIi devices to Windows Mobile 5.0 and it is highly unlikely this will happen.
Q. What is the spec of the Xda Exec?
A. The provisional spec (some of which is subject to change) is as follows;
Windows Mobile 5.0 (which includes 'persistent memory')
Intel XScale PXA272 520MHz processor
ROM 128MB (used as storage)
Ram 64MB (used for running apps only)
3.6” 640x480 65k transflective colour backlit LCD
up to 4/2/20/200 GSM Talk/3G Talk/PDA/Standby time
GSM Tri-band (900/1800/1900), UMTS Single-band (2100)
GPRS class 10, UMTS 64/384
Bluetooth 1.2, Infrared and mini-USB connector
Wireless LAN 802.11b
SD/MMC/SDIO slot
3.5mm Audio Connector
Stereo Speakers
Integrated camera (resolution 1280 x 960) with LED flash and 2nd CIF camera for 3G video calls
Integrated antenna
15 buttons (Answer, hangup, PTT, OK, Start, Camera, Power, VoiceRecord, 5-way nav
56-key QWERTY keyboard with light sensor to auto-adjust backlight
Removable battery (1620mah)
Weight: 285 grams
Minimum Activesync version required 4.0
PC operating systems supported Windows 2000/XP (no support for Windows 95, 98, ME, NT)
Supports Activesync synchronisation of video/audio files in conjunction with Windows Media Player 10
Screen: 10640 x 480 VGA resolution
Enhanced O2 Active interface
Power Save software
Three setup modes - Full O2 Active, Intermediate and Corporate
Dimensions are 81mm x 127.7mm x25mm
Q. Why does Xda II have more RAM memory than Xda Exec?
A. You shouldn't compare RAM across the different operating systems as they use RAM very differently. The difference is as follows;
Windows Mobile 5.0 devices use RAM for running programs only.
Windows Mobile 2002/2003 devices split RAM memory in half - between running programs and user data storage (emails, contacts, pictures, videos, Word documents etc.)
So Xda II and Xda Exec use roughly the same amount of RAM for running programs. However Xda Exec stores user data in the Flash ROM memory, as part of the "persistant storage" feature of Windows Mobile 5.0.
It should also be remembered that more RAM impacts battery consumption, so more RAM would require a larger battery.
Click to expand...
Click to collapse
Hope that's enlightened a few people.
Cheers,
Andy
I'm a bit worried about that screen size, it's going to be a problem getting it in your pocket!
lol yeah looks like he might a slight typo
unless they have a new technology that makes pixels super tiny
Andy
it is supposed to appear as:
Screen: 10" 640 x 480 VGA resolution
i guess...
ahmmmm...
let's say:
Screen: 10cm 640 x 480 VGA resolution
anyway, thanks for posting that o2 letter. that really enlightens at least me.
Nice, the first ever PPC with a WideWideWide scren
NICE NICE
the 64mb ram makes me think... IMO i find it little to use... any way to upgrade it ? to at least someth i can live with (128)
The more RAM you have, the less time the battery will last. Manufacturers are starting to use ROM going forwards to enable longer battery life.
but there are bigger batt avail...maybe in time to come for the universal.
rick83 said:
the 64mb ram makes me think... IMO i find it little to use... any way to upgrade it ? to at least someth i can live with (128)
Click to expand...
Click to collapse
In fact u can!!...there's room for 2 additional slots,so u can have ur 128MB REAL RAMS....read this http://forum.xda-developers.com/viewtopic.php?t=26375 ...
But the question is:do u need 128 MB RAM....remember that u don't have ext ROM nor storage memory anymore,wich used to share with u ur old RAMS...now u have 64MB...and they are pure RAMs.....
greetings...
RAGO :lol:
well since the ram is only for running applications and not storage
then it should not matter
if it's 64 over 128 with our devices now nobody use 128MB as application memory anyway since we use some for storage
and applications use the memory they were made to use
having more should not make them speed up
the only thing more pure application memory does it that applications people have closed as in minimized live for longer before they are terminated
as in faster multitasking of running programs
how do i upgrade the ram. Is it like those SD card type (just slot in) or do i need to soulder ?
how do i upgrade the ram. Is it like those SD card type (just slot in) or do i need to soulder ?
Click to expand...
Click to collapse
as far as i can tell from the pictures then you need a soulder
and a smd soulder at that
not something for a person not exp'd with such things
maybe some company will offer the upgrade
not sure if it would require a special rom to address the extre memory though
but thats just application running ram you can still get a sd card for storage if you need more then the 128 mb storage it comes with
(that is unless the 128 is also for the rom itself)
I think that we should put together a "WISH LIST" for the XDA3.
I'll go first
4GIG Hard Disk - Like the Palm 1
5MP Camera - with a decent lens and Optical Zoom
Proper USB port allowing for a loud speaker like on the samsung phones
The Case shouldn't scratch so easily
Proper Head Phone Jack (blody annoying with the 2,5" rubbish)
Faster WIFI 54 (if not 108)
I can think of loads more - but I'll throw it open right now!
.
A tiny screen on the front cover to tell who is calling without needing to open the flip and if possible basic input buttons to dial and write short SMS without needing to open the flip
srmz said:
A tiny screen on the front cover to tell who is calling without needing to open the flip and if possible basic input buttons to dial and write short SMS without needing to open the flip
Click to expand...
Click to collapse
I think I've writtne in the wrong String My XDAIIi doesn't have a Flip of any Description
Hi
I was wondering if I can run q3a on my SPV M3100.
After I try to launch it, I get a message "Insufficient memory to start Q3CE. Try freeing up more program or storage memory."
Program or storage? Does this is true only with devices with shared memory? Or maybe this game can use also my storage memory on hermes, which doesn't share memory?
q3a needs 96MB, which is possible on Hermes (free storage + program memory)
I know that this game isn't playable on any device (and Hermes isn't so fast) but it would be nice to see it on my ppc.
If anyone managed to play this game on Hermes, please post here. I don't know if I want to change my ROM to super-duper-lite version without even MS Office just to see q3a working... or not.
The men in white coats are coming to get you...
Run!
Joking aside, I'm assuming you actually mean the quake game - not arena...that would be pushing it a little
Assuming that then, AFAIK, quake was written specifically for the Dell Axim X5x (whichever one had the 3D graphics card in it) so presumably, that is why it's failing on your hermes - it's not memory thats missing, just a graphics card...
Smiffy.
http://quake-3-arena-ce.softonic.com/pocketpc
I mean Quake 3 Arena :]
This is from README:
Quake 3 Arena CE Installation Guide
Version 1.1b
-------------------------------------
Requirements:
* Pocket PC 2003 compatible handheld (ARM/XScale CPU)
* Intel 2700g if you want hardware acceleration.
* 124MB of storage space (Fits on a 128 MB SD Card )
* 40MB of available storage+program memory (64 MB devices running PPC2003, 96MB running WM5)
* An installed copy of Quake 3 Arena on your PC, complete with all the upgrade patches
Installation:
1. Ensure you have a copy of Quake 3 Arena installed on your PC. You're going to need the
artwork/content from the game because it is not redistributable.
2. Run the pakconvert tool like this to build the pk3 file for your handheld:
cd pakconvert
bash ./pakconvert.sh c:/q3a (replacing path with wherever your Quake 3 Arena installation is)
3. Copy everything over to your handheld. You will need 124 MB of space
DELL AXIM AND ACCELERATED HANDHELDS:
q3ce.exe
gx.dll
baseq3\q3config.cfg
baseq3\pak0.pk3
baseq3\cgamearm.dll
baseq3\qagamearm.dll
baseq3\uiarm.dll
UNACCELERATED HANDHELDS:
q3ce.exe
gx.dll
libgles_cm.dll
baseq3\q3config.cfg
baseq3\pak0.pk3
baseq3\cgamearm.dll
baseq3\qagamearm.dll
baseq3\uiarm.dll
The other files are unused by the actual game.
4. You should not need to adjust your "program versus storage" memory, though on some devices with greater than 64MB
of memory, adjusting to have more program memory may improve performance.
Notes:
1. Network support is obviously limited. Your Pocket PC likely doesn't have a very fast internet connection, so
your ping times are going to be crap. Hell, it might not even work. Maybe in the next release...
2. You may have a hard time entering text, or a CD key or whatever, unless you have an external keyboard. Avoid
menus where you have to type stuff in. Maybe virtual keyboard in next release...
3. I had to eliminate support for the virtual machine in the codebase. This means that many 'mods' will not work for
you, as the UI, Game, and CGame modules are all hard-coded into the program. If someone wants to find a way to get
that working on the ARM cpu in a fast fashion (ha! and steal resources from our meager graphics?!) feel free
to do so.
4. Memory now autopartitions itself, so you don't need to worry about reconfiguring stuff. You still need a lot of
memory, but requirements have been reduced to work with 64MB PPC2003 devices.
5. Audio has been converted to MP3 to save space
6. Fonts and graphics have been cleaned up by using better resizing mechanism.
I think that's all.
11/15/05
Christien Rioux
[email protected]
Click to expand...
Click to collapse
mrbabcia said:
Hi
q3a needs 96MB, which is possible on Hermes (free storage + program memory)
Click to expand...
Click to collapse
Really?
You can have at the best at about 90 MB (30 MB program/60 MB storage).
I thing I saw a screenshot yesterday with so much free memory but I was tired. ;]
*** Black Satin Light (differences from Medium) ***
Free Storage ROM: 64MB
RAM on cold boot: 31MB
Click to expand...
Click to collapse
well, 1 more MB ;]
Or maybe we could decrease limit to 95MB xD.
What about WM6? It's 96MB on WM5 and it seems that with newer Windows Mobile we need more free memory... but WM6 is faster, right? Maybe also memory requirements in q3a would be lower?
seeing the amount of frames per second in the screenshots i'd say hardly playable
Quake 1 2 & 3...
Its says in Spanish that its a test version and they have not seen more than 5fps they say it is insufficient speed to enjoy the game.
I remember all of the previous versions of this port were slow and unplayable it seems even less likely our Hermes can run quake 3 with no hardware acceleration. Full Stop.
It just isn’t going anywhere, the creators of the quake 1 & 2 ports just gave up didn’t they?
There must be some tweaking what can be done for Q3.
Hi,
I have Q3 on my Hermes and it runs slowly around 5fps. Yet i tried it on about ten roms, some wouldn't load it up fully. The rom i use now loads it up at 5fps. Also my rom doesn't have 96mb of program/ram free about half and it loads up the same yet they say you needed 96mb free. The rom i use now loads and plays it best. I will keep testing though to see if i can tweak it. Not much to edit in the config txt. But sometimes one edit can be enough to give 50% more.
I know more cpu and gpu power would do the trick. Pity i cannot overclock the cpu anymore than 500 mhz. Some games though do look and perform well.
FRAGEYE said:
Hi,
I have Q3 on my Hermes and it runs slowly around 5fps. Yet i tried it on about ten roms, some wouldn't load it up fully. The rom i use now loads it up at 5fps. Also my rom doesn't have 96mb of program/ram free about half and it loads up the same yet they say you needed 96mb free. The rom i use now loads and plays it best. I will keep testing though to see if i can tweak it. Not much to edit in the config txt. But sometimes one edit can be enough to give 50% more.
I know more cpu and gpu power would do the trick. Pity i cannot overclock the cpu anymore than 500 mhz. Some games though do look and perform well.
Click to expand...
Click to collapse
Wow, so may old threads popping up!
The hermes doesn't have excelerated video, and your not really overclocking to 500mhz, the hermes cpu isn't scalable.
Not too sure q3a will ever run on the hermes.
I have got it to overclock to 500 mhz when load is over 70 %, i notice the difference in speed and response of taps and loading, trying duke nukem 3d atm and it runs smooth as anything ! Classic shooter, runs average 25-30 fps.
It might be old this hermes but still handy bit of hardware.
I have run Q3 but 5fps is no good. Sometimes little tweaks tho can give extra speed.
Official ppc games run very smooth, so i think if effort is put into a port it can turn out really good !
Wonder what halo type game microsoft are doing for WM ? Some think it will be a multiplayer over net too.
I wrote some Managed Direct3D Mobile code, using fixed point arithmetic. It runs slow as a dog and its performance relative to the floating point version of the code shows little improvement.
This is on a Kaiser phone. I know that there are issues with graphics on that thing. I am only trying to use the software renderer, but the speed of my app is so slow that I wonder if it's in my implementation. It is a cube with textured faces, spinning as as fast as it can, and I can only achieve 7 seconds per frame (yes... seconds per frame. Obviously my goal is something in the FPS range!).
Would anyone with experience in writing D3DM code care to give me a hand by looking at my code? I'm at kramer (underscore inserted) ae (at) hotmail (dot) com.
Thanks,
Brian
Sorry to say the Kaiser only has reference drivers for d3dm, all software driven. Thats why its a dog.
and it also dont help that ms stoped all development of Managed Directx along time agoe and most people who wanna do 3d from .net these days use opengl
also on a as weak platform as arm compared to pc
.net being much much relatively slow on arm compared to on x86
doing 3d in a not truely native language as c++ will never give much speed
less so when it comes to graphics
These comments aren't helping. I understand that my environment is not up to industry standards in terms of performance (15-60 fps, for example). But rendering a cube in Direct3D should not be as bad as one frame every 10 seconds. I'm in search of someone who knows the correct baseline performance expectation for my scenario and can help bring the perf of my simple 3D application in line with what is really expected. Alternatively, there may be anecotal information that says my application is actually performing as fast as expected. I don't know that.
The attached archive contains a native and a managed D3D example showing a rotating textured cylinder (from the WM6 SDK). Both run interactive on my HTC Touch (Elf).
Hi everyone,
I have a small technical problem to solve and hopefully someone knows an answer for it. Someone gave me a HTC Diamond 2 (very nice toy I think). I don’t know which hardware is exactly inside the phone but I assume it’s an ATI ImageOn 2300 which fully supports OpenGL ES 1.0 + Extension Pack (that’s what GL_EXTENSION is saying). And all of these extensions are doing fine. As everyone knows HTC is not providing a D3D driver for their phones and all other drivers I have seen are just a wrapper around OpenGL ES. So using D3D is currently not an option.
I have to write an application which requires some render-to-texture functionality in realtime and here my problems are starting to grow.
[1] glCopyTexImage2D:
I recognized that glCopyTexImage2D() is very slow. My framerate is dropping dramatically from >100 frames down to ~20 frames. Somehow this is done in software by the driver and not hardware- accelerated. glCopyTexSubImage2D() is even more slow (down to ~10 frames per second), but both functions are working. I tried to move it into a different thread, but the driver is not supporting shared contexts. Also it’s not supporting two bound contexts at the same time with two different windows and threads. So this can’t be improved or I’m doing something wrong.
[2]PBuffers:
PBuffer are working fine. But PBuffers which can be bound to a texture are not supported by OpenGL ES 1.0. And that’s what happens also on this ATI card.
[3]GL_OES_framebuffer_object:
This was my preferred choice. But framebuffers are not officially supported by the installed OpenGL driver. But the libgles_cm.dll on the HTC is exporting these functions so I tried them and recognized that they are not working correctly. Somehow the vertex pipeline is allowing only triangles in the center of the viewport. All others will be discarded. When I turn it off it renders correct. Using glDrawTexiOES() will be ignored while using framebuffers. I assume that either the current implementation of the framebuffers is just waste of some development guys or the functionality is locked in some way.
[4]D3D:
Normally D3DM is supporting to switch between different rendertargets. But we are all know the D3D problem. I tested some other D3D drivers but they are not usable. Also I can’t imagine how render-to-texture will be implemented in these drivers while it’s not working in OpenGL.
I’m wondering what TouchFlow3D is using internally, whether they are using render-to-texture or not. The only thing I know is that they are using OpenGL ES and some extensions. But Manila.exe is querying the functions of libgles_cm.dll during runtime. So I have to write a few proxy dlls first and need to hook into the system to track what they are doing. And I don’t want to spend time on this.
Does someone knows an alternative to do some render-to-texture on the ATI or knows some secrets of the libgles_cm.dll which I don’t know? There are a lot of private functions inside but can’t find some documentation about it. Also ATI and Qualcomm are not very helpful to me.
Thanks.
Maybe, glReadPixels and then glTexSubImage2D (what probably glCopyTexImage2D is doing)?
(I know that this goes two times over the graphics bus, but you never know...)
What kind of scene (number of triangles, lights, textures) are you rendering with > 100fps?
glReadPixels() + glTexImage2D() is even more slow than glCopyTexImage2D...
Also this can't be parallized. I thought using AHI2DATI.dll instead to do the same thing, but I don't know how to get a surface handle from a OpenGL texture id.
>>>What kind of scene?
A very simple scene yet. Only a few depth sorted + material sorted objects (via VBO) with some textures (backed lighting) on it. Textures are compressed. Currently no lighting, no skinning or other things. While the render thread is waiting for glFinish() to return, a second thread prepares the next frame. Also the rendering thread is not redrawing the entire viewport each time.
The OpenGL texture id is the handle. There's nothing more you can do with it. PBuffers or framebuffer objects are the only way I know for doing performant render to texture in OpenGL.
No...I mean the surface handle of the AHI2DATI library. Here you have access to the raw data of the surface. Somehow the libgles_cm.dll uses these surfaces for it own buffers and/or textures or not?!
But this is not really useful unless someone tells us whats going on inside libgles_cm.dll.
See:http://greengalaxy.wordpress.com/2009/04/18/ati-direct-access-to-hardware/
Hi jeansmsixer, I don't think there is no efficient way to do it. Have you tried eglCopyBuffers?
Aren't all textures stored in system memory? - they surely have to be because the device reports no available video mem.
Even if you get a pointer to the color buffer, it's impossible to wrap the memory in a HBITMAP to select onto a HDC and use GDI fonts for instance. (which is what I need to do).
If you do write the proxy dll like you were suggesting, can you please let me know what TF3D does for fonts? Are they textures or have they somehow mixed 3D with GDI?
Hi jeansmsixer, something else you could try is what is described here:
http://brewforums.qualcomm.com/showthread.php?t=10668
Looking on glbenchmark.com it looks like HTC devices support the extension. You should be able to get a pointer directly to the color buffer (which I presume is in normal system memory) so you could copy off pixels fairly efficiently with your own memcpy(). However, you will need to eglWaitGL() etc to ensure 3d stuff is complete before attempting to access it.
I love the irony of the only helpful information for WM opengl being found on a brew site for symbian. If WM7 is as terrible as the current mess, then I'm moving to iPhone.
Maybe HTC is reading this forum, so I start a thread for your changes and wishes for HD2. My changes are (wishes for HD3):
- Oled display
- display with capacitive sensors AND press sensitivity , for gloves, finger nails, stylus
- More battery power or less power consumption
- Hardware GPU support for ALL applications !!!
- TV - Out with adapter
- Hardware Buttons in better quality AND going inside (like iphone , Grr) , so you don´t press always any button if you just take the phone in your hand
- Maybe better CPU power or dualcore. I don´t need it right now, but 1 year is a long time and I want to avoid that htc use the same CPU for another 5 years as in the past
- Camera with 720 p video and better lenses.
- stronger WiFi connections
And my manila wishes are:
- manila style Task manger / switcher
- manila style task management tool instead of MS office old thing.
- manila style notes
- manila style counter and stopwatch, like it is in Android right now.
- manila style Email client !!
- better album application, with easy folders access.
- much better mp3 player ! : I want rate my music (and sync, of course), intelligent playlists for my own ( 4 stars, for example), I want to search for music with keyboard and switch fast though it with letters on the right side to jump to S for example. The last two wishes are already there, in the contact manager !! I want the same for music and video ! Better caching of thumbnails, there should be no reload every time I scroll. (same as contacts, there IS no reload !! right now )
- video player with folders and DETAILED view: I want an image AND the name of the movie ! Most time you can´t see what file it is, because it is just a small image . Rateing and playlists, too. And of course keyboard search and Jump to letter, just the same interface for contacts, music, videos, Footprints, weather cities with same slight modifications for each area.
- manila style google maps application with smooth !! multitouch.
- Opera 10 with multitouch, of course.
And : SAVE AND SNYC with ALL Manila and System settings with my desktop or in a file at least !!!!!
Imagine, you do a Rom Update or Hard Reset, just load this settings file and ALL your favorites and "make it mine" settings are back, without hours of tweaking again, your email is set up again, you weathers, your ringtone, ALL of it ! What a dream.......
edit - deleted until HansZimmer version 3 is released with a better humour chip.
I don´t understand your message. Do you think HTC is not going further anymore ? I don´t think so and just want to tell what for me as customer is important for the next device. And as far as I know htc is building the devices for us customers, so I let them know which areas are important for me. If you don´t have anything to tell about this subject, please let you opinion on another place. thank you.
How would I change HD2? I'd have it fulfill all the promises on the box and the specs: SMS without anguish, all notifications working as advertised, OS that worked out of the box and not needing constant hotfixes, a battery that doesn't have you constantly scoping out the next available wall plug...
Shall I go on?
Yes, please. This is the why I started this thread
Hardware: Nothing. I'd say it's perfect for now. No doubt it will be improved with faster processor, more memory, wimax in the future, but that's how it goes, and for its time it's just perfect.
Software: A "bigger" Sense. As in continue what has been done now, and "finish" putting that excellent layer over the old WM to hide it completely. But I'm pretty sure that's what WM7 will be. And don't forget to store a whole lot of settings in the registry so that we cant continue to tweak them to our own liking
Also, unified software and hardware specs to ensure inter-device compatibility, so we dont have software that works on some devices but not others, or miss support for hardware capabilities anymore, and a marketplace that goes with it. Also part of it as it seems.
longer battery, more than 3 alarms
that's it
imagine an HD2 with the same buttons on both side of the screen but the middle buttons are dpads/trackpads/touch screen maybe even track balls!
Audio Oblivion said:
imagine an HD2 with the same buttons on both side of the screen but the middle buttons are dpads/trackpads/touch screen maybe even track balls!
Click to expand...
Click to collapse
I'd love that! It'd be like the HP iPAQ hx4700 (4" VGA display PDA), which I LOVE. Buttons on sides and trackpad in the middle. Though I wouldn't want to make it bigger or make the screen smaller...
Stereo speakers. Such a beautiful device needs beefy sound to complete the package.
Bigger internal storage.
Sense should BE the default UI for Windows Mobile... forever. It is the most beautiful UI on any Phone OS to date!
HTC Should build their own proprietary OS just for their phones so that it is tailored to work the best in terms of speed and stability. And not some overlay on another OS. Love my HD2 tho!
The HTC HD2 is almost perfect! What changes I would like to see...hmmm...easy
1- Remove the camera protrusion in the rear.
2- TV-out
3- More internal memory
4- Video Call feature
5- Built-in VoIP SIP
What I would "want" them to do...
a- capablity to install Xeon QuadCore processor chip
b- Twin Hyper cooling fans for the processor
c- Night vision with heat/UV vision camera
d- Direct Blu-Ray quality video recording
e- Capablity to Plugin a USB external HDD
...think I've oozed out too much greed....I'll just stop now!
athar13 said:
The HTC HD2 is almost perfect! What changes I would like to see...hmmm...easy
1- Remove the camera protrusion in the rear.
2- TV-out
3- More internal memory
4- Video Call feature
5- Built-in VoIP SIP
What I would "want" them to do...
a- capablity to install Xeon QuadCore processor chip
b- Twin Hyper cooling fans for the processor
c- Night vision with heat/UV vision camera
d- Direct Blu-Ray quality video recording
e- Capablity to Plugin a USB external HDD
...think I've oozed out too much greed....I'll just stop now!
Click to expand...
Click to collapse
And don't forget this important aspect: purchase price!!
Putting the new HD3 on the market at $199 (€145, £127) would definitly be the best aspect of them all
And don't forget to give all accessories prices like: $27 for car charger, $ 25 for extended battery + cover etc..
Ah well... we'll have to keep dreaming, 'cause who knows what the 'evil' minds of HTC are up to next
Grtz,
Degake
santahtc,
yes, bring us good stereo speakers as my sharp 903 had.
and an always accessible SDhc card slot.
and a flat back, not that surfboard one!
I'd like the HD2 to have a more constructive forum on xda, where there's less trolls and flamers. Other than that, I can't fault it.
A touchscreen that enables typing would be nice. http://forum.xda-developers.com/showthread.php?t=595655
See what I mean
johncmolyneux said:
See what I mean
Click to expand...
Click to collapse
lol I was expecting just that.
There is nothing wrong in pointing the good and the bad stuff.. I happen to be one who has those problems... Shouldn't I be looking for solutions?
Cheers mate! Peace!
Is it just me, or are people wanting a quad core laptop in a smartphone...
The reason I got the HD2 was to combine my phone, PDA and media player, and it does
My pockets are so light now.
One thing, I wish I could lock the screen during music/video playback I want to see the screen and not pause the playback accidentally
USB host
Video Out
Better battery performance
IrDa to control my TV