This media is not supported in your browser
VIEW IN TELEGRAM
The Xiaomi 17 Air Prototype
Xiaomi was developing a Xiaomi 17 Air smartphone which is basically a copy of the iPhone Air model. It featured a 6.59-inch display, an ultra-thin 5.5 mm body, and a dual-camera setup.
However, it never made it to mass production, likely due to quality issues or they noticed the poor sales of the OG iPhone Air, thus cancelled their plans.
Xiaomi was developing a Xiaomi 17 Air smartphone which is basically a copy of the iPhone Air model. It featured a 6.59-inch display, an ultra-thin 5.5 mm body, and a dual-camera setup.
However, it never made it to mass production, likely due to quality issues or they noticed the poor sales of the OG iPhone Air, thus cancelled their plans.
❤3
How to access Hyperisland settings and customize it for all Apps | Hyperisland tool kit & Bridge
https://youtu.be/gP3sgqPFGrI
https://youtu.be/gP3sgqPFGrI
https://youtu.be/gP3sgqPFGrI
Download link
https://youtu.be/gP3sgqPFGrI
https://youtu.be/gP3sgqPFGrI
https://youtu.be/gP3sgqPFGrI
Download link
Extend Battery life of samsung galaxy smartphones | Simple & Effective Tips
https://youtu.be/DwP4F1c70Mo
https://youtu.be/DwP4F1c70Mo
https://youtu.be/DwP4F1c70Mo
https://youtu.be/DwP4F1c70Mo
https://youtu.be/DwP4F1c70Mo
https://youtu.be/DwP4F1c70Mo
This media is not supported in your browser
VIEW IN TELEGRAM
A shipment of Nokia mobile phones ordered
by a Libyan phone dealer in 2010 has finally been
delivered-16 years.
by a Libyan phone dealer in 2010 has finally been
delivered-16 years.
later-after being stuck in
warehouses amid the country's prolonged instability.
The phones were stranded following the outbreak of
Libya's civil war in 2011, which led to the collapse of
logistics networks, dysfunctional customs systems
and persistent security concerns. The long-delayed
delivery highlights the far-reaching impact of conflict
on everyday commerce, with goods ordered in
peacetime remaining inaccessible for more than a
decade due to sustained chaos.
🙈5
Captain #offline (Dead till 2027)
Photo
The Detailed Version
1. The Origin of the Claim
On January 11, 2026, Reuters published an exclusive report claiming that India's Ministry of Electronics and Information Technology (MeitY) was considering a package of 83 security standards. Key points included:
Source Code Sharing: Forcing makers to hand over code to government-designated labs for vulnerability testing.
Bloatware: Requiring software changes to allow users to uninstall pre-installed apps.
Background Monitoring: Mandatory blocking of apps using cameras or microphones in the background.
Software Updates: Forcing companies to alert the government before releasing major software updates or patches.
2. The Government's Rebuttal
Within hours of the report's publication, the PIB Fact Check and MeitY issued a series of statements:
The Denial: "The Government of India has NOT proposed any measure to force smartphone manufacturers to share their source code."
The Reality: The government admitted that consultations are happening, but they are "routine and part of standard industry engagement." They aim to build a framework for mobile security against fraud, but sensitive IP like source code is not on the table.
Quote from IT Secretary S. Krishnan: He stated that "any legitimate concerns of the industry will be addressed with an open mind" and that it was "premature to read more into it."
3. Why This Caused a Stir
Smartphone companies (Apple, Samsung, etc.) and industry bodies like MAIT (Manufacturers' Association for Information Technology) reportedly expressed deep concern because:
Proprietary Risk: Sharing source code exposes the "recipe" of the phone, posing massive intellectual property and security risks.
No Global Precedent: No major democratic nation (EU, USA, etc.) currently mandates the sharing of source code for consumer electronics.
Battery/Performance: Some proposed measures, like constant malware scanning or 12-month log storage, were flagged as technical burdens that would drain battery life.
4. Current Status
A high-level meeting between the IT Ministry and tech executives is scheduled for tomorrow, Tuesday, January 13, 2026, to further discuss these security standards and clear up the confusion caused by the reports.
1. The Origin of the Claim
On January 11, 2026, Reuters published an exclusive report claiming that India's Ministry of Electronics and Information Technology (MeitY) was considering a package of 83 security standards. Key points included:
Source Code Sharing: Forcing makers to hand over code to government-designated labs for vulnerability testing.
Bloatware: Requiring software changes to allow users to uninstall pre-installed apps.
Background Monitoring: Mandatory blocking of apps using cameras or microphones in the background.
Software Updates: Forcing companies to alert the government before releasing major software updates or patches.
2. The Government's Rebuttal
Within hours of the report's publication, the PIB Fact Check and MeitY issued a series of statements:
The Denial: "The Government of India has NOT proposed any measure to force smartphone manufacturers to share their source code."
The Reality: The government admitted that consultations are happening, but they are "routine and part of standard industry engagement." They aim to build a framework for mobile security against fraud, but sensitive IP like source code is not on the table.
Quote from IT Secretary S. Krishnan: He stated that "any legitimate concerns of the industry will be addressed with an open mind" and that it was "premature to read more into it."
3. Why This Caused a Stir
Smartphone companies (Apple, Samsung, etc.) and industry bodies like MAIT (Manufacturers' Association for Information Technology) reportedly expressed deep concern because:
Proprietary Risk: Sharing source code exposes the "recipe" of the phone, posing massive intellectual property and security risks.
No Global Precedent: No major democratic nation (EU, USA, etc.) currently mandates the sharing of source code for consumer electronics.
Battery/Performance: Some proposed measures, like constant malware scanning or 12-month log storage, were flagged as technical burdens that would drain battery life.
4. Current Status
A high-level meeting between the IT Ministry and tech executives is scheduled for tomorrow, Tuesday, January 13, 2026, to further discuss these security standards and clear up the confusion caused by the reports.
❤4
Realme Neo 8 Display
#realme #realmeNeo8
📱 165Hz LTPS Samsung M14 Sky Display
📱 M14 Flagship Luminous Material
☀️ 1000nits Manual Maximum Brightness
☀️ 1800nits Global Peak Brightness
☀️ 3800nits 20% APL
☀️ 6500nits Local Peak Brightness
🧿 103% P3 Ultra wide color gamut
⚡️ 1500h Samsung T95 165Hz Sky Display Performance
🎮 165FPS Ultra-high frame rate gaming
🧿 Customized Touch Chip
🧿 3800Hz Instantaneous TSR
🧿 360Hz Ten-finger TSR
👁 Green field eye protection
#realme #realmeNeo8
🔥2
A news report by Reuters claims that India proposes forcing smartphone manufacturers to share their source code as part of a security overhaul.
❌ This claim is #FAKE
▶️ The Government of India has NOT proposed any measure to force smartphone manufacturers to share their source code.
▶️ The Ministry of Electronics and Information Technology (GoI_MeitY) has started the process of stakeholders’ consultations to devise the most appropriate regulatory framework for mobile security. This is a part of regular and routine consultations with the industry for any safety or security standards. Once a stakeholder consultation is done, then various aspects of security standards are discussed with the industry.
▶️ No final regulations have been framed, and any future framework will be formulated only after due consultations.
❌ This claim is #FAKE
▶️ The Government of India has NOT proposed any measure to force smartphone manufacturers to share their source code.
▶️ The Ministry of Electronics and Information Technology (GoI_MeitY) has started the process of stakeholders’ consultations to devise the most appropriate regulatory framework for mobile security. This is a part of regular and routine consultations with the industry for any safety or security standards. Once a stakeholder consultation is done, then various aspects of security standards are discussed with the industry.
▶️ No final regulations have been framed, and any future framework will be formulated only after due consultations.
❤2🤝1
Create Recovery & Flash any AOSP ROM to Any Android Phone Without PC 🖥 | 2026 Guide
https://youtu.be/GEVKP9q9qRo
https://youtu.be/GEVKP9q9qRo
https://youtu.be/GEVKP9q9qRo
Download link
https://youtu.be/GEVKP9q9qRo
https://youtu.be/GEVKP9q9qRo
https://youtu.be/GEVKP9q9qRo
Download link
❤2