yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] justen7723:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Someone correct me if im wrong but i think, the official link is by rootbox and the unofficial link are the nightlys by formula84.

I like the LTE in the status bar.

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

Ui sound mods 3/10/13 [NOW 19 SETS!!, Zelda, Mario, Crysis, Dead Space, Mass Effect]
[Samsung Galaxy Nexus] formula84:
No Sir, thats official from Bajee...

So far Bajee has been pumping out builds for us Toro users frequently. Straight RootBox Source Sync builds will only come from me if i see a reason to (something interesting was added to source and there was no official nightly)
[Samsung Galaxy Nexus] formula84:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

I found that if you use Xposed per app DPI module you can modify android system to get the lockscreen think your a tablet and still keep 320 DPI for those not into hacked market...

Settings -> per-app settings-> Select "Android system" -> look at the screen shot for settings.

And this one is what the lockscreen looks like at stock DPI with 8 targets. Keep in mind others that lower DPI it looks even better at 280 IMO but breaks market... The trick I was using with Xposed did not last, so I'm sticking with the Android System running in 320 DPI and have certain apps running at a lower DPI.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] formula84:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

And below is what the untouched stock phone layout is.... Anyone think the shortcut icons are too small?

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] justen7723:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Ya I thought so as well

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

Ui sound mods 3/10/13 [NOW 19 SETS!!, Zelda, Mario, Crysis, Dead Space, Mass Effect]
[Samsung Galaxy Nexus] tattedupboy:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

A few days ago I posted that every once in a while my notifications would sometimes not sound and at first I thought it was because I had deleted my 0 folder. I redownloaded all my ringtones and wouldn't you know it, I'm still having that issue. The only way I'm able to get my sounds back when this happens is with a reboot. Is this happening to anyone else? Is there a fix, or at the very least, is there a way to get my sounds back without having to reboot?
[Samsung Galaxy Nexus] formula84:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Have never had this issue... What kernel?

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] t1.8matt:
if you have market issues with a lower dpi, i've been putting the market at stock dpi (320) with default screen dp, clear data, cache, force stop, enter market and hit accept, reboot. no more market issues.
[Samsung Galaxy Nexus] tattedupboy:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

AK kernel. #731
[Samsung Galaxy Nexus] formula84:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Yeah that's what I did as well including gsf and play services at 320 but it did not stick for more then a few days.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] t1.8matt:
Really? Its been well over a week and no problems. But ever since I went to 3.9.1 every one in a while an app won't update or download and I have to clear market data. Other than that, I don't get the app is not compatible any more.
[Samsung Galaxy Nexus] axi0m:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Runtastic is broken on this build.
[Samsung Galaxy Nexus] zandroid:
I haven't had that issue, but if you want to get rid of or keep from getting the 0 folder when you flash ROMs use TWRP. You will need to wipe your system and internal storage, so basically start clean when you flash a new ROM. Copy your internal storage to your computer for a backup before wiping everything.

Note, that when you do this you will need to either side load the ROM with ADB or use an OTG USB flash drive to flash a new ROM. I found OTG to be the easiest.
[Samsung Galaxy Nexus] justen7723:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Anyone else have issues with RB wallpapers??

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tattedupboy:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Deleting the 0 folder wasn't what caused the issue. Even after redownloading all my ringtones, I'm still experiencing this issue intermittently,and only a reboot fixes it. I'm looking for a way to stop this from happening, or at the very least, get notification sounds back back to working without having to go through the trouble of rebooting.
[Samsung Galaxy Nexus] jameshmiller:
If you flashed a 4.2 ROM without updating your recovery first, then you need to take zandroid's advice and start fresh. People that have deleted there"0" folder, are usually the ones that have not updated their recovery prior to jumping onto the 4.2 train. I'm just making assumptions here, so forgive me if I'm wrong.

Easiest way to update recovery - Goo Manager/menu/install OpenRecoveryScript

