Related
Just looked at mobilefun.co.uk and they have the K-Jam specs as this :-
· Microsoft Windows 2005
· High resolution trans reflective TFT-LCD screen (240 x 320 pixel)
128 MB Flash ROM / 64MB SDRAM
Triband 900/1800/1900 MHz
MMC / SDIO Memory Slot
802.11b Wireless LAN
· Boosts all the lastest communications including integrated WLAN, GPRS and UMITS technology
· Push Email Service
· 1.3 Megapixel CMOS camera & Flash
· Built-In 62 Key QWERTY keyboard
· Radio - WCDMA / GSM / GPRS PDA
Look at the Radio this states 3g rather than Edge .... can someone confirm.
Qtek 9100 specs (confirmed with supplier at smartdevicesdirect.co.uk):
Hardware Specifications:
Operating System -Microsoft Windows Mobile version 5.0 Pocket PC Phone Edition
Processor - TI OMAP 850
GSM/GPRS Module - Internal antenna, Quad-band (850/900/1800/1900)
WiFi (manufacture option) - IEEE 802.11b, Internal WLAN antenna, 11, 5.5, 2, and 1 Mbps per channel, auto fallback for extended range, ELP mode, Security: WPA authentication – WEP, PSK, EAP-TLS, PEAP, LEAP
Memory - ROM: 128 MB, RAM: 64MB SDRAM
LCD module - 2.8” 240 x 320 pixels. 64K-color TFT Transflective LCD
Sound - Built-n Microphone, Receiver, Dual speaker on both sides, Loud speaker for Hands-Free supported.
Power - Removable and chargeable Lithium ion polymer battery, 1200mAh (TBD). Talk time: 4~5 hours (TBD) Standby time: 200 hours (TBD)
Camera - CMOS 1.3 Mega pixel with fixed lens, video/flash light, Preview Mirror.
Expansions - Mini-SD slot
Connectivity - Infrared IrDA SIR, External antenna connector, 2.5Ø stereo audio jack.
Dimensions - 108 mm (L) x 58 mm (W) x 23.5 mm (T), 150g with battery pack.
Generic software applications - Photo Album with editing picture capability, Camera capture utility, Camcorder, Zip, Polyphonic MIDI Ringtone Engine Intelli Dial, Intelli Pad, Smart Launcher
Click to expand...
Click to collapse
My point exactly ,,, these specs don't even mention EDGE !!
Thats because its not EDGE compliant. The HTC Apache is the EDGE compliant version of the Wizard.
The specs I have posted are official as they have been confirmed with the supplier.
ShALLaX said:
Thats because its not EDGE compliant. The HTC Apache is the EDGE compliant version of the Wizard.
The specs I have posted are official as they have been confirmed with the supplier.
Click to expand...
Click to collapse
As far as we have heard and seen in the States, the HTC Apache is the CDMA version of the Wizard and has EVDO (and thus not EDGE which runs on GSM). Rumor has it that the Wizard (at least the one that will be released by the US GSM carriers) will have EDGE.
The specs here confirm the EDGE rumor on the Qtek 9100: http://msmobiles.com/news.php/4173.html
Oh crap my bad.. sorry, yes the Apache is the CDMA version and apparently the Wizard has EDGE.
Here we go:
http://www.qtek.fi/qtek9100.htm
does anyone know if this will have support for USB 2.0 (the sync port)?
OMAP 850 specs
Well, I got a bit curious and went digging on the TI site for information about the OMAP 850 and found this:
http://focus.ti.com/general/docs/wt...00&path=templatedata/cm/product/data/omap_850
Based on this I would say that yes, it is possible that the device has 802.11g (The diagram shows a/b/g) and they could very well have Bluetooth 2.0 (Did anyone spot a BRF6300 chip on the device?).
Robert Harrold
Houston, TX
Very unlikely that it will have anything above 802.11b.
In the specs:
CMOS 1.3Mega pixel with fixed lens
Or
CMOS 2.1Mega pixel with macro lens / AF
anyone heard of a unit selling with the 2.1?
Also, I in the specs under MSD:
Blackberry email client (Optional)
I heard of a blackberry client available for the Magician, anyone have it?
-mix
Re: OMAP 850 specs
robinton said:
Based on this I would say that yes, it is possible that the device has 802.11g (The diagram shows a/b/g) and they could very well have Bluetooth 2.0 (Did anyone spot a BRF6300 chip on the device?)
Click to expand...
Click to collapse
The diagram only shows peripherals the processor supports... The final call is the sole property of HTC whether to put an a, b, or g. Just like Intel Bulverde supports Wi-Fi internally, Palm Treo 650 (Bulverde 312 MHz) doesn't come with Wi-Fi.
Hi, I'm almost new here
Since this is my first post, I cannot post in the development section, I hope this do not cause problems.
A few days ago I got my first android phone and started to do some low-level development and I needed to record both the input from the headset mic and the internal mic at the same time. I searched a lot on the net and did not find anything useful for the Galaxy S (Vodafone european I9000), so I decided to add this feature to the wm8994 driver included in the samsung kernel source for the Galaxy S.
Since I've never worked with this kind of device, I do not know if this is the correct way to do it, but it seems to work great.
Basicly I've enabled both input at the same time and routed left adc channel output to left audio interface channel and right adc channe output to right audio interface channel. Everything else is on default settings (as configured by MAIN and SUB path, in fact I've just used the same code).
The code also adds a new enum entry for the capture path, called "DUAL", which now is after "MIC OFF", but its just an hack, I'll clean it up later. Using the command "amix" will dump all the mixer channel:
Code:
...
7 MIXER 0 0 0 1 rw ENUM Capture MIC Path { Main Mic=0, Hands Free Mic=1, BT Sco Mic=2, MIC OFF=3, Dual=4 }
...
It can be tested using the pcm_* and mixer_* routines taken from samsung's libaudio, you just need to call pcm_open without specifying PCM_MONO but just PCM_IN, since now both left and right channels will be populated. If you have access to Cyanogen Mod repository, just grab the arec.c source from there and remove the PCM_MONO flag. Beside this I suggest you to dump raw pcm audio and load it into something like Audacity, arec.c seems to produce a wrong riff header.
Now for the questions...
Any ideas on how to correctly setup the gain on both channels? Currently the gain of the headset mic is set to +15 dB on the input PGA and +0 dB on the adc channel while the gain of the internal mic is set to +10.5 dB on the input PGA and +0 dB on the adc channel. I also tried to use the same settings from Voodoo Sound high sensitivity path (with drc enabled), but no results so far... The default gain is far too low, I must talk very near to the headset mic.
Beside this, I've also noticed a strange behavior when recording from both mic. If they're very near, the audio recorded from the headset mic channel will be highly suppressed, if they're far apart, no suppression occurs. As far as I know, wm8994 do not perform noise cancellation on device, any clues on this? Anyway this is not a big deal, since the two microphones will be quite far during normal usage. By far the biggest problem is on the gain for the headset mic.
I hope someone might be interested on this extension to wm8994, this device is really powerful, it's a shame that samsung is using 1/10 of its power...
Attached to this post is the patch file, I've worked on the 2.6.35-12 (recently switched to -13) kernel from teamhacksung, you can get it on github (cannot post the link for the 8 post limit...), just apply the patch from the root kernel directory and rebuild the kernel image as usual.
Any help is highly appreciated
Thanks.
Bye!
EDIT: OPS I'm sorry but I forgot to mention that to enable dual mic recording, you have to activate its path of course through alsa_mixer, like this:
ctl = mixer_get_control(mixer, "Capture MIC Path", 0);
printf("ctl: %x\n", ctl);
if(ctl)
{
int r;
r = mixer_ctl_select(ctl, "Dual");
printf("res: %d\n", r);
}
Click to expand...
Click to collapse
forgive me
i think you should contact supercurio ( https://twitter.com/#!/supercurio )
he's a real badass when it comes to tweaking WM8994 driver
also you might want to check out his app called "voodoo control (plus)"
Welcome to xda! .... That's a great first post!
Sorry to not have any info to help you, but I hope you find what you are looking for and get this working how you want.
I agree that Supercurio is probably the most clued up on audio for these phones. But you probably already knew that since you mention Voodoo Sound (which is his work).
Good luck
Mike
Quake2 said:
Hi, I'm almost new here
Since this is my first post, I cannot post in the development section, I hope this do not cause problems.
A few days ago I got my first android phone and started to do some low-level development and I needed to record both the input from the headset mic and the internal mic at the same time. I searched a lot on the net and did not find anything useful for the Galaxy S (Vodafone european I9000), so I decided to add this feature to the wm8994 driver included in the samsung kernel source for the Galaxy S.
Since I've never worked with this kind of device, I do not know if this is the correct way to do it, but it seems to work great.
Basicly I've enabled both input at the same time and routed left adc channel output to left audio interface channel and right adc channe output to right audio interface channel. Everything else is on default settings (as configured by MAIN and SUB path, in fact I've just used the same code).
The code also adds a new enum entry for the capture path, called "DUAL", which now is after "MIC OFF", but its just an hack, I'll clean it up later. Using the command "amix" will dump all the mixer channel:
Code:
...
7 MIXER 0 0 0 1 rw ENUM Capture MIC Path { Main Mic=0, Hands Free Mic=1, BT Sco Mic=2, MIC OFF=3, Dual=4 }
...
It can be tested using the pcm_* and mixer_* routines taken from samsung's libaudio, you just need to call pcm_open without specifying PCM_MONO but just PCM_IN, since now both left and right channels will be populated. If you have access to Cyanogen Mod repository, just grab the arec.c source from there and remove the PCM_MONO flag. Beside this I suggest you to dump raw pcm audio and load it into something like Audacity, arec.c seems to produce a wrong riff header.
Now for the questions...
Any ideas on how to correctly setup the gain on both channels? Currently the gain of the headset mic is set to +15 dB on the input PGA and +0 dB on the adc channel while the gain of the internal mic is set to +10.5 dB on the input PGA and +0 dB on the adc channel. I also tried to use the same settings from Voodoo Sound high sensitivity path (with drc enabled), but no results so far... The default gain is far too low, I must talk very near to the headset mic.
Beside this, I've also noticed a strange behavior when recording from both mic. If they're very near, the audio recorded from the headset mic channel will be highly suppressed, if they're far apart, no suppression occurs. As far as I know, wm8994 do not perform noise cancellation on device, any clues on this? Anyway this is not a big deal, since the two microphones will be quite far during normal usage. By far the biggest problem is on the gain for the headset mic.
I hope someone might be interested on this extension to wm8994, this device is really powerful, it's a shame that samsung is using 1/10 of its power...
Attached to this post is the patch file, I've worked on the 2.6.35-12 (recently switched to -13) kernel from teamhacksung, you can get it on github (cannot post the link for the 8 post limit...), just apply the patch from the root kernel directory and rebuild the kernel image as usual.
Any help is highly appreciated
Thanks.
Bye!
EDIT: OPS I'm sorry but I forgot to mention that to enable dual mic recording, you have to activate its path of course through alsa_mixer, like this:
forgive me
Click to expand...
Click to collapse
@Quake2 : DO you have datasheet /pin diagram of wm8994
I would like to insert digital data on mic instead reading from analog input
I saw this on the net and might thought it could be useful for others...
Here's the Sony Ericsson Xperia X10 Schematic and Disassembly manual. After a year since of its released date we spotted on the net the download links of the file.
General 2G Network GSM 850 / 900 / 1800 / 1900
3G Network HSDPA 900 / 1700 / 2100
HSDPA 850 / 1900 / 2100 / 800 - X10a for Americas
Announced 2009, November
Status Released 2010, March
Size Dimensions 119 x 63 x 13 mm
Weight 135 g
Display Type TFT capacitive touchscreen, 65K colors
Size 480 x 854 pixels, 4.0 inches
- Scratch-resistant surface
- Accelerometer sensor for auto-rotate
- Proximity sensor for auto turn-off
- Timescape/Mediascape UI This repair manual includes the following files listed below:
Sony Ericsson Xperia X10 Service manual/Schematic Diagram
Disassembly and Reassembly Manual, Product Specification, Electrical parts & Parts list PCB board layout and Schematic diagram.
This may help on Sony Ericsson Xperia X10 Repair and Troubleshooting for the following problems like:
* LCD Display problem - Abnormal Display
* Touch Screen Problem - Touch Screen Not Working
* Power ON problem- Power On does not work
* Initial Failure problem - Hang, frozen and restart
* Not Charging Problem - Abnormal charging
* Sim Card problem - insert sim card error, sim card not detected or recognize
* Micophone Problem - No voice call sound transmit
* Speaker problem - buzzer speaker malfunction
* Bluetooth and WiFi problem -Bluetooth and Wifi operation failures
* Camera problem - Camera Function not working
* GSM network signal problem - No Signal on GSM network
* HSDPA network signal problem - No signal on WCDMA network
Sony Ericsson Xperia X10 service manuals, assembly - disassembly instructions, troubleshooting guide and schematics downloads
http://www.megaupload.com/?d=F3RMJLMK
Very cool and usefull ,thanks
aw man, finally! hoorah!
why am i so happy? because with this, and the component list, i can find suitable replacements for the speaker and earpiece!
no more quiet phonecalls!!!
I think we need a new hosting site because megaupload just got shutdown.
can you reupload
Sent from my XT862 using Tapatalk
Son of a *****! I hate our government sometimes... Has anyone successfully replaced their screen? This manual would have been great to have. I recently broke my screen. I just ordered a SGS2, but I would like to fix the screen on my X10 if possible to keep as a backup..
Doh, could have done with this before I replaced my screen and button board. Mind you if I'd have seen the inside first I might not have dared swap them!
Sent from my X10 using XDA App
Here guys, this will be of some use to you...
http://forum.xda-developers.com/showthread.php?t=989196
I hope i don't need this but anyway thanks
Can you put the file some where else please please
New Link
For those still looking for this file...enjoy its a nice video run through including the reassembly of the device
http://hotfile.com/dl/48411548/f6606ab/SE_X10i_Disassembly.rar.html
You can download whole service specs here, along with schematics, etc. Look carefuly, as some schematics are hidden in pdf file.
http://www.cpkb.org/wiki/Sony_Ericsson_Xperia_X10_service_manual
thanks for this link!!
saving for later
Cholek3 said:
You can download whole service specs here, along with schematics, etc. Look carefuly, as some schematics are hidden in pdf file.
http://www.cpkb.org/wiki/Sony_Ericsson_Xperia_X10_service_manual
Click to expand...
Click to collapse
Thanks, good source...
dawia said:
Thanks, good source...
Click to expand...
Click to collapse
Thank God I found this link...you guys are a life saver!!!
old link
Hey guys, does nayone still have the schematics of the xperia x10i?
All the links are dead
Hi all,
I've lost my watch, and am looking for an app to help me find it. Does this exist? I've seen plenty of the reverse but after a lot of searching haven't seen a "Find my watch" app that works with any watch. My watch is a Sony Smartwatch 3. Thanks for any help.
If it's still in bluetooth range and connected to your phone, install something like IFTTT on your phone and create an android wear recipe to send a notification to the watch. Give it a couple of minutes to sync, then you can keep sending that which will light the display momentarily and make it vibrate.
If it's not in bluetooth range, then it's lost until you find it again I'm afraid.
bradpitcher said:
Hi all,
I've lost my watch, and am looking for an app to help me find it. Does this exist? I've seen plenty of the reverse but after a lot of searching haven't seen a "Find my watch" app that works with any watch. My watch is a Sony Smartwatch 3. Thanks for any help.
Click to expand...
Click to collapse
Hey Brad, I hope you find your watch. If you do, there's an app that you may have seen called Pear... it just received an update today to let you set up notifications on your phone or tablet if you leave your watch behind. You can download from the Play Store here: https://play.google.com/store/apps/details?id=com.dconstructing.android.pear
I did find my watch
Thanks for the suggestion, that's a step in the right direction but not quite what I'm looking for.
Given the watch cannot make any noise, except the sound of vibrations. Locating it is hard if you lose it.
An app that would show a form of map of an area with the location does not exists and would probably be expensive. Of course it would not be an actual map, but a layout of space with a maker of the location on that. Just to give you an idea where to look.
But glad you found it.
Sent from my Nexus 10 using Tapatalk
Might not be what your looking for but i set something up in tasker that when i get disconnected from my watch, tasker switches my gps on, gets location and then stores that location.
I then get a notification on the phone with a map view of where i last had my watch.
It obviously won't help you find it behind the sofa etc but will help you narrow the search area, i.e work, gym, home car etc. And also if someone picks it up then your out of luck.
phil gpx said:
Might not be what your looking for but i set something up in tasker that when i get disconnected from my watch, tasker switches my gps on, gets location and then stores that location.
I then get a notification on the phone with a map view of where i last had my watch.
It obviously won't help you find it behind the sofa etc but will help you narrow the search area, i.e work, gym, home car etc. And also if someone picks it up then your out of luck.
Click to expand...
Click to collapse
That's a great idea. Thanks for sharing it.
I solved the problem by creating an trusted electronic leash with my watch via Tasker. In short, when the watch and phone are connected, the PIN on the phone is disabled. Immediately upon disconnection, the phone is PIN locked and an alarm rings. So, I know exactly where the phone is, it meets access security requirements, and I don't leave my watch too far behind as the phone alarm indicates that I left it just out of range. Here's the recipe:
Profile: LG G Watch R Connected (5)
State: BT Connected [ Name:G Watch R 0DA0 Address:* ]
Enter: Unlock phone (7)
A1: Secure Settings [ Configuration:Clear Password Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
Exit: Lock phone (8)
A1: Secure Settings [ Configuration:Set Pin Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
A2: Secure Settings [ Configuration:Lock Device Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
A3: Alarm Volume [ Level:7 Display: Off Sound: Off ]
A4: Music Play [ File:Ringtones/hangouts_incoming_call.ogg Start:0 Loop: Off Stream:4 ]
A5: Wait [ MS:0 Seconds:3 Minutes:0 Hours:0 Days:0 ]
A6: Music Play [ File:Ringtones/hangouts_incoming_call.ogg Start:0 Loop: Off Stream:4 ]
A7: Wait [ MS:0 Seconds:3 Minutes:0 Hours:0 Days:0 ]
A8: Music Play [ File:Ringtones/hangouts_incoming_call.ogg Start:0 Loop: Off Stream:4 ]
I purchased a headset that claims to support aptX, but I can't verify it's working. I've enabled it in OP5 settings, and also tried restarting the phone for good measure. The manual for the headset specifies that it supports aptX, and it doesn't list any special steps to enable.
Looking at logcat and btsnoop output it seems to be negotiating SBC. I've tried playing FLAC and MP3 files with VLC, and streaming over Google Play music and it does not negotiate aptX. Has anyone else been able to confirm that aptX is working on their OP5?
I followed this answer on stackexchange and got the btsnoop logs, analyzed with WireShark. This is what I came up with:
Code:
AVDTP 25 Rcvd ResponseAccept - GetCapabilities - Audio SBC (16000 32000 44100 48000 | Mono DualChannel Stereo JointStereo | block: 4 8 12 16 | subbands: 4 8 | allocation: SNR Loudness | bitpool: 2..53)
The headset is obviously responding with SBC, but does this definitively mean the headset is refusing to support aptX, or could it be an issue with the OP5?
I can post more of the btsnoop logs or logcat if necessary.
How would I confirm it? I see the "aptX HD" logo briefly flash on the screen whenever I start playing video or music after connecting to my LG HBS-730, but how would I know for sure? I mean it does sound better than the same media on my wife's Moto X Play.
Chahk said:
How would I confirm it? I see the "aptX HD" logo briefly flash on the screen whenever I start playing video or music after connecting to my LG HBS-730, but how would I know for sure? I mean it does sound better than the same media on my wife's Moto X Play.
Click to expand...
Click to collapse
If you run a logcat over adb while either connecting or playing the media (I'm not sure which) you should see some output about codec negotiation. That's probably the quickest and easiest way. The btsnoop method in the stackexchange I linked is more low level, but I was hoping to see conclusively if the device supports aptX
I've never seen an aptX logo you up on screen. Hopefully that's a reliable indicator, but I would think that would get annoying!
One more thing, my understanding is that aptX and aptX HD are two different things (someone correct me if I'm wrong), even if one is working I don't think that necessarily means the other is.
I'm probably going to return this headset if I can't prove that aptX is working for it...
Here is the screenshot.
And here's an exert from logcat while trying to play some tune via Google Play Music app:
Code:
08-17 17:39:43.734 2880 20308 D bt_btif : btif_snd_ctrl_cmd : A2DP_CTRL_CMD_START DONE
08-17 17:39:43.734 2880 2900 D bt_btif : btif_av_state_opened_handler event:BTIF_AV_START_STREAM_REQ_EVT flags 0 and index = 0
08-17 17:39:43.734 2880 2900 I bt_btif_media: btif_a2dp_encoder_init SCMS_T DISABLED
08-17 17:39:43.734 2880 2900 E bt_btif : bta_av_select_codec hdl = 65
08-17 17:39:43.734 2880 2900 I bt_btif_media: btif_a2dp_encoder_init Selected Codec aptX
08-17 17:39:43.734 2880 20306 D bt_btif : btif_media_thread_handle_cmd : 5 BTIF_MEDIA_SBC_ENC_INIT
08-17 17:39:43.734 2880 2912 D bt_btif : AV Sevent(0x41)=0x120b(AP_START) state=3(OPEN)
08-17 17:39:43.734 2880 20306 D bt_btif : btif_media_thread_handle_cmd: BTIF_MEDIA_SBC_ENC_INIT DONE
The "Selected Codec aptX" bit makes me think it's working. There are a lot of crappy knock-off headsets that boast aptX "support" that isn't working right because they omit the profiles necessary for it to actually work. I remember reading an article a while back about this very problem, but can't seem to find the link anymore.
Chahk said:
The "Selected Codec aptX" bit makes me think it's working. There are a lot of crappy knock-off headsets that boast aptX "support" that isn't working right because they omit the profiles necessary for it to actually work. I remember reading an article a while back about this very problem, but can't seem to find the link anymore.
Click to expand...
Click to collapse
Ok, that logcat looks like what I was expecting to see. I agree that yours is working. Thanks!
For the record, this one *is* some cheap Chinese one I found on Amazon. The sound quality is not awful for the price, but the false advertising is unforgivable.
I see aptX logo flashed on a screen after my Sennheiser HD1 got connected via Bluetooth. And I don't see that logo when using other BT headsets.