Related
Is there some software that can turn the InfraRed on Hermes for use as a remote control for things like TVs?
There is. Say, VITO Remote. But Hermes infrared port is really short-ranged (no more than a meter, I recall), so it's of little use.
Koterpillar said:
There is. Say, VITO Remote. But Hermes infrared port is really short-ranged (no more than a meter, I recall), so it's of little use.
Click to expand...
Click to collapse
like every pda-ir i've ever saw^^
softonic123 said:
like every pda-ir i've ever saw^^
Click to expand...
Click to collapse
Some iPaqs have a decent range, heck even wizard has a better range than Hermes. Anyway Hermes' IR is not meant for remote controlling the TV.
Would make an interesting project to see if the ir led could be changed or boosted for a longer range. Would love to use my hermes as remote as well
you can search in the old parts of the forum for posts by me for curcirs layout extentions for boosters for ir for pda's
it's alot of work but hardware addons always are
bchau said:
Is there some software that can turn the InfraRed on Hermes for use as a remote control for things like TVs?
Click to expand...
Click to collapse
so why didnt you search the forums first on this topic? theres enough threads on the limited range of iRda.
Novii Remote Deluxe
My Wizard would operate the TV from the couch just fine.
No such luck on the Hermes though. It's IR port is substantially weaker then the Wizard's
the Ipaqs where designed to be used as a remote, a special IR was put in it.
Three is one other option, you can make a sound to IR adapter and "play" the ir signal from a wav file.
forgot where i read about it, but think it was from an ipod hack. gd luck
TyTN Multi Remote Controler...
Koterpillar said:
There is. Say, VITO Remote. But Hermes infrared port is really short-ranged (no more than a meter, I recall), so it's of little use.
Click to expand...
Click to collapse
SHORT RANGED
I use Novii Remote Deluxe from http://www.novii.tv/pocketpc/ on my TyTN (Hermes) and it works just fine at about 10 meters with my TV, Hi-Fi Sat. decoder etc. etc.
My wife likes to hide the remote when the Game is on, so I use my "TyTN-Multi-Remote" quite often...
DexterH said:
SHORT RANGED
I use Novii Remote Deluxe from http://www.novii.tv/pocketpc/ on my TyTN (Hermes) and it works just fine at about 10 meters with my TV, Hi-Fi Sat. decoder etc. etc.
My wife likes to hide the remote when the Game is on, so I use my "TyTN-Multi-Remote" quite often...
Click to expand...
Click to collapse
EXACTLY which version of Novii did you use and what Rom do you have installed on your Hermes?
DexterH you don't sell that software do you
which hardware and rom do you ahve?
Acuum2 said:
DexterH you don't sell that software do you
which hardware and rom do you ahve?
Click to expand...
Click to collapse
ha-ha, No I do not sell anything, though I could do with an extra income... ( wife just LOVES shoes )
Anyway, I think I exaggerated a bit with the 10m (32feet), took the wife's measuring-tape-thingy-for-making-clothes and my couch is about 5m (16feet) from my TV etc.
Sorry about that, but it is still much further than most of the people I talked to said the Hermes can do, most people talked about less than 1m (3feet) I paid the odd $30 which is less than you would pay for a good hardware Universal Remote and you still can't carry it with you like a PocketPC.
My TyTN (Herm200) was bought new May 2007. I flashed the official WM6 ROM 3.54.255.3 from HTC (5.2.1437 build 17944.0.3.1).
The software version for Novii Remote Delux is 4.11 (build 2006.08.21a, IRv27), released in August 2006.
Sorry again for exaggerating, as you get older the percieved distance from one resting place to the next tends to get greater...
IR
Select models of discontinued HP's that included the Nevo remote software were specially designed with CIR that allows them to have better range etc. This is the same type of IR diode in your conventional remote controls. The Hermes has IRDA. Designed for short range transmission.
DexterH said:
ha-ha, No I do not sell anything, though I could do with an extra income... ( wife just LOVES shoes )
Anyway, I think I exaggerated a bit with the 10m (32feet), took the wife's measuring-tape-thingy-for-making-clothes and my couch is about 5m (16feet) from my TV etc.
Sorry about that, but it is still much further than most of the people I talked to said the Hermes can do, most people talked about less than 1m (3feet) I paid the odd $30 which is less than you would pay for a good hardware Universal Remote and you still can't carry it with you like a PocketPC.
My TyTN (Herm200) was bought new May 2007. I flashed the official WM6 ROM 3.54.255.3 from HTC (5.2.1437 build 17944.0.3.1).
The software version for Novii Remote Delux is 4.11 (build 2006.08.21a, IRv27), released in August 2006.
Sorry again for exaggerating, as you get older the percieved distance from one resting place to the next tends to get greater...
Click to expand...
Click to collapse
Many thanks for getting back and supplying the info. I suspect that the hardware that one is using it on also is a factor.
I tried the exact same version of NoviiDeluxe on 2 different devices (so far). One a very cheap no name DVD player and an even cheaper Matsui TV. The maxium range I got from DVD player was ~ 3 metres and the TV barely got to 2 metres.
Anyway, it is much better than often stated. The Novvi software is very good. From their forum there might be a problem on Hermes phones with the pre-built IR codes but there is no problem learning and implementing codes.
novii is nice, but the range kills the fun with stock IR
Wam7 said:
Many thanks for getting back and supplying the info. I suspect that the hardware that one is using it on also is a factor.
I tried the exact same version of NoviiDeluxe on 2 different devices (so far). One a very cheap no name DVD player and an even cheaper Matsui TV. The maxium range I got from DVD player was ~ 3 metres and the TV barely got to 2 metres.
Anyway, it is much better than often stated. The Novvi software is very good. From their forum there might be a problem on Hermes phones with the pre-built IR codes but there is no problem learning and implementing codes.
Click to expand...
Click to collapse
Don't know but I think it also has a lot to do with the quality of the signal of the original remote,
May be my imagination, but when in IR-learning mode, I got a huge difference in range if I use new batteries and press-and-hold for a few sec. the button on the original remote, instead of just a quick press. It is as if the captured code is just that little bit stronger...
As said, this may or may not help, but give it a go, you never know...
tweety2 said:
Select models of discontinued HP's that included the Nevo remote software were specially designed with CIR that allows them to have better range etc. This is the same type of IR diode in your conventional remote controls. The Hermes has IRDA. Designed for short range transmission.
Click to expand...
Click to collapse
allow me to elaborate on this, my last pda (which i kinda sat on - not as sturdy as a remote apperantly...) was the ipaq rx3715.
there are two type's of ir ports generally for pda's - sir and cir.
confused? its sipmle - Serial Infra Red and Consumer Infra red.
the ipaq had SIR on it because it was part of the "media oriented packege" that RX models sport.
TyTn seems to use CIR, short range in order to communicate with other devices. most devices these days dont even get ir ports these days. i've owned my tytn for a year now and haven't once used it.
you'l get up to three meters max on a CIR usually as far as i know - BUT I COULD BE WRONG!!
maybe it could be done something from the radio rom to increase the radio power of the IR port
So,
I'm waiting for the Dell Venue Pro to be released, but it keeps getting delayed...
I'm wondering if some manufactureres would be releasing new phones close to the release of the dvp, thuss, maybe there would be some better phones by then...?
Anyone read something interesting?
quinstar said:
So,
I'm waiting for the Dell Venue Pro to be released, but it keeps getting delayed...
I'm wondering if some manufactureres would be releasing new phones close to the release of the dvp, thuss, maybe there would be some better phones by then...?
Anyone read something interesting?
Click to expand...
Click to collapse
That's truly an interesting question for one reason: MS will be doing updating and all phones are suppose to be similar hardware wise...to avoid fragmentation. I believe, with the exception of screen types and camera res, that every WP7 phone currently released, and likely the CDMA versions included, use the same processing hardware.
The reason this is interesting is because, how will MS handle hardware evolution. These WP7 phones certainly can't remain the same forever. Eventually there will be 1.5GHz CPUs and higher res screens. How will MS handle incorporating phones equipped with higher speed CPUs and higher res screens into WP7 filled with the current tech. The whole point of WP7 is keep things level across the board. A current 1GHz SnapDragon certainly would not be level with a 1.5 or 2GHz FlamingLizard dual core CPU.
MartyLK said:
That's truly an interesting question for one reason: MS will be doing updating and all phones are suppose to be similar hardware wise...to avoid fragmentation. I believe, with the exception of screen types and camera res, that every WP7 phone currently released, and likely the CDMA versions included, use the same processing hardware.
The reason this is interesting is because, how will MS handle hardware evolution. These WP7 phones certainly can't remain the same forever. Eventually there will be 1.5GHz CPUs and higher res screens. How will MS handle incorporating phones equipped with higher speed CPUs and higher res screens into WP7 filled with the current tech. The whole point of WP7 is keep things level across the board. A current 1GHz SnapDragon certainly would not be level with a 1.5 or 2GHz FlamingDragon dual core CPU.
Click to expand...
Click to collapse
Windows Phone 8 in a year?
It'll be like games consoles, a new one every 5 years or so. After all, with the OS being as fast as it is on 1GHz processors, nobody cares about 1.5GHz ones. Except geeks.
As a geek, I can say that I would insta-buy a FlamingLizard device. That name is just pure awesome.
Seriously though, certain hardware was specified because MS is providing the correct drivers to use that hardware correctly (glowers @ HTC). When new stuff hits, MS will pick a new item they like, make drivers for it, and tell OEM's what to use, just like they've done with the current line. MS has way too much invested in WP7 to let it get relegated to second-rate hardware. Even if Metro doesn't ask for a huge level of processing power, MS is heavily pushing live integration, and I believe that they will be all over stuffing powerful processors into phones in order to sell them as gaming platforms.
MS could go apples way.
Every year in november for example, ms could allow to use higher hardware.
Like: iphone 2g, 3g, 3gs, 4
And ms give us a wp7 version for each generation of wp7 phones
i think the best way for MS to give the hardware manufacturers more capabilities would be to set up benchmarking for all the different components. have the current components as the benchmark for example, and if they want to change say the CPU/GPU, it has to outperform the current benchmark. this way, it becomes a lot more like Android in the manufacturers can make the devices the way they'd like using the parts they'd like.
the only issue is, MS would need to be involved in creating every driver for every different component. i think at present it's quite restricted down to particular components so that you get a good boot up time and running experience, because there isn't redundant/generic drivers on the phone.
As far as I know the requirements aren't as specific as what people are saying, but more "Minimum Requirements"
From what I can remember it's something along the lines of
AT LEAST a 1ghz Processor
AT LEAST a 3.5" Screen
AT LEAST 8Gb Storage
etc etc.
So new devices can come out with faster processors, they wont though... Manufacturers will milk the cheapest hardware for as long as they can. I would expect a rehash of requirements each year.
The whole point of it all isn't really to keep things level, it's to make sure that underpowered devices aren't released that run the OS like crap (Eg Wildfire, Tattoo) and also so that devices aren't released running a version of the OS that's over a year old (Xperia X10)
yeah thats what I was wondering. Those were the minimum requirements not specific reqs as people assume. The hardware manufacturers just stuck to those to save costs. I'm sure if MS did not have these then they would have used even lower end crap, thus destroying any chance WP7 has of attaining success.
FL5 said:
As a geek, I can say that I would insta-buy a FlamingLizard device. That name is just pure awesome.
Seriously though, certain hardware was specified because MS is providing the correct drivers to use that hardware correctly (glowers @ HTC). When new stuff hits, MS will pick a new item they like, make drivers for it, and tell OEM's what to use, just like they've done with the current line. MS has way too much invested in WP7 to let it get relegated to second-rate hardware. Even if Metro doesn't ask for a huge level of processing power, MS is heavily pushing live integration, and I believe that they will be all over stuffing powerful processors into phones in order to sell them as gaming platforms.
Click to expand...
Click to collapse
+1 for the flaminglizard dual core cpu. or even blazedmonkey dual core cpu. or bullsballz dual core cpu. so long as it's dual core, i'll buy it. hell, i might even buy it if it ran windows, then dump a android rom on it and have a flaming-dog-ballz rooted/ unlocked dual core cpu smash phone.
HA
ohgood said:
+1 for the flaminglizard dual core cpu. or even blazedmonkey dual core cpu. or bullsballz dual core cpu. so long as it's dual core, i'll buy it. hell, i might even buy it if it ran windows, then dump a android rom on it and have a flaming-dog-ballz rooted/ unlocked dual core cpu smash phone.
HA
Click to expand...
Click to collapse
LMAO...funny stuff!
cbebop7 said:
yeah thats what I was wondering. Those were the minimum requirements not specific reqs as people assume. The hardware manufacturers just stuck to those to save costs. I'm sure if MS did not have these then they would have used even lower end crap, thus destroying any chance WP7 has of attaining success.
Click to expand...
Click to collapse
I think what certainly would have happened, at least with HTC is they would have 1 premier device, probably the HD7 in it's current iteration. The rest of the devices would then go from Bad to Absolute ****. The Trophy or Mozart would probably have a smaller screen and a severely slow processor by today's standards.
What will happen eventually is someone will realise that the majority of the handsets are the same and release something with better specs than the current bunch in an attempt to stand out from the crowd. My guess is it will be LG
Here's my take on it.
First half of 2011:
* Chassis 2 handsets start appearing, being technically the same as launch devices.
Come November 2011:
* WP8 devices come consisting of second or third gen snapdragons and/or introduce another SoC like Hummingbird or OMAP.
* Chassis 3 handsets also start appearing (tablets or gaming style deisgn like PSPhone maybe?)
My wishes:
* Resolution bump for tablets and smartphones
* Hero phone introduced by Microsoft (much like the Nexus series), Zune/xbox phone anyone?
edit: looks like WP8 will actually be coming out end of 2012 http://pocketnow.com/windows-phone/windows-phone-7-mango-rumors
I was looking through the BOM for the Galaxy Nexus, and apparently it uses the SiRFstarIV device for GPS.
That device (like any modern GPS chipset) supports WAAS/EGNOS, which offers a nice increase in precision. My Garmin handhelds will eventually tune into satellites 46, 48 or 51 which supply the data used for the WAAS correction. They're in a geostationary orbit over the western hemisphere, so they are always present in the sky.
But I never see those birds on any Android device, and no GPS app I have seen has advertized WAAS. Why not? The hardware supports the feature!
I was hoping to answer this question myself by looking at the source code; but I have no experience with large software projects (or Git) and I haven't been able to find a "driver" yet by browsing source repositories. Would anyone be willing to "hold my hand" a little to guide me towards the relevant sources?
Well, I started trying to figure out what the max clock speed is for
mmc1 (external SDHC) and why the audio is such crap in SGH-T999.
I thought I would share the differences with US and the i9300 I found.
Starting with the Service Manuals for i535 and i9300 and the
teardowns of the T999 and i9300....
We can figure out enough making some assumptions and also
lacking high quality zooms of all the US board...
First a system overview:
{
"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"
}
In the i9300, the FM radio is sent directly from a Silicon Labs
CMOS FM radio receiver chip to an audio line in on the Wolfson
WM1811 audio codec and speaker driver chip. The schematics
don't provide the part numbers, but through the teardowns people
already know about the Wolfson chip. The SiLabs part hasn't been
mentioned anywhere I have seen. The schematics, pin out, and
part number match the unidentified part in the teardowns as the
SiLabs part:
We can see this extra SiLabs radio chip with is on the thin side of the
board and this chip is missing from the US versions:
All Galaxy S3 boards appear to use the same Murata SoC module
that incorporates the Broadcom BCM4334. From the service manuals,
we see the exact same Murata part and schematics: (top one is i9300)
This might be where the confusion is for people trying to use the i9300
firmware to enable FM radio. Yes, the BCM4334 has FM capabilities and
could have been used for maybe FM radio, but it isn't used in any of the boards.
This is the same WLAN/bluetooth hardware, but an unpopulated pin and a deadend.
There isn't even an external pin you could add a wire to.
Now the audio differences:
What is also of interest is that (sadly) the US Galaxy S3 use the
Qualcomm WCD9310 Audio Codec which drives the headphones.
There aren't any datasheets for what this is capable of. In (at least)
the i535 the speaker is driven with a Texas Instruments TPA2039D1
Audio Power Amplifier. And I suspect it is the same for all the US versions.
Whereas, the i9300 uses the Wolfson WM1811 which both drives the
headset and a speaker driver with many other features.
Code:
TPA2039D1 Class-D, 12-dB fixed-gain audio power amplifier
3.24 W (4 Ω, 5 V, 10% THDN)
2.57 W (4 Ω, 5 V, 1% THDN)
1.80 W (8 Ω, 5 V, 10% THDN)
1.46 W (8 Ω, 5 V, 1% THDN)
Code:
Wolfson WM1811
2W stereo (2 x 2W) class D speaker driver
Capless Class W headphone drivers
(5.3mW total power for DAC playback to headphones)
ReTune™ Mobile 5-band, 4-channel parametric EQ
In both cases we don't really know much about the headphone
driver except that you would rather have the Wolfson chip.
I did find this interesting blog post with some
hints about tailoring the WCD9310. Now if only someone had a Qualcomm datasheet.
Good stuff. Thanks.
On a side note. I know everyone agrees about the superiority of the Wolfson implementation, but I don't find the audio in the T999 to be bad at all. Of course, I haven't directly compared the two, and I am certainly no audiophile. Is there a way to do simple tests (besides how loud it is) to find out how good/bad one's audio is?
I know no one cares, and this should be in a R&D development forum, but anyways, here are the tabla registers.
This would allow hardware control of muting, gains, calibration bias currents...
include /linux/mfd/wcd9310/registers.h and the whole commit
http://goo.gl/HZJgw
In related news, I found the debugfs controls for the battery charging, so I guess this adventure comes full circle.
You should move this nice thread to Hardware hacking instead...
http://forum.xda-developers.com/forumdisplay.php?f=1425
So we have the chip that can be used for FM radio, but the antenna isn't there? Am I understanding this right?
aNYthing24 said:
So we have the chip that can be used for FM radio, but the antenna isn't there? Am I understanding this right?
Click to expand...
Click to collapse
Yes, but it's more complicated than that.
None of the Galaxy S/S2/S3/Note class devices use the Broadcom chip for FM. The International versions that have FM use a Silicon Labs chip.
Many cheaper Samsung devices use Broadcom for FM.
There are over 200 posts on the subject of FM on the US GS3 here: http://forum.xda-developers.com/showthread.php?t=1732685 The last 20-50 posts or so might give a more complete idea of the findings made.
joederp said:
...hints about tailoring the WCD9310. Now if only someone had a Qualcomm datasheet.
Click to expand...
Click to collapse
Qualcomm datasheets are almost impossible to find/get.
I'm pretty familiar with most of the info you posted, but thanks for the pics and the added details.
Are you sure the GT-i9300 uses an SI-4705 and what's the source of that info ? There's no clue in the stock ROM of course, the si470x driver is generic and the 470x chips are very similar.
I don't recall exactly the differences with the 4705, but if there's a register difference, I can check on my 9300.
mikereidis said:
Are you sure the GT-i9300 uses an SI-4705 and what's the source of that info ? There's no clue in the stock ROM of course, the si470x driver is generic and the 470x chips are very similar.
I don't recall exactly the differences with the 4705, but if there's a register difference, I can check on my 9300.
Click to expand...
Click to collapse
I'm about 99% sure the i9300 uses the SiLabs 4705.
I am the only source for that and I figured it out based on looking through the i9300 Service Manual.
They include some schematics that point to a radio chip labeled U203, well I googled the pin names
on the schematic, because everyone reuses they symbols provided with the models/abstracts. So the
schematic labeled U203 pointed to SiLabs names on some of their chips, I googled the FM receivers a
little and found one with the same footprint. The only one that fit was the 4704/05 series which are for
mobile.
Now I went back to the service manual and if you search for U203, you will find a parts list that designates
the part as a SI4705-D50-GM. What was confusing is the parts list table is shifted by one row on the right
column. This can be confirmed throughout the document.
So it doesn't take a rocket scientist to figure out that is what the chip is.
It is a Silicon Labs 4705-D50.
So, I hope that helps the i9300 rom efforts.
aNYthing24 said:
So we have the chip that can be used for FM radio, but the antenna isn't there? Am I understanding this right?
Click to expand...
Click to collapse
I would say that they would need the resistors, and inductors inside the SoC module, and an antenna. And then some was to get the data out of the broadcom chip, and then can it handle FM while using bluetooth and WLAN? So I'm guessing based on the cost and module specs, they abandoned it. For the flagship i9300 international design they just threw in another chip. The respin US version they want to save money and the Wolfson and SiLabs volume and cost makes more sense to use the Qcom part and abandon an extra audio input. Also US cell companies go out of their way to disable FM radio even when it is "free". They would rather you pay for data or some crazy nonsense.
...
joederp said:
I would but some asshole mod just threw my post (Not even a new thread, a legit reply to a thread on 8960)
into the general Q&A thread and removed it from hardware.
http://forum.xda-developers.com/showthread.php?t=1888652
That was a post, not a thread that needed a title.
His own forum rules state:
"relating to the hardware of devices and in many circumstances dealing with families of devices. "
Which my COMMENT was, but the power mad mods have to delete my comment. So they obviously don't care about hardware or my research, so **** that mod.
Click to expand...
Click to collapse
Chill...mods try to keep things orderly. If you feel you're treated unfairly, pm the mods and plead your case...it's never a good idea to publicly criticise staff (made up of volunteers) dedicated to our shared interests.
On topic, the FM stations are miserable here, full of annoying racket and ads...I'd never even consider listening to FM even if the SIII had an operable implementation.
mikereidis said:
Are you sure the GT-i9300 uses an SI-4705 and what's the source of that info ?
Click to expand...
Click to collapse
I just googled some more proof for you that it is Si7405. Check the datasheet and compare the part numbering:
YWW is 2012 Week 7 from the photo.
joederp said:
I would say that they would need the resistors, and inductors inside the SoC module, and an antenna. And then some was to get the data out of the broadcom chip, and then can it handle FM while using bluetooth and WLAN? So I'm guessing based on the cost and module specs, they abandoned it. For the flagship i9300 international design they just threw in another chip. The respin US version they want to save money and the Wolfson and SiLabs volume and cost makes more sense to use the Qcom part and abandon an extra audio input. Also US cell companies go out of their way to disable FM radio even when it is "free". They would rather you pay for data or some crazy nonsense.
Click to expand...
Click to collapse
I'm sure you're right about 4705. 9300 schematic shows DOUT which is the digital out the 4701 doesn't have. I didn't even look at the parts list; previous service manuals didn't use the real part numbers so I figured it was useless again.
It's a shame Samsung didn't use the Digital out IMO. But this leads into the fact that they have a "settled design" for FM on the higher end Galaxy S/S2/S3/Note devices. The "settled design" uses a Silicon Labs si470x chip with analog output. I don't know if SL chips have better audio than Broadcom currently, but I suspect they did when the Galaxy S was designed at least (along with a high quality Wolfsson audio chip.)
Samsungs "settled design" for FM on lower end products always uses Broadcom combo chips, that also support BT and WiFi. FM piggy-backs on the BT core and is handled by the Broadcom proprietary BT/FM stack on stock ROMs.
joederp said:
And the Si4705 uses a 32.7MHz crystal, but it can also take
a reference clock from 31.130 to 40.000
...
Can you read RDS through the SDIO?
Click to expand...
Click to collapse
32,768 Hz (2^15)
Hardware wise, yes all si470x registers, including RDS registers, are accessed via SDIO.
The V4L driver accesses the si470x registers.
Samsungs proprietary Silicon Labs/high end specific FM API accesses the V4L driver.
My Spirit FM app, like the Samsung app, can access the Samsung API. But Spirit can also speak directly to the V4L driver, which is preferred.
So there are multiple software layers between an app and the hardware pins such as SDIO.
I'd be interested to access some unique features of the si4705, such as operation down to 64 MHz. but I don't think the V4L driver allows it, as it's generic to si470x.
Just for your benefit, they saved cost by skipping the crystal for the radio chip, it is using the reference clock from the BT chip which is 37.4 and might impact which freq you can tune.
joederp said:
Just for your benefit, they saved cost by skipping the crystal for the radio chip, it is using the reference clock from the BT chip which is 37.4 and might impact which freq you can tune.
Click to expand...
Click to collapse
There are no FM tuning problems on GT-i9300: 76-90 or 87.5-108.
I didn't mean problems but more like in the datasheet if you don't use crystal and have ref clock then there are certain multiplier issues. I was pointing out they are sharing they wlan
Sent from my SGH-T999 using xda app-developers app
it'd be nice to be able to change the headphone amplifier volume (as voodoo does). Does this information you guys found help in that area? It'd be nice to lower the analogue volume to reduce hiss and artifacts.
Yes and no. You can directly modify the tabla register for the qcom codec, but I don't have and darasheet to know what 00 is versus c4 or whatever in the register. I have to write it up still
Sent from my SGH-T999 using xda app-developers app
joederp said:
Yes and no. You can directly modify the tabla register for the qcom codec, but I don't have and darasheet to know what 00 is versus c4 or whatever in the register. I have to write it up still
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Any news on that?
I'm working on an NFC related project for my company and I had a couple of questions that I was wondering if any of you guys could cover:
1) Does Microsoft/Google have requirements for what NFC standards are required? For example, The Nexus 4 has a chip that doesn't fully support MIFARE, so am I to assume that the ISO 18092 standard must be supported since that is technically the definition of NFC?
2) I hear that the NXP chip is currently in android handsets, except for the Nexus 4. Is it the PN 512 chip?
3) Does anyone know what NFC chips are in the Windows Phone 8 handsets?
ShensMobile said:
I'm working on an NFC related project for my company and I had a couple of questions that I was wondering if any of you guys could cover:
1) Does Microsoft/Google have requirements for what NFC standards are required? For example, The Nexus 4 has a chip that doesn't fully support MIFARE, so am I to assume that the ISO 18092 standard must be supported since that is technically the definition of NFC?
Click to expand...
Click to collapse
Required for what? NFC Standard is defined by the NFC Forum. NFC is 18092, Mifare is 14443-3A