Messages

1

Gemini PDA - General Discussion / Oreo on its way

« on: May 08, 2019, 01:07:27 pm »

Finally full update instructions for x25/x27 with 4G. No download yet for wifi-only
Download: http://support.planetcom.co.uk/index.php/G...droid_8_Upgrade
Update worked fine on my x25.

Can you confirm you had the following on screen before you selected manual upgrade? I have also X25 and all the info fields (PatchId, PatchSize, UpdateDate and UpdateInformation) are empty. I'm asking because I have done the manual update yesterday and my X25 had SIM card menu in Android settings. This menu was present on X27 only in Android 7.1. Can you check please if you have this menu (SIM card) in settings after the update?

 [img]http://support.planetcom.co.uk/images/e/e2/29.jpg\" border=\"0\" class=\"linked-image\" /]

2

Gemini PDA - Hardware / Wireless LED

« on: May 04, 2018, 06:03:02 pm »

According to the quick start guide coming with Gemini, there is another LED on the top of device (right side). I never saw it turned on. Is it really there?

It should turn on when your Gemini is charging.

I am talking about the LED on the RIGHT side :-)

3

Gemini PDA - Hardware / Wireless LED

« on: May 04, 2018, 01:54:14 pm »

According to the quick start guide coming with Gemini, there is another LED on the top of device (right side). I never saw it turned on. Is it really there?

4

Gemini PDA - Android / Google certification

« on: March 19, 2018, 10:39:22 am »

Can someone please open Play Store on her/his Gemini, go to Settings, scroll down to Device Certification and tell me if her/his Gemini is Certified or Uncertified? I flashed rooted bootloader, TWRP recovery, magisk manager and then reverted back to stock setup and my Gemini shows Uncertified status. I would like to know what was the status of the stock Gemini :-)

Did you try to fake device information with Magisk? I found Magisk module for this, but not sure if it can trick Google Play.

Yes I did. The result:

CTS Profile: False
Basic Integrity: True

That's why I asked for the Device Certification of the stock Gemini. You can't get CTS Profile: True in magisk if the stock device is Uncertified

I didn't try the module you linked

5

Gemini PDA - Android / Google certification

« on: March 19, 2018, 09:43:01 am »

Can someone please open Play Store on her/his Gemini, go to Settings, scroll down to Device Certification and tell me if her/his Gemini is Certified or Uncertified? I flashed rooted bootloader, TWRP recovery, magisk manager and then reverted back to stock setup and my Gemini shows Uncertified status. I would like to know what was the status of the stock Gemini :-)

6

Gemini PDA - Hardware / display orientation

« on: March 12, 2018, 01:04:38 pm »

Are there people out there with working display rotation? Not that I really intend to run the device much in portrait mode, but I do wonder about the sensor setup.

I do know that the compass is disabled in the firmware because Planet Computers did not get the compensation for the lid magnets working (I still would like to see if one can re-enable it, though, as you should be able to compensate for any static magnetic field, however complex the field lines flow), but it looks to me that people do have display rotation possibly working. When looking into SatStat, I see no information for compass (as we know) and also no information for orientation.

But I do see a working accelerometer that nicely indicates the direction of gravity when I am not spinning around the device. Should there be orientation information extracted out of that and is anyone getting screen rotation with the stock Android OS? I did toggle that setting for fixed/rotating display in the drop-down settings back and forth, nothing.

Both 'Force Landscape' and 'Force Portrait' option must be set off in App Bar settings in order to make rotation working! :-)

7

Gemini PDA - General Discussion / Just got it - observations and issues

« on: March 12, 2018, 10:46:42 am »

Tips:
The back plate does not close the same way it opens! It opens from the back, and closes at the front. See diagram in printed quick start guide. I tried forcing it close from the back – it doesn’t work like that!
...

What do you mean by that? Are you talking about the top/front plate or about the bottom/back plate? Both can be opened. I opened and close the front plate (as described in quick user guide) without any problem. Your tip is confusing at best!

8

C1000/3x00 General discussions / Full Debian On The Sl-c3000

« on: January 05, 2005, 07:19:55 pm »

1. screen calibration doesn't work. The pdaxrom calibration utility doesn't work with c3000 frame buffer driver anymore...

I believe the 3000 uses a different video chip, Intel PXA270' instead of the ATI. I think that may add some complexity to porting the pdaxrom to the 3000...

It's not about a different video chip. It seems to me there is no dedicated graphics chip (Intel 2700G) in the Zaurus. I just tried to compile the Zaurus C3000 Linux kernel with a patched frame buffer driver but there seems to be a lot of bugs and it's in question if to try to fix them or to wait until LAZE and MASLOVSKI fix them for us :-) That's why I dindn't produced any temporary pdaxrom for c3000 yet. My work will be obsolete when they decide to support the c3000...

Milan

9

C1000/3x00 General discussions / Full Debian On The Sl-c3000

« on: January 03, 2005, 03:43:51 pm »

IMHO we will have to wait for sharp to release an update to the c3000 ROM so developers will be able to hack the updating process as it's slightly different from other models (OS is now installed in the microdrive instead of internal flash memory) ... then we should be able to see some openembedded ROMS or cacko's one ... for a pdaXrom we will have to wait for some driver to be achieved for the new graphic chip but I think it could run in framebuffer too in a first time ^^ Oh and of course we will mainly have to wait for one of the developers of one of these roms to buy himself a c3000