I don't see anyone else having the same issues you are, so that is why I am assuming you need to start fresh. Like zandroid said.
[Samsung Galaxy Nexus] tattedupboy:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

I do have the most current version of TWRP, 2.4.4.0. The 0 folder I had was from way back in November when I started flashing 4.2 ROMs before TWRP was updated to deal with the 0 folder issue. My issue with sometimes getting no sound for notifications has nothing to do with that, I can assure you.
[Samsung Galaxy Nexus] jameshmiller:
Maybe someone else can help you. As for me, I would search, if I couldn't find the answer, then I would start fresh. Considering no one else has reported this issue. GL
[Samsung Galaxy Nexus] jonstrong:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Usually, if a problem like this occurs after several hours of use, and is temporarily fixed by a reboot, there's a memory leak involved somewhere, or a process that continues to grow without cleaning up after itself. Ideally the VM should manage this, but it's not perfect.

If I had a problem like this, I'd find a memory monitor utility and start watching processes that are running to see if any of them are consuming increasing amounts of memory as a start. I just did a quick peek at the Play store for a free utility like this. I didn't look too closely, but this one is probably a good example of what I'm describing:

https://play.google.com/store/apps/details?id=pavel.ugo.cpumonitor4

...beamed to your planet from my Nexus 10
[Samsung Galaxy Nexus] justen7723:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Anyone :rolleyes:

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] formula84:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Works fine here... 3.9.1 I am using nova... Not sure if that matters

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] jameshmiller:
I just checked, and they do not appear to be loading. Could be a RootBox network problem. I think they load from the cloud and are not local files. I usually find something I like on 4walled.cc or use the Zedge app for wallpapers.

Using Nova also....weird. :)
[Samsung Galaxy Nexus] justen7723:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Yesterday and today could only get a few names to show up with no images to go with them over 4g, on WiFi they still seem to load slow.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] zandroid:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

I agree, it's probably not related to the 0 folder. I was just letting you know how to keep from getting the 0 folder in the future. I always found it a pain to deal with it every time.
[Samsung Galaxy Nexus] tifford:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

I'm getting a force close every time I try to open Rootbox Settings

:confused:

It's a fresh install of the newest nightly with 3/01 gapps
[Samsung Galaxy Nexus] jameshmiller:
Latest RootBox is official 3.9.1. Try that.
[Samsung Galaxy Nexus] formula84:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Yeah sorry I forgot to pull that build.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] tifford:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

It's fine other than that... Only thing I really use in there anyway is dpi, and I just edited build.prop, so I'm good :D
[Samsung Galaxy Nexus] jameshmiller:
FYI - 20130318 nightly is up on RootBox Goo!
[Samsung Galaxy Nexus] formula84:
Change log - http://tinyw.in/KiFP

Download (Bajee) - http://tinyw.in/qTnc
[Samsung Galaxy Nexus] justen7723:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Dark rootbox setting is nice. This has been running great for me with ak cylon 801.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] t1.8matt:
same here, running awesome with 801. had one sod but that was due to my kernel settings. that dark rootbox is the shiz in combination with BB8 mms.apk. just in case anyone wants it.

