yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] diablo009:
The best place to find any info abt any ROM/kernel would its OP. Try looking there.

Plus there won't be so much use of anyone compiling the differences 'cos a new version would be out every now n then. This is one of the reasons why there is no such thing.

Rather than asking for something generic like this, u could ask more specific questions like say. That way u wud get ur answers sooner.

I am with this. Cos a kernel that works on mine might not give the same results on urs.

1. wifi always has phone searching for it all time the screen is on. So keep it in when screen turns off, or the option u selected.

2. Themes are personal choices. Based on the ROM u choose, u can select theme of ur choice, or make a theme urself. There are guidelines posted.

3. Most ROMs now are 2.2.1. Would be mentioned in the OP.

4. Custom ROMs cannot guarantee that. Devs take all care and iron out issues when they find or when someone tells them abt them.

Check out a few ROMs and settle for one that suits u. And if u plan on putting on custom ROMs, don't bother on keeping ur hands clean. I think I flashed more than a dozen different ROMs before settling for what I am on now. And since I now found what suits me best, been sticking to it.

This is the normal process most people follow here.
[Captivate Q&A, Help & Troubleshooting] kangi26:
Unfortunately, mcord11758 and diablo009 are right.

The differences are minimal, and you need to research each ROM. The very basics are.

MOST roms right now are running Froyo 2.2.1. Some are still 2.2. The JPY, JS3, JS5, KB1(Stock 2.2) Are, for lack of a better definition, are build numbers.

What you'll need to do is, quite frankly, read up on one that has your interest, flash it and if it doesnt work well for you try another. Each Captivate may respond to a ROM differently to the ROM/Kernel/Modem combination. So you literally have to try it
[General Questions and Answers] VB2008er:
Hi,

I have Android 2.2 Froyo on my i900 Omnia! Now I would like to install apps from the market place, but the Internet does not work on the Omnia. Can I download the apps on the PC? And there are Android for WVGA, WQVGA, etc. different versions?

Please help!
[General Questions and Answers] Omnichron:
You could download them to the PC, then transfer them to your device in USB storage mode.:)
[General Questions and Answers] VB2008er:
But HOW can i download them?
[General Questions and Answers] Omnichron:
You mean from the Market Place? I would suggest installing the Android Emulator on your PC then download an Android Virtual Machine that has the Android Market installed and voila!(start downloading). Then you can extract the APKs from your virtual machine.:)
[General Questions and Answers] VB2008er:
I dont know about the emulator, thanks!
[HD2 Android Q&A, Help & Troubleshooting and Genera] cariebjam:
Everything on the ROM works great , however I'm having an issue getting the camera to work it keeps saying no sd card found ......

I'm not sure what the setup is suppose to be on the SD card,

I've tried fat32 primary then ext 3

then fat32 prim them fat 32 again

anyone help me out
[HD2 Android Q&A, Help & Troubleshooting and Genera] paolo.dc:
Had a similar problem with another build which worked well but it couldn't find the SD where it(self) was installed.

I have tried 3.2.2 and the camera works fine so probably it is better to just reinstall the OS.

I don't understand why you had an ext3 partition I did use just a fat32 and it worked fine. :)

Paolo
[HD2 Android Q&A, Help & Troubleshooting and Genera] epic1si:
it's my understanding that you should start with a nice clean format so format the whole sd card.

then get a partition program of your choice that can do what is needed.

move resize the first primary fat32 so that you have unallocated space of 1024. that space then needs to be assigned primary ext3. then format and that's what i did with my card and all seems fine.

then format and all should be good at least that's what i did with the partition program.

maybe your sd card isn't reading right i also read some cards were hit or miss on rafdroid.
[HD2 Android Q&A, Help & Troubleshooting and Genera] cariebjam:
I've tried different cards from different manu's still nothing tried formtaing differently same result, not sure what I'm missing
[HD2 Android Q&A, Help & Troubleshooting and Genera] sepma:
Not sure if you solved your problem. I had the same issue with SD RAFDROID 4.2 on a 16GB class4 SanDisk microSD card.

original partitions were:

FAT32 - 64K block size - primary

ext3

linuxswap

RAFDROID didn't detect an SD card when it came to camera and other operations that were SD dependant.

I used minitool and changed the partitions to a single FAT32 partition, with 32K bloxk size and set to primary and it worked like a charm ... this build is really good!

