yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] mcord11758:
If you are willing to flash custom roms hours is fixed, not complete fix, but working well

I get lock in under 10 seconds within 10 meters, and tracks well with little bouncing
[Captivate Q&A, Help & Troubleshooting] alaimar:
Welcome back!!! I've found several ROM's that have great GPS. Not 100% but good enough for me.
[Captivate Q&A, Help & Troubleshooting] kegobeer:
I get a fairly quick lock on my stock ROM. I got one inside last night, so I certainly can't complain about GPS issues.
[Captivate Q&A, Help & Troubleshooting] haroonazeem638:
My captivate from rogers has never had any gps issues
[Captivate Q&A, Help & Troubleshooting] cappysw10:
+1

stock JH7 with gpsjm9 files works fine.

Sent from a phone somewhere in the universe
[Captivate Q&A, Help & Troubleshooting] diablo009:
If u r planning to get the refurb pieces or current versions, Samsung seems to have corrected the GPS issue. Mine is a refurb I got under warranty exchange with batch code 10.07, and has GPS working fine.
[Captivate Q&A, Help & Troubleshooting] DarrellRaines:
I have a 1007 and have never had an issue with the GPS other than needing ot reset it after a ROM install.

Also hear these things are hard as hell to brick.
[Captivate Q&A, Help & Troubleshooting] diablo009:
Yes *touch wood*
[Captivate Q&A, Help & Troubleshooting] yokozuna82:
thanks guys for all your help
[Nexus S General] dannstarr:
I am preparing to root my beloved new Nexus S, but am just wanting to make sure everything is set before I venture off.

I'm a previous nexus one owner, and used fastboot and adb in the past following guides from on here.

Following another guide from here, i've managed to get "fastboot devices" to show my Nexus S connected, however, when I try adb devices, nothing is listed.

I run windows 7, in order to get the fastboot devices to work, I downloaded some drivers and installed them, and then an "unknown Android 1.0 device (as shown in Device manager) was recognised as an ADB device - so I assume i'm all good on the driver front.

Is there any specific mode I need the phone connected in to get adb to recognise it? I cant remember from when I last did it on my N1?
[Nexus S General] slowz3r:
to be safe you should uninstall the unknown device and reinstall ur NS
[Nexus S General] unremarked:
Do you have USB Debugging on under Menu > Settings > Application > Development?
[Nexus S General] dannstarr:
?? huh?

unremarked - thanks very much, this is the step I had forgotten - usb debugging. Now turned on, computer auto installed some drivers, adb devices now works.

Thanks a whole bunch :D
[Nexus S General] slowz3r:
glad to see you got it working but it shouldnt say unknown android device
[Nexus S General] dannstarr:
Sorry - my bad explanation. Before I got "fastboot devices" working, it was shown as an unknown android device. I downloaded and installed drivers and that then turned in to a recognised android adb device

I got that bit done, thats why I was still confused over why in cmd "adb devices" did not show anything listed - but yeah, all sorted now, thanks :)
[Android Software/Hacking General [Developers Only]] dased14:
just rooted my evo for the first time now i have a problem.

flashed AC_Rebirth-rom now no haptic or vibe fuction at all could this be a problem with the rom i used or the vibrate motor. is it fixable or will i have to unroot and have it repaired at a sprint store, any insight would be really helpful

Thanks
[Android Software/Hacking General [Developers Only]] sitlet:
Well, to see if its the rom thats doing it, flash a different rom or a stock rom. It it comes back, then its the rom. If not, its probably hardware.
[G Tablet General] LittleBirds:
I upgraded my GTablet with a "leaked" version of the new software upgrade but now I want to update to the "official" version. Unfortunately my device won't recognize that there is an update available even when I run the updates app to look for one.

Is anyone else having this problem? Any solutions?

I hear VS may be making a recovery image available for those who have modded their GTab's beyond repair...but in the meantime, I'm curious how others are addressing this issue.
[G Tablet General] thebadfrog:
If the leaked version was the 3389 update then that is the official version. Otherwise I believe their official website has the 3389 update.

This is a link to the 3389 update that Roebeet posted

http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3389-user.zip
[G Tablet General] guitar geek:
I had been unable to get OTA updates since Nov 19. I read on another thread how a user downloaded the 3053 update manually and then his OTA started working again. So I gave it a try and sure enough it fixed my problem. In fact I have gone back to this version twice just to reset my G-Tab to stock. I have not mod'd my unit. I have flash, market and Rothnic enhancement pack.

