Is it possible to make a WM5 rom for HTC Voyager / O2 Xphone? HTC Voyager is still abundant here in the Philippines and others are wondering if it is capable to have a WM5 rom. Since no one here in the Philippines can make a rom, I brought it up here where there are lots of person who can make one.
Thanks
Here are some of the main features of the HTC Voyager. Please add more fun features that you've used.
Operating System
Windows Mobile 2003
Distributors
Orange SPV E200, O2 Xphone, Smart Amazing Phone 2, Dopod 515/535, I-Mate Smartphone 2, Qtek 8080,
Processor
Ti OMAP 710 132mhz
Memory
64MB Flash ROM 32MB SDRAM
Display
176x220 64k Colours
Design Type
Candybar
Frequency
Tri-band GSM 900, 1800, 1900
Wi-Fi
No
Bluetooth®
Yes
Email
POP3, Browser Based
Battery
Li-ion 1000 mAh
Speakerphone
Yes
Internet
GPRS, WAP
Built-in Camera
VGA 640x480, Video 352x288
Caller ID
Yes
Audio
WAV, MIDI - Polyphonic, MP3, WMA
Video
WMV, 3GP, AVI
IRDA
Yes
Expansion
SD/MMC
Dimensions
120.4 x 50.1 x 24.4 mm
Weight
130g
Messaging
SMS, E-mail, MMS
Thanks in advance
anyone?
anyone?.........
Technically I think its possible since motorola mpx200 has the the same specifics(?) and DOES have wm5 upgrade.
vlodeck said:
Technically I think its possible since motorola mpx200 has the the same specifics(?) and DOES have wm5 upgrade.
Click to expand...
Click to collapse
if it's possible, i hope someout out there wouldn't mind to make a rom....it would be greatly appreciated by filipinos
My guess - its too late. This model is not popular around here
I know this is a old thread. But..
Ive been looking around for a small smartphone that could be used to play my music and be used with my bluetooth headphones. Im using the blue angel at the moment and it works superb (except the ablity to use sdhc cards). But its just too big and im always worried if i crack the screen plus it looks pretty nerdy..
So i saw this phone.. Which is excazly what im after. (Which i might add is the only phone that has bluetooth and supports a sd cards).
But i see no one has made any upgrades for it?
Well ill just put it out there that if someone can make this phone to enable a2dp bluetooth profile and support sdhc sd cards (having windows mobile 5+ would be a bonus). Id have to say that this phone with an extended battery would be one of the best phones on the market today.
Ive just started doing a three year programming course at the moment. So if no one else is willing to program a rom. Then hopefully soon ill learn how to develop me own one
is it just me or do all HTC Cameras in WP7 seem half-assed compared to Samsung, LG, and Dell's cameras...
i own a Surround and whenever I upload a 720p video to my HD, the audio seems so... "underwater."
Are you all experiencing the same with HTC phones?
heard something on the engadget mobile podcast that htc uses phone mic software for their video sound recording where most use better software.
I have a question for the developers (im not one):
Though the KF doesnt have a built-in mic, it supports an external one for audio recording. Ive been using Android devices for a little over two years, and have tried a number of audio recoring apps on them.
There are a number of stereo microphones available (from Belkin, Tascam, Blue, etc) that allow high-quality stereo recording on ipods and iphones. There are a number of apps available for recording on Android, but the quality of the recordings is not great. Why is that? Is there something inherent in the Android platform that does not permit hi quality recording?
Sent from my Kindle Fire using Tapatalk
This link might enlighten you a bit. Along with extremely poor audio-latency it would seem that audio recording is also problematic. Strange to find this in an audio device such as a phone eh?
Thanks; I actually used to use the Rehearsal Assistant app. I posed this same question to the developer of J4T, which is a very cool Android multitrack recording app, and I just got his response:
"One reason might be that the best recording quality that is supported by most Android phones is mono, 16-bit pcm, with samplerate 44100. So to make sure a recording app runs on most most android phones, the developer should probably use those numbers and not go any higher.
But it also means it's possible to have android phones that can record at much higher quality, and maybe they are out there. But that capacity may go unused, because the apps are developed for the 'average' phone.
Perhaps on other platforms the 'average phones' have higher bitrates and samplerates.
There are actually 2 ways to do audio recording on Android, but I'm not familiar with the other way (where you can record to AAC or AMR format). Perhaps the quality using those codecs is better than PCM, I don't know.
Please don't take this as a definite answer - this is just a guess from my perspective, maybe a manufacturer (or the Android team) would give a different answer."
I've been using a Belkin Tundtalk stereo microphone with a 3rd-generation ipod nano to make reharsal recordings of my rock band; the quality is actually very good. It records in wav format, stereo, 16-bit pcm, with samplerate 44100. So, outside of the fact that Android records in mono, not stereo, the potential for decent quality is there. The lousy quality must have a lot to do with the cheesy microphones used in the Android phones. If I could find a decent quality mic that would work with my Android phone (or with the Fire), I imagine it would make a big difference.
Yeah, from what I know about Android audio going the other way, the audio-latency issues, Google really managed to screw up on a bunch of levels. The audio app market on the iPhone is pretty big and they just haven't stepped up to the plate for developers from what I can see. I see a few apps coming out like AudioSketch that claim to have custom low-latency audio drivers, but that one isn't available for the Kindle Fire so I really can't say. But, sorry, I am digressing. I'd be curious as to see what results you get from your experiences.
grvthang said:
Perhaps the quality using those codecs is better than PCM, I don't know.
Click to expand...
Click to collapse
This man doesn't now a thing about sound encoding. PCM is uncompressed audio format so it have smallest use of CPU and it has best quality. Only problem is that is space-hungry in comparison with other codec's.
In audio, whole system is good as the weakest thing in it. You need good MIC, you need good MIC input, you need good audio driver and you need good recording app. If one link in this chain is inadequate resulting sound quality is on level of that poor part.
Hey, just a thought but you might be able to turn your question into a free Kindle Fire if you were so inclined.
Buffet_of_Lies said:
Hey, just a thought but you might be able to turn your question into a free Kindle Fire if you were so inclined.
Click to expand...
Click to collapse
Now that you've brought it to my attention, I AM so inclined! That's for letting me know.
I posted my question there, and after about an hour it was Closed as "not constructive" lol.
As I said, I'm not a developer. Even before I posted the question here I googled the subject and haven't been able to come up with a definitive answer as to why this is so. I would think there would be a huge market for after-market microphones for people to use on their Android phones (as there is for iphone and ipod). If I was an iphone fanboy, this would be my first argument against Android - crappy audio recording!
Hi,
I do have a hearing aid (ReSound) and want to connect it to the phone using the ReSound app (via Bluetooth).
Has anyone here already done this? I read about connecting the hearing aid to the phone and it seems there may be problems with Android phones.
AFAIK connecting the ReSound hearing aid to a iPhone 5/5C/5S works like a charm (hearing the phone calls via the hearing aid - like a Bluetooth headset) but not with Android as there is one of the Bluetooth profiles missing in Android that is needed for the connection.
Can anyone confirm, that connecting the ReSound hearing aid to an Android phone (preferably the HTC ONE M8 as I alread own one) works?
(Sorry for my bad English - it's not my mother tongue.)
Thanks!
Chris
According to Mohammed Qasim Shiraz the UK product manager for GN ReSound - http://www.techradar.com/news/phone...phones-are-supercharging-hearing-aids-1260865
"Building the connectivity into iPhones and iPads needed direct work with Apple, and while phones like the Galaxy S5 have the necessary compatibility, Shiraz said it wasn't that simple, although admitted that owners of popular Android phones might be able to use the LiNX in the future too:
The biggest struggle with Android is the platforms they operate on. iOS is one platform, but with Android we're looking at over 1200 platforms."
Apparently Bluetooth 4 is only part of the connection equation and Apple/Linx have worked out a proprietary feature that only works with the iPhone. Looks like until HTC? or Samsung? decide they want to add hearing aid compatability we androidians won't be connecting without an intermediate device.
Currently looking into doing this setting the thread is a couple years old hoping maybe something change Resound LiNX2 9 with Samsung s6
Resound LINX2 works with Android now. Officially on Resound.com (http://www.resound.com/en-US/compatibility) only listed Samsung brand, but it seems that it works with all Android version higher than ver 4. I'm using LG V10 (Android 6.00) and it works fine. However, the app only allows to change environment (preprogrammed when the HA is set up), adjust volume on the left and right hearing aids. Streaming is only applicable to iOS, for Android a $300 Resound Unite Phone Clip+
From Resound Q&A
Can I stream audio directly from the Android phone?
A: The technology in Android phones do not currently support direct streaming of audio to the hearing aid. Android users are encouraged to utilize the ReSound Unite Phone Clip+ for this enhanced set of streaming capabilities to their ReSound hearing aid.
Can we somehow solve the streaming issue? Obviously android phones can connect now, but just needs to be detected as a streaming device.
It's lame that in 2016 we still have to ask this. Google was very late to the party to implement hands-free profile 1.6 with wideband audio. They just started with the N6 in late 2014, the N5 did not have it. But, the N9 does not have it, the Shield Tablet does not have it, the N10 of course doesn't either, so no Google tablets that I know of (haven't tried a 2013 N7 though).
If you're wondering, so-called HD Voice in bluetooth (not to be confused with the carriers' "HD Voice" which is a similar thing but within their network) is also called wideband audio because normally BT cuts out at about 3kHz for voice/talk. HFP 1.6 wideband doubles the bandwidth to about 7kHz so voice is much, much clearer.
Usually this is advertised for phones cause the carriers are implementing their own HD Voice, and you'd need a BT HFP 1.6 wideband headset to take advantage of that, but what everyone seems to miss is that pretty much all VoIP apps use a wideband codec, and those work great with these HD headsets.
So, if anyone is familiar with this, could you test it on the Pixel C? You'd need a HD Voice headset, of course. I know pretty much all Sony ones are (but for some like the SBH52 and BRH10 you have to explicitly enable it with an app), and most modern ones from the big brands. If you don't know how, you can make a hangouts-to-hangouts voice call from your phone, and listen to the clarity. (Don't use Skype though, I think its Android app while it does use wideband normally, falls back to narrowband for bluetooth.) There shouldn't be much difference between using headphones and using the headset connected to the tablet. If it's not HD Voice, you'll notice a big difference with the higher frequencies, especially the "S".
andy o said:
It's lame that in 2016 we still have to ask this. Google was very late to the party to implement hands-free profile 1.6 with wideband audio. They just started with the N6 in late 2014, the N5 did not have it. But, the N9 does not have it, the Shield Tablet does not have it, the N10 of course doesn't either, so no Google tablets that I know of (haven't tried a 2013 N7 though).
If you're wondering, so-called HD Voice in bluetooth (not to be confused with the carriers' "HD Voice" which is a similar thing but within their network) is also called wideband audio because normally BT cuts out at about 3kHz for voice/talk. HFP 1.6 wideband doubles the bandwidth to about 7kHz so voice is much, much clearer.
Usually this is advertised for phones cause the carriers are implementing their own HD Voice, and you'd need a BT HFP 1.6 wideband headset to take advantage of that, but what everyone seems to miss is that pretty much all VoIP apps use a wideband codec, and those work great with these HD headsets.
So, if anyone is familiar with this, could you test it on the Pixel C? You'd need a HD Voice headset, of course. I know pretty much all Sony ones are (but for some like the SBH52 and BRH10 you have to explicitly enable it with an app), and most modern ones from the big brands. If you don't know how, you can make a hangouts-to-hangouts voice call from your phone, and listen to the clarity. (Don't use Skype though, I think its Android app while it does use wideband normally, falls back to narrowband for bluetooth.) There shouldn't be much difference between using headphones and using the headset connected to the tablet. If it's not HD Voice, you'll notice a big difference with the higher frequencies, especially the "S".
Click to expand...
Click to collapse
Hey Andy o
I have a Plantronics Voyager Edge with Wideband - I use it daily with my N6P on voice calls (GSM).
I'd be happy to pair it with the Pixel C and happy to try via hangouts, but no one I know uses hangouts anymore. PM me if you want to try and test this.
Seems that the pixel c has no hands free Bluetooth profile at all (not narrow band and not wide band). When you connect a Bluetooth headset the tablet pairs but doesn't connect to any hands free profile. It has A2DP for music streaming but if you were thinking of making voip call using a Bluetooth headset, forget it. Pretty lame for a $500+ device.
clubtech said:
Seems that the pixel c has no hands free Bluetooth profile at all (not narrow band and not wide band). When you connect a Bluetooth headset the tablet pairs but doesn't connect to any hands free profile. It has A2DP for music streaming but if you were thinking of making voip call using a Bluetooth headset, forget it. Pretty lame for a $500+ device.
Click to expand...
Click to collapse
Holy crap, it appears you're right. That was unexpected. First, no GPS, then this? Damn that is terrible.
sephstyler said:
Hey Andy o
I have a Plantronics Voyager Edge with Wideband - I use it daily with my N6P on voice calls (GSM).
I'd be happy to pair it with the Pixel C and happy to try via hangouts, but no one I know uses hangouts anymore. PM me if you want to try and test this.
Click to expand...
Click to collapse
Thanks for the offer, but it appears I already have an answer, worse than I thought!
andy o said:
Holy crap, it appears you're right. That was unexpected. First, no GPS, then this? Damn that is terrible.
Click to expand...
Click to collapse
Hence why I returned it. This and the lack of auto correct when typing with the keyboard killed it for me.
I wonder if this is because of the rumors that it was designed for Chrome OS which, unbelievably, just got the HFP profile last July. If so, it might be available in future updates, and would support the notion that the software on this thing was rushed out.
Regardless of the reason, it is simply unacceptable that such a premium device being sold and a high price tag will lack basic features like this.
I'm sure most users won't use a headset with this device but for the price support for it should be included. The original nexus 7 didn't have it either. The second nexus 7 had it (lowband). The nexus 9 had this profile.
This is why apple is doing so well. Everything just works.
I don't even think "premium" comes into play. That any modern tablet or phone doesn't have it is nuts. I can't imagine a modern BT chip not having support for it, so it's probably a software/drivers issue, but who knows if Google will fix it.
BTW, are you sure the 2012 N7 didn't have it? I remember it not having a TRRS (headphone+mic) connector, which also crippled it for Square payments, and which was just as dumb a product design choice. But IIRC one of the workarounds was to use a BT headset.
Also, I don't think the N9 has HFP 1.6 wideband. The audio itself is just terrible in comparison with HD-enabled devices like the N6P, N6 and my iOS devices. Even using a frequency generator just to be super sure has it cut off at just above 3500 Hz which is expected for the narrowband profile. With wideband I can still hear on the other device up to 7800 Hz or so.
Yes I don't think the N9 had wideband either. As far as I can recall the N7 2012 didn't have HFP profile either as I remember it driving me nuts that I couldn't use a Bluetooth headset on it to make voip calls.
I went ahead and opened a thread on the Google product support for the pixel c and it has been escalated. Let's see what comes back and if they intend to enable HFP on this device or not.
Sent from my Nexus 6P using Tapatalk
clubtech said:
I went ahead and opened a thread on the Google product support for the pixel c and it has been escalated. Let's see what comes back and if they intend to enable HFP on this device or not.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Would you mind linking the thread? I can't seem to find it at the Google product support forums.
https://productforums.google.com/forum/m/#!categories/nexus/pixel-c
it's what i think he mentioned.
Thanks, that's it https://productforums.google.com/forum/#!topic/nexus/f8c_iLUs_rI Will be following it.
clubtech said:
Regardless of the reason, it is simply unacceptable that such a premium device being sold and a high price tag will lack basic features like this.
I'm sure most users won't use a headset with this device but for the price support for it should be included. The original nexus 7 didn't have it either. The second nexus 7 had it (lowband). The nexus 9 had this profile.
This is why apple is doing so well. Everything just works.
Click to expand...
Click to collapse
I don't believe the Nexus 7s or the Nexus 9 have HFP support (low or wide). I can confirm the Nexus 9 doesn't, I couldn't use my bluetooth headset for voip calls via Hangouts. Here's Google's table with Bluetooth profiles:
https://support.google.com/nexus/answer/6048862?hl=en
I can confirm that the table is correct about the Nexus 10, I used Plumble and Hangouts perfectly with the same Bluetooth headset as I used above for calls.
BinaryTB said:
I don't believe the Nexus 7s or the Nexus 9 have HFP support (low or wide). I can confirm the Nexus 9 doesn't, I couldn't use my bluetooth headset for voip calls via Hangouts. Here's Google's table with Bluetooth profiles:
https://support.google.com/nexus/answer/6048862?hl=en
I can confirm that the table is correct about the Nexus 10, I used Plumble and Hangouts perfectly with the same Bluetooth headset as I used above for calls.
Click to expand...
Click to collapse
That table is wrong. I can 100% confirm that the Nexus 9 and Nexus 7 2013 did have hands free support. The Nexus 7 2012 did not.
Sent from my Nexus 6P using Tapatalk
clubtech said:
That table is wrong. I can 100% confirm that the Nexus 9 and Nexus 7 2013 did have hands free support. The Nexus 7 2012 did not.
Click to expand...
Click to collapse
I'll have to check my Nexus 9 with Plumble + Bluetooth then, only used it with Hangouts video chat and it worked great, but Hangouts Dialer calls to a phone number wouldn't work with my bluetooth headset.
Anyone here with the Pixel C on the latest developer preview? Can you confirm if they added Bluetooth headset support (hands-free profile)?
How can one check, which Codecs are used over Buetooth ?
On my Xiaomi Mi A2 Lite I can somehow enable under Developper Mode the APT-X and LDAC Codecs,
but how can I test it, if it being used e.g. in Skype for Android or other Voice Applications ?
My Blootooth Stereo Headset has Apt-X , but during Skype calls or a Wireless Video Recorder app, it still uses only the 8 Khz SBC bad audio codecs...
Any idea how I can test it and how to enable the Wideband Audio Codecs ?
Many thanks.
Regards., Stefan.
It has to support mSBC for handset:
https://www.rfwireless-world.com/Terminology/SBC-vs-mSBC-codec.html
An app like Bluetooth Monitor might show more info about the actual connection.