yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Compact Android Development] 115ek:
Hey! It's not the time to give up!

Did you already checked the carbon rom msm8974 repo? https://github.com/CarbonROM/android_device_sony_msm8974-common/commits/cr-6.1 They've got active development there. And [MENTION=5258151]drakonizer[/MENTION] has open sources too. Big thanks for that :good: They had similar problems like we've got. (no wonder, it's the same platform, just the big sister of our device ;)).

I've got not much time, but we should look into their commits. I already saw something in relation to credmgrd and sockets...

https://github.com/CarbonROM/android_device_sony_msm8974-common/commit/9583ba84a8201eae6197cd236a628bed898d1279

Come on, lets give it a try! :fingers-crossed:
[Xperia Z1 Compact Android Development] munjeni:
That have nothing to do with our problem since we right now use permissive selinux. Problem is not credmgr and sockets, its working! Credmgr and its service was sucesfully init, problem is something diferent e.g. hidl implementation
[Xperia Z1 Compact Android Development] Viktor245:
IN aicp firmware, too, problems with the Internet and the camera, they do not lose hope for success, and you do not lose hope!
[Xperia Z1 Compact Android Development] 115ek:
I took a strace of /vendor/bin/hw/android.hardware.wifi@1.0-service.

But it hangs at the end with ERESTARTSYS. I had to kill strace with ctrl-c.

