Swype: I can't install it. - Samsung Galaxy Nexus

I am rooted;
ROM = AKOP
Kernel=Franco
I can't install swype from the swype beta website.
I get the "not supported screen size" error.
I am pretty sure it's the newest one, but if anyone can confirm that version 2.0.26481 (13.00) is the newest version.
I don't know if it's the ROM, or if it's cuz I tried changing the screen density to 290. I changed it back to 320, but there was still an error.
Help?

You need to change back to default 320, and reboot. After that you should be good to go.
Sent from my Galaxy Nexus

I did do that. Still doesn't work.
I tried:
Downloading an app to change the density to 320, and reboot.
Change the build.prop to density 320 in the systems folder with root explorer, saved it, and rebooted.
Change the density via the unicorn rom option thing in the AKOP rom, rebooted.
EDIT: T.T Had to finally factory reset my phone in order to get swype. I tried SlideIt, but they got a ****ty algorithm compared to Swype.

After you have it installed, and run it once you can switch back to 290.
Sent from my Galaxy Nexus

Related

LCD Density Changer, changing density says apps not compatible with my device?

Hi if I change the density on me GS2 some apps no longer show up under downloaded to my phone. one example is Adobe Flash Player. I can find it in the market and it will say its installed but on top it says not compatible with my device. Does anyone know if there is a way to fix this.
No fix, just confirming the same thing, even when only changing from 240 to 220.
It's related to the new Market, the only fix right now is using a "supported" density such as 160 or 240.
Trying 160 now,seems to be ok. Thanks for the tip. TW launcher leaves a large dead spot under the screen indicator. Switched to Launcher Pro, looks good.
Change Reboot method to "killall" then apply... should work now.
Near disaster with this app. Checked compatability mode under settings, it rebooted but only showed splash screen, then went black. Tried rebooting, same thing. Could get into recovery and download modes, but nothing else. Odined stock kernel again, no change. Cleared data and cache, still nothing. Finally has the idea to Odin Zedomax V4.1, and got CWM. Restored a saved backup, and finally it booted. Odined the stock kernel again, use Titanium, and back to normal. Lesson learned-don't try compatability mode.

[FIXED] "Your Device Isn't Compatible with This Version"

IT IS WORKING NOW.
Quick background. I have the SPH-L900, but I am on Sprint's MVNO Ting. Before I activated it, I rooted it and downloaded several apps. Some of the apps are Paid apps, the others are free. During activation Ting asked if they could do a factory reset and I said yes. I never lost root, but lost all my personal information and my apps. Now the apps that I had successfully downloaded before, I cannot download now.
I do have Rom Manager Premium and Rom Toolbox Pro, if that will help solve my problem.
Be clear, because I am new to all this.
Oh, I did send an E-Mail to Cloud.TV for HD Widgets, but didn't get a reply.(2 days) Since I did pay, I hoped they would solve the problem for their app and maybe I could use that information to fix the rest.
Please help
Re: [Q] "Your Device Isn't Compatible with This Version"
I had the same problem and it turned out to be the dpi... make sure your build.prop has 320 dpi in both parts and clear cache
after you do this and install your apps you can revert to whatever dpi you want
Sent from my SPH-L900 using xda app-developers app
reinaldistic said:
I had the same problem and it turned out to be the dpi... make sure your build.prop has 320 dpi in both parts and clear cache
after you do this and install your apps you can revert to whatever dpi you want
Click to expand...
Click to collapse
It didn't work. I made sure the DPI is 320. (Yes, I had changed it to 280) I then used ROM Toolbox to wipe both caches. Rebooted and still got the error on the Play Store.
It is working now. The only thing I did, after trying everything in search, plus what reinaldistic suggested is to go to Settings and then to System Update. Then asking for an update for every choice they gave me.
I do not know if that is what worked or it was something else.

How to Change DPI to 240 on 4.3?

I had to get a new phone today as my old Note2 wifi died.
The phone is already updated to 4.3 from Sprint. I rooted and if I change the DPI to 240 the Samsung Keyboard breaks. I used Xposed on 2.1 and was able to adjust the settings for each app manually. When I used TI backup to use Xposed again it killed the phone and put it into a boot loop. I'm assuming this is due to it being out of date.
I recovered and see there is a new Xposed. Does this work on 4.3 stock roms that are rooted? I really just want Nova Launcher and a few apps to be 240dpi, or the entire phone if I have too, but I want to keep using the stock keyboard.
Thanks