https://www.dropbox.com/s/e3t3n4ffzio8b0l/BB8-Mms.apk
[Samsung Galaxy Nexus] bajee11:
you do realize that replacing the messaging app will cause some important features to stop working or malfunction right? What's your reason for replacing it in the first place.
[Samsung Galaxy Nexus] t1.8matt:
like which functions? i replaced it because running the stock sms app with dark rootbox enabled was still a white app. and it has vibrate pattern feature. it's just what i wanted to put in, not telling anyone to put it in unless they want to.
[Samsung Galaxy Nexus] bajee11:
For starters you lose the ability to use breath MMS. Don't know if you're MMS has fixes for group participants and MMS auto retrieval. And on top of that, RootBox MMS is fully themeable by yourself if you go into MMS>Settings>Theme Settings.
[Samsung Galaxy Nexus] t1.8matt:
i don't much care about the breath sms, but it is neat. i didn't know about the sms>theme settings. i'll check that out. thanks for the info. i still do like having the vibrate pattern though. let's me know it's a text in my pocket and not an email.
[Samsung Galaxy Nexus] bajee11:
I didn't intervene here for you. It essential that you announce to other users how replacing the stock MMS by another one could potentially affect their usage. If you don't, then this thread will simply be flooded with useless bug posts due to that negligence. Better be safe than sorry right? Btw, No offence to you.
[Samsung Galaxy Nexus] t1.8matt:
good point, didn't think of that. TO ALL WHO USE BB8 MMS, IF YOU HAVE PROBLEMS, IT'S ON YOU. There we go. lol. :) And no offense taken.
[Samsung Galaxy Nexus] shorttripp86:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE][ROM][

Since MMS theme settings happen to be the current topic... Is there a setting I'm just overlooking that allows you to change the color of the text input in the send to/contact search box when starting a new conversation? If I set my background color to black, I can't see the what I'm actually entering, due to the fact that the default color of recipient search box text is also black.

Example: I typed "Domino" but you can't see the text being entered.

Samsung Galaxy Nexus Rootbox/Purity
[Samsung Galaxy Nexus] melp57:
When I set a custom icon for a Nav ring, such as screen off, it doesn't stick. I think I am doing it correctly. It lets me choose the icon, and I hit the save, but just keeps the default white icon. What am I doing wrong?

thanks
[Samsung Galaxy Nexus] jameshmiller:
I just tried mine, and it worked fine. Maybe try a another picture? Ida Know? Sounds like you are doing it right.
[Samsung Galaxy Nexus] jameshmiller:
FYI - 20130320 is up on RootBox Goo
[Samsung Galaxy Nexus] justen7723:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Just got the new nightly (3/22)....

What happened to MMS theme settings????

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] modernbummer:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

I believe it has something to do with Dark Rootbox.
[Samsung Galaxy Nexus] justen7723:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

I get dark rootbox but why not have both options???

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] formula84:
Edit : it seems like hidden navbar is not working in the latest so the below won't work till that does. Sorry for the confusion.

Anyone use PIE and hate the invisible PIE after unlock issue? I have a fix I just found... nothing in source but a user configurable option that resolves it...

So if you enable hidden navbar then enable PIE seems to fix the bug...I think it has something to do with the hidden navbar code and how it enables navbar searchlight (googlenow ring) on lockscreen then hides the navbar after unlock

when hidden navbar is enabled and PIE is enabled PIE takes precedence so they don't interfere with each other... perfect solution

I am actually quite pleased with myself right now for stumbling on this "workaround" cause I know so many people have been bringing this up all over the place in ROMs where PIE is kanged.
[Samsung Galaxy Nexus] t1.8matt:
i just responded in the carbon thread but deleted that post since it wasn't relevant to their rom, but on the 3/20 build that still does not work for me. it is still invisible after unlock.
[Samsung Galaxy Nexus] formula84:
Weird Let me reboot and check again, do you have the drag handle for hidden navbar showing? With my setup and hidden navbar enabled then enable PIE I can still see the hidden navbar drag bar but PIE is overtop of it...

Edit: Works after reboot too... I have my Navbar height set to 24 so searchlight takes up less space on the lockscreen (navbar Ring) = More Widget room.

Is your PIE on the bottom?
[Samsung Galaxy Nexus] t1.8matt:
Oh, when I read it you said expanded desktop which I thought was the one in the root box settings. I didn't try the hidden navbar in ROM control, I was just using the nav bar toggle from the power menu. I'll give that a try.

---------- Post added at 06:17 PM ---------- Previous post was at 06:13 PM ----------

