yashsingh1/xdaforums huggingface dataset:
[Nook Color General] bugeyed1:
Thanks for pointing out the app. Mine seems fine. It shows blue if not moving & green when I move. Really shows how hard it is to hold the finger still! It would be nice to know the size of the contact area. I mean, it would be nice if it showed the exact area that the finger is contacting the screen. Then you could see if it was off by a bit.

Thanks,

kev
[Nook Color General] Paul22000:
Is it plugged in / charging?
[Nook Color General] aaps:
Nope. Mine seems ok. I'm running HC.
[Nook Color General] dieselg5:
I tried getting adb to work through usb and while I was checking and unchecking debugging, the multi touch fixed itself. Idk why or how but it works perfectly in multitouch test now.

Sent from my Epic P.O.S.
[Captivate General] TonyStark R.I.P.:
Oh no competition for Galaxy phones

http://www.youtube.com/watch?v=u84-crSbZ0E&feature=uploademail
[Captivate General] thunderstar2500:
I saw stuff about Acer's new "ace", lol. I think it looks surprisingly good. I can remember reading stuff about it months ago and quickly disregarding it, but now I'm impressed.
[Captivate General] shust82:
Thats not a phone, Its a brick with a screen!

13.6mm thick, 185g does it come with a physio plan?
[Captivate General] TonyStark R.I.P.:
It's an Android on roids:D
[Captivate General] Dante04SRT:
We started with phones in bags that were huge.... then phones went small... then smaller.... until we finally had to make fun of ourselves......

http://www.youtube.com/watch?v=ZWTaS-GaBmA

Now they're getting bigger... and bigger....and bigger.... pretty soon they're gonna start putting strap loops on the damn things...
[Windows Mobile Development and Hacking General] michaelmalak:
I have a Psion Workabout Pro3 running Windows Mobile 6. The Device Name under Start->Settings->System->About->Device ID->Device name is the default "WORKABOUTPRO". However, when I connect via WiFi to my wireless router, the wireless router's DHCP table lists a blank name for the IP address assigned to the Workabout even though it correctly lists the Windows computer names for all the desktops, laptops, and smartphones connected to the router (whether wired or wireless).

Why isn't the Workabout's Device name showing up on the router's DHCP table?
[EVO 4G Q&A, Help & Troubleshooting] twiz0r:
so I bought widgetlocker today and it downloads and that's it. Doesn't try to install. Any ideas?

Swyped from my cyanogenized and gingerbreaded EVO
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
You can clear your market cache and try to re-download it.
[EVO 4G Q&A, Help & Troubleshooting] Sulten:
How do you clear the Market Cache?
[EVO 4G Q&A, Help & Troubleshooting] CCallahan:
First, go to Settings - Applications - Market and check the cache amount. It may let you clear from there. If not, maybe try downloading "Market History Manager" and see if that helps.

If none of that works, send a PM to the developer of Widgetlocker with your issue.
[HD2 Android Q&A, Help & Troubleshooting and Genera] cobhc:
http://xdaforums.com/showthread.php?p=11379272

Go devs go!
[Galaxy 3 Themes and Apps] barqers:
I found a thread with an awesome way to create amazing text icons.

The creator just added a way to center your text by typing (center) without brackets in the x and y coordinate boxes.

Check it out, I'm in the process of customizing my phone's icons while waiting for Lestatious 1.1 to be released!

http://xdaforums.com/showthread.php?t=868627
[Galaxy 3 Themes and Apps] osbozzy:
osbozzy, you do not have permission to access this page. This could be due to one of several reasons:

1. Please Read: New members (those with fewer than 10 posts) are not permitted to post to development-related forums. The developer forums are intended for experienced users and developers to discuss ways to improve technical aspects related to ROMs and Software. While you may be an expert, we ask ALL users to avoid posting questions about using or installing ROMs and software in the Development Forums. To encourage this new Users can read but not post in these forums.

To ask Questions about developing your device, installing ROMs, software and themes you must go to the Q&A or General Forum.

Remember, your question has very likely been asked already, so please search before posting.

2. Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?

3. If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Can u pls copy-paste teh contents ..
[Galaxy 3 Themes and Apps] barqers:
Ooops!

I posted the wrong link.

Fixed it, try now. Sorry!!!
[Captivate General] mnjm9b:
With every fifth post being some sort of claim about the release of froyo for captivate, How will we ever know when it happens for real?