You may wanna backup the folders on your SD to your pc.
[Vega Accessories] xjarl:
In my hand for Zpad, I don;t know if it if fit for vega....
[Vega Accessories] andrewdolphin:
Looks nice - can you measure it?
[Vega Accessories] kdeezy:
Yeah i'm thinking about buying this for the advent vega. What do you think of it?
[Vega Accessories] dkampo:
Don't buy i buy one for 57$ from dhgate.com and advent vega is to big. I was lucky because a friend of mine has gtablet and i sold it to him same price. Is the best case i have ever see high quality and the best is the 3 position of the angle.

Sorry for my bad English

Cheers
[Vega Accessories] kdeezy:
Thanks for the heads up
[Vega Accessories] yioti:
I thought the gtablet was the same size as vega?
[Nexus One Q&A, Help & Troubleshooting] Zmydust:
Ever since the gingerbread update and new Google maps version, my nexus one "gps" icon in the notification bar has been popping up throughout the day. So I began checking under "running services" and now Google Maps is constantly running, I am 100% positive this was not the case before because I checked it repeatedly throughout the day while monitoring battery life like an OCD patient.

Does anyone know the reasoning behind this?
[Nexus One Q&A, Help & Troubleshooting] NexusDro:
try signing out Google Latitude and see if the problem persist.
[Nexus One Q&A, Help & Troubleshooting] sitinon327:
I've noticed it since they updated to Maps 5.1. Its definitely related to Latitude. If signing out doesn't solve your issue, I have an apk for Maps 5.0 that you can use. I rolled back when 5.1 first came out. I'm gonna see how much 5.2 caused maps to stay running.
[Nexus One Q&A, Help & Troubleshooting] Zmydust:
How do I sign out of latitude? I have never used this service.
[Nexus One Q&A, Help & Troubleshooting] NexusDro:
If you have never used this service, then you don't need to sign out. Under Google Maps option do you see "Latitude" or "Join Latitude"? If it is the latter, then you don't have to sign out anything. If you see "Latitude", click that and go to your Latitude privacy settings to sign out.
[Nexus One Q&A, Help & Troubleshooting] baseballfanz:
Long press back button can kill any app you want.

Just turn it on in Applications>Developement
[Nexus One Q&A, Help & Troubleshooting] pfmiller:
Not in Gingerbread you can't, I don't have any such option.
[Nexus One Q&A, Help & Troubleshooting] baseballfanz:
Check again, it's a GB feature.

Settings>Applications>Developement>Stop app via long press

Anyhow I always use back button to exit out of any "GPS" related applications
[Nexus One Q&A, Help & Troubleshooting] Zmydust:
That option is NOT in my applications>development folder either, check your info.

That said, what I am looking for is a way to disable latitude/google maps from constantly restarting itself in the background and staying on and now using 2-5% of my battery everyday even though I am not using the program. I know how to kill it under running services but it always restarts now.
[Nexus One Q&A, Help & Troubleshooting] Namuna:
That 'Stop app via long press' is actually a CM feature, not Gingerbread. It was introduced with CM6, which predates GB.
[Nexus One Q&A, Help & Troubleshooting] pfmiller:
I figured as much. It seems enabling that could cause problems. How well does it play with apps like Browser which have their own action defined for long press on back?
[Nexus One Q&A, Help & Troubleshooting] baseballfanz:
My bad, though it was a GB feature since it was not under CM settings
[Nexus One Q&A, Help & Troubleshooting] albundy2010:
Do you have any other apps or Widgets that use the GPS while updating? Like a weather widget or something?
[Nexus One Q&A, Help & Troubleshooting] Zmydust:
none whatsoever
[Nexus One Q&A, Help & Troubleshooting] dreamerworx:
I have the same issue - never used Latitude, Long-press to kill Maps and still when I go into Applications/Manage Applications/Running - Maps is still there!? Even tho it doesn't appear in my Advanced Task Killer app?

There should be a way to exit this app properly?! I use it from time to time and going deep into menus is no good.

Froyo with CM6 here...
[Nexus One Q&A, Help & Troubleshooting] iolinux333:
bump for an old thread, same issue with my gsm RAZR running 2.3.5 stock. i have signed out of latitude, it always restarts!
[Touch Diamond, MDA Compact IV Themes and Apps] pumpido:
Hi guy I used to have some application that allows me to change what diamond will do when I click somewhere on display. Example the X on right corner close app and I used to have set than when I click on battery icon next to the X I could set than it did the same as original X icon. Not open a battery.

