yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] marauderz:
I wonder what's going to happen when you have both ur PS3 and ur Diamond on at the same time? The box doesn't mention multiple connection sources :P

well just let us know, I haven't gotten home to try it out with my PC yet so I don't know about what happens with multiple sources.
[Touch Diamond, MDA Compact IV General] swampy:
WOOT it works just like you said!

About ps3, i'm not sure - i am using it in pc mode (switch at the back of dinovo) so it wouldn't work anyways if my ps3 was on. Later on i will try my laptop/dinovo and diamond/dinovo.

On the diamond, when i soft reset, i have to delete and remake another bt connection before dinovo would work again - toggling the bt would not make it connect. Bummer but hey this gadget is really cool!

Thanks again
[Touch Diamond, MDA Compact IV General] vince31415:
Hi

I have also a DiNovo paired sucessfully with my Diamond, but the "bug" with the hardware keys is really a downer. I've searched MSDN and the Net but I didnt find anything to solve this Problem. I hope somone else can do this for me

vince
[Touch Diamond, MDA Compact IV General] jameslovell:
WOW!

just connected my Diamond to my Logitech MX5000 keyboard :D
[Touch Diamond, MDA Compact IV General] Neo3D:
I'm trying to do this w/my dinovo edge keyboard and it's not working? Can you please provide some more details? I'm assuming you keyed in a 4 digit code and pressed ENTER on the keyboard, then typed in the same 4 digits on the phone and pressed NEXT?

Good find, hope I can get it working too!

EDIT: I found specific instructions on how to do this. You have to enter the code in this order=>

It seems that the pairing procedure is as follows for devices that do not generate their own random passcode for use with the Dinovo, although I gathered this from experimentation:

Press Connect button on underside of keyboard

Search for Bluetooth devices with computer/PDA/phone

Select Dinovo from devices found

Enter a passcode on computer/PDA/phone if prompted (you choose the code), submit

Enter the same code on the Dinovo keyboard

It may be necessary to press ENTER on the Dinovo keyboard

Hopefully, the pairing will be successful.
[Touch Diamond, MDA Compact IV General] qunybble:
smartphone - windows mobile 6

i would like to use the mini with windows mobile 6 - more specifically the tmobile shadow2. I can connect the device and my mobile recognized the keyboard as a form of input, but the keys on the mini are not working. are there any wm6 updates that i should find? I am on .net compact 3.5
[Touch Diamond, MDA Compact IV General] martinl1:
National characters

Does somebody try to use Logitech Dinovo Mini for typing the national characeters? (like ľščťžýáíé etc...)
[Xperia Z5 Compact Android Development] beflythis:
Does its existence for devices like the Z3C make it more or less likely for us to see on suzuran? Would love to see a LineageOS 17 ROM for this device. Makes me wish I was a dev. Thanks to all those who continue to grind hours into porting and developing ROMs for the platform.
[Xperia Z5 Compact Android Development] Berni-0815:
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:

But.... As my 16.0 try this rom is not booting... :(

Don't know why
[Xperia Z5 Compact Android Development] Joel16:
Are you making any kernel changes? If not, that's probably why. You can't use the LineageOS 15.1 kernel on the PIE. Correct me if I'm wrong but Pie requires linux kernel 4.4x and greater while, Android 10 requires 4.9 and greater.
[Xperia Z5 Compact Android Development] Berni-0815:
Apart from fixing compile-errors, no.

But I don't think that the kernel version is important. This project uses kernel 3.x too, if I'm not wrong...

Sure, there have to be changes, but I can't do so...
[Xperia Z5 Compact Android Development] Berni-0815:
I've tried another kernel (this one) and I changed/added some files to avoid compile errors. But the result is the same:

The splash screen apears, then a blank screen....

The splash screen apears, then a blank screen....

The splash screen apears, then a blank screen....

The splash screen apears, then a blank screen....

...and so on until end of battery... :(
[Xperia Z5 Compact Android Development] Joel16:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
[Xperia Z5 Compact Android Development] Berni-0815:
Where should these logs be?

I have no access to the device at this early stage... :confused:

An when I reflash a working rom /system will be overwritten.

I've tried to build pie with this kernel. Nearly the same result.
[Xperia Z5 Compact Android Development] Joel16:
Weird, I ran into some issues building pie yesterday, but didn't have any time to fix it. I'll try again tonight and see how it goes. If I still have issues, I'll have to wait till the weekend.
[Xperia Z5 Compact Android Development] Berni-0815:
I'm sorry; I should have tell you about that... :angel:

I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):

.bashrc:

export CPU_SSE42=false

to avoid crashes in hiddenapi and profman

device/sony/kitakami-common/SonyOtgSwitch/Android.mk:

LOCAL_SDK_VERSION := current

kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):