So if you were to stumble across the real release, How would you title your thread????

Lol. This ought to be good...
[Captivate General] sujesharukil:
If it becomes official

1. At &t will announce it.

2. Every android site would announce it.

3. This forum will go nuts with everyone putting [official] in the title.

4. Custom ROM users would be laughing at the quality of it.

:-)

But till then keep the dream alive.... I like your optimism.
[Captivate General] javi80:
Where's my Gingerbread!!!
[Captivate General] eelall:
Something along the lines of hell freezing over....
[Captivate General] zizzerboy:
My title would start with [yawn] :)
[Captivate General] Miami_Son:
If it happens before St. Patrick's Day, I would expect the title to also have news of Mikey Mike's heart attack.:D
[Captivate General] boborone:
Speaking of that, what happened to your signature, no more patrick's day betting?
[Captivate General] Battlehymn:
Well, I for one, could care less if/when they release it ... I think the devs around here can use some portions of it to further improve the ROMs we're seeing. I'm sure that there are quite a few people who have cappys, and don't even know what XDA Developers is, that should be very excited should it ever be released.

I'm on Andromeda 2.1 with the Speedmod K13 kernel and everything is great.

But to answer the question as to how we'll know when it's out? ... Your Mom will have it on her phone.
[Captivate General] Johnnie5000:
I predict AT&T will announce their official plans for froyo and eventually gingerbread for the captivate on April 1st.
[Captivate General] agh1701:
I would troll it like this

"Attention folks wanting Froyo from ATT"
[Captivate General] boborone:
Hahaha great
[Captivate General] RaneMan:
I would title it...."they served me yogurt when I asked for a cookie!"

********

Sent from my Samsung Captivate using the XDA app

ROM: Paragon RC5.1 1200 mhz/100hz kernel
[Captivate General] MastaBetta:
I stopped caring about an official froyo release the day I learned to flash roms on my cappy.
[Captivate General] javi80:
"Hey Samsung why u no froyo teh captivate till now yo? Why no gingerbread heh?
[Captivate General] shiftylock:
The day we get Froyo.... is the day they make an LG Env with froyo for all the preteen girls who want to text their BFF Jill without needing a lagfix. We're such a low percentage of the customer base.

4/5 captivate owners I know don't even know what froyo is.

Getting it out there isn't quite a main concern of AT&T right now, what with their unveiling of newer, shinier Pantech phones with lower specs than the ones before it. T_T
[Captivate General] MikeyMike01:
:confused:
[Captivate General] DStan:
Yeah, most of the people that really want Froyo just flash their phones. Why would AT&T/Samsung bother paying someone to make a working build when their customers will do it for free? The only reason AT&T will release Froyo and Gingerbread updates would be to prevent their customers from using tethering and AP for free. Speaking of which, I need to donate to Team Komin ;)
[Captivate General] mnjm9b:
Let's stay on topic here....

This is a serious thread... lol
[Captivate General] snaai8:
The day that froyo releases somebody will start a thread with the name:

It's Finally here! Froyo has arrived [Official]

And then all the trolls will spam the thread with their WE WANT GINGERBREAD trolling. So I guess it's the day the world explodes..
[Captivate General] majortool:
Something like "Holy crap, Froyo is out for cappys. No really, it is, seriously, not a joke, look for yourself. Ah forget it"
[Captivate General] maxjivi05:
Who cares if att releases froyo.. it wont be better then the devs roms .. I much rather have the roms currently out then waiting for att to release one then wait for the devs to make it worth using by that time gingerbread should be out and ready to go
[Captivate General] cappysw10:
i'm still sticking with St. Patrick's Day (said so since day one). It was a good round figure around the end of Q1. :D
[Captivate General] alphadog00:
We will know because there will be 10 new threads per hour in the Dev section saying "official froyo released"

This will be followed by 10 new threads: "OTA update not working for me" in the Dev section as well.
[Captivate General] bames:
goog point but their won't be an OTA

so it will be along the lines of "Kies update won't process" or "Kies update bricked my phone".