Bingo. It works. I have it on the right side and turned the nav bar opacity all the way down so I can't see the little tab at the bottom and it works fine. Sometimes I activate the nav bar though while I'm typing, but it works.
[Samsung Galaxy Nexus] formula84:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Yeah i got my PIE on the bottom do I don't have that issue... With SwiftKey I set the option to show arrows on the bottom (rarely used) but what this does is push up the keyboard a bit so PIE activation area is not a problem while typing. See screen shot...

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] formula84:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] tattedupboy:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Glad to see that this works. I also have the option to hide the status bar, but that only works when I'm not on the home screen; when I'm on the home screen, then status bar is visible. Any way I can keep it always hidden when not on expanded mode?
[Samsung Galaxy Nexus] t1.8matt:
hidden nav bar in rom control does not work on bajee's 3/22 build, at least for me. just fyi for future builds.
[Samsung Galaxy Nexus] tattedupboy:
Re: [ROM][4.2.2][AOKP/CM/PA]Vanilla RootBox[03/12/13][v3.9.1][Per-App-DPI][PIE]

Is the issue of the disappearing pie while on expanded desktop mode still present?
[Samsung Galaxy Nexus] t1.8matt:
It only works with the hidden nav bar feature in Rom control, not expanded desktop in root box settings. Since hidden nav bar doesn't work, the pie workaround won't work.
[HTC EVO 3D] Shinydude100:
It's late, i get busy, but i still like to do my homework before coming forward with a question.

Unfortunately, I get the feeling my issues boil down to the fact that all my USB ports are 3.0 The issue at hand is that my sister's Evo 3D had an outdated 2.3.4 MetroPCS rom, and I was going to get her on Nocturnal's latest, I believe that's the ICS version. I don't want her on JellyBean since I don't want to hear her complain about too many things not working, and also, she's on Metro.

To my understanding, she's got her Bootloader unlocked, and her S-On (which i was at a brick wall in turning off without USB 2.0 Ports.)

HBoot 1.50

Luckily, I'm not that ignorant not to make a CWM backup of her phone before messing with it, and so it has the only working tacky outdated ROM that seems to be locked down as the only thing that wants to run on her Evo 3D.

I admit, in attempt to fix a feature for her, I broke another/ gave her an annoying force-close issue. I followed some old steps on August 28, 2012 to getting Voicemail notification to work on her MetroROM, and i suppose the Android GB versions were a tad diff, so each time her calls end, she gets force-closing issues and so forth. (It was my fault) The easiest thing I can think of is hunting down the 2.3.4 Official Rom, extract the Phone.APK from there, and push it to her phone, although I am unaware if that'll do the trick.

Anyway, that's the trouble I caused her, and so when i finally got tired of hearing her complain (for an issue i made her deal with for about..6 months? LOL (poor sister) ) I decided it was best to update her to the latest Metro Rom i could find for Evo 3D.

I would like to know what my options are (if any) assuming I had only 3.0 USB Ports to work with.

Thanks for your time!

(For now, I restored her back to the CWM backup from August 28, 2012) --Deleted all her contacts (again) :rolleyes:
[HTC EVO 3D] DjDom:
Hmm, there's a way in Windows to change the USB 3.0 to 2.0 somehow.

Try looking that up, I don't remember where I read it, but it's possible.
[HTC EVO 3D] VIRGIN KLM:
I think it's possible in the BIOS, my PC and laptop offer that option since all of the ports were USB3.0, my HTC Evo 3D is S-OFF now.
[HTC EVO 3D] Shinydude100:
No such option on my BIOS. If there's no other way to get S-OFF on a laptop that is just 3.0 ports then I'll just have to find a 2.0 usb port equipped laptop.
[Transformer TF300T Q&A, Help & Troubleshooting] Smeech99:
I tried searching but couldn't find anything:

I have an unlocked/rooted/custom ROM'd TF300T. I don't have any issues, but just have a concern when rebooting or powering up: the Asus / Unlocked device splash screen sometimes becomes distorted, especially around the top left hand corner of the screen. Once it goes to the Asus splash screen, all is well. Is this something to be concerned about?
[Transformer TF300T Q&A, Help & Troubleshooting] 1dog9:
I had this happen to me it didnt seem to be a problem. I fixed it by reflashing the rom and kernel i was running after i wiped. Hope this helps
[Transformer TF300T Q&A, Help & Troubleshooting] 1dog9:
Also, are you running a tf700 kernel? That is known to cause a distortion where " This device is unlocked" is.
[Transformer TF300T Q&A, Help & Troubleshooting] Hazard17:
I had the same problem when I used Clemsyn 1,7GHz kernel.
[Networking] biggardr:
FYI

