yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Q&A, Help & Troubleshooting] jonnybueno:
This looks like a modified screenshot...

The issue with this is that 3rd party apps sometimes use their own resources for notifications text. You'd have many apps where the text is visible but anything that uses black text would be invisible

It looks like you modified a screenshot in this one as well. If someone can spend some time digging around through source to find a xml file to hexedit, then I know how to change "textAppearance". I'm really not sure if this is something deeper than that though.

Good suggestions, but there are some limitations to overcome. I'm open to improving things and your ideas are definitely things that I have already considered but I am only one guy with a ****ty laptop and a baby. After I finish graphics, I can look into hacking some of the resources to achieve the desired effects but without help from you guys its not likely that I'll find the time to do so.

We must find a balance between functionality and aesthetics... I don't like putting stuff out that only works sometimes.

Edit: BTW, you can view source for AOSP here: http://github.com/android

You can't view source for Sense
[Droid Incredible Q&A, Help & Troubleshooting] djkms:
Yeah all I did was modify screenshots. I have no idea how to code anything but I am pretty knowledgeable when it comes to graphic design, let me see if I can help you in any way...
[Droid Incredible Q&A, Help & Troubleshooting] jonnybueno:
More on editing the text for the menu...

From AOSP:

<!-- Panel attributes -->
<item name="panelBackground">@android:drawable/menu_background</item>
<item name="panelFullBackground">@android:drawable/menu_background_fill_parent_width</item>
<item name="panelColorBackground">#fff</item>
<item name="panelColorForeground">?android:attr/textColorPrimaryInverse</item>
<item name="panelTextAppearance">?android:attr/textAppearanceInverse</item>

from: http://github.com/android/platform_frameworks_base/blob/master/core/res/res/values/themes.xml

I'm no developer, but from my experience(i have compiled apks from existing source in eclipse) the values dir is not accessible after the fact. I'm really not aware of what actually happens with this, but it is most likely a smali edit to change this. That's our major hurdle, as I have absolutely no java knowledge (have owned a computer for about two years now) and doing smali edits without very specific instructions is difficult for me.
[Droid Incredible Q&A, Help & Troubleshooting] djkms:
I just unzipped the apks to poke around a bit and WOW! There are a lot of xml files involved. I have edited xml files for websites and such (joomla if your familiar). The problem I faced when editing xml is that changing a property in one place could potentially break attributes in another. I dont know if the same would hold true with the android platform but I would imagine so.

When I get some free time I will do a little research and see if I can help out.

Edit: in the com.htc.resources there are 1,367 png files in just that 1 apk, you have really put a lot of work into these themes!
[Droid Incredible Q&A, Help & Troubleshooting] jonnybueno:
I think this xml file actually becomes hard coded into java after being compiled... i could be very wrong as I am a super novice noob lame-o wanna-be developer type, but prior to compiling, dir is there, after compiling, poof! gone. It would actually be super easy and quick for me to hexedit the xml if it was possible

public static final int textAppearanceInverse
Since: API Level 1

Default appearance of text against an inverted background: color, typeface, size, and style.

Must be a reference to another resource, in the form "@[+][package:]type:name" or to a theme attribute in the form "?[package:][type:]name".
Constant Value: 16842805 (0x01010035)

would simply become

public static final int textAppearance
Since: API Level 1

Default appearance of text: color, typeface, size, and style.

Must be a reference to another resource, in the form "@[+][package:]type:name" or to a theme attribute in the form "?[package:][type:]name".
Constant Value: 16842804 (0x01010034)

Literally just change one number
[Droid Incredible Q&A, Help & Troubleshooting] djkms:
Ok I found this:

http://www.droidforums.net/forum/jrummy/52130-notification-font-colors.html

Reading up on it now to see if it helps us in anyway
[Droid Incredible Q&A, Help & Troubleshooting] ilinfinityil:
hey johnny did you get the PM i sent you?
[Droid Incredible Themes and Apps] mickskillz:
Could somebody post the vanilla calendar.apk.... Or any other one besides the stock sense calendar. Thanks in advance
[Droid Incredible Themes and Apps] jdkoreclipse:
Im currently working on a 2.2 rom that has a little bit of everything in it...including the calender.
[Droid Incredible Themes and Apps] mickskillz:
could you please post just the new calendar .apk? thanks
[Vibrant Themes and Apps] LatinSilEighty:
After making a shortcut to Maps with Better Cut, i try and click on the Icon and it sais "application is not installed on your phone" but if i open the app drawer and click on the actual Maps icon it works just fine... anyone having this problem?
[Vibrant Themes and Apps] joe.kerwin:
I use bettercut, works just fine for me. I add through the "add" menu though, as if I was adding a widget. If i open the app and hit new shortcut it doesn't recognize my launcher (adw).

