Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Android Zaurus

Pages: [1] 2 3
1
Android / Google Android M5-rc14 Installable Image Available!
« on: May 13, 2008, 04:56:56 am »
Finally, touchscreen driver has been fixed. Now touchscreen works correctly.

Android Zaurus: Touchscreen works!
http://androidzaurus.seesaa.net/article/96581331.html

A reader of my blog has done a great job! Big thanks to Rebecca.

Cheers,

2
Android / Google Android M5-rc14 Installable Image Available!
« on: April 12, 2008, 11:24:15 pm »
A hacker in Japan successfully runs m5-rc14 on C700! His blog is written in Japanese, so I translated roughly.

o Android Zaurus: Android m5-rc14 on Zaurus C700

Very interesting news here is, frame buffer driver of C700 (w100fb.c) doesn't have double buffer support. Double buffer may not be mandatory for some cases. I'll update if there's any progress.

Cheers,

3
Android / Android On Nokia N810
« on: April 11, 2008, 03:33:59 am »
Quote from: speculatrix
well, someone's been hard at work!

Yeah, I'm glad to know their hard work paid off.

Dirk, the owner of "Android on OMAP" on elinux.org, had the same issue with our "m5 on Zaurus project", which was turned out to be double buffer support in frame buffer driver. Since Dirk successfully up Android on OMAP dev board, I was hoping somebody starts to port Android to N810. And found this post on April 1.
o Android on Nokia n810 (OMAP2420) - Android Internals | Google Groups

I'm really glad Android runs on more and more platform. Next target is Nintendo DS --- just kidding. But iPhone/iTouch is possible.

Cheers,

4
Android / Opera
« on: April 11, 2008, 02:58:41 am »
Quote from: jfv
Just saw this: Opera Mini and I wonder if it'll run on the Zaurus.

I tried Opera Mini on my Android Zaurus. It works. But there are a lot of issues, which happpen as well on emulator. I think the current version is more like a proof of concept than an alpha version.
  • can not scroll with cursor keys
  • can not change font size
  • can not set focus at input form
  • crashes a lot
  • UI is not optimized for Android - everything through [Menu] key
Anybody behind firewall, keep it in mind that Opera Mini uses TCP port 1080 to connect to Opera server. As documented in labs.opera.com, Mini retreives Web pages as compressed OBML format through Opera server.

Cheers,

5
Android / Google Android M5-rc14 Installable Image Available!
« on: March 10, 2008, 05:26:14 am »
I totally forgot about updating my RotateView to m5-rc14/rc15. Just uploaded to my blog.

o Android Zaurus: RotateView for Android SDK m5-rc14/rc15

Eventhough I made some improvement in double buffer handling of frame buffer driver, still rotating display eats a lot of CPU power. A lot slower than portrait view.

Have fun.

6
Android / Google Android M5-rc14 Installable Image Available!
« on: March 06, 2008, 05:27:34 pm »
Quote from: speculatrix
fired up android and the browser, it reports "Page Load Suspended
No network coverage. Lod will resume when network connection recovers"

I think that 3G is stuff. We can ignore it for now.

Did you set net.eth0.dns1 in etc/default.prop?

7
Android / Porting M5rc14 To Real Hardware
« on: March 03, 2008, 06:08:59 am »
zaurick

Thanks for your tips. I guess I need to check the differences between fbi->fb.var and var.

Today I tried schedule_work() instead of changing DMA address at once. It seems OK. Flickering is gone.

o Android Zaurus: Improvement of double buffer

8
Android / Porting M5rc14 To Real Hardware
« on: March 02, 2008, 07:24:52 am »
Quote from: zaurick
Normaly the base adresse is calculated with the var.yoffset value from var_screeninfo.
I'm going to work on that !

Big thanks from me. I'm not familliar with fb driver. Please make the patch better. I noticed that some long cycle flickerings while I tried a couple of times booting Android up. I guess I need exclusiveness to change DMA address.

9
Android / Porting M5rc14 To Real Hardware
« on: March 02, 2008, 02:56:04 am »
Today I implemented my version of double buffer and pan in pxafb. It works. m5_rc14 booted up on my Zaurus finally. My patch is very primitive. Any suggestions make it better are very welcome.

o Android Zaurus: m5_rc14 works on my Zaurus C3000

Cortez,
Is your keyboard working correctly? Something funny with mine. I can't navigate on the menu by cursor keys. It's like a jumping around.

10
Android / Screenshots?
« on: February 28, 2008, 11:44:41 pm »
Andy Rubin, the Android Guy himself shows off a prototype of Android 3G phone.

BBC NEWS | dot.life | A blog about technology from BBC News | Under the bonnet of Android

Smooth Web browsing, Quake at 30fps, Google Maps Street View.

I want it NOW!

Cheers,

11
Android / Porting M5rc14 To Real Hardware
« on: February 27, 2008, 08:01:25 pm »
Is there anyone who is familliar with OpenEZX?
http://www.openezx.org/

Their wiki mentions double buffer support.
  • video/pxafb.c  MV file, changes for backlight timer, 18bpp/19bpp and double buffering support
http://wiki.openezx.org/CodeAnalysis

I looked around their svn, but I couldn't find paticullar patch or source code.

12
Android / Porting M5rc14 To Real Hardware
« on: February 27, 2008, 05:39:33 am »
Cortez,

Thanks for trying to make a module.

Quote from: cortez
It says "page flipping not supported (yres_virtual=640, requested=1280". I think this is the problem we're facing.

Gee. We need a double buffer capable driver. Means a bit of work to modify current pxafb driver code.

13
Android / Porting M5rc14 To Real Hardware
« on: February 26, 2008, 08:32:55 pm »
My guess for now. Let the Android use drivers/video/pxafb.c not platform driver in arch/arm/mach-pxa. I'm working on another project for now and my Zaurus is configured for m3 Android. Later I'd like to try to build the kernel with CONFIG_FB_PXA=m and see what happens.

By the way, I found this wiki is very informational.

Android on OMAP - Embeddedlinux
http://elinux.org/Android_on_OMAP

14
Android / Porting M5rc14 To Real Hardware
« on: February 19, 2008, 09:47:52 pm »
Quote from: Mrflying
2). There's nothing appear on the screen. (screen is turned to black,
it doesn't happen on previous version, too)

Same for Angstrom Zaurus. Just blank screen, nothing displayed.

I don't think this would work though, give a try to copy /dev/fb0 to /dev/graphics/fb0 and chmod 666. The emulator is working like that.

Android Zaurus: Confusing issue of Android m5_rc14
http://androidzaurus.seesaa.net/article/84934031.html

15
Android / New Sdk And Galleries/videos
« on: February 14, 2008, 04:55:26 am »
Dont' forget emulator -wipe-data once, if you already have older version in your PC.

By the way, I tried to boot it up on my Zaurus. No happy yet.
Android Zaurus: Android SDK m5_rc14 release

Cheers,

Pages: [1] 2 3