Android Question KitKat emulator

boten

Active Member
Licensed User
Longtime User
Some of my users complain about the "hollow font" in KitKat.
Since I don't have a KitKat device, I installed the SDK for android 4.4

First hurdle: AVD manager would not let me define a 4.4 device until I also installed "ARM EABI v7a System Image"
I did that, and defined a 4.4 device 4.0" 480x800

Second hurdle:
Trying to compile the program I got the error msg:
B4X: 
Installing file to device.  Error
   pkg: /data/local/tmp/myapp.apk
Failure [INSTALL_FAILED_CONTAINER_ERROR]
   Setting CanInstallToExternalStorage attribute to False may solve this problem.

I changed Module Attributes to:
B4X: 
#CanInstallToExternalStorage: False
Now it compiled and I get the hollow fonts.
Still, how can I specify
B4X: 
#CanInstallToExternalStorage: True
so the app can be installed to external storage?

Third hurdle:
Hollow font.

I replaced core.jar with the one supplied here
Font is OK.

Question remains:
how can I specify
B4X: 
#CanInstallToExternalStorage: True
so the app can be installed to external storage?

Side note: nothing to do with B4A, but 4.4 emulator is EXTREMELY slow.
 
Sort by date Sort by votes

boten

Active Member
Licensed User
Longtime User
I'm pretty sure I do.
Here's a screen shot of the KitKat Emulator parms. Am I missing anything?
 
Upvote 0

boten

Active Member
Licensed User
Longtime User
Slow, but any idea about my parms to make it install for external storage?
 
Upvote 0

Erel

B4X founder
Staff member
Licensed User
Longtime User
Your configuration looks correct. Might be a bug in this emulator. I highly recommend you to use a real device instead of the emulator. Currently there are two known issues with Android 4.4, the hollow text with Canvas.DrawText (which is fixed) and the fast scroller which is missing in ListView, and for now there is no workaround.
 
Upvote 0

boten

Active Member
Licensed User
Longtime User
Erel said:
... Might be a bug in this emulator
Click to expand...
Probably so.
Until I get a KitKat device my procedure is this:
1) I will test KitKat emulator (for NO hollow font) with
B4X: 
#CanInstallToExternalStorage: False
2) When everything is OK, compile with
B4X: 
#CanInstallToExternalStorage: True
3) Even after failing to install on emulator (as per my 1st post) - The APK is already there in Objects, so I can UL it to Google Play.

Makes sense?
 
Upvote 0

boten

Active Member
Licensed User
Longtime User
Further observation:
In the definition of the KitKat emulator, if I leave the SD Card: field blank (do not specify any value as size), then
compilation with:
B4X: 
#CanInstallToExternalStorage: True
works.
Does not seem logical, but it works. (Ours not to reason why)
 
Upvote 0
T

TedDog

Member
Licensed User
Longtime User
I have a Nexus 4 running 4.4.2, and I'm getting "hollow text" on my canvas.drawtext, too. I tried changing the Typeface value, but it doesn't help.

The Kit Kat upgrade also turned the button default color to a gray that was so dark it became hard to read the black text. That was easily fixed by setting the color manually to light gray.
 
Last edited:
Upvote 0
You must log in or register to reply here.

Similar Threads

  • Question
Android Question How to get data into a variable with HTTP GET on Android KitKat and Jellybean
Replies
3
Views
425
Erel
  • Question
Android Question Complete SMS intercepting example after KitKat
Replies
17
Views
5K
Erel
  • Question
Android Question Video Screen Capture (KitKat)
2
Replies
21
Views
5K
Asim A Baki
A
  • Question
Android Question SQLCipher on KitKat
Replies
3
Views
2K
Rusty
Bug? FastScroller and KitKat
Replies
5
Views
4K
Informatix
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…