Rogers Wireless APNs

LTE- ltemobile.apn

HSPA- internet.com
[Verizon Samsung Galaxy S III] TehFlyingIndian:
As the title says, I love the functionality of AOSP type roms, yet my work needs require that I untilitze an encrypted tether. Any current non-TW roms out there that provide that? I know it's a rare commodity, but it's worth a shot. Thanks!
[Captivate Q&A, Help & Troubleshooting] saintnova:
Hey, im in Jamaica and ive got a challenge for Captivate users. No one has been able to figure this dilema out. Hopefully someone can solve this.

My captivates usb port has stopped doing anything. The details are:

1. The phone works fine and used to be rooted but the root is corrupt i think. Super user installed but the phone behaves unrooted and SU gives errors.

2. I cant flash ROMs since there is no usb.

3. Cannot sideload as the phone cant receive the AT&T OTA update since im in Jamaica.

4. I changed the USB port but same result (no charge, no connection to pc)

Im thinking the usb is bricked since the person i got it from says it charged the day before she reset the phone to give to me.

5. Cant update.zip via 3 recovery (i get e: siganture verification failed)

Can anyone figure this out!? Im thinking its impossible now. If only i could use sideload wonder machine wirelessly, then i could use Z4ROOT or Visionary to flash.
[Captivate Q&A, Help & Troubleshooting] [Face]TigerBite:
Maybe stupid question. But do u have the Samsung USB drivers installed? If yes then probably need a new USB cord. Try a different one.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
You went through this thread yet? http://xdaforums.com/showthread.php?t=1953930
[Captivate Q&A, Help & Troubleshooting] saintnova:
1. Ive tried several usb cables but no response.

2. If the phone wont even charge via usb then im not sure installing the drivers will help.

3. Whats the jig supposed to do? Get me into download? If so, when i hold the volume buttons and power button, it takes me to a screen that gives me the options to clear cache, user data, and reinstall packages. but when i try various update.zip files i get the signed verification failed message. I think this is recovery mode but ill search for how to get into download mode. Does download mode work without usb?

Tried entering download mode but i guess since the usb doesnt work, thats why it doesnt function.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
If the phone doesn't charge through the usb, you need a new usb port on your phone. If you know how to solder, you can probably get one for cheap and look at videos on how to do it. Otherwise, you can go through mobiletechvideos.com to get it replaced.

As for download mode, it's vol down + power.
[Captivate Q&A, Help & Troubleshooting] saintnova:
The usb port was changed but the result was the same. All this happened after the person wiped the phone before i got it. Before that the usb port worked fine. Trying to put it into download mode now but a question again is, will it work if the usb port doesnt work?

Tried volume down + power but phone just boots as normal.

Im on froyo 2.2
[Captivate Q&A, Help & Troubleshooting] saintnova:
The other way to fix this would be sideloading but ATT doesnt allow the OTA where im at. Anyway to upload Z4root quickly to googleplay then download it? LOL. My phone only allows apps from google play.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
There's a security feature, you can uncheck it in your settings.

And holding vol down+power while phone is off will boot it in download mode (don't have the usb plugged in). Also, formatting and resetting a phone doesn't break usb. My guess, the job wasn't done correctly.

Have you tried it on other pc? Perhaps your pc usb port is defective.
[Captivate Q&A, Help & Troubleshooting] saintnova:
1. There isnt any such setting on the ATT version of my captivate. I guess that option came after the sideload OTA update.

2. I hold the volume down button and the power when the phone is off but it just boots up as normal. No download mode. Is there a site that keeps update.zips or OTA update that can be pushed?