Database Users

How to fix market download "freezes"

I think I've found the cause of this, where you download something from the Market and it says downloaded but just sits there forever. Google has something called a "checkin" service that sends them anonymous usage data, bug reports, crash logs, etc, but it fails a lot. When you download something from the Market, it sends a message to Google about it, and if it fails it just freezes.
You can turn this off easily with a system property. I haven't seen any issues with doing this except that it will break the setup wizard if you have this set during boot after a wipe.
All you need to do is add this line to the end of /system/build.prop:
Code:
ro.config.nocheckin=1
So, something like this:
Code:
adb pull /system/build.prop .
(edit file with notepad, vim, emacs if you hate yourself)
adb remount
adb push build.prop /system
adb shell reboot
Hopefully this helps someone and Google doesn't shoot me down from space

build.prop reverts after reboot
hey
followed instructions
- pulled build.prop
- added ro.config.nocheckin=1 to end
- adb remount (RW filesystem)
- pushed new build.prop, says 2593 bytes written
- rebooted device
upon reboot: /system/build.prop reverts back to original
any idea for a Rogers Dream user here

Just wanted to clarify that the steps should actually be:
Code:
adb remount
adb pull /system/build.prop .
*(edit file with notepad, vim, emacs, whatever)*
adb push build.prop /system
adb shell reboot
Otherwise, people are going to reboot their computers willy-nilly, and not their androids.

cyanogen said:
Hopefully this helps someone and Google doesn't shoot me down from space
Click to expand...
Click to collapse
Google is going to have you wacked for figuring this out.

terminal commands plz?

G1-evolve said:
terminal commands plz?
Click to expand...
Click to collapse
Code:
su
mount -o remount,rw /system
echo "ro.config.nocheckin=1" >> /system/build.prop
reboot

cyanogen said:
Code:
su
mount -o remount,rw /system
echo "ro.config.nocheckin=1" >> /system/build.prop
reboot
Click to expand...
Click to collapse
Thanks alot! What would be the "Undo" to this incase one day I need to wipe/flash a rom?
edit: seems to still "hang" and not work. Only works if I log into "gtalk"

After having completed this procedure, I've still managed to "hang" the market once. Though in all fairness, once is fine, because it used to happed daily.
However, I've noticed something that some people might consider a "down side" - when you uninstall apps, they remain in your downloads. That's exactly the same behavior that people were complaining about before cupcake came out.

besides anonymous usage data, bug reports and crash logs, what else would i be disabling by doing this?

AlfaTrion said:
besides anonymous usage data, bug reports and crash logs, what else would i be disabling by doing this?
Click to expand...
Click to collapse
Well, as I've mentioned in my post above yours, all apps that you ever downloaded while having check-in disable, will stay in your My Downloads. Again, it doesn't bug me as I use aTrackDog primarily for update checks, but I know some people don't like this.

Have you tried clearing the market cache in Settings > Applications > Manage Applications > Market? I'm curious to know if that assist with that at all.

jordanjay29 said:
Have you tried clearing the market cache in Settings > Applications > Manage Applications > Market? I'm curious to know if that assist with that at all.
Click to expand...
Click to collapse
I haven't, but I'll try. Though I am quite sure it will not do anything because that list remains the same through flashes and upgrades, so I'm sure it's pulled from Google servers.

my solution......
Whenever the market hangs when I download [email protected] reboot and it works fine. I don't get the hang problem a lot so it doesn't bother me to reboot.

pistol4413 said:
Whenever the market hangs when I download [email protected] reboot and it works fine. I don't get the hang problem a lot so it doesn't bother me to reboot.
Click to expand...
Click to collapse
It's not only about Market hanging. After disabling check-in, Market actually works much faster because data does not get sent to Google every time you do something (download / remove / update / etc.)

Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.

jordanjay29 said:
Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.
Click to expand...
Click to collapse
The framework could be modded for that, but thats a lot of work. Right now, the checkin code is a listener, and just wakes up for certain events (like an app install).

I THINK this could happen if one changes or deletes the APN of the phone.. for me it started to freeze the download after I completely closed the 3g/2g connection. So maybe google uses that connection in order to gether the data instead of the wifi. Can that be changed so that both use the wifi?

