Database Users

[SOLVED] Uninstall Swype?

I need to uninstall swype and reinstall it. Ive tried over writing it with the default apk but its not removing a theme I installed with metamorph. If I can uninstall it, a fresh install should fix it.
I just dont know how to remove it

I don't know if you want to go to this extreme, but I did. I fudged up the phone real good by removing and installing stuff. I finally got fed up and flashed it back to stock and applied root again. This time I'll keep my fingers out of it. I hated touchwiz in the beginning, but now it's kinda growing on me. I've never had an iphone but the home and drawer remind me of iphone wannabe. It's okay for now.
Sent from my SPH-D700 using XDA App

There a tool over at sdx-developers that can remove that when root explorer can't. I forget the name of it. There's also a pay app in the market that I think is called root manager that can successfully remove crap too. I didn't have much luck putting the general swype 1.61 in. It refused to install. That's when I think I just flashed it back to factory image. A full reset/wipe wouldn't fix it either.
Sent from my SPH-D700 using XDA App

I had to do this a few days ago for similar reasons. This is what I did:
First, you have to open your browser or other app with a text field. Select the text field then long press the text field again and switch the input method to the stock android kb.
Next, you have to make sure /system is mounted as r/w. The early versions of the the rooting scripts did not remount correctly but the newer ones supposedly fix it. I just looked in the initial rooting .bat file (on the PC) for the remount command and used adb to remount /system.
You can test if it's remounted correctly by renaming Swype.apk to Swype.bak with Root Explorer then going up a level and back to /system/app. If it's not mounted correctly it will show as Swype.apk again. If it shows as Swype.bak still, then you just have to copy the original Swype.apk to /system/app and then switch input method back to Swype!
Sent from my Epic 4G using XDA App

yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?

I don't know what's causing it but root explorer doesn't seem to work properly on the phone (not sdcard) filesystem in the system app folder. It's stuck in rw mode. People have said different things why but I forgot. I did noobnl's latest flash and it's still not working right. His script is removing the old root and my phone doesn't have that on there. I don't know what to tell ya. Maybe I should look for another root file manager.

kennethlongshaw said:
yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?
Click to expand...
Click to collapse
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)

dwyw42 said:
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)
Click to expand...
Click to collapse
mmmm. That fixed. it. I owe you a beer