9766 fstat64(6, {st_mode=S_IFREG|0444, st_size=131072, ...}) = 0
9766 mmap2(NULL, 131072, PROT_READ, MAP_SHARED, 6, 0) = 0xab074000
9766 close(6) = 0
9766 openat(AT_FDCWD, "/proc/self/cmdline", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 6
9766 fstat64(6, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
9766 read(6, "/vendor/bin/hw/android.hardware."..., 1024) = 49
9766 read(6, "", 1024) = 0
9766 close(6) = 0
9766 futex(0xaab66088, FUTEX_WAKE_PRIVATE, 2147483647) = 0
9766 ioctl(4, _IOC(_IOC_READ|_IOC_WRITE, 0x62, 0x1, 0x18), 0xbeec4538) = 0
9766 ioctl(4, _IOC(_IOC_READ|_IOC_WRITE, 0x62, 0x1, 0x18), 0xbeec4538) = 0
9766 ioctl(4, _IOC(_IOC_READ|_IOC_WRITE, 0x62, 0x1, 0x18), 0xbeec4090) = 0
9766 ioctl(4, _IOC(_IOC_READ|_IOC_WRITE, 0x62, 0x1, 0x18), 0xbeec4538) = 0
9766 ioctl(4, _IOC(_IOC_READ|_IOC_WRITE, 0x62, 0x1, 0x18), 0xbeec4718) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
9766 --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
9766 +++ killed by SIGINT +++

Any ideas on that? :confused:
[Xperia Z1 Compact Android Development] 115ek:
I've got new findings... Logcat leads me to frameworks/opt/net/wifi/libwifi_system_iface/interface_tool.cpp

So [MENTION=4120742]munjeni[/MENTION] was right. They try to create a socket here. But that fails. (probably caused by missing permissions...).

How to find out which files needs which permissions now? :confused:

I think libwifi-system-iface.so is the problem. android.hardware.wifi@1.0-service loads it and uses one of the functions GetUpState or SetUpState().

BTW: libwifi-system-iface.so seems to be new in 8.1. That could explain the working wifi in 8.0. :rolleyes:

Any advice?

bool InterfaceTool::SetUpState(const char* if_name, bool request_up) {
[COLOR="Lime"]base::unique_fd sock(socket(PF_INET, SOCK_DGRAM | SOCK_CLOEXEC, 0));[/COLOR]
if ([COLOR="red"]sock.get() < 0[/COLOR]) {
LOG(ERROR) << "[COLOR="Red"]Failed to open socket to set up/down state[/COLOR] ("
<< strerror(errno) << ")";
return false;
}

struct ifreq ifr;
if (!GetIfState(if_name, sock.get(), &ifr)) {
return false; // logging done internally
}

const bool currently_up = ifr.ifr_flags & IFF_UP;
if (currently_up == request_up) {
return true;
}

if (request_up) {
ifr.ifr_flags |= IFF_UP;
} else {
ifr.ifr_flags &= ~IFF_UP;
}

if (TEMP_FAILURE_RETRY(ioctl(sock.get(), SIOCSIFFLAGS, &ifr)) != 0) {
LOG(ERROR) << "Could not set interface flags for " << if_name
<< " (" << strerror(errno) << ")";
return false;
}

return true;
}
[Xperia Z1 Compact Android Development] munjeni:
Lineage 14.1 working wifi:

init.qcom.rc:

service wpa_supplicant /system/bin/wpa_supplicant \
-iwlan0 -Dnl80211 -c/data/misc/wifi/wpa_supplicant.conf \
-I/system/etc/wifi/wpa_supplicant_overlay.conf \
-e/data/misc/wifi/entropy.bin -g@android:wpa_wlan0
# we will start as root and wpa_supplicant will switch to user wifi
# after setting up the capabilities required for WEXT
# user wifi
# group wifi inet keystore
class main
socket wpa_wlan0 dgram 660 wifi wifi
disabled
oneshot

service p2p_supplicant /system/bin/wpa_supplicant \
-ip2p0 -Dnl80211 -c/data/misc/wifi/p2p_supplicant.conf \
-I/system/etc/wifi/p2p_supplicant_overlay.conf -N \
-iwlan0 -Dnl80211 -c/data/misc/wifi/wpa_supplicant.conf \
-I/system/etc/wifi/wpa_supplicant_overlay.conf \
-puse_p2p_group_interface=1 \
-e/data/misc/wifi/entropy.bin -g@android:wpa_wlan0
# we will start as root and wpa_supplicant will switch to user wifi
# after setting up the capabilities required for WEXT
# user wifi
# group wifi inet keystore
class main
socket wpa_wlan0 dgram 660 wifi wifi
disabled
oneshot

Lineage 15 not working wifi:

init.qcom.rc:

service wpa_supplicant /vendor/bin/hw/wpa_supplicant \
-ip2p0 -Dnl80211 -c/data/misc/wifi/p2p_supplicant.conf \
-I/system/etc/wifi/p2p_supplicant_overlay.conf -N \
-iwlan0 -Dnl80211 -c/data/misc/wifi/wpa_supplicant.conf \
-I/system/etc/wifi/wpa_supplicant_overlay.conf \
-puse_p2p_group_interface=1 \
-e/data/misc/wifi/entropy.bin -g@android:wpa_wlan0
# we will start as root and wpa_supplicant will switch to user wifi
# after setting up the capabilities required for WEXT
# user wifi
# group wifi inet keystore
class main
socket wpa_wlan0 dgram 660 wifi wifi
disabled
oneshot

I didn't remember why I changed it in init.qcom.rc! Does wifi worked in 8.0?
[Xperia Z1 Compact Android Development] vyunov55:
Yes he been worked.
[Xperia Z1 Compact Android Development] 115ek:
Yes, it was working in 15.0

And it is working in 15.1 now ;)

I finally found the trick: hardware/interfaces/wifi/1.1/default/android.hardware.wifi@1.0-service.rc needed a patch. I already played with it a week ago, but I had no luck.

What comes next? LED and sensors?

Are you motivated to fix some things? :fingers-crossed:
[MENTION=6425591]SpiritCroc[/MENTION] is also on the way with his AICP. There are some more things working on his build :cool:
[Xperia Z1 Compact Android Development] munjeni:
What you done for wifi? I'm not demotivated but soo lazy, to be honest I'm at this moment bored with android, thing which happeninng on android all the time (progress kill) after every api change make me lazy doing anything at this moment, maybe later thing change in my head but not right now. :o Hope somebody get some progress on mainline kernel and os which I forgot its name :) [MENTION=4900593]mirhl[/MENTION] know what I mean

