Hi all. I'm a noob, so can't post in the dev forum, so I'm asking here.
I had one of the RC HoneyStreak builds (forget which on exactly) but had to go back to StreakDroid due to the Kindle app auto rotating. That is, using 2.2.2 the Kindle app had an option to allow me to lock the screen in whichever orientation I was in at the time. With 3.1 there was no lock option.
So, in HS R2 can I lock the Kindle app into portrait or landscape mode as I see fit?
Thanks!
Jeff
rattlehead02 said:
Hi all. I'm a noob, so can't post in the dev forum, so I'm asking here.
I had one of the RC HoneyStreak builds (forget which on exactly) but had to go back to StreakDroid due to the Kindle app auto rotating. That is, using 2.2.2 the Kindle app had an option to allow me to lock the screen in whichever orientation I was in at the time. With 3.1 there was no lock option.
So, in HS R2 can I lock the Kindle app into portrait or landscape mode as I see fit?
Thanks!
Jeff
Click to expand...
Click to collapse
You can't in the app itself but you can stop the auto rotation with 3.1/3.2 in the system. Just touch the time on the bottom right and youll see where you can tick auto rotation on and off. Hope this helps...
At least you got Kindle to work. Mine will crash every time I pull up a book.
johnw91498 said:
At least you got Kindle to work. Mine will crash every time I pull up a book.
Click to expand...
Click to collapse
You need to change the screen density to use the kindle app. Just download LCD Density from the market and change the density to 100 or 105 with that app and it will work.
Nook color with CM7.1 stable and latest kindle app.
"Disable full screen" unchecked so the status bar is hidden in kindle reading mode, however, when I bring up the book info interface the status bar also comes up and the display is broken.
Here is a screenshot:
http://i40.tinypic.com/t7y74l.png
I think its a kindle bug but just want to know if CM7.2 or CM9 happens to have better result? or any fix for that?
Thanks!
arda99 said:
Nook color with CM7.1 stable and latest kindle app.
"Disable full screen" unchecked so the status bar is hidden in kindle reading mode, however, when I bring up the book info interface the status bar also comes up and the display is broken.
Here is a screenshot:
I think its a kindle bug but just want to know if CM7.2 or CM9 happens to have better result? or any fix for that?
Thanks!
Click to expand...
Click to collapse
CM 7.2 RC1 works the same way. And it's not just the latest version of Kindle that does that. Earlier versions did that as well. You need to check the box and then you can manually dismiss the status bar to get it out of your way.
Sent from my NookColor using Tapatalk
arda99 said:
Nook color with CM7.1 stable and latest kindle app.
"Disable full screen" unchecked so the status bar is hidden in kindle reading mode, however, when I bring up the book info interface the status bar also comes up and the display is broken.
Here is a screenshot:
http://i40.tinypic.com/t7y74l.png
I think its a kindle bug but just want to know if CM7.2 or CM9 happens to have better result? or any fix for that?
Thanks!
Click to expand...
Click to collapse
Same here in 7.2rc1.
Update: got it fixed by modifying kindle apk.
I noticed that the corruption occured only on white mode so I changed the background color of white mode, which was defined in res/values/colors.xml, to light cyan and it worked. I believe any other color might also do the trick.
I have a non rooted Kindle Fire HD and wanted to set a 3rd party app as default action for home button. Its telling me to "Clear Defaults" on Kindle Fire stock Launcher but its greyed out. Any idea on how to pick other app as a default launcher without rooting the device?
nitu01 said:
I have a non rooted Kindle Fire HD and wanted to set a 3rd party app as default action for home button. Its telling me to "Clear Defaults" on Kindle Fire stock Launcher but its greyed out. Any idea on how to pick other app as a default launcher without rooting the device?
Click to expand...
Click to collapse
Nope. The only way to set another launcher to default is to make it a system app, which cannot be done without root access
onemeila said:
Nope. The only way to set another launcher to default is to make it a system app, which cannot be done without root access
Click to expand...
Click to collapse
Thanks!
i have remplaced the system ui of my kindle fire hd (rooted) then i rebooted it, it load, and then at the home screen all is black, all black screen, the superuser notification only appear, how can i fix this. i cant enable adb because i cant see notification bar. please help me
Hi android developers, I have my kindle fire hd 7 softkeys hidden using qemu.hw.mainkeys=1. The problem is this gets rid of my app menu icon in the action bar. And lmt launcher's app menu button won't work please help
Update, this is to clarify qemu.hw.mainkeys=1 gets rid of softkeys and gap between keyboard and notification menu but as I said has a glitch with the app menu button not being shone in action bar. How do I force a tablet to show it in action bar or get the app menu button to work on lmt launcher
Wait, are you saying that when you changed that line in the build.prop that you don't have the gap? How is that possible? Send a screenshot please.
As for the menu button, you'll have to lower the density of the device or flash a custom rom.
Go to build.prop and add the code qemu.hw.mainkeys=1 on a new line. Then restart device This is telling the device that you have hard keys. Thus not giving you the gab. The problem is like I said it gets rid of app menu in action bar and lmt launchers app menu sadly didn't work. This is what I'm trying to fix. Own order to mess with build.prop you need to be rooted and have we file explorer installed
Sent from my KFTT using XDA Premium HD app
Do you have a screenshot to show that you don't have the gap anymore? I'm asking because I tried this method long ago and the gap remained. And yes, I am rooted running a custom rom.
For the menu button, you can lower the density or switch roms to get it back.
Braves1995 said:
Do you have a screenshot to show that you don't have the gap anymore? I'm asking because I tried this method long ago and the gap remained. And yes, I am rooted running a custom rom.
For the menu button, you can lower the density or switch roms to get it back.
Click to expand...
Click to collapse
Here is the screen shot. As you can see the notification bar is down and there is no gap. As I said before there is still a glitch, there is no way to get into the app menu. Because the lmt launcher app menu button doesn't so you are locked out. That is why I am currently still during the dumb nav bar at the bottom of the screen.
BTW I'm have Kindle Fire HD 7 running version 7.3.1 forked version ICS 4.0.3, Stock amazon os rom with ADW as default launcher, rooted with binary root with restore v31. So with these stats is there a way to fix the app menu problem
Anybody have any ideas
Sent from my KFTT using XDA Premium HD app
Braves1995 said:
Wait, are you saying that when you changed that line in the build.prop that you don't have the gap? How is that possible? Send a screenshot please.
As for the menu button, you'll have to lower the density of the device or flash a custom rom.
Click to expand...
Click to collapse
What do you mean lower the density and how do I do that. Is it dangerous
Sent from my KFTT using XDA Premium HD app
Lowering the density is another setting in the build.prop. I don't remember if its dangerous nor not I think it might make some apps display incorrectly if not set right though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
JORDANZ1998 said:
Hi android developers, I have my kindle fire hd 7 softkeys hidden using qemu.hw.mainkeys=1. The problem is this gets rid of my app menu icon in the action bar. And lmt launcher's app menu button won't work please help
Click to expand...
Click to collapse
Try https://play.google.com/store/apps/...t#?t=W251bGwsMSwyLDEsImNvbS5zbWFydC5zd2tleSJd
stunts513 said:
Lowering the density is another setting in the build.prop. I don't remember if its dangerous nor not I think it might make some apps display incorrectly if not set right though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
how do I change it in build.prop and what should i change it two 200??? people seem to like that one.
OK I'm throw I g a guess at the value because this is the default in my cm tablet version, but find ro.sf.lcd_density in the build.prop, try setting the value to 178 and see what happens.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Ok will it bootloop my kindle again don't want that happening
Sent from my KFTT using XDA Premium HD app
stunts513 said:
OK I'm throw I g a guess at the value because this is the default in my cm tablet version, but find ro.sf.lcd_density in the build.prop, try setting the value to 178 and see what happens.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
The rom kinology uses a 200 dpi even though I'm on stock rom will that be safest since kinology is basically amazon is with perks. Will it not boot loop my kindle if I set it to 200
Sent from my KFTT using XDA Premium HD app
Idk about boot loops, I haven't ever messed with the density, I think it will just make or screen malfunction, if it malfunctions too bad you'd have to pull the file over adb then push it back after making necessary changes and chmod the permissions back to how they were.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Lowering the density is another setting in the build.prop. I don't remember if its dangerous nor not I think it might make some apps display incorrectly if not set right though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
i think im going to wait till they update KF first aide. there going to have an automatic dpi change. there