script to disable checkin service:
Code:
#!/bin/sh
su
if ! grep -q "^ro.config.nocheckin=" /system/build.prop; then
echo "Mounting system as read/write"
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
echo "Disabling Checkinservice"
echo "ro.config.nocheckin=1" >> /system/build.prop
echo "rebooting.."
reboot
else
echo "CheckinService already disabled"
fi

jordanjay29 said:
Would there be a way to schedule this checkin? Or make it run only once every x times? That might bridge the difference between no hangs and retaining all past downloads, and many hangs but clearing the downloads list.
Click to expand...
Click to collapse
I disassembled the classes.dex from the checkin.apk with baksmali and in the CheckinService.smali these fields are defined:
Code:
.field private static final CHECKIN_INTERVAL:J = 0x6ddd00L
.field private static final CHECKIN_INTERVAL_MAX:J = 0xa4cb800L
.field private static final CHECKIN_INTERVAL_MIN:J = 0x927c0L
Values in decimal(dont take the last character for conversion!). I think they should represent milliseconds:
0x6ddd00L: 7200000
0xa4cb800L: 172800000
0x927c0L: 600000
Maybe you can "schedule" the checkin service by changing these values, assemble the dex again with smali, replace the original classes.dex in the apk and push it back to the Phone.
Code:
adb remount
adb pull /system/app/checkin.apk .
Make a backup copy of the apk ;)
extract the classes.dex
java -jar -Xmx512m baksmali-0.94.jar -o ./checkin classes.dex
Edit the File
java -jar -Xmx512m smali-0.94.jar -o classes.dex ./checkin
Replace the classes dex in the pulled checkin.apk
adb push checkin.apk /system/app/checkin.apk
adb shell reboot
You can get smali and baksmali from here:
http://code.google.com/p/smali/

I was talking about the explicit checkin that happens after apps are installed, etc..

Accelereometer Issue After Updating to 5.0.6 from 5.0.5.3

My landscape orientation is slightly off, how to I reset the accelerometer, or clear the cache like some have suggested?
I thought my battery was running hot too so I ran Raging Thunder to see how much the graphics would raise the temperature. As I started driving I realized the car has a serious over-steer to the right. I have to have turn to the left just for it to drive straight.
Edit: I've tried the instructions here and it didn't work at : (http) ostebaronen.dk/fixing-accelerometer-on-htc-magic/
I'll just wipe and hope that fixes everything. :-/
Edit 2 (04/20/10): Solution found, see post #7 in this thread.
Edit 3 (04/20/10): Nevermind it did not work. I though it did failed to realize that my bubble level app was still calibrated to correct the misalignment. :/

do a full wipe then re flash the cyanogen rom again
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

I wiped, tested- no change in orientation unalignment
reloaded teh 5.0.53 rom, tested- no change in orientation unalignment
wiped again
wiped rotation
wipe cache, tested- no change in orientation unalignment
wiped
restored nandroid, tested- no change in orientation unalignment
guess i'm out of luck perhaps it could be a hardware issue...

After research and using sensor testers from the marketplace, I believe the file I need to delete/reset is AK8973. In ADB SHELL, once I run the command "mount -o rw /dev/block/mtdblock5 /data" then I can go into "cd /data/misc." If I list the directory I see a file called ak8973prms.txt .
Based on the sensor testers, it always lists the values under ak8973 so I see the relation.
What is my next step? Do I delete the .txt? Can I at least make a backup first. It'd be nice to see what the contents of the file are. I tried the pull command and I can not seem to get a copy of it to my computer for the life of me. I've never used linux before but I learn quick I just don't know where to resource now.
Edit 2:08: I figured out how to the view the file with the more command. Here are the internals. I'm curious if this is the source of the missalignment but I'm not sure how to fix. My issue is that the AK8973 Orentation sensor Y axis (pitch) is negatively off by about 4 degrees. I'm not sure if this txt file is a recent snapshot or a guide to help calibrate.
adb shell
/ # cd data/misc
cd data/misc
/data/misc # ls
/data/misc # more AK8973Prms.txt
more AK8973Prms.txt
[AK8973]
HDOE_STATUS=1
HDOE_SUCTEMP=113
HDAC.x=1
HDAC.y=128
HDAC.z=7
HOFFSET.x=335
HOFFSET.y=-687
HOFFSET.z=-210
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
/data/misc #

