Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7440901
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T10:55:26+00:00 2026-05-29T10:55:26+00:00

Disclaimer : this is a strange issue that only happens in a Kindle Fire

  • 0

Disclaimer: this is a strange issue that only happens in a Kindle Fire (so far).

Technologies Involved: Android SDK, Eclipse, LibGDX.

I have a relatively simple app running with LibGDX. The way LibGDX works is by having an OpenGL thread that will call Create() (once) and then Render() as many times as possible (so you can do your render…).

So when you initialize the Device, your “Create()” method is called and then when the OpenGL surface is initialized (all this happens automagically), your Render() starts getting called.

If the OpenGL context is lost, destroyed, etc. your Resize(width,height) method is called by LibGDX.

So far. So good.

Now I came across a strange issue with a Kindle Fire where things looked a few pixels off or “cut”. The Kindle Fire has a “softbar” at the bottom of the screen (20 pixels) that you can’t hide or skip, which is “kind of ok” because the device doesn’t have physical buttons. You’re expected to touch this soft bar and get a bigger bar to go back, go home, etc. According to Amazon, this bar cannot be removed. (is not 100% clear but nobody has found a way -that is not breaking the Amazon rules). The only App I’ve seen that removes that is the Amazon Video Players for videos streamed from Amazon’s Cloud only. So as you can see, there doesn’t seem to be a way to “permanently” hide that bar.

So if the bar is there, your real screen state is not the hardware resolution 1024×600 (landscape) but 1024×580. So I added some logging to my methods to see what was going on, and was surprised with this… (remember the create(), render() and resize() methods):

12-23 15:17:04.119: I/myapp(19921): SCREEN HEIGHT AT CREATE(): 600
[snip other unrelated log stuff]
12-23 15:17:04.673: I/myapp(19921): SCREEN HEIGHT AT RENDER() LOOP: 600
[snip other unrelated log stuff]
12-23 15:17:04.705: I/myapp(19921): MyApp - Resize() Called.
12-23 15:17:04.705: I/myapp(19921): SCREEN HEIGHT AT RENDER() LOOP: 580

So the screen has been “resized” by the Kindle Fire, “at some point”.

Has anyone come across something like this?

This is a screenshot (notice the black bar on top, that’s not added by me!). Forgive me for blurring the image but this is a client’s project and I can’t “disclose” anything.

enter image description here

The fun part begins when sometimes, the bar won’t be there and the app will look like the next (again, sry for the blur). Notice how the top bar is not there…

enter image description here

Upon a closer examination of both shots, you can tell that the bottom (which should be the same), is not. The kindle is doing strange things.

Any ideas?

The assets were originally packed as 1024×600 but we have changed that (580 now) and will assume that the viewport is now 1024×580 but I was wondering if anyone found a better way to deal with this nonsense? 🙂

note: we do have android:theme=”@android:style/Theme.NoTitleBar.Fullscreen” in the manifest. Doesn’t do anything.

Thanks in advance.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T10:55:27+00:00Added an answer on May 29, 2026 at 10:55 am

    Kindle fire has a strange behavior, once the app loads seems like it “moves” screen 20px up (Softbar height) therefore your app looks a few pixels off or cut. That’s because when you create your GLSurfaceView and set your renderer it calls two times to onSurfaceChanged method.

    First time, after onSurfaceCreated is called, with a resolution value of 1024×600 and a second time after first call to onDrawFrame with a value of 1024×580.

    The solution, you must control the two calls to onSurfaceChanged and resize the opengl viewport.

        private static boolean appStarted = false;
        ...
    
        private static class Renderer implements GLSurfaceView.Renderer 
        {
            public void onSurfaceChanged(GL10 gl, int width, int height) 
            {
                if ( !appStarted )
                {
                     //Initialization (Resolution 1024x600)
                }
                else
                {
                     //Second call, screen resolution changed (Resolution 1024x580)
                     //Resize(width,height)
                }   
                appStarted = true;
            }
    
            public void onDrawFrame(GL10 gl) {
            //Render()
            }
    
            public void onSurfaceCreated(GL10 gl, EGLConfig config) {
            //Create()
            }
        }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

[Disclaimer: this is a Windows 7 specific issue as far as I can tell]
Disclaimer: this is needed for an old and ugly codebase that I'd much rather
Disclaimer : This is for a semester project that I am currently working on.
This is an academical exercise (disclaimer). I'm building an application that will profit from
Disclaimer: Ok I know that this is being discussed in the thread linked below,
Disclaimer: This is my first time writing unit tests...be gentle! :) I am trying
Disclaimer: this is not a question about how to install asp.net or an application
Disclaimer: This is for a programming class, but it is not the answer or
Disclaimer: This question is strictly academic. The example I'm about to give is probably
(Disclaimer: I realize this is a massive wall of text, but I have done

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.