Hope this helps

Roebeet listed all of the official TNT downloads here.

http://xdaforums.com/showthread.php?t=842000&highlight=3053

*rothnic has a new enhancement pack v2 that will not erase your stock files. It will increase the speed a little bit..
[Desire HD Q&A, Help & Troubleshooting] iridium21:
This question has been asked on a few other threads a while a go but there's never been a definitive answer :(...

Is there any way to reduce the size of, or remove, the home screen 'snap-to-grid'?

A hell of a lot of screen space is wasted because it's so large :(
[Desire HD Q&A, Help & Troubleshooting] Andy:
You will need to use an alternative launcher. Launcher Pro will allow you to do this, and its free.
[Desire HD Q&A, Help & Troubleshooting] Burning_aces:
What widget do you lose with launcher pro?

Only the HTC Sense ones or?

Also if you switch to launcher pro how do you stop htc sense from starting up?
[Desire HD Q&A, Help & Troubleshooting] Elemental_Fire:
Get a task manager that shows all apps and processes running. Once you install LauncherPro, press the home button and set the default homescreen you want. Then, kill the HTC processes and it won't load again in the background. Once every rebot do this, or set htc Sense as an auto-kill process only that, it should to the trick. Alternate options include imstalling a non-sense rom eg Cyanogen Mod or a senseless series rom. Hope I helped :)
[Desire HD Q&A, Help & Troubleshooting] Burning_aces:
yeah man cheers. I like leeroids rom at the moment, so will keep using that for now. Will test out the different home screens though
[Android Themes] medicparsons:
Ok, I just rooted my droid 1 and am using the new liquid froyo ROM. Theres some other themes that go with, but I have no idea how to load/use them. They saved as a zip file to my computer, where do I go from here?
[Android Themes] zHk3R:
Put them on the root of your SDcard. I have a folder called "FLASH THESE FILES" where I put all themes/ROMs.

Just boot up in recovery using two or more hardkeys. I have a HTC Desire and in order to boot into recovery I press the back key and power key for 5 seconds. You have something in the same manner. If you already have a rooted ROM you might have a "REBOOT" option when you shut down your phone using the power button - Use that to boot into recovery.

When you're in recovery the rest is a piece of cake - Just find your desired theme and flash it!

For future reference: The search function would have given you the same answers without having to create a new thread.
[myTouch 4G Q&A, Help & Troubleshooting] MeatyCoins:
hello, i have a fully rooted mt4g with clockwork recovery & evil desire hd port.

i let my phone die completly before charging it and every time i plug it in while the phone is off it boots back up into clockwork recovery, thus not being able to charge while off. any fix or is it suppose to be like this ?

& another thing, how do i boot into recovery mode the normal way? (not through bl)

thankyou
[myTouch 4G Q&A, Help & Troubleshooting] VibrantOwnr:
known bug in clockwork...i believe it is being worked on..
[myTouch 4G Q&A, Help & Troubleshooting] RavenWulf:
the charging issue is a commonly known issue for the MT4G after rooting and installing clockwork mod. not sure what you mean by "not through bl", the only 2 ways I know for booting into recovery is through ROM Manager or powering off phone and holding down the volume down and power buttons at the same time till phone boots.
[myTouch 4G Q&A, Help & Troubleshooting] shlongwoodian:
Try the workaround over on this thread...

http://xdaforums.com/showpost.php?p=10148208&postcount=135

i.e. Enabling Fast Boot.
[myTouch 4G Q&A, Help & Troubleshooting] henryblank:
So has anyone figured this out, or has there been a new clockworkmod released ? I tried the 'Fastboot' option but my phone still turns on in the CWM recovery menu.
[myTouch 4G Q&A, Help & Troubleshooting] RavenWulf:
Go to Settings>Connect to PC set "default connection type" to "charge only"
[G2 and Desire Z Q&A, Help & Troubleshooting] jojo_16:
guys i need your expertise regarding my power button it just stopped working i think its a hardware problem cause i restore and re-flash roms but still no luck. What do you think i can do?? CWR helped me alot it shuts on my phone and i dunno how long am i gonna hold into this, my auntie bought the phone w/o insurance i got the phone on the 1st what do you think i should do?? does anyone has the trackpad that acts as a power button pls help thnks..
[G2 and Desire Z Q&A, Help & Troubleshooting] MacaronyMax:
It comes with a yr warranty anyway i think :D Just ring htc :)
[G2 and Desire Z Q&A, Help & Troubleshooting] jojo_16:
my phone is rooted and my rom manager doesnt work cannot it says "an error occured while attempting to run privileged commands!" i cannot even restore backups and when i go to fastboot it just goes there and i cannot press anything but when i boot power volumes work i dunno how to use adb and will HTC need to send my phone in order to do a warranty or will they send me first?? pls help

