help with android 2.2 on Fujitsu Lifebook p1510

[mrkavanagh]

I have a Fujitsu Lifebook p1510 that I have successfully installed the
generic android 2.2 x86 on, but I have problems. I installed it
directly to the hard drive and I have also tried to install it to its
own partition.

I can not get the touch screen to work nor does the wireless work?

This would make for an excellent android tablet if I could get all the
hardware to work. Would I be better off running android through
VMware?

What am I missing?

PC specs

Processor Name
Intel Pentium M 753
Operating System
MS Windows XP Professional
Processor Speed
1.2 GHz
RAM
512 MB
Weight
2.2 lb
Screen Size
8.9 inches
Screen Size Type
widescreen
Graphics Card
Intel Graphics Media Accelerator 900 GM
Storage Capacity (as Tested)
30 GB
Networking Options
802.11g
Primary Optical Drive
External

[phigan]

On Apr 18, 6:58 am, mrkavanagh <dlkma...@gmail.com> wrote:
> I have a Fujitsu Lifebook p1510 that I have successfully installed the
> generic android 2.2 x86 on, but I have problems. I installed it
> directly to the hard drive and I have also tried to install it to its
> own partition.
>
> I can not get the touch screen to work nor does the wireless work?
>
> This would make for an excellent android tablet if I could get all the
> hardware to work. Would I be better off running android through
> VMware?
>
> What am I missing?
>

I too would like to to see Android working with touchscreen and wifi
on my P1510, but I can't tell how much of a project getting these to
work is going to be. From what I understand, the touchscreen should
just be a serial interface. Hopefully the wiffi issue is just a matter
of copying the drivers that work in Linux.

I've been booting off USB stick so far, and it seems a little
sluggish. Which of the three video options did you choose?

[Arobase40]

I have the Fujitsu LifeBook P1610 which is very close to the P1510
model.

Those 2 models use a serial wacom based touch panel and I think an
Intel based 3945BG WiFi chipset.

I wanted to create a custom build for them, but haven't got the time
to work on it yet, as I'm working on the Acer Aspire target at the
moment.

I guess the generic build doesn't make use of HW Acceleration (not
sure) and the lattest source code is still incompatible with the Intel
GMA 950 (or GMA 945 ?) gfx card.

I'll try to see if I can work on this project, but I can't tell when
it will be ready...

[Arobase40]

I started working on the target for the Fujitsu P1610 and P1510 : got
Wifi, Bluetooth, Ethernet, SD Card and sounds working.
The P1610 doesn't have a webcam so I don't know if this works or not.

Almost finished the implementation of the serial touchscreen based on
Stefan wacom-input : ts_calibrate is still not working...

But the most troubleshouting issue, is that the 945GM GPU sounds not
to be supported either by latest or older Mesa driver, so only got
Vesa 1024x768x16, and it is much too slow to be usable.

I got the same issue with an Asus U1F with same GPU.

So I guess this is a dead end, unless the Mesa driver got fixed !

Sorry for the bad news.

[Andy in Indy]

Where should I look to find the p1610 configurations you were working on?  "make" does not recognize TARGET_PRODUCT=p1610 for froyo or gingerbread.

[ppafford]

I have P1610 I WOULD LOVE TO TEST THE INSTALLATION WITH

[Arobase40]

@ Andy in Indy and ppafford,

The target is not available in the official tree, as it's still in pre-
alpha version
As I mentioned above this build is on standby or may be dead, as HW
Acceleration is not working at all !!!

If P1510 has a camera, it may work for a second then crash
immediately. Photos Gallery both with P1510 or 1610 is real slow, so
you may have thumbnails, but could not display pictures in full size.
No videos play back, nor youtube and any apps that need HW
acceleration will not work either.

Ts_calibrate is not working either, so touchscreen as well for the
moment, as when I saw HW Acceleration was not functioning I just gave
up and stop the development.

