CLOSE
My phone is defaulted to 240, changing it makes my phone not boot :/
jenbek said:
My phone is defaulted to 240, changing it makes my phone not boot :/
Click to expand...
Click to collapse
Explain what you did. How low did you put it?
Sent from my SGH-T769 using XDA Premium App
charlieb620 said:
Explain what you did. How low did you put it?
Sent from my SGH-T769 using XDA Premium App
Click to expand...
Click to collapse
Instead of pulling battery and chancing corruption, just reboot twice. ;-) always rename your buildprop to "buildprop.bak" so you can revert.
Cheers
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
jenbek said:
My phone is defaulted to 240, changing it makes my phone not boot :/
Click to expand...
Click to collapse
Pull a stock build prop and push with adb.......or restore your backup
Changing density will take a while to boot & most importantly always nandroid b4 messing with buildprop!
charlieb620 said:
Explain what you did. How low did you put it?
Sent from my SGH-T769 using XDA Premium App
Click to expand...
Click to collapse
I lowered it to 220, just sits at a black screen.
How long should i be letting it sit before calling it quits and restoring my backup?
Alright so my phone wont boot after changing my DPI, I dont know WHAT THE HELL A BUILD PROP is lol.... some help would be greatly appreaciated
motez23 said:
Alright so my phone wont boot after changing my DPI, I dont know WHAT THE HELL A BUILD PROP is lol.... some help would be greatly appreaciated
Click to expand...
Click to collapse
http://lmgtfy.com/?q=build+prop
Am i the only one that didn't run into any issues?
Dpi shouldn't affect boot especially such a small change..I have mine set to 200 running fine even 180 runs good. If anyone iis having trouble after you can always push a fresh build.prop through cwr with this commands.
1. Mount system
2. cd to where you have your build.prop
3. Type this in cmd(for windows)
"adb push build.prop /system/
Or terminal (Linux)
"./adb push build.prop /system/"
4. Then "adb reboot"
And viola you're back to how you were before
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
Changed mine to 200 and rebooted twice and worked just fine. Everything looks much more fancy now thanks for the post didn't know about this before
Sent from my SGH-T769
What dialer did you use, because my stock dialer does look small lol.
Edit: never mind found it, exdialer
Sent from my SGH-T769
Just a quick heads up that I have identified a bug with LCD Density Modder in the Play Store as shown in the post below:
http://forum.xda-developers.com/showthread.php?p=31237737
Sent from my MB860 using Tapatalk 2
After looking up for a couple hours trying to figure out how to change the lcd density without having problems in the play store i have had no luck i tried swapping out "Phonesky.apk" with a modded one tried editing the apk using apktool and was treated to some errors even though i followed a guide...tried using lcd density modder and ended up having to retore a backup, so yea im pretty butthurt at the moment 240 is just wayy too big for me lol
Any help would be great
Sent from my SGH-T769 using xda app-developers app
Got 180 somehow messing around with few apps from the store, but can't revert back tried changing build.prop and even though it says 240 the dpi is still 180 any solutions?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
aanonymoushuman said:
Got 180 somehow messing around with few apps from the store, but can't revert back tried changing build.prop and even though it says 240 the dpi is still 180 any solutions?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
One of the apps may have created /data/local.prop which overrides /system/build.prop. Open /data/local.prop and providing you only see the entry for dpi, you can delete the file.
Sent from my MB860 using Tapatalk 2
charlieb620 said:
Am i the only one that didn't run into any issues?
Click to expand...
Click to collapse
Nope, had no problems at all here. Didn't even have to reboot twice or wait a long time for it to boot up.
Also, I can now confirm that this works well with the first NIGHTLY of CM10.
marchingknight11 said:
Nope, had no problems at all here. Didn't even have to reboot twice or wait a long time for it to boot up.
Also, I can now confirm that this works well with the first NIGHTLY of CM10.
Click to expand...
Click to collapse
Do most of your apps not show up in play store? because with dk8 i was able to change the density fine but play store only recognized a few of my apps I know that is what normally happens is there a fix for it or? Haven't tried cm10 yet.
Sent from my CM10 Blaze
chrisxbell714 said:
Do most of your apps not show up in play store? because with dk8 i was able to change the density fine but play store only recognized a few of my apps I know that is what normally happens is there a fix for it or? Haven't tried cm10 yet.
Sent from my CM10 Blaze
Click to expand...
Click to collapse
No, everything works just fine. I didn't change the dpi in an app. I did it directly through root explorer by modifying build.prop and then rebooted.
marchingknight11 said:
No, everything works just fine. I didn't change the dpi in an app. I did it directly through root explorer by modifying build.prop and then rebooted.
Click to expand...
Click to collapse
That's exactly what I did with dk8 and it didn't work correctly with play store. Guess I'll try with cm10 and see what happens.
EDIT
So far works great even restarted a couple times to see if the apps would stay recognizable. awesome.
Sent from my CM10 Blaze
chrisxbell714 said:
That's exactly what I did with dk8 and it didn't work correctly with play store. Guess I'll try with cm10 and see what happens.
EDIT
So far works great even restarted a couple times to see if the apps would stay recognizable. awesome.
Sent from my CM10 Blaze
Click to expand...
Click to collapse
I set my DPI to 220. I did notice that Drop Box doesn't seem to work now, although I'm not sure if that's a JB issue or a DPI issue. That's the only app I've found any problems with.
UPDATE
I reverted back to 240 and now dropbox works again. I guess it's a problem with the dpi change. Anyone know how to fix it?
Related
I just rooted my phone using the clockwork recovery method and have been trying to use LCD Density and it doesnt work at all. All it does it save the setting but doesnt do anything. Anyone have a fix for that?
myunitisz said:
I just rooted my phone using the clockwork recovery method and have been trying to use LCD Density and it doesnt work at all. All it does it save the setting but doesnt do anything. Anyone have a fix for that?
Click to expand...
Click to collapse
The developer probably needs to update it to work with Gingerbread. There's a lot of differences under the hood with our NS, even if it actually looks a lot like Froyo.
Have you contacted the developer? Here's his website, and there's always an email link in the Market page for an app to report problems and make requests.
Thanks I just saw that it doesn't work guess ill wait for an update.
Sent from my Nexus S using XDA App
Check out my videos... it works for me and others on gingerbread.
did it just work for you right off the bat or did you have to do something?
U have to root your phone... then it works.
I did root it that's the weird part it just won't work
Sent from my Nexus S using XDA App
myunitisz said:
I did root it that's the weird part it just won't work
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thats strange.... My phone worked once I rooted. I change the settings to 180-200, press the button, and it reboots with new settings.
I'm having the same problem...
Sent from my Nexus S
I Have a Samsung Galaxy s 4g on tmobile and i rooted the phone the other day using the one click root thing and i was working for a while until I downloaded Root Tools of the App Market For $1.50 when i did that i saw that it had an option to increas screen density so I choose one of the options and rebooted My phone because that what it asked me to do
After that my Phone booted up fine but when I went to the home scree my Phone vibrated and the error apperred it says
Tha application TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly. Please Try again
I have done a master reset on the Phone and still Nothing keeps doing it i cant even accses the Settings on Phone bacause the errror Prevents me from doing anything to the Phone
Please can anyone Help me ???? is there anything i c an do to save my Phone?
Flash a ROM using odin, cheout the development thread.
Sent from my SGH-T959V using XDA Premium App
fknfocused said:
Flash a ROM using odin, cheout the development thread.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Thanks i Fixed my phone a Few Hours later after posting got desprate and started reading around and ended up Flashing the Rom seems to work fine now thanks
Glad to hear your back up and running.
Where did you find that rom...i would love a link
Sent from my SGH-T959V using XDA Premium App
de1packers said:
Where did you find that rom...i would love a link
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
cmon dude, member since 08 and using prem. app, READ or SEARCH
http://forum.xda-developers.com/forumdisplay.php?f=1068
Lol im totaly new to the Root scean and From what i can tell This website isamong the best i have ever seen still kinda of an Iphone 4 guy but i an loveing my galaxy and as far as the link thing gose I used one Posted by a Site Member and just used oddin its the stock rom + root
Is there a way to un root my Phone whitout haveing to flash it?
fknfocused said:
cmon dude, member since 08 and using prem. app, READ or SEARCH
http://forum.xda-developers.com/forumdisplay.php?f=1068
Click to expand...
Click to collapse
he only has 2 posts though lol. In regards to the author of this OP I think I would avoid changing the density via an app, you can do it manually via the property files I think, but again probably a risky venture if you aren't too aware of how it works.
Additionally, some apps don't work well when the density is changed others may but some dont lol.
joedeveloper said:
he only has 2 posts though lol. In regards to the author of this OP I think I would avoid changing the density via an app, you can do it manually via the property files I think, but again probably a risky venture if you aren't too aware of how it works.
Additionally, some apps don't work well when the density is changed others may but some dont lol.
Click to expand...
Click to collapse
Yeah kinda figured that one out the hard way lol but im just happy to have my samsung up and running again
joedeveloper said:
he only has 2 posts though lol. In regards to the author of this OP I think I would avoid changing the density via an app, you can do it manually via the property files I think, but again probably a risky venture if you aren't too aware of how it works.
Additionally, some apps don't work well when the density is changed others may but some dont lol.
Click to expand...
Click to collapse
KD1 ROM's do NOT like changing the screen density via app. The LCD Density Changer App and others does not seem to work well.
Yet again, Google Chrome Beta is broken after the latest update. I have ICSSGS RC4.2 and just updated Chrome Beta to the latest release. And as before, this update fails the Chrome Beta to launch on my Cappy... so beware...
I am using my old copy as before until someone figures out how to fix it... ... again...
Running 4.0.4 AOKP build 32 and it works with no problems.
Sent from my glitched ICS Captivate using XDA App
Have you tried editing your build.prop, which was the easiest fix for the previous chrome issues?
Sent from my glitched ICS Captivate using XDA App
cmilldrummin said:
Have you tried editing your build.prop, which was the easiest fix for the previous chrome issues?
Sent from my glitched ICS Captivate using XDA App
Click to expand...
Click to collapse
I can and I will but what should the build.prop entry be to allow Chrome to load properly?
The thing is, I can find the new update with no issues. It installs fine, it just refuses to open. It hangs and then dumps me to the main window.
So, can someone give me suggestions as to what the right build.prop entry should be and I will try it.
Thanks
Look at your build.prop and the line that says ro.build.id= should match the line that reads ro.build.display.id=. If either one says gingerbread edit it to match the other and reboot your device.
Sent from my glitched ICS Captivate using XDA App
Chrome is working for me on my Captivate, running Slim ICS (even though Chrome is fairly buggy and annoying in one or two places).
cmilldrummin said:
Look at your build.prop and the line that says ro.build.id= should match the line that reads ro.build.display.id=. If either one says gingerbread edit it to match the other and reboot your device.
Sent from my glitched ICS Captivate using XDA App
Click to expand...
Click to collapse
Ok. So my build.prop shows as such.
ro.build.id=IML74K
ro.build.display.id=SGH-I897-user 4.0.3 IML74K eng.onecosmic.20120204.223407 test-keys
So what has to match? Do I edit the display ID=IML74K??? and delete the rest?
Make a backup before doing so, but yes chrome beta does a check to see if that line is correct. If it's says something other then what a stock ROM would say, it won't run. So change it as you already described and it should work fine. But again make sure to make a backup of your build prop before doing so, just in case.
Sent from my glitched ICS Captivate using XDA App
cmilldrummin said:
Make a backup before doing so, but yes chrome beta does a check to see if that line is correct. If it's says something other then what a stock ROM would say, it won't run. So change it as you already described and it should work fine. But again make sure to make a backup of your build prop before doing so, just in case.
Sent from my glitched ICS Captivate using XDA App
Click to expand...
Click to collapse
I tried this change .. no success
Did you reboot after editing and make sure the change stuck?
Sent from my glitched ICS Captivate using XDA App
cmilldrummin said:
Did you reboot after editing and make sure the change stuck?
Sent from my glitched ICS Captivate using XDA App
Click to expand...
Click to collapse
I have same problem too. Updated build.prop and reboot but still not work
sbu888 said:
I have same problem too. Updated build.prop and reboot but still not work
Click to expand...
Click to collapse
Ok... It seems that some people are using what I posted as a direction to change the build.prop to make the Chrome work... Actually, what I put on my earlier post is my exact build.prop what is NOT allowing the Chrome to work... so some one needs to provide an exact line entry. Please do not use my post as this is how my stock (ICSSGS ICS RC4.2) build.prop looks like...
Sorry for the confusion.
I downloaded chrome beta, but I cannot even install it. Something about a para phase error. Idk
Sent from my Serendipity VII flashed Captivate using xda premium
I'm not sure if your situation is the same, but upgrading an existing chrome install didn't work for me. It crashed whenever I tried to open it. I uninstalled the one I had then installed the latest one from the play store. Its been working fine since. Running Slim 3.4 btw.
Sent from my SGH-I897 using xda premium
You guys should tell me why I should bother getting Chrome? Isn't stock browser Chrome based with HW accel by Samsung?
I've just tested this problem myself, and if you have LCD density set to 120 that's the cause of the issue. Set it back to 160 in build.prop or using dalingrin's CWM zip, and it works....
Fixed in latest update to Chrome... now works at lcd density of 120.
technosapien said:
I've just tested this problem myself, and if you have LCD density set to 120 that's the cause of the issue. Set it back to 160 in build.prop or using dalingrin's CWM zip, and it works....
Click to expand...
Click to collapse
BTW Chrome release works. How do you like it? Beta was superbuggy, would not render certain websites, or leave white holes.
still won't work on custom roms
Sent from my YP-G70 using xda app-developers app
arceusg said:
still won't work on custom roms
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by "won't work"? It's working on my captivate.
Ask all your questions here, please keep the development thread clean. Report Bugs there.. Ask questions here.
Screenshots look awesome!!!! I can't wait to get to work lol.
Sent from my SGH-T959V using xda app-developers app
This is the only one of the ICS roms that caused trouble. installed with tiny fonts, on reboot it went into bootloops, and I had to reinstall from stock. Everything was wiped before installation.
nazcalito said:
This is the only one of the ICS roms that caused trouble. installed with tiny fonts, on reboot it went into bootloops, and I had to reinstall from stock. Everything was wiped before installation.
Click to expand...
Click to collapse
It has tiny font cause I set its density to 200dpi by default - cause its given me best experience , if u dont like it, u can set the build.prop, at the density line to 240 and everythig should be ok (or flash another font I provided to have thicker font...other than that, I have no issues except ones from OP
Sent from my SGH-T959V using xda premium
nazcalito said:
This is the only one of the ICS roms that caused trouble. installed with tiny fonts, on reboot it went into bootloops, and I had to reinstall from stock. Everything was wiped before installation.
Click to expand...
Click to collapse
I had no problems with installation. I experienced slight lag while scrolling apps, but I'm sure the Rom just needed to cook some more before I started messing with stuff lol. I loved the tiny font, the settings menu scrolls like butter and the response time for bringing up the multitask menu is amazingly fast.
Really really nice rom!!! Love the message app.
Sent from my SGH-T959V using xda premium
I flashed the nokia font but it is not changing anything.
Sent from my SGH-T959V using xda premium
What is the hot fix for?
Sent from my SGH-T959V using xda app-developers app
@mierkat09 It's probably like a patch since its very small compared to full-flexed rom's.
mierkat09 said:
What is the hot fix for?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Read the changelog in OP bro...it fixed FC of galaxy s 4g advance settings (TV out)...read the OP carefully as I always provide all stuff there
Sent from my SGH-T959V using xda premium
daothanhduy1996 said:
Read the changelog in OP bro...it fixed FC of galaxy s 4g advance settings (TV out)...read the OP carefully as I always provide all stuff there
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Gotcha thanks, didnt think it would be in changelog
am i the only one who gets an fc when attempting to play an mp3 via the music app?
pre and post hotfix, btw.
MatisyahuSerious said:
am i the only one who gets an fc when attempting to play an mp3 via the music app?
pre and post hotfix, btw.
Click to expand...
Click to collapse
maybe you can give out a logcat when it force closes, it will help dao greatly
n1vlek said:
maybe you can give out a logcat when it force closes, it will help dao greatly
Click to expand...
Click to collapse
this is my first time grabbing a log, please excuse any extraneous data.
have you ever try rebooting the phone?
n1vlek said:
have you ever try rebooting the phone?
Click to expand...
Click to collapse
a few times a day typically - so its just me experiencing this, eh?
@MatisyahuSerious haven't had that problem. I deleted all my music but i tried test tones for ya. No error though the test is only 5 seconds.
Does it stop in the middle or at the begining?
Could be a corrupt file?
And as for the lag in the app drawer I mentioned earlier, haven't had the problem since i jumped back into the rom.
I love the theme.
Thanks.
Love it
I am loving the rom however It is not allowing me to download a lot of my apps from the playstore. I recently wanted to load my lose it app but it tells me that my device is not supported. What does the play store see the phone as? Thank you in advance.
Edit build.prop and change dpi to 240 or you might be able to do it from the actual settings menu.
That's weird because I thought I would have issues with the dpi and the Play Store but I do not. I wonder why others have it
Is it normal that i cant download Pandora on CyanogenMod 10 for my Samsung Galaxy S 4G?
No
Sent from my SGH-T959V using xda premium
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
http://forum.xda-developers.com/showthread.php?t=2044470
CyanogenMod 10 for SGS4G Q&A
Sent from my SGH-T959V using xda premium
johnadelic said:
No
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Can you tell me what i did wrong? I flashed the ROM then GAPPS. but for GAPPS there was two. One for 4.1 and the other for 4.2.1. I chose 4.1.
Idk what you did. Back up all your data with titanium backup, wipe system, data and cache. Flash ROM and 4.1 gapps and try and I stall it again.
Please post in the q&a section.
Sent from my SGH-T959V using xda premium
Why say reflash with so little information?
Ohh I forgot to tell you im not running ICS instead im on Jellybean if that changes anything.... I rather ask some question on here since it takes a while for people to reply this late at night.
Overkore said:
Ohh I forgot to tell you im not running ICS instead im on Jellybean if that changes anything.... I rather ask some question on here since it takes a while for people to reply this late at night.
Click to expand...
Click to collapse
DPI issue?
Sent from my Galaxy Nexus using xda premium
probably
http://forum.xda-developers.com/showthread.php?t=2150433 This might help with a DPI issue
Sent from my SGH-T959V using xda app-developers app
Can you explain what DPI is?
Sent from my SGH-T959V using xda app-developers app
Dots Per Inch.
DPI sets how much stuff is able to fit on the screen.
Cooptx said:
http://forum.xda-developers.com/showthread.php?t=2150433 This might help with a DPI issue
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
What does Boot Animation have to do with DPI?
That's a great question.
Well, obviously that's not a solution.
Reflash the rom, but before you transfer it to your sd card, open it up in 7zip, go to /system/build.prop. Change ro.lcddensity or something like that from 182 to 240. Then reflash. It will work.
airfluip1 said:
That's a great question.
Well, obviously that's not a solution.
Reflash the rom, but before you transfer it to your sd card, open it up in 7zip, go to /system/build.prop. Change ro.lcddensity or something like that from 182 to 240. Then reflash. It will work.
Click to expand...
Click to collapse
Why does he need to reflash to change dpi?
airfluip1 said:
That's a great question.
Well, obviously that's not a solution.
Reflash the rom, but before you transfer it to your sd card, open it up in 7zip, go to /system/build.prop. Change ro.lcddensity or something like that from 182 to 240. Then reflash. It will work.
Click to expand...
Click to collapse
Why tell someone to unzip something to make a build prop edit? There are a lot of apps on the market that will do the same thing WITHOUT having to reflash anything. Also if your gonna tell someone to play around with a .prop file make sure you get the name right. It's:
Code:
ro.sf.lcd_density
Telling people to open then edit props can easily lead to a bootloop. It's much safer for most users to use System Tuner or another equivalent program. Edit that value. Reboot. Done.
I'm sure that cm10 also has an lcd density option in the settings app that walks you through changing the lcd density to allow custom dpi settings to work with Google Play. I know both AOKP jb and slim jb have the setting
Wow man did exactly what you said and my phone LCD density looks normal like it was before I flashed it, Thank You. Would it matter if I uninstall System Tunner?
Sent from my SGH-T959V using xda app-developers app
The edit will stick if you uninstall it so it doesn't matter. It's a pretty handy app to have of you plan on playing more with your phone though. It does a lot.
Can you answer one more thing? My Camcorder doesn't work only my Camera can you tell me why?
Sent from my SGH-T959V using xda app-developers app
It's a known bug and is being worked on. If you read the ROM OP you'll see a list of all bugs.