Problem is I can not remeber which application it was :((((

can anyone help me ? thank a lot
[Kyocera Zio M6000] sinisin:
So it seems to me that trying to read other threads about using fastboot is that it's pretty specific to the phone you're using. None of the other fastboot threads work for me when trying to get fastboot to load up on the comp here. I have it installed, have the path right, and can't get it to stay up. It pops up, runs a ton of script and closes. I never get a chance to type anything in to any line anywhere, muchless actually send a command. I need help and am totally lost
[Kyocera Zio M6000] sinisin:
So so lost

I am totally lost and have absolutely no idea which direction to be going to learn this stuff. Any links to useful info for our phone, or anything you can find or tell me or whatever is apprechiated. I believe the problem is in the SDK, since I can never get the command screen open for more then a second. Or I may just be a total idiot. Should I be booting into fast boot on the phone and then plugging in, or plugging in then booting up? Do i have to open fastboot on the computer first or second? Or do I even open fastboot on the computer. Simply put I cannot get the phone and computer to link up, or keep a dialog box open on the computer end to send commands thru. :confused:
[Kyocera Zio M6000] sinisin:
Ok so Ive gotten as far as knowing that I have fastboot on the computer and ADB. Now I cant figure out how to get the device to register. I uninstalled and reinstalled drivers as all the reading has told me to do. When I boot into fastboot on the phone, and plug in, the google fastboot driver recognizes the phone is there but ADB isn't coming up. In all of the reading I've done in this case it says to uninstall all drivers associated with the phone and plug it in while in fastboot. I did this, twice, to no avail. I then reinstalled all the drivers and am still stuck at not being able to get my device recognized by adb
[Kyocera Zio M6000] Sorry_8D:
You have to access those through a command prompt.
[Kyocera Zio M6000] sinisin:
basically if it was working I may not know. I have no idea what happens or how to use fastboot or adb. but I think it should do something when I plug the phone into the usb in fastboot. it should bring up a command window for telling the phone what to do right? or do I have to do something to get the command window open. as far as i can tell everything is working like it should. :confused::mad::eek:
[Kyocera Zio M6000] sinisin:
Ok this is where I must be lost. shouldnt there be a window to type the prompt in to?

YEAH NEVERMIND
[Kyocera Zio M6000] Eofhan:
Black background, no skaterboarders?

Hello.

Slowly learning noob. I have a Zio from Cricket (as yet unmodified), running Android 2.2.1. I'm a Mac user (OS X 10.6, if it makes a difference).

I've downloaded adb, and confirmed it's working by using "adb devices" to identify my phone.

I've downloaded fastboot-for-mac. I've been able to reboot my phone using "fastboot reboot". BUT, the command "fastboot devices" returns "??????????????? fastboot". :confused:

I'm wondering if my phone's actually in fastboot mode. I power-off the phone, then simultaneously press-and-hold the Send (green) and End (red) buttons. After a few seconds, I see a black screen with white writing. I do not see the white screen with 3 skateboarders that my reading here, and Google Image search, leads me to expect. I assume I'm doing something wrong. I haven't discovered what, though. Advice would be appreciated.
[Kyocera Zio M6000] sinisin:
When you boot up with end/send the Zio boots in to fastboot yes.....
[Kyocera Zio M6000] Eofhan:
Thanks!

That tells me I am in fastboot. Any suggestions about why "fastboot devices" returns only a string of question marks?

I don't want to proceed with rooting, etc., if I can't even get fastboot to identify my device.
[Kyocera Zio M6000] bryanskinner:
You should beable to root without fastboot just dl universal androot from market and run. I personaly would wait til u have a chance to use a windows based pc to run fastboot and install spz0 2.1 rom.
[Kyocera Zio M6000] sinisin:
Sounds like a environment variables path issue. Running Windows 7?
[Fascinate General] Terror_1:
Just a little observation here but it seems lime less is going on wjth our new mod.... maybe because posts all have a home now, don't know but I like it.
[Fascinate General] bobloblaw1:
I thought this was a MOD as in something to do with the phone.... /sigh

This couldn't have gone in our new Mod's introduction sticky? :confused:
[Fascinate General] Terror_1:
Yeah I noticed that after the fact.
[Xoom General] velazcod:
Alright, first of all, this is an internal device, I will not be using these changes on my own device.

We use tablets (previously Galaxy Tabs) in our office for employees to use an internal application. Our application manages its own navigation, and users do not need to access anything else other than the application. I made it a home screen launcher so it's the first thing that loads. On the Galaxy Tab (Android 2.3), I'm also hijacking all the hardware buttons in the device and I can properly secure the device.

However, on Android 3.0, there are no hardware buttons anymore, and you cannot hide the system bar, I have no way to secure the device if the system bar is always there. I understand why it needs to be there, but this is really killing me.

I have 3 options:

Root the device, try to disable the system bar by editing the framework-res.apk --- Already tried this, unsuccesful since I couldn't find anything in there.

Wait for Android 3.0 to drop in AOSP, build my own custom rom which hides the system bar and do my own modifications on it.

Build Android 2.3 from AOSP for the XOOM -- this will be a lot of work, and I would need help, is anyone interested on helping me with this?

Thanks everyone.
[Xoom General] kenhunt:
Downgrading to 2.3 might be your best bet, wish 3.0 AOSP would hurry up, want to get somethings working differently as well myself. Let us all know if you downgrade and how it went! Wouldn't mind trying to sneak the shut off animation onto 3.0 if possible.
[Xoom General] velazcod:
Yeah, I haven't gotten into it yesterday, but the only thing I'm concerned about running 2.3 on the Tab is the whole issue with Dual-core support, not sure if I would even be able to do it thanks to that, but I'll see. I'm also trying to call a few contacts to see if we can get into some kind of agreement with Moto to try to get the source code early... we'll see...
[Xoom General] bwcorvus:
Have you tried running a different launcher? They allow you to hide system bars on the old android os...might work on 3.0
[Xoom General] velazcod:
Yeah, that won't work, the system bar is part of the framework, it's very very low level, you can't hide it since it allows the user to navigate through the device. Before 3.0, devices were required to have hardware buttons, that's not a requirement anymore because of this system bar, it will always always be there.
[Xoom General] destroyerbmx:
Atrix runs 2.3 and the same processor
[Xoom General] velazcod:
True, hopefully they release the kernel source soon so I can take a look and see if I can try to make 2.3 work on the XOOM with the same kernel that's working with 3.0.
[Xoom General] fletch33:
here is Tegra 2 with many options running various versions of 2.2 and 2.3.

you should reach out to GoJimi over there.
[Xoom General] angermeans:
I'm pretty sure atrix is running 2.2.
[Xoom General] bigrushdog:
u can't do anything until source drops. You need baksmali for framework and custom recovery to flash.
[Xoom General] BartJJ:
I think your best bet would probably be changing the DPI settings somehow (Like they did for the HC build on some phones to get the tablet version) and it would cause you to go into the "phone" version of HC (Doesn't have the system bar) then I would say modify the volume buttons and lock button long presses to recreate the home/back/multitasking buttons if you really want them (such as they have done for the i*hone android ports because ios is dumb and has 1 button). Just a suggestion and honestly I have no idea if this would work.
[Xoom General] carnegie0107:
I'm sure the system bar has a process you can kill with root. I know the status bar can be killed this way on 2.3. Watch logcat and see what you can find. Anyone know more on this?
[Xoom General] B Dizzle:
Porting 2.2 from the g-tab maybe. Similiar hardware I think.
[Xoom General] bwcorvus:
Just installed lcd denisty on mine and put it at 240 from the default 160...the system bar was gone.
[Xoom General] BartJJ:
Glad to see it worked now hopefully the OP sees it. GL to all
[Xoom General] ftgg99:
Could you please check your /system/build.prop to see whether the lcd density app has added any code?

I usually tweak density directly through this file but the code isnt there atm on my xoom.
[Xoom General] arrtoodeetoo:
I tried changing the density yesterday and was disappointed to discover that the LCD density wasn't in the build.prop. adding the line of code didn't work, either.

XOOM'd from the XDA app.
[Xoom General] bwcorvus:
Looking at the date on my build.prop it hasn't been modified. And just to be sure i looked through the file, nothing in there.
[Xoom General] velazcod:
Huh, I wasn't receiving notifications on email even though I'm subscribed for instant notifications...

anways, will try the density trick, but that seems like a pain in the butt to redo all the layouts in our app, but that is a very very clever idea, might work.

Update: Yes it works, but only if you use one of those apps, not when editing the system.prop file, anyone care to share what's exactly being edited here?

Thanks again!

Update 2: Actually, I had a typo on the line I wrote on the build.prop, if you write 'ro.sf.lcd_density=240' (or whatever density you want to use), push it and reboot, it does work as it should.
[Xoom General] dota-lina:
how are u going to press "home" or "back"?

xoom doenst have physical buttons like phones.

how do u get back to home screen if u downgrade to 2.x？
[Xoom General] ftgg99:
+1 - im also interested in how the density change is applied in these apps on a device with no string in the build properties
[Xoom General] velazcod:
I will manage my own navigation on our internal app, I just need it to work with our internal app and that's it, my app manages everything.
[Xoom General] velazcod:
Actually, I had a typo on the line I wrote on the build.prop, if you write 'ro.sf.lcd_density=240' (or whatever density you want to use), push it and reboot, it does work as it should.
[Xoom General] ftgg99:
aah, thanks a lot, just what i need!
[Xoom General] arrtoodeetoo:
When I wrote that string into the build.prop, it didn't do anything. I pushed it with 240, 192, and 160 while I kept a dime on the screen to measure any changes.

Does it matter where you insert the string?

Also, as for getting rid of the status bar, but still having it pop back up when needed, it would be great if we were able to swipe up from the bottom of the screen to cause it to reappear/swipe down to hide it again.
[Xoom General] nemith:
CM7 has soft keys if you need them and is based on 2.3.
[Xoom General] velazcod:
soft keys? where?
[Xoom General] nemith:
Actually now that I think about it, they are in the status bar. But at least the code is there, you could remove the rest and leave the the soft keys.
[Xoom General] BartJJ:
Maybe just install swipepad beta and sit your launcher on it. Gives you a way to at the very least get back to your home
[Xoom General] BartJJ:
Last idea I have is have the app change the LCD density on start and when you use the in app controls to close it tell it to reset the density before closing. Density changes don't need a reboot to be applied do they?
[Xoom General] velazcod:
I'm already showing an OnGoing Notification when I launch the app the first time, I can go back to the home through the notification bar if I ever need to go into the settings, so far it's perfect.
[Xoom General] mjbeam:
That sounds like it will work a lot better than putting black electrical tape over the system bar like I was going to suggest...
[Xoom General] velazcod:
LOL, no way jose, I need to really lock these babies down, stupid users wanting to be hackers around.
[Xoom General] BartJJ:
Meh the thing about android devices is there's no such thing as being locked down. That is so long as you don't have a locked bootloader (like the ones on the DX and D2 and such, not like the xooms) so whatever you do anyone with half a brain will probably be able to go back and fix it. If anything they could boot recovery do a wipe and install an app to change the dpi back so I'd say to really be safe put your company's app in /system/app just so they can't get rid of it too easily ;)
[Xoom General] velazcod:
Oh, I'm aware of that, don't worry the devices are also locked in a special "cage" or "bracket" with no access to any of the ports or power button. It's custom made for the XOOM and fully locked down with a special key (We used to use Galaxy Tabs but they were too small).

They are also fully monitored via CCTV cameras as well as my own custom admin security (live location tracking, remote wipe, etc), all via an internal web application, just in case.
[Xoom General] Facegarden:
Hey guys,

I saw this thread a while back, and finally decided to make an app to solve this problem. If you guys have root access on your tablets, and want to be able to hide the system bar without disabling your tablet, check out my new app! It hides the system bar in landscape mode, but shows it in portrait, so you can easily get to it to back out of your app, but when watching movies or browsing the web in landscape you can have more vertical space.

http://xdaforums.com/showthread.php?p=16850588

-Taylor
[Xoom General] velazcod:
Glad to see this being done. Mind sharing the method you are using? Thanks
[Xoom General] okantomi:
I have tried it and it works! I will use it as needed...to warch movies, mainly, but it's awesome.
[Xoom General] okantomi:
You got a free thanks...enjoy!
[Xoom General] velazcod:
I have tried it as well. Works very nice and clean. Would be nice to get a hold of the actual method so that I can play with it as well.
[Xoom General] Facegarden:
http://android.serverbox.ch/?p=306

Since you are part of why I did it. :)