My another z1c (dev phone) is with totaly dead battery, only red led blinking, so I can't test. On main phone I'm so lazy too test since I need phone daily.
[Xperia Z1 Compact Android Development] mirhl:
I swear you'd fap over on #postmarketOS and ##linux-msm (where I guess there's still no display driver, but hey, you have rob freaking clark all for yourself)
[Xperia Z1 Compact Android Development] 115ek:
Heyho. I tried logging in into xda since yesterday without success. Seems that something is broken :confused:

Anyway - I'm finally in here.

Wifi works with this commit https://github.com/115ek/android_device_sony_amami/commit/e03648106821b99952dfe5097d2f94a79ddda219.

It seems we aren't the only ones getting this problem. The guys from HalogenOS also used this patch https://review.halogenos.org/c/484.

And I fixed the LED. It was broken due to changes in the lineage-SDK :silly:

I think the biggest problem will be the camera. You're an expert with it, aren't you? ;)
[MENTION=6425591]SpiritCroc[/MENTION] made some progress with RIL problems. Maybe mobile data and telephony are working on his build. Unfortunately I can't test. My dev device has got a broken SIM reader. And the working one is in daily use with 14.1 :cool:
[Xperia Z1 Compact Android Development] 115ek:
Just as a note:

I switched to [MENTION=6425591]SpiritCroc[/MENTION]'s AICP sources and built lineage 15.1 succesfully. Look over here https://xdaforums.com/sony-xperia-z1-compact/orig-development/rom-aicp-13-1-o8-1-amami-t3755554 to see whats working. I think about opening an own thread with the lineage build. But actually AICP looks and feels really similarly. Let's see...

Big thanks [MENTION=6425591]SpiritCroc[/MENTION] :good:
[Xperia Z1 Compact Android Development] jho55:
It would be nice to see if the camera quality could be matched in comparison to [MENTION=4120742]munjeni[/MENTION] los 14.1. rom.
[Xperia Z1 Compact Android Development] munjeni:
Soo wifi and led is working? From my last own test build (lineage 15.1) ril was worked! See this post about working ril https://xdaforums.com/showpost.php?p=75564960&postcount=55 and non working camera because this failed:

02-14 14:00:57.622 363 887 E [COLOR="Red"]CamDev@1.0-impl[/COLOR]: Could not open camera 0: -19
02-14 14:00:57.622 363 887 E CameraHardwareInterface: initialize: openSession failed! Function not implemented (-38)
[Xperia Z1 Compact Android Development] 115ek:
Yes, wifi and led is working. But I switched to the AICP sources now. I think that's better because it's already in a usable state. It's wasted time and power to repair everything on your own.

There are only minor issues and it's possible to profit from other sony developers like [MENTION=2233641]AdrianDC[/MENTION]. What was your starting point? Do you started with cyanogen/lineage tree?

NFC is still not usable with the AICP sources - what was your progress with it in 14.1?

And how was the camera improved? You used a modified stock kernel instead of CM kernel, right?

I thought the bad image quality in custom firmwares results from the absence of frameworks patches the vendor did on his own Stock version.

And there's no source available because the vendor wants to keep the secret of his extra pretty images.

What about contributing to AICP? It's a only a tiny patch in makefiles to go back to a lineage build (because AICP in newer versions is forked from lineage.).