=)
[Captivate General] alphadog00:
I know there won't be an OTA, but that won't stop 100 newbies from trying and then posting in the Dev section that it isn't working. :)
[Captivate General] jcabibi:
It would be titled... "Samsungjohn is a D-BAG!" :mad:
[Captivate General] mnjm9b:
Let's not turn this into a flame thread.... this is supposed to be funny.
[Captivate General] javi80:
fyi if you google samsung john or samsungjohn, the results are pretty interesting...
[Captivate General] Miami_Son:
You're the guy I was referring to about the heart attack. Got you mixed up with Mikey Mike.;)
[Captivate General] jcabibi:
Very interesting... I hope the Official 2.2 release doesn't have Sri Lankan porn for a boot animation :p
[Captivate General] jgr208:
He is probably one of those guys that use the same username for everything :p
[Captivate General] boborone:
:oOIC:eek:
[Android Software/Hacking General [Developers Only]] mikereidis:
Devices

Devices

List of devices and FM chips. At this time I'd like to limit this to Android devices, but might consider others.

Would be useful to list limitations here. For example, some Motorola Droid owners were understandably disheartened,

after much work, to find they had no Fm Rx antenna connection, and could not make one without opening up the cans, etc.

on the board. So technically they had Fm Rx, practically, they had none.

Also, some boards may have no Tx antenna, but might possibly work within a few inches of an external FM receiver antenna.

--------------------------------------------------------------------------------

TI FM devices:

--------------------------------------------------------------------------------

HTC Legend: WL1273

HTC Tattoo/Click WL1271?

HTC Dream/Google G1 WL1271?

HTC Sapphire/Hero BRF6300 = WL1271?

HTC Diamond/Raphael/Blackstone BRF6350 (Windows Mobile?)

Motorola Droid WL1271

Motorola Backflip WL1271?

Motorola Milestone WL1273?

Nokia N900 WL1273? (Maemo?)

Barnes & Noble Nook Color WL1273?

--------------------------------------------------------------------------------

Broadcom FM devices:

--------------------------------------------------------------------------------

HTC Nexus One: 43xx

--------------------------------------------------------------------------------
[Android Software/Hacking General [Developers Only]] mikereidis:
FM Apps and APIs

FM Apps and APIs

Many handset manufacturers provide their own proprietary FM radio apps. Some people have managed to get an

FM radio app meant for another device working on theirs. Most, however, have library or other issues with a foreign app.

AFAICT, Google has not released any sanctioned FM radio API, nor do they intend to. I'd guess FM radio likely

won't bring much revenue to Google or the carriers.

In an ideal world, Android apps would use the same API as on Linux: the "Video For Linux version Two" aka V4L2.

This API makes use of a /dev/radioX device. This is somewhat similar to the /dev/videoX devices that some devices

appear to support for cameras.

If the V4L2 API was available on Android, Android FM radio apps could then be ported more easily from Linux.

Alas, there are relatively few Linux radio apps. GnomeRadio hasn't been touched in over 2 years and Gnome

doesn't run on Android anyway of course. Some command line apps could be ported, but that doesn't make for

an Android app.

So thus far, the defacto "API" for FM radio on Android has been vendor specific commands over HCI, the

Bluetooth interface. This is more or less similar to the way it can be done via I2C, but apparently

most FM chips are not wired via 12C; they use the existing HCI UART. Once again, FM radio is the

poor neglected "step-child".

One advantage of using HCI is that no new kernel drivers are needed. A disadvantage is that some mediation

driver would be required to use bluetooth and FM at the same time; the only alternative being drivers for

both smashed together, but that would be an Android specific hack and is not a good idea.

I've noted that one individual created an API spec and an app for Windows devices a few years back.

I believe it was called GFMRadio and XFMRadio or similar. That project was apparently abandoned.

MIUI released a GPL licensed FM app for some phones based on broadcom chips; HTC Desire and Nexus One.

The source code contains the string "/dev/radio", but AFAICT it doesn't appear to actually use V4L API.

It speaks directly to the broadcom FM chip via HCI.

Since MIUI source is GPL and available it could be used as a base for a TI, or TI and broadcom specific app.

In theory patches could be submitted to MIUI but I'm not sure they are open to that and the language barrier

from English to Chinese and back may be difficult.

Some interesting posts on MIUI here: http://xdaforums.com/showthread.php?t=837691

http://www.miui.com/thread-1687-1-1.html

Using hcitool commands, or similar, one could write a radio app in bash or Perl etc. LOL.

TI has an "fmapp" command line testing utility that relies on libfm_stack.so .

This app won't run on my Legend because it depends on snd_ctl_* APIs in libaudio.