That ,means you could only use the build with the trackball and the
keyboard.... ^^ Not really user friendly.

What work : got Wifi, Bluetooth, Ethernet, SD Card and sounds working,
virtual keyboard in your own language. But without touchscreen : not
really useful... ^^
Power management is not working at all BTW (so display timeout is set
by default to "NEVER").

At least you can use it only for Web Browsing and listening MP3
files. ;-)

If you're still want to test this build, send me a private mail, and
I'll tell you where to download it.

If you have some knowledge about development and building, I can also
send you the target, so if you have any idea about touchscreen (at
least ts-calibrate), and may be about Mesa, I'll be please to share
the work with you.... ^^ ;-)

Regards,

Arobase

[Andy in Indy]

I'll send the private message as soon as I can.  The e-mail unlock seems to be off line.

I should be able to do the ts_calibrate or work around it.  I don't know anything about Mesa, but I have a week off to learn something new. :-)

-Andy in Indy

[Arobase40]

@ Andy and @ ppafford

I sent you both the tar ball.

Arobase

[Andy in Indy]

Okay,  I downloaded and moved the device files into the Froyox86 file system, synched, lunched and tried to build.  I would up with an error building pmem.  When I switched to generic-x86, everything builds just fine.  Any ideas about where this is coming from?  There output is below.

-Andy in Indy

  CC      kernel/configs.o

  LD      kernel/built-in.o

  CC      drivers/misc/pmem.o

/home/andy/Desktop/Froyox86/kernel/drivers/misc/pmem.c: In function ‘flush_pmem_file’:

/home/andy/Desktop/Froyox86/kernel/drivers/misc/pmem.c:805: error: implicit declaration of function ‘dmac_flush_range’

/home/andy/Desktop/Froyox86/kernel/drivers/misc/pmem.c: In function ‘pmem_setup’:

/home/andy/Desktop/Froyox86/kernel/drivers/misc/pmem.c:1275: error: implicit declaration of function ‘ioremap_cached’

/home/andy/Desktop/Froyox86/kernel/drivers/misc/pmem.c:1276: warning: assignment makes pointer from integer without a cast

make[4]: *** [drivers/misc/pmem.o] Error 1

make[3]: *** [drivers/misc] Error 2

make[2]: *** [drivers] Error 2

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/andy/Desktop/Froyox86/kernel'

make: *** [out/target/product/p1x10/kernel] Error 2

