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.
Related
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?
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
I'm brand new to the SIII, switched from a Rezound yesterday. I'm rooted, unlocked and running CleanRom. I know others have gotten Google Now to work but I'm at a loss for device specific install instruction! This is what I did and had no luck, kept getting force closes and black screens: downloaded the m7_velvet.apk to extsd....rename as 'GoogleQuickSearchBox.apk.....replace in /system/ app....change the permissions to read,write,execute/read,execute/read,execute....rebooted. Any help would be awesome!!
mike1984jr said:
I'm brand new to the SIII, switched from a Rezound yesterday. I'm rooted, unlocked and running CleanRom. I know others have gotten Google Now to work but I'm at a loss for device specific install instruction! This is what I did and had no luck, kept getting force closes and black screens: downloaded the m7_velvet.apk to extsd....rename as 'GoogleQuickSearchBox.apk.....replace in /system/ app....change the permissions to read,write,execute/read,execute/read,execute....rebooted. Any help would be awesome!!
Click to expand...
Click to collapse
Go to here
http://forum.xda-developers.com/showthread.php?p=30809177
Download the flashable zip of your choice for the ARMv7. I recommend the online only version. Then flash it in cwm.
Sent from my SCH-I535 using xda app-developers app
Dont know what post I was reading that was telling me to just install the apk, but what I was trying to install earlier was now obviously just the update apk. Works fine now, thanks!!
I just installed it today. I think it's a little silly that the back button doesn't work to exit the app. Others having issues with that?
dunderball said:
I just installed it today. I think it's a little silly that the back button doesn't work to exit the app. Others having issues with that?
Click to expand...
Click to collapse
Yes that's a common problem, but you have to remember is from jb ported back to ics. It's really good for a port!
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Yes that's a common problem, but you have to remember is from jb ported back to ics. It's really good for a port!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Very true, not going to complain too much and all I had to do was drop a few files. I renamed all the other folders/files it was supposed to overwrite so all is good, didn't need to take a nandroid or anything. Pretty nifty feature to have and takes stock rooted one step closer to JB.
dunderball said:
Very true, not going to complain too much and all I had to do was drop a few files. I renamed all the other folders/files it was supposed to overwrite so all is good, didn't need to take a nandroid or anything. Pretty nifty feature to have and takes stock rooted one step closer to JB.
Click to expand...
Click to collapse
Ya, i loved it on my razr and on my stock rooted s3. But i finally just went with a jb rom
Sent from my SCH-I535 using xda app-developers app
EDIT: Google Now is located under just Google
I like the black keyboard in blackbean. Is there a way to make my keyboard black like that? or could someone post the keyboard from blackbean so I could install it on my s3.
thanks!
edit - just had an idea and unzipped an blackbean download folder. I found the system files but i cant find keyboard. I thought ive seen somehwere that latinIME or something like that isthe keyboard. I installed it through apps installer and i still have the same keyboard.
any guidance?
ddurandSGS3 said:
I like the black keyboard in blackbean. Is there a way to make my keyboard black like that? or could someone post the keyboard from blackbean so I could install it on my s3.
thanks!
edit - just had an idea and unzipped an blackbean download folder. I found the system files but i cant find keyboard. I thought ive seen somehwere that latinIME or something like that isthe keyboard. I installed it through apps installer and i still have the same keyboard.
any guidance?
Click to expand...
Click to collapse
I think its samsungime.apk but I could be wrong
Sent from my cm_tenderloin using xda premium
jbeitel said:
I think its samsungime.apk but I could be wrong
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
ah, im sorry.
Im currently running AOKP. thats probably important.
i just tried to copy and paste the apk into system using astro and it made me overwrite the file, but when i went to use it it was still the regular keybaord. is it incompatible? or is there another way.
ddurandSGS3 said:
ah, im sorry.
Im currently running AOKP. thats probably important.
i just tried to copy and paste the apk into system using astro and it made me overwrite the file, but when i went to use it it was still the regular keybaord. is it incompatible? or is there another way.
Click to expand...
Click to collapse
Not sure what keyboard aokp uses. Maybe look for aospime.apk
Sent from my cm_tenderloin using xda premium
im not sure either.
this is the first time ive ever tried something like this.
am i going about it the right way?
ddurandSGS3 said:
im not sure either.
this is the first time ive ever tried something like this.
am i going about it the right way?
Click to expand...
Click to collapse
If black bean was touchwiz then no
Sent from my Android powered HP Touchpad
I think black bean is based off of aokp. So I thought this would be easy
Sent from my Galaxy Nexus using xda app-developers app
this is the only thing missing from my new setup, any help?
this is what i am looking for.
all you have to do is drop the LatinIME.apk in your system\app folder....replace it, fix its permission then reboot...after you try to use the keyboard, it will pull up the voice keyboard...close it then do it again and you should see your blackbean keyboard....i use it with whatever ROM im running at any given time
I installed it through apps installer. It didn't work the first few times but did after. It doesn't stayb installed though. I reinstall on every reboot or so
Sent from my Galaxy Nexus using xda app-developers app
ddurandSGS3 said:
I installed it through apps installer. It didn't work the first few times but did after. It doesn't stayb installed though. I reinstall on every reboot or so
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Must be installed to system/app and permissions set to rw-r-r for it to stick on boot. Sounds like it is in data/app.
prdog1 said:
Must be installed to system/app and permissions set to rw-r-r for it to stick on boot. Sounds like it is in data/app.
Click to expand...
Click to collapse
i installed and ti said this is a system app, do you want to overwrite or something like that. So i think its going to the right location.
i fixed permissions in CWM, ill have to search for a way to set permissions, that must be different.
edit: downloaded solid explorer went to fix permissions and it woudnt let me do the combo you provided.
i got rw-r--r
Hope this helps those looking for the latest Apps from 4.2. A big thanks to the original posters!
Please read the individual threads carefully, paying attention to any issues mentioned and following the installation as recommended.
Please remember to hit the thanks button for those who originally got these over to our device!
Please let me know if I have missed anything!
4.2 Keyboard with swipe gestures:
http://forum.xda-developers.com/showthread.php?t=1965696
4.2 Camera + Gallery app with gesture based settings and PhotoShere
http://forum.xda-developers.com/showthread.php?t=1965492
4.2 Clock with timer/stopwatch/alarms
http://forum.xda-developers.com/showthread.php?t=1971736
4.2 Launcher
http://forum.xda-developers.com/showthread.php?t=1973323
4.2 Gmail with swipe to archive/delete & pinch to resize [This is now available direct from the Playstore]
http://miui-germany.de/forum2/index.php?page=Thread&threadID=6082 or in post #2 below!!
Many thanks to s10shane for spotting this glaring omission!
here is the new gmail app apk as well u can add to ur list. i found it here.. http://miui-germany.de/forum2/index.php?page=Thread&threadID=6082
s10shane said:
here is the new gmail app apk as well u can add to ur list. i found it here.. http://miui-germany.de/forum2/index.php?page=Thread&threadID=6082
Click to expand...
Click to collapse
How do I install this,cause I get signature fault.
Sent from my HTC One S using xda app-developers app
Thanks for this. Though the 4.2 cam doesn't record videos. just thought I'd let everyone else know.
Sent from my HTC VLE_U using Tapatalk 2
I would re-download it and try again, does the issue arise from flashing a zip or are you pushing it manually to /system/app?
Sent from my HTC One S using Tapatalk 2
FatherD said:
I would re-download it and try again, does the issue arise from flashing a zip or are you pushing it manually to /system/app?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Ive tried pushing and flashing.
Flashing every zip found on XDA for the 4.2 camera.
It records fine. But the recorded video doesbt play.
It reads 'video can't be played' and then it gets deleted. :/
Sent from my HTC VLE_U using Tapatalk 2
Which app are you using to play it, look for MX player in the play store, let me know if you get a different result!
Sent from my HTC One S using Tapatalk 2
Oops! Major oversight as i am using it already lol. Will update op a bit later. Thanks.
Sent from my HTC One S using Tapatalk 2
Elloco305 Does this work for you http://d-h.st/QTY
FatherD said:
Elloco305 Does this work for you http://d-h.st/QTY
Click to expand...
Click to collapse
I'm going to flash an. Aokp build to test this.
I reverted to sense last night
Update. Sadly it doesn't. I can record and view my ffc videos but not with the back camera.
Sent from my HTC VLE_U using Tapatalk 2
qzem said:
How do I install this,cause I get signature fault.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
not sure lol. i just tried to install it but this is what i got (check the photo) . but in his video it showed the gmail app worked perfect. my phone isnt rooted at the moment so idk why it wont install.
Edit: you need to be rooted to install the gmail apk. i found the steps on how to install it here.. http://www.androidpolice.com/2012/1...ed-gmail-4-2-apk-with-pinch-to-zoom-and-more/
If you are getting random force closes thier is a 4.2 Gapps package floating around that you can flash in cwm or twrp
actually here it is i forgot i posted it in the AOKP forum earlier.
http://forum.xda-developers.com/showthread.php?t=1971526&page=2
blackhartct said:
If you are getting random force closes thier is a 4.2 Gapps package floating around that you can flash in cwm or twrp
actually here it is i forgot i posted it in the AOKP forum earlier.
http://forum.xda-developers.com/showthread.php?t=1971526&page=2
Click to expand...
Click to collapse
I'm installing this one right now
http://androidspin.com/2012/11/06/d...re-apps-in-one-zip-file-for-the-galaxy-nexus/
EDIT: Everything seems to be working great.
I flashed the one from @KillDroidHack and now I have FC with gmail and Google Play Store says always "Server error"... Do you know how to fix this?
wanxu said:
I flashed the one from @KillDroidHack and now I have FC with gmail and Google Play Store says always "Server error"... Do you know how to fix this?
Click to expand...
Click to collapse
Back up all you're stuff and do a full wipe then install the package from el smurfos post
Sent from my HTC One S using xda app-developers app
2Tone5 said:
Back up all you're stuff and do a full wipe then install the package from el smurfos post
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
FYI, one thing I've noticed about this zip is that it may install some apps in non-standard locations, such as gmail in system/app. Since this is different than other gapps packages (gmail is usually not included, so is installed via market to data/app), the CM backup script won't keep this from ROM flash to ROM flash unless you follow up with this app package flash again.
This link includes a zip with everything from 4.2, http://d-h.st/wBX
Sent from my HTC One S using xda app-developers app
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
And here's the new wallet for those who are interested http://d-h.st/DSY
Sent from my HTC One S using xda app-developers app
Anyone have any issues with the 4.2 Play store? I can't figure out why this is happening, but out seems only a handful of my apps are compatible. I had originally changed my LCD.density to 210, and then read that it had to be set to one of the non-custom numbers of 160 or 240, so I changed it to 160 (for fun), but it appears I have the exact same problem.
I never had an issue with the play store or apps requiring 160 or 240 (though I know some apps and games won't be compatible unless the LCD.density, the model, and manufacturer are changed in the build.prop file)... So the 160 or 240 setting seems incorrect.
Anyway, I have tried clearing data/cache for the play store, and the same thing for Google services framework (and reboot), but still have no change.
Could it be anything else in my build.prop file?
I am running Baked Black Bean (a JB 4.1.2 AOKP ROM).
Any thoughts or help are appreciated!
P
Sent from my HTC One S using xda premium
Don't like the keyboard. When I swipe, it wont show my swear words, such as ****, ****, ****, and so on, even though I saved the words to my dictionary. **** always shows as duck and I can never type ******. I will stick with Swype Hopefully Android will allow to swipe custom saved words in the future / official release.