Presenting my new Java phone x3

[JoseskVolpe]

I'm glad to present my just new Java-enabled phone on my collection: Samsung GT-i6220


Completing the different kinds for my collection, i now have:

• Samsung GT-M2510 (Numpad candybar)
• LG x350 (QWERTY)
• Samsung i6220 (Touchscreen)
  

I found this phone on a wardrobe, the battery was dead and i didn't had the cable to charge it, also, the sounds were not working because i used it's speakers to fix GT-M2510's audio. I later found the cable, used another's broke phone speakers to substitute it, and charged it. It was working great, with only the screen backlight being a little weird
It was a little hard to be able to use this phone, this phone was SIM locked and i didn't had the SIM for it, and i couldn't install applications on it without the SIM. I decide to unlock that by using a FT232 module, but i couldn't predict that my cracked z3x software didn't had it on the list and the other one, Samsung 2G Tools, wich had this phone, did not had any crack and i couldn't crack it. But lucklym i found a Claro SIM card wich worked on this phone. Unfortunately, i can't use internet on this phone as i planned, bu at least, i can install widgets and Java applications now

By having a different Java touchscreen phone, i can now:

• Test my audio engine in more models quicker
• Test touchscreen in my future projects
• Test different APIs
• Make their compatibility list wider
• And many more stuff
  

¿Why not just test J2ME Loader?
Java is a virtual machine, and has many different implementations in different models. A premise for development is to test it in many different devices so you can make development wider.
J2ME already has a feature to debug your applications: Sun Wireless Toolkit
But it has itself some limitations that i would have problems running in other devices. And trying it only in J2ME SDK Mobile would make me face these issues aswell. For example, because PCs and Android devices are much more powerful than any Java-enabled phone, they can't imitate their performance and processing limitations. Indeed, you can set an FPS limit and threading delay to simulate that, but it isn't as precise than a real hardware.
Another limitation, also, is that they can't imitate different devices limitations. Some devices has available and not-available APIs, some of them aren't even available in both J2ME Loader and WTK, they also handle sounds and Image rendering in different ways etc. All these limitations can't be reached by using emulators.
Android devices, for example, usually has a bigger screen, with a higher resolution and a better multi-touch screen. i6220, for example, has a resistive single-touch screen with a 240x400 resolution, due that some corners are harder to touch than on a Android device.
Because of that, i had issues trying Snakes.io 2 on this device. The "Options" and "Ok" buttons are in the very bottom-left corner of the screen, and it was hard to press that until i discovered i had to press a little outside of the screen to reach that corner, the precision was just crappy.
Many Java devices had resistive screens and almost all of them are single-touch, indeed some of them were multi-touch, but MIDP 2.0 framework were single-touch only and multi-touch ability were only used on OS built-in apps or, in some cases (e.g. Symbian), apps built specifically for that OS platform.

Now with a touchscreen Java device, i can optmize most of my projects to Java phones with a touchscreen :3

[Stokes]

Cool..

[King_Dave]

Can you modify SDK and the text editor to support touchscreen?

[JoseskVolpe]

(06-29-2021 09:39 AM)King_Dave Wrote:  Can you modify SDK and the text editor to support touchscreen?

I tried before to decompile the SDK, but that had a huuuge source code and so much decompiling errors (returning only assembly code) that makes basically impossible to a single person to reverse engineer that..

There's a tool that can add some buttons for touchscreen devices, but that would not make the app touch-optimized, instead, it would be same as using your built-in on-screen navkeypad

---

I'm still finding a way to contact Mumey to see if i can get the source-code

[java gamer]

who is Mumey ?

[King_Dave]

(06-29-2021 10:25 AM)JoseskVolpe Wrote:  

(06-29-2021 09:39 AM)King_Dave Wrote:  Can you modify SDK and the text editor to support touchscreen?

I tried before to decompile the SDK, but that had a huuuge source code and so much decompiling errors (returning only assembly code) that makes basically impossible to a single person to reverse engineer that..

There's a tool that can add some buttons for touchscreen devices, but that would not make the app touch-optimized, instead, it would be same as using your built-in on-screen navkeypad

---

I'm still finding a way to contact Mumey to see if i can get the source-code

Oh... mumey the vendor
i was once a touchscreen modder but i've lost my modding tools

[JoseskVolpe]

(06-29-2021 02:58 PM)King_Dave Wrote:  i was once a touchscreen modder but i've lost my modding tools

http://4pda.info/winmobile/ppc_soft/ppc_...-java.html

[Abidemhie]

Whats that?