Akshay Mahalle

1.3K posts

Akshay Mahalle

Akshay Mahalle

@AkshayM_m

nothing is in possible. every thing is possible

Yavatmal Maharashtra India Katılım Eylül 2019
50 Takip Edilen95 Takipçiler
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
Thank you for the confirmation. The parcel has been dropped at the shared service center premises since Xiaomi was closed today. I will collect it tomorrow morning and update if there are any issues. @DTDCIndia
DTDC Express Limited@DTDCIndia

@AkshayM_m Hi, We would like to inform you that your shipment is successfully delivered on29th May. We sincerely appreciate your patience and understanding during this process. If you have any further questions or require additional assistance, please reach out to our customer service team.

English
0
0
0
14
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
For the past two days DTDC Courier is giving the same reply that their team is looking into it. Does it really take three days to finish one single work. When you are operating in a major city like Amravati we expect professional service and speed. Stop giving the same copy paste replies and deliver my courier immediately. @DTDCIndia @MiIndiaSupport @jagograhakjago
English
0
0
0
24
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
Hey DTDC_India, what is going on with my shipment? It was booked on 21st May 2026 from Gurgaon and the expected delivery date was 23rd May 2026. The package actually reached the Amravati destination office on 26th May 2026, but it has been lying there idle for the last 3 days without being delivered. Today is 29th May 2026 and it is still showing In Transit. Why is it being held up at the destination for so long? Kindly look into this urgently and deliver my package today itself! Tracking No: X1005493650 Reference No: DBIN26052100731 Destination: Amaravati (444601) @DTDCIndia @jagograhakjago @XiaomiIndia @MiIndiaSupport
Akshay Mahalle tweet mediaAkshay Mahalle tweet media
English
0
0
0
42
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
Hey DTDC_India, what is going on with my shipment? It was booked on 21st May 2026 from Gurgaon and the expected delivery date was 23rd May 2026. The package actually reached the Amravati destination office on 26th May 2026, but it has been lying there idle for the last 3 days without being delivered. Today is 29th May 2026 and it is still showing In Transit. Why is it being held up at the destination for so long? Kindly look into this urgently and deliver my package today itself! Tracking No: X1005493650 Reference No: DBIN26052100731 Destination: Amaravati (444601) @DTDCIndia @jagograhakjago @XiaomiIndia @MiIndiaSupport
English
1
0
0
65
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
विषय: ग्राहकांच्या वेळेची किंमत शून्य? शाओमी (Xiaomi) आणि डीटीडीसी (DTDC) कुरिअरचा अजब कारभार! #JagoGrahakJago #ConsumerAwareness सर्व ग्राहक मित्रांनो, मोठ्या कंपन्या आणि नामांकित कुरिअर सर्व्हिस ग्राहकांना कसा मानसिक त्रास देतात, याचा एक धक्कादायक अनुभव मी सध्या घेत आहे. माझ्या जुन्या शाओमी (Xiaomi) फोनमध्ये मदरबोर्डचा मॅन्युफॅक्चरिंग दोष असल्यामुळे, कंपनीने मला नवीन रिप्लेसमेंट फोन देण्याचे मान्य केले. हा नवीन फोन अमरावती सर्व्हिस सेंटर येथे जमा होणार आहे आणि तिथून तो मला मिळणार आहे. पण खरा घोळ इथे सुरू होतो: - हा नवीन फोन २६ मे २०२६ रोजीच अमरावतीच्या DTDC कुरिअर हब मध्ये येऊन पडला आहे. - आज ४८ तासांपेक्षा जास्त वेळ उलटून गेला आहे, तरीही DTDC कुरिअरचे लोक तो फोन अमरावती सर्व्हिस सेंटरला डिलिव्हर करायला तयार नाहीत! - सर्व्हिस सेंटरचे म्हणणे आहे की, जोपर्यंत कुरिअरवाला आमच्याकडे फोन आणून देत नाही, तोपर्यंत आम्ही तुम्हाला फोन देऊ शकत नाही. फोन अमरावतीतच असूनही केवळ DTDC कुरिअरच्या ढिसाळ आणि बेजबाबदार पणामुळे ग्राहक म्हणून मी हक्काच्या फोनपासून वंचित आहे. ४८ तासांची मुदत संपूनही या दोन्ही कंपन्या ग्राहकाच्या वेळेची आणि त्रासाची कोणतीही किंमत ठेवत नाहीत. तक्रार तपशील: COMPANY: शाओमी इंडिया (Xiaomi India) COURIER PARTNER: DTDC अमरावती Reference No: DBIN26052100731 Tracking No: X1005493650 LOCATION: अमरावती, महाराष्ट्र. ग्राहकांनो जागे व्हा! आपल्या हक्कासाठी आवाज उठवा! #JagoGrahakJago #XiaomiIndia #DTDCCourier #ConsumerRights @DTDCIndia @XiaomiIndia @MiIndiaSupport @jagograhakjago
MR
0
0
0
28
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
@DTDCIndia Thank you for the quick response. Since the phone is already in Amravati since 26th May, please ensure that it gets delivered to the service centre TODAY itself. I need the device urgently.
English
0
0
0
34
DTDC Express Limited
DTDC Express Limited@DTDCIndia·
@AkshayM_m Hi, We've already forwarded your query to the escalation team. We understand that you have been extremely patient, yet, please allow us a little more time and we'll try to resolve the issue as soon as possible.
English
1
0
0
125
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
Disappointed with the service! My replacement phone reached Amravati courier hub on 26th itself, but DTDC/courier team is still not delivering it to the Amravati Service Centre even after 48 hours. Already suffered a lot due to a motherboard defect in the old device. Kindly intervene and get my phone delivered today! Reference No DBIN26052100731 Tracking No X1005493650 @DTDCIndia @MiIndiaSupport @XiaomiIndia @jagograhakjago
English
1
0
0
131
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
It has been nearly 30 hours since my parcel reached Amravati. Keeping a parcel idle for so long and asking for more time is totally unacceptable and unprofessional. I want my parcel delivered in the next 2 hours, or provide me the exact location so I can come and pick it up myself. Stop testing my patience. @DTDCIndia @MiIndiaSupport
English
1
0
0
112
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
My Tracking ID is DBIN26052100731. The parcel reached Amravati 24 hours ago, yet it has not been delivered. I am not interested in doing DM or having a private discussion. Stop delaying and deliver my parcel today itself. If my parcel is not delivered immediately, I will file an official complaint against DTDC with the Consumer Forum (National Consumer Helpline) for deficiency of service. @DTDCIndia @XiaomiIndia @MiIndiaSupport
English
1
0
0
113
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
My Xiaomi 17 replacement phone was being sent to the service center. As per tracking ID DBIN26052100731, @DTDCIndia shows it as 'Delivered' but the service center hasn't received it yet. Time/date details are missing in tracking. Please look into this urgently! @XiaomiIndia @MiIndiaSupport
Akshay Mahalle tweet mediaAkshay Mahalle tweet media
English
1
0
0
222
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
Shocking negligence by @DTDCIndia My Xiaomi 17 replacement phone (Ref: DBIN26052100731) reached Amravati yesterday (26th May) at 8:26 AM. It’s been over 24 hours, but it hasn’t been delivered to the Xiaomi Service Center yet. Worse, the portal falsely shows Delivered with blank date/time details, but the service center confirms they haven't received it! Is this how you handle premium packages? @XiaomiIndia @MiIndiaSupport ple ase look into your courier partner's sloppy work and track my device urgently!
Akshay Mahalle tweet mediaAkshay Mahalle tweet media
English
2
0
0
111
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
My Xiaomi 17 replacement phone was being sent to the service center. As per tracking ID DBIN26052100731, @DTDC_India shows it as 'Delivered' but the service center hasn't received it yet. Time/date details are missing in tracking. Please look into this urgently! @XiaomiIndia @MiIndiaSupport
Akshay Mahalle tweet mediaAkshay Mahalle tweet media
English
0
0
0
28
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
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 @DisabRights_Ind @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
English
0
0
0
28
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
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 @DisabRights_Ind @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
English
2
7
6
277
Akshay Mahalle
Akshay Mahalle@AkshayM_m·
दो दिव्यांग यात्री हटिया एक्सप्रेस ट्रेन नंबर 22846 में सफर कर रहे हैं। PNR 6943725852 सीट नंबर B4 और B5 उन्हें कंबल और तकिया नहीं दिया गया है। AC कोच अटेंडेंट उनसे शिकायत करने पर धमकी दे रहा है और बोल रहा है किसी के पास भी कंप्लेंट कर लो दिव्यांग यात्रियों के साथ यह व्यवहार बेहद शर्मनाक और दुखद है। कृपया तुरंत जांच करें और उन्हें उचित सुविधा उपलब्ध कराएँ। @RailMinIndia @RailwaySeva @AshwiniVaishnaw @BhusavalDivn @drmpune @drmmumbaicr
हिन्दी
0
0
0
58