yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] sudeepm:
hi all..

the release notes mention using spirit FM from the market, but it doesnt seem to work for me.

the gingerbread stock FM radio app used to work fine..is thr a way to install that into this version of ICS..or any other suggestions for FM radio app..

FM is one of my quite frequently used apps as i travel a lot..if this works..RC3 would be the perfect rom for me!!

thanks.
[Galaxy S I9000 Q&A, Help & Troubleshooting] sudeepm:
quick update..I managed to find the FM radio apk from gingerbread, pushed it to system/app folder using root explorer..but it still doesn't show up in the installed apps list..

can someone guide me on the usage of system/apps folder..do i have to do nething more after copying the app apk to that folder?

appreciate someone's help on this.

Thanks.
[Galaxy S I9000 Q&A, Help & Troubleshooting] sudeepm:
no clue to anyone?? :-(
[Galaxy S I9000 Q&A, Help & Troubleshooting] darkmoon078:
you have to change permission using root explorer to:

Owner : Read & write

Group : Read

Others: Read

And in the spirit FM you have to change this:

setings --> Audio ---> method -> GalaxyS ALSA
[Galaxy S I9000 Q&A, Help & Troubleshooting] sudeepm:
thx..i'll try changing permissions. Also, i read warnings about using spirit FM on galaxy S leading to permanent speaker damage? is tht true for onecosmic's RC3 too?

thx again.
[Galaxy S I9000 Q&A, Help & Troubleshooting] darkmoon078:
I used it without problems, but to be on the safe side I prefer to use it bye headset. ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] sudeepm:
Hi

Thanks for the update.. Have been using spirit FM "at my own risk" ;-) no issues so far.

Thanks for all the help.
[XPERIA X8 Q&A, Help & Troubleshooting] eLGi:
Hi fellows. I have weird problem with my phone. I have GingerDX v021 ROM, stock kernel, not overclocked CPU and locked bootloader. My problem is that when someone is calling me phone is not making any sound or even vibrating. I checked in settings and everything is correct. I can't answer any call if I won't look at my phone in the time someone's calling.

Any ideas?
[XPERIA X8 Q&A, Help & Troubleshooting] pesky_89:
try a factory reset in CWM. if this doesnt help, try this:

1.flash stock ROM

2. test your incoming call sound

3. if it works, root your stock and install xrecovery

4. flash gingerdx013 using xrecovery and test your incoming call sound

5. gingerdx013 has builtin CWM. reboot in cwm

6. install gingerdx021

7. install stock kernel applications for gingerdx (uv dual touch etc)

8. test it
[XPERIA X8 Q&A, Help & Troubleshooting] eLGi:
Thanks a lot, man. Now it works :)
[XPERIA X8 Q&A, Help & Troubleshooting] pesky_89:
np just hit the thanks button :D
[Nexus S Q&A, Help & Troubleshooting] allenxx:
Hey guys! i have been searching through all the forums on xda and google on how to downgrade 4.0.3 to gingerbread. And no luck. I have Rooted BM ICS, and i have flash some other ics and quite frankly all are buggy so i want to go back to gingerbread since i cant find a fully stable ICS (Battery, ram etc.) Btw i have i9020T and cwm.
[Nexus S Q&A, Help & Troubleshooting] turkobr:
If you unlocked the bootloader and is rooted, the easiest way is to download rom manager from the market, choose a rom from the dev section and install it.
[Nexus S Q&A, Help & Troubleshooting] nevrlow:
Yes in rom manager peter alfonso has stock images. Just download and install

This will unroot ur phone but will keep the bootloader unlocked. From there you can reroot and have gb or a gb rom of choice.

sent from an HTC sensation on CM7 alpha #10
[Nexus S Q&A, Help & Troubleshooting] allenxx:
aight then im about to do so, uhhh just another question...how do you root again?? i forgot lol and will this change my radio?Also does it matter what rom i choose?
[Nexus S Q&A, Help & Troubleshooting] isaacfank:
you dont root when you install a custom rom. they come rooted. so you can just flash whatever you want, when ever you want.

if you need a refresher, when you change roms you need to format everything, format data/cache and dalvik cache, (in advanced) then find the rom and install from zip. anymore questions ill help you out. just pm me.

and research your questions first. this place has a wealth of knowledge.
[HD2 Android Q&A, Help & Troubleshooting and Genera] mmg06:
So, i know, again the sd problem, but nopt the "normal" lock problem:

The hd2 donna read any sd card in magdlr!

But from the piont of beginning:

1) original miui version installed (from german miui)

2) installed WP7 back to future, dunno run, so i changed the sd card to an 8gb one. also not work, so i want to go back to android.

so i installed a clean wp7 back2future rom and use the unlock.cab 2 unlock my sd card, worked more or less but sd cards are unlocked now

3) first flash the original wm 6.5 built from htc, everything worjks(read sd card)

4) task 29

5)magdlr

6) cwm installed

7) want to copy over a rom, but windows told me, that i have to format the card, but if i do, theres ionly one 1kb partiotion...

but the sdcard worksd always in windows mobile roms and with a reader! what can i do? all sd cards are unlocked!

mmg06

ps: sorry for the double post, but i realy need help ;)
[HD2 Android Q&A, Help & Troubleshooting and Genera] gdsbalaji:
try panasonic sd formater, do full erase with adjust size option checked...should work post that.
[G1 General] frankdrey:
Twas the night.......nah that's not gonna work...

Anyways, I had just compiled froyo from android source and wanted to flash it

But apparantly I needed a specific spl when I did "fastboot flashall -w" (one of them being 0.95.0000 or whatever, too lazy to remember..but it was one that didn't support fastboot....which is dumb lol since fastboot is saying to use it)...

So I decided to install engineering spl

I had danger spl and the 2.something radio it needs

I decided to flash it from recovery

BRICK!

So really g1s are impossible to brick...if you flash radio and spls from fastboot not recovery

(Most of this knowledge is from a thread about g1s and spls and bricking that I'm too lazy to link to)

What happens is that recovery FORCES the g1 to boot to recovery on next boot...even if you press buttons

And with a mismatched radio/spl recovery will not start

So you have a brick...

Moral: use fastboot not recovery

Anyways so my solution...

I had a really messed up rogers dream that had a cracked screen and bad ribbon cables...

Pretty much everything was broken except for the motherboard...

Well I decided to try and put this rogers motherboard into my tmobile g1

It worked!

Even booted up into the rom I used to have (biffmod) on the rogers dream before it got screwed up beyond usability

I am posting from my g1 with a rogers motherboard in it as I speak...post....

Moral 2: you can mix motherboards between dreams

One problem is that this ROM still has the keymap for the rogers dream and my home and call button don't work

Hopefully flashing a new rom it will detect the tmobile keyboard

Well this was fun...but I don't know if I'm gonna try to flash my aosp froyo or not again...

Comment please on how you manage to flash a compiled aosp froyo:D...maybe ill try flashing engineering spl again through fastboot this time

Edit: oh and I like this motherboards vibrate more:P

Its quieter...

The old one rattled like crazy

So this actually a very win situation

I got Frayo back on and everythings beautiful
[G1 General] mishamosher:
In a rom's zip there is this file:

META-INF\com\google\android\updater-script

Try to open it and read the first lines, there are the asserts generally (the part that tells to the device that particular SPL/Radio/Files are needed to proceed the install)

Here's an example of an assert:

assert(getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||

getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire");

assert(getprop("ro.bootloader") == "1.33.0013" ||

getprop("ro.bootloader") == "1.33.2013" ||

getprop("ro.bootloader") == "1.33.3013" ||

getprop("ro.bootloader") == "1.33.0013d");

This assert checks many things, with logical operators (|| that's or; == that's equal; "" that's a string; () that's an argument; etc). If you've ever programmed, you'll understand very fast how to change the assert to make it less agressive of checking this things and anothers and not let you install.

The previous assert cheched that the device, or product, ot board where "trout" or "sapphire". Also it needs an specific bootloader ("1.33.0013", or "1.33.2013", or"1.33.3013", or "1.33.0013d").

It's an good idea tho check the updater-script that's in your zip installation file, view what installs it, add/remove asserts and unwanted things, and then, proceed to install it safely from recovery and the SPL/Radio combo that you prefer. Also, it's an good idea to flash an alternative kernel (ezterry one's are very good).

Remember that the only thing that's really recommended to install from fastboot is the SPL and the Radio. Other things are installable from wherever you want (fastboot, OS, recovery) without an potential hard brick risk.

So, if you want to install an ROM (AOSP FroYo as you described), it's not needed to install it from fastboot, and it will not represent an brick risk if it really is only a ROM installer what you have.

---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------

Oh, and if you can paste here the updater-script it would be usefull, more than one buddy will say you how to change it to let you install everithing by a correct and safe way.
[G1 General] frankdrey:
Yes yes I know all of that

I'm using fastboot because the compiled output is not an update.zip

Its all the image files and I am supposed to do "fastboot flashall"

Its alright though...I got cm6 source working

That will work:D
[G1 General] mishamosher:
It should be also fun to convert your images to a zip format.

When you flash those full images, you don't know if it will flash more things than needed. Zip files give you more control, and the updater-script also.

The "fastboot flashall" command is kinda risky with images that touchs radio/spl/partitions layouts/etc. It's really recommended to do a wipe of everithing from fastboot when you're installing this images, and also, of course, know what those images will install and be carefull to have the right pre-requisites to don't harm the device.

Good to know you got it working after all :D !
[G1 General] frankdrey:
Alright maybe putting images into zips will be an adventure for later

As of now, the AOSP froyo source and built images are in the deep dark room of a PC's deleted files :D

Thanks for the tip about flashall! :P
[G1 General] Scrip:
No need for flashall

instead of using

make

use

make otapackage

You will find a zip ready for flashing

if you are building cm6 then use

squisher

to optimise the zip

have a look in the opticharger script to make improvements like replacing pngcrush with something better
[G1 General] frankdrey:
Thanks:D

And here I was about to go and start extracting the images and writing an updater-script:P

And I went back to AOSP

CM6 has too many missing files that I don't want to go through the trouble of finding
[G1 General] mishamosher:
OTA packaging is easier and more simple, I agree... but something is true... fighting with those extractions and updater-script is kinda funnier :D

Happy source-compiling ;)
[G1 General] frankdrey:
Alright I have the zip and all

It checks for the spls though

Should I just remove that from the script?

And try with DangerSPL?

DangerSPL is a port of the mytouch spl right?

Maybe I shoulda built for mytouch?

Also, it looks like it patches recovery after install.

Is that safe? Should I remove the entire folder and entry in the update script?
[G1 General] mishamosher:
You must do a little change.

First, open the updater-script, then find the bootloader assert

It will be like this:

assert(getprop("ro.bootloader") == "1.33.0013" ||

getprop("ro.bootloader") == "1.33.2013" ||

getprop("ro.bootloader") == "1.33.3013" ||

getprop("ro.bootloader") == "1.33.0013d");

Just be shure to add the SPL version that you've installed on your phone already. For example, if I've a 1.33.2222 bootloader, then the change will be this:

assert(getprop("ro.bootloader") == "1.33.0013" ||

getprop("ro.bootloader") == "1.33.2013" ||

getprop("ro.bootloader") == "1.33.3013" ||

getprop("ro.bootloader") == "1.33.2222" ||

getprop("ro.bootloader") == "1.33.0013d");

It doesn't matter if you put the new bootloader assert on the beginning or at last or in the middle, it'll be the same. Also, you can delete some asserts if you want to. Be carefull to keep right the sintax.

And the recovery thing, it's better to delete that part, zip will give less troubles whithout that part. And better to delete it from the script and the zip!

I recommend you to use the 1.33.0013d SPL, it'll give you extra RAM and is fully compatible with AOSP FroYo. Just be shure that after flashing the ROM, you flash the right kernel to let the OS boot up.

And remember, if you use Amon_RA recovery, you'll need to re-sign the zip that you modify, if you don't do it, the verification part of the flashing will fail.
[G1 General] frankdrey:
Ok thanks I thought all of that too, just wanted to make sure
[G1 General] mishamosher:
Oh, and I forgot it...

DON'T edit the script with notepad on windows, it leaves an "Error 6" in recovery when flashing.

In windows you can use notepad++ (google it, it's free), or if you're using other text editor just be shure that the "Enter" (new line in text) key is on right encoding, it's kinda of Unicode if I've good memory yet
[G1 General] frankdrey:
Yes I have edited them before
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] drew2jr:
Hi everyone my tablet is rooted I wanted to know how can I play pc games on it like SKYRIM.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] animatechnica:
You cant directly buy u can install splashtop on your pc and tablet and use tablet to remote in to your pc to play skyrim
[Galaxy S I9000 Q&A, Help & Troubleshooting] underzoom:
Hello friends! This forum has been of great help to me and my device for a very long time. Appreciate all the help and guides provided here for the not so tech savvy people like me.