"strings libfm_stack.so" produces lots of interesting detail and embedded BTS scripts.

The source code I've found for TI fmapp, and it's FM stack library does not seem to have all

the functionality I've seen in the binary fmapp I found. So they may have stripped much code

for the publicly released source code.
[Android Software/Hacking General [Developers Only]] mikereidis:
Audio routing

Audio routing

On HTC phones, FM analog audio routing can be achieved by:

# Default

adb shell 'echo "disable" > /sys/class/htc_accessory/fm/flag'

# Headset

adb shell 'echo "fm_headset" > /sys/class/htc_accessory/fm/flag'

# Speaker

adb shell 'echo "fm_speaker" > /sys/class/htc_accessory/fm/flag'

# View

adb shell cat /sys/class/htc_accessory/fm/flag
[Android Software/Hacking General [Developers Only]] mikereidis:
Firmware, TI BTS file, HCI and I2S/I2C issues, tools etc.

Firmware, TI BTS file, HCI and I2S/I2C issues, tools etc.

The Nokia V4L driver loads radio-wl1273-fw.bin, although the code does indicate it may not be necessary.

I can't find this firmware file anywhere. As with many other firmwares, it may simply be a known firmware

file renamed. This has been noted with other firmware files for the TI radio.

Information on firmware for these TI chips seems scattered and incomplete. Same with the BTS Bluetooth script files

which are usually important for accessing the FM functionality.

I think one of the reasons for this lack of information is that most parties do not want us messing with the available functionality.

- Device manufacturers do not want their devices used in violation of FCC or other regulatory body rules.

For example, FM transmission at higher power levels or improper frequencies. Also RDS transmissions with bogus data.

- Device manufacturers and carriers want us to buy newer or more expensive products for additional functionality.

They also would rather we use voice minutes instead of FM "walkie talkies".

- Google and carriers want us to stream music via data rather than pick it up for free from over the air.

...

Where do I find utilities to dump/decode/encode BTS files ?

....

HCI is usually used to access FM functions, but I2C might be usable on some devices.

...

fm_rx_init_6350.1.bts

fm_rx_init_6350.2.bts

fm_rx_init_6450.1.bts

fm_tx_init_6450.1.bts

fmc_init_6350.1.bts

fmc_init_6350.2.bts

fmc_init_6450.1.bts

tiinit_0.0.0.bts

tiinit_5.2.34.bts

tiinit_5.3.53.bts

tiinit_6.1.24.bts

tiinit_6.2.31.bts
[Android Software/Hacking General [Developers Only]] mikereidis:
HCI/I2C Commands

HCI/I2C Commands

Most of this information is gleaned from:

- The Linux WL1271 FM Radio source code written by a Nokia employee.

- TI source code for fmapp/fmstack, etc.

Various forum posts also make it clear there is a bewildering array of commands etc. not referenced in the source codes above.

Some information can also be retrieved by looking inside BTS, firmware, app, utility and library etc. files.

...

Vendor Specific Opcodes for the various FM-related commands over HCI. (_FmcCoreTransportFmCOmmands)

_FMC_CMD_I2C_FM_READ	0x0133

_FMC_CMD_FM_I2C_FM_READ_HW_REG	0x0134

_FMC_CMD_I2C_FM_WRITE	0x0135

?0x136

_FMC_CMD_FM_POWER_MODE	0x0137

?0x138

_FMC_CMD_FM_SET_AUDIO_PATH	0x0139

_FMC_CMD_FM_CHANGE_I2C_ADDR	0x013A

Format of an HCI READ/WRITE command to FM over I2C is:

HCI Header:

- HCI Packet Type:	(Added internally by the HCI Transport Layer)

- HCI Opcode:	2 bytes (LSB, MSB - LE)

- HCI Parameters Total Len:	1 byte (total length of all subsequent fields)

HCI Parameters:

- FM Opcode:	1 byte

- FM Parameters Len:	2 bytes (LSB, MSB - LE)

- FM Cmd Parameter Value:	N bytes

For "simple" (non-RDS) read commands "FM Parameters Len" is always "2, 0" (2).

...
[Android Software/Hacking General [Developers Only]] mikereidis:
FM Receiver script

---null set---
[Android Software/Hacking General [Developers Only]] mikereidis:
FM Transmitter script

---null set---
[Android Software/Hacking General [Developers Only]] qzem:
I think you are doing an awsome job and I really hope that you'll succeded. But the reason why I'm writing this post is to get this thread on the first page again for a while, so maybe more developers will see it, and can contribute :)!

