Posts Tagged ‘Android’

9-patches insight – things you wont read on android’s doc.

September 4th, 2011

So i had to you a 9-path, for couple of month now i let our designer do the 9-path thing. If any of you think he bothered reading the docs. you are dead wrong :-) , designer, what did you expect happy little guy with 0 tolerance for long writings…. i used the 9-pathces for button’s backgrounds and for dialogs background, but alas! in some cases i got very very strange results which i could not understand. I had to turn to the documentation to check what it says regarding 9-patches and what the lines on top, bottom right and left actually mean…
» Read more: 9-patches insight — things you wont read on android’s doc.

wrting a GUI for android with TextEdit bind.

March 13th, 2010

In the work i do i came across a strange bug we discovered only when dealing with LTR languages.

The problem was in the TextEdit object in the android platform.

The problem Was that when you change from landscape to portrait the textEdit gets the previous screen’s state size, that is in landscape it is the width of a portrait and in portrait the width of the landscape.

It’s important to emphasize that this is NOT an android bug but porting bug. The place i work in has it’s own GUI that to work all it needs is Graphics object that implements certain interface (with basic warding capabilities)  and transfer the touch events to the Framework that was created in house for handling.

» Read more: wrting a GUI for android with TextEdit bind.

The problem with in-house frameworks porting.

February 8th, 2010

I work i a company which basically likes to have it’s own GUI and tools framwork to work with for both java and c++ codes.

They first create the basic code, set up interfaces to work with “shared code” and then “platform code” is created to support different platforms (windows\linux\symbian etc…)

The real advantage used to be that:

1. we had some great (well relatively ;-) ) GUI when you compare it to the native GUI (on WM 6.5, old symbian devices and J2ME deices)

2. our applications looked the same on all platforms, major plus if you are used to our application and change your phone to a new platform.

3. most ports are easy enough.

It all looks pretty pinky on the horizon, only times have changed.

To be honest i think that even J2ME have prettier GUI these days and if not you can still use LWUIT which is open source.

» Read more: The problem with in-house frameworks porting.

How To Upgrade the FW of LG EVE (GW620)

September 1st, 2009

Not too long ago I got an LG EVE device. If you are curious it’s an Android device from LG.

It’s amazing how LG have the special ability to take anything, from the poorest tools to the best OS I’ve seen and shred it to pieces…

What do I mean you might ask ? Well first of all the home screen Can be customized to be LG home screen, Or Orange home screen or Android home screen, this sounds nice, but I think all Android devices should have common interface and look and feel especially to the home screen since this is what you guys, as users will learn to know and love.

Second, like Samsung in the GLAXY device, the neglected the DPI definition, if you try to get the X and Y DPI you’ll discover them to be 160 average, the default…. Since the pixels width and height in the API are right (320×480) than most likely they did not update the screen’s size in inches in their FW. I also experienced crashes when the device was connected\disconnected from the USB cable, when I say crash I mean black screen with ARM registers displayed and you can only take off the battery to restart… you know… crash :-)

Sooooo I went on to flash it with a new FW I got from Orange.
» Read more: How To Upgrade the FW of LG EVE (GW620)

Theme Tweaker by Unreal