Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by ddark-il

  1. 11 minutes ago, FlyingAntero said:

    I started to think about a new scenario that maybe WiFi 2.4G issue is related to assumed network issue.

    Don't think so. In my case I was never connected to WiFi, during the reboot.

    The theory with energy spike causing reboot seems more plausible, I have dual-sim with multiple mail and messenger accounts always syncing.

    • Like 2

  2. It is known bug on few devices. I got wierd way to replicate it - it always reboots on specific train. Already sent bugreport data to Waxberry.

    If it's too annoyingfor you, you can revert to OTA version before SafetyNet(can't remember the exact build, but it was ~8MB), it still reboots, but much less.


    • Thanks 2

  3. On 1/24/2020 at 8:04 PM, MickH said:

    For some reason my Pro1 shut itself down 3 times in a row today.
    I was out shopping and glanced at my phone to see the time. When I pressed the power button I was asked for the boot-up unlock code. After that the phone booted OK.
    Within half an hour the same thing happened another 2 times.

    Any Ideas?

    Are you using it dual sim?

    Does it happened in low reception/coverage area?

    Do you got some of Google Apps disabled?

    Do you got some app that frequently checks location?


    Those are just guesses..

  4. On 12/26/2019 at 11:42 PM, silversolver said:

    VoLTE is turned off by default on the phone. Try *#*#4636#*#* and flip all the switches and reboot.

    Please let us know if this makes VoLTE work so others can know. Also, it sounds hairy over there. Stay safe!

    Switches are greyed out  😞

    • Like 1

  5. Israel:

    Pelephone - LTE/WCDMA network (No VoLTE)

    Partner (ex Orange)  - Global network (No VoLTE)

    Need to try the mule method.


    Roaming at Netherlands worked flawlessly for both SIMs, can't remember the networks.

    • Thanks 1

  6. 8 minutes ago, EskeRahn said:

    if you pull a plastic BT keyboard from one pocket and a budget phone from the other

    Also it's not always possible to pull both keyboard and a phone.

    I've worked on client's servers while being on the bus to airport, there is no way that I would manage to perform it with bluetooth keyboard.

    • Like 2

  7. 53 minutes ago, cerialphreak said:

    If you have a chance could you switch the Bluetooth profile to AAC in developer options and try connecting to the Sonys again? The specs on Sonys website say they support that codec and I'm curious to see if the issue is limited to aptx.

    Tried that, also with LDAC and other AptX variations, it's either falls back to SBC or got no sound at all.

    But I still haven't seen confirmation that someone else got same behavior, so it might be limited only to my case.

  8. 29 minutes ago, EskeRahn said:

    Nice review!

    On the vignetting thing. It seems to be limited to the Google app in your examples. So I guess that means the Qualcomm app are compensating by boosting the brightness of the corners? Just did a quick test here with "OpenCamera" versus Qualcomm's and I see the same.

    Edit: I confused the labels as below not above the images, DOH


    There is also what i assume is a 'calibration' issues in the Camera2 API. If you do HDR in OpenCamera the stitching gets the brightness levels wrong, leaving a dark 'halo' around a bright subject. It is hardly a bug in OpenCamera as their HDR works fine on e.g. Samsung S8-. My GUESS is that when the camera via the API is requested to do an image with specific parameter variation, they are handled slightly incorrect, so when the app try to brighten/darken as would match their parameters to do the stich, it fails to give the correct result. My guess would be a bug with handling a parameter as linear/logarithmic. That is e.g. is 25% increase in some parameter 1.25 or 2^0.25=1.19...

    The image below is on a slightly older software, but it is the same bug. Best seen in very bright sunlight, and well not much of that in this wet autumn in Denmark


     I see it on both apps, hope that you're right, and it's only a software calibration issue, other than that the camera quality is really good.

  • Create New...

Important Information