yashsingh1/xdaforums huggingface dataset:
[Captivate General] Dave the Knave:
Exactly what I was thinking. It doesn't make sense to be trying so hard to fix that when a simple one click Odin will remedy the problem.

Sent from my Captivate
[Vibrant Q&A, Help & Troubleshooting] distortion:
I just rooted and unlocked mine via instructions here. I am getting an "E" icon, does that mean edge? How do I get 3G to work like people are claiming. I am outside of Orlando with a VERY reliable 3G connection normally.
[Vibrant Q&A, Help & Troubleshooting] air2k57:
It won't give you 3g on att lol. Tmobile uses different bands and vibrant does not support att 3g bands, just edge. You should have gotten the captivate, which is made to work on att 3g. It's just a given, almost every phone is like that. You can take most att phones, unlock them to work on Tmobile, but will only get edge, same thing with Tmobile phones. Can't be done...
[Vibrant Q&A, Help & Troubleshooting] ekramsam:
Apparently it supports AT&T 3G bands

Source:

http://www.engadget.com/2010/08/22/confirmed-galaxy-s-unlock-codes-are-stored-in-your-phone-vibra/

Now the question is if the vibrant has both 850mhz and 1900mhz 3g bands.
[Vibrant Q&A, Help & Troubleshooting] hipmel:
I was wondering a similar thing. I saw that T-mobile roams on AT&T's networks a lot during a recent road trip, so do you think you can get 3g data speeds over those networks without the need for an ATT sim card?

Just debating whether or not to try to unlock it.
[Vibrant Q&A, Help & Troubleshooting] gsvnet:
This is really odd - have not seen a device do this before but Engadget generally doesn't lie.

So basically it works on AT&T's 1900mhz based 3G network. In a lot of areas, it could actually work with an ATT SIM once unlocked.

I'm going to give this a try a bit later and will report back how it goes in my area. I know AT&T has both 850 and 1900 based 3G here.
[Vibrant Q&A, Help & Troubleshooting] distortion:
I just took the fam out for icecream and picked up a 3G signal, but back at home on Edge...bah...
[Vibrant Q&A, Help & Troubleshooting] gsvnet:
Yeah, their 1900mhz isn't as abundant as their 850mhz signal.

The best 'half-band' solutions typically involve a device that supports 850mhz but not 1900mhz, like the HD2 T9193 or HD T8285 both of which get 3G in *many* AT&T areas
[Vibrant Q&A, Help & Troubleshooting] mrzane:
Hi peeps,

My research on various forums so far suggests to me that there seems to be contradicting reports whether or not the Vibrant works on AT&T 3G.

I'm planning on importing this phone and use it with an HSPA 850 MHz network in my country, but I'm still skeptical about reception capability of this particular phone. Some reports indicated that the phone works with HSPA 850 while others confirmed that it only works with 1900 MHz band on AT&T.

Therefore, can anybody please confirm if this phone, once unlocked, actually works with HSPA 850. Thanks in advance for any help you might offer.
[Vibrant Q&A, Help & Troubleshooting] gsvnet:
The phone definitely does not work with 850MHz.

I have a 850-only phone (HD T8285) as well as this Vibrant (1900 only) in front of me.

I just tested an AT&T SIM in both.

The T8285 gets excellent reception here, around 81dbm.

The vibrant on the other hand gets very spotty reception, ranging from 97dbm to around 110.

If the vibrant worked on 850, it would be getting similar reception. Instead it drops to EDGE a lot when using it on AT&T.

Edit: If I go outside, I can get decent 3g and good speeds:

Still, very clearly 1900 due to spotty signal indoors

This is however quite a nice surprise - it opens the opportunity to use it on AT&T's network in places where 1900 3G is solid.
[Vibrant Q&A, Help & Troubleshooting] larry996:
So it does not support 850? Secondly how do I know if I am in 850 or 1900 area?
[Vibrant Q&A, Help & Troubleshooting] gsvnet:
Most areas are going to have both if anything, so the main thing you're going to want to know is if 1900 is strong enough where you are.

Unfortunately I dont know a truly reliable way to check a specific area for whether thats the case, besides actually trying a 1900 only phone
[Vibrant Q&A, Help & Troubleshooting] DevPhone1337:
Not true, AT&T is working on moving their entire 3G network to the 850mhz band... Here in New York City they're exclusively 850mhz unless I'm mistaken.
[Vibrant Q&A, Help & Troubleshooting] larry996:
I heard that same thing. So if the Vibrant "only" does 1900.... those in 850 are SOL!

Anyone know how old this map is....?????

