Database Users

Toshiba e805 PDA

HELP!!
I have a Toshiba e805 PDA, can I upgrade it to Windows Mobile 5 or 6 (IT or EN)?
Memory
* Installed RAM
* 128 MB
* RAM technology
* SDRAM
* Installed ROM
* 64 MB Flash
Processor
* Processor
* Intel 400 MHzXScale PXA263
Audio
* Audio input type
* Microphone
* Audio output type
* Speaker(s)
* Voice recording capability
* Yes
Display
* Display type
* 4 in TFT active matrix
* Color support
* 16-bit (64K colors)
* Max resolution
* 480 x 640
* Max resolution (external)
* 800 x 600
Expansion / Connectivity
* Wireless connectivity
* IrDA, IEEE 802.11b
* Expansion slot(s) total (free)
* 1 SD Memory Card, 1 CompactFlash Card Type I/II

Officially, you can't and I don't know of unofficial upgrades either. However, Toshi has released a free (!) WM2003SE upgrade for it.
Also make sure you check out the Toshi 800/830 forum ( http://forum.brighthand.com/forumdisplay.php?f=52 ) at BrightHand, it's the most lively Toshi forum out there

i dont think so
Roms are device specific, so unless toshiba release or have released a rom, it wont happen. A quick google suggests they havent, and if they didnt release wm5 they definitely arent going to release wm6.
Sorry about that, but why not upgrade to a hermes or artemis or even a kaiser, theyre all great devices, and my hermes, well i couldnt do wihtout it, and the mass of roms for it, you can customise it any way you like. [If you do want one, ebay is the best place]
Sorry for the bad news
Rory
x

htcclassaction.org

Is there any way we can get the Athena on the list of phones that suffer from lack of hardware acceleration? I have e-mailed them but they replied and said there was not enough information do add the device. If someone here that has the information needed could contact them it could be a great help to get some extra speed from this phone.
Also I have sent e-mails to htc and this is the only reply i have from them.
hank you for your inquiry about the X7500.
We here at HTC definitely understand your concern about being able to use your device to its full potential. In this case regarding the video rendering capabilities of your X7500.
HTC has received similar feedback from other users and we are currently collecting examples to assist us in developing a fix. We request that you provide us with the following information about your device so that we can further investigate it. Please include:
* Your full name:
* Mobile number:
* IMEI:
* P/N:
* S/N:
* ROM Version:
* Details of issue:
Please provide a detailed account of the issue that you have experienced, which includes:
* Program used
* File size
* File format/encoding
* Resolution
* Video scaling (50%, 100%, full screen, etc.)
* Any other details that you believe to be relevant
We apologize if this issue has caused you any consternation. Please provide us with the above information at your earliest convenience.
Now when I do reply.. my question is should i let them know im using PK3 rom or just give them the wm6 updated rom version.

As far as HTC is concered, ALL our ROMS are OEM versions. Although not relevant to the video issues we are having, HTC will decline support for any device running a hacked OS.
There are good instructions (including the answer to your question) over at www.htcclassaction.org.

Only Hacked?
toyfreak said:
As far as HTC is concered, ALL our ROMS are OEM versions. Although not relevant to the video issues we are having, HTC will decline support for any device running a hacked OS.
There are good instructions (including the answer to your question) over at www.htcclassaction.org.
Click to expand...
Click to collapse
Original HTC X7500 Windows Mobile 6 have problems with video and games too,
HTC universal faster (with cooked wm6 rom ) than X7500 with original Wm6 rom.
They don't want to make a fix. ( I'm sure about that )
Windows Mobile 5 runs perfect and super fast ( like a laptop )!
Have no problems with Video ( Divx and DVD ) games runs very cool
pda goes not WARM!
But other side,
Windows Mobile 6 more functional, looks better, Useful etc...

I must make a clarification here... The issue of OS was not addressed specifically on htcclassaction.org; only video playback software used was addressed. I still think it is best to reference the original ROM only, especially since the video-related issues we are all having exist in all ROMS, hacked or OEM. There is no reason to give HTC a way out when they certainly do not deserve one.

Windows Mobile 7 [??]

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.

The Possibilities of A7

What are some possibilities that you all see with the original A7?

