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 - mibry

Pages: 1 ... 3 4 [5]
61
Gemini PDA - Linux / Problems latest firmware
« on: May 31, 2019, 10:20:49 am »
Quote from: cam1965
Quote from: mithrandir
Quote from: cam1965
As I said , I think Planet has changed , because every another kernel that I flashed didn't boot on gemini . The last was compiled perfectly, but for some reasons it didn't boot. Only the kernel provided inside the debian image can boot gemini. Also I've tested the kernel from the repository ( not the modular ) and it installs perfectly . No need to dd, because it automatically detects the correct partition. Reinstalled again the modular kernel . The partition is correct. ( boot2 ) . I've checked this. But I've also did a test with the manual dd at the correct partition and only the kernel provided from planet boots gemini.

follow the results of /cat/cmdline attached.
Please, contact planet and tell me how are the steps to compile his kernel. Because I've compiled the kernel modules from the source kernel ( they are also with + sign ) , but I can' t load any module as I said before .Also when I do lsmod ( with my modules compiled ) an error appears saying libkmod error , etc ... and could not open /proc/modules.
Thank you again

From your cmdline you appear to have an unmodified bootloader, so there is no way the kernel package could detect the right boot partition. Otherwise there would be a bootpartition entry in the cmdline. Unless the method of partition detection has changed (@Adam: Has it?), manual flashing with dd is necessary.

Thank you .
As I said I am using the default installation from Planet. ( debian and android oreo images ). Fresh install ( flashed ).
I think something has changed. I also did manual  flashing with dd ( kernel ) and only the kernel from debian image boots gemini.
Thank you again.

I also reflashed my gemini with the new debian image from planet support website and had the same kernel as cam1965. I did a dd of the linux-boot.img kernel image in /usr/share/kernel and was able to boot into debian. I also notice before I flashed the image I had the same kernel version as cam1965. The kernel version has now changed to 3.18.41 without the + at the end.

62
Gemini PDA - Android / Multi boot to Android 8.1 only
« on: May 09, 2019, 09:21:34 am »
Quote from: FredL
I currently have a multi-boot setup for Android and Sailfish.

I'd like to go to a single boot Android 8.1 only firmware, but I'm not sure whether I can go ahead and follow the instructions here http://support.planetcom.co.uk/index.php/G...droid_8_Upgrade - or wait for the multi-boot partition tool to support 8.1 and choose a single partition android - http://support.planetcom.co.uk/partitionTool.html

Any recommendations?

Download the new firmware from http://support.planetcom.co.uk/download/An...A6_06052019.zip and apply it with the flash tool. The android only scatter file is included with the zip. It will mean you will loss all you programs so best to make sure you back before flashing. You might be lucky and preserve you data if you unselect the userdata partition.

63
Gemini PDA - Linux / Final call for TP3
« on: January 31, 2019, 10:07:11 am »
Ok thanks

Quote from: Kiriririn
Quote from: mibry
I hope that TP3 will fix the problem I am encountering. I had to reflash my gemini with android and debian, when I did the dist-upgrade and install kernel I had not taskbasr come up after rebooting the gemini, I only had the background and was unable to access any menus.

Any ideas?

Thanks in advance.

Quote from: mithrandir
@TheKit:
Thanks, good to know.

Then (obviously) I would also like the Wayland solution, but as you told, this would be too much for TP3. The kernel part is a bit unfortunate, really hoped for an update. 3.18 is pretty much EOL... Also hoped for a newer kernel fixing the sd card performance after sleep issue, present in both, Android and Debian.

Regarding GPS apps, it should be possible to run navit on the gemini, still using this on my old n900, but there are quite some more, i.e. kismet supports GPS, via gpsd if I remember correctly.

It's a dependency issue in the new pulseaudio update, I had assumed it was 'just me' with the amount I've changed things but I guess not

You can fix it by installing ubuntu-application-api3-touch via apt

64
Gemini PDA - Linux / Final call for TP3
« on: January 31, 2019, 04:43:12 am »
I hope that TP3 will fix the problem I am encountering. I had to reflash my gemini with android and debian, when I did the dist-upgrade and install kernel I had not taskbasr come up after rebooting the gemini, I only had the background and was unable to access any menus.

Any ideas?

Thanks in advance.

Quote from: mithrandir
@TheKit:
Thanks, good to know.

Then (obviously) I would also like the Wayland solution, but as you told, this would be too much for TP3. The kernel part is a bit unfortunate, really hoped for an update. 3.18 is pretty much EOL... Also hoped for a newer kernel fixing the sd card performance after sleep issue, present in both, Android and Debian.

Regarding GPS apps, it should be possible to run navit on the gemini, still using this on my old n900, but there are quite some more, i.e. kismet supports GPS, via gpsd if I remember correctly.

65
Gemini PDA - Sailfish OS / Getting to SFOS 3.x on Gemini PDA
« on: November 02, 2018, 05:25:14 am »
Quote from: Meganerd
Hello fellow Linux bros,

