Saurav Hegde

Student at Brihan Maharashtra College of Commerce Pune. Tech enthusiast. Trying to make others that little bit mmore aware about accessibility and inclusion.

[Saurav Hegde @SauravHegd64393]

@yatinpanchal143 Earlier you had the excuse of aggressive pricing but now good smartphones don't come cheap. Brands with highest bloatware. @SamsungIndia @realmeIndia @XiaomiIndia @Vivo_India @OPPOIndia learn from @LavaMobile who provide clean UI even in low price.

[Yatin Panchal @yatinpanchal143]

SMARTPHONE MANUFACTURERS: TRUE DEVICE OWNERSHIP MUST NOT DEPEND ON TECHNICAL EXPERTISE — END FORCED BLOATWARE & INTRUSIVE ADS

As a technical user, I can remove bloatware using ADB or rooting. However, this is not a solution. Any system that requires advanced skills, risks warranty loss, or instability to gain control is unjust.

This issue is not about power users. It is about ownership.

Most consumers—parents, teachers, healthcare workers, small business owners, students, and seniors—do not know ADB commands, cannot root safely, and should never be expected to. Yet they are forced to accept pre-installed third-party apps they neither want nor consented to. Often, manufacturers provide no option to disable them. These apps exist due to commercial agreements, not user choice.

What forced bloatware does:

• Accelerates e-waste by consuming storage, background CPU, and battery health, shortening device lifespan. • Drains performance through persistent background services that reduce stability and responsiveness. • Injects intrusive advertisements into core system interfaces. • Retains privileged “zombie” permissions for tracking and telemetry despite user restrictions. • Expands the attack surface by embedding unvetted code with system-level privileges.

These are not features. They are monetisation mechanisms.

Even flagship devices costing over $1,000 ship with ads and sponsorware. This is predatory double-dipping: charging a premium for hardware while monetising users through ads and data extraction. If a consumer pays full price, the transaction should end there.

This creates a tiered ownership model. Full control is reserved for the technically elite, while everyone else is treated as a second-class licensee on hardware they paid for. True ownership must be universal.

Technically, there is no justification for these restrictions. Modern operating systems can allow one-tap uninstallation of any non-kernel app without compromising stability or security.

The “System App” label is routinely abused. Proprietary browsers, app stores, analytics tools, ad services, and community apps are falsely marked as system-critical to prevent removal. Unless an app is a driver or core OS framework, it is software and must be removable. These barriers exist only to protect pre-installation revenue.

Every consumer deserves, without exception: • Clean, minimal software out of the box. • One-tap uninstall for all non-driver pre-installed apps. • At minimum, the ability to fully disable any pre-installed app. • Freedom from forced ads inside system interfaces. • No need for developer mode, root, or external tools to reclaim privacy. • Full transparency about pre-installed apps and their commercial purpose.

Respect means empowering users, not exploiting them. Privacy, security, and a clean experience must be the default.

The era of forced bloatware and intrusive ads must end. Consumers will increasingly choose brands that respect ownership and user trust.

If you believe device control, privacy, and an ad-free experience should be accessible to every user, quote, reply, or repost.

#NoMoreBloatware #EndBloatware #NoForcedAds #UniversalOwnership #DigitalRights #ConsumerRights #PhonePrivacy #CleanSoftware #MyPhoneMyRules #RightToUninstall #SustainableTech

@Google
@GoogleIndia
@SamsungMobile
@SamsungIndia
@Xiaomi
@XiaomiIndia
@MiIndiaSupport
@XiaomiSupport
@Moto
@motorolaindia
@Moto_Support
@oneplus
@OnePlus_IN
@OnePlus_Support
@oppo
@OPPOIndia
@OPPO__Support
@Vivo_India
@realmeglobal
@realmeIndia
@realmecareIN
@POCOGlobal
@IndiaPOCO
@POCOSupport
@global_iQOO
@IqooInd
@ASUS
@ASUSIndia
@ASUS_ROG
@nokia
@HMDdevices
@HMDdevicesIN
@tecnomobile
@TecnoMobileInd
@Infinix_Mobile
@InfinixIndia
@Honorglobal
@HiHonorIndia
@Android
@AndroidDev
@AndroidAuth
@androidcentral
@AndroidPolice
@Androidheadline
@xdadevelopers
@MishaalRahman
@sundarpichai
@TechCrunch
@91mobiles
@TheHackersNews

