i was trying to install swiftkey x and somewhere in the middle of failing to install it my display got stuck in landscape mode.
has this happened to anybody else?
Try the Windows Fix
Have you tried the 'Windows Fix' aka rebooting?
Do you have the option to uninstall swiftkey?
If those don't change anything, try switching to another keyboard (if you have more than one option)?
i did try rebooting and i never really got swiftkey installed. there's only the stock keyboard installed and nothing else i can find to uninstall as a test...
i can try another keyboard though.
is there any particular way of finding out exactly which apk's are installed and weeding through them?
i use root explorer and es explorer and have gone through the lists they each have but they don't exactly match up.
thank you for any feedback.
Related
Hey, i posted this in the MoDaCo 3.1 post but im not sure if it's specific to that Rom so im asking the masses here in hope someone has encountered the same problem I have...
I have a GSM Hero and am running the latest MoDaCo 3.1 Rom and decided to partition my SD card to ext3 to use A2SD. One this was complete, Linda Manager stopped working. When i open it, it stays at a black screen. I have tried reinstalling without success.
I then formatted my card again thinking it was an error or something. This however deleted all my apps (that are not part of MoDaCo 3.1) I'm assuming A2SD automatically transferred all those apps to SD. Is there anyway to control this? Any preferences anywhere?
Anyways, my main concern (as i have titanium backup, restoring the apps was a no brainer) is that Linda File manager is not working, i prefer it over Astro ans would like to know if anyone else has encountered this problem and how they solved it.
Thanks in advance
Simon
So i found the solution!
It had to do with the new version of Linda I think and a quick and weird solution is to touch the trackball......
this has to be done every time the program opens up...
AndroZip
Try Androzip from Market, it should work and I found it to be euqal or better than other smilar apps.
I know this sounds very weird, but I had the same problem (I also run Modaco 3.1, maybe it's related). Try touching the trackball when you're at the black screen..
Edit: never mind, you figured out the same thing
I've been having an issue getting Thumb Keyboard working with Calkulin's G-Tab ROM. I've tried moving the .apk to system/app with rootexplorer and changing the permissions of it to rw-r-r, but I'm not sure if there's an order I should be following in order to get it installed correctly.
Does anyone have any insight into how to get a keyboard set up with Calkulin's G-Tab ROM? They show up in the settings, but clicking the checkbox and agreeing to the popup doesn't check the box, it remains unchecked and the keyboard cannot be selected as an input method.
Any help would be appreciated.
I have done the same thing, trying to get Swype to work after installing the beta from the swype website. It actually worked swyping 2 words, and then stopped. I am still able to type like a normal keyboard. Moved from data/apps to system/apps - permissions were already changed. Enabled in settings, and then rest the tab. Thoughts?
Simplest way to get a keyboard working in any version of TnT is to go ahead and install the keyboard and then run the the settings replace, and rollback files located here:
http://forum.xda-developers.com/showpost.php?p=9532446&postcount=1
You can install the keyboard from the Market, an apk, whatever. To select it you install the settings replace file from clockwork, then boot your tablet and go to settings, language and keyboard, and select the keyboard. After that go back and run the rollback file in clockwork and your TnT settings menu will be back. You need to put the TnT settings menu back or some widgets and other stuff won't work.
It only takes about 1 minute to do this and it works great.. And whenever I say best way... It means best way for me... I'm pretty sure someone will be by to tell me there way is better.. Happens every time
Sprdtyf350 said:
Simplest way to get a keyboard working in any version of TnT is to go ahead and install the keyboard and then run the the settings replace, and rollback files located here:
http://forum.xda-developers.com/showpost.php?p=9532446&postcount=1
You can install the keyboard from the Market, an apk, whatever. To select it you install the settings replace file from clockwork, then boot your tablet and go to settings, language and keyboard, and select the keyboard. After that go back and run the rollback file in clockwork and your TnT settings menu will be back. You need to put the TnT settings menu back or some widgets and other stuff won't work.
It only takes about 1 minute to do this and it works great.. And whenever I say best way... It means best way for me... I'm pretty sure someone will be by to tell me there way is better.. Happens every time
Click to expand...
Click to collapse
this worked perfectly for me, thanks a bunch
Sprdtyf350 said:
Simplest way to get a keyboard working in any version of TnT is to go ahead and install the keyboard and then run the the settings replace, and rollback files located here:
http://forum.xda-developers.com/showpost.php?p=9532446&postcount=1
You can install the keyboard from the Market, an apk, whatever. To select it you install the settings replace file from clockwork, then boot your tablet and go to settings, language and keyboard, and select the keyboard. After that go back and run the rollback file in clockwork and your TnT settings menu will be back. You need to put the TnT settings menu back or some widgets and other stuff won't work.
It only takes about 1 minute to do this and it works great.. And whenever I say best way... It means best way for me... I'm pretty sure someone will be by to tell me there way is better.. Happens every time
Click to expand...
Click to collapse
Thanks so much!
Hi everyone,
Well, I found this topic
http://forum.xda-developers.com/showthread.php?t=751848
and have been tried to install those apk, but after install and run it, the screen just a pinch black.
Any suggestion ?
I am using rooted nook tablet.
anyone ? any suggestion is fine
I assume you mean pure black? I tried one, and that's what I saw. Perhaps there's an intent missing. I tried it in /system/app too, and same thing. I didn't reboot, though. You try that?
I tried all the method that I know, didnt work at all , and yeh , pure black beside the taskbar ( shows set wallpaper and setting option )
here is situation:
1. I had rooted 1.4.2 with not blocked OTA and my NT updated to 1.4.3.
2. It is obvious that root and some apps stopped working and some of them even disappeared from the device (like WinAmp for example).
3. I rooted 1.4.3 with SDcard method and it looked like things are fine until I started to get my apps back.
4. I used FIREFOX as a main browser with 1.4.2 update and after registering at Play store on rooted 1.4.3 I read that FIREFOX is incompatible with my device!!! What the hell?
5. Also, my NT registered at Play as NEW device, not the old one as I had - so it seems my serial changed or something has changed in the build.prop or somewhere else in the identification part of device.
6. Besides, after root, i started installing apps and it seems Notification bar has some sort of glitches - it does not clear all the messages and keeps the last downloaded file in the list...
Can anyone point me how to fix incompatibility issue?
---------------
Now, second situation:
7. I reverted back to 1.4.2 with the img file from this post: http://forum.xda-developers.com/showthread.php?t=1663836
8. But the thing is that I want to try 1.4.3 again
9. I downloaded official update from B&N and put it onto the SDCard
10. It boots and progress bar starts to move but at some point (25% of bar) it shows me exclamation icon with '!' and says "Please restart your device and try again..."
What is this issue and how it can be fixed?
Thanks in advance.
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
titanshadow said:
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
Click to expand...
Click to collapse
Can you share the links or files that get your nook back to normal state?
I've been reading and reading a lot the forum but still miss something important. Step-by-step guide would be much appreciated, if possible.
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Nook Color
Eustace2 said:
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Click to expand...
Click to collapse
This was actually a fix for Nook Color... to modify the build.prop. If you copy/pasted the entire build.prop I would think it would work.
One other thing to do is
1.) manage google play
2.) clear data
3.) uninstall updates
4.) manage google market
5.) clear data
6.) manage google services framework
7.) clear data
8.) reboot
This didn't always work and I had to do this a couple time. Not sure if which step made a difference or what order but it eventually worked. And I could see as many apps as my Captivate (Galaxy I).
Anyway, again, this worked for Nook COLOR and not Tablet. Or at least I havent figured Table yet. If you figure it out. Let me know.
My recent attempt was to copy the build.prop from Nexus and I got black screen after start up. Now I had to unbrick my device and I'm back to square one.
Good luck.. Keep me posted!!!!
@rtabasco - Good plan, but it didn't work. Even when I uninstalled the update and just used the Market app. Looks like 1.4.3 may have changed something other than the build.prop file. I'll keep poking around. It would help if the Play Store would provide a little more detail about the compatibility issue.
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
PepeladZ said:
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
Click to expand...
Click to collapse
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
Click to expand...
Click to collapse
I am set at 160 dpi and that didn't help.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ?. The market is your friend.
Click to expand...
Click to collapse
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
PepeladZ said:
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
Click to expand...
Click to collapse
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Eustace2 said:
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Click to expand...
Click to collapse
Thanks for explanation. I looked in build.prop from CW7 and DPI there is set to 160. I will try and report if this solved at least firefox problem.
old_fart said:
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
Click to expand...
Click to collapse
Thank you for video, but I was not asking how to edit text document, but rather what this change will give me.
Well, BNs build.prop has separate settings for X and Y dimensions. Following the logic, it does not matter if DPI is set via one command or via two... Anyway, simply changing to 160 DPI and rebooting did not help me with firefox compatibility in play store as well as other apps that were noted to show incompatible.
Any other suggestions and ideas would be very much welcome!
Hi all.
When I unlock the device, there is only a beautifull black screen because I uninstaled some default amazon stuff(I thought it was not so important files).
The kindle fire is already rooted and safestrap is already working, but I couldn't make any custom rom work yet. I gess is due stock firmware version. Gapps are working too. I tried unsuccesfuly via google play to install something.
As solutions I thought about sideload (I don't know exactly what) or solve this by making start settings on startup to reinstall the default firmware.,or renaming general settings file instead the locksreen one. Even including this into "recent content" may fix it.
I don't know if there is a better solution, or how to make this.
Thank you for your help.