rombold said:
Gingerbread
New Feature Constants
The platform adds several new hardware features that developers can declare in their application manifests as being required by their applications. This lets developers control how their application is filtered, when published on Android Market.
* android.hardware.audio.low_latency — The application uses a low-latency audio pipeline on the device and is sensitive to delays or lag in sound input or output.
* android.hardware.camera.front — The application uses a front-facing camera on the device.
* android.hardware.nfc — The application uses NFC radio features in the device.
* android.hardware.sensor.barometer — The application uses the device's barometer.
* android.hardware.sensor.gyroscope — The application uses the device's gyroscope sensor.
* android.software.sip — The application uses the SIP API on the device.
* android.software.sip.voip — The application uses a SIP-based VoIP service on the device.
* android.hardware.touchscreen.multitouch.jazzhand — The application uses advanced multipoint multitouch capabilities on the device screen, for tracking five or more points fully independently.
For full information about how to declare features and use them for filtering, see the documentation for <uses-feature>.
* android.hardware.touchscreen.multitouch.jazzhand — The application uses advanced multipoint multitouch capabilities on the device screen, for tracking five or more points fully independently.
IF a7 was limited on the multitouch screen due to software wouldn't this be a relevent fix for it.
I would really like to hear Dexters thoughts on this.
Click to expand...
Click to collapse
It is a hardware limitation. Please read.

I'm very new to android OS and have been doing alot of research on the whole multi touch thing, most things lead me to believe its a software issue. Most things I have read spoke of the firmware supporting the screen must be very indepth. Maybe I am grabbing for something that isn't there but I find it hard to believe the a7 doesn't have full multi touch for any reason aside from a rush firmware the lacked the coding to do so.

rombold said:
I'm very new to android OS and have been doing alot of research on the whole multi touch thing, most things lead me to believe its a software issue. Most things I have read spoke of the firmware supporting the screen must be very indepth. Maybe I am grabbing for something that isn't there but I find it hard to believe the a7 doesn't have full multi touch for any reason aside from a rush firmware the lacked the coding to do so.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=932035
http://www.cypress.com/?id=1938
Look at screen Generation 2
Anything else?

rombold said:
I'm very new to android OS and have been doing alot of research on the whole multi touch thing, most things lead me to believe its a software issue. Most things I have read spoke of the firmware supporting the screen must be very indepth. Maybe I am grabbing for something that isn't there but I find it hard to believe the a7 doesn't have full multi touch for any reason aside from a rush firmware the lacked the coding to do so.
Click to expand...
Click to collapse
From the eLocity webite FAQ:
Q: I've heard different information about the A7's touch screen. Is it really multi-touch?
A: The eLocity A7 has a capacitive touch screen with single point zoom out and zoom in gesture technology. It is not a multi-touch screen. We are sorry for the touch screen confusion mentioned in the Amazon description and other articles which were written early on in the product development stage. Our capacitive touch screen still outperforms most if not all of the tablets on the market. We use Grade "A" LCD panels from Tier 1 suppliers in our products and our goal with the A7 is to deliver the best performance, video and image quality and other functionality (i.e. NVIDIA Tegra 2, 1080P HDMI Output) that is superior to other tablets at similar price points. We know of no other tablets in our price range that offer true multi-touch, which is fairly expensive for larger LCD screens at this time.

What are some possibilities that you all see with the original A7?

allNEW FEATURED SDK FOR DEVs

Airplay SDK is unique in providing the
facility to build your application as an
entirely OS-agnostic binary file that contains
native CPU instructions. So no compromise
on performance, yet no need to port your
application between operating systems.
Airplay SDK supports single-click
deployment to all of the following operating
systems: * iPhone OS * Android * Samsung
Bada * Symbian * Windows Mobile * BREW
* Palm/HP webOS * Maemo Additionally,
Ideaworks Labs is working closely with
leading device manufacturers to open up
new distribution opportunities for Airplay
content. Airplay SDK fixes fragmentation
within each operating system by removing
the need for developers to worry about
individual device eccentricities. Here are just
five examples of the hundreds of per-device
problems that Airplay SDK solves: *
Dynamic portrait/landscape screen
switching handled identically for all devices
* Accelerometer API implemented
identically for all devices (despite the large
number of bespoke device drivers and APIs
in the market) * Device-application
interoperability handled identically for all
devices (i.e. your application is guaranteed
to 'play nicely' with the device software, for
example to respond to incoming phone calls
and messages) * Audio handled identically
for all devices (for example, by providing
advanced software sound mixing) * Single
drawing API supports OpenGL ES 1.x,
OpenGL ES 2.0 and super-fast software
rendering, allowing your app to run with or
without any form of hardware graphics
acceleration FEATURES: Save development
time by writing your Airplay app using
vanilla C++ in the IDE of your choice. Airplay
currently supports all versions of Visual C++