yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Original Android Development] optimumpro:
You should do logcat through adb. In Windows you must install adb drivers first. In Linux you are all set. Type adb shell on computer; it should start adb daemon and say waiting for device. Turn on your phone and connect it to usb. Once you get adb shell (on computer) type adb logcat and you will have logcat on screen...
[Xperia Z3 Original Android Development] xz123:
Thanks – but that's what I already did, and adb remains just "waiting for device".

adb works during normal operation, fastboot works, adb in twrp works, but it does not work at the point during boot at which it hangs.

In the same vein, LiveBoot doesn't help, too, because it seems like the issue is before that could start, too.

That's what I meant with not being able to get a logcat.

I've actually even tried modifying my init.rc as mentioned in my last post to get some early logging this way by un- and repacking the boot.img, but after flashing the modified boot.img something seems to be quite wrong (only getting a red flashing LED) – which is fortunately easy to fix by flashing your original boot.img again.

So I'm somewhat out of ideas.
[Xperia Z3 Original Android Development] optimumpro:
If the fault occurs that early, that means something in kernel won't allow execution - most likely one of October's kernel patches. In order to have another kernel working with Jaguar, you have to put ramdisk from Jaguar into another kernel and repack it. The entire ramdisk, because if you mess with files inside, the phone won't boot. Also, there isn't any other kernel for LP 5.1.1 that is up-to-date with security patches. Another way is to use UART socket on the phone, but that's pain: removing back cover, soldering etc....
[Xperia Z3 Original Android Development] xz123:
Thanks – I'd prefer sticking with your kernel, though. (I like the security aspect of your ROM/Kernel, so opting for another one wouldn't be an option)

If I had SMD-soldering equipment I'd go with the UART option, but unfortunately I haven't.

Have you, in the meantime, decided on whether to include signature spoofing or not? Maybe you could not enable it by default but make it an option hidden in the dev menu instead or something like that? That's my main reason for using Xposed, so if that was included I'd not require Xposed anyway.
[Xperia Z3 Original Android Development] blackhawk_LA:
I had to leave this ROM because I don't feel confident enough that the alarm will sound in time. I always put the phone in airplane mode at night, so if it reboots itself or (more probably, as it actually happen lol) I reboot it and forget to set time, I won't wake up in time. I know it's my fault, but is there any not difficult way to reenable qc time services? Thank you! I really like this ROM...
[Xperia Z3 Original Android Development] optimumpro:
First, If it reboots by itself, you need to adjust kerneladiutor settings. Don't reduce voltages, as this is the main reason for self-reboots. Plus, there is zero benefit from reducing current to CPU. None. Instead, try to go up 20-25 from default. Second, if you set time/zone on automatic (from your carrier), you get the time always on reboot. Airplane mode does not change the time, unless you reboot the phone in airplane mode, which there is no reason to do. Even on a release with Qcomm time services enabled, if you reboot the phone in airplane mode, you won't have the correct time until you turn it off...
[Xperia Z3 Original Android Development] blackhawk_LA:
Thanks for your answer. Actually, my z3 has never rebooted itself in the eight months I'm having it. But you know, Murphy is waiting at the corner... :silly:

I think I can try and live with the ROM as it is, but I don't understand all that you've said. What is the reason why this ROM resets date and time on every reboot (if it's not set to automatic-from network) I thought that this was the result of disabling qc time services. Just out of curiosity.

Thank you again for your work and time!
[Xperia Z3 Original Android Development] optimumpro:
Most smart phones, including Sony, don't have RTC (real time clock), so, qualcom time service connects to some server through a cell modem on very early boot and sets the time before the phone is fully booted. No one knows what else this service does, but it is dependent on Android running the daemon. That's why if you shut down the daemon, there is no connection and no time setting. Without the daemon, the time is set when your simcard is registered with the tower. Anyway, unless you are in an airplane mode, the time is set before you get image on your screen.
[Xperia Z3 Original Android Development] blackhawk_LA:
Anyone else facing the screen flickering issue? I can see it when screen brightness is at the minimum, and is more noticeable on white backgrounds.

I've attached logs to see if it can help

http://cloud.tapatalk.com/s/582100c59458f/Log_1972-02-21_10-34-16.txt

http://cloud.tapatalk.com/s/5821011cba476/kmsg.txt
[Xperia Z3 Original Android Development] optimumpro:
This happens on after-market displays. Just don't set brightness to the lowest. I have had 3 after-market displays and they all had different issues until I bought a broken down phone (water damage) with OEM display that still had a badly scratched Sony screen protector. I removed it and the LCD now looks (and works) like brand new...
[Xperia Z3 Original Android Development] blackhawk_LA:
But my screen has never been replaced. I've always read about Sony using different panels on their phones, so maybe mine is one of the "strange" ones.
[Xperia Z3 Original Android Development] optimumpro:
I will adjust brightness up a bit in the next release...
[Xperia Z3 Original Android Development] CCody:
Working good so far. But everytime I go to Google Keyboard settings and select one of the options provided, Google Keyboard is crashing. Does this caused due to me flashing GApps?

Also I also notice screenflickering, but only after the devices dims the brightness after some time of inactivity.
[Xperia Z3 Original Android Development] optimumpro:
As it says in the OP, some Gapps cause Aosp/Google keyboard to crash. So, either use another Gapps package or get a third party keyboard.

Regarding brightness: have you read 1-2 posts above? Don't set the brightness to the lowest, as it causes flickering on some display panels. I will adjust brightness upward in the next release...
[Xperia Z3 Original Android Development] CCody:
Thanks for your input. Now I want to install Xperia Keyboard (http://xdaforums.com/android/apps-games/app-sony-xperia-keyboard-phones-t3346736), but it says 'App is not installed'.

Never mind. I got it! ^~^
[Xperia Z3 Original Android Development] optimumpro:
New Build

Rom updated to include November Security Patches. See post #3 for download...
[Xperia Z3 Original Android Development] Omessy7:
hey mate, great work keep it up!

one small request if i may, coming up with a modem patch to enable SIM data/calls on the dual variant D6633.

Thanks
[Xperia Z3 Original Android Development] CCody:
Can we flash this without data loss?
[Xperia Z3 Original Android Development] optimumpro:
Yes, but only on top of a previous Jaguar release.

You can flash Z3 dual modem patch in TWRP. Search on XDA...
[Xperia Z3 Original Android Development] Omessy7:
i flashed one...i booted but no SIM detected, i installed the AFwall app and activated... no luck,also my recovery was gone, if i try to go to it LED turns orange and it reboots
[Xperia Z3 Original Android Development] optimumpro:
Baseband/sim detection has nothing to do with afwall. Jaguar doesn't have recovery, nor does it touch recovery partition. So, whatever you had there should be there. I an not familiar with modem patch for Z3, but there is a similar modem for Z1 non Lte device which works fine. Try the modem patch for LP.
[Xperia Z3 Original Android Development] Omessy7:
i have tried 2 but no luck. it's just that thing otherwise its easily a solid daily driver ROM.
[Xperia Z3 Original Android Development] TechnoFreak750:
I need to change modem for this aosp.. I have a stock firmware modem.mbn file.. How can i use that modem on aosp?? Any suggestion?? Because in stock rom there is a modem switcher app to switch modems.. How can i switch modem in jaguar?
[Xperia Z3 Original Android Development] optimumpro:
AOSP roms don't have modem switch, but whatever you switched to on stock should stick in AOSP.
[Xperia Z3 Original Android Development] TechnoFreak750:
even if i install modem switcher from stock ftf, it recognises modem files from system/etc/customisations/modems/modem.mbn

but in AOSP modem is located in system/***/firmware/modem.b00

so it wont actually switch the modem.. logically..

any other help is welcomed.
[Xperia Z3 Original Android Development] optimumpro:
I wasn't talking about installing modem switcher onto a custom rom: it would simply not work. But if you change modem while on stock, the change should stick on a custom rom.

I have a question: why do you need to change modem when you go from stock to custom rom?
[Xperia Z3 Original Android Development] TechnoFreak750:
Since the custom rom flashes its own modem whenever it is installed.. means no VoLTE on other modems.. :( my carrier reliance jio supports a specific modem, which is present in stock rom.. But unfortunately not in any custom/aosp/cm based rom. It shows VoLTE on stock rom but wherever i flash jaguar (which i like the most), VoLTE doesn't work... :(
[Xperia Z3 Original Android Development] optimumpro:
Have you ever made a successful call on stock Volte? The main modem is located on a separate partition that is not touched by any custom rom. There are modem support files in /etc/... that may or may not prevent Volte calls.
[Xperia Z3 Original Android Development] TechnoFreak750:
yes I did make volte calls on stock lollipop and marshmallow.. http://xdaforums.com/crossdevice-dev/sony/enabling-volte-xperia-z2-xperia-z3-t3438505 this thread contains the procedure, including the flashable zip to enable volte.
[Xperia Z3 Original Android Development] xz123:
[MENTION=5075064]optimumpro[/MENTION]: would you consider including an optional signature spoofing, like omnirom did?

Maybe it could even be improved upon so you could choose to only allow spoofing for specific apps, but with my almost nonexistant understanding of Android programming I can't (easily) help with that (yet).
[Xperia Z3 Original Android Development] blackhawk_LA:
[MENTION=5075064]optimumpro[/MENTION], do you think you could include [MENTION=6979267]nailyk[/MENTION] fix for screen flickering (http://xdaforums.com/showthread.php?p=69804486) in future releases? It's done for Nougat and I don't know if it's possible to add/port to Lollipop. Thanks anyway for your ROM!
[Xperia Z3 Original Android Development] optimumpro:
It is done already, will be included in December release

Those values are in 3.4 kernel anyway. I will increase minimal brightness from 10 to 15, which should fix flickering
[Xperia Z3 Original Android Development] blackhawk_LA:
I had screen flickering on official CM12.1 as well as on every non Sony rom. Maybe it's not only because of the lower brightness value?
[Xperia Z3 Original Android Development] optimumpro:
CM12.1 has 10 as the lowest brightness value, which is low for some panel varieties.. Keep in mind that the Nougat fix is not a fix at all: when switching branches, Jerplea & Co, forgot to transfer the correct values. Now, someone else did. Unfortunately, they keep creating new bugs with each new branch...
[Xperia Z3 Original Android Development] optimumpro:
New Build

Rom updated. See post #3 for download and description...
[Xperia Z3 Original Android Development] blackhawk_LA:
Thank you very much. I don't see anything related to screen brightness in changelog. I really want to use this rom but I'm afraid that screen flickering could end up affecting display lifespan.
[Xperia Z3 Original Android Development] optimumpro:
The brightness changes were in, but they were put in between compilation for Z3 and Z3c. In other words, one build has the changes, the other - doesn't and I don't remember which one...

Anyway, if you use automatic brightness, don't go below 1/3 of the scale and you shouldn't have any flickering...
[Xperia Z3 Original Android Development] blackhawk_LA:
Haha ok, I will flash tomorrow and report. Thank you!

Edited: tried and screen flickering is still present, also I'd say that minimum brightness is the same very Iow brightness as the old version, so the changes might have been made only in z3c
[Xperia Z3 Original Android Development] CCody:
What should I do if I just want to flash the new updates, but don't want to lose any apps/data? Also to make updates easier, are there any thoughts about OTA updates or some other "one-click-updater"?
[Xperia Z3 Original Android Development] optimumpro:
You should just flash dirty (without wiping data partition). Full wipe is required when you are coming from a different rom. OTA requires a server that costs money...
[Xperia Z3 Original Android Development] jerchi:
Would there be a reason as to why Cyberian Camera does not work. After flashing it through twrp, it says 'Optimizing app x of xx.' and then proceeds to get stuck on 'Starting apps.'

Was just trying to see if I could fix the odd fisheye issue with the camera. :p
[Xperia Z3 Original Android Development] CCody:
Now after updating to Dezember patches, SuperSU doesnt work anymore. It won't update the binaries. That also means no internet access, since AFWall can't operate without root. What should I do?
[Xperia Z3 Original Android Development] optimumpro:
Supersu is no longer included. Enable root in Developer settings. If you installed Supersu as a normal app, it won't have root until enabled. So, flash Supersu zip separately.

Camera: you won't fix eyefish effect by changing an app. And Cyberian camera is for stock roms.
[Xperia Z3 Original Android Development] kakobr:
This ROM is very good, but I have not adapted to some things... Can Qualcomm's Time Services be re-enabled? And use the Internet without Afwall?

I don't use mobile data, and when I'm out of my house and have to restart the device, I get the wrong time :(
[Xperia Z3 Original Android Development] optimumpro:
Enabling time services triggers a complete rebuild of the rom. If you are set to have time automatically from your carrier, you don't need data, as it is done through gsm channel via modem.

If you don't want Afwall, you need to use a file manager with root rights and delete the crashdod file in /system/etc. Reboot and you are done...

I will rebuild and post the rom with new brightness values...
[Xperia Z3 Original Android Development] optimumpro:
New build only for those with a display that has flickering on low brightness. Download in post #3.
[Xperia Z3 Original Android Development] blackhawk_LA:
I'm sorry but the screen flickering is still present. I have attached a logcat and dmesg in case it's useful. http://cloud.tapatalk.com/s/5851b388e8743/Log-2016-12-14-09.14.51.csv.txt

http://cloud.tapatalk.com/s/5851b3b251de8/Log-2016-12-14-09.15.08.csv.txt

Thank you.
[Xperia Z3 Original Android Development] optimumpro:
Try the attached kernel and report. Unzip the file and flash in fastboot: fastboot flash boot boot.img. Then reboot...
[Xperia Z3 Original Android Development] blackhawk_LA:
Withb this kernel the screen is black all the time; I can't even see the sony logo or bootanimation, but the phone boots. I've tried to get a logcat or dmesg from adb but it says operation not permited, although I have enabled and authorized adb and root in development settings.
[Xperia Z3 Original Android Development] optimumpro:
Then unfortunately this 3.10 kernel fix is incompatible with 3.4 kernel. The flickering only affects Novatek Auo displays. I don't have Z3 and can't experiment. Perhaps [MENTION=6979267]nailyk[/MENTION] can take a look at 3.4 kernel and make changes. The relevant file is in /arch/arm/boot/dts/dsi-panel-leo.dtsi...
[Xperia Z3 Original Android Development] blackhawk_LA:
Too bad :( I wanted to use this ROM but the brightness level I have to set to not have flickering is very high and hurts my eyes in dark environments.

Thank for all your efforts!
[Xperia Z3 Original Android Development] nimblemike:
I've got a similar problem - with the xposed framework flashed I also get a bootloop. I've been able to get logcat to work. It seems with xposed, the bootloop start with AudioFlinger dieing and then Netd continually restarting. Looking up in the log, there are a few items in the log that are missing with xposed flashed. For instanced I don't see these lines at all with xposed:

[FONT="Fixedsys"]I/AudioFlinger( 431): loadHwModule() Loaded primary audio interface from QCOM Audio HAL (audio) handle 1
D/audio_hw_primary( 431): adev_open_output_stream: enter: sample_rate(48000) channel_mask(0x3) devices(0x2) flags(0x2) stream_handle(0xb5880c40)
D/audio_hw_primary( 431): adev_open_output_stream: Stream (0xb5880c40) picks up usecase (low-latency-playback)
I/AudioFlinger( 431): HAL output buffer size 240 frames, normal sink buffer size 960 frames
I/AudioMixer( 431): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project[/FONT]

The xposed flash log is also contains no entries referring to the NatController, MediaPlayerFactory, and libcameralight.

I'm not sure if it is the patches. I've tried all of your Z3 images from October onward with a combination of versions 85-87 of the 32bit, sdk22 xposed. It seems the same thing happens no matter the version. The hardware is a single sim Z3. I'm not exactly sure why this is occurring.

Other than incompatibility with xposed, this ROM is quite excellent. I'd like to get it working with xposed. Do you have any thoughts on where to start looking for a work around?
[Xperia Z3 Original Android Development] Nekser1208:
I downloaded this: http://xdaforums.com/devdb/project/dl/?id=22108

I installed according to: Instructions:

1. Be on LP at least, have TWRP, unlocked bootloader and root

2. In TWRP, wipe data / factory reset, then wipe System / Data / Cache / Dalvik

3. Flash the rom

4. If you use Xposed, flash the latest installer

5. Reboot and install Afwall Kernel Adiutor as normal apps; activate Afwall to have Internet

6. Enjoy the rom, say thank you, or donate to both

And the phone stops at the logo "Xperia". Any ideas why?

A and can not enter the "recovery".

---------- Post added at 02:40 PM ---------- Previous post was at 01:48 PM ----------

Edit: Xposed causes bootloop ;)

---------- Post added at 02:43 PM ---------- Previous post was at 02:40 PM ----------

TWRP don't work :(
[Xperia Z3 Original Android Development] optimumpro:
Jaguar requires a special version of Twrp that pulls in all libs required for decrypting. I only built ones for Xperia Z1 and Z1c. I hope I would be able to build the same for Z2 and Z3 in January.

Jaguar has quite a few security related commits from Nougat. One of them no longer allows opening of the same jar file more than once at the same time. Xposed uses this loophole in LP and MM. That is why there is no Xposed for Nougat. Hence the boot loop. Use builtin privacy guard instead...
[Xperia Z3 Original Android Development] nimblemike:
I appreciate the work you're doing here. I think your approach - hardening the build - is far better than just using privacy guard. I suppose I should have read the Z1 Jaguar thread - that would have saved me the afternoon trying to get Xposed to work :o. You may want to change your instructions though - one of the step implies that at least one of your posted Z3 builds supports Xposed. I don't think any do.

As for the recovery - I'm pretty sure this one by nailyk supports decryption: http://xdaforums.com/z3/development/z3-twrp-2-8-7-0-d6603-t3273996

That recovery worked fine for me with installing Jaguar, though I've only tried encryption/decryption on a CM ROM.
[Xperia Z3 Original Android Development] Nekser1208:
I downloaded a recovery from here: http://nut.xperia-files.com/ and works without any errors. ;)

Rom works on the event very well. Keep it up.

Regards , Marek.
[Xperia Z3 Original Android Development] optimumpro:
Nailyk's TWRP supports vanilla Android encryption, which uses 128 bit CBS. Jaguar has 256 bit. That's why you need a special TWRP that supports 256 bit. But even if your data is encrypted, you can still update to newer Jaguar versions with a standard TWRP. Just enter recovery and press 'Cancel' when asked for password. Then you can flash the rom... But if you want to change roms, you'll have to format everything including data...
[Xperia Z3 Original Android Development] Nekser1208:
Doesn't function copy / paste. :(
[Xperia Z3 Original Android Development] optimumpro:
Enable background access to clipboard in Developer settings...
[Xperia Z3 Original Android Development] optimumpro:
TWRP 3.0.2 able to decrypt data posted

This is TWRP for Jaguar. It should work with your encrypted data partition. See post #3 for download...
[Xperia Z3 Original Android Development] Nekser1208:
Security=> Allow background clipboard access ?

Work! THX

And in Polish language doesn't work "sieci komórkowe" Cellular networks but in English (US) work perfectly. ;)
[Xperia Z3 Original Android Development] optimumpro:
You need to make changes in English and then switch to Polish: the changes will hold...
[Xperia Z3 Original Android Development] frabe8378910:
Considering a test of jaguar on my Z3 now. I maintain a second Z3 for my wife and I try to always keep them on the same ROM and so on. I'm running still the latest CM12.1 nighly (20161016) on both and so far I always went back to CM for several reasons. I have tested some ROMs based Android 6 + a few on Android 7 for my Z3 and a Z5, but in terms of stability and usability I still consider CM12.1 (so LL) the best platform.

So I really appreciate your Android base decision.

But there is one point, that drives me... and I know the questions is not predictable to answer, but anyway...

a) What is your planned time frame to support your ROM on Z3?

b) Will you in the near future switch to Android 6, 7 or whatever risking a lot of core features not working any more?

Thanks.
[Xperia Z3 Original Android Development] optimumpro:
"The latest CM": While CM Android LP 5.1.1 contains some 10-12 commits (as opposed to hundreds implemented by Google and Code Aurora), https://review.cyanogenmod.org/#/q/cm12.1 its kernel has been totally abandoned since February 2016 https://github.com/CyanogenMod/android_kernel_sony_msm8974/tree/cm-12.1. So, the only real thing that CM updated is the build date...

I am going to continue to update Z1-Z3, as long as I have Xperia Z1. And I have no plans to upgrade in the next few years...
[Xperia Z3 Original Android Development] frabe8378910:
Yes, I knew that. But in respect to usability, stability and stuff like OTA, theme engine (drive everything dark) it was the best daily for me and before you throw Jaguar an the Z3 market I didn't knew valuable alternatives. Stock is NOT an option for me. And most important to mention: For some time there was a high chance to get the same OS/ROM for a different device only with CM, because they had the broadest device support.

:good::good: I'm still using my Xperia Z for MTB tours or Gym. And if there ever will be a usable CM, Jaguar :D, whatever ROM for my Z5, then the Z5 will the daily and the Z3 my sports phone. :D:D