I'll upload a manifest and device repo with patches later this day. Then you can have a look. :cool:
[Xperia Z1 Compact Android Development] mirhl:
Afaik that's workaroundable nowadays.
[Xperia Z1 Compact Android Development] munjeni:
I will stay on Lineage 15.1. Didn't remember starting point, it was based on [MENTION=4311238]SuperLamic[/MENTION] LOS14.1 work, you can get changelog one by one on my site, I have uploaded device tree for LOS15 and also kernel changes on my git, all is based on LOS 14.1 and work done for LOS 15, don't have LOS 14.1 device tree right now since I have modified it for LOS15 (15.1), kernel source code is fully on my git booth for 14.1 to 15.1. Kernel is modified stock kernel. Nfc on 14.1 is half working, can't tell you how its working since I newer used nfc. Camera on LOS 14.1 is based on stock blobs and fully working, you can install stock camera app on it. Camera quality at least what I have found is no diferencie, for me its better on LOS than stock rom, much faster and responsive, image quality I didn't noticed diferencie. I wil not contribute to AICP, only to LOS (don't promise anything, I said what I think about android some posts back). And I am low active on xda since injuistice happened with me, my title lost, it disapointed me.
[Xperia Z1 Compact Android Development] levone1:
It's what has always made you the best - you're not afraid to stick your neck out and you're not always trying to please everyone. It has the unfortunate side-effect of causing simple-minded reactions in those who don't get it.

Thanks for your work.
[Xperia Z1 Compact Android Development] cedar555:
Hi. You still supports the firmware? If so, where can I download the latest version?
[Xperia Z1 Compact Android Development] cedar555:
Could you upload your fixed version to the site?

Just the one that was posted by the developer is outdated
[Xperia Z1 Compact Android Development] 115ek:
I'm going to do so. Just waiting for the registration on afh to finish.

By the way: my current Lineage build is based on [MENTION=6425591]SpiritCroc[/MENTION] (AICP) sources. You can find them here.

For now the camera isn't working. I need to apply some patches SpiritCroc already figured out.

Except of this, everything should work as in AICP 13.1.

If you want a continuously updated firmware you should better stick to AICP. I think OTA updates are planned therefore as soon as some more bugs are fixed...
[Xperia Z1 Compact Android Development] cedar555:
I have no 3g on his rom, It is awful
[Xperia Z1 Compact Android Development] jho55:
I have 3g on AICP 13.1 when I tried it. Just be patient.
[Xperia Z1 Compact Android Development] 115ek:
You have three options:

fix the issue by yourself, source is freely available

wait for [MENTION=6425591]SpiritCroc[/MENTION] fixing the issue (if it really is an issue)

don't use preview version, or custom firmwares at all

Your useless comments don't help in any case.

Please consider this is a developer forum, all guys here invest their free time to bring something up.

No one forces you to use their software. You still can use the stock software - and maybe that's the better option for you.
[Xperia Z1 Compact Android Development] cedar555:
I tried to fix it, the logs laid out, but it was useless

Could you tell where to look for the problem?
[Xperia Z1 Compact Android Development] jho55:
[MENTION=6807112]cedar555[/MENTION]: you mentioned that it worked with an older version:

So unpack the working version, unpack the non working version. Compare both folder and then at least you know which files could be affected.
[Xperia Z1 Compact Android Development] cedar555:
The type of network switched, but the Internet was not working
[Xperia Z1 Compact Android Development] jho55:
[/COLOR]

so you mean it was not working at all? The whole time? also with older version of AICP 13.1? I understood it like it was working for you in an older build.
[Xperia Z1 Compact Android Development] cedar555:
You didnt understand. I had no Internet conection with 3g/2g almost always, but sometimes it works. It is strange, really? Network type swithed on march version, on April version it is not switch.
[Xperia Z1 Compact Android Development] jho55:
If it is not working almost at all, but for all the other users, then something is wrong maybe with your phone. You can now only be patient and use a rom which is working for you and try new roms from time to time when they appear.
[Xperia Z1 Compact Android Development] 115ek:
Just did a quick build for testing purposes: camera und video recording should work.

https://androidfilehost.com/?w=files&flid=269301

(Nearly) all credits to [MENTION=6425591]SpiritCroc[/MENTION] . You'll find my manifest here: https://github.com/115ek/manifest
[Xperia Z1 Compact Android Development] Samwei14:
Tested video recording and it works :)

Compared to this thread last build: https://xdaforums.com/sony-xperia-z1-compact/development/rom-lineage-os-15-1-sony-xperia-z1-t3785057

where video recording freezes - thank you :)
[Xperia Z1 Compact Android Development] vhcolombo:
What changes you made out to make the camera work?

We have the same problem in Lineageos 15 for Moto X 2014
[Xperia Z1 Compact Android Development] Rafaru:
Hello ,I am selling away my z1 compact , how can I downgrade from Lineage to latest stock firmware please ??