http://www.cellularmaps.com/att_850_1900.shtml
[Vibrant Q&A, Help & Troubleshooting] gsvnet:
They've simply re-allocated much of the 3G network to the 850Mhz band, but based on my testing (with a vibrant), they have not totally gotten rid of 1900 3G - it still exists.

The problem with that map is it doesn't differentiate between 2G and 3G.
[Vibrant Q&A, Help & Troubleshooting] GuestK0080:
I have an att sim and I can get 3g on my unlocked vibrant. You can get into the debug screen and clearly see wcdma 850 listed and it is unchecked by default. Only 1900 and AWS bands are enabled. Since we have 1900 att 3g here it works fine. I just haven't had nerve to enable the 850 in the screen to test it. But I have read reports that enabling 850 does absolutely nothing anyway since the hardware does not support that band.
[Vibrant Q&A, Help & Troubleshooting] Alex530:
Its confirmed that it gets att 3g: http://www.engadget.com/2010/08/22/confirmed-galaxy-s-unlock-codes-are-stored-in-your-phone-vibra/ My recommendation is to mess around with it.
[Vibrant Q&A, Help & Troubleshooting] rothariger:
could someone confirm the 850mhz reception?
[Vibrant Q&A, Help & Troubleshooting] millia90:
To what ive seen the vibrant comes with both 850/1900 bajds making it more then compatable with ATT 3G
[Galaxy S I9000 Themes and Apps] appelflap:
One last note: Users that have installed the previous versions should/ are adviced to download the new version from the other thread. The new version addresses the problem that one can't boot into the system because of a conflict between a particular density setting and a launcher and or widget.

The apk's attached to this post are now removed. Head over to the new thread to download the app.

Update v2.1 * addresses some problems other devices than the Galaxy S variants had with the former version. * some minor cosmetic changes. (note: I also opened a thread on the android developers forum, so other devices can profit from this tweak as well. I have decided to post my updates there and, of course, on the Android Market. The new thread can be found http://xdaforums.com/showthread.php?t=765639

Update v2.0 * Added option to turn on/off compability settings for app scaling. * Possibility to restore default density setting (the default density that is stored is the density of your screen when you run the tool for the first time). * Added helpfile * Added option to reboot automatically after changing the density.

Update v1.1: a) Optimization of code: faster, more safe b) some cosmetic changes

I created a little app to play with the LCD Density Settings as described in this thread. The app lets you set the LCD Density Setting without edditing the build.prop file (directly).

Be aware that the tweak only will work with launchers like LauncherPro. It doesn't work with Samsungs own TouchWizardLauncher. (If you insist on experimenting with the TWLauncher, make sure that you have the USB Debugger enabled to get you out of the mess ).

Screenshots

Instead of a donation you can consider to buy the app from the Android Market (0,75 euro). Search for LCD Density Changer or scan:

I will keep this app for free for download and always up to date here on this forum!

Future work

I will keep on investigating how the software environment can be made compatible with lower density settings. My intention is to update the app constantly with new tweaks and settings so that eventually it can function as a full control panel for the density tweak.

Thanks to jdsemler who discovered this tweak.

Note: if you don't want to take any risk, make sure you make a nandroid backup. Although the new version is reported to be error-free, it is always a good idea to create a full system backup before one is going to play with these kind of tools.

(also) thanks to

* bratfink for giving some very useful input

* Cutefox for bringing to our attention that turning of the compatibility mode via an app called "Spare Parts" solves the scaling problem.

* Nelson Mandela for bringing peace

* Mahatma Ghandi for his inspiration

* Bell for inventing the phone

* Samsung for the upcomming GPS fix

* and many, many others I forgot to mention.

Download history

LCD Density Changer.apk (16.3 KB, 223 views)

LCD Density Changer v1.1.apk (17.6 KB, 91 views)

LCD Density Changer v2.0.apk (28.9 KB, 264 views)
[Galaxy S I9000 Themes and Apps] jim_panse:
What are the standard values?
[Galaxy S I9000 Themes and Apps] jdsemler:
HDPI = 240 (Galaxy S default)

MDPI = 160

LDPI = 120

The larger the number, the larger the stuff on-screen is. The smaller the number, the smaller stuff is. The smaller numbers are great for getting more stuff on screen to see, like when using RSS readers to see more articles on the screen before you have to scroll.
[Galaxy S I9000 Themes and Apps] appelflap:
Yeah, it's such a nice tweak. Thanks again! Any progression on the scaling issue?
[Galaxy S I9000 Themes and Apps] jdsemler:
Nothing useful yet. I'm convinced that the /system.prop is the problem. Somehow, they are updating that file on every reboot, and it is impacting certain apps that are having the 240 value passed to them from that file, which makes them render in that set size.