make: Leaving directory `/home/andy/Desktop/Froyox86'

[Chih-Wei Huang]

Disable PMEM. It doesn't support by x86 platform.

2011/7/12 Andy in Indy <andrew...@gmail.com>:

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Arobase40]

Sorry, I forgot to mention I disabled pmem in kernel/driver/misc/
Makefile. ^^ ;-)

May if you mailed me, I would have told you about this... :-D

[Arobase40]

This can be done also modifying the Kconfig file.

[lunar]

Hello there,

I have a p1510, too and recently installed android 2.2 x86. I too
would like to work on wifi and touch screen issue which I have no idea
how to solve the issues.

Can anyone help me with that?

Truly appreciated in advance.

[Arobase40]

If the wireless card is the same as the P1610, the problem is solved
with my target, but there is still issues with touchscreen : at least
with ts_calibrate.

I have to do some more testings with uvesa, as Mesa is not working.

[lunar]

Thanks very much Arobase40 for the reply.

I am sorry for being silly here, but your target?

Can you please send me that and teach me how to do it?
I am so sorry if this bothers you much.

Look forward to hearing from you soon

[Arobase40]

Ok, I can send you the target BUT you are supposed to know the basis
about Android and the building process. So you'll be on your own with
it.

BUT, if you find something useful, you'll have to share it back with
me.

If I share the sources, it's because I need myself some helps.

This is the second time, I share my sources (Aspire 1000s for the
1825PTZ, and this one), a dozen of people are holding them in their
hands and I never got a single feed-back, nor a hello. Never beg for
thanks either, but still !!!

If I forgot something, such as the pmem file, I'll answer you, but I
can't teach you how to use the target...

So if you agree with this, send me your email.

[Arobase40]

I finally partially retrieved the video settings so there is no need
to use debug mod with nodemodeset option, so it boots directly with
MDPI even though it's still work s with uvesa mode without HW
Acceleration. Ethernet, Wifi and Bluetooth are still working. pairing
with a BT keyboard is still a ass due to the need to enter a code and
don't get paired easily. But it works quite fine with a BT headset
without the need to enter any code. Camera should work if there was HW
Acceleration (tested with an Asus U1F with a webcam), but due to this
limitation the webcam only works for a second before crash.
Internet connexion is fairly fast. Mouse moves quite fine, except when
setting dialog boxes are in use.

As SD Card was disabled with this build, I couldn't test sounds, nor
photos gallery even though I know it's quite slow...

ts_calibrate is still non functioning, for some unknown reasons. :(

[Arobase40]

Hallelujah !!!

Got HW Acceleration both with P1610/P1510 and Asus U1F !!!!

ts_calibrate pop up now (manually though), but I can't select the
different points yet in order to get touchscreen working. ^^

Should be very close to get a functional touchscreen device... ;-)
Hopefully...

Webcam works fine with Asus U1F as this is the only device that has
one. Photo Gallery works fine either with both devices P1610 & U1F.
Ethernet, Wifi and Bluetooth still working except for the Asus U1F
with which I got an error. I guess I missed something.

Resume does not work at all for the moment.

Resolution for the Asus U1F = 1366x768, while P1610 = 1280x768 !!! :-D

Arobase

[StefanS]

That is great, how did you get the HW accell to work???

Stefan

[Arobase40]

With the old Mesa lib... ^^ ;-)

[Andy in Indy]

Congratulations on the progress!  I am still trying to work my way through understanding the way this is all put together (full time job and teenage daughter = not much free time).  I am still way too new at this. :-)

-Andy in Indy

[Shady Rasheed]

Hello There

I have a Lenovo Idea Pad S10e which uses the same gpu as your lifebook
I tried fruitlessly to get HW working.. but reached a dead end.
Can you give me some pointers on how you managed to have HW acceleration working?
Am using gingerbread, but willing to fall back to 2.2 if I can get decent graphics and decent video playback. Unfortunately for me, the statement 'using old mesa lib' didn't help me enough to know where to start!

Quick question: does having HW acceleration improve video playback? On 2.3.4, the UI is very smooth as good as on my nexus one, but video playback is at a very low framerate, and the video is pixelated.

Any help or pointers to the right direction are highly appreciated.
Thanks in advance.

> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>

[Arobase40]

Wait for tonight or tomorow (Paris - France TimeZone).

I will explain everything ! I guess I located the Mesa issue for
almost every CPU/GPU if not all supported GFX chipsets, whether with
the old or latest MESA version !!!!

At the moment, I got it work with i945GM and GMA 4500HD...

I still have some works in progress and more testing to do to confirm
my theory and conclusion.

This is a SILLY SILLY STUPID little thing... ^^

Some may laugh, some others may not. I myself am just in between as I
spent some much time, just to discover the issue was soo simple to
solve... ^^ :(

For the rest of your questions, you also have your answers. If not
step backward some posts above (Hallelujah !!! ).

On 26 juil, 11:38, Shady Rasheed <rasheedsh...@gmail.com> wrote:
> Hello There
>
> I have a Lenovo Idea Pad S10e which uses the same gpu as your lifebook
> I tried fruitlessly to get HW working.. but reached a dead end.
> Can you give me some pointers on how you managed to have HW acceleration
> working?
> Am using gingerbread, but willing to fall back to 2.2 if I can get decent
> graphics and decent video playback. Unfortunately for me, the statement
> 'using old mesa lib' didn't help me enough to know where to start!
>
> Quick question: does having HW acceleration improve video playback? On
> 2.3.4, the UI is very smooth as good as on my nexus one, but video playback
> is at a very low framerate, and the video is pixelated.
>
> Any help or pointers to the right direction are highly appreciated.
> Thanks in advance.

> On Jul 23, 2011 9:28 PM, "Arobase40" <arobas...@gmail.com> wrote:> With the old Mesa lib... ^^ ;-)

[Shady Rasheed]

Hello Arobase40,

I tried the settings you posted about i915, however I didn't notice a difference. I'm not sure if I understood correctly, would you please confirm if the steps below are correct?

In my target folder I set the BOARD_USES_I915C and 965C to true
In the s103t_info file, I set the FB0DEV=i915

I compiled and ran ... but no difference there. I checked logcat, I didn't see any line stating HW acceleration enable or disabled (although in one of the images I used before, can't recall which, it used to state that it wasn't enabled)

When in portrait mode, the graphics in the second half of the screen are offset a bit (if you are reading a sentence half way through the sentence, the line is drawn a few pixels lower than the begining)

My S10e netbook is Atom N270 based, uses the 945 gpu that you also have.
Your assistance in getting the gpu to run (at least for videos to play properly) is highly appreciated.
Thanks in advance

[Arobase40]

Hi Shady,,

if you are talking about this thread :

http://groups.google.com/group/android-x86/browse_thread/thread/40294e60f008152c#

I guess you endeed misunderstood it.

According to Chih Wei, there is no problem with your settings.

According to me, I thought your Atom based Netbook should not be
affected by the New Mesa version, and the issue. But may be you're an
exception... ^^

In my thread, I explained the FB0DEV=i915 setting in the s103t_info
file should NOT be used at all (at least I thought this was just the
case for the laptops), so just remove it.

Then I'm unsure if BOARD_USES_I915C and 965C to true can be used
together, so test by yourself, and let me know.

On 30 juil, 11:57, Shady Rasheed <rasheedsh...@gmail.com> wrote:
> Hello Arobase40,
>
> I tried the settings you posted about i915, however I didn't notice a
> difference. I'm not sure if I understood correctly, would you please confirm
> if the steps below are correct?
>
> In my target folder I set the BOARD_USES_I915C and 965C to true
> In the s103t_info file, I set the FB0DEV=i915
>
> I compiled and ran ... but no difference there. I checked logcat, I didn't
> see any line stating HW acceleration enable or disabled (although in one of
> the images I used before, can't recall which, it used to state that it
> wasn't enabled)
>
> When in portrait mode, the graphics in the second half of the screen are
> offset a bit (if you are reading a sentence half way through the sentence,
> the line is drawn a few pixels lower than the begining)
>
> My S10e netbook is Atom N270 based, uses the 945 gpu that you also have.
> Your assistance in getting the gpu to run (at least for videos to play
> properly) is highly appreciated.
> Thanks in advance

[Shady Rasheed]

Alright,

I tested the foryo-x86 branch with my target, Compiles but doesn't boot ... (first time I try froyo) logcat keeps showing line after line " Waiting for sevice media.audio_policy"

So i rebuilt the generic_x86 build of froyo-x86 with the changes that you mentioned applied.

It worked, the gallery is much faster, the world clock is smoother and the camera works. And the interface doesn't slow down when a dialog box is showing.

I will try to get the settings working with my target (which is based on the s103t, my netbook is an s10e)

However, the interface in gingerbread is much smoother than in froyo, not sure if this has to do with the drivers or just froyo vs gingerbread.

Quick question: Would this work in gingerbread too? 

Thanks a million for your help, I will try some different combinations and post back with more results.

[Arobase40]

I'm happy this helps you...

I can't tell much about gingerbread-x86 and for what I know there is
no official MESA support.

I know there is work in progress made by Chia-I Wu but haven't got
time to fully test it.

I guess I won't even do as, as as Chih Wei said I'm waiting his time
and may be the development team time by the way...

Regards,

Arobase


Shady Rasheed a écrit :

[Chih-Wei Huang]

2011/7/31 Shady Rasheed <rashee...@gmail.com>:

> So i rebuilt the generic_x86 build of froyo-x86 with the changes that you
> mentioned applied.
> It worked, the gallery is much faster, the world clock is smoother and the
> camera works. And the interface doesn't slow down when a dialog box is
> showing.

Wow, another Arobase?

The facts are:
* There is no FB0DEV setting in generic_x86.
* The hardware acceleration is not enabled in
the generic_x86 build.
(unless you tried to turn on it yourself)

What changes you applied exactly? Please show us.

[Shady Rasheed]

Hello,

As I said, when I used the s103t target on my s10e board in foryo-x86, it simply doesn't boot. So i had to go to the generic_x86. 

The default settings in the generic_x86 do not work for my netbook, so i changed the def config (CONFIG_WL=m) and the BoardConfig.mk (BOARD_USES_ ... ) 

I also created a file  named generic_x86_info (i have no idea if this affected the build in any way) which is the same as the s103t_info file (but without the FB0DEV)

I also changed the overridable value of uses the 3d from false to true.

The above settings (as messy as they seam, I applied them for the purpose of a quick test) showed a difference in performance. Where before, gallery wouldn't open, camera wouldn't work, and the interface became sluggish with dialog boxes showing. Now, all that works. Unfortunately, I never managed to play videos in froyo-x86. (it shows a message stating that the video can't be played)

I currently use Gingerbread-x86 (using the s103t target from froyo-x86 and the CONFIG_WL=m in the defconfig) The performance of the UI is fantastic, and everything installs and runs (with the exception of the arm specific apps) My question is, how could I improve video playback on it (gpu is i945GM) ??? Will we see Mesa for gingerbread soon?

Side question: Any app that tries to access the internal mic, such as the speech recorder, causes a force close. Have you come across something similar?

Any help is highly appreciated. 

I hope the android-x86 project doesn't loose any members. I'm sure that all discussions, as heated as they become, are still valuable in one way or another.

--

[Chih-Wei Huang]

OK, thank you for the info. Sounds you have enabled
the hardware acceleration, that's fine.

But please state it clear at the first time.
Because when you said you used the generic_x86 build,
I expected you use the default generic_x86 settings.
We can't guess you have done so much changes.

The FB0DEV should be removed in s103t_info.
That's right. But I left it to the maintainer of this target.
Anyway, it's just a surplus and can't do harm.
You can try to add it back and it won't change anything.

For the video playback issue, I suspect it's because
your sound driver is not configured correctly.

2011/8/1 Shady Rasheed <rashee...@gmail.com>:

--

[SkyPhoenix Loo]

Hi, I'm new to Android. I've installed Android OS X86 to my Tablet PC (Futjitsu P1610).

 

But the problem is, the touch panel doesn't work, the device I'm using is touch pen.

And there is no sound there even I've maximum the sound volume. 

In my current MS. Win7, it have the software called, "3G Watcher". It can be using a SIM-card to online and make call.

The problem is in Android OS, that I've installed can't support this function.
Do you have any suggestion or solution for these problem?
 
Can you help me solve those problem?

• Touch Pen
  
• Sound device.
• WiFi / Doesn't work.
  
• Sim-Card [3G Watcher]
  

Device details:

• SigmaTel High Definition Audio CODEC
  
• Sierra Wireless HSDPA Network Adapter
  
• Intel(R) PRO/Wireless 3945ABG Network Connection
  
• Sierra Wireless MC8755 HSDPA Modem
  
  
  

Thanks,

Your Sincerely, 

Phoenix

[SkyPhoenix Loo]