if you use touchwiz, place the stock maps shortcut on your phone, open bettercut, and choose edit shortcut, see if that works.
[Vibrant Themes and Apps] LatinSilEighty:
every other icon is working fine other than the map one i tired on adw lp and touchwiz and it doesn't work on any of them :(
[Vibrant Themes and Apps] joe.kerwin:
Didn't have a maps shortcut but I literally just did menu > add > shortcuts > bettercut > activity > google maps. Changed the icon and saved it, worked just fine. Maybe the icon back? Uninstall and reinstall bettercut?
[Vibrant Themes and Apps] AndroidZ28:
Did you make the icon before updating google maps. I have to re-add my google voice icon to launcher pro's dock every time I update it.
[Vibrant Themes and Apps] CapnChronic:
Im having the same issue with the map shortcut, but only in launcher pro, not touchwiz. It works in the dock but not the home screen. Tried joe's method to add but still no luck.
[Vibrant Themes and Apps] LatinSilEighty:
yeah i tried uninstalling and installing bettercut and still a no go :(
[General Topics] dosesdoyle:
http://www.mediafire.com/?v76qz6ajw8db083

Go nuts!
[EVO 4G Themes and Apps] norkoastal:
So I'm looking at the wiimote I just bought and see not only the perfect emulator controller, but also as a perfect companion in the car to act as a remote to scroll music and adjust volume.. are there any aps out there that give the wiimote a cursor to scroll around with and select things with? $10 donation pending for a similar app that can controll mixzing from the wiimote with customizable functions.

Thanks!
[Droid Incredible General] Garrett07:
Is it a leak still? And if so are they releasing official radio 2.x with the ota froyo?
[Droid Incredible General] jdkoreclipse:
They would have to release the radio. And it.is.still a.leak
[Droid Incredible General] Garrett07:
Ok so are they going to build in the 2 ota's together on the "august 6th" release?
[Droid Incredible General] jdkoreclipse:
That would be the most logocal thing to do, but i am not vzw or htc.

If the leak needs the 2.x radio to use 720p then i would say that whey would put it all together.

Btw. The evo is getting it on august third, so i would think we would be getting it pretty soom.
[Droid Incredible General] Garrett07:
Yeah but i don't see the point of the 2.x radio updates, unless it was put in place to update the kernal but thats not really necessary and the "august 6th" was the so called release by our vzw rep at best buy
[Droid Incredible General] jdkoreclipse:
The radio was for the 720p...and for better reception
[Windows Mobile Apps and Games] ChromJ:
I searched and found one thread that explains how to get the phone profile to automatically change to vibrate during meetings by changing the setting in the settings in "Sound&Display" from nomrmal to Auto which was already very useful to me and I did not knew about it before the search

However, I hate the vibrator and I want the ringer to mute completely, no ring and no vibrator. I can see the screen light.

Is there any way to do that weather with the system or with separate application

my best regards
[Captivate Android Development] for_ap1:
In my Captivate I noticed a kernel module with name Si4709_driver.ko

Si4709 is a FM radio receiver www .silabs. com /products/audiovideo/fmreceivers/Pages/Si470809.aspx (sorry, I can't post URL)

By default it is not loaded, but when I tried to load it, it did. Now we need to know what API is used for user mode programs.

It would also help if those who put i9000 ROM into Captivate (but have stock kernel) tried load module and then run FM radio app.

# cd /lib

# ls

modules

# cd modules

# ls

dpram.ko

rfs_glue.ko

j4fs.ko

multipdp.ko

param.ko

vibrator.ko

Si4709_driver.ko

dhd.ko

rfs_fat.ko

stgloc

s3c_bc.ko

pvrsrvkm.ko

scsi_wait_scan.ko

fsr.ko

drop_caches.ko

fsr_stl.ko

s3c_lcd.ko

# insmod /lib/modules/Si4709_driver.ko

# lsmod

Si4709_driver 15744 0 - Live 0xbf195000

vibrator 6744 2 - Live 0xbf191000

s3c_bc 2880 0 - Live 0xbf18b000

s3c_lcd 5060 0 - Live 0xbf184000

pvrsrvkm 205996 48 s3c_bc,s3c_lcd, Live 0xbf14c000

multipdp 30968 1 - Live 0xbf13f000

dpram 194152 10 multipdp, Live 0xbf10a000

param 10132 0 - Live 0xbf105000 (P)

j4fs 65604 1 - Live 0xbf0ef000 (P)

rfs_fat 235456 5 - Live 0xbf0b0000 (P)

rfs_glue 74328 1 rfs_fat, Live 0xbf098000 (P)

fsr_stl 248012 6 j4fs, Live 0xbf056000 (P)

fsr 328428 3 dpram,fsr_stl, Live 0xbf000000 (P)

#
[Captivate Android Development] THATTON:
Nice find. This may turn into something. :)
[Captivate Android Development] dalingrin:
With the module loaded the FM radio app no longer has the error 'Unable to turn on FM radio." However, the FM app has no sound and cannot seek for channels.
[Captivate Android Development] decepticon:
Looks like the hardware may be there after all, you were using the headphones right? If so then maybe the antenna isn't wired to the headset port.
[Captivate Android Development] for_ap1:
Another note: Its is possible that hardware is not there. I found another tool that seems to test FM Radio

# ./si4709_test -h

How to control FM Radio (Si4709) .........

================================================================

Usage: ./si4709_test [controls] [value]

-p power, up|down	si4709 power control

-s search, up|down|auto	seek channel

-rstate,	show si4709 radio state

-rssi,	show si4709 rssi status

-r, on|off	RDS/RBDS Enable/Disable

-rds,	show Show RDS/RBDS data

e.g) si4709_test -p (up/down)