Take Root Explorer for example. It runs in a very small area when not in HDPI mode on the Samsung device. I installed it on my Dell Streak, which natively is set to run in MDPI mode, and it goes full screen without issue. I then set it for LDPI, and it goes full screen again. Going to HDPI also makes no issue, so it is something that Samsung is doing, and if we can figure out what is updating /system.prop and stop it, I think we'll have it licked.

I think I'm way out of my league when it comes to debugging the Samsung's behavior though.
[Galaxy S I9000 Themes and Apps] lpsi2000:
Can someone post the original build.prop because mine seems to be 0 byte and I can see anything on the screen.

Thanks.
[Galaxy S I9000 Themes and Apps] appelflap:
nonetheless a very interesting problem. :) The thing that intrigues me is that some apps run full screen without any problem. I'm gonna decompile those apps later on to see how they have defined the layout.

BTW can you upload some of the dell streak prop files that may be relevant in this case?
[Galaxy S I9000 Themes and Apps] appelflap:
Did you use my app? Because in that case that's not good. What did you do?

Have you rooted your device, did you have busybox installed? Have you granted superuser permission?

Anyway, I attached the build.prop from my Galaxy S.

EDIT if it's right there's a copy of build.prop in the folder /data/data/com.beansoft.lcd_density_setting (or something like that). Can you look and see if that file is 0 bytes to? Otherwise, copy that back to the system folder
[Galaxy S I9000 Themes and Apps] jdsemler:
I attached my default (HDPI setting) Samsung build.prop and my current Dell Streak build.prop.

The Streak build.prop has a different fingerprint, because I'm using the 2.1 build and had to have a recognized (by Market) fingerprint to get to my protected apps.

The Streak does not have a /system.prop file, unlike the Samsung.
[Galaxy S I9000 Themes and Apps] bratfink:
System.prob

It does seem that the dpi settings in system.prop are what seems to be the issue with some of these applications. I could be that the samsung framework explicitly allows 240 as the only acceptable dpi and thus restores the system.prop automatically if it finds a different value.

In this case if someone doesnt mind flashing or is currently using that vanilla custom rom that works on the SGS (Its in its Alpha stages) then it would be interesting to see if the changes are permant and accross the board when using vanilla. Anyone care to try?
[Galaxy S I9000 Themes and Apps] appelflap:
Makes sense. Question though, when do all these prop files load? Don't think it will work, but can an app at boottime change the system.prob values so that it doesn't affect the modified dpi value?
[Galaxy S I9000 Themes and Apps] asrrin29:
tried using your app to change the setting to 220, and the at&t logo pops up, the samsung sound goes off, and the screen stays blank. I can't get access to su in adb shell and all I can do is reboot. what's going on?
[Galaxy S I9000 Themes and Apps] appelflap:
I suppose you have a rooted device with the whole sjabang (SuperUser and Busybox) installed on it?
[Galaxy S I9000 Themes and Apps] asrrin29:
yes. when I try to use su I get

[1] Segmentation fault su
[Galaxy S I9000 Themes and Apps] lpsi2000:
Yes, the app is what I use and I can't even get su to work under adb shell. It looks like I am going to need to re flash.
[Galaxy S I9000 Themes and Apps] F_L_Abs:
Used the app, same result....

Reflashing now... Normally not a problem for me to reflash, but I didn't get to backup my text messages and notepad -_-

Oh well...
[Galaxy S I9000 Themes and Apps] appelflap:
that's weird. all I do in the app is trigger some shell commands like "su" and "busybox cp". But can't you try to do the rooting procedure again by "apply: /sdcard/update.zip" in adb?

Makes me wonder if there are any users, except me, who got this app working? :)
[Galaxy S I9000 Themes and Apps] asrrin29:
not sure that's going to work, because I can't get super user access until I grant it permission without a ui.
[Galaxy S I9000 Themes and Apps] appelflap:
I'm sorry ... The Android SDK isn't the best toolkit to do such low level system hacking. The security levels are high, and to break them you have to do all kind of weird stuff. Anyway, I changed the first post and put a extra warning in it.
[Galaxy S I9000 Themes and Apps] asrrin29:
Is there a way to use Odin 3 to restore the files changed?
[Galaxy S I9000 Themes and Apps] appelflap:
Ok, I understand. BTW what launcher do you use? And did you apply the tweak earlier without my app? Sorry, but I have to debug this app otherwise I take it back asap.
[Galaxy S I9000 Themes and Apps] lpsi2000:
I like that idea, better yet is there a way using the update.zip to replace the bad file with a good one?
[Galaxy S I9000 Themes and Apps] lpsi2000:
I did not apply the tweak earlier without your app. I did have usb debug on because I keep that way all of the time. And I was using LauncherPro.
[Galaxy S I9000 Themes and Apps] asrrin29:
I use Launcher Pro, and I did not use the other fix, just your app.