EDIT: i just restored through clockwork reco i just waited for fastboot and it works

what do you think about sending my phone to warranty(maybe the replacement is root proof)??

EDIT: power button not broken idk it seems it takes long enough to appear buttons or i think when i press touch screen then press power after a while it appears idk what the hell happened to my phone :confused:
[Captivate Q&A, Help & Troubleshooting] gocats7:
I am considering buying an otterbox and I got to thinking how big a pita it may be to remove the sim and sd card each time I flash. So my question is what does it cause if you leave the SIM in and SD in and flash a new ROM? Whatever problems people say it cause, has anyone experienced the problem themselves?

Some things are just 1 in a million or old stuff that doesnt impact things now so I am trying to figure out the difference.

Thanks!
[Captivate Q&A, Help & Troubleshooting] mcord11758:
I do it as rule of thumb. Today I did not. Have not had an issue yet
[Captivate Q&A, Help & Troubleshooting] plasticdarlow:
I've never removed my sim, and never had a problem.....
[Captivate Q&A, Help & Troubleshooting] ccdoggy:
I am a firm believer that if you are having problems with a ROM delete everything possible and remove the SIM and SD. though I have installed the last few ROMs with both in without any real problems.

i would be interested in finding out why its suggested...
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
Never removed anything before unless I soft bricked it.
[Captivate Q&A, Help & Troubleshooting] Cozmo1:
I never remove the SIM while flashing. Don't generally remove the external SD card either. I didn't even remove them when recovering from a soft brick. If it's a concern of possibly losing data you can always back it up when you mount them to use on your computer.

To answer your ultimate question you really don't need to be removing the Captivate from your Otterbox.
[Captivate Q&A, Help & Troubleshooting] DarrellRaines:
I've never removed it. Don't see why we would need to to be honest
[Captivate Q&A, Help & Troubleshooting] Dungeon47:
I've never removed mine, never had trouble. I think it might be one of those "do it if it makes you feel better" sort of things.
[Captivate Q&A, Help & Troubleshooting] avs420:
I flashed once with the SIM to Cog6 about 5 weeks ago and lost my baseband version. Meaning, I couldn't make calls.

Reflashed to 1 click then back to Cog W/O SIM and I calls worked again
[Captivate Q&A, Help & Troubleshooting] Phateless:
So reflashing can actually clear SIM settings? Yikes.
[Captivate Q&A, Help & Troubleshooting] upNsmokeAllDay:
neither have i and i have flashed probably 30 times or more and never had a single issue.
[Captivate Q&A, Help & Troubleshooting] MikeyMike01:
I think I took the SIM out like once. And I've done hundreds of ROM flashes.
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
Only time you would need to take out your SIM is if your phone is soft-bricked so bad you end up having to do the whole take out everything to get it back into DOWNLOAD mode.

Otherwise - I've flashed probably about as much as Mikey (sad for not being a developer/chef) and never had an issue.
[Droid X Android Development] sniffle:
What a crazy 3 months it has been, with life in general getting in the way of development, but it's over and here is a release for everyone!

For the full list of changes please see the changelog at http://bit.ly/aH0ioL.

*Please note*

All Google apps that are available for download from the market will no longer be included in the CCRoms Google apps package, to facilitate updating the apps the way Google intends.

Also this release is FROYO, Gingerbread will most likely be our next release with this gem version's features ported to AOSP Gingerbread.

The Main Highlights:

Obsidian for the Droid X is now a fully stable build, some minor bugs might still exist, but otherwise it is rock solid.

Tanzanite for the Droid 2 is also stable build, since it is so close to the Droid X.

Emerald for the HTC Evo is also stable for all pre-2.10 and 2.02 hboot updates.

Sapphire is just as stable as ever.

Ruby has been updated to the Miui ril for better connectivity and is more stable than ever.

That's right we are now on 5 phones, Thanks for all of your support everyone!

