Reply
Thread Tools
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#881
I have another question. (well two)
If anybody is aware of any of them please don't hold it back.

1. How can I preinstall packages?
(I have seen one version, might be 2.0.4.13 came with messwerk installed by default)

2. How can I run a custom script during the initial phone setup but only once and before the lipstick starts?

Thank you!
 
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#882
You could try to add packages to one of the yaml files in patterns.

What do you want to add? And which script do you want to run?

Are you building in a Virtual machine?
 
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#883
Originally Posted by mautz View Post
You could try to add packages to one of the yaml files in patterns.

What do you want to add? And which script do you want to run?

Are you building in a Virtual machine?
Thank you.
I would like to pre-install some packages that I always install like sudo, cifs-utils, filetug, filetug-root, storeman, ...etc.

The script I would like to run is an extract from kimmoli's diyicon script. My idea was to pre-distribute the shrank images into '/usr/share/themes/sailfish-default/meegotouch/z1.82/' within sparse, then with a script remove the '/etc/dconf/db/vendor.d/locks/silica-configs.txt' file and add the extra key '/desktop/sailfish/silica/theme_pixel_ratio to 1.82' into '/hone/nemo/.config/dconf/user' and run the 'dconf update'
As after this lipstick must be restarted, I thought would do this before the lipstick started first.
This way I can have pixel ratio 1.82 right out of the box.
Plus I would like to pre-populate the extra browser search engines. (And probably I will build an image for myself with some other stuff in there. Like keyboard tweaks: longer space bar, quicker popup keys, shorter keyboard. Oh and reducing the remorse timer to 2secs.

I build in ubuntu directly installed on my pc.
 
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#884
Good news:
- wifi tethering also works (with this method)
- the games have correct sound in AD
- mp3 playback works

Bad news:
- audio forwarding to 3.5 jack doesn't work
 

The Following User Says Thank You to edp17 For This Useful Post:
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#885
Take a look here for the headphones problem:

https://github.com/mer-hybris/hadk-faq#id36
 

The Following User Says Thank You to mautz For This Useful Post:
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#886
Originally Posted by mautz View Post
Take a look here for the headphones problem:

https://github.com/mer-hybris/hadk-faq#id36
Thanks. I have seen this file 'accessories.ini' in your repo. I thought would grab it then I didn't do. But looks like it is inevitable.
 
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#887
Originally Posted by mautz View Post
Take a look here for the headphones problem:

https://github.com/mer-hybris/hadk-faq#id36
The hadk-faq says: "replace jack-match and jack-device with values from evdev_trace"

In your repo, there is no jack-device in the accessories.ini file. You have only jack-match.
Do you remember why? Thanks.

Edit:
the evdev_trace on my device (wip0.6) shows:
Code:
----====( /dev/input/event0 )====----
Name: "qpnp_pon"
ID: bus 0x0, vendor, 0x0, product 0x0, version 0x0
Type 0x00 (EV_SYN)
Type 0x01 (EV_KEY)
	 KEY_POWER

----====( /dev/input/event1 )====----
Name: "touch_dev"
ID: bus 0x0, vendor, 0x0, product 0x0, version 0x0
Type 0x00 (EV_SYN)
Type 0x03 (EV_ABS)
	 ABS_MT_SLOT=0 [0,9] ABS_MT_TOUCH_MAJOR=0 [0,15]
	 ABS_MT_POSITION_X=0 [0,1079] ABS_MT_POSITION_Y=0 [0,1919]
	 ABS_MT_TRACKING_ID=0 [0,65535] ABS_MT_PRESSURE=0 [0,255]

----====( /dev/input/event2 )====----
Name: "gpio-keys"
ID: bus 0x19, vendor, 0x1, product 0x1, version 0x100
Type 0x00 (EV_SYN)
Type 0x01 (EV_KEY)
	 KEY_VOLUMEDOWN KEY_VOLUMEUP
Type 0x05 (EV_SW)
	 SW_LID

----====( /dev/input/event3 )====----
Name: "hs_detect"
ID: bus 0x0, vendor, 0x1, product 0x1, version 0x1
Type 0x00 (EV_SYN)
Type 0x01 (EV_KEY)
	 KEY_VOLUMEDOWN KEY_VOLUMEUP KEY_MEDIA
Type 0x05 (EV_SW)
	 SW_HEADPHONE_INSERT SW_MICROPHONE_INSERT

----====( /dev/input/event4 )====----
Name: "msm8974-taiko-mtp-snd-card Button Jack"
ID: bus 0x0, vendor, 0x0, product 0x0, version 0x0
Type 0x00 (EV_SYN)
Type 0x01 (EV_KEY)
	 BTN_MISC BTN_1 BTN_2 BTN_3 BTN_4 BTN_5 BTN_6 BTN_7

----====( /dev/input/event5 )====----
Name: "msm8974-taiko-mtp-snd-card Headset Jack"
ID: bus 0x0, vendor, 0x0, product 0x0, version 0x0
Type 0x00 (EV_SYN)
Type 0x05 (EV_SW)
	 SW_HEADPHONE_INSERT SW_MICROPHONE_INSERT SW_LINEOUT_INSERT
	 SW_HPHL_OVERCURRENT SW_HPHR_OVERCURRENT SW_UNSUPPORT_INSERT
In your repo you set 'jack-match = hs_detect' and the hadk-faq suggest: 'jack-match = msm8974-taiko-mtp-snd-card Button Jack'

The hadk-faq also sets 'jack-device = /dev/input/event4'

In my device I have all three ('hs_detect', 'msm8974-taiko-mtp-snd-card Button Jack' and 'msm8974-taiko-mtp-snd-card Headset Jack'.
So which one I should use in the accessories.ini?

I bet on 'jack-device = /dev/input/event5' and 'jack-match = msm8974-taiko-mtp-snd-card Headset Jack' but I am not sure why you and the hadk-faq has different jack-mach.

I have tested all three and your one is the winner, so the content of accessories.ini:
eci-probe-delay = 2500
disable-incompatible-quirk = true
jack-match = hs_detect
jack-device = /dev/input/event3

Now the jack also works.

Last edited by edp17; 2019-11-20 at 23:40.
 
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#888
Well, I have created a new image. Included the bluez4, bt-sleep-motnitor, ril_substrciption, wifi module, sensor config, camres config, and everything else I knew so far.
It boots and starts but goes back to the language screen when I accept the end user licence agreement.
 
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#889
Originally Posted by edp17 View Post
Well, I have created a new image. Included the bluez4, bt-sleep-motnitor, ril_substrciption, wifi module, sensor config, camres config, and everything else I knew so far.
It boots and starts but goes back to the language screen when I accept the end user licence agreement.
The main problem that I don't know whether the kernel, the hal, or sailfish itself is causing this. So I am not sure where to start looking.
 
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#890
The latest build (wip0.12) has basically everything except the accessories.ini file. But it is affected with the 'initial setting screen loop' issue. I very much appreciate if somebody can take a look and point me to the right direction where to find the root cause. Download from here.
 
Reply

Tags
hammerhead, nexus5, sailfishos, sfdroid


 
Forum Jump


All times are GMT. The time now is 15:37.