I know nothing about update.zip or any other way, but if someone else could package it, I would definitely test it. I'd rather not reflash my phone if I can help it.
[Galaxy S I9000 Themes and Apps] appelflap:
I will look into this. Actually seems like a good idea, because one doesn't have to be rooted with this method to copy files to the system dir. But I have to go, have to look into it later.

EDIT: In the GPS epic fix in this forum there is an example of an update.zip file... Maybe you can use that. One doesn't need to set any file attributes, just copy the build.prop to the system dir. (jdsemler posted a copy of the original build.prop from the Captivate earlier in this thread)
[Galaxy S I9000 Themes and Apps] F_L_Abs:
I thought about using an update.zip, but I don't think you can even put it onto the internalSD at this point...

Then again I didn't even bother trying hard enough. Reflashed and did the fix manually. The setting for 200 looks great so far!
[Galaxy S I9000 Themes and Apps] asrrin29:
I can still push an update.zip I think, someone just needs to package it for me and I can try.
[Galaxy S I9000 Themes and Apps] Case_:
Try these update.zip's, they SHOULD work, at least when using ClockworkMod recovery. You can see the firmware version the build.prop is taken from. Sorry, but these are the only ones I've got here available right now...
[Galaxy S I9000 Themes and Apps] lpsi2000:
Wow, Recovered from this

Got it to work. That is good because I almost re-flash and I would have had to reinstall everything. use the attached and rename it to update.zip, copy it to the root of your sdcard. Reboot into recovery mode then reinstall packages
[Galaxy S I9000 Themes and Apps] asrrin29:
I'm trying the vibrant, though if you have a jh6 build prop that would work better. will let you know in just a second.
[Galaxy S I9000 Themes and Apps] asrrin29:
crap. what's the file structure to dump a file onto the internal sd?

I tried /sd/ and /home/sd/
[Galaxy S I9000 Themes and Apps] Case_:
/sdcard

And I don't have JH6 available, sorry.
[Galaxy S I9000 Themes and Apps] asrrin29:
vibrant file fixed it, lets just hope that it's the same as the captivate's prop file. Thanks for the help! wonder if I should try your app again, lol.

Weirdly, my swype seems to have stopped working. I restored my backup rom I made just before applying this fix and it's back to normal, but just fyi, the build.prop may have something to do with the swype, I'm not sure.
[Galaxy S I9000 Themes and Apps] Aery:
Just some Background Infos:

http://developer.android.com/resources/dashboard/screens.html

http://developer.android.com/guide/practices/screens_support.html
[Galaxy S I9000 Themes and Apps] asrrin29:
so just fyi, it seems everyone in the captivate forum is having a similar problem as me. screen blacks out after logo when the app tells us to reboot. Must be a captivate only thing. is there anything I can do to help you pinpoint the problem? I can run alogcat or test files or whatever is needed, just let me know.
[Galaxy S I9000 Themes and Apps] Bhonka:
My Galaxy S is also black screening.

Galaxy S - JM5 with samset 1.9e + ryanlagfix2-3
[Galaxy S I9000 Themes and Apps] Bhonka:
Worked on my i9000 JM5.

Cheers.
[Galaxy S I9000 Themes and Apps] appelflap:
First, glad you 've sorted it. Case_, thanks for this! Sorry for all the trouble you guys.

It would be nice when you or someone else with a Captivate can do some testing. The su error you reported was very strange. Maybe it has something to do with the busybox version that is installed on the captivate during the rooting process, maybe not.. I keep you posted, thanks in advance.
[Galaxy S I9000 Themes and Apps] Cutefox:
using jjg4 rom rooted with lagfix..

using the setting 200 instead of 160.. everything looked sooo sharp.. like retina screen!! beat that iphone4!! btw if you find any apps not behaving properly go to spareparts and switch off compatibility mode.. and you will find most apps screen res working again.. im leaving mine in this configuration.. sweeet!!!!
[Galaxy S I9000 Themes and Apps] appelflap:
THAT's IT!! Great find! Solved the scaling problem.

BTW Did use my app to change your settings? Did it work on your device.