Just wanted to check for an opinion from you guys here. I have been having this ghosting problem on my i9000 where on a clear white screen, there is a fixed ghost image (or whatever you call it) of the pattern lock screen hard on embedded.

This is only visible on a clear white background. I have enquired in the local shops here (in Malaysia) but they all seem to suggest changing the screen and the digitizer but cannot prove that it will work and I would have spend more if the problem isn't fixed.

There are 2 links of the problem I mentioned here and I appreciate any suggestion from you forumers as to what would have gone wrong and the most probable component that needs to be changed as I believe people here would have seen more occurrences like these compared to the local stores here. FYI, the warranty period of my phone has already expired as it is a 1 and a half year old set. Thank you very much in advance!

p/s: i would love to add an image link of the problem but due to being a new user, i am unable to show this problem to you. :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] alzaq:
could you please upload those images on upload sites
[Galaxy S I9000 Q&A, Help & Troubleshooting] underzoom:
The link are as below

i102.photobucket.com/albums/m96/underzoom/b.jpg

i102.photobucket.com/albums/m96/underzoom/a-1.jpg
[Galaxy S I9000 Q&A, Help & Troubleshooting] GIBbeerSKY:
I have the same, but less visible.

It's one of disadvantages of OLED screens - screen degradation. The more particular pixel is used, the darker it becomes.