================================================================

# ./si4709_test -p up

# ./si4709_test -rstate

[FM RADIO] Radio State

================================================================

Power State = 0

Seek State = 0

================================================================

I tried to do the same on my wife's I9000 and it reported "Power State = 1"

So we may be out of luck with Captivate.
[Captivate Android Development] decepticon:
Not judging anyone but why worry about an FM radio when we have apps that do it all, about 4 of my local stations are on iheartradio and another 20 are from immediate areas around me.

When I used FM on my Nokia it was a battery drain more so than 3G.
[Captivate Android Development] for_ap1:
I tied to run test with headphones connected. Attempt to power up device results in reboot.

Below is kernel log related to loading driver and connecting headphones:

<7>[ 197.626426] device: 'fmradio': device_add

<7>[ 197.628218] PM: Adding info for No Bus:fmradio

<7>[ 197.635228] bus: 'i2c': add driver Si4709_driver

<7>[ 197.665086] i2c-adapter i2c-8: NAK from device addr 0x10 msg #0

<6>[ 204.231953] [ JACK_DRIVER (jack_type_detect_change,404) ] 3 pole headset or TV-out attatched : adc = 46

I also noticed that after I load driver, I see device file called /dev/fmradio. It disappers when I unload driver. It looks like /dev/fmradio is a control device for radio chip (i found string /dev/fmradio inside si4709_test tool).
[Captivate Android Development] zerosource:
oh noes! I want the fm radio function. :cry:
[Captivate Android Development] decepticon:
Any way to compare pics of the Captivate mainboard with a Galaxy S? In the general Captivate forum there are pics of the board. Compare chip numbers and see if there are any unmatching chips.

lol I can see the use for it in a natural disaster, during Katrina the radio was all we really had but all the good channels were on the AM side.
[Captivate Android Development] for_ap1:
I looked at these photos and also at photos from FCC site, but resolution is too low to read chip markings. FM chip is very small in size, so it is really hard to find it.

It seems that receiver talks via I2S bus and also needs few GPIO lines to work. If I understand correctly, I2S bus has no explicit acknowledgment, so driver might not now that device is not present on the bus. I couldn't find detailed application notes for the chip, just brief description is available. I need to look at driver sources to understand how it works. Hopefully Samsung releases it.
[Captivate Android Development] cesierra:
Will Samsung or AT&T tell us if there is an FM chip in there or not?
[Captivate Android Development] behrouz:
Maybe a brave soul, will tear the phone apart and finally give us a straight answer :D

wont be me though :p
[Captivate Android Development] immer:
In the source code for the captivate, there's is a folder called fm_si4709 containing many files pertaining to that radio. Perhaps someone astute w/ kernel stuff could work the magic and enable the HW if it is there...
[Captivate Android Development] for_ap1:
Well, I looked at sources of the driver (i9000 and I897 are the same). It does not do anything with hardware on driver init. So successfully loaded driver does not mean that hardware is present. I need to find a way to compile driver with debug mode on. Another option will be to build a tool that probes I2C bus (i2cdump and i2cdetect) from shell.
[Captivate Android Development] for_ap1:
Ok, I was able to build modules using Samsung sources and toolchain from Sourcery. I do not know if I can use it with stock kernel though. Will try to play with it, if I have spare time on weekend.
[Captivate Android Development] ctalbot:
I just built the kernel using the sourcery toolchain: http://www.codesourcery.com/sgpp/lite/arm/portal/release1033

