yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Original Android Development] okij:
Thanks for your reply. :)

In the meanwhile, I took a TWRP backup and installed the latest Carbon build from last Tuesday for testing WiFi. But WiFi signal strength is the same as with latest LineageOS build, so the Carbon commit you pointed me to doesn't help in this matter.

I then also tested the changes of the commit I wrote of (since it uses different, probably even older blobs than those used by Carbon now) but they also deliver just same WiFi signal strengths. So I guess we really have to live with it.

(Before you are asking: Since I'm not a dev I made a small Magisk module which places the older versions of bcmdhd.cal, fw_bcmdhd.bin and fw_bcmdhd_apsta.bin into their according places.)

I was also hoping that Screen Cast would start to work with the older drivers, but so far I couldn't get it to work on any 7.1 ROM.

I'm now restoring my LOS TWRP backup.

And hey, it's great to see you and [MENTION=6979267]nailyk[/MENTION] chat on the dev channel again. :)
[Xperia Z3 Compact Original Android Development] FlintStoned-:
May I ask, do you guys also suffer from slow changing speed? I for example am at 83% and it says it would take 46min until full charge. Any thoughts?
[Xperia Z3 Compact Original Android Development] zEminho:
This is correct ?
[Xperia Z3 Compact Original Android Development] skaterbub2003:
Just FYI: I had no charging reboots for a while now. I don't know if it's because I removed my SD card. But this is the only thing I had changed recently. ^^

I'm still on version 17/06/07.
[Xperia Z3 Compact Original Android Development] Robot76:
I did have this annoying problem, especially when charging from my pc's usb port, seemed ineffective but now it's fine,

I wonder if it's because I am now using magisk 13.3, as I heard v12 was doing a lot of processing, or whether it's because of the new magisk enable doze google play services, or magisk for greenify?

Or some other tweak

Perplexing, or maybe all my tweeks balanced out the problem...

[emoji7]

Time will tell...

Λ.᪃.I.S.Ξ_Z3C_MΛGISK_SUᗱST᪃ΛTUM
[Xperia Z3 Compact Original Android Development] difto:
For what it's worth, I never used an SD card (the SD card reader is dead on my phone) and never had any reboots when charging on any version.

---------- Post added at 09:28 AM ---------- Previous post was at 09:17 AM ----------

I posted a log some time ago on this issue (on page 89)

Not sure if it will help or not, when I recorded it, LTE, 3G and EDGE network where available but the phone did not reconnect to any of them until reboot. Then I had another related issue, it would only connect to EDGE network although LTE and 3G where available. If I tried to change the network manually, it would see both 3G and LTE as forbidden. There is also a log on this issue on page 89.
[Xperia Z3 Compact Original Android Development] tomascus:
[MENTION=6058817]difto[/MENTION] [MENTION=4916555]okij[/MENTION] and anyone else with data issues. Need testers.

1. Backup boot (boot image) in TWRP

2. Flash this kernel: https://www.androidfilehost.com/?fid=745425885120752459

3. Report back after using data for some time
[Xperia Z3 Compact Original Android Development] okij:
Now this becomes really interesting, as it might narrow down the search for the bug significantly. Thanks for reporting! :good:

[MENTION=4675360]tomascus[/MENTION], [MENTION=4550727]xkeita[/MENTION], [MENTION=6979267]nailyk[/MENTION], [MENTION=4063475]derf elot[/MENTION], [MENTION=5621191]rcstar6696[/MENTION], [MENTION=3816568]Myself5[/MENTION] (sorry for tagging all of you ;) ): If this is no coincidence, it should guide the way to further debug the nightly reboot issue. I know that it has been supposed before that a nightly fstrim operation could cause the reboots, so this might still be the case, but only apply to attempts of the system to fstrim the external SD card.

Of course also a media scan of the external SD card or something like that could be the reason.

I hope that this new approach helps you to finally fix this issue. :fingers-crossed:
[Xperia Z3 Compact Original Android Development] idreamer86:
Hi,

i flashed the recovery via fastboot mode (it flash in boot partition). But when use it to install rom via zip it broke the recovery. Where i make mistake?

I have the same problem with network data.. how is the best way to flash kernel?

Thanks
[Xperia Z3 Compact Original Android Development] okij:
Thanks for the test kernel! :good:

Just one question: I guess it is for debugging the mobile data connection issue? (So not about WiFi data, since we talked about this yesterday.)