In our example - previous owner left phone with lockscreen visible and long timeout set for very many times.

Only way to get rid of it is OLED screen replacement, warranty is not covering the screen degradation. Remember that the screen is integrated with digitizer.
[Xoom Q&A, Help & Troubleshooting] williamthegoat:
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
[Xoom Q&A, Help & Troubleshooting] supenova3000:
I have had the same issue for the past few days I have also tried the steps here no luck.... http://xdaforums.com/showthread.php?t=1249798
[Xoom Q&A, Help & Troubleshooting] williamthegoat:
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
[Xoom Q&A, Help & Troubleshooting] supenova3000:
I tried moving the files from the tools folder to platform tools still no luck.. all of this for the I C S flash I'm going to keep working on a solution I will let you know if I have any luck!
[Xoom Q&A, Help & Troubleshooting] williamthegoat:
So I have the android sdk in c:\ , and in the sdk folder I have everything, and in the platform tools I have my fastboot and recovery. I then use cmd to get into adb, then I put the xoom in fastboot. From there I try to flash the recovery, which always fails. I must be doing something wrong here.
[Xoom Q&A, Help & Troubleshooting] d3athsd00r:
Try downloading the IMG again. Or try out the rogue recovery. I actually like rogue better.
[Xoom Q&A, Help & Troubleshooting] williamthegoat:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS

Thanks for the responses and help guys
[Xoom Q&A, Help & Troubleshooting] subslug:
Think you have to be stock to flash to ICS, at least that was the word yesterday.

I gave up trying to root just as I found out about the ICS update.
[Xoom Q&A, Help & Troubleshooting] okantomi:
Two simple errors:

1) not opening the command window from the folder where you have fastboot and the image files you're trying to flash; and

2) not realizing that you have hidden file extensions in Windows, and typing ...recovery.img.img
[Xoom Q&A, Help & Troubleshooting] Dr.Samsumoto:
I assume that you've set up a path in environment variables to run adb and fastboot from ay directory... and are running the flash command from a folder other than where your .IMG file is located. In order for fastboot to find the file you're trying to flash, you actually have to run your flash command from the folder your file is located...

So, cd\...\platform-tools and then flash
[Xoom Q&A, Help & Troubleshooting] xxspark89xx:
The simplest way I perform all of my operations for this:

I leave everything installed into it's default locations. I download tiamat's CWM image and place it into the platform-tools folder.

For Windows 7, I use Windows PowerShell.

For example: Open Start Menu > Type "power" to search, "Windows PowerShell" should show up. (For me, its default at the top - so I press enter to open it)

Once opened: I type this configuration EXACTLY as is: (Keys in <>)

cd C:\Pr <TAB><TAB> An <TAB> An <TAB> Pl <TAB><TAB> <ENTER>

This above brings me directly to:

C:\Program Files (x86)\Android\Android-sdk\Platform-tools\