Anyway, if I can make it work on any device I try to integrate this compatibility mode changer in this app.
[Galaxy S I9000 Themes and Apps] toca79:
You think it's possible to make it work with touchwiz?
[Galaxy S I9000 Themes and Apps] Cutefox:
no worries.. i used ur apk file to change.. i tried 160 but its messed up the notification bar.. hence 200 is the best.. i also use launcherpro for my home app rather than twlauncher.. so far so sweet.. everything looked so sharp and nice!!!
[Galaxy S I9000 Themes and Apps] appelflap:
LOL, that's the first report I get that the app is running without any problems. You have a Galaxy S I guess?

Thanks for your feedback, I now can continue my work on this app.

I've noticed that the dialer doesn't scale (maybe because the dimensions are hard-coded), have you noticed any other apps that don't scale right?

And hell yes, this is the greatest tweak ever for this device. I got so much more information on my screen with the 200 density setting.
[Galaxy S I9000 Themes and Apps] appelflap:
That's a nice problem to solve. Maybe it works with the tip Cutefox posted. I haven't the nerve to try it though at the moment. :)
[Galaxy S I9000 Themes and Apps] Piny12:
Tried it on JM5 with APK Lagfix and ADW.Launcher. Stuck on black screen at boot... Glad I made a nandroid backup a minute before.
[Galaxy S I9000 Themes and Apps] appelflap:
Thanks for testing ;) Did you checked the build.prop in the system directory before resetting the device, as suggested in the first post? Have you installed another busybox version than the one that comes with the standard update.zip rooting facility when you installed the APK lagfix?
[Galaxy S I9000 Themes and Apps] Piny12:
I'm at work actually and it seems that my nandroid backup doesnt get my phone to live again. That may be due to the lagfix I applied... No MicroUSB cable around so no more Galaxy S for me till I'm at home today :P

I'm on the newest busybox version.
[Galaxy S I9000 Themes and Apps] Toss3:
Got the black screen as well(Jm5 + Samset 1.9d + OneClickLag 2-3), but the update.zip file fixed it for me. Gonna try doing it the right way now.
[Galaxy S I9000 Themes and Apps] appelflap:
Have you checked the build.prop in the system dir. before resetting the device?

C'mon guys, some feedback please. I don't have to put this app online ... you know. I'm perfectly happy with it, because it works for me.
[Galaxy S I9000 Themes and Apps] Toss3:
Nopes, but I know it didn't work(could try it again if you want?). :) No worries man just because it doesn't work for everyone - everyone here always appreciate the work you devs do! Wasn't my intention in any way to criticize your work so please excuse me for not expressing myself properly.
[Galaxy S I9000 Themes and Apps] appelflap:
That's not a problem at all. The only intention of my reply is to get some work done here and to kick some asses :) It's just a pain in the ass to rely on "su" in an app. I can't control the outcome from within a app, so basically I can't do a thing. And, a second thing is that the shell execute possibilies are broken in the SDK I'm working with, so...

Anyway, for now I only like people to backup the build.prop (name it build.doh or something like that, not build.prop.bak) in the system directory and check the file with a tool like root explorer or astro file-explorer (free).

Also, I know there's a weird problem going on with .bak files. If a build.prop.bak exists in the system directory, things become really unpredictable.
[Galaxy S I9000 Themes and Apps] Cutefox:
yup im using galaxy s.. im glad u ever made the apk for this! made me even more appreciates my galaxy s.. dialer wont scale right.. a few apps wont scale right either.. but not to the point where the galaxy s is not usable.. i mean dialer is still dialable.. apps like ultimate faves pro for example are smaller but still usable.. but most apps scale correctly even games like asphalt using the compatibility mode tweak.. i do wish u can somehow choose which apps can be excluded using this mode that way all apps can scale right.. and u can choose which one that make use of this hack or not.. btw have u tried dolphin browser? now i can read the whole website without pinch zooming!!
[Galaxy S I9000 Themes and Apps] appelflap:
Count yourself lucky the app works for you :D

I will look into your suggestions to control the compatibilty tweak. For now, i'm going to work on the existing app and try to add some useful features to it to control this tweak on the fly.

And no, I don't use dolphin, but the tweak works also great for the standard browser. I love the fact btw that so many more items are displayed in lists!
[Galaxy S I9000 Themes and Apps] wuffa:
Spare Part compatibility worked for apps, mostly. Dialer is still out of place and none of my games work properly :)
[Galaxy S I9000 Themes and Apps] Cutefox:
which games dont work on your end? i can test for u from my side.. so far i gotten all gameloft games to work, need for speed shift also works.. will test more apps..