Good luck!

EDIT: Perhaps it just needs more outstandig title, maybe Unviersal FM radio for android devices with TI WL chips, or something that would get people to read it.
[Android Software/Hacking General [Developers Only]] mikereidis:
:) It's already off the first page, LOL.

My plan has been to post a link to this thread in the various existing threads for different devices using the TI FM chips. I'm sure that will get this thread some notice. I think a lot of devs and dev types stick to the forums for their devices and don't look at this general section.

At least there are so many potentially matching keywords in the first 10 posts that google searches on the subject are likely to link here.

I agonized over the thread title name for some time and "TI FM Radio" is best description I could think of, technically at least. I don't know if I can rename the thread, but it might help to put the names of popular devices with TI chips in the title.

As I posted on the Legend thread, I now have an App Inventor app up and running with functionality to tune, scan, change volume and see signal strength. The audio routing is the last major piece of the puzzle, but it may be different on different devices.

I'll spend a few more days at most to try and get audio routing working, and then, whether working or not, I'll post in a few threads looking for further info and people who want to try the app I'm building.

Would be nice to see the RDS and transmitter working soon too.
[Android Software/Hacking General [Developers Only]] hwertz:
Regarding merging the bluetooth and FM drivers, TI's solution appears to be what they call a shared transport line discipline driver. The way this should work, each driver has what appears to it to be dedicated access to it's respective core, and the line discipline driver takes care of any queueing or delaying of commands & such that has to happen to keep them from stepping on each others toes.

Oh, and "IP" is "Intellectual Property" in this case. So the core, generally you'd say the WL127x has a wifi core, bluetooth core, etc. and 128x has a gps core as well. An IP core uses a description language (it used to be VHDL) to describe the layout of the core, so for instance if a company wants to build wifi onto their own chip, they can buy use of the IP core from TI instead of having to buy a phyiscal chip and interface to it.

I've got a debian install wedged onto my Droid 2 Global, I'm going to look into the "ti-st" V4L2 FM drivers, and see if I can get a module that will insert. The kernel can't be replaced on D2G yet, but as far as I know if I get a 2.6.32.9 kernel tree, and get ti-st driver to compile under it, I don't see why it shouldn't insert as a module just fine. Also, I'll look REAL closely to see if I can discern how it gets audio out, so I might have an hcitool command or two to add if that pans out.
[Android Software/Hacking General [Developers Only]] mikereidis:
Thanks for the info hwertz .

OK I understand "IP" now; never heard it used in that way to designate blocks on a chip.

Yes I read something about the line discipline. Some block diagrams: http://omappedia.org/wiki/Wilink_ST

If you know of any HCI commands dealing with audio routing, please post or pm whatever info you can share.

So I'd guess your opinion is that the v4l2 api is the best route to support FM radios on Android ? That was among my first thoughts until I saw that there is currently virtually no such support on any Android ROM I've heard of. HCI seems to work fine, but it requires chip specific commands of course.

Clearly though, at least Nokia and TI both are working on efforts to bring V4L2 apis for the TI chip in the embedded linux or Android environments.

I'm not sure how audio routing would be configured on Android when using v4l2 apis. The PC environment requires moving digital data from source to destination. But SOC devices often can move digital or analog data directly and without software support.
[Android Software/Hacking General [Developers Only]] Lipton1:
FM Transmitting Radius

So I hope this question is not too basic for this forum, but I'm new to it and wonder how large the FM transmitting radius of such a chip might be. I basically just need to get an idea, but of course I'd also be thankful if you can refer me to all sorts of literature, specs, overviews, etc.

Thanks!
[Android Software/Hacking General [Developers Only]] mikereidis:
This thread is over 2 years old now. The original purpose was to try and find others interested in sharing the undocumented secrets of TI's FM chip.

But after my info dump, nobody showed up to share with me, and likely nobody will, so I will close it after this post.

Any further discussion about FM can move to the Spirit FM thread in my sig.

These chips put out tiny amounts of power in transmit mode, maybe 10-30 milliwatts or so. The only phones I have that transmit have to have their headset cable antenna wrapped around the receiver antenna to get anything resembling decent quality.

So I'd call the transmit radius a few centimetres at most. Little wonder then, perhaps, why so few Android devices support transmit.