Now for the important part, Obsidian 2.0, Ruby 2.0, Sapphire 2.0, Tanzanite 2.0 are released!

All Downloads are available under the downloads section on our wiki: http://wiki.ccroms.net

Be sure to read the wiki pages fully for known issues and install instructions for certain roms.

NOTE: Emerald has been having some kernel issues and 2.0 will be delayed slightly.
[Droid X Android Development] mattyboy1013:
Just flashed, running very fast!!!! Thank you sniffle and CVPCS. And the post above is the official post from sniffle himself :D
[Droid X Android Development] amasse:
Really awesome work. Is running very stable for me. Reboot ->Recovery works perfectly as well so there is nothing to fear for people uncomfortable without needing Koush's bootstrap app.

Love that the Nexus wallpapers are all included. Also digging all of the customization options.

Again, Thank you for your work.

EDIT: Also I should not that you should download the apps .zip file before you flash the ROM because the stock browser can't download from the site for some reason. I had to do it on my computer and transfer over. Not very difficult but it will save a couple minutes to just download it before you flash.
[Droid X Android Development] cvpcs:
if you notice any bugs please post them to the bug tracker (bugs.ccroms.net)!

(be sure to check if the bug exists before posting a new one)

hope everyone likes the release!
[Droid X Android Development] sunder74:
quick question

So the Obsidian note in the op says stable, is the bug list on the wiki current? No pin point Gps, camera or cam corder correct?
[Droid X Android Development] cvpcs:
yes. the wiki list is the current bug list. by "stable" we mean it doesn't reboot uncontrollably anymore. it's still in beta and has kinks to be worked out.
[Droid X Android Development] bringatowel:
Could anyone be helpful and point me towards the install instructions?
[Droid X Android Development] pCarson92:
Great job guys. I'm waiting until GPS and Camera are working though. Can't wait to see a Gingerbread release!

Also, you guys should get a Google Code page.
[Droid X Android Development] mhsbrian:
I'd like a install guide as well, I don't wanna have to SBF my phone.
[Droid X Android Development] imronburgundy:
I third that. Quick question besides how to install this rom...i notice that the wiki said it provides bad battery life. I have an extended battery, but if it is so bad at this time, can i sbf back to Stock? Thanks for the hard work
[Droid X Android Development] jaskru:
some tips...

http://wiki.ccroms.net/obsidian/releases/2.0.0
[Droid X Android Development] imronburgundy:
Sorry, that doesn't actually say how to install the rom originally. Just says don't use clockwork mod after its installed. Is this originally installed through cw mod then using ccroms own clockwork app? Also can you sbf back to stock if it isn't for you?
[Droid X Android Development] cvpcs:
for those wondering about installation:

basic installation procedure:

Download main (and possibly gapps) zips and push to your sdcard

Use koush's bootstrap recovery to get into CW recovery

NANDROID NANDROID NANDROID!

Wipe data/cache (Factory reset)

Install core zip from sdcard (no need to manually mount /system first)

(Optionally) install gapps zip from sdcard

Reboot

once in the system, do NOT use koush's bootstrap to get into recovery. instead, simply long-press the power button to bring up the global options menu, then select "Reboot" and "Reboot Recovery"

after that, you should reboot into CW again. from here you can nandroid all you like. nandroids from koush's bootstrap will work with the provided copy of CW recovery. note however that nandroids of obsidian will NOT work with koush's bootstrap recovery, as koush's bootstrap recovery does not backup/restore the /preinstall partition.

also, this installation only edits the /system and /preinstall partitions, so SBFs still work just fine if something goes wrong.
[Droid X Android Development] ejgilkey:
So if we wanted to go from another rom back to an Obsidian nandroid, how would we accomplish this?
[Droid X Android Development] LexusBrian400:
On obsidian.. in the reboot menu... when u hit reboot, it give u the option to flash into recovery. Dont install the bootstrapper cuz its already included in the reboot menu on obsidian.
[Droid X Android Development] ejgilkey:
So you'd have to flash the rom first, then restore the nandroid? Is there an advantage to this recovery compared to bootstrapper?
[Droid X Android Development] LexusBrian400:
Sorry I have no idea what u mean.
[Droid X Android Development] Namolas:
Bootstrap is not a recovery, it is merely the "vehicle" that gets you into Clockwork Recovery. Basically this ROM comes equipped with its own "vehicle" to boot to Clockwork Recovery.

