I changed my lcd density to 160 because of the market issues now whenever i boot up my nook freezes and i have to reboot at least 4 times for it to work. Anyone know the cause of this?
EverythingNook said:
I changed my lcd density to 160 because of the market issues now whenever i boot up my nook freezes and i have to reboot at least 4 times for it to work. Anyone know the cause of this?
Click to expand...
Click to collapse
What rom are you on?
---------------------------------
Sent from my LG Optimus V using Tapatalk
CM7 7.1 stable
What gapps version are you flashing? Or, what version of market do you have?
skwalas said:
What gapps version are you flashing? Or, what version of market do you have?
Click to expand...
Click to collapse
I have the newest market.
EverythingNook said:
I have the newest market.
Click to expand...
Click to collapse
3.1.5?
Have you flashed newest gapps (0828)?
skwalas said:
3.1.5?
Have you flashed newest gapps (0828)?
Click to expand...
Click to collapse
Yes 3.1.5 and i have the newest gapps.
I changed my lcd density to 160 ...
Click to expand...
Click to collapse
By default, 7.1 stable should already have set it to 160 dpi, why you need to do it again?
votinh said:
By default, 7.1 stable should already have set it to 160 dpi, why you need to do it again?
Click to expand...
Click to collapse
Because after i installed 7.1 market wasnt at 160 dpi. I tried clearing data and cache and reflashing the gapps and 7.1 but that didnt work
How did you change your lcd density?
mgs526 said:
How did you change your lcd density?
Click to expand...
Click to collapse
The LCD Resolution app
EverythingNook said:
Because after i installed 7.1 market wasnt at 160 dpi. I tried clearing data and cache and reflashing the gapps and 7.1 but that didnt work
Click to expand...
Click to collapse
Are you all set or still need help?
Anyway, the bold above, doesn't make any sense to me.
votinh said:
Are you all set or still need help?
Anyway, the bold above, doesn't make any sense to me.
Click to expand...
Click to collapse
Sorry, no its not fixed. I installed CM7 7.1 stable on my friends nook, his nook is at 161 dpi but his market looks like its at 160 dpi and he has no "Your device is incompatible". Whenever i installed 7.1 stable and flashed the new gapps that was not the case for me.
Don't panic.
Go slow.
Why do you keep saying the NC is set to 161 dpi with CM7.1?
AFAIK, it set to 160 dpi by DEFAULT.
What I talked about is the NC lcd_density. Forget about the Market for now, let focus on the NC lcd_density.
I suggest you start over again, from scratch, installed CM7.1 then check out the lcd_density. Don't do anything else, don't use any app to change it.
votinh said:
Don't panic.
Go slow.
Why do you keep saying the NC is set to 161 dpi with CM7.1?
AFAIK, it set to 160 dpi by DEFAULT.
What I talked about is the NC lcd_density. Forget about the Market for now, let focus on the NC lcd_density.
I suggest you start over again, from scratch, installed CM7.1 then check out the lcd_density. Don't do anything else, don't use any app to change it.
Click to expand...
Click to collapse
It says its 160 but the market is still messed up. Should i uninstall the market with titanium backup then reflash gapps?
1. make sure you get lcd_density set to 160 dpi (should be by default)
2. what version of Market do you currently have? 3.1.3 or 3.1.5?
EverythingNook said:
It says its 160 but the market is still messed up. Should i uninstall the market with titanium backup then reflash gapps?
Click to expand...
Click to collapse
Go into Manage Apps from the CM7 menu on task bar.... scroll down to market and clear data (thaqt should also clear cache and cause it it to stop... the force stop button will dim).... press "n" button to go back to home screen... launch market.... you should have to accept terms of service again.
It should work now.
I have 3.1.5 and it says its set at 160.
DizzyDen, I have tried that already but thank you. I think im gonna uninstall the market then reflash gapps.
With 160 dpi set and v 3.1.5, I just about to say exactly what Dizzy said above.
Do make sure CLEAR DATA and CACHE of MARKET itself, not Market Updater. NO NEED to uninstall anything, no need to uninstall Market.
After that, just execute Market again, agree the term and sign in again.
Reboot if needed.
votinh said:
With 160 dpi set and v 3.1.5, I just about to say exactly what Dizzy said above.
Do make sure CLEAR DATA and CACHE of MARKET itself, not Market Updater. NO NEED to uninstall anything, no need to uninstall Market.
After that, just execute Market again, agree the term and sign in again.
Reboot if needed.
Click to expand...
Click to collapse
I have already done that. Im thinking i might have messed something up when flashing 7.1 stable
Related
So i just got the NC. Rooted it with manualnooter, emmc CWM, CM7, and everything runs good! Now my market updated and i cant download certain apps! I found some help on the search button(yes, people do use it!) and i havent found anyway to solve my problems. Here are some of the solutions i have found and tried and havent worked!
http://forum.xda-developers.com/showthread.php?t=1232147
http://forum.xda-developers.com/showthread.php?t=877505&page=2
If i can go back to the old market i WILL do it! Dont care for new market at all!
903tex said:
So i just got the NC. Rooted it with manualnooter, emmc CWM, CM7, and everything runs good! Now my market updated and i cant download certain apps! I found some help on the search button(yes, people do use it!) and i havent found anyway to solve my problems. Here are some of the solutions i have found and tried and havent worked!
http://forum.xda-developers.com/showthread.php?t=1232147
http://forum.xda-developers.com/showthread.php?t=877505&page=2
If i can go back to the old market i WILL do it! Dont care for new market at all!
Click to expand...
Click to collapse
Edit your build.prop and change the screen density to 160.
I have the exact same issue and have tried all the "solutions" I have found, nothing so far helps.
I'm running of an SD, CM7 nightly from August 28, one of the later kernels.
Everything works fine except this #$%^$ market.
Ideas?
Since none of my apps seem to be affected by screen density I simply uninstalled the marker updater app and kept the old market. If you are already on the new market. Uninstall the updater app first and then go into the applications settings for the market and uninstall the last update. Clear the data and cache as well.
doncaruana said:
Edit your build.prop and change the screen density to 160.
Click to expand...
Click to collapse
Can you direct me to what needs to be changed in build.prop? Thanks.
There should be a line that says
Code:
qemu.sf.lcd_density=161
Just change the number to 160.
I did that, thought there might have been some other line to be edited there that they weren't mentioning. Thanks.
MadMikeSS said:
I did that, thought there might have been some other line to be edited there that they weren't mentioning. Thanks.
Click to expand...
Click to collapse
Start up the Terminal. Become Superuser by typing "su" and return.
Remount /system as read/write by typing:
mount -o remount,rw /system
Edit /system/build.prop and change qemu.sf.lcd_density=161 to be 160.
Then go to Applications, force-close Market and clear all its data (but do not uninstall).
Then reboot.
If this still did not work, search the Internet for the latest Google Apps zip from August, 2011. If you have Rom Manager it's the newest one listed under "Download ROM...Google Apps" window. It's even newer than what is offered on download sites that have Phiremod or CM 1.7 RC.
When Market first starts it might ask you to install a list of apps. Choose a couple of them. I've observed that Market will then automatically upgrade itself again when I do this. I've been using the newest Market app with the 160 DPI setting for about a week now and it has never stopped working. I suspect that it might be the newest Google Apps that fixes some of the magic.
Note that some things, like the on-screen keyboard, have letters that are too large due to this setting. It's really supposed to be set to 170 DPI but 160 DPI is the setting that makes the Market app work again.
patruns said:
Since none of my apps seem to be affected by screen density I simply uninstalled the marker updater app and kept the old market. If you are already on the new market. Uninstall the updater app first and then go into the applications settings for the market and uninstall the last update. Clear the data and cache as well.
Click to expand...
Click to collapse
I don't see how to uninstall the market updater. It doesn't have the option in "manage applications" to uninstall it, and it doesn't show up in astro. How can I get rid of it?
kat3k said:
I don't see how to uninstall the market updater. It doesn't have the option in "manage applications" to uninstall it, and it doesn't show up in astro. How can I get rid of it?
Click to expand...
Click to collapse
I used Titanium Back. It is free in the market.
patruns said:
I used Titanium Back. It is free in the market.
Click to expand...
Click to collapse
Thanks. I did finally see it there after I installed Root Explorer. Having access to everything on the NC, it makes me want to root my phone.
This is probably the same problem I have experienced.
Yesterday I install CM7 bootable to a new SD card I just bought. After everything installed, I found that several essential google apps, like maps, youtube, are not able to install. Market complains that my device is not compatible.
However, these apps run properly in my old SD card. The Market from the old card has been updated, and it seems it's working properly as well. I'll check the DPI setting on both card. I don't think they are different because I installed both card through the same build.
Question: how to clone the entire old card to my new card? They are from different brand, old Kingston and new Sandisk. I've used WinImage32 to clone the Kingston to the Sandisk, but it doesn't boot at all.
Guys, how do I download script manager from the market to a NC? It keeps telling me it is not compatible with the NC.
Thanks in Advance!
You need to upgrade your CM version to 7.1 stable (if you are using CM) or change your dpi to 160
Sent from space
Thanks for your reply.
I am currently running CM 7.1 stable.
I just tried downloading it and no problems downloading here. Try clearing market cache and data and see if that changes anything.
Sent from space
Tried that and no go--I am stumped! Now I cannot even find it with search in the market. This is a first for me. Any other ideas?
Jimbo67 said:
Tried that and no go--I am stumped! Now I cannot even find it with search in the market. This is a first for me. Any other ideas?
Click to expand...
Click to collapse
Use my IMEI generator and set it up to do the following build.prop edits:
;Device_Manufacturer =
Device_Manufacturer = Samsung
Manufacturer_Device = GalaxyS
Device_Model = NC_CM7
;LCD_Density = 240
LCD_Density = 160
Since the blank Device_Manufacturer and LCD_Density = 240 lines are commented... it will run making the edits and make sure LDC_Density is set to 160 for your Nook.
Jimbo67 said:
Tried that and no go--I am stumped! Now I cannot even find it with search in the market. This is a first for me. Any other ideas?
Click to expand...
Click to collapse
Did you try the market website? That should show all apps.
gallahad2000 said:
Did you try the market website? That should show all apps.
Click to expand...
Click to collapse
I did, and it does show script mgr.--but it still asks for a device and when I click on it it says Nook Color--when I click that it says not compatible with NC. Is there a way to tell the market that you are trying to download to a different device?
Jimbo67 said:
I did, and it does show script mgr.--but it still asks for a device and when I click on it it says Nook Color--when I click that it says not compatible with NC. Is there a way to tell the market that you are trying to download to a different device?
Click to expand...
Click to collapse
See my post 3 up...
DizzyDen said:
See my post 3 up...
Click to expand...
Click to collapse
Thanks Dizzy, I somehow missed your post above
Your generator worked like a charm, now market works well!
Also was able to get script mgr. and move on through the V6 supercharge.
Thanks a TON!
Any memory optimizer will do the same thing supercharge does. I set my minfrees to 10,20,200,250,300 because I like lots of free memory yet plenty for the apps I do run. Multitasking isn't all that great on GB so why have so many background apps running? Anyways.
Hey guys,
Recently I rooted my Nexus 4, put on CWM and SuperSU.
Problem now is that I can't install apps like Words with Friends or Dead Trigger. I'm on JB 4.2 Build No. JOP40C.
I was believing that it has something to do with me changing the dpi to 260, I use an app named Density Changer from the Play Store.
weird, I have supersu installed and can play Dead Trigger without any problems
I read somewhere that your issue might be caused by a program called Density Changer. Have you tried uninstalling it?
firstness said:
I read somewhere that your issue might be caused by a program called Density Changer. Have you tried uninstalling it?
Click to expand...
Click to collapse
I'll try that now. I'll also clear cache too.
You kind of answered your own question there. DPI change.
It's the DPI change that causes it?
qwahchees said:
It's the DPI change that causes it?
Click to expand...
Click to collapse
99% sure, yes. CWM and SuperSu or the mere presence of Density Changer shouldn't have an impact.
I just undid everything, cleared dailvik and cache and still fc's.
:/
Change DPI back to stock if you haven't already. Clear data on the game so it detects settings again.
estallings15 said:
Change DPI back to stock if you haven't already. Clear data on the game so it detects settings again.
Click to expand...
Click to collapse
I did, still no dough
qwahchees said:
I did, still no dough
Click to expand...
Click to collapse
you have to clear google play store settings (after reset dpi settings, should be 320), then reboot.
Melissan said:
you have to clear google play store settings (after reset dpi settings, should be 320), then reboot.
Click to expand...
Click to collapse
Okay I fixed it. I went to build.prop and just edited lcd.density
Everything works now
Next time you change DPI
Install the Multi DPI play store
Will work for sure
Hi,
I have just changed density on my Nexus 4 with LCD Density Modder and now I can't boot :-/.
My N4 is rooted and I have CWM. I tried to go to CWM and wipe data/Factory reset and it didn't work.
How can I fix this?
Thanks for your help.
Re-flash the ROM.
How?
go back into clockworkmod and click "install from sd card" and select the ROM zip file.
Ok, but how can I transfer the rom to mobile? Debugging mode is disabled :/
Problem solved. I did it with NEXUS 4 TOOLKIT (option 9)
So, we can't change density on Nexus 4? Or have someone managed to do this successfully? How?
I have just edited build.prop manually and it works.
But Google Play Store doesn't show every app :-/. I have 280 density setting. I have tried to fix it with LCD Density Modder, but i can't install GSF. Does anyone know solution that really works?
ankerek said:
But Google Play Store doesn't show every app :-/. I have 280 density setting. I have tried to fix it with LCD Density Modder, but i can't install GSF. Does anyone know solution that really works?
Click to expand...
Click to collapse
Flash a modified multi DPI play store.
Sent from my iPad 4
ankerek said:
But Google Play Store doesn't show every app :-/.
Click to expand...
Click to collapse
play doesnt work with nonstandard dpi and so do many other apps. dont do this to your poor phone. paranoidandroid was originally written for this purpose, it started with hybrid engine. every single issue has been cleared out for you. things work, no compromises, nothing crashes, nothing to small because you choose size on per app basis, size is separate from the layout which you pick from a list of actual UI's an app offers, you treat the phone interface in the same way as any regular app, set it to this and that size and UI without trashing anything else, you control all this with a handy little panel thats giving you the changes you've made on sight. i lost half a year of my life to help getting android get over this build.prop nonsense - make use of it. it has found its way into a couple of roms, so flash something else if you hate pa, but use hybrid engine for goodness sake, there is no alternative that can compare to it. :highfive:
ran into the same problem as op, running liquidsmooth rc2 with franco. everytime i changed the lcd density to anything other than stock and rebooted i got stuck in a boot loop and had to go into twrp and wipe cache/dalvik just to boot. changed lcd to stock and no more boot loops. sucks because i really like running 280.
Just wanted to mention that the official Android L launcher works on our Tabs
I have attached the .apk
You have to change the build.prop to get the new UI
set ro.build.version.codename to L and reboot
It works also as a system app, no FC's.
Supports 4.2.2 / 4.3 / 4.4.2
Note: You have to update/download the latest Google Search app and Google Mail may force closing
Proceed with caution, you may end up having boot-loops !
Thanks go to:
@ivan123
@Ashutos1997
thanks
good to know, thanks!
Not quite...
UA,
hi i would ask that you amend your post to mention this launcher requires google search to be functional.
As per your instructions I did so and the launcher does not register as system app without google search,
and on regular install call for updated google search to function.
thank you for reading.
m
moonbutt74 said:
UA,
hi i would ask that you amend your post to mention this launcher requires google search to be functional.
As per your instructions I did so and the launcher does not register as system app without google search,
and on regular install call for updated google search to function.
thank you for reading.
m
Click to expand...
Click to collapse
Thanks,
I have added this information
Works perfectly!
notice
UAdeveloper said:
Just wanted to mention that the official Android L launcher works on our Tabs
I have attached the .apk
You have to change the build.prop to get the new UI
set ro.build.version.codename to L and reboot
It works also as a system app, no FC's.
Note: You have to update/download the latest Google Search app
Thanks go to:
@ivan123
@Ashutos1997
Click to expand...
Click to collapse
Hi I noticed after doing this sometimes gmail would force close untell I reboot
dsilx said:
Hi I noticed after doing this sometimes gmail would force close untell I reboot
Click to expand...
Click to collapse
Thank you for that information. (This problem appears on my tab, too)
UAdeveloper said:
Thanks,
I have added this information
Click to expand...
Click to collapse
Doesnt work for me, it just keeps rebooting.
Im running the latest version of Nolekat.
DuceTheTruth said:
Doesnt work for me, it just keeps rebooting.
Im running the latest version of Nolekat.
Click to expand...
Click to collapse
Did you first download the latest Google search app ?
Screenshots?
F1Fanatic27 said:
Screenshots?
Click to expand...
Click to collapse
Good idea,
will post them on friday.
UAdeveloper said:
Just wanted to mention that the official Android L launcher works on our Tabs
I have attached the .apk
You have to change the build.prop to get the new UI
set ro.build.version.codename to L and reboot
It works also as a system app, no FC's.
Supports 4.2.2 / 4.3 / 4.4.2
Note: You have to update/download the latest Google Search app and Google Mail may force closing
Thanks go to:
@ivan123
@Ashutos1997
Click to expand...
Click to collapse
When you say, "set it to L", you ARE referring to the property value under where it says ro.build.etc.... correct?
jonstowe78 said:
When you say, "set it to L", you ARE referring to the property value under where it says ro.build.etc.... correct?
Click to expand...
Click to collapse
Yes, you have to set the value for ro.build.version.codename to the letter L.
PHP:
ro.build.version.codename=L
I've installed this apk, changed the build.prop, and after a reboot, the tab just keeps rebooting every time it starts a system. i cant get to do anything, it just reboots again and again... help??? :S
crnjaz said:
I've installed this apk, changed the build.prop, and after a reboot, the tab just keeps rebooting every time it starts a system. i cant get to do anything, it just reboots again and again... help??? :S
Click to expand...
Click to collapse
What device do you have?
What Android is it running?
Did you deinstall, Touchwiz (Samsung stock) launcher?
Did you set the launcher as a system app?
UAdeveloper said:
What device do you have?
What Android is it running?
Did you deinstall, Touchwiz (Samsung stock) launcher?
Did you set the launcher as a system app?
Click to expand...
Click to collapse
gt-5200, 4.4.2 deodexed stock...
No i did not, i just installed given apk (it updated current google now launcher), and changed build.prop
anyway, i tryed to fix premisions, and delete the google launcher from the app folder from recovery, but still rebooting continued.
and while trying to fix the build.prop from the recovery, i funked the system a bit, so a reflashed the whole rom again, so I'm back at the begining... (no new launcher, but tab works fine...)
crnjaz said:
gt-5200, 4.4.2 deodexed stock...
No i did not, i just installed given apk (it updated current google now launcher), and changed build.prop
anyway, i tryed to fix premisions, and delete the google launcher from the app folder from recovery, but still rebooting continued.
and while trying to fix the build.prop from the recovery, i funked the system a bit, so a reflashed the whole rom again, so I'm back at the begining... (no new launcher, but tab works fine...)
Click to expand...
Click to collapse
It seems like, you screwed up inside the build.prop
Or, it only works as a system app on 4.4.2, that would be bad.
I will check that, thank you for trying and sorry if you got any problems because of me.
UAdeveloper said:
It seems like, you screwed up inside the build.prop
Or, it only works as a system app on 4.4.2, that would be bad.
I will check that, thank you for trying and sorry if you got any problems because of me.
Click to expand...
Click to collapse
well, i used root explorer to edit build.prop, and i didnt change anything except switch REL with L...
but i guess build.prop was screwed somehow, it managed to stay on for a while before the reboot a few times (for about half a minute), but it kept giving the fc error screens for play services, mail, etc, and then restarted again.
I will try it in a few minutes!
UAdeveloper said:
Yes, you have to set the value for ro.build.version.codename to the letter L.
PHP:
ro.build.version.codename=L
Click to expand...
Click to collapse
When first time I installed this launcher I changed the build.prob as u said....
And after a week I came to know that gmail is get fc's every time
I saw the log of gmail and came to know that the changes made in the build.prob coz of that gmail app getting fc...
Then I changed it to og value in build.prob
From then everything is working totally fine
So I don't think that we should change the codename, without changing it everything is working fine...even gmail app
Sent from my SM-T311 using XDA Free mobile app