For me it happens quite rarely that I get no mobile data after leaving WiFi network (the last time was on the day I flashed the 07-26 build and it didn't happen since), so we need some more testers who have this issue too.
[Xperia Z3 Compact Original Android Development] tomascus:
There are clear instructions in the second post.

Doesn't my post say " anyone else with data issues"? :P
[Xperia Z3 Compact Original Android Development] okij:
Yep, but there's both mobile data and wifi data. ;)
[Xperia Z3 Compact Original Android Development] khalisz:
That's will be nice if you could add it : Energy Aware Scheduling (EAS)

https://developer.arm.com/open-source/energy-aware-scheduling
[Xperia Z3 Compact Original Android Development] tomascus:
1. It's based on top of 3.18/4.4 kernel, we're on 3.4 kernel. It would be major major major pain to backport it.

2. EAS seems to be made in mind primary for big.LITTLE architecture CPUs.

3. Energy model values for each CPU and sched energy cost values need to be calculated and no idea how to do that because afaik it has never been done with a homogeneous CPU like ours.

4. LineageOS is generally against massive changes like this.

The time and effort it would take is not worth it.
[Xperia Z3 Compact Original Android Development] difto:
Thanks tomascus, I flashed the kernel and will report back.
[Xperia Z3 Compact Original Android Development] MagicRobert:
Home Button

Hi,

I have some issues with the home button.

It works for a long time. And at some point, it stops working. The touch is registered, the phone gives audio and haptic feedback., but nothing happens.

This is the logcat output, when I click the button, when it's already broken:

281 439 D audio_hw_primary: start_output_stream: enter: stream(0xb6170140)usecase(1: low-latency-playback) devices(0x2)
281 439 D audio_hw_primary: start_output_stream: enter: usecase(1: low-latency-playback) devices(0x2)
281 439 D audio_hw_primary: select_devices: out_snd_device(2: speaker) in_snd_device(0: )
281 439 W msm8974_platform: Codec backend bitwidth 16, samplerate 48000
281 439 D hardware_info: hw_info_append_hw_type : device_name = speaker
281 439 I msm8974_platform: platform_send_audio_calibration: sending audio calibration for snd_device(2) acdb_id(15)
281 439 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 15, path = 0
281 439 D ACDB-LOADER: ACDB -> send_adm_topology
281 439 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
281 439 D ACDB-LOADER: ACDB -> send_asm_topology
281 439 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
281 439 D ACDB-LOADER: ACDB -> send_audtable
281 439 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
281 439 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL
281 439 D ACDB-LOADER: ACDB -> send_audvoltable
281 439 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
281 439 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
281 439 D ACDB-LOADER: ACDB -> send_afe_cal
281 439 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
281 439 D ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL
281 439 D audio_hw_primary: select_devices: done
3170 3170 I SlideTouchEvent: vel=111.27916, MinimumFlingVelocity=100
3170 3170 I SlideTouchEvent: Sliding distance is too short, can not trigger the single hand mode
2369 2405 V KeyguardServiceDelegate: **** onKeyguardExitResult(false) CALLED ****

And the dmesg output:

pastebin.com/ B991Jq6z (can't post links yet...)

And, I'm using the 2017-07-26 release.
[Xperia Z3 Compact Original Android Development] tomascus:
Bad news: Issue still occurs with this.

But it looks like I have almost identified the cause, can both of you please go to /data/tombstones and copy all the tombstone files to a zip and upload here?
[Xperia Z3 Compact Original Android Development] okij:
Graveyard is attached, hope it helps. :)
[Xperia Z3 Compact Original Android Development] Xelux_usa:
Is NFC payment working on last version?

With magisk, i have configured my bank app for NFC payments, i will try to use when possible and report
[Xperia Z3 Compact Original Android Development] strofo:
I also passed SafetyNet test with Magisk and activate bank app. But when I try to pay with the phone, the POS terminal is unable to register the phone. I am able to scan credit card with the phone, so NFC is working.
[Xperia Z3 Compact Original Android Development] nailyk:
Your touch is registered as a slide event:

3170 3170 I SlideTouchEvent: Sliding distance is too short, can not trigger the single hand mode

Try disabling it into settings.
[Xperia Z3 Compact Original Android Development] Xelux_usa:
So NFC payments doesnt work? :(
[Xperia Z3 Compact Original Android Development] strofo:
Nope. At least for me.
[Xperia Z3 Compact Original Android Development] blue4you:
How did you do that?

With magisk my phone fail with cts profil
[Xperia Z3 Compact Original Android Development] strofo:
with Universal SefetyNet Fix module.
[Xperia Z3 Compact Original Android Development] difto:
And here you go. The issue still did not occur with the new kernel on my side.
[Xperia Z3 Compact Original Android Development] Xelux_usa:
I can confirm NFC payments are working.

I've already use it 3 times in different shops without problems.

It's working perfectly
[Xperia Z3 Compact Original Android Development] maxtkp:
I have collected some more last_kmsg files. During last week I had random reboots basically every time I charged my phone. I encrypted my data partition and the phone makes a sound when waiting for the unlock key to be able to boot into android. So I get to know when the phone rebooted. Unfortunately it wakes me up at night sometimes. But here are some log files:

2017-07-14: pastebin.com/LdTc1HUb

2017-07-27: pastebin.com/nYp2F4wU

2017-07-27: pastebin.com/s8bVBHg7

2017-07-30: pastebin.com/eU4PjitC

2017-08-01: pastebin.com/spQa5MtN

I hope that helps to find the source... Anything else that I can to to help you find the bug?
[Xperia Z3 Compact Original Android Development] claudiobar:
Hi Tomascus. Just to let you know that I tried flashing the new kernel provided, and the connectivity improved hugely in my case (I was having this issue as well, but thought it'd be related to my cheap-o carrier)

Thanks!!!!!!!!!!!!
[Xperia Z3 Compact Original Android Development] .:B:.:
Question: are you using profiles? I haven't reported this, but I get similar behaviour when auto-switching profiles. Home button will stop working. When I switch back to the previous profile, then switch manually, it will work again. I haven't had the chance/time to log and report this though.
[Xperia Z3 Compact Original Android Development] mcgi5sr2:
build for testing DATA connectivity

Hello,

here is a build which I would like people to test for the data connectivity bug. That is the bug that you lose data connection when fast toggling data connection on and off, and/or when you disconnect from wifi and try reconnecting to data.

I am not interested in anything else, so please don't reply about it. Relevant logs are welcome, but not necessary in this case.

To be clear you can replicate this bug by fast switching your data on and off lots and lots of times. This is then only fixed by a hard reboot. If you install this build, please let me know if you can make this happen!

To sweeten the deal and pull more testers in I have added OMS to the build, as a honey pot for testers.

link:https://www.androidfilehost.com/?fid=673368273298975996

MD5:455620189156abf08438855559e327e4
[Xperia Z3 Compact Original Android Development] okij:
[MENTION=4675360]tomascus[/MENTION], [MENTION=4901061]mcgi5sr2[/MENTION]: This morning I had the mobile data loss again after leaving the WiFi network. There have been two tombstone files from yesterday evening (already being in WiFi network). I attached them in case you still need them.

[MENTION=4901061]mcgi5sr2[/MENTION]: Thanks for your test build! One question: Is the relevant change in the kernel? If so, I can't test it yet, since I'm currently testing [MENTION=4275152]someone755[/MENTION]'s r_11 release of his Kernel12 which might fix the fix reboots on charger (3am reboots).
[Xperia Z3 Compact Original Android Development] tomascus:
Yes, most of us already know about this but i'm holding off release until this data issue is sorted out
[Xperia Z3 Compact Original Android Development] mcgi5sr2:
Not kernel related afaik
[Xperia Z3 Compact Original Android Development] someone755:
Just for the record, https://review.choose-a.name/#/c/723/

It apparently does fix the issue.
[Xperia Z3 Compact Original Android Development] mcgi5sr2:
yea sorry pal, wasn't saying reboot wasn't kernel issue. Was saying the data "fix" wasn't kernel related!
[Xperia Z3 Compact Original Android Development] someone755:
No worries, I wasn't referencing the data issue.
[Xperia Z3 Compact Original Android Development] difto:
What is the difference between this and the test kernel posted by tomascus? I did not have any data drop yet with the new kernel
[Xperia Z3 Compact Original Android Development] tomascus:
I can reproduce the issue on the test kernel, issue is not related to kernel it seems.
[Xperia Z3 Compact Original Android Development] blue4you:
I can confirm this, yesterday I removed my SD card and last night, I did not have a reboot.

I'm on 17/07/26
[Xperia Z3 Compact Original Android Development] exh333:
Mobile data issue seems fixed with this kernel for me, need more testing, don't know about wifi, i don't use it.
[Xperia Z3 Compact Original Android Development] MagicRobert:
Yes, I am using profiles. They are activated by WiFi connect/disconnect.

Good to know, because I hadn't seen any correlation between the profiles and the breaking of the home button.

Finally, I found out where the gestures are configured (Settings->Languages & Input->Virtual keyboard->AOSP->Gesture Typing)

When the problem already occurred, disabling gestures had no effect.

I disabled the gestures now. I will report back, if the problem happens again with gestures initially disabled.

---------- Post added at 10:25 PM ---------- Previous post was at 10:16 PM ----------

At least in the gesture settings there is the sentence:

Maybe the work "SlideEvent" refers to "Slide to unlock".

In one of my profiles ("Home"), I disable the lock screen. And in the "Default" I explicitly enable it.

Maybe it has to do with bad timing on WiFi loss and the lock screen?

---------- Post added at 10:36 PM ---------- Previous post was at 10:25 PM ----------

Ok, now it was fairly easy to reproduce:

Disable WiFi on my router to ensure I'm in "with lockscreen" profile

Press power button to turn screen of / lock phone

Enable WiFi again

Wait for WiFi begin up to ensure I'm in "no lockscreen" profile

Press power button again

The phone starts without lock screen, but the home button doesn't work

The problem does not arise, when the screen is on while reconnecting.
[Xperia Z3 Compact Original Android Development] difto:
I dirty flashed it + dalvik/cache cleared (did not have the time to do a clean install) and I still have the issue, could replicate it four times with less than 10 attempts each. Not sure a clean flash would do a difference.

Did further testing, re-flashed 26/07 version, same as the test firmware, repeated two times, bug occurs after less than 10 attempts.

Flashed the kernel from tomascus, while the connection dropped after about 5 attempts, re- toggling mobile data restored it, happened three times and each of them the connection recovered (30 attempts in total). So for me it is the best solution known (and in real life it did not drop in three days)
[Xperia Z3 Compact Original Android Development] okij:
[MENTION=4901061]mcgi5sr2[/MENTION]: I also dirty-flashed your test build (+ [MENTION=4275152]someone755[/MENTION]'s Kernel12 v_11) and so far I didn't have mobile data drops, also not after toggling mobile data off and on 10+ times. Just for the statistics.

[MENTION=4675360]tomascus[/MENTION]: I didn't have any BT connection problems again after I reported it for the 07-26 build on the same day. So maybe it was caused by thermal throttling (as another user supposed), since the phone was quite warm after flashing and the first booting, or this also is an issue which just happens after first boot and is fixed by rebooting. If it should happen again I will report it, but ATM I'm happy. :)
[Xperia Z3 Compact Original Android Development] autan:
[MENTION=4675360]tomascus[/MENTION] , los 08/02 tested. Bt now work without disconect with sbh 60, some times have 1-2 sound mute, but it better then disconect, thank you, now i can stop on your rom :fingers-crossed:
[Xperia Z3 Compact Original Android Development] okij:
[MENTION=4675360]tomascus[/MENTION]: What's the changelog for your 08-02 build? Are there any changes compared to [MENTION=4901061]mcgi5sr2[/MENTION]'s test build from the day before?
[Xperia Z3 Compact Original Android Development] difto:
As far as I can tell 08/02 doesn't have data drop issues
[Xperia Z3 Compact Original Android Development] tomascus:
Had issues last minute and decided not to release it, hence why you don't see me announcing it or anything.

Anyway, my touchscreen partially broke a few weeks ago, rendering the navigation bar and most of the top portion to not respond to touch, so........

I bought a HTC U11 instead.

My dad will be using my Z3C until his phone come back from repairs and so until then development will be quite slow. But yes, it will continue. Z3C will then purely be my development device.

I'll endeavour to upload the 3AM reboot fix tomorrow hopefully.

Besides the data reconnection issue and bluetooth (which I can't seem to solve), everything seems good to go for official I think....
[Xperia Z3 Compact Original Android Development] okij:
As I wrote yesterday, BT de-/reconnections have stopped at least for me.

It would be good to get some more feedback from other users if BT works flawlessly for them or if there are still problems.

Congrats to your new phone! :cool: And thanks a ton for all you did for the Z3c development and that you will continue to support it. :good:
[Xperia Z3 Compact Original Android Development] :
Well [MENTION=4675360]tomascus[/MENTION] you did it,my headphones are not disconnecting anymore from Bluetooth,mobile data works fine now.

Thank you for the amazing development of yours,you are truly amazing. You basically got my phone back to the state it should've been when it was running KitKat.

Everything is smooth,fast,battery life is great and now I cannot leave this ROM,until stable Android O comes to the Z3c I am staying here on this ROM.

And hope you enjoy your new HTC U 11,heard great reviews about it.
[Xperia Z3 Compact Original Android Development] baudbox:
Done for "Bluetooth MIDI service". Will report later if workaround works.

Note: but I can receive my notification during this time. I guess that it's not completely broken

***

Edit: nope workaround doesn't work. I need to wait until the next release then :)
[Xperia Z3 Compact Original Android Development] devil188:
[MENTION=6164641]baudbox[/MENTION]

Yo dude did you get Magisk to work? It's green for me, but I can't enable Root Access in dev options

#edit: nvm, gotta activate it inside magisk manager
[Xperia Z3 Compact Original Android Development] baudbox:
[MENTION=4862290]devil188[/MENTION]

Yes working fine with Magisk 11.6
[Xperia Z3 Compact Original Android Development] devil188:
CTS safety working for ya?
[Xperia Z3 Compact Original Android Development] baudbox:
Nope
[Xperia Z3 Compact Original Android Development] cattolicboy:
Flashtool

Some suggestions to make flashtool work with Windows 10 (if you don't want to use XP): it is a combination of partial and permanent solution and for me is the only way to have the drivers working.

A)

Uninstall the old version of flashtool (possibly with a software like Revo Uninstaller to delete every traces of the program).

B)

Step 1. Enter Troubleshoot.

There are many ways to get into Troubleshoot. In Windows 10/8.1/8, you can click “Restart” from the power options menu or the Start menu and hold down the “Shift” key at the same time. Once the computer has rebooted, you will be able to choose the Troubleshoot option. Or you can try Windows key + R to bring up the Run box, try shutdown/r/o and hit Enter, click “Close” to sign off and then you can choose the Troubleshoot option when the computer has rebooted.

Step 2. Select “Advanced options” and “Startup Settings”.

Step 3. You need to restart you computer one last time to modify boot time configuration settings.

Step 4. You will be given a list of startup settings, including “Disable driver signature enforcement”. To choose the setting, you need to press F7 key.

C)

Click start, and type gpedit.msc

ENABLE the option for code signed drivers at:

User Config/Admin Templ./System/Driver installation

then set the drop box to "Ignore".

D)

1. Open the Command Prompt window by clicking the Start button, clicking All Programs, clicking Accessories, and then Right clicking Command Prompt and select "Run as Administrator".

2. On the Command Prompt type in the command “Bcdedit.exe /set nointegritychecks ON” without the quotes.

E)