I saw this thread today Sailfish OS 3.0.0 released to early adopters today
(https://www.oesf.org/forum/index.php?showtopic=35592&st=0&#entry290497)

I have to keep type this up quick since it is literally 2:00 AM for me and I am recovering from recent sickness with work tomorrow- so I apologize for the formatting.
Also thanks to Depscribe and Yoram for the thread, it also had some useful information and links for me to get this done.

I was on SFOS 2.1.3.7 initially, but flashed the SFOS 2.1.4.14 build since I wanted to triple boot.
So these are the steps I performed from a fresh install on that build.

Enable early access to SFOS releases at https://account.jolla.com/
(Requires Jolla account; Not sure if required but I enabled it)


I enabled SSH under developer options.
I used SSH for this next task.
Code: [Select]
ssh-keygen -f "/home/meganerd/.ssh/known_hosts" -R 192.168.2.15
ssh nemo@192.168.2.15


Code: [Select]
devel-su
vi /usr/share/ssu/features.d/adaptation-community-common.ini
(Press 'i' to enter insert mode, modify text, ESC, then enter :wq)


change this line:
adaptation-community-common = http://repo.merproject.org/obs/nemo:/devel...latest_%(arch)/

to:
adaptation-community-common = http://repo.merproject.org/obs/nemo:/testi...hos_%(release)/


Quote
If do not change from devel: (state: unstable) to testing: (state: testing) you get trouble with your sensorfw (sensors not working, only a software problem). Before next step you can verify that the change is done with:
Code: [Select]
ssu lr

You must go to 2.2.0.29 before going to 3.x
So start the update to 2.2.0.29:

Code: [Select]
ssu re 2.2.0.29
pkcon refresh
version --dup
sync
reboot

(if you get "Fatal error: File ... not found" on you made a typo on the file)



Code: [Select]
megaman@machine:~$ ssh nemo@192.168.2.15
nemo@192.168.2.15's password:
Last login: Fri Nov  2 00:59:21 2018 from 192.168.2.4
NOTICE: Env value ignored HYBRIS_LD_LIBRARY_PATH=/usr/libexec/droid-hybris/system/lib:/vendor/lib:/system/lib
,---
| SailfishOS 2.1.4.14 (Lapuanjoki)
'---
[nemo@Sailfish ~]$ devel-su
Password:
[root@Sailfish nemo]# vi /usr/share/ssu/features.d/adaptation-community-common.ini
[root@Sailfish nemo]# ssu lr
[D] unknown:0 - "No carrier"
Enabled repositories (global):
 - adaptation-community        ... http://repo.merproject.org/obs/nemo:/testing:/hw:/planet:/geminipda/sailfishos_2.2.0.29/
 - adaptation-community-common ... http://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_2.2.0.29/
 - apps                        ... https://releases.jolla.com/jolla-apps/2.2.0.29/armv7hl/
 - hotfixes                    ... https://releases.jolla.com/releases/2.2.0.29/hotfixes/armv7hl/
 - jolla                       ... https://releases.jolla.com/releases/2.2.0.29/jolla/armv7hl/

Enabled repositories (user):
 - store ... https://store-repository.jolla.com/geminipda/armv7hl/?version=2.2.0.29

Disabled repositories (global, might be overridden by user config):

Disabled repositories (user):
 - home ... https://download.jollamobile.com/home:/honeybadger/latest_armv7hl/
[root@Sailfish nemo]# ssu re 2.2.0.29
Changing release from 2.2.0.29 to 2.2.0.29
Your device is now in release mode!
[D] unknown:0 - "No carrier"
[root@Sailfish nemo]# pkcon refresh
Refreshing cache                                                                                                                                                
Starting                                                                                                                                                        
Refreshing software list                                                                                                                                      
Finished                                                                                                                                                      
[root@Sailfish nemo]# version --dup
REFRESHING CACHE AND DOWNLOADING PACKAGES
Finished transaction (status=1, runtime=321682ms)
UPGRADING SYSTEM
Finished transaction (status=1, runtime=373457ms)
FINISHING


After reboot, and attempting to boot into SFOS the device looks like it is in a powered off state.
But I can hear the USB sound from SFOS when I plug it in... so I SSH in to the device. This works.

(Eventually the screen started working so you can SSH or wait)

Code: [Select]
megaman@machine:~$ ssh nemo@192.168.2.15
nemo@192.168.2.15's password:
Last login: Fri Nov  2 01:37:50 2018
,---
| Sailfish OS 2.2.0.29 (Mouhijoki)
'---
[nemo@Sailfish ~]$ devel-su
Password:
[root@Sailfish nemo]#


So now I need to get to 3.0.0.0 or 3.0.0? (I am guessing the build is this)

UPDATE - I got stuck:
It is way past time for me to get to bed, unfortunately I will have to pickup on this tomorrow.
If anyone who was successful could help me figure out what I am doing wrong that would be awesome


I read that Yoram said he had to switch his adaptation layer to salfish_latest

so I modified the file back to its original state
(/usr/share/ssu/features.d/adaptation-community-common.ini)

Then attempted multiple releases but got an error from here
Code: [Select]
ssu re 3.0.0.0
ssu re 3.0.0

Both of them throwing me this error

Code: [Select]
Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/testing:/hw:/planet:/geminipda/sailfishos_3.0.0.0/'
I see that the output is still trying the first modified syntax even after updating the adaptation-community-common.ini file?

I took a brief look at the ssu command but no luck.
I have run out of time to get this going for tonight- sorry!

Code: [Select]
[root@Sailfish nemo]# ssu --help

Usage: ssu [-command-options] [arguments]

Repository management:
    updaterepos, ur            update repository files
    repos, lr                  list configured repositories
               [-m]            format output suitable for kickstart
               [device]        use repos for 'device'
               [flags]         additional flags
               rnd=     set rnd or release mode (default: take from host)
    addrepo, ar          add this repository
               [url]           specify URL, if not configured
    removerepo, rr       remove this repository from configuration
    enablerepo, er       enable this repository
    disablerepo, dr     disable this repository

Configuration management:
    flavour, fl              display flavour used (RnD only)
      [newflavour]           set new flavour
    release, re              display release used
      [-r]                   use RnD release
      [newrelease]           set new (RnD)release
    set                      display global variables
      [-r]                   operate on repository only variables
                   display value of
           set value of to

Device management:
    status, s         print registration status and device information
    register, r       register this device
          [-h]        configure user for OBS home
    update, up        update repository credentials
          [-f]        force update
    model, mo         print name of device model (like N9)

[root@Sailfish nemo]# ssu ur
[D] unknown:0 - "No carrier"
[root@Sailfish nemo]# pkcon refresh
Refreshing cache                                                                                                                                                                        
Starting                                                                                                                                                                                
Refreshing software list                                                                                                                                                                
Finished                                                                                                                                                                                
Fatal error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/testing:/hw:/planet:/geminipda/sailfishos_3.0.0/'

[root@Sailfish nemo]#



Sources:
https://together.jolla.com/question/186471/...anet-computers/
https://jolla.zendesk.com/hc/en-us/articles/201836347#2
https://www.oesf.org/forum/index.php?showto...mp;#entry290497

So it looks like the reason why the upgrade didn't work is there is no listing at http://repo.merproject.org/obs/nemo:/testi...net:/geminipda/ for 3.0.0.0

Index of /obs/nemo:/testing:/hw:/planet:/geminipda
[ICO]   Name   Last modified   Size   Description
[DIR]   Parent Directory       -    
[DIR]   sailfishos_2.1.4.14/   26-Jul-2018 17:46    -    
[DIR]   sailfishos_2.2.0.29/   26-Jul-2018 17:46    -    
Apache/2.2.22 (Debian) Server at repo.merproject.org Port 80

66
Gemini PDA - Hardware / MediaTek System On Chip - mtklogger malware
« on: June 07, 2018, 04:47:10 am »
Quote from: Murple2
Quote from: TallTim
Ran across a blog post on Medium that referenced MediaTek's SoC and what he describes as a "keylogger" mtklogger as part of the package.

Reference - https://medium.com/@chpapa/review-after-two...ne-7dd8b550609a

If this is accurate, how exactly do we trust this in its default state as Gemini PDA's are shipped, and how do you remove/fix this?

If this is not the proper forum, I apologize, thought hardware may be the best area.

Thanks in advance for any guidance on this.

There was discussion around this a month or so back, I came to the conclusion I wasn't too worried - no more than I am about the inclusion of hardware backdoors on every electronic device I own.  If you were super paranoid you could sniff outbound traffic from the gemini (the ethernet adapter may be the easiest way to do this) but even this isn't fool proof.
I took a pragmatic approach and downloaded "Engineer Mode MTK" from the play store which allowed me to disable a whole load of logs (which were already switched off anyway). Of course, maybe this app is malicious and I have made my device less secure.

I think I'll stick to pen and paper from now on...

If you are really worried about the mtklogger process then best to install the rooted version of the fireware and use a firewall like AFWALL+, it is available in the play store.

67
Gemini PDA - Linux / linux on Gemini
« on: June 02, 2018, 03:30:57 am »
Quote from: depscribe
Quote from: mibry
I have been using Debian for a few weeks now and like what is available. I was wondering if it is possible for KVM to be included with the next kernel?
The next kernel is likely to be 4.4 -- at least that's what the Android update would/will be, and we're tragically tied to the Android kernel. Whether it will be built in the default kernel, I do not know. But there are people burning their own kernels/modules/etc. from the source, which is available on, I believe, Davide's github site: https://github.com/dguidipc

If I were to do this, I'd subscribe to the #gemini-pda freenode chat. People who have jumped through those hoops tend to be there.

Cool thanks.

68
Gemini PDA - Linux / linux on Gemini
« on: June 01, 2018, 10:30:53 am »
I have been using Debian for a few weeks now and like what is available. I was wondering if it is possible for KVM to be included with the next kernel?

69
Gemini PDA - Linux / How to flash Debian Linux on Gemini
« on: May 18, 2018, 08:16:21 am »
Quote from: Guest
I wrote a guide for this, which is a bit more extensive than the original guide by PC.
Link: https://geminiplanet.com/2018/04/07/how-to-...-on-the-gemini/

Any word when the Mac version of the flashing tool will be released?

Pages: 1 ... 3 4 [5]