Modify Lcd Density In Build.prop

I have rooted my Tab Pro 10.1 and tried to use Root Explorer to change the lcd density to 400 in build.prop. I have changed the screen density in several other devices successfully this way. But when I rebooted my Tab Pro, there were so many system errors and fc's I couldn't even get to root Explorer to change back. I had to completely restore with Odin.
Has anyone else been able to change the lcd density successfully? Any tips or suggestions?
I've tried as well on my Tab Pro 8.4" and I'm running a rooted custom rom based on stock. Had to reinstall rom.
I don't know if the errors are related to Samsung's Magazinelauncher and if changing launchers would help, I haven't tried. I've been trying to live with Touchwiz, if I can't there's no point for me to stay on a stock(ish) rom. If I decide to use CM then I'll try changing density again, maybe even try resolution change to extend battery life.
I'm using Apex launcher, so I don't think that's it. Still working to find solutions.

[HOWTO] Change DPI of your screen w/o messing up the interface

If you tried to change your screen density and ran into gfx glitches etc, this is for you. A simple how-to change your screen DPI on a LePro 3 running EUI without messing up lockscreen clock, dialer, etc.
Firstly, the two methods I knew of with which to change screen density are as follows
- (ROOT REQ) Just changeing the sf.lcd_density value in build.prop (mostly) doesnt work at all, and doesnt affect the resolution whatsoever.
- The other method commonly used, and which doesnt require root if you have access to a computer running ADB is via shell, and using WM (window manager). This one will work, and change your DPI, but will mess up the interface. This is also the method employed by many apps on play store which require root to change your DPI, hence giving the same messy result.
Well, tonight I finally managed to make it work without any glitches, misplaced text etc, all is as it should be, and I'm running 360 DPI right now (screenshots).
Root is required (alternatively you could use TWRP to replace the file, on non rooted phones, I guess). Using a root explorer, navigate to \data\property\ and find the file named persist.sys.sf.lcd_density. Open it as a text document, all it contains is a number which is your phones native DPI
Change it to whatever you like, save and reboot.
Be warned, a TWRP backup is handy, coz a wrong setting can cause the system ui to crash on boot, leaving you dead in the water. :laugh:
Cheers, works here. My lockscreen pattern is still ****ed up, its either to the left or right, not centered, but apart from that its all good.
Is it better solution than Nova Launcher?
marik1 said:
Is it better solution than Nova Launcher?
Click to expand...
Click to collapse
What are you talking about? Thia changes your device DPI, as in everything, not just home screen
@Incogn I believe that is a feature, to ease one handed unlocking, it moves the pattern to the side of the screen on which youve swiped your finger on.
I can live with the messed up dialer for now. 300dpi is perfect for me. =D
Joms_US said:
I can live with the messed up dialer for now. 300dpi is perfect for me. =D
Click to expand...
Click to collapse
Using 380 and dialer is perfect here
Anything below 380 messes up the dialer, but nothing else. I solved that one by installing the google dialer
trizex said:
Anything below 380 messes up the dialer, but nothing else. I solved that one by installing the google dialer
Click to expand...
Click to collapse
Interesting, which version? TIA
@Joms_US did it just this morning, @Abdiel1224 posted on Turbo's thread that it was possible by downloading opengapps aroma version, then install them through TWRP, selecting just the dialer and dialer framework. Sounds simple enough, but it wasnt smooth for me at all. After flashing, once booted, app called setup wizard would FC non-stop and wouldnt let me access my launcher/or anything else. After trying numerous times different gapps flashing options, restoring my TWRP backup, then flashing all gapps, etc etc, I finally concluded it was googles setup wizard that was f*cking with me....
The way i got around it was...creative. Managed to get into my recent apps, through solid explorer was able to launch titanium backup, and then force stop/freeze the offending app (google setup wizard). Et voila, after that it worked like a charm.
To save you all the headache/legwork that I had, if you should run into the same problem I did (System wizard FC on boot), just reboot to TWRP, navigate over to System/priv-app/setupwizard/ and delete setupwizard.apk
Works for me. However, the file did not exist. I just created it and put the number in. It worked great!
What is the original dpi in le pro3. I have a rom 20s by cydras and he reduced dpi...
patryk0511 said:
What is the original dpi in le pro3. I have a rom 20s by cydras and he reduced dpi...
Click to expand...
Click to collapse
I'm pretty sure it is 420

Categories

Resources