Thanks for your help
[Xperia Z1 Compact Android Development] knv01:
You have to restore your drm keys, then you have to close your bootloader. After that you can restore the original firmware with the Sony suite.
[Xperia Z1 Compact Android Development] jho55:
For unlocked bootloader you can also use the EMMA tool from Sony. It is meant for users with unlocked bootloader to install original rom again.
[Xperia Z1 Compact Android Development] Rafaru:
Hello , I found out and did so , but I am not sure if using EMMA also restores stock kernel , is it ??? Also as I have a backup of TA how do I restore it please ?? Shall I root again ???

Thanks for your help
[Xperia Z1 Compact Android Development] jho55:
It is restoring stock kernel because EMMA wipes phone and then flash stock rom! So stock kernel is also included! I do not know what to do then with the TA backup. Maybe you can leave it like it is?
[Xperia Z1 Compact Android Development] DeadXperiance:
I think you should read this thread for restore your Ta Backup

https://xdaforums.com/showthread.php?t=2292598
[HTC 10 Questions & Answers] Devzz:
Hey,

Bit of a weird one - So I have the bootloop issue and have had it for a couple of months if not longer (https://xdaforums.com/htc-10/help/random-shut-boot-loops-t3690547).

A few days ago, my phone shut down randomly at around 45-50% and when it rebooted, it seems to have corrupted something and now my fingerprint reader does not read my print. The scanner works fine as it still turns the screen on when I tap it. To unlock the screen, it says "pattern required to enable fingerprint" but regardless of how many times the pattern is entered, the scanner does not set to read the fingerprint data.

I cannot amend the scanned prints either. In settings, it does not allow me to delete my current prints. It also does not allow me to add any more. The setup wizard runs but when it asks me to scan my finger, it simply gives a red error at the bottom stating "Fingerprint setup was cancelled. Please try again."

If it helps, I am rooted with Magisk, I have systemless xposed framework version 88.2 and elementalX kernel 3.18.31 with the kernel manager.

WITHOUT having to wipe my phone/factory resetting it, is there anything I can amend either via the kernel manager or through system files that may help?

Thanks in advance for any help!
[HTC 10 Questions & Answers] sphinxcs898:
Are you using the latest version of Venom? I had a similar problem when upgrading from 3.5.0 to 5.11.0 - where I selected the incorrect kernel version ( i haven't changed my kernel yet) - and the fingerprint scanner option completely disappeared post-install. To make matters worse, the Home button stopped working as well.

I had to reset everything and reinstall the ROM again with the correct kernel selected from Aroma. This did the trick.
[HTC 10 Questions & Answers] mtoda:
Same exact problem...

I also have the same exact problem!! Except my phone is still stock. I haven't rooted it or put any mods on it. It started like the original post said, where the phone randomly rebooted, then the finger print reader stopped working. The button itself still works fine. I can wake the phone up by pressing on it, get to the home screen, and even activate google now by holding it down... Everything works fine except for the damn fingerprint scanner. And the strangest part is, as mentioned, before, I can't edit/delete existing fingerprints from the menu settings.

My phone is bought unlocked from HTC, and i haven't installed anything recently. Any help would be appreciated! Thanks
[HTC 10 Questions & Answers] Eaboo:
The exact same problem

Anyone has a solution for this please?
[HTC 10 Questions & Answers] lechaim:
Same

having the same issue
[HTC 10 Questions & Answers] wiktor717:
Same here, all stock and full updated. Can't unlock by fingerprint, I need to use the pin, I can't reset settings for fingerprint.
[HTC 10 Questions & Answers] michal.fuciman:
Same exact problem

I am the next one with the same issue. It seems like it is hardware issue. It also began with the restarts when the battery was appr. 50%. Now, after 3-4 months of unexpected restarts the fingerprint scanner has the same issue as described. It happened without any new installation or update. My phone is original without rooting. Only official updates. I tried many ways, how to solve it including restart in safe mode, nothing helped. Does anybody tried to replace the home button with the scanner?
[HTC 10 Questions & Answers] wiktor717:
I'm sure that's that is not any hardware issue. If it was, you could reset fingerprint settings without any issues. There's some sort of software problem, propably caused by some app update. Why? Because we all get same problem at once.
[HTC 10 Questions & Answers] wiktor717:
Have you guys tried to install ruu? Mine fingerprint scanner works now after trying ruu, so maybe try that
[HTC 10 Questions & Answers] ryllyq:
I had the exact same issue. Nothing worked including booting into Safe mode. Ended up doing a factory reset which solved the fingerprint scanner issue. I hope it doesn't come back after the next crash T.T (I'm currently waiting for a new battery I ordered to see if it fixes the bootloop issue I am facing as well).
[HTC 10 Questions & Answers] Feniu:
Have you been doing something after replacement, calibration or hard reset? I was having typical problems, shutdowns and bootlops, crap battery life etc. After buying new battery and replacing it by gsm service the problems with bootlops and shutdowns are gone (it looks like), but im getting only arround 3hrs on SoT. Looking for issue for that situation, want to get a little bit more.
[HTC 10 Questions & Answers] nitinrajpoot007:
Fingerprint scanner not working

I've also faced same problem...just a simple solution...hope it works for all ..just go to settings>apps>system apps>fingerprint scanner and clear all data then force stop and just restart it...now add add fingerprint. :)

Thanxx
[Essential Phone Questions & Answers] Bill1976:
Hi everybody,

We have essentia phone with a friend and we have the same problems.

1) whastapp voice messages very frequently cut the time, and not leave too record more than 1 second, you have to restart the phone