I enabled the debug flag for the FM radio driver (uncomment #define Si4709_DEBUG in kernel/modules/fm_si4709/Si4709_common.h)

I did an insmod of the compiled module (Si4709_driver.ko). Note the last few lines from dmesg (i2c_read failed & Si4709_dev_init failed) . Doesn't look promising.

<2>[277139.763458] --------Si4709_driver_init called

<7>[277139.766871] device: 'fmradio': device_add

<7>[277139.768313] PM: Adding info for No Bus:fmradio

<2>[277139.774798] --------Si4709_driver_init request_irq success 192

<2>[277139.779520] --------Si4709 i2c driver Si4709_i2c_driver_init called

<7>[277139.785779] bus: 'i2c': add driver Si4709_driver

<4>[277139.799406] ----- si4709_i2c_probe 94

<7>[277139.801782] device: '8-0010': device_add

<7>[277139.801979] bus: 'i2c': add device 8-0010

<7>[277139.802269] PM: Adding info for i2c:8-0010

<7>[277139.802442] driver: '8-0010': driver_bound: bound to device 'Si4709_driver'

<2>[277139.802555] --------Si4709 i2c driver Si4709_probe called

<2>[277139.807314] --------Si4709_dev_init called

<7>[277139.847935] i2c-adapter i2c-8: NAK from device addr 0x10 msg #0

<2>[277139.848866] --------i2c_read failed

<2>[277139.851148] --------Si4709_dev_init call over

<2>[277139.855568] --------Si4709_dev_init failed

<2>[277139.859757] --------Si4709_driver_init successful
[Captivate Android Development] YellowGTO:
Damn that sucks :-(. Wish we knew what the chip looked like so we could just see if its on the phone.
[Captivate Android Development] zerosource:
why would they put the drivers in, if there is no chip? This is just a hope.
[Captivate Android Development] danr238:
I was think the same thing. I don't know much about kernel building but I would imagine if I was the guy at Samsung making it I wouldn't add sh!t that was useless
[Captivate Android Development] dalingrin:
They didn't add a potentially useless driver, they just didn't remove it. Big difference :)
[Captivate Android Development] sevenvt:
The same could be said for whatever manufacturing process that was used to differentiate the multiple galaxy s models. Is the fm chip worth another production line or would it be cheaper given the provider who doesn't care to offer the perk, to not ship thousands of boards with an extra but of tech attached to it. Most US model galaxy s dont have fm radio. There could definitely be left over drivers... Then again... Are there always useless drivers sitting on these phones? They didn't install everything from the euro versions do that gives me hope of us having fm someday.
[Captivate Android Development] shaneaus:
I PM'd someone who works for BroadCom and he stated that he couldn't see why they would use a different chip in the US SGS variants.

The GPS/FM/BT is all on one chip. For them to change chips for the US variants they would also have to have different drivers, etc for the different chips (someone correct me if I'm wrong!)

Also, if you look into the Captivate kernel there is a LOT of code in the FM Driver Module file. However, most of it is written in binary - and, I don't know anything about binary. There are several comments I could read referencing fail results for the FM Drivers.

I think we are looking at the same chip as in the I9000 - and, the Broadcom employee also thinks the same.

What is most likely happening is there is some code that ATT had put into their files that either tells the FMRadio files not to be loaded or ignored if they are loaded.

I wish I knew how to compile or I would remove a bunch of the ATT kernel files - leave all the same files there from the I9000 - flash the kernel and see what happens.

I may try to tackle learning how to do this later this week....
[Captivate Android Development] shaneaus:
Check here to see what they are doing with the Vibrant. I really wish we all had one section instead of all of us having to check three sections to see what is being accomplished/attempted!

http://xdaforums.com/showthread.php?t=738318

They have brought out a couple of different issues - worth a read.
[Captivate Android Development] boborone:
Just wait till vrzn and sprint get there's out, then we have 5. It really is something we ought to suggest is combing em into one sub. Galaxy S, then break it down into say, GSM and CDMA, something like is used for the HTC TP phones.
[Captivate Android Development] YellowGTO:
VZW and Sprint don't have the same GPS/FM/BT Chip. They have the 2.1BT model. I'm betting not only does the GPS work better but the drivers will be diff.

BCM2049 i'm guessing.
[Captivate Android Development] boborone:
Then that right there would be a way to seperate the sub, by chipset. I've been looking for soft difference between the phones, but if it's a hard one, then all else would fall in that....maybe. idk, I hate hardware and jelous of you guys.

.....ill go hide behide my stack of punch cards and tape now
[Captivate Android Development] YellowGTO:
I could be wrong. The could have the same GPS and the same FM just a diff BT.
[Captivate Android Development] cesierra:
The OP on this thread is saying something about the radio working but it's not clear. We'll see.

http://xdaforums.com/showthread.php?t=740486
[Captivate Android Development] derek4484:
If you look at the source code that samsung posted, its got the drivers for the BCM4329. Go to broadcomm's website and read the description of that chip. Its Wifi/BT2.1/FM all in one chip. Its an FM receiver and transmitter.

BCM4329 - Low-Power 802.11n with Bluetooth® 2.1 + EDR and FM (Tx and Rx)

GPS is not on this chip, the GPS is a different chip, BCM4571 or something like that.
[Captivate Android Development] danr238:
Wrong thread sorry
[Captivate Android Development] rambo6:
AT&T and NO FM Radio?

I cannot believe AT&T did not activate the radio. I'm using an HTC HD2 and I use the radio all the time. The guy saying 3G drains less than the FM Radio doesn't know what he's talking about. At least on My HTC HD2 on AT&T, I can listen to the radio all day at work and still have battery life. If I run 3G, it definitely won't last more than a few hours.

I was just about to go out and buy the captivate, but I think I'll wait. It's most likely the hardware is there for the FM Radio, but I'm not buying until I know the device has Froyo and an FM Radio. They really should have added a flash for the camera also.
[Captivate Android Development] LGSilva:
I don't know if it have anything to do with the FM radio but I was looking at settings.db and there is a "bt_svcst_bluetooth_fm_receiver_test" setting set to 0.

I changed it to 1 but didn't notice any difference on the "settings" menus.

Maybe with the modified kernel...
[Captivate Android Development] YellowGTO:
"08-02 00:23:12.281: INFO/FmRadioController(2264): FmRadioController_powerOn failed" :-(

We need an alogcat from the EU version to see what loaded up with the FM Radio.
[Captivate Android Development] for_ap1:
From what I can see FM chip does not respond on I2S bus. This means that it is either not installed, or has another address than in global version. There are also several GPIO lines connected to it, they also have their addresses and it is possible that lines are different from global version. What we need to know if Si4709 isactually present. Considering that it is a dedicated chip, that does not have any other function, I can see that AT&T decided not to install it and save few pennies per device. I also found few commented out lines in driver sources. They refer to different initialization sequence for the chip. It's probably worth effort try to compile driver with these changes.
[Captivate Android Development] opensourcefan:
You know guys I don't have a clue what your all talking about but I just wanted to say keep up the good work as FM Radio is very important to me and I am appreciating your efforts.
[Captivate Android Development] immer:
Hey bahnburner, since you have everything setup, can you try reducing the sample rate in the source from 44Khz to maybe 16Khz and see if the FM radio turns on? I had problems w/ voice recorders wanting to force close when operated at 44Khz but they gladly worked at 22Khz and below. I am not saying this would fix the problem but it's worth a try. Also reinstall the FM radio app before doing this.
[Captivate Android Development] for_ap1:
I do not think that this is an issue. What I see is that driver can't talk to hardware either because it is different from I9000 or plain missing.
[Captivate Android Development] bahnburner:
That sounds like it might be above my skill level.
[Captivate Android Development] LGSilva:
Is there such thing as "lshw" on android? It's a Linux command to list all the hardware...
[Captivate Android Development] ptc62:
Lsmod get what you are looking for?
[Captivate Android Development] Anim8ED_1:
Are you looking for this?
[Captivate Android Development] opensourcefan:
I'm not sure if this is useful or not but the Bell Canada Vibrant has FM working out of the box. Played with it in the store today.
[Captivate Android Development] YellowGTO:
Is the Canadian Vibrant the same as Tmo?
[Captivate Android Development] ardyer:
I think it is the International Version.
[Captivate Android Development] sdimezq8:
Does anyone know if any progress has been made on this? From the little information I have gathered, it seems like the radio hardware may not be present in the Captivate. :confused: