Hi,
I am a developer and facing an issue in kindle fire which is not there in other phone and tablets.
I have a custom view whose width will be initially (0.75 * screen width). Then I will be increasing its width upto (2 * screen width). But the entire view is not drawing. In all other android devices the view drawing. This issue is only in kindle. Can you please help me out of this??
Thank you
rock.sujin said:
Hi,
I am a developer and facing an issue in kindle fire which is not there in other phone and tablets.
I have a custom view whose width will be initially (0.75 * screen width). Then I will be increasing its width upto (2 * screen width). But the entire view is not drawing. In all other android devices the view drawing. This issue is only in kindle. Can you please help me out of this??
Thank you
Click to expand...
Click to collapse
Could be some override on the "bounds" properties for the parent containing "type/view", like clipToBounds etc, or any of the related ones
Related
Hi,
I'm an Android noob with aging eyes. I have trouble seeing some of the text on the rooted N2E and in apps.
In Kindle, especially, the biggest font size I can set is still a little small.
Any tips?
Thanks, John
You can change screen density... but there are some issues...
jrec said:
Hi,
I'm an Android noob with aging eyes. I have trouble seeing some of the text on the rooted N2E and in apps.
In Kindle, especially, the biggest font size I can set is still a little small.
Any tips?
Thanks, John
Click to expand...
Click to collapse
You can use one of the various LCD density changers from the Android Market. This will allow you to set the relative pixel density of the display. Try this application:
https://market.android.com/details?id=lv.n3o.lcddensity&feature=search_result
This works fine with many third party applications, however, the stock Barnes and Noble applications were not necessarily written to follow the rules. They do not adapt well to the change and various pieces of the GUI for those applications will be cut off. You can experiment with it a bit to set the density to something that will yield much larger text and GUI elements for side loading applications.
Michael.Rose said:
You can use one of the various LCD density changers from the Android Market...
You can experiment with it a bit to set the density to something that will yield much larger text and GUI elements for side loading applications.
Click to expand...
Click to collapse
Thanks, Michael, I'll give it a try!
Edit: the app LCDDensity for Root, which is free and in beta, does what I wanted it to do: it makes the Kindle app more readable for me, and the material on the Android home screen larger and easier to read. It also works in the Nook reader on the Nook "side" of the Android device (so I can switch back and forth between Kindle and Nook readers and have them both provide usable--for me--font sizes.
As Michael noted in his posting above, the stock Barnes and Noble apps are not necessarily written to work with this. Thus, the Barnes and Noble menus and such were not usable in my hasty look at them with LCDDensity set to 200%. That's ok by me--this gives me readable Kindle and Nook which is what I wanted.
There are other lcd density apps that I haven't tried, at least one of which is paid. Perhaps one of those would work better with the Nook Simple Touch.
Thanks again, Michael!
John
Thanks, Michael.
I changed LCD density to 200 and reaching Home Button Savior became a lot easier and reading on Repligo Reader is perfect now (if you click the option to "convert" pdf to text, zoom is limited to 150%).
LCDDensity for Root does solve the readability issue with Kindle/gReader/Email, but also screw up B&N native app including slide to unlock/Home menus etc while at it... hmmm, wonder if this would be improved somehow - like a special version just for Nook STR (heh, might be asking too much)?
jo2kxda said:
LCDDensity for Root does solve the readability issue with Kindle/gReader/Email, but also screw up B&N native app including slide to unlock/Home menus etc while at it... hmmm, wonder if this would be improved somehow - like a special version just for Nook STR (heh, might be asking too much)?
Click to expand...
Click to collapse
I've notice a few places where the contrast could be improved. Some apps are effectively unreadable because they put dark grey on slightly less dark grey.
I'd like to create a theme that increases the contrast of all drawable resources, an effect similar to setting your computer to display High Contrast (Windows) or Toggle Invert Colors (Mac).
voluntarytestsubject said:
I've notice a few places where the contrast could be improved. Some apps are effectively unreadable because they put dark grey on slightly less dark grey.
I'd like to create a theme that increases the contrast of all drawable resources, an effect similar to setting your computer to display High Contrast (Windows) or Toggle Invert Colors (Mac).
Click to expand...
Click to collapse
I'd pay for this - especially if it eliminates the "missing text" effect created by the white text resident in many menus and notification boxes.
I have my launcher home screen virtually black on white now, and it is great on the eyes.
Sent from my NookColor using XDA Premium App
All,
The new Pocket App (all 4.x versions) on CM7 (7.1.0) has super wide margins in the reading view. I've e-mailed them multiple times, and while they were nice enough to respond, I don't think they're going to fix the issue. Changing the font size has no effect on the margin width.
This wasn't a problem with Read it Later and it isn't a problem with the Kindle Fire, which has the same screen resolution and DPI as the Nook Color with CM7.
I tried changing my DPI in build.prop to 161 (from the default of 160) and it made the Pocket app margins normal, but made the article view text super small and disabled the default grid view. I never changed my dpi from the default before installing Pocket.
Can someone else with CM7 on a Nook Color install Pocket let me know if you see the same issue?
I had thoughts of monkeying with my build.prop to emulate a Kindle Fire, but I'm not sure what other issues that would cause in the Android Market/Google Play thingie.
Any other advice? Thanks.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Hi everyone
I think WP 8 should be like this, like Windows 8 Destop
Edit :
Link
http://www.youtube.com/watch?v=txdMwNNlTiw
Forgot the link x)
http://www.youtube.com/watch?v=txdMwNNlTiw
No, thanks.
Looks like an android mod.
No thanks, one of the reasons i like windows phone is the metro as start screen.
mcosmin222 said:
Looks like an android mod.
No thanks, one of the reasons i like windows phone is the metro as start screen.
Click to expand...
Click to collapse
It's the same as Windows 8 desktop ..
I think mode the scrend for up to down is not a good idea and we are easily lost when we search for an application..
isma33 said:
It's the same as Windows 8 desktop ..
I think mode the scrend for up to down is not a good idea and we are easily lost when we search for an application..
Click to expand...
Click to collapse
I beg to differ.
The vertical scroll feels much more natural on a phone than on a tablet or PC. The phone display is has its height bigger than the width (aka portrait) scrolling horizontally just feels out of place. I have that on my android 4.0.4 and I just replaced it with a vertical scroll.
On a computer it ain't a problem cause most displays are landscape or square, and they can display more tiles in the native modes.
So does a phone. It can display more tiles in a screen if it were vertical scroll.
As for the apps, i don't see how you get lost in em? it's easier to get lost in matrix based displays, as our eyes tend to only follow one flow direction (vertical or horizontal) and going horizontal then vertical then horizontal again is quite a pita when you eyes are tired.
Besides, the current listing of apps is nice, cause it allows you to see their full name.
Hello guys,
The background (example:Splash screen) that i have developed for my app is being rendered very badly on some android devices.By bad i mean the actual composition of brightness,contrast, sharpness all is getting very messed up, resulting in a very different background colour than the one i orignially created.Is there a solution for it,appreciate your help in advance! If any more info is required please ask..
Riser101 said:
Hello guys,
The background (example:Splash screen) that i have developed for my app is being rendered very badly on some android devices.By bad i mean the actual composition of brightness,contrast, sharpness all is getting very messed up, resulting in a very different background colour than the one i orignially created.Is there a solution for it,appreciate your help in advance! If any more info is required please ask..
Click to expand...
Click to collapse
Have you stored different resources for different DPI values (Same image in multiple resolutions) ?
Could you post a screenshot of the actual intended screen and the badly rendered screen, does it appear bad on a device of specific resolution or of some particular manufacturer ?
Hi All,
It is well known that browsers do not report exact screen resolution, e.g. on 1920x1200 tablet it reports 1280x752, on 1080x1920 phone it reports 360x592 (same stock Browser of OmniROM). This way the viewport size is being managed. But what if I want to make things smaller ( = increase reported resolution), where in a Browser's APK can I do that? Changing build.prop is not an option, that will affect all the apps.
In other words, when we build a ROM for a specific device where can we specify screen resolution for it?
Thanks...
Edit:
Compared to different browsers and figured out its more about "Wide Viewport" that needs to be switched OFF to get what I want. It was possible to get old pre-KitKat browsers to Debug mode and switch it there, but no options for one in KitKat. Anyone knows how to remove Wide Viewport functionality from the APK itself?