2) smart lock blank screen, you have to unselect trusted app xxx and restart the phone to get back the menu, and sometimes it stay unlocked showing the lock icon open...

Any solution?
[Essential Phone Questions & Answers] lifeisfun:
Happens on other devices as well, disable Smart lock in Trust Agents reboot and enable it again
[Essential Phone Questions & Answers] warpjavier:
I had the same problem with whatsapp once. I don't know if there was an update or what but it fixed itself.
[Essential Phone Questions & Answers] minhas4all:
Have same issue whatsapp record 2 sec only then have to restart the phone.

please advise some thing

thanks
[Essential Phone Guides, News, & Discussion] badbomb:
Call audio reduces whenever a notification is received. But it doesn't go back to the original volume again. It stays the same. It comes back to normal once the call ends. Hopefully this is fixed in Oreo.
[Tilt, TyTN II, MDA Vario III General] mcq3000:
I have searched the forums long and wide for it and I cannot find it. Is it simly cooked into roms as an oem package or is there an actual cab we can install for those that are using prebuilt roms?
[Tilt, TyTN II, MDA Vario III General] lowreeds:
look here

http://xdaforums.com/showthread.php?t=356192

read the first post. I think you will have to create the Long_End.lnk and assigned it to EndKey.exe

this may also be of interest

http://xdaforums.com/showthread.php?t=356322
[Tilt, TyTN II, MDA Vario III General] thomassster:
i'm pretty sure you didn't try the advanced google search. Please use that next time. Searching endkey cab on there gave me a bunch of searches on this thread.

http://xdaforums.com/showthread.php?t=344533
[Tilt, TyTN II, MDA Vario III General] SH4YD33:
Here you go...
[Tilt, TyTN II, MDA Vario III General] kyakubov:
long press delay

is there a way to change the durations of long press?

I think it takes too long for along press end key and long press power keys to work.

I can't seem to find the registry entry where to change.

Any help is appreciated.

thanks

K
[Tilt, TyTN II, MDA Vario III General] marm0lade:
I actually think he wants "long press power key". That is the one that is cooked into numerous roms. If you search for long press end key, or HTC end key, you will find plenty of threads. Long press power key is a different story.

Edit: Ok I think I was wrong. Long press power key is by Schaps. He wants the long press end key mapped to the red end call button. If you install it normally, which is what you get 10000 threads on if you search, it installs it to the right soft key.