RMNET_NETLINK_DEL_VND_TC_FLOW,

/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME

bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:

#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)

hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:

ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));

hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:

void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])

and line 67:

static struct audio_extn_module aextnmod [B]__unused[/B] = {

hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:

ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",

hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:

ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",

and line 320:

ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",

device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:

LOCAL_PRIVATE_PLATFORM_APIS := true

Changes in bold ;)
[Xperia Z5 Compact Android Development] Joel16:
Yup I made those changes except for

export CPU_SSE42=false

I did not get any issues building but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.
[Xperia Z5 Compact Android Development] Berni-0815:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.

Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
[Xperia Z5 Compact Android Development] Joel16:
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.
[Xperia Z5 Compact Android Development] BORNIOS:
You can do It!!!
[Xperia Z5 Compact Android Development] I_did_it_just_tmrrow:
What is about adbd, see here:

https://xdaforums.com/showpost.php?p=67386761&postcount=13

The z5c is based on Qualcomm Snapdragon 810 MSM8994, like:

SONY XPERIA Z5 PREMIUM | MOTOROLA DROID TURBO | MICROSOFT LUMIA 950 XL | NUBIA Z9 MAX

Is there any source of a pie build availible where we can get some hints how get a pie build to run?

Here are some kernel sources from the Nubia Z9 Max (nx510j):

https://github.com/nubia-development/android_kernel_nubia_msm8994
[Xperia Z5 Compact Android Development] Berni-0815:
I'll have a look at this. :good:
[Xperia Z5 Compact Android Development] I_did_it_just_tmrrow:
For my self I try slowly become deeper into that topic: building a rom.

So I did a little bit of research in github and gitlab and I found some interesting repos from this user:

https://github.com/Cyborg2017?tab=repositories

I ask him if he could help us a little bit and the first result is this.

@Joel16 & @Berni-0815 Perhaps this is useful:

https://github.com/Cyborg2017/android_kernel_sony_msm8994/tree/sony_msm8994_p-upstream

I hope it help us to come closer to an LineageOS 17 for suzuran.
[Xperia Z5 Compact Android Development] Berni-0815:
Error 404

A little time later:

I think, you're talking about this kernel?

---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------

Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.

How can I include adbd into my build? I'll give it a try...
[Xperia Z5 Compact Android Development] I_did_it_just_tmrrow:
Yep, just try his source. He told that it could be useful to test this kernel with building twrp first.

To the logging problem. I understand that right that you have nothing in:

/proc/last_kmsg

Nor in:

/sys/fs/pstore/console-ramoops

and you check this with the twrp terminal?

You should take a look at this:

https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg
[Xperia Z5 Compact Android Development] Berni-0815:
I'm actually building a rom with that kernel. I'll see later if it's working.

Right

Ah! Nice. I'll try it later. Thank you very much! :good:
[Xperia Z5 Compact Android Development] Joel16:
Let me know how it goes, I'm more than certain kernel is what's preventing us from getting Pie/Q to boot up.
[Xperia Z5 Compact Android Development] Berni-0815:
Sure! :good:
[Xperia Z5 Compact Android Development] Joel16:
Well for Z5P I tried the Android 9 kernel with lineage-16. It got stuck in an infinite bootloop and no kernel logs were dumped. Let me know if you have any luck.
[Xperia Z5 Compact Android Development] Berni-0815:
I've successfully built a LineageOS 17.1 with that kernel.

But, the splash screen appears for some time (20 to 30 seconds), then the led turns red and the device reboots on and on.

I've been able to grab logs. The archive includes two files:

oops.txt; created with

find -iname *oops* > /sdcard/oops.txt

pmsg-ramoops-0

But unfortunately I can't "read" this file. (I can open it but I can't interpret the content)

Maybe someone is able to do so?

Maybe I've grabbed the wrong file?

Please let me know...
[Xperia Z5 Compact Android Development] Joel16:
How did you manage to grab the logs? That's what I'm currently struggling with. Also it seems your phone doesn't even boot into the boot animation which is not good. In my case I tried 9.0 (Pie) and I got into an infinite boot animation, no kernel panics. I managed to open your binary file and got the following from the logs: https://pastebin.com/WkpfAEKV

