I don’t think it is relevant: it should happen only when the phone is on.
1Hz is a quite low frequency.
However, what you say may be the reason why the manufacturers don’t display the seconds.
I don’t think it is relevant: it should happen only when the phone is on.
Short update from my side concerning problems with speech recognition:
I had to deactivate the “Android System Intelligence” system app. Afterwards it seems that google engine is again really the default one (as Android SI seems to have been kind of hidden default one).
Now my automate flows work like a charm with other than US English language.
I reported this also to FP support. Hopefully they think about this edge case for the next update.
This is a new Android 12 addition. Google’s Pixel phones use “Google Tensor”, a processor which was initially intended as an accelerator for neural network machine learning (what marketing calls “AI”…).
As a smartphone chip it is rather unremarkable, which is probably the reason Google is injecting heaps of machine learning (“AI”) into Android, to give its processors a competitive edge over the competition…
“Android System Intelligence” is such a solution in search of a problem, sort of super-Clippy which observes 24/7 what you do (collecting all sort of useful marketing knowledge ), and then takes initiatives, doing for you what it thinks you wanted to do (or rather what Google’s marketing thinks you should want to do)…
Unfortunately there is no “artificial intelligence”, there is only natural stupidity, and this will most certainly end in tears…
This data is stored and kept offline, such as quick suggestions for messaging, automatic quick shortcuts, keyboard improvements, adaptive brightness, image processing (until you upload it yourself to the Cloud of course) and many more.
Might be, although Google clearly states that although ASI is local, “Private Compute Services provides a secure bridge to the cloud”. So, apparently ASI does need access to Google’s “cloud” (fluffy name for “servers”), and it does that through PCS (which, having “Private” in its name, is highly suspect!)…
Anyway, whatever it is, Google being Google it is clear they will eventually “monetize” this.
Also, going through the features, besides the automatic translation I don’t see a single feature my Samsung Note 2 didn’t already have (in some form) 15 years ago, except of course some features I’d rather pay not to have, like “suggestions” (I rarely if ever do not know what I was about to do, so I don’t need some dumb Clippy bothering me with its silly remarks).
“Android System Intelligence” is another perfect example of “AI” being mostly hollow, meaningless marketing buzzwords…
The Quickstep Launcher still causes problems. I’m having a hard time believing that these problems are hard to fix. The minimum display brightness is then turned down via update instead of correcting the error.
The launcher still has the problem that the header is displayed in the wrong color if you have previously scrolled down and started an app and then minimized or closed it. Then the header suddenly appears gray instead of black.
similar problem with light mode too. The header is also displayed in the wrong color here.
Darkmode colors are still wrong. white writing on a light blue background is just not legible.
in the bright mode, the contrast is as it should be.
I don’t think it’s rocket science to just match the colors. Please fix the problem! Please! This is your business card and the first impression you make.
I’ve just updated my FP4 to Android 12 FP4.SP21.B.048.20230215 and I’m interested in how you managed to extract the boot.img via recovery. Could you please let me know?
Would it be something like the following?
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img exit adb pull /sdcard/boot.img stock_boot.img
Do I require TWRP installed?
Yes, the commands are fine. I extracted /dev/block/bootdevice/by-name/boot_a and /dev/block/bootdevice/by-name/boot_b just n case. In fastboot mode you can check which is the active slot first to minimize the effort and then boot the TWRP image via fastboot. No need to install the recovery.
Thanks @Lars_Hennig , do I need to boot TWRP at all or will adb shell not work without it?
You need to boot something that has root access in order to access the partition with the boot image. You could also use the recovery image from LineageOS and boot it with fastboot.
Thanks for your help I managed to get TWRP installed and my FP4 rooted with Android 12, all working nicely now.
I hope you didn’t actually flash TWRP, otherwise you’ll have to restore the stock
boot anyway of course) before you’ll be able to install the next OTA.
Keep that in mind if your next update fails.
The latest factory images are already available BTW, no need to mess with TWRP or otherwise
dding partitions from a running system.
I mean it’s a great learning experience, but the
boot.img is right there for the taking
Already installed! Everything works great! Thank you!
I did flash TWRP, I tried a few times to ‘flash boot twrp.img’ but it would just freeze and I would have to hold down VolDown + Power to reboot. Is there a trick to booting TWRP?
Are suggesting I flash the whole stock image on with the following instructions;
No, you don’t need to flash it.
Just download the factory images, extract the archive and the
boot.img you wanted is right there
Can’t help you with TWRP, I don’t use it, sorry.
Since you flashed it, you might want to hold on to the factory images you downloaded, because you will have to flash stock
recovery before you can update to the next OTA.
So I could download the latest FP4 stock Android 12 image, extract it and flash just the recovery to get rid of the TWRP, or should I revert back to the full stock Android 12 image and then try to root it again without flashing TWRP?
You only need to flash
Regardless of what you do now, you’ll also have to follow the OTA update instructions at the bottom of this post, once an update arrives.
This is turning very off topic, for further Magisk related questions please follow up in the dedicated root topic.
Received the update today on KPN in The Netherlands. Update went smooth and no issues so far.
Is there still anyone unfortunate with Android 11 on the phone? I’m talking to support about a behavior change, but I base it just on my gut feeling, so it would be nice to have some hard evidence
What bothers me is that when the phone is in my pocket (i.e. proximity sensor says CLOSE and ambient light sensor says low values) and a notification is received, then the display shows the notification on black background (that’s the same), but on A12 it also activates the touchscreen. My gut feeling is that on A11, this black-background notification screen did not react to touches and I actually had to press the power button to interact with the phone (with the exception of incoming calls and alarm, of course). The easiest way to test this is lock the phone, send an SMS to the locked phone from another phone, and try to touch the screen. Now, take a piece of something non-conductive (e.g. cardboard) and lay it over the top 2cm of the phone so that the proximity and lighting sensors are covered. Repeat the thing with SMS and trying to touch-interact.
I’d be really glad if anyone still on A11 could help me with recording a video (or just telling me my gut feeling is wrong and the touchscreen activated also on A11).
The problem I have with this behavior is that once or twice a day I pull the phone from my pocket with lots of numbers typed to the emergency calling screen. I can’t find any other explanation than this unwanted activation of the touchscreen.
The support told me to disable waking the screen for notifications, which could help, but I want to retain this visual part. I just want to get rid of the interaction part of it.
Are you sure the phone is really locking? And are you sure you dont touch the fingerprint sensor and just unlock the phone? I havent noticed this behaviour I have the phone in my pocket a lot…
Edit: I tested it with A12 as you described and surprise surprise, you are correct…
And overall just another sensor issue, to add to the list…
Edit 2: does not happen always or it only happens when I dont only touch but swipe up slightly🤔