I see MikeyMike01(all credit goes to him) has figured this out, so I thought I would share how it was done since his thread doesn't go into how he did it.
DEVS ONLY!!
(Don't ask for compiled versions in here)
(I am doing this in Linux)
Decompile android.policy.jar:
Copy out the classes.dex file somewhere
java -jar baksmali.jar -o classout/ classes.dex
Go to classout/com/android/internal/policy/impl
Apply the patch (attached below):
patch -p1 < ../path/to/homehaptic.patch
Recompile android.policy.jar:
java -Xmx512M -jar smali.jar classout/ -o new-classes.dex
Copy new-classes.dex back into the jar file as classes.dex
Push android.policy.jar back to your phone, reboot and enjoy haptic feedback on your home button on JPY!
SWEET. Can we get a precompiled version for Perception? </troll>
smmalis37 said:
SWEET. Can we get a precompiled version for Perception?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
designgears said:
Click to expand...
Click to collapse
I'm going to make that my wallpaper
Sent from my liberated Captivate via XDA App.
Damn DG you beat me to it, I was staring at the following screen and couldn't figure it out for the life of me.
Was I at least close?
Left = Mikey's V8
Right = Mikey's V9
http://psfreedom.com/images/compare.png
smmalis37 said:
SWEET. Can we get a precompiled version for Perception? </troll>
Click to expand...
Click to collapse
Editing your post afterwards doesn't fix your stupidity.
>Iwasonlypretendingtoberetarded.jpg
TheEscapist said:
Editing your post afterwards doesn't fix your stupidity.
>Iwasonlypretendingtoberetarded.jpg
Click to expand...
Click to collapse
And that's why it works.
devz3r0 said:
Damn DG you beat me to it, I was staring at the following screen and couldn't figure it out for the life of me.
Was I at least close?
Left = Mikey's V8
Right = Mikey's V9
http://psfreedom.com/images/compare.png
Click to expand...
Click to collapse
These highlighted lines were present on Captivate ROMs and not on i9000 ones.
Ipso facto.
http://img64.imageshack.us/img64/2695/33554972.png
I knew I had to be looking in the right place
I also knew it was 8 lines that was inserted. I guess I just got cross-eyed :/
Either way great job finally figuring out this mystery!
As MikeyMike can attest... I'm retarded still when it comes to android. But this, I am excited for!
Good work MikeyMike!
why is dg posting this if all credit goes to the other dude? just curious!
Mike fixed it but didn't write it up. DG found his fix and wrote it up so all could benefit. Sometimes it's nice to have someone else write stuff up when you're too busy...
It wasn't too hard to figure out though. It only took about an hour of looking through phone window manager.smali to find out where the code need to be inserted.
Mikey was the brave one though and tested out some random code insertion lol. It just happened to work first try. Else I would have tested a couple other methods in the smali.
Good job Mikey
Can someone recreate patch for my JPB firmware, if i give a file for now? Can't use android sdk and java for some time...
Yuna said:
Can someone recreate patch for my JPB firmware, if i give a file for now? Can't use android sdk and java for some time...
Click to expand...
Click to collapse
Post it up, ill take a look
okay, but i have my rom odexed (forgot to mention it)...
http://rapidshare.com/files/441310491/android.policy.zip
thanks
I tried it, the patch doesn't seem to work on JPY android.policy.jar, not sure what is being patched here. I did try several different ones too. Then I gave up trying to use the patch, grabbed Mikeys android.policy.jar and did a diff with my JPY policy. What I saw there made a whole lot more sense and was about 20 lines of code, so i just copied the PhoneWindowManager.smali from Mikey to mine and recompiled. There were a lot less differences between Mikeys and JPY then there were from the patch and jpy.
For example: The patch wants to change line 4248 from cond_152 to cond_163. Both JPY and Mikey read cond_12.
If anyone can do this for JW4, I don't have access to any Linux/Windows(Cygwin) at the moment. If you can't, thanks for trying. I will get to it later.
Related
After spending 2 days of work, the TyphoonLabs tutorials (http://www.khronos.org/developers/resources/opengles/) are successfully compiled & run on my Diamond.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation
Simply unzip the content to any folder, but the /resources folder and underneath files must be copied to root.
Instructions
After startup, click the top right corner cross or press the DPAD to quit.
Some demos will have different effect when tap the screen, just try it.
Enjoy!
Will try it out immediately!
As you can see in my sign I'm currently using Panosha ShineOn 1.6 ROM on my Diamond. I don't know if he changed any drivers or so in his ROM, but I can only initiate tutorial 1 + 2.
EDIT: ok, yeah... misread the instructions. Had to put it on the root on the storage card, not the internal memory.
Only 1 and 2 work.
Some do Nothing at all
Some give openGL ES init error.
Riel said:
Only 1 and 2 work.
Some do Nothing at all
Some give openGL ES init error.
Click to expand...
Click to collapse
I have the same effect
same here...
all seven worked out fine for me
i got stock 1.93 ROM
Just 1 & 2 For me, Stock 1.93 ROM
@ALL
If you can only run 1 & 2, make sure you have copied the folder \resources including the underneath files to root.
Amazing work.. Looks great. The resource should be on the root of the device and not the storage card.
Really nice, great work
Interesting,
on the last test (7) (as pictured in your first post) I get a FPS rating of 74/75
Nice work !
Only 1 and 2 work on my stock uk tmobile rom too?
A_C said:
Simply unzip the content to any folder, but the /resources folder and underneath files must be copied to root.
Click to expand...
Click to collapse
Had the same when I built them ages ago, couldn't seem to get relative filepaths working
Still having no joy with that ".\" is always root ?!?
Nice work A_C, I really hope you will be implementing this into your S2 applications, that would be amazing!
Very nice,
great work, looks real good.
PS.: At the last Tutorial, I have also over 70FPS.
greets doena
Magilla said:
Had the same when I built them ages ago, couldn't seem to get relative filepaths working
Still having no joy with that ".\" is always root ?!?
Click to expand...
Click to collapse
Windows Mobile does not seem to have a concept of "current working directory" when launching an application. It's pretty annoying.
I work around this using the following:
public static string CurrentWorkingDirectory
{
get
{
return Path.DirectoryName(Assembly.GetExecutingAssembliy().GetName().CodeBase);
}
}
Then use that directory to build relative directories...
Koush said:
Windows Mobile does not seem to have a concept of "current working directory" when launching an application. It's pretty annoying.
I work around this using the following:
public static string CurrentWorkingDirectory
{
get
{
return Path.DirectoryName(Assembly.GetExecutingAssembliy().GetName().CodeBase);
}
}
Then use that directory to build relative directories...
Click to expand...
Click to collapse
Thanks loads... much appreciated!
impressive!!!!
All work fine in root \
psc001 said:
Interesting,
on the last test (7) (as pictured in your first post) I get a FPS rating of 74/75
Nice work !
Click to expand...
Click to collapse
doena said:
Very nice,
great work, looks real good.
PS.: At the last Tutorial, I have also over 70FPS.
greets doena
Click to expand...
Click to collapse
I got that FPS too. The screenshot shows a lower no. because it's running a screen-capture program in the background.
Jin187 said:
Nice work A_C, I really hope you will be implementing this into your S2 applications, that would be amazing!
Click to expand...
Click to collapse
That's my dream.
Nice work A_C.
Thanks
I try to compile and execute these tutos. There's no pb to execute on emulator.
But when I try on my phone (HTC Touch Pro), it doesn't work.
When I try your .exe, A_C, there is no pb. Maybe I have a pb when I create the exe.
Could you help me ?
Thanks
the guys in this thread have put together an awesome keyboard replacement. however, because of Tattoo's small resolution, even the low-res version looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know how to modify the keyboard so it would work on Tattoo, but maybe someone else can. please go to the original thread if you think you can help developing the app.
+1 would be cool!
I also posted in the original thread... I hope someone fixes it! =)
Same here. http://forum.xda-developers.com/showthread.php?t=655363
For a while I downloaded other keyboard....
Maver|ck said:
Same here. http://forum.xda-developers.com/showthread.php?t=655363
For a while I downloaded other keyboard....
Click to expand...
Click to collapse
I uploaded the files in that thread, in case you still need them.
shears said:
I uploaded the files in that thread, in case you still need them.
Click to expand...
Click to collapse
Hey Thank you. Let me see if that works
No, It doesnt work . I got this messege Failure [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES]
How did you install it ?
You have to push it with ADB.
Im doing this:
Code:
adb remount
adb push HTC_IME.apk /system/app
adb push Clicker.apk /system/app
adb install -r HTC_IME.apk
adb install -r Clicker.apk
adb reboot
You don't have to install it ! Just reboot and it's done.
I did it. it keeps the huge keyboard
This is how my keyboard looks, its hard to tell but each letter is a little bit vague but it works ok... i would like to know if anyone else has this problem, its almost like each letter looks hand drawn with a pen !!!
..
fixed
ignore my last post !!
was on wrong track.. tattoo res unsupported, in process of fixing now..
.
some news from that thread:
It's not technically difficult to port the mod to Tatto. However, I don't think that I will ever do it given what I have to work with now. I don't have the time to keep several code bases up to date (spare time project after all) so I must be able to share code bases between the different resolution versions. The two current versions are from Desire and Legend. They are essentially the same from a code point of view so it's feasible for me to keep them both updated. The current Tattoo version is an older HTC_IME generation with several differences in the internal logic. It's possible to port my hack one by one manually to the Tattoo version, but I don't have the time. The source code is posted so anybody who want's to start working on it can do so...
Click to expand...
Click to collapse
JoOoSs said:
You don't have to install it ! Just reboot and it's done.
Click to expand...
Click to collapse
Done. But it's not jus doing that. We need go to Application option and uninstall Update of Touch Input app.
Thank You every one
terminal 7 said:
ignore my last post !!
was using old version, the new one seems all fixed
.
.
Click to expand...
Click to collapse
Can I make you post a link?
I get Install_Failed_dexopt when trying to install?!
Well I can try mess a bit around with it... but it's smali files which isn't my strongest site, sadly
Mod. edit: not dev related, moved to general
though it would best match t&a, let me know when it's solved and I will move it accordingly then
I checked again the thread and in the first post there is no longer a warning that the keyboard doesn't work on tattoo.
however when i did a quick search though the pages i didn't find anyone who would successfully install the keyboard on tattoo. someone mentioned that it doesn't work correctly, but only in landscape mode.
i will try to install the latest (27) version later today and will post screenshots afterwards.
I've tried the newest v27 and the keyboard is still too great. No Screenshots there because nothing changed.
Pure Eris 2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks Konikub for an awesome rom, original rom here.. Click Me
Whats New:
-Overclock'ed [Recommended 710mhz)
-Working Gallery
-Helix Launcher
-New Icons
-Wifi(fixed)
Removed:
-HtcLockscreen
-Clock from taskbar
-Other little things
Not Working:
-Power Down(gonna fix this asap promise )
Credits:
Me
Konikub- making the rom
Overclok-
Make It Faster:
Auto Killer Aggressive
Spare Parts Animations Fast
Download:Pure Eris 2.0
Looks fantastic. I love Sense, but may try this for giggles. Thanks for the work!
Nice, looks good, T.C.P i did pm you,
This looks pretty awesome I might just use this if there are no big problems...can't wait to try it out!
TopazAaron said:
Nice, looks good, T.C.P i did pm you,
Click to expand...
Click to collapse
ok pm'd back
T.C.P said:
ok pm'd back
Click to expand...
Click to collapse
ok thanks, and replyed also.
F5
thanks.
thanks ....... this looks good ......
The auto rotate is not working just letting you know unless something didnt go right with the flash.
Nice, this is what I've been waiting for Can't wait to give it a download tonite.
Thanks!
A couple issues.
Looks pretty cool.
A couple of notes:
*I've actually got a pretty similar project called Tainted Vanilla http://forum.xda-developers.com/showthread.php?p=6414649
*Contrary to what the author of the rom states, it is *not* stripped of sense any more than my rom is. There are pieces of sense that can't be removed and they are in this rom too. (examples included in this rom include HTCAlbum, HTCCamera, HTCDialer, HTCFacebook, HTCTwitter, HTC's Browser, etc.)
*This rom includes a launcher from the market (Helix launcher) which is great & free, but not open source. Including it in this rom is a bad idea as it's infringing on copyright.
Looks great though, nice work.
Can someone post a Linpack score please? thank you very much!
i can't get this rom to boot ....i have flashed it twice ....even redonloaded it ....both time i go into an endless bootloop
E: Failure at line 2: asser getprop("ro.product.device") == "heroc"
installation aborted
Click to expand...
Click to collapse
Couldn't flash the maps version...
rvpartsguy said:
i can't get this rom to boot ....i have flashed it twice ....even redonloaded it ....both time i go into an endless bootloop
Click to expand...
Click to collapse
did u wipe? and then flash?
droidfreak said:
Couldn't flash the maps version...
Click to expand...
Click to collapse
try downloading againg and wipe dev/factory reset im running it right now and it worked for me
T.C.P said:
try downloading againg and wipe dev/factory reset im running it right now and it worked for me
Click to expand...
Click to collapse
I wiped everything, but will download and try again..
droidfreak said:
I wiped everything, but will download and try again..
Click to expand...
Click to collapse
the update script is wrong. That wrror means he didnt change heroc to desirec in the metainf folder.
Spencer_Moore said:
the update script is wrong. That wrror means he didnt change heroc to desirec in the metainf folder.
Click to expand...
Click to collapse
i did chance it, because i flashed it to mine and it worked and my girlsphone too, but ill double check it
When I went to download again the file had a different name and was a little bigger... I am flashing the new download...
edit: Same name but just entered differently..
addition: flashed now booting up....
This is the Gingerbread keyboard apk and appropriate libs to make it work on any Froyo rom on Eris (probably).
Please report back with feedback.
EDIT: PLEASE! If you're not in the mood to have to wipe and reflash in case this doesn't work, do a Nandroid Backup before flashing. (Duh.)
Thanks to Workshed, I've got everything sorted out.
Mind you I'm devving while on vacation in Hawaii sipping on a Kirin Ichiban.
downloading and flashing
got
E: cant find update script
installation abortion
im running froshedyo v7
Sweet. I really hope this works lol.
I did test the two files on my phone, but I'm not sure how my update.zip will work. I'm not entirely sure how to make the updater-script. I kinda just lifted one from another update.zip >.<
Retrogress said:
downloading and flashing
got
E: cant find update script
installation abortion
im running froshedyo v7
Click to expand...
Click to collapse
You might want to redownload and try again. He just pulled original download link and redone it.
Thanks. Re-writing the script right now. I'll have it up in the next 5 minutes or so.
Edit: Posted updated version. Please report back with results.
Installed with no problems on KaosFroyo V38 with clockwork but on reboot i dont have the new keyboard. all i get is HTC IME MOD and Multitouch
Agh. Trying to figure this out.
flashed successfully, but my phone wouldn't boot
doing a nandroid restore
Retrogress said:
flashed successfully, but my phone wouldn't boot
doing a nandroid restore
Click to expand...
Click to collapse
So very glad you backed up... I need to figure out what's up with this.
Edit: Tenzo tells me I don't need the line to set permissions, and I need to add lines to remove the previous versions of the files that are being replaced. Currently working on that.
when i flashed i got syntax error in update script any ideas
aw shoot. I'll fix it tomorrow hopefully.
i did a manual install this way:
http://forum.xda-developers.com/showthread.php?t=764021
and it repeatedly crashes every 2 sec.s
Here you go Agent, replaced update-script with the newer updater-script... should work fine now. You can use this dload link for your main dload link on the OP if you'd like.
Stock Gingerbread Keyboard: GingerbreadKB-STOCK-5thAgent.zip
Flash in recovery...
You can also grab a nice blue themed GB keyboard by Macrodroid in my thread.
workshed said:
Here you go Agent, replaced update-script with the newer updater-script... should work fine now. You can use this dload link for your main dload link on the OP if you'd like.
Stock Gingerbread Keyboard: GingerbreadKB-STOCK-5thAgent.zip
Flash in recovery...
You can also grab a nice blue themed GB keyboard by Macrodroid in my thread.
Click to expand...
Click to collapse
flashed on KaosFroyo v38 and worked great! Many thanks!
Thanks, Workshed!
5thAgent said:
Thanks, Workshed!
Click to expand...
Click to collapse
Not a problem, you're most welcome.
Thanks to you & Macrodroid!
Thanks for kickin ass guys for real
Sent from my Sinister eris using xda app.
Can someone post pictures? What's the difference with the old keyboard?
yanger said:
Can someone post pictures? What's the difference with the old keyboard?
Click to expand...
Click to collapse
This is the Gingerbread KB... this one is skinned blue, the stock is the same, just gray and black.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can grab this blue one here if you'd like - http://forum.xda-developers.com/showthread.php?t=824160&page=120
workshed said:
This is the Gingerbread KB... this one is skinned blue, the stock is the same, just gray and black.
You can grab this blue one here if you'd like - http://forum.xda-developers.com/showthread.php?t=824160&page=120
Click to expand...
Click to collapse
Damn, sure wish I would have seen this kb before I spent the time to skin my own.
Sent from my nonsensikal froyo
We have some additional problems.See the picture below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know where's the problem here.I put the kernel in the cm7/device/lg/swift directory but now there's this error.If you know something please tell us.
Please help
Please help us.If we solve all of the problems we will release the first build soon.
what error are you getting?
eoghan2t7 said:
what error are you getting?
Click to expand...
Click to collapse
As you can see in the picture maybe some files are missing.I will take a look at openswift's source and try to fix this.
eoghan2t7 said:
what error are you getting?
Click to expand...
Click to collapse
I get this errors when I type the code highlighted it the picture.
make sure no files have brokin during repo sync and that you have modded the source correctly
Edit the file / android_manifest/hardware/msm7k/Android.mk '
On the line: msm7k_adreno_dirs: = $ (common_msm_dirs) boot libgralloc-qsd8k libaudio
Remove "libgralloc-qsd8k libaudio".
I have already encountered this issue and many others when trying to build cyanogen. I have given up for a bit as its a real pain in the butt to get to build successfully.
I found some of the build issues and solutions on this page:
HTML:
http://translate.google.co.uk/translate?hl=en&sl=ru&u=http://4pda.ws/forum/lofiversion/index.php%3Ft215440.html&ei=2ICoTYaMOMjDhAf9gvTQCQ&sa=X&oi=translate&ct=result&resnum=8&ved=0CFkQ7gEwBw&prev=/search%3Fq%3Dgt540%2Balready%2Bdefined%2Bby%2Bmsm7k%26hl%3Den%26safe%3Doff%26client%3Dfirefox-a%26hs%3DnO8%26rls%3Dorg.mozilla:en-GB:official%26channel%3Dnp%26prmd%3Divnsfd
This problem has been solved however we have additional problems which I will post later.
ephraim87 said:
Edit the file / android_manifest/hardware/msm7k/Android.mk '
On the line: msm7k_adreno_dirs: = $ (common_msm_dirs) boot libgralloc-qsd8k libaudio
Remove "libgralloc-qsd8k libaudio".
Click to expand...
Click to collapse
Its a wrong way. Just use a TARGET_PROVIDES_LIBAUDIO := true in your build configs. And you should try edit a CM sources as minimum as you can.
And I do not undrstand what makes sense to do it if it's already done?
Instead of this try to build a Codeaurora version, they can be a more fast and powersaving.
The topic has been updated.If you know something please post the answer below.
Thanks in advance.
Mur4ik said:
Its a wrong way. Just use a TARGET_PROVIDES_LIBAUDIO := true in your build configs. And you should try edit a CM sources as minimum as you can.
And I do not undrstand what makes sense to do it if it's already done?
Instead of this try to build a Codeaurora version, they can be a more fast and powersaving.
Click to expand...
Click to collapse
I didn't change anything in the cm source.
Mur4ik said:
Its a wrong way. Just use a TARGET_PROVIDES_LIBAUDIO := true in your build configs. And you should try edit a CM sources as minimum as you can.
And I do not undrstand what makes sense to do it if it's already done?
Instead of this try to build a Codeaurora version, they can be a more fast and powersaving.
Click to expand...
Click to collapse
Is the code aurora rom easier to build than cyanogenmod?
fdespotovski said:
Is the code aurora rom easier to build than cyanogenmod?
Click to expand...
Click to collapse
Should I download the source?
Should I download the source?
Click to expand...
Click to collapse
If you can build ROMs without sources, then no, you should not download the sources
And if you did not know something about C or C++, and you can not write/change a drivers, then you waste your time now. Just building from source does not get you anithing.
Mur4ik said:
If you can build ROMs without sources, then no, you should not download the sources
And if you did not know something about C or C++, and you can not write/change a drivers, then you waste your time now. Just building from source does not get you anithing.
Click to expand...
Click to collapse
We know Visual Basic, if that makes any difference.
Im glad you have some of the problems fixed fdespotovski. I was bored while doing my final year project for uni so I thought to have a go at building Android, turns out its a bit of a chore to do. Closest thing to c++ is java which I am on good turms with.
Although with java I can at least write some good apps for Android.
ephraim87 said:
Im glad you have some of the problems fixed fdespotovski. I was bored while doing my final year project for uni so I thought to have a go at building Android, turns out its a bit of a chore to do. Closest thing to c++ is java which I am on good turms with.
Although with java I can at least write some good apps for Android.
Click to expand...
Click to collapse
Thaks for the post!We don't know any other programming languages than Visual Basic.Net and we are still learning it.We will try to fix the problems but if we don't succeed maybe we will give up.Building Android is a hard work when you don't know what you are doing.