Of course, this will be different depending upon your computer setup. I've nailed this routine to get to the path the quickest.

to use FASTBOOT (XOOM already in fastboot mode):

./fastboot flash recovery rec<TAB><ENTER>

This auto completes the filename as ./recovery-tiamat-r4c-xxxx.img

Of course, depending on how many files/folders you have, you may have to hit <TAB> multiple times. I have to do it 3 or 4 times to select the recovery image I want.

Auto-complete is a nice thing. "./" is added to command from the working directory.
[HTC Flyer, EVO View 4G] k0ral:
As in the object, does anyone has tried to play videogames on the Flyer connected to a TV through HDMI or DLNA ?

How is the experience? Positive? Marvellous?

I like playing Asphalt 6...and I was imaging how can it be playing it on TV :)

Inviato dal mio HTC Flyer P510e usando Tapatalk
[HTC Flyer, EVO View 4G] DigitalMD:
I've done it HDMI , works fine.

Certainly the picture quality is not as good as a Xbox or Ps3 and of course the controls are not as good.

Not sure that would work with DLNA, I doubt it and there would at least be a significant delay
[HTC Flyer, EVO View 4G] k0ral:
Which games have you played?

Inviato dal mio HTC Flyer P510e usando Tapatalk
[HTC Flyer, EVO View 4G] DigitalMD:
Whatever you can display on the Flyer screen displays also on the TV on HDMI.

I tried Madden 12, but you need to look at the touch screen to operate it successfully.

DLNA does not work that way, it allows you to share media ie. photos, music, movies.
[HTC Flyer, EVO View 4G] k0ral:
I thought that with DLNA I'd have had less cables..so i'd have to drive my car in videogames better :)

Inviato dal mio HTC Flyer P510e usando Tapatalk
[HTC Flyer, EVO View 4G] aostl:
I've played onlive with mhl and the onlive controller. It works awesome if you have fast internet. The controller can be a pita to connect
[HTC Flyer, EVO View 4G] aostl:
DLNA only let's you stream photo, music, and some kinds of video, so games wont work, at least not with htcs adapter
[Samsung Galaxy Nexus] Chopstix9:
I moved to the G-Nex from the Charge. I drive a truck and have the Charge cradle. It's a nice cradle with suction mount and locking swivel. Like many, I was really bummed to see the one piece molded mount Verizon has for the Nexus.

Much to my delight, I've found that with a very minor 5 minute modification, the Nexus fits the Charge cradle beautifully. The Nexus is the same width but taller. Take a Stanley knife or similar razor knife and cut the top left protrusion off of the cradle, where it would snap onto the top left corner of the Charge. Just trim it flush so the Nexus back rests on it. Then take a pair of needle nose pliers and pull out the micro usb plug from inside the charging slide lock. Slip in your Nexus, slide the charge slider closed and presto !! A nice swivel mount cradle for the G-Nex.

Yes, you do have to plug the cable in the bottom, it doesn't plug into the cradle, but that is small potatoes IMO. It makes a real nice cradle for the Nexus.
[Samsung Galaxy Nexus] rtadams89:
Can you post a picture of the dock and the way it is mounted. Also, a link to the dock you have would be great as I am not familiar with the Charge accessories.
[Samsung Galaxy Nexus] Chopstix9:
It's the cradle for the Charge they sell in Verizon company stores. Not a 3rd party retailer.
[Samsung Galaxy Nexus] Chopstix9:
This is the mount ==> http://www.verizonwireless.com/b2c/store/accessory?action=refineByPhone&phoneId=5642

if you expand the picture, the corner I am talking about trimming would be the lower left. I only use it in portrait position so that makes it the upper left. I've twisted it to landscape and the phone is still in there firm though.

It is the only mount on the Verizon site that is device specific for the Charge

Edit: oops ... that link just goes to the Charge accessories page. Under the category tab far left click on mounts and it will appear.
[Samsung Galaxy Nexus] Bear55:
I came from the Droid Charge as well. I use my Charge car mount for now without any modifications. It doesn't look pretty because, as the OP said, this phone is taller and without modifications to the dock the phone sits at an angle. It seems fairly secure though; better than a crummy universal dock that I tried out anyway. I would not recommended buying the Charge dock over the Galaxy Nexus dock though because at the end of the day they are both just a chunk of plastic when used with this phone and the only reason I am using the Charge dock is because I already had it.