kennethlongshaw said:
mmmm. That fixed. it. I owe you a beer
Click to expand...
Click to collapse
Hi guyz.
I cant delete swype.apt file from /system/app/*
i am using SUFBS program (reed/write option enabled)
i tried use command in terminal:
Code:
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
but i get only;
Code:
permission denied
z4root show info that my phone is rooted
PDA i5800XXJI2
any ideas how to del that file? :]

[ROM][3.19.2011]Basic Debloat

This is a basic rom and due to early rooting/s-off procedures, requires ADVANCED knowledge. If you are not sure whats going on, please wait to flash.
Rooting instructions:
http://www.androidpolice.com/2011/0...he-htc-thunderbolt-and-unlock-its-bootloader/
This rom is just a basic debloated stock Sense, based on the 1.12.605.9 RUU. This is NEWER than what is being currently shipped with the TB.
New rom uploaded, with fixed root and market.
Features:
--Most crap bloat gone. All HTC bloat still there.
--Deodexed.
--Zipaligned.
--Boot animation, startup sound, and shutdown animation re-routed to system/media for more convenient modification.
--Dalvik heapsize increased to 32M.
--Wifi scan interval increased to 90 seconds, from 15 seconds.
--newest market as of today.
--latest gmail as of today.
--busybox 1.19
just a basic rom to get folks rolling. I will be releasing something much better here in the near future.
CWR currently has some issues, so...flashing the kernel becomes a little more challenging. Using adb:
adb reboot bootloader
This should boot you into fastboot usb.
Put the boot.img you downloaded into the same directory your command console is working from. Then:
fastboot flash boot boot.img
Once its done:
fastboot reboot
To verify kernel flashed, your kernel date should be March 1st.
Rom
http://www.multiupload.com/7P2QVZ7EFJ
Kernel
http://www.mediafire.com/?50sowujwsos53ft
Thanks:
jcase, and everyone else who helped with rooting, and ThatDudeButch for being my guinea pig!
Issues: just one that i know of. Sometimes, superuser is lost. Re-use psneuter to reset permissions on su. chmod 4755 /system/xbin/su.
Missing market apps?
Flash this:
http://dl.dropbox.com/u/2056318/market_fix.zip

Badass, adrynalyne! I'm assuming the ROM package is just flashed in CWM like normal? Kernel or ROM first?

Doesnt matter which is first and yeah, rom is via cwr.

Thanks!
Now just waiting for a one click method or unrevoked.

adryn, as i'm coming from the fascinate... i'm ecstatic to see you here!

Also coming from the fascinate and very excited to see adrynalyne here....I too think ill hold off on this, I'm just not 100% confident with my adb skills yet lol...thanks to everyone taking part in this, you guys are amazing...
Edit: I took the plunge, rooted and s-off, without a hiccup. Was actually pretty easy
Sent from my ADR6400L using XDA Premium App

We got a rom already! Sweet!

going to flash this now, i'm lazy. Didn't want to delete everything myself. Thanks

uh, possibly a dumb question. how do i "click" on something in cwr. on my dinc it was trackbutton. lol im sitting here in cwr like uhhhh?

madfatter said:
uh, possibly a dumb question. how do i "click" on something in cwr. on my dinc it was trackbutton. lol im sitting here in cwr like uhhhh?
Click to expand...
Click to collapse
power?
Sent from my ADR6400L using XDA App

power just makes the menu go away. i read in another thread that somehow theback optino became available randomyl and he used that, but i dunno. if I figure it out ill post it ehre. if anyone else has figured it out, pelase pot back. thanks!

You will need to get a root shell (psneuter, perhaps) and change the permissions on the su if you want root:
chmod 4755 /system/xbin/su

try holfing the volume up or down keys for a few seconds. i did that right after i plugged in the usb cable. try any of those three. either way, now back buttons acts as ok. HERE WE GOOOOOOOOO!!!!!!!!!!

In CWM, keep hitting the volume up/down buttons until CWM says the back button is enabled. Then use that to select.
However, if you are like me, you cannot do a factory reset/wipe in CWM. I have a way around it if you like, but it is a little involved.

adrynalyne said:
Rom
URL 1
or
URL 2
Kernel
URL 3
Click to expand...
Click to collapse
Just to be clear... I need to download BOTH of these files and "flash" them both, correct?

same issue here - cant select anything in rom manager, just shows the manager symbol and nothing happens.
edit: i pushed between the volume buttons and it said something about the back button... now i can do it. I think you have to push both volume rockers to get this thing going?

Was able to flash the rom ok, but when i try and flash the kernel it just says
< waiting for device >
any ideas?
EDIT:
Fixed, thanks guys

my root is not working after flashing... mind giving detailed instructions to restore it? Thanks

Sounds like you don't have the bootloader driver. Look in Device Manager. Are there any "banged" out items?

This will get root access back:
To gain root:
adb shell
/data/local/psneuter
The following will remount /system and set up SU:
adb shell
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
/data/local/busybox cp /data/local/su /system/xbin/su
chown 0:0 /system/xbin/su
chmod 4755 /system/xbin/su
(Corrected to 4755, not 6755)

[MOD] [LG P500] CRT Screen Off for Optimus One

Hello All.
Here are the framework-res.apk and build.prop files for the Optimus One, Stock 2.3.3 firmware. All you need to do is replace those files and you will get the CRT ScreenOff effect
I used the post by Skynet28, modified a little to only use adb commands.
This was the first thing done after rooting the phone.
-NEEDED:
Rooted phone
.7Z file View attachment 949259
5 Minutes of your time
NOTE: YOU WILL MOST PROBABLY LOOSE YOUR PHONEBOOK, I DID WHILE DOING ALL THIS. PLEASE BACK THAT UP.
The procedure to install is as follows:
You must set the /system on the phone with RW permision
From a Command Prompt:
First we locate where /system is mounted
Code:
adb shell
su
cat /proc/mounts
Locate /system in the mount and write down the mountpoint (mtdblock1 or similar)
the type
Code:
mount -o rw,remount /dev/block/[I][COLOR="Purple"]MOUNTPOINT[/COLOR][/I] /system
exit
exit
Then we push both files to the phone with the folowing adb command
Code:
adb push framework-res.apk /system/framework
adb push build.prop /system
Finally we chmod those 2 files
Code:
adb shell
su
cd /system/framework
chmod 664 framework-res.apk
cd /system
chmod 664 build.prop
exit
exit
Thanks to this post
http://forum.xda-developers.com/showthread.php?t=1185231
If you like this post, buy me a beer!!

Does it workss ???????? Reply anyone

Do you lose contacts on phone or sim?

Kvidli said:
Do you lose contacts on phone or sim?
Click to expand...
Click to collapse
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..

chrisdf said:
Hello All.
Here are the framework-res.apk and build.prop files for the Optimus One, Stock 2.3.3 firmware. All you need to do is replace those files and you will get the CRT ScreenOff effect
I used the post by Skynet28, modified a little to only use adb commands.
This was the first thing done after rooting the phone.
-NEEDED:
Rooted phone
.7Z file View attachment 949259
5 Minutes of your time
NOTE: YOU WILL MOST PROBABLY LOOSE YOUR PHONEBOOK, I DID WHILE DOING ALL THIS. PLEASE BACK THAT UP.
The procedure to install is as follows:
You must set the /system on the phone with RW permision
From a Command Prompt:
First we locate where /system is mounted
Code:
adb shell
su
cat /proc/mounts
Locate /system in the mount and write down the mountpoint (mtdblock1 or similar)
the type
Code:
mount -o rw,remount /dev/block/[I][COLOR="Purple"]MOUNTPOINT[/COLOR][/I] /system
exit
exit
Then we push both files to the phone with the folowing adb command
Code:
adb push framework-res.apk /system/framework
adb push build.prop /system
Finally we chmod those 2 files
Code:
adb shell
su
cd /system/framework
chmod 664 framework-res.apk
cd /system
chmod 664 build.prop
exit
exit
Thanks to this post
http://forum.xda-developers.com/showthread.php?t=1185231
If you like this post, buy me a beer!!
Click to expand...
Click to collapse
You cant use this on anything but stock LG 2.3.3!
That means Cyanogenmod, AOSP, etc

kunnaliskinng said:
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..
Click to expand...
Click to collapse
Flash stock v20g using KDZ then root and do what this post says right away, i assure you it works.
This is only for STOCK 2.3.3

Kvidli said:
Do you lose contacts on phone or sim?
Click to expand...
Click to collapse
On your phone, but if you have it linked to your gmail account, when you sinc you will have them back.
you should still back up anyway, its safer that way

Only stock Rom
I want use on oxygen Rom .
Sent from my LG-P500 using Tapatalk 2

Are there any available screenies?

doesn't work for me..

kotobodj said:
Only stock Rom
I want use on oxygen Rom .
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
If you want it on any GB Rom, follow the tutorial i followed, check at the end of the post there's a link.

kunnaliskinng said:
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..
Click to expand...
Click to collapse
i think nothing to angry for this. just read carefully before do anything :laugh:

)
cool!)

Not bricked, but can't wipe in CWMR

I installed a custom font on my Tab. I decided to try and replace the Roboto_Bold.ttf, and that's why my Tab started to boot loop. (Long story short: I did the same thing to my Nexus, but I was able to salvage what I could and am now in the process of flashing a new ROM). I wiped the Cache/Dalvik on my Tab and flashed the ROM I had on it, over itself without wiping--thinking it would give me enough control to be able to flash a new ROM. I was wrong. I install the latest CWM (v5.5.0.4) and I go into Recovery mode. CWM won't let me Wipe Data. It just sits there, then ultimately kicks me back to the CWM "Home" screen; the same thing happens when I use an older version of CWM (v4.0.0.4). I've tried restoring backups and nothing works. I even had difficulty mounting the Tab on my laptop long enough to transfer over the newer ROM.
I have no clue what to do, and I feel so powerless. I usually can fix this kind of stuff by myself, but I can't this time.
Any and all help is appreciated.

Flash to stock using Odin ...I think you'll be able to reach downloading mode.
Of not try via adb of You are sure that debugging is checked
Sent from my GT-S5360 using Tapatalk

kishorsidu said:
Flash to stock using Odin ...I think you'll be able to reach downloading mode.
Of not try via adb of You are sure that debugging is checked
Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse
I can reach Download mode--but I have no clue how to flash anything from ODIN. -_-

Shameless bump.
Autocorrected from my GNexus

Here is a good guide to start over (is the last part "Re-“Stocking” Yer System…"): The Guide. The only problem is that you'll lose all your data.
I had a similar problem, but instead of going back to stock, I manually wiped the data/cache folders via adb, some folder was the culprit, it couldn't be deleted with its content, so first I deleted everything inside the folder and then the folder (in terms of commands, I did a rmdir instead of rm -r).

MapleSyrup said:
Here is a good guide to start over (is the last part "Re-“Stocking” Yer System…"): The Guide. The only problem is that you'll lose all your data.
I had a similar problem, but instead of going back to stock, I manually wiped the data/cache folders via adb, some folder was the culprit, it couldn't be deleted with its content, so first I deleted everything inside the folder and then the folder (in terms of comands, I did a rmdir instead of rm -r).
Click to expand...
Click to collapse
I don't mind losing the data; however, would you mind sharing the commands with me?

natezire71 said:
I don't mind losing the data; however, would you mind sharing the commands with me?
Click to expand...
Click to collapse
This is not a step by step guide, be careful if you decide to use this method, so you won't delete anything important.
First, to access the tablet shell
Code:
adb shell
To gain root permissions
Code:
su
To remove/wipe the data
Code:
rm -r /data/data/*
That's when I encountered the problem, I had to delete directories by groups until I found the problematic one. In my case was com.google.android.tts/
Then I did:
Code:
rm -r /data/data/com.google.android.tts/*
Code:
rmdir /data/data/com.google.android.tts/

MapleSyrup said:
This is not a step by step guide, be careful if you decide to use this method, so you won't delete anything important.
First, to access the tablet shell
Code:
adb shell
To gain root permissions
Code:
su
To remove/wipe the data
Code:
rm -r /data/data/*
That's when I encountered the problem, I had to delete directories by groups until I found the problematic one. In my case was com.google.android.tts/
Then I did:
Code:
rm -r /data/data/com.google.android.tts/*
Code:
rmdir /data/data/com.google.android.tts/
Click to expand...
Click to collapse
So, what was the problem you had? Couldn't you have just wiped in Clock Work?
Autocorrected from my GNexus

natezire71 said:
So, what was the problem you had? Couldn't you have just wiped in Clock Work?
Click to expand...
Click to collapse
That was the problem, I couldn't do it in cwm.

Just wanted to put it out there that I erased the data using Super Manager. Not a clean enough delete for preparing it for sale but good enough for my intentions.

Build.prop Edits (Stock ROM)

I wanted to start an official thread on performing build.prop edits on KFHD since no one has of yet. I have tinkered for several hours yesterday trying to get one that allows Google Play apps to install that show "unsupported device". I have had zero luck unfortunately, and am hoping some others want to take up the challenge and find a solution.
I suggest you get busybox before attempting this, it makes copying files easier. Get it in the GooglePlay store:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Make sure you back up your file first!!! I did these steps:
Code:
# adb shell
# su
# mount -o remount,rw /system
# cp /system/build.prop /system/build.prop.orig (cp comes with busybox see link above)
# cp /system/build.prop /sdcard/build.prop.orig
# exit
NOTE: If you didn't install busybox, then you can do the cp commands as below:
Code:
# cat /system/build.prop.orig > /system/build.prop
Word of caution, I have managed to get my Kindle into a boot loop several times through this, but fortunately have been able to recover (details below). I cannot guarantee that you won't damage your Kindle in the process, and prevent it from booting.
I am also attaching a copy of the stock build.prop in case you manage to damage yours. I can't guarantee you will be able to put it back if you get in a boot loop, but you should be able to at minimum "vi" the existing one and manually enter everything to fix you up.
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.

nvrmore100 said:
I wanted to start an official thread on performing build.prop edits on KFHD since no one has of yet. I have tinkered for several hours yesterday trying to get one that allows Google Play apps to install that show "unsupported device". I have had zero luck unfortunately, and am hoping some others want to take up the challenge and find a solution.
I suggest you get busybox before attempting this, it makes copying files easier. Get it in the GooglePlay store:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Make sure you back up your file first!!! I did these steps:
Code:
# adb shell
# su
# mount -o remount,rw /system
# cp /system/build.prop /system/build.prop.orig (cp comes with busybox see link above)
# cp /system/build.prop /sdcard/build.prop.orig
# exit
NOTE: If you didn't install busybox, then you can do the cp commands as below:
Code:
# cat /system/build.prop.orig > /system/build.prop
Word of caution, I have managed to get my Kindle into a boot loop several times through this, but fortunately have been able to recover (details below). I cannot guarantee that you won't damage your Kindle in the process, and prevent it from booting.
I am also attaching a copy of the stock build.prop in case you manage to damage yours. I can't guarantee you will be able to put it back if you get in a boot loop, but you should be able to at minimum "vi" the existing one and manually enter everything to fix you up.
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
Click to expand...
Click to collapse
Do you means that if we get stuck in the boot loop, we can try the third code to recovery?

It should let you get back to the device if you are in a loop like you would experience with the build.prop edit. Meaning you can still use adb shell to access the system even though its not entirely booted up, and you can't use SU.

No one willing to try more build.prop edits? I spent another few hours at this, I'm still no farther. I am able to trick play.google.com into thinking I have a different system (Nexus S in this case) but the play store on the kindle doesn't allow me to install several apps. If I tell it to download via the web site, it does not push them down to my device. Also, if I try to do a combination of website / play store app at various stages of the process, I can get all the way to install portion and then it tells me its not compatible...

Does anyone ever try to change DPI to 160 or lower?
Sent from my KFHD rooted

Yes, with a lower dpi, the normal android lock screen returns, however, the keyboard gets seventy messed up and becomes unusable. This was at 130 dpi.
Sent from my KFTT using XDA Premium HD app

Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app

madddoggj said:
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
use market unlocker.its ok.

madddoggj said:
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Yes, when Google says no, I go look for the apk and download it anyways. So far nothing has crashed. But I try to stick with things for ICS.

I messed with the ro.product.board entry... and now when reboot it got stuck at "Kindle is Upgrading... Starting application..."
Tried adb but device not attacked.
Is there a way to boot it up again?

dexd, http://forum.xda-developers.com/showthread.php?t=1930656

nvrmore100 said:
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
Click to expand...
Click to collapse
Worked like a charm on 7.2.1 jcase and sparkym3 are brilliant. I have no idea how this code works or what makes sense about it, but it's fantastic. Also, since this code lets you copy files without root, could this be another method for rooting my device?

Yuretz said:
dexd, http://forum.xda-developers.com/showthread.php?t=1930656
Click to expand...
Click to collapse
I followed the guide and got myself this factory cable and I can boot it up again

My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother

Thank you for your post, this thread may be quite useful for who has had a bricked device.

Yuretz said:
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Click to expand...
Click to collapse
I don't know what the other two things mean, but the "No need to block accelerometer in games" is something I need! Are you sing a Kindle Fire HD 7"? If so, I'm definitely doing this!

macravin said:
I don't know what the other two things mean, but the "No need to block accelerometer in games" is something I need! Are you sing a Kindle Fire HD 7"? If so, I'm definitely doing this!
Click to expand...
Click to collapse
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support

Yuretz said:
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Click to expand...
Click to collapse
So you can download apps from marked which are marked as "incompatible device" with stock build.prop ? Thank you for your answer! :fingers-crossed:

Yuretz said:
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Click to expand...
Click to collapse
I did this, but the dpi made my keyboard unuseable (the keyboard doesn't fit on screen idk why it became big when everything else became small)... does anyone know of a fix for this? That would be really great!

Does this work on Kindle Fire HD 8.9?
Yuretz said:
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Click to expand...
Click to collapse
Ok I am very excited.I saw this possible solution to my problem, as I would like to download NBA Jam for android (that I modded with Jordan in it that I have working on my rooted Kindle Fire with CM10 linaro on it, but what I wonder is if this will work for a rooted Kindle Fire HD 8.9 as well as a Kindle Fire HD 7? Thank you in advance.