I want to be able to grab logs to and hopefully get pie booting on this device.
[Xperia Z5 Compact Android Development] Berni-0815:
Boot the phone. Wait a few minutes. Press the power button and hold'em *). Press volume up. Directly after the power off vibration press volume down and into TWRP open the terminal.

*) I don't release the power button during the whole process until TWRP is starting.

That's right.

Same here but I can't interpret what I'm reading... So I can't say why the bootloop occurs... :(
[Xperia Z5 Compact Android Development] I_did_it_just_tmrrow:
What is about the

fsverity_initFailed to load

?
[Xperia Z5 Compact Android Development] Berni-0815:
I actually don't know. But I'll take a look into the source code asap...

But I've been able to grab another oops-file (pmsg-ramoops-0) with an interesting information in it (see last two lines):

vold Failed to LOOP_GET_STATUS64 /dev/block/loop4: No such device or address
vold Failed to LOOP_GET_STATUS64 /dev/block/loop5: No such device or address
vold Failed to LOOP_GET_STATUS64 /dev/block/loop6: No such device or address
vold Failed to LOOP_GET_STATUS64 /dev/block/loop0: No such device or address
vold Failed to LOOP_GET_STATUS64 /dev/block/loop2: No such device or address
vold Failed to LOOP_GET_STATUS64 /dev/block/loop3: No such device or address
vold Failed to LOOP_GET_STATUS64 /dev/block/loop7: No such device or address
vold Failed to LOOP_GET_STATUS64 /dev/block/loop1: No such device or address
fsverity_init Failed to load /product/etc/security/fsverity/*.der
/system/bin/mini-keyctl Failed to open /proc/keys: No such file or directory
fsverity_init Failed to restrict .fs-verity keyring
apexd Failed to walk /product/apex : Can't open /product/apex for reading : No such file or directory
apexd Failed to activate packages from /data/apex/active : Failed to scan /data/apex/active : Can't open /data/apex/active for reading : No such file or directory
apexd Failed to rollback : Rollback requested, when there are no active sessions.
apexd Failed to activate packages from /product/apex : Failed to scan /product/apex : Can't open /product/apex for reading : No such file or directory
cutils Failed to mkdir(/data/system/users/0): No such file or directory
vold Failed to prepare /data/system/users/0: No such file or directory
vold Failed to prepare user 0 storage
/system/bin/recovery-persist Failed to unlink /data/misc/recovery/last_install: No such file or directory
FrameworkListener read() failed (Connection reset by peer)
/system/bin/tombstoned tombstoned.cpp:87] failed to open directory: /data/tombstones: No such file or directory
/system/bin/tombstoned received fatal signal 6
[Xperia Z5 Compact Android Development] Berni-0815:
comes from system/core/debuggerd/tombstoned/tombstoned.cpp; line 87:

PLOG(FATAL) << "failed to open directory: " << dir_path;

So, this is a FATAL error!!! :eek:

comes from system/core/debuggerd/tombstoned/tombstoned.cpp; lines 406 to 414:

int main(int, char* []) {
umask(0137);

// Don't try to connect to ourselves if we crash.
struct sigaction action = {};
action.sa_handler = [](int signal) {
LOG(ERROR) << "received fatal signal " << signal;
_exit(1);
};
...(shortened code)...

Wtf does this mean? :confused:
[Xperia Z5 Compact Android Development] I_did_it_just_tmrrow:
Can you check this + under folder:

/data/tombstones/

Source
[Xperia Z5 Compact Android Development] Berni-0815:
There is no /data/tombstones/ at all!

Maybe it's too early and this directory will be created later. There are these entries in my device tree's init.qcom.rc:

mkdir /data/tombstones 0755 system system
mkdir /data/tombstones/vendor 0755 system system

under

on post-fs-data

and this

symlink /data/tombstones /tombstones

under

on early-init
[Xperia Z5 Compact Android Development] I_did_it_just_tmrrow:
Could you try to disable SELinux with that:

setenforce 0

Source

I think this just works until a reboot but you can try one of this too.

Edit build.prop file in the system folder:

#ro.boot.selinux=disable

or

ro.buid.selinux=1

Or this crazy way.

Or in the kernel itself.
[Xperia Z5 Compact Android Development] Berni-0815:
Actually I got a lot of crashes like this one:

PerMgrSrv QCRIL registered crash_dump64 obtaining output fd from tombstoned, type: kDebuggerdTombstone
crash_dump64 performing dump of process 5381 (target tid = 5381)
DEBUG *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
DEBUG LineageOS Version: '17.1-20200205-UNOFFICIAL-suzuran'
DEBUG Build fingerprint: 'Sony/suzuran/suzuran:10.0.0/QQ1B.200105.004:user/dev-keys'
DEBUG Revision: '0'
DEBUG ABI: 'arm64'
DEBUG Timestamp: 1973-02-12 00:07:10+0000
DEBUG pid: 5381, tid: 5381, name: rild >>> /vendor/bin/hw/rild <<<
DEBUG uid: 0
DEBUG signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
DEBUG Abort message: 'stack corruption detected (-fstack-protector)'
DEBUG x0 0000000000000000 x1 0000000000001505 x2 0000000000000006 x3 0000007fd402b2a0
DEBUG x4 0000000000808080 x5 0000000000808080 x6 0000000000808080 x7 0000000000000030
DEBUG x8 00000000000000f0 x9 f926fcb2e82019de x10 0000000000000001 x11 0000000000000000
DEBUG x12 fffffff0ffffffdf x13 0000000000000000 x14 0000000000000000 x15 002471ed4ee71b2d
DEBUG x16 000000783f7c18c0 x17 000000783f79f230 x18 0000007840ca6000 x19 0000000000001505
DEBUG x20 0000000000001505 x21 00000000ffffffff x22 000000783e80b530 x23 000000783e80b508
DEBUG x24 0000000000000000 x25 000000783eea9f64 x26 0000000000000000 x27 000000783bf5b6a0
DEBUG x28 000000783cba32b8 x29 0000007fd402b340
DEBUG sp 0000007fd402b280 lr 000000783f752ecc pc 000000783f752ef8
DEBUG
backtrace:
DEBUG #00 pc 0000000000081ef8 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: a0262d6029ecf82773ce8ded7eae2f3e)
DEBUG #01 pc 00000000000cd658 /apex/com.android.runtime/lib64/bionic/libc.so (__stack_chk_fail+20) (BuildId: a0262d6029ecf82773ce8ded7eae2f3e)
DEBUG #02 pc 000000000000c1d4 /system/vendor/lib64/libperipheral_client.so (android::pm_register_connect(android::PeripheralManagerClient*, pm_event*)+1300) (BuildId: 86f5115244bdc5060969673fe8ec912f)
DEBUG #03 pc 000000000000ca4c /system/vendor/lib64/libperipheral_client.so (pm_client_register+344) (BuildId: 86f5115244bdc5060969673fe8ec912f)
DEBUG #04 pc 00000000005e20c8 /system/vendor/lib64/libril-qc-qmi-1.so (qmi_ril_peripheral_mng_init+608) (BuildId: 93d4d8a5aa4cb19e245380a0e580da74)
DEBUG #05 pc 00000000001c5e0c /system/vendor/lib64/libril-qc-qmi-1.so (qcril_qmi_load_esoc_and_register_with_pm+572) (BuildId: 93d4d8a5aa4cb19e245380a0e580da74)
DEBUG #06 pc 00000000001ca858 /system/vendor/lib64/libril-qc-qmi-1.so (RIL_Init+84) (BuildId: 93d4d8a5aa4cb19e245380a0e580da74)
DEBUG #07 pc 0000000000002360 /system/vendor/bin/hw/rild (main+784) (BuildId: ccbc728c854718f9a3f0ad92a63f5511)
DEBUG #08 pc 000000000007d798 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: a0262d6029ecf82773ce8ded7eae2f3e)

In the actual *oops* file this error occurs 68 times... And the pid counter is increased by 1. So, rild is started, it crashes and then restarted and so on
[Xperia Z5 Compact Android Development] I_did_it_just_tmrrow:
People told me the best way is to stsrt with building twrp with a selected kernel and bring everything to run with it. Then step by step to get building succesfully the different versions.

Nougat -Android 7 (you did that but should do it with the same kernel)

Oreo - Android 8 (I think you tried it already but not with the same kernel)

Pie - Android 9

Q - Android 10

At the Moment I try to read in my freetime about building Android roms but I am very slowly. Sorry I can not help so much at the moment.

But I think this could be a huge target for many phones with the same chipset. The oneplus 2 had the same when I am not wrong and there is already good progress with LOS10. But I read that Sony does make it difficult for dev's.

But we are still hoping.
[Xperia Z5 Compact Android Development] Berni-0815:
You're right. My problem is the same: I'm still learning.

My idea was to get some information on how to "read" these errors. I don't know anything about dumps and backtraces. Therefore I don't know where to start searching for a point to fix them...
[Xperia Z5 Compact Android Development] trisolaris:
Hi Berni, you may need a customized twrp version to run LOS 17.1! The official twrp version is not yet ready for LOS 17.1 .Maybe GreyLeshy can help? Good luck for the next steps!
[Xperia Z5 Compact Android Development] Berni-0815:
Are you sure or do you suspect?

Because... The system is flashed and the device is starting.

I'm not sure but what else should twrp do?
[Xperia Z5 Compact Android Development] Berni-0815:
Just flashed boot.img and system.img manually using fastboot. Same result...
[Xperia Z5 Compact Android Development] aviraxp:
kang libperipheral_client.so from angler
[Xperia Z5 Compact Android Development] Berni-0815:
What does this file change?
[Xperia Z5 Compact Android Development] Berni-0815:
Tried your repos but stuck in a bootloop.

Got Failed to dlopen() libashmemd_client.so: dlopen failed: library "libashmemd_client.so" not found

Can't find libashmemd_client.so anywhere... :confused:
[Xperia Z5 Compact Android Development] Joel16:
I got 17.1 booting on Z5 Premium. However after a while it starts to lag heavily and it basically becomes unusable until you power off the device. There seems to be some exceptions in the logcat which I'll take a closer look at tonight. (Been very busy with work). I barely had time to look at the logcat last night, however I noticed the crash seems to be happening due to NFC.
[Xperia Z5 Compact Android Development] tarkzim:
This is not the cause of your problem, it must be somewhere else. (i guess it's NFC, try to delete your /system/system/app/NfcNci folder)

And if you don't mind, can we create a telegram group for Z5/C/P development?

let me know via PM.

EDIT: Sorry for misleading, NFC commit was on kitakami common folder of my vendor trees.
[Xperia Z5 Compact Android Development] Berni-0815:
There is no NfcNci at all. Maybe it's not installed before the system crashes while booting...
[Xperia Z5 Compact Android Development] I_did_it_just_tmrrow:
The only diff of the sony xperia 5 normal/premium/compact is the camera and display, or not?

https://www.gsmarena.com/compare.php3?idPhone1=7536&idPhone2=7535&idPhone3=7534#diff-

They share almost the same hardware.
[Xperia Z5 Compact Android Development] Berni-0815:
The camera is always the same; the display is different. The z5p is available as single and dual sim variant.
[Xperia Z5 Compact Android Development] Berni-0815:
Please continue discussing in this thread!
[Xperia Z5 Compact Android Development] strongst:
Thread closed

Please continue here

strongst

Forum Moderator
[LG G6 Questions and Answers] xGiox:
Since we got unlocked bootloaders on several models that was not available before,are there any developers kind enough to test twrp ports and root methods and soon for h870s( dual sim) and other models that got bootloader unlocked.
[LG G6 Questions and Answers] Gerilac:
Yeah, it would be nice since LG Dev team is unlocking our bootloader on demand via mail. I don know what to do now, how (and can i) install twrp and root my phone. Is it the same process like on H870 EU?

LG-H870S via Tapatalk
[LG G6 Questions and Answers] xGiox:
Well we need new files probably,like twrp and so on.
[Huawei Mate 20 Pro Questions & Answers] Davii77:
Updated to EMUI 10 MY LYA-09 with 29 C432 file but some apps like files and Huawei I'd on settings is missing? Anyone has a fix for that? Reinstalled firmware but nothing happened
[Huawei Mate 20 Pro Questions & Answers] dog121:
Did u make a backup via hisuite before upgrading..
[Huawei Mate 20 Pro Questions & Answers] Davii77:
Yes I did but it happens with the fresh install and after restoring the back up the same thing.
[Huawei Mate 20 Pro Questions & Answers] dog121:
Try a downgrade back to 9.1 then try again
[Samsung Galaxy S8 Questions and Answers] Deleted member 9660679:
This is ridiculous for a big company. Unlike other companies (OnePlus), they push updates for old devices but for a 2017 phone not getting Android 10, this is outrageous. As of 2019 a lot of people still use the S8, S8 +, Note 8 and phones of 2017. If Samsung won't finacially and finally make a good choice, I may even migrate back to iPhone. Android 10 is big and many people should deserve a chance for another year to experience it.

Who's with me?