GMB
[Droid X Android Development] pCarson92:
I think you are confused.

Reboot Recovery using whatever ROM you are on

Create Nandroid backup

Install Obsidian from .zip

Play with Obsidian

Hold down power button, press reboot, then reboot recovery

Now you are in Recovery again

Click "Restore"
[Droid X Android Development] ejgilkey:
If I'm running Fission (or any other rom) and want to flash a nandroid backup I created using the Obsidian recovery, I would need to first install the Obsidian .zip and then reboot into Obsidians recovery to flash back to the Obsidian nandroid. Correct?
[Droid X Android Development] :
He stated that Obsidian nandroids won't work with Koush's recovery.
[Droid X Android Development] Namolas:
Yes. :)

GMB
[Droid X Android Development] pCarson92:
I think you're getting it. If you are running GummyJAR and you try to restore to an Obsidian backup, it won't work because of reasons he described. The other way around WILL work. Maybe in the future, Koush will update his app to work interchangibly or vice versa.
[Droid X Android Development] :
Ok thanks! Going to try this out!
[Droid X Android Development] amasse:
Ah wish I had read this before I flashed back to fission. Oh well. I look forward to trying the next versions.
[Droid X Android Development] iamrobk:
Just out of curiosity, what're the differences between the bootstrap method this uses vs. what koush's app does? Or is it too technical?

I can't wait to try this out, it's a huge step for the DX community, but I think I'll wait until the GPS and performance issues are fixed. Hope it's soon.
[Droid X Android Development] cvpcs:
OK HOLD ON TO YOUR HORSES! IT'S TIME FOR SOME TECHNICAL CRAP ABOUT RECOVERIES! :D :D :D :D

So why does obsidian require it's own recovery and not just use koush's bootstrap like the rest of the DroidX/Droid2 ROM world? Well here we go.

Basically, recovery works like this:

Early on in the boot process, the initialization program (known as /init) makes a call to mount the /cache partition. This call is "hijacked" as in we replace the "mounting" program with another program that effectively pauses /init, and then start up recovery.

Koush's bootstrap already provides this mechanism. That's how recovery is started. When you're clicking "reboot recovery" in his app, he is essentially creating a file (/data/.recovery_mode), and restarting phone. On reboot, the hijack program finds that file and because it is there, instead of letting /init proceed, it "hijacks" it and starts recovery.

HOWEVER. Obsidian is an AOSP rom, and therefore it cannot function properly using moto's provided /init. We cannot change /init because it is part of the boot partition. So what do we do?

The solution is to ALWAYS hijack /init. If /data/.recovery_mode is there we boot into recovery, if not, we kick off an AOSP /init and tell motorola's /init to sleep for roughly 136.192519501522 years. If it comes out of this sleep? well...we tell it to go back to sleep for another 136.192519501522 years... indefinitely (let's just say we tell moto's /init to screw off).

So here is the cardinal reason why koush's bootstrapper can't be used. If you bootstrap koush's recovery app, then it will overwrite obsidian's hijack executable. If that happens, then if not booting into recovery mode, moto's /init will continue (as koush's hijack knows nothing about obsidian's aosp /init) and the phone will fail to boot.

Now, on to the next major question. What is different between the two recoveries (koush's and obsidian's) that make obsidian's nandroids incompatible with koush's recovery, but koush's nandroids compatible with obsidian's?

The answer is simple. Koush's recovery does not nandroid the /preinstall partition. Obsidian requires use of the /preinstall partition to boot, so in order to properly back up the entire working system, clockwork recovery had to be modified to add /preinstall to the list of partitions backed up. Hence, when you use nandroid to restore a koush-based backup, obsidian's recovery just says "oh, there's no /preinstall backup, no big deal, skip it). However, if you use koush's recovery to restore an obsidian nandroid, koush's recovery knows nothing about the /preinstall partition and therefore will skip it, and hence skip restoring a vital part of the obsidian boot system.

I hope that answered some of the questions people were having.
[Droid X Android Development] blkblt412:
I noticed in the changelog for Obsidian that a fix for the battery issue was found. Will there be an update released soon to resolve this issue? I'm currently running the beta and would like to continue doing so but if it will be a while for the fix I'm probably going to have to go back to a different ROM in the interim. My battery went from 100% to 80% in less than an hour this morning. Other than the battery life I really like this ROM so far. I'm willing to test as well if needed.