I'm developing an app. I have implemented dark mode by creating colors-night file , using a switch and appCompatDelegate. I have written some code so that the app doesn't follow the system when phone's dark mode is on . And it works properly. Yet, the Splash screen does not obey and appears dark-colored when phone's dark mode is on(while the app continues light). I know this happens because the system reads the night resources before launching. (I figured it out since disabling dark mode in the onCreate method in SpashActivity or in Application does not work(and did some research) ). Adding "forceDark = false" on xmls doesnt work either. Does anyone know how to fix this?
I know it would be better to leave it this way since it is user's preference but i want on the first use, the user to see my company's colors and logo and then, choose the dark theme. Which, i also cant find how to change. I mean change dynamically splash activity's color depending on the sharedPreferences. (as i said before, doesnt work).
Thank you in advance :slight_smile:
I'm excited to roll out my first codename one app but I'm running into issues with the look of the program. On Netbeans my images great and my label backgrounds are appropriate. However, on my tablet, images have a background and my labels look odd.
The tablet image is from a Samsung Galaxy Tab 3.
Any idea how to fix this?
(Since SO won't allow me to post images, here is a link to the screenshots: http://www.pricepasta.com/random/Uglypng.jpg)
Use the Android build argument android.asyncPaint=true to use the newer rendering pipeline.
You would also need to test in the Android simulator to see the misalignment on the simulator as well. I'm assuming this is triggered by misuse of the layout managers.
I am new to java and android and wanted to see how developing for android works
I started by downloading the SDK FROM HERE
However after I finish making the Hello World project sample given in the website HERE, if I try to run it on the emulator as explained HERE, the emulator screen appears, but nothing seems to happen. I can see the word android on the middle of the screen with some animation happening, but that's it. The website says something about unlocking the emulator, but I have no idea what that means. What I have gathered from reading other posts is that the emulator is supposed to have some kind of slider switch as in real smart phones which should be dragged to unlock it, but I can't see it in my case. Now I have no idea why this is happening or what I should check out in order to fix this. Are there any installation logs or something else that I can check to see what the settings are?
What I have tried till now:
I downloaded the SDK ADT bundle from HERE and just unzipped it. Then looked for eclipse.exe and ran it directly. Is there anything else I should have done prior to this?
When I did it for the first time, I had only JRE installed and not JDK, which I realized after reading THIS POST. So I downloaded JDK from HERE, updated the required environment variables and restarted eclipse, but still it's the same thing.
I looked at the Eclipse isn't talking to the emulator section GIVEN HERE, but all it says is to restart eclipse and the emulator, and it doesn't do anything at all.
Rant:
I can understand if the program had failed to compile when I didn't have JDK , or if the IDE gave any indication at all of a faulty program install, but that isn't the case. Everything seems ok, there are no errors, but it just doesn't do anything. This is the type of thing that makes people pull their hair out, and personally, I think the With a single download, the ADT Bundle includes everything you need to begin developing apps: in the android website is very misleading, especially for complete beginners
Anyway, what should I do to make the tutorial program run on my computer? My computer is a bit old and slow so could that be an issue? My computer is Windows XP SP3 on Intel(R) Pentium(4) 4 CPU 3.20 GHz 3.19GHz 2.50GB RAM, but if that was the case I assume the emulator shouldn't even start up
You just have to wait a bit longer. Android loads pretty long on emulator.
Tutorial says about unlocking, because when Android is loaded, your screen on emulator will be locked.
If you find emulator too slow for you, you may want to check this topic out: Why is the Android emulator so slow? How can we speed up the Android emulator?
I had the exact same problem as you when I first got into Android development a week ago. The two things I did are simply
1) Set the usable RAM on your AVD to 768MB
2) When you run your Hello World program in your emulator, give it about 5-10 minutes. Don't touch or click the window at all, just let it load up. Later you can make it persist
3) If your home screen comes up, click and hold the mouse button in the center of the screen, then drag towards the sides and release, this should unlock the device.
Try these steps first, if they don't work then there is likely a problem with your AVD configuration.
If you are launching your app first time with emulator, it will take appropriate time.After that, on Lock icon click and slide to the right. then you can view you application. If not check for your app(icon) installed.
By seeing your configuration of PC I think it will take some time to load emulator. After emulator is load (see below image)
then and then run your code and also check in eclise-device that whether emulator is online or not.
For checking emulator in eclispe :
In second image just above windows logo you can see small rectangular button with plus sign click on that you will get list from which you can select devices. You can find similar button in you eclipse at the bottom.
I had the exact same problem and followed the exact same steps, but was also unsuccessful. I ended up creating a new AVD with a Nexus 4 instead of the latest Nexus 6. The resolution of the 4 is much lower, which I think is what solved my problem. It loaded much more quickly using the 4.
Also, When I was using the 6, I could only see "ndroi" because the size of the screen was much larger than the size of the phone. Now I can see the full device.
vs.
You may just need to relaunch the Android studio 3.6.3.
I got a similar problem. The hello world app does not install on the emulator.
Problem solved after relaunch.
I'm currently working on a map/navigational project for Android, and I chose OpenLayers because it claimed to support mobile development and the examples worked well on my Android phone.
I made a basic map prototype with one marker, a popup from the marker, and a layer switch control. All of this works as intended on both my PC and my Android, except for one weird issue with Android. I'm the .html file and all dependencies through a WebView in my app, and there are some weird issues coming up. For one, whenever I tap something like my marker or the zoom controller, an orange box appears briefly around it, and sometimes it doesn't register the tap.
To clarify, I have touch navigation enabled on my map, and all events for the popups are on-touch and working for the most part. But the orange boxes and occasional failure to register a tap are really ruining any degree of polish that the app has. Just wondering if anyone else has encountered this at before, and possibly has a fix?
whenever i see this type of behavior, i.e. orange crisscrossed boxes in openlayers, it is many times caused by failure to locate icon graphics files. try creating a marker whose icon file does not exist where it should and see if that is the "orange box" that you describe.
if so, then you should check any broken links (mouseovers, especially).
I have a Samsung Galaxy Tab, Android version 3.2, that is displaying the default Button control much much darker. Android 3.2 doesn't do this in the emulator, it doesn't do it on a newer ICS tablet, it doesn't do it on any of our phones or in any version of the Android emulator. Has anyone encountered this? We are not doing anything to the button controls display wise. They are completely out of the box controls.
Is there a fix that doesn't require custom coloring all our button controls? We're kind of stuck, because we can't reproduce it anywhere but the tablet it's happening on is our final QA approver, and she's a stickler for this sort of thing (it's an enterprise app we're trying to get going).
Edit: Looks for sure like it's setting a transparency on the buttons that none of the other devices are, rather than using a different color.
Edit: Here is a screen shot. Specifically, the Submit Shipping Selection.