Install last version of flashtool.

Install the drivers inside the folder and choose theese 3: flashtool, fastboot and the ones for z3c

F)

Restart your pc and flash your .291 ftf
[Xperia Z3 Compact Original Android Development] Cirra92:
Can anyone using OpenGapps (Nano package) check CPU usage? I am having more than 70% CPU usage even when device is idling with screen on. BBS shows "com.google.android.gms" usage for 50% of the time, so I suspect it is the cause.

So far CPU is at max freq for more than 50% of the time on battery which is just killing the battery and making the device hot.
[Xperia Z3 Compact Original Android Development] Pisiont:
I'm installing gapps in a minute so I'll let you know. CPU constantly running at high speed was always problem for me on Nougat ROMs, seems to work better here, but I don't have gapps yet
[Xperia Z3 Compact Original Android Development] Cirra92:
While I understand such process has to run constantly, in order for apps to get notifications through it, I don't remember that it was that high on stock for example, and CPU usage is damn high and it just causing too much drain. Maybe it's not GApps though, but something is making CPU load high, and after 3 clean flashes, it's still the same.
[Xperia Z3 Compact Original Android Development] snaky90:
What TWRP version use to flash the latest build ? With russel5 version twrp 3.1.0 flash fine but bootloop
[Xperia Z3 Compact Original Android Development] dalekesi:
I'm stuck on boot animation, any help? I followed instructions from op with recovery link from page 5. My device is D5833, thanks.
[Xperia Z3 Compact Original Android Development] snaky90:
Same problem here with D5803
[Xperia Z3 Compact Original Android Development] Cirra92:
I used 3.0.2-1, but I was on latest bootloader as last ROM I flashed through TWRP was .291, if that has any influence.
[Xperia Z3 Compact Original Android Development] vooR9er:
I will not lie but the System I have loaded about 20 minutes and maybe longer.
[Xperia Z3 Compact Original Android Development] tomascus:
Guys try download this one: https://twrp.me/devices/sonyxperiaz3compact.html in the download link section

fastboot flash FOTAKernel twrp-3.x.x.img

power button + volume down to access.

If that doesn't work, might need clean flash of .291 first
[Xperia Z3 Compact Original Android Development] dalekesi:
Yes with 3.0.2-1 from twrp.me works, thanks
[Xperia Z3 Compact Original Android Development] Cirra92:
Wtf is this? Wifi scanning is off, I have never seen this, 26 alarms per hour is just too much.