TG Telegram Group Link
Channel: 24*7 Poco News
Back to Bottom
Delete channel?
Final Results
50%
Delete
50%
No. Leave it as is.
100 votes done.
50/50.

Due to sentimental and nostalgic reasons, channel and group stay.
Telegram is deleting the channel usernames for inactive channels.

This is another message to keep it alive! πŸ₯²

To all the 1.8k subscribers, those who still own a Pocophone F1 can check out @oos_beryllium, new build is dope!
If you are looking for a ROM that continues the legacy of some good stuff AEX official used to offer, take a look at this ROM here :-

https://hottg.com/resist15_support/28178
./keepAlive
Any Android (13?) Desktop Mode enthusiasts here?
Drop your desktop mode setup screenshots in the comments section below :)
In case your Pocophone F1 is your tertiary/quaternary device, feel free to play with the Renegade Project.
The device-specific guide can be found here:- https://renegade-project.tech/en/devices/xiaomi/beryllium

Authored by yours truly.

Feel free to fuck brick your beryllium by following the guide on the main page :)
Don't forget to backup EFS else rip IMEI

P.S:- Don't expect to have a DIY Steam Deck. This sucks big time due to lack of x64 GPU HW acceleration.
A Games Tracker list can be found here

DISCLAIMER:- DWYOR! On these uncharted waters, you are solely responsible for your actions if you mess your Poco F1! You have been warned!
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
Android 14 is HERE! (Told y’all it’d be todayπŸ˜‰) Google is uploading the Android 14 source code to AOSP. Once the code is uploaded, I'll dig through it to see if there's any interesting features or changes I missed. If you find anything yourself, send me a tip!

Android 14 is rolling out to the Pixel 4a 5G and later starting today and will be available later this year for devices from Samsung, iQOO, Nothing, OnePlus, OPPO, Realme, Sharp, Sony, Tecno, Vivo, and Xiaomi.

Read more at Esper.io.
Current 4.19 status on Poco F1:
- Audio βœ…
- BT βœ…
- BT audio βœ…
- BT offload βœ…
- Camera βœ…
- DDR BUS βœ… (currently: {min=50mhz, max=451mhz}, stock: {min=150mhz, max=933mhz} (FKM derp)
- Deep Sleep ⚠️ (doesn't work when charger is connected)
- DT2W ❌
- FM βœ…
- Fingerprint βœ…
- LED βœ…
- RIL βœ…
- Touchscreen ⚠️ (Sleep mode is broken, FTS acts strange)
- Vibration βœ…
- VIDC βœ… (from 4.14)
- WLED βœ…
In case anyone missed it :D

Credits:- sid_key and team
This media is not supported in your browser
VIEW IN TELEGRAM
So, what went wrong?

Apparently, DDR BUS values reported by FKM are taken from the ddr-bw node taken from /sys/class/devfreq. The formula used is cpubw * 0.065536.

However, in 4.19, the path changed. cpubw -> cpu_cpu_llcc_bw now, but in FKM it was set to cpu_llcc_ddr_bw, which is llccbw on 4.9.
This media is not supported in your browser
VIEW IN TELEGRAM
In the future, it could be that the kdrag0n's Safetynet fix would not be reliable anymore.
As mentioned in this post, a modded fix was needed to fix Safetynet.

With the deprecation of Safetynet API and the introduction of Play Integrity API, a new module is needed to fix Device Integrity. To add insult to injury, Google is ban-hammering old device fingerprints, thus rendering existing methods of fixing Device Integrity obsolete.

Enter PlayIntegrityFix

Consider this: If you pass Safetynet using apps like YASNAC and Play Store of your device says "Device is not certified", this fix is for you!

This app helps evaluate your device's PlayIntegrity status.
This media is not supported in your browser
VIEW IN TELEGRAM
HTML Embed Code:
2024/03/28 01:37:58
Back to Top