Forwarded from vx-underground
The new check mark system has resulted in Threat Actors successfully impersonating Twitter and defrauding users out of money
Although the account is now suspended, it rapidly got 35,000+ retweets and 4,990 likes.
A simple $8 investment can result in thousands of dollars stolen.
Although the account is now suspended, it rapidly got 35,000+ retweets and 4,990 likes.
A simple $8 investment can result in thousands of dollars stolen.
👍6
https://news.1rj.ru/str/MishaalAndroidNews/68
Enjoy what comes next:
Threat actors sign whatever they want and are understandably uninterested in helping you to install custom high level software and firmware on normally non-unlockable device, they instead want you on unpatched stock ROM.
OEMs are uninterested in releasing absolutely needed patches to EOL devices that are still in use, while being also uninterested in releasing tools and/or suitable update that would let you unlock their bootloader.
The way things are, both the threat actors and OEMs remain happy, as exclusivity of leaked keys ensures that there won't be as many rogue-signed apps as there could be otherwise, in result putting a smaller pressure on OEMs to act and to change their security support policies, while threat actors will certainly be glad that more devices remain unpatched.
Best part? The same is applicable to every private exploit possible. The only difference is that a private exploit can be reverse engineered if the exploit binary didn't get purged from device in time. The rest stays the same: threat actors don't want to get any competitors, public awareness of the vulnerability and especially they don't want to see widely available security patches.
Enjoy what comes next:
Threat actors sign whatever they want and are understandably uninterested in helping you to install custom high level software and firmware on normally non-unlockable device, they instead want you on unpatched stock ROM.
OEMs are uninterested in releasing absolutely needed patches to EOL devices that are still in use, while being also uninterested in releasing tools and/or suitable update that would let you unlock their bootloader.
The way things are, both the threat actors and OEMs remain happy, as exclusivity of leaked keys ensures that there won't be as many rogue-signed apps as there could be otherwise, in result putting a smaller pressure on OEMs to act and to change their security support policies, while threat actors will certainly be glad that more devices remain unpatched.
Best part? The same is applicable to every private exploit possible. The only difference is that a private exploit can be reverse engineered if the exploit binary didn't get purged from device in time. The rest stays the same: threat actors don't want to get any competitors, public awareness of the vulnerability and especially they don't want to see widely available security patches.
Telegram
Mishaal's Android News Feed
Okay, so what are the immediate implications/takeaways for users?
- You can't trust that an app has been signed by the legitimate vendor/OEM if their platform certificate was leaked. Do not sideload those apps from third-party sites/outside of Google Play…
- You can't trust that an app has been signed by the legitimate vendor/OEM if their platform certificate was leaked. Do not sideload those apps from third-party sites/outside of Google Play…
Durov says that the highly non-contextual, often foreign language, cheap looking ads you rarely see made more money than 1+ million premium subscribers. I have doubts.
https://news.1rj.ru/str/durov/203
https://news.1rj.ru/str/durov/203
😁2
The leaks were right. This is a real phone.
https://fdn.gsmarena.com/imgroot/reviews/22/tecno-phantom-x2-pro/lifestyle/gsmarena_021.jpg
https://fdn.gsmarena.com/imgroot/reviews/22/tecno-phantom-x2-pro/lifestyle/gsmarena_021.jpg
👍3
Tadi Channel
Dear Tecno, you're now on my pantheon right after Mate X2 and S20, S21 high res modes, congrats! You may be even unaware that your results beat so many biggest OEMs around. https://fdn.gsmarena.com/imgroot/reviews/22/tecno-camon-19-pro/camera/gsmarena_013.jpg
And despite the ridiculously (and unnecessarily) huge camera island, they regressed
😁2
Tadi Channel
And despite the ridiculously (and unnecessarily) huge camera island, they regressed
It's worth noting that they forgot to regress on the full res processing of tele camera, which probably isn't the best in the optical area (despite the impressive aperture diameter), but still not as bad to not benefit from less destruction. Sharpening of the binned mode functions as a censorship of not so great demosaicing, but in result ruins the natural micro contrast, adds a few artifacts and clearly makes thin lines thicker.
👍3
Tadi Channel
Looks like devices with support for SCALER_STREAM_CONFIGURATION_MAP_MAXIMUM_RESOLUTION are finally starting to pop up. The device in the screenshot is Axon 40 Ultra.
Also there on Vivo X90 Pro+. The frame duration visible here correctly translates to 15 fps, as the only high-res sensor mode at 30 fps they implemented is direct 8k which they didn't expose, at least as a raw stream.
A big part of why these tables finally start being populated is because Qualcomm already implemented them in camera HAL for the recent SoCs. It's likely that their reference designs offer high res streams out of the box now with 0 code changes.
A big part of why these tables finally start being populated is because Qualcomm already implemented them in camera HAL for the recent SoCs. It's likely that their reference designs offer high res streams out of the box now with 0 code changes.
👍5
In 2016, XDA came with the idea of a brightness flashlight API dependant on a blob. Well, in 2022, "thanks" to GRF, this is exactly a thing that won't come to most of existing Android devices running their stock vendor image. If you're on Android 13, just try this app:
Forwarded from Google News | En
Flashlight Tiramisu.apk
2.4 MB
Android 13 flashlight brightness adjustment app for Pixel 6, 6 Pro and 6a. (and Galaxy S22 on One UI 5 beta)
Features:
• You can add a "Brightness control" tile to the quick settings for easy access;
• Support for dynamic colors and themed icon;
• Support for predictive back gesture;
• Demo;
You can't install this app on earlier Android versions.
Thanks to @polodarb for the build.
Google News | En
Features:
• You can add a "Brightness control" tile to the quick settings for easy access;
• Support for dynamic colors and themed icon;
• Support for predictive back gesture;
• Demo;
You can't install this app on earlier Android versions.
Thanks to @polodarb for the build.
Google News | En
❤2👍1
As media directly copied the imprecise claims of my friend on what staggered HDR actually is, let me correct it:
Typical sensor capture process works in a way that as long as your exposures are short, the integration (exposure start) of next frame won't happen any sooner than than the cycle of next frame, which basically starts when each of the sensor lines start integration, top to bottom. So for a sensor in 30 fps mode, it won't matter if your exposure time is 1/800s or 1/40s, you won't be able to capture more frames just because their exposure time is short.
Staggered HDR changes that. A sensor in such mode is able to have more than one ongoing integration start at a time, as long as a given line already stopped integration for the previous frame. This is better than bracketing typically is, as it lets the frames represent a narrower range of time. But it's really not a perfect timing match, the frames won't represent the same exact moment in time. To achieve that, you still need to rely on either dual...
Typical sensor capture process works in a way that as long as your exposures are short, the integration (exposure start) of next frame won't happen any sooner than than the cycle of next frame, which basically starts when each of the sensor lines start integration, top to bottom. So for a sensor in 30 fps mode, it won't matter if your exposure time is 1/800s or 1/40s, you won't be able to capture more frames just because their exposure time is short.
Staggered HDR changes that. A sensor in such mode is able to have more than one ongoing integration start at a time, as long as a given line already stopped integration for the previous frame. This is better than bracketing typically is, as it lets the frames represent a narrower range of time. But it's really not a perfect timing match, the frames won't represent the same exact moment in time. To achieve that, you still need to rely on either dual...
👍4
Tadi Channel
As media directly copied the imprecise claims of my friend on what staggered HDR actually is, let me correct it: Typical sensor capture process works in a way that as long as your exposures are short, the integration (exposure start) of next frame won't happen…
/triple conversion gain merge or gain-based QHDR (or Nona, Hexa etc. equivalent of it). It's a good moment to remind of the Samsung presentation I linked here: https://news.1rj.ru/str/TadiBlog/111
Telegram
Tadi Channel
https://hc33.hotchips.org/assets/program/conference/day2/(Final)Hotchips2021_CIS_Samsung_ISOCELL_GN2.pdf
👍2
A graph I made representing the non-staggered (typical) operation of a sensor. It's a bit idealized, as it skips the blanking time and other margins.
👍2