I was having this problem along with some others so I went back to 5053

I went back to other roms, including stock and the problem continues for me.

Ok so i finally found the fix, it was by overriding the AK8973Prms.txt with a blank file. I rooted a week ago and I'm so excited to have found this solution. Having a problem has forced me to learn some linux commands.
There may be a better way to do this, if so chime in but here are my caveman instructions.
Reboot your phone in Recovery mode (home+end/power > bootloader > recovery)
Connect via usb
Windows Start > Click Run > type CMD and press enter
Access your SDK tool folder with command: cd [file path]
adb shell
mount -o rw /dev/block/mtdblock5 /data
exit
[Make a blank file AK8973Prms.txt with notepad in your windows sdk\tools directory]
(in CMD window type, remember to change the the C:\ file path in the command to yours)
adb push C:\Users\name\Desktop\android-sdk-windows\tools\AK8973Prms.txt /data/misc/AK8973Prms.txt
exit
Reboot and wola!

i have managed to calibrate my nexus one g-sensor system wide using your method as a guide, thanks alot

Fix Mobile Data drain.

After 2 days of testing i think i have a clean solution to fix the mobile data drain by setting the preferred network mode to 1 (GSM only). No need to delete or rename anything. Just update the db that is already there .
You need a rooted device for this.
Extract the sqlite3.zip and push to your device with the following commands:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell
su (to gain root permissions)
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
reboot

I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.

agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
Sure, as long as you have some sort of terminal emulator installed.

agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
with root explorer and a terminal app (eg connectbot) you can do it.

What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App

Thanks! Mine is done. I'll report back later after I charge and give it a go.

mrkrabs said:
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.

_motley said:
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
Click to expand...
Click to collapse
couldn't describe it better

2g = only poll cell if request is made that needs cell, 3g = poll all the time, which means that if you change to only 2g then it should not check for cell if you are in wifi range.
I am sure thats how the tech works if i remember my time at nokia right LOL

is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date

I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.

Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA

kinnerc said:
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
Click to expand...
Click to collapse
Default value is 0 (zero).

agentdax5 said:
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Click to expand...
Click to collapse
It's not about what your stats say, but what your mA drain is. i loose only a couple of % in a night (sleep).

edgemaster191 said:
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
Click to expand...
Click to collapse
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?

try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.

nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
FTFY. 10char.

I am going to have to run some logs....just not seeing any drain that would justify doing this ....will definitely keep an eye out for it though

nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
such things will be able with kernels that overwrite the default.prop

matguard said:
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
Click to expand...
Click to collapse
i was able to finally get it, i copied the splite3 to /system/bin using root explorer, ran chmod through terminal emulator then ran the final command from adb shell.
not ideal but it worked

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.

[Q] How to disable change page buttons?

Hello,
my old Nook sometimes has faulty change page buttons, when i press them it's like they are constantly pressed and changes a lot of pages before it stops.
So I would like to disable them software side so that I can only use the touch screen (which works fine).
is it possible?
Also I have no way in settings to change the time, is it possible to do that maybe using terminal?
Thanks!

borzowsky said:
Hello,
my old Nook sometimes has faulty change page buttons, when i press them it's like they are constantly pressed and changes a lot of pages before it stops.
So I would like to disable them software side so that I can only use the touch screen (which works fine).
is it possible?
Also I have no way in settings to change the time, is it possible to do that maybe using terminal?
Thanks!
Click to expand...
Click to collapse
Which Nook model is this, exactly?

Hi sorry, it's the Nook Simple Touch (not the glowlight one, but the one without backlit)!
Thank you very much.

borzowsky said:
Hi sorry, it's the Nook Simple Touch (not the glowlight one, but the one without backlit)!
Thank you very much.
Click to expand...
Click to collapse
Alright, good.
To completely disable the four hard keys, all you have to do is navigate to /system/usr/keylayout using ES Fike Explorer (or something else), long-press on TWL4030_Keypad.kl, and change its permissions from rw- r-- r-- to --- rwx r-x. Then, after you reboot, your hard keys will not function anymore.
If for some reason you end up wanting your hard keys back, just change the permissions back to their original state.
Hope this helps!

ИΘΘK¡€ said:
Alright, good.
To completely disable the four hard keys, all you have to do is navigate to /system/usr/keylayout using ES Fike Explorer (or something else), long-press on TWL4030_Keypad.kl, and change its permissions from rw- r-- r-- to --- rwx r-x. Then, after you reboot, your hard keys will not function anymore.
If for some reason you end up wanting your hard keys back, just change the permissions back to their original state.
Hope this helps!
Click to expand...
Click to collapse
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!

borzowsky said:
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!
Click to expand...
Click to collapse
It probably is - I'm researching it right now. While you wait, though, here's the command for setting the time/date through ADB:
Code:
adb shell date -s YYYYMMDD.HHmmss
...in which "Y" is year, "M" is month, "D", is day, "H" is hour, "m" is minute, and "s" is second.
---------- Post added at 10:56 ---------- Previous post was at 10:45 ----------
borzowsky said:
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!
Click to expand...
Click to collapse
Alright, I got it.
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
Then, a reboot will finalize the change, which can be done either straight from your Nook, or using this ADB command:
Code:
adb reboot

ok one last thing and I won't bother you no more!
to revert to working buttons, what is the corrisponding command to this one?
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
is the power button and the "N" button continue to work if i do the change, right?
That changes only the change page buttons, right?

borzowsky said:
ok one last thing and I won't bother you no more!
to revert to working buttons, what is the corrisponding command to this one?
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
is the power button and the "N" button continue to work if i do the change, right?
That changes only the change page buttons, right?
Click to expand...
Click to collapse
To revert the page buttons to working order, use this command:
Code:
adb shell chmod 644 /system/usr/keylayout/TWL4030_Keypad.kl
And yes, this modification will only turn off the side page-turn buttons, and not the "n" and power buttons (those are controlled by a different file, gpio-keys.kl).

Ok I tried the clock trick and it works, but this command:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
says read-only file system, how can i fix this?
edit: ok i put this:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
in the shell, then quit the shell, gave the command and it didn't told me anything
then I did adb reboot and it rebooted, but the buttons to change page are still working.

borzowsky said:
Ok I tried the clock trick and it works, but this command:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
says read-only file system, how can i fix this?
edit: ok i put this:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
in the shell, then quit the shell, gave the command and it didn't told me anything
then I did adb reboot and it rebooted, but the buttons to change page are still working.
Click to expand...
Click to collapse
Hmm. Let me look into this.

ИΘΘK¡€ said:
Hmm. Let me look into this.
Click to expand...
Click to collapse
yeah sure, take your time!
you've been really helpful so far

Did you manage to find a way?

borzowsky said:
Did you manage to find a way?
Click to expand...
Click to collapse
Sorry for not getting back to you - been pretty busy lately. Here's what I'm tryng to figure out how to do:
I have discovered in the past that if a system file's permissions are not rw- r-- r--, or 644 in numerical value, the OS will not recognize the file as usable. What I am trying to do here is use the chmod command (change mode) to change the permissions of TWL4030_Keypad.kl to something other than the default setting so that it will not get used, therefore making the side keys unusable.
The problem is, I need to actually find a permission setting that does keep the system from seeing the file, and then I have to translate it into a numerical value for the chmod command to work. I know that --- rwx r-x works, but I don't know if I translated it right.
I'll post again when I get something usable.
---------- Post added at 10:41 ---------- Previous post was at 10:12 ----------
borzowsky said:
Did you manage to find a way?
Click to expand...
Click to collapse
Alright, I have a solution! Use this command in ADB (after mounting /system as read-write [adb shell mount -o rw,remount /dev/block/mmcblk0p5 /system]):
Code:
adb shell chmod 000 /system/usr/keylayout/TWL4030_Keypad.kl
Then, after a reboot, you will be good to go.

I'll try this as soon as I get home.
thank you for your efforts.
great it worked, thank you very much!