[Maruti paramwad @Marutiparamwad]

@SauravHegd64393 @Dev_Fadnavis @mieknathshinde @AjitPawarSpeaks @CMOMaharashtra @MirrorPune @PunekarVoice हे जास्तकरून रिक्षा स्टैंड वर असणाऱ्या रिक्षा वाल्यांचा प्रॉब्लम आहे. यांचे पाहून बाकी त्यांचेच अनुसरण करतात.

[Saurav Hegde @SauravHegd64393]

I am also a visually challenged person, so walking is not an option for me even for short distances. Not all but many rikshaw drivers charge unreasonable amounts for no reason. This is not good for a city like Pune. @beingpunekar @mohol_murlidhar @supriya_sule @MissionAccess_

[Saurav Hegde @SauravHegd64393]

I advocate for bike taxies in Pune.
Rikshaws often charge too high for short distances like Rupees 50 for a kilometer. Rikshaws do not come for short distances especially in evening. @Dev_Fadnavis @mieknathshinde @AjitPawarSpeaks @CMOMaharashtra @MirrorPune @PunekarVoice

[Saurav Hegde @SauravHegd64393]

@XA11y the automatic image and video description feature you had introduced was awesome. However, it has stopped working for some reason. Kindly re-enable it to provide maximum accessibility for screen reader users. @elonmusk @X @XCorpIndia @GoI_MeitY @MissionAccess_

[Saurav Hegde @SauravHegd64393]

@NetflixIndia if you want to give audio description for blind viewers, please stop making the narrator translate English dialogues into Hindi! Many viewers want to listen to the original dialogue. @MissionAccess_ @Rahul400 @MIB_India not able to enjoy movie with others.

[Amar Jain @amarjain2006]

@DARPG_GoI @narendramodi @PMOIndia @DrJitendraSingh @svoruganti1466 @MIB_India @PIB_India @DDNewslive @airnewsalerts @mygovindia A blind citizen‘ single grievance cannot be resolved on this portal because the portal requires an image captcha to be solved, which is not accessible. The portal needs to provide audio/text captcha in addition to image captcha to make it accessible for persons with blindness.

[शुभम देशमुख @sbdeshmukhamt]

Collective Appeal from the Blind Community: Google TTS Needs Action, Not Just Acknowledgment.

This is a comprehensive public report on "Speech Services by Google" (Google TTS).
We are posting this publicly because these issues are not new. They have been reported by multiple users over a long period, and many have already been accepted by your teams through standard feedback channels.
We do not need to "DM for details" or "provide audio recordings." We need these long-standing issues and accepted feature requests to be fixed and implemented.
The post is clear to avoid any confusion:
PART 1: ACKNOWLEDGED FEATURE REQUESTS (NOT IMPLEMENTED)
1. User Dictionary: We still have no ability to create a user dictionary to fix custom pronunciations (e.g., for names or technical words).
2. Uninstall Default Voices: We still cannot uninstall the default English (US) voice pack, which wastes storage and clutters the menu.
3. Number Processing: We still have no feature to choose how numbers are read. The default "millions, billions" format is annoying, and we need options (like digit-by-digit).
4. Date Processing: We still have no feature to customize date formats. We need to be able to set regional standards (e.g., DD/MM/YYYY for India).

PART 2: LONG-STANDING BUGS (NOT FIXED)
1. "Zero" Pronunciation Bug: The digit "0" is still incorrectly read as the letter "O" (e.g., "one O five" instead of "one zero five"). This affects all English variants (US, UK, IN, AU, NG).
2. Poor Audio Quality: The voices are not "clear, crisp, and crystal." They are muffled and sound nasally, "like somebody is speaking in the nose."
3. High Latency (Accessibility Failure): The TTS has "huge latency" and is "sluggish." This makes accessibility services like Explore by Touch (TalkBack) "pathetic" and unusable. The "quick responsive" feedback needed for scrolling and swiping is completely absent.
4. No Expressiveness: The engine ignores punctuation. A sentence ending in a question mark (?) is read with the same flat, declarative tone as a period, failing to convey intent.
5. Broken Auto-Language Switching: The auto-language detection "is not working properly." When it does try to switch, it introduces a "huge delay" that disrupts the flow of reading.
6. Incorrect Voice Switching: The system ignores the user's selected "desire voice." For example, a user sets Voice A for English and Voice B for a regional language. When reading, the system will suddenly use a random Voice C for the regional language, creating inconsistency and confusion.
7. Unsolicited Voice Downloads: Google TTS is still automatically downloading unnecessary voices that the user never requested. Even after being manually uninstalled, the system forcibly re-downloads them, wasting data and storage against the user's explicit wishes.