In fact it it's not so difficult to get pdaxrom running on c3000. I have it on my c3000 after a great time of hacking/tweaking. You have to get C3000's hard drive initialized. It's not like a PC PCI HD, it's connected as a PCMCIA device so you have to get up and running the whole PCMCIA susbsystem prior the booting from the HD. The rest is pretty straightforward, I would say even easier than with cx00 series, because you can forget about different flash rom sizes etc. The only problems I found so far are:

1. screen calibration doesn't work. The pdaxrom calibration utility doesn't work with c3000 frame buffer driver anymore...

2. pdaxrom uses some kind of proprietary SD card manager kernel module. I can't compile this module for c3000 kernel because I have no source and there is a different kernel version (2.4.20 instead of 2.4.18).

So this is the report. based on my experience with pdaxrom team schedule, you can expect to have a pdaxrom distribution running sometimes in Q3/2005 :-)))


Milan

10

C1000/3x00 General discussions / Full Debian On The Sl-c3000

« on: December 12, 2004, 07:27:19 pm »

Dear Newbix ,

You How To for installing debian the Zaurus 3000 has been very helpful.
Below are some notes, I have made where I deviated from your instructions.
 Which may help other users.

I have managed to get to the stage where  Fbvnc launches successfully.
This gives me  Xterm open, but I do not think I have IceWM running, I do
not have the IcWM panel, as per your pretty screen shot:-
  http://www.eleves.ens.fr/home/leurent/zaurus.jpg

I am very poor with Window Manager generally, so this will be a good
learning exercise. I wonder if you could give me any tips on launching
IceWM.


Once again thank-you for the detailed HowTo.

Regards,
Brendan M. Sleight

http://www.barwap.com/blog/


****


I followed Gaëtan instructions with a few minor tweaks.

First once I was root, I did a :-
df -h
To confirm which partition is the biggest spare...
In my case this was hda3 not hdc3. I believe looking at the rc.rofilesys,
this hints at the fact that it could be hda hdb or hdc:-
mount -t $LINUXFMT -o noatime /dev/${IDE1}3 /hdd
Hence refernces to hdc3 were replaced with hda3

When doing the command 'mount -o remount,rw /dev/root' I get an error that
/dev/root is not listed in fstab. I therefore copy the line from mtab to
fstab. (I used an editor but here it is in one line)

cat /etc/mtab | grep /dev/root >> /etc/fstab

To copy the debian-tar ball onto the zaurus I used :-
wget http://pocketworkstation.org/files/zaurus-...n-big-v0.17.tgz
wget http://pocketworkstation.org/files/gnu-tar.gz

I then had to make gnu-tar execuatable.
chmod ugo+x ./gnu-tar

./gnu-tar xvzf zaurus-debian-big-*.tg
Should read ./gnu-tar xvzf zaurus-debian-big-*.tgz

I was unable to launch the fbvnc inside the tar ball - screen calibration
error. Had to use the one suggested
http://www.tcp-ip.or.jp/~naorou/linuzau/fb...20041121.tar.gz


Un-able to figure out how to get the IceWM panel. I got a feeling it
something stupid I am missing.

IceWM: you should create $HOME/.xinitrc according the howto :-)

11

C1000/3x00 General discussions / Full Debian On The Sl-c3000

« on: December 11, 2004, 11:16:51 am »

Well, the original environement (QTopia) is still present if you need it, but it isn't run at all when you use the debian system (well, the sharp kernel is still used). The debian comes with it's own X server, and you can run any windows manager you like.

If you want to get back to QTopia, you'll have to reboot the zaurus. There is maybe a better way, but I don't need it so I haven't searched in that direction.

So the drawback is that when using debian you don't have acces to QTopia and QTopia apps (but to me it is more an advantage than a drawback).

As foar as kanji are concerned, the debian programms are in english, but you can put some of them in other language if you like. However ther seem to be a bug somewere, and unicode chars are not displayed properly, so you should stay with latin-1.

It works perfectly! Thank you very much Newbix :-)

12

Zaurus - pdaXrom / Does your pdaXrom rc3/rc5 freeze in X11?

« on: October 15, 2004, 04:52:52 pm »

Hi,

I had old issues in rc3, things like battery emptying very quickly and other little bugs but most of them are now resolved in pdaXrom rc5. But there is still a big one that should prevent most of you from using pdaXrom everyday if you experience it. It's a X11 freeze when the device is powered on.

Symptoms:

_ The keyboard is frozen in X11. No more way to get out with Control-Alt-Backspace. No way to open the menu of send keytrokes to applications.
_ No more click even sent to applications. They are not frozen because the hour on the tray will continue to evolve but my click doesn't do anything.
_ Even if the click doesn't work, the mouse is still moving and follow the on screen click.
_ I can still poweron and poweroff the device but nothing else.
_ Before having this issue, I experience strange switch off: I switch on the device and it swicth off 1 second after and I have to power if on again.
_ Before having this issue, clicking on the screen keyboard is very slow and I have to let my stylus on the screen a bit longer to have the message sent to the application.

The only solution found at present: take out the battery for cold reboot.

My device is a SL-C760.

Thank for any report. If I'm not alone, reporting your experience here should help to find what is going on and where to search. Hoping that my device is not having hardware failure.

I'm having exactly the same problem with RC5 as Amrein reports. After resuming my 860 doesn't respond to the keys pressed down. The cursor moves as it should. It seems me there is a relation between networking and this problem.

Milan