Reply
Thread Tools
edp17's Avatar
Posts: 599 | Thanked: 711 times | Joined on Jul 2019 @ UK
#861
Originally Posted by mautz View Post
Lots of stuff missing in droid-config-hammerhead.spec.

Please compare with my spec file and missing parts to your file:
https://github.com/mautz-kernel/droi...ammerhead.spec

modem, ofono, community adaptation, dcd path
Thank you.
What are the dcd and community_adaptation for?
 
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#862
dcd only shows the path to droid-config device folder. Community adaptation is needed to get the store working for example.
 

The Following User Says Thank You to mautz For This Useful Post:
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#863
Storeman works for me, maybe you need to do a 'pkcon refresh' in the terminal?
 

The Following User Says Thank You to mautz For This Useful Post:
edp17's Avatar
Posts: 599 | Thanked: 711 times | Joined on Jul 2019 @ UK
#864
Oh, I wanted to say, don't bother trying the version that is in the 'initial screen loop'. I will update the configs accordingly and generate a new version (hopefully better that the last one ). I also use wip0.6 version as that was the most "stable" so far. Thanks.
 

The Following User Says Thank You to edp17 For This Useful Post:
edp17's Avatar
Posts: 599 | Thanked: 711 times | Joined on Jul 2019 @ UK
#865
Originally Posted by mautz View Post
dcd only shows the path to droid-config device folder. Community adaptation is needed to get the store working for example.
I am just thinking out loud. I didn't have the community_adaptation but the Jolla store works fine. So it seems this is not required for the store anymore. It would be useful what else requires this. Is it getting some extra driver/programs/whatever else?

My other question is about the pixel ration. If I set 1.75, will it work? The hadk-faq says 1.75 is a valid icon_res value, so in theory it should work. I'll try.
 
edp17's Avatar
Posts: 599 | Thanked: 711 times | Joined on Jul 2019 @ UK
#866
Originally Posted by mautz View Post
Relating Bluetooth: You need to change droid-config-hammerhead-bluez5 to droid-config-hammerhead-bluez4 in jolla-hw-adaptation-hammerhead.yaml.

The kernel does not support bluez5. Just stick with 4 or try to backport bluez5 to the kernel:

https://github.com/mer-hybris/hadk-f...hci-smd-driver
Yeah, I have read this in the hadk-faq yesterday but because I didn't find a few flags in neither John's nor the original CM kernels, I didn't put the missing flags into mine. I will do this too.
Thank you!
 

The Following User Says Thank You to edp17 For This Useful Post:
edp17's Avatar
Posts: 599 | Thanked: 711 times | Joined on Jul 2019 @ UK
#867
Originally Posted by mautz View Post
Lots of stuff missing in droid-config-hammerhead.spec.

Please compare with my spec file and missing parts to your file:
https://github.com/mautz-kernel/droi...ammerhead.spec

modem, ofono, community adaptation, dcd path
Well, I have double checked my 'droid-config-hammerhead.spec' and only the dcd_path was missing from it. I added.

I applied all three patches for the bluetooth and added the necessary flags into defconfig and changed the bluez5 to 'droid-config-hammerhead-bluez4' in 'jolla-hw-adaptation-hammerhead.yaml'.

I have found an error in the bluetooth patch in tcrypt.c
The lines the patch recommends to add with +
Code:
	case 151:
		ret += tcrypt_test("rfc4106(gcm(aes))");
		break;

+		break;
+
+	case 153:
+		ret += tcrypt_test("cmac(aes)");
+		break;
+
+	case 154:
+		ret += tcrypt_test("cmac(des3_ede)");

	case 200:
		test_cipher_speed("ecb(aes)", ENCRYPT, sec, NULL, 0,
If I add the code this way, the first 'break;' is an extra and at case 154 the 'break;' is missing,

So, I think the correct code should be
Code:
	case 151:
		ret += tcrypt_test("rfc4106(gcm(aes))");
		break;

+
+	case 153:
+		ret += tcrypt_test("cmac(aes)");
+		break;
+
+	case 154:
+		ret += tcrypt_test("cmac(des3_ede)");
+		break;

	case 200:
		test_cipher_speed("ecb(aes)", ENCRYPT, sec, NULL, 0,
The highlighted code (break should go where I indicated.
Now, I am ready to compile and rebuild. Will let you know the outcome.

Last edited by edp17; 2019-11-20 at 10:19.
 
edp17's Avatar
Posts: 599 | Thanked: 711 times | Joined on Jul 2019 @ UK
#868
Originally Posted by mautz View Post
Storeman works for me, maybe you need to do a 'pkcon refresh' in the terminal?
Yes, you were right! It needed a 'pkcon update' at command line. Then it started working.

Plus I have tested the hw acceleration with Quake 2. (Not the native version because that needs to be recompiled for the new libhybris-libGLESv2, but the android app from Aptiod.) It plays very smoothly. I am not sure whether it has sound though.
 
edp17's Avatar
Posts: 599 | Thanked: 711 times | Joined on Jul 2019 @ UK
#869
Another question regarding the bluetooth. It seems we are compiling the bluetooth as module in kernel (CONFIG_BT=m) just like the wifi.
But I didn't find any place where the driver is loaded.
For wifi, we added 'bcmdhd' into 'droid-hal-hammerhead.conf' in '/usr/lib/modules-load.d/'

Isn't a similar solution necessary for the bluetooth? Or that just works?
 
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#870
Sorry, i was looking at the wrong spec file...my fault.

Which patches did you add? For bluez4 you shouldn't need patches or build BT as module or you are going the backport route?
 

The Following User Says Thank You to mautz For This Useful Post:
Reply

Tags
hammerhead, nexus5, sailfishos, sfdroid


 
Forum Jump


All times are GMT. The time now is 18:51.