These are not new reports requiring investigation. They are well-documented failures requiring action. We request escalation and a timeline for these fixes.

@Google
@GoogleAccess
@Android
@sundarpichai
@MissionAccess_
@dequesystems
@accessibility00
@LevelAccessA11y
@IAAPOrg
@A11yNews
@MSFTEnable
@acbnational
@NFB_voice
@BlindUnion
@IDA_CRPD_Forum
@socialpwds
@GoI_MeitY
@_DigitalIndia
@ncpedp_india
@Ncpwds
@BeMyEyes
@DisabRightsFund
@accessible_apps
@FreedomSci
@APHfortheBlind
@fbaccess
@NVAccess
@DisabilityRepor
@BlindDroidUsers
@AndroidDev
@AndroidAuth
@androidcentral
@AndroidPolice
@_ShivamBhatt
@Sindhuvasini
@VGTtweets
@ppranava68
@NirendraNagar
@amarjain2006
@mtonykurian
@Rahul400
@istemtech
@yatinpanchal143
@PrakashWKamatPK
@drvj70
@GyanTherapy
@iamasagar
@friendsofeyeway
@ScoFoIndia
@MishaalRahman

#GoogleTTS
#SpeechServicesByGoogle
#TalkBack
#AndroidAccessibility
#Accessibility
#BlindCommunity
#ScreenReaderUsers
#UserDictionary
#CustomPronunciation
#NumberProcessing
#LowLatency
#FixGoogleTTS
#AccessibilityMatters
#DisabilityRights
#InclusionMatters
#AccessibilityForAll
#DigitalInclusion
#TechForAll
#EqualAccess
#FixAccessibility
#AccessibleTech

[Prakash W. Kamat @PrakashWKamatPK]

Railway stations not accessible, police stations not accessible, banks and ATMs not accessible, schools and colleges not accessible....so accessibility,inclusion, empowerment of Persons with Disability seems to be just a slogan...where is the hope? Where is the sensitisation? Where is that empathy....does anyone care to stand up and be counted?🤔
@discommgoa @tahahaaziq @RBI @RBIsays @MSJEGOI @rajeshaggarwal @Office_of_CCPD @armanaly @Sugamyata @puneetsinghal22 @VijaiSardesai @ViriatoFern @Yurialemao9
@GaureeM_TOI @Navhind_Times @thegoanonline @DrVrushaliRaut @khanumarfa @charuhaasparab @priyankac19 @GoaHumaneTrust @SKBEHERA76 @FirstSutraFdn @EgnaCleetus @Coll_NorthGoa @Coll_SouthGoa @kbdessai @rohinimd25 @goadisability @asinaib @DGP_Goa @Goa_edu @FrazellaA @RahulGuptaIPS @DHS_Goa @HemoIndia @zoo_bear @nagvekarvishant @OmkarSantoshPa1 @TukaramGaonkar4 @Varsha270819 @mausamii2u @priyanka2bharti @RajVaidyaGoa @water4voiceless @ShabrinZeenat

[Saurav Hegde @SauravHegd64393]

Dear @nothing please fix the following bug. Headphones connected to Nothing Phone 3A malfunction as audio often stops playing from the earphones causing inconvenience. @mrtechpedia @GyanTherapy @TechWiser @geekyranjit @jagograhakjago @nothingsupport @nothingindia

[Saurav Hegde @SauravHegd64393]

@sbdeshmukhamt @yatinpanchal143 @telegram It is shameful that such a large MNC is not serious and concerned about accessibility and also @GoI_MeitY who is not asking social media platforms to submit audit reports from an IAAP certified auditor to ensure maximum accessibility on social media apps. @AshwiniVaishnaw

[शुभम देशमुख @sbdeshmukhamt]

The message from me and my friend @yatinpanchal143 on behalf of the entire blind community.

Hey @Telegram, enough is enough.
Your complete disregard for accessibility is shameful. People with disabilities have been reporting these issues since November 2021, and you have done absolutely NOTHING.

Issue 1: Message Reading
Screen reader users cannot even read messages properly. No way to read by character, word, line, or paragraph. In groups, channels, or personal chats — it is a total mess.

Issue 2: Video Calls
Sure, the voice call ” and “video call” buttons are accessible, but once the call starts, the entire screen becomes a blank wall for screen reader users. No feedback, no control — just silence.

Issue 3: iOS Accessibility
On iPhones, your app is practically unusable. VoiceOver users cannot even navigate the interface properly. It is like accessibility never existed in your design meetings.

You are violating WCAG 2.2 guidelines and still pretending this is not your problem. This is not a small bug — it is pure negligence.

Accessibility is not optional. It is not a “nice to have.” It is a right. And your ignorance towards it is unacceptable.

@MissionAccess_
@duro
@dequesystems
@accessibility00
@GyanTherapy
@iamasagar
@JaikyYadav16
@LevelAccessA11y
@IAAPOrg
@A11yNews
@googleaccess
@MSFTEnable
@acbnational
@NFB_voice
@BlindUnion
@IDA_CRPD_Forum
@socialpwds
@GoI_MeitY
@_DigitalIndia
@ncpedp_india
@Ncpwds
@BeMyEyes
@DisabRightsFund
@AppleSupport
@tim_cook
@accessible_apps
@FreedomSci
@APHfortheBlind
@fbaccess
@NVAccess
@DisabilityRepor
@BlindDroidUsers

#MSFTEnableFeedback
#TelegramAccessibility #AccessibilityFail #DoBetterTelegram #DisabilityRights #InclusionMatters #AccessibilityForAll #DigitalInclusion #TechForAll
#EqualAccess #FixAccessibility #AccessibleTech #ShameOnTelegram

[Saurav Hegde @SauravHegd64393]

@instagram I have really lost hope from your team and developers. This is the height of non-compliance! A legal action is really required! @MissionAccess_ @Rahul400 @Office_of_CCPD @sunil_abraham @GoI_MeitY @DePwDSCTGP @rajeshaggarwal The app is seriously inaccessible!

[Saurav Hegde @SauravHegd64393]

accessibility issues are:
1. Talkback is unable to perceive ETA when driver is reaching location.
2. Cannot rate the driver with Talkback after trip.
3. Cannot understand driver's exact location when driver is reaching destination displayed by Ola Maps.. @MissionAccess_

[Saurav Hegde @SauravHegd64393]

Ola application is not accessible to us as it is incompatible with Our screen reader that is called Google Talkback. Request for urgent action to this end. Happy to provide specific inputs. @MissionAccess_ @Olacabs @bhash @Rahul400 @rajeshaggarwal @DePwDSCTGP @PrakashWKamatPK

[Omkar Santosh Pawaskar @OmkarSantoshPa1]

After 6 Sep update, Kuku FM app became inaccessible with TalkBack. Blind users can’t search, play next episode, or navigate. So please resolve this issue @KukuFMOfficial @PrakashWKamatPK

[Saurav Hegde @SauravHegd64393]

Thankyou so much @X and @XA11y and @elonmusk for introducing automatic image description for screen readers on your platform, really means a lot! The description is rich and detailed, other social platforms should learn from this. @instagram @facebook @WhatsApp @sunil_abraham

[Saurav Hegde @SauravHegd64393]

@TeamYouTube Yes, have done that and issue did not get resolved.

[Saurav Hegde @SauravHegd64393]

Experiencing a frustrating bug on Nothing Phone 3A. Music starts to buffer and stutter when listening to music on YouTube music with C type earphones when screen is off but with no other app. I am not going to visit service center. Case no 1266572. @nothingindia @youtubemusic

[Saurav Hegde @SauravHegd64393]

Issues that need to be discussed are:
9th/10th kids as scribes for blind in JEE, Braille/recording not binding and rough-work denied.
No tech deadlines, own scribe barred, quality unchecked. This creates a disadvantage for disabled students. @openletteryt @mohakmangal

[Saurav Hegde @SauravHegd64393]

dear @openletteryt your videos about social issues are very detailed. I request you to talk about the unjust scribe guidelines prescribe for students with disabilities. @PrakashWKamatPK @mohakmangal @palkisu @namanshrivastav @abhiandniyu