Notices


Reply
Thread Tools
Posts: 101 | Thanked: 132 times | Joined on Apr 2010 @ Switzerland
#21
Hello,
I'm working exactly on that subject - porting Dvalik on Linux, standard kernel + android modules if necessary + standard linker ld.so:
http://ymartin59.free.fr/wordpress/i...et-n900-maemo/
Any help is welcome
 

The Following 7 Users Say Thank You to ymartin59 For This Useful Post:
clasificado's Avatar
Posts: 466 | Thanked: 180 times | Joined on Feb 2010
#22
it worths a try!
 
sytheii's Avatar
Posts: 57 | Thanked: 10 times | Joined on Jun 2010
#23
Originally Posted by ymartin59 View Post
Hello,
I'm working exactly on that subject - porting Dvalik on Linux, standard kernel + android modules if necessary + standard linker ld.so:
http://ymartin59.free.fr/wordpress/i...et-n900-maemo/
Any help is welcome
Hellz Yea!
__________________
Can you see them?
 
Posts: 97 | Thanked: 12 times | Joined on Feb 2010
#24
Originally Posted by ymartin59 View Post
Hello,
I'm working exactly on that subject - porting Dvalik on Linux, standard kernel + android modules if necessary + standard linker ld.so:
http://ymartin59.free.fr/wordpress/i...et-n900-maemo/
Any help is welcome
great
how can we help?
 
Posts: 101 | Thanked: 132 times | Joined on Apr 2010 @ Switzerland
#25
Here are tasks in pipeline at the moment concerning developments on Maemo itself:
  • Create a userspace in-memory framebuffer device (or with a Maemo Linux kernel module). That device will be use by Android application to draw as a virtual screen.
  • Create a Maemo application ("android-ui" in Qt) to display framebuffer content as fullscreen or in a window with menu. This application will intercept mouse and keyboard events and direct them to Android processes - question to investigate: how/where Android binaries get that events.
  • Port and compile Android modules (/dev/binder and /sys/android_power) as modules for Maemo kernel or build in a power kernel for instance. Another option is to divert these interfaces usage in Android libraries (libc ?) by Maemo specific code.

I work myself on the Android build system itself - based on google open android sources and android-x86 project.
  • Investigate to understand how "/system/bin/linker" is created/used in the compile chain to force static address mapping
  • Replace this specific linkage by standard Linux ld.so method
  • Remove useless compilation sub-trees like "adb" to speed up dev cycle
  • First step: run /system/bin/gzip compiled from Android sources on standard Linux and then ARM Maemo

Any detailed information, proof-of-concept codes or how-to concerning any of these steps are welcome.

Last edited by ymartin59; 2010-07-05 at 10:00.
 

The Following 2 Users Say Thank You to ymartin59 For This Useful Post:
Posts: 109 | Thanked: 45 times | Joined on Aug 2010
#26
The majority of the android USAA app is just pointing to different "mobile" pages on the USAA web site (I've also used the android app and USAA is my bank). The only part that might be proprietary is the PIN interface that saves you from having to fully log in each time you go to the site.

You might see if you could find source code for a different linux mobile banking app and switch the urls around and see what sort of progress you make....
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 04:42.