Hi guys,
It seems that after receiving the new OTA update I ran into some issues.
My problem is that after installing the update my phone started to occasionally refuse to unlock the screen after pressing the power button.
If I connect the charger the screen unlocks but otherwise I have no option to unlock it.
I did a Factory restore (of course I lost every bit of apps I had installed - even tough I had the Backup settings activated-) and it seems that I'm seeing the same problem a few times a day.
Has anyone encountered this issue?
The phone is bought from Vodafone and original software installed.
Haven't rooted or S-off it.
Thanks
if ur phone is s-on and have same issue like s-off phones thats actually good news..seems that HTC messed up something...maybe is good advice for u to give phone to repair service if is s-on and see what thay can say about that.
I actually had that bug BEFORE the update, but not after. Instead of that, HTC Locations stopped working after the update and still is refusing to start even after factory resets and reinstall.
I have tried to contact HTC through their website to ask wheter something can be done about the issue, but the "Email Us" form doesn't seem to be sending anything after pressing submit and the "Chat with Us" form just shows blank white... I tried them on IE, FF and on my phone but they all show the same kind of behaviour.
It's really beginning to get irritating...
Clearly a software issue if it really happened after the OTA.
Wiping your Cache, Dalvik-cache partitions along with your Data (Factory Reset) should be able to refresh your phone as a "brand-new" one. That is if you can.
Stock recovery has an option to wipe Data and Cache.
If these still doesn't work, shove it to HTC's arses.,
Just kidding..
Send it for repair or maybe show it first to them.
some more bug.
-> live wallpaper sometime hang.
Starting yesterday I disabled the new feature "Trace keyboard" and since then the phone unlocked everytime.
Has anyone else kept this option activated and working ok?
2.3.5 OTA suxxxxs
Hi All,
I got OTA 2.3.5 Sense 3.0 on last Friday.
Since I have the screen problem = after a call sometimes I cannot unlock the screen with power button. If connect to the charger it's unlock and after the
power button works again. My phone is S-ON, fully original.
And I have 2 friends, they have Desire S and got this update too,
and after it the problem appear on their phones too.
So I think something wrong with new OTA update.
And I also notice the TTS Service, don't work too, it's always
halted.
(I made a factory reset and my friends too, but we have this problem too)
Any idea?
Everybody "got" this bug with OTA?
Bye,
Istvan from Hungary.
Wait for fix from HTC. They messed up something.
~Swaypovano sa Desire S BRE!~
I was finally able to get in touch with HTC regarding the Locations bug. The service agent said that he has never heard of such a problem before. His advice was that I should try the factory reset once more without the SIM card and without logging in to my Google account. I did that but the Locations still won't work. Only advice after this was to send my phone in for service... I'm really not happy with sending it in just to get an app (that was broken by their own update) to work again. I'm also pretty sure there was something wrong with the update to begin with considering all the new bugs being surfaced all the time.
This is really frustrating...
Would the people that have updated please tell wheter their Locations works perfectly? And if so, where are you from?
Bmw_m6 said:
Hi All,
I got OTA 2.3.5 Sense 3.0 on last Friday.
Since I have the screen problem = after a call sometimes I cannot unlock the screen with power button. If connect to the charger it's unlock and after the
power button works again. My phone is S-ON, fully original.
And I have 2 friends, they have Desire S and got this update too,
and after it the problem appear on their phones too.
So I think something wrong with new OTA update.
And I also notice the TTS Service, don't work too, it's always
halted.
(I made a factory reset and my friends too, but we have this problem too)
Any idea?
Everybody "got" this bug with OTA?
Bye,
Istvan from Hungary.
Click to expand...
Click to collapse
Try to disable the "Trace keyboard" feature. I did that and it seems that for the last ~18 hours I didn't encountered the unlock bug once.
Trace keyboard...
My "Trace keyboard" was off and the problem also present.
I tried to switch on, it hasn't any effect to the problem.
I hope the HTC will soon cede to this OTA full with bugs...
But as I known them, they not soo fast.....
Since the OTA update my Desire S crashes about once a day, and after it reboots it tells me it has recoverd from an error and asks me if i want to send the report to HTC. Seeing as how it reboots without any problems, and it works perfectly except the crash once a day, i suspect it has something to do with the flashing to 2.3.5.
Should i try a factory reset, or could there be another solution (seeing as how i really want to avoid a factory reset).
Oh and I have not rooted or S-OFF'ed my DS before the OTA update, so it's totally stock (as it has been since I got it)
I was able to fix the bug with Locations not starting up by changing my phone's language to English, then starting Locations, then changing the language back to Finnish again and voilá, it worked. One less problem for me.
I think that the Locations bug is limited to Nordic language versions (or even only to Finnish versions).
Hello
After update i have also the issue with the screen impossible to re-activate by power button after call is ended.
howto reproduce the issue: it happens only when screen is locked by security lock (PIN) and I receive a call. I pick up the call, screen is automatically turned off during call. After the call is finished, I'm unable to get the screen active again by pressing the power button!
Only working workaround is to attach phone to charger or connect to USB. Then the screen is activated and I can unlock it by PIN and working normally...
I need to have security lock enabled to be able to sync corporate email ( this is the security policy enforced by corporate Exchange server).
Ferro
Sent from my HTC Desire S using XDA App
This new OTA update looks more like a beta testing for many users still haven't got it and those who got it are complaining about bugs.
Some are affected by power button bug and others experience difficulties unlocking their phones.
What makes the situation even more strange is HTC not announcing the update.
Sent from my HTC Desire S
hamedunix said:
This new OTA update looks more like a beta testing for many users still haven't got it and those who got it are complaining about bugs.
Some are affected by power button bug and others experience difficulties unlocking their phones.
What makes the situation even more strange is HTC not announcing the update.
Click to expand...
Click to collapse
I'm sure you're right. HTC must have got a whole load of their people committed on new phones, others working on the recent security issues, so updates to our DS must be fairly low-priority. It smacks of the way that Microsoft beta-tested new OSes (perhaps still do) - Deploy many different public beta versions, don't bother actually reading the feedback but just simply measure how many complaints come in on each version. Finally, make official the version that got the fewest complaints.
I wouldn't be surprised if it goes quiet again for a week or so now.
The reply from HTC regarding the power bug:
Thank you very much for your cooperation and please be informed that we will get into this issue and we will try to determine what could cause these problems and what can be the solution. Please be patient with us because the investigation process itself it may take between 2 weeks and 4 weeks.
Have a nice day!
Disappointing
Hello,
After investigating further on my issue about "unable to resume screen by power button after call is finished" I described in my previous post I found it is most probably not related to OTA update but to HW problem...
I found my Proximity sensor is possibly dead. How the phone behaves (regarding screen on/off) during making or pick-up the phone is non standard. I also tried several android apps that are checking all sensors available on the phone and I see activity from all sensors except Proximity .
Talked also with HTC support... I'm going to sent my DS to HTC service center
Wish all getting the OTA update to enjoy it - I will certainly do so after I get my phone is repaired.
cheers
Ferro.
Pressing the power button during call or afterwards should light up the display.
At least that's what happened with the previous software version.
I'm still convinced HTC messed something in the update.
I have the exact same issue.
Has there been any work arounds how to fix this problem.
Mine's is on O2, never been rooted. Just stock.
If all fail looks like I will have to wipe phone and start again
Related
I have been having this error where the phone prevents itself from booting, showing a screen that tells you to connect to PC , for a while. Only way to fix it is to remove the battery and restart but that is just a temporary fix. What exactly is this? What causes it? Is it a software issue or a hardware issue? Should I get an exchange or do you guys think this will be fixed with the next update?
Thanks
Never seen that error message. I'd say reset once, if you see it again, get it exchanged.
Yea this my 4th HD7 it shows the error code when you plug it to the PC in zune. Funny thing is that I owned a speck case and I reboot the phone in the case till then. This time i pulled the battery out, put it back in and powered the phone on without the case and it is working fine. I guess the case is pushing down a button or sth and that prevents the phone from working properly. Very weird..
Hey there! I've been having the same error! This is my 2nd HD7, I own the Speck case and I do not think its the case. This issue is happening on mine with or without the case. Pulling out the battery just doesn't cut it. I have to:
1. Remove the battery
2. Plug the USB Charger
3. Insert the battery back
4. Turn on.
I love the phone but this is really frustrating!
Edit: Too bad I can't post the link to youtube due to member status. But the video is up just search for it "c101002e"
Just happened to me too. First day using the Speck case too and i let the battery drain till it died and upon reboot it showed the 'plug into computer' screen. Hope it is just the case causing problems.
did you all updated the sd card ?
you could try to reflash this rom (if you are on t-mobile USA ) http://forum.xda-developers.com/showthread.php?t=810346
Take this one "RUU_Schubert_TMOUS_1.20.531.01_Radio_5.51.09.11a_2 2.31.50.09_Signed_SCHUBERT_RELEASE"
its just the stock tmous rom .
Weird coincidence that all of y'all are using the same case. Maybe it is damaging on of the buttons?
nrfitchett4 said:
Weird coincidence that all of y'all are using the same case. Maybe it is damaging on of the buttons?
Click to expand...
Click to collapse
somewhere on the board they did tell that this case make the buttons really sensitive and it make the phone unusable .
theres a thread on tmobiles forums talking about the same issue, and most if not all the people there have the speck case. Someone says they tested it with and without the case and came to conclusion that the case is putting too much pressure on the camera button, which seems to be causing the problem.
would post the link to the other forum but i cant find it lol
pierce_m said:
theres a thread on tmobiles forums talking about the same issue, and most if not all the people there have the speck case. Someone says they tested it with and without the case and came to conclusion that the case is putting too much pressure on the camera button, which seems to be causing the problem.
would post the link to the other forum but i cant find it lol
Click to expand...
Click to collapse
Yea that was pretty much what was happening to mine. Although I remember trying to boot it without the case and having the same error before so what I did that I did a hard reset ( press power and both volume buttons at the same time) then when the phone booted, I rebooted it without the case immediately and its been working no problem since. I am pretty sure that case pushes the camera button since it grips the phone very tightly. I even overloaded the ram by opening lots of apps that runs in the background and then rebooted but it is working perfectly fine as of right now. Weird.. I am guessing its just a weird bug not a hardware defect.
I found it in a post in the mozart forums, so i tried it, as you do, cause its something new to play with cause my TP2 didnt like swimming, but anyway it was something about hoding down the camera button while power on, and it brought up a picture of a phone and cable and instructing you to plug it into a pc and when i did it started Zune and something about restoration error, so like in the previous posts it may be a stuck or faulty button somewhere on the phone that is causing it.
i didnt watch the video so if that had it in it never mind
cheers
Today 11 April 2011 I got notification about NoDo update for my phone.
It is HTC Mozart on Orange France network.
The pre-NoDo update was istalled about 20 days before.
The update got stuck at step 8. It seemed I had an unusable phone. In a periodic reboot mode into the update screen.
I checked on my W7 64 bit laptop the relevant backup folder, where all my phone data was supposed to have gotten backed up during the update. The folder was empty.
I therefore realized my phone got its rom corrupted during the update and I could not get back my pre-NoDo backup, since this latter was missing from my laptop.
Zune was on no help, stating a C101002E error.
The Windows Phone Support Tool was also of no use, reporting an error code while trying to restore my data.
XDA-forum provided me with a solution:
I went here
http://forum.xda-developers.com/showthread.php?t=1000781
and downloaded both bootloaders with relative roms.
After getting into the bootloader screen (red, green and blue screen), I installed the first ROM provided by Ansar. This could not install succesfully.
With the bootloader tool I could nevertheless confirm my idea I did not have anymore a functioning rom into my phone.
The second rom, the one ending with "Signed_by_ansar" could be succesfully installed.
I now have a Mozart fully functioning.
I had to restore my windows live account, Gmail, etc. My apps did not come back up after syncing with Zune.
I realized I just lost all my SMSs and home screen settings.
My phone was originally network unlocked and remained as such.
I got a notification that there is an official update for my phone the first time I rebooted. I will wait before attempting this update. The ROM by Ansar has got anyway copy/paste, being a NoDo ROM.
The ROM from Ansar, although for Orange France, removes the Orange splash screen when the phone starts. I guess if I need to use warranty on this phone right now I may have some issues with Orange France. Maybe when I update the phone following the update notification I got, I will re-establish a fully certified Orange ROM.
i9o pls and any one pls help me , i faced problem with [260] connection problem between my hd7 and pc vista 64 bit, actually i followed to steps in forum (error code C101002E) and drivers were installed (htc usb sync) before i started to flash rom NoDo bootloader 1, But no way still the problem [260]. i also tried another RUU htc asia xxx707xxx. because i have spl 1.23.2250.0(112138).also some links of RUU to download signed by ansar disappeared in rapid and other sourses, pls help to solve connection problem
Microsoft has release the Windows Phone Support Tool to fix this problem: http://support.microsoft.com/kb/2530409
WPS doesnt help in my case, Im malaysian and thought that need Asia RUU, but when i tried Europian RUU it nicely works, maybe because of i have 8G phone. the RRU is RUU_Schubert_HTC_Europe_1.69.401.01_Radio_5.54.09.21_22.33b.50.10_Signed_SCHUBERT_RELEASE(2)
day2die said:
Microsoft has release the Windows Phone Support Tool to fix this problem: http://support.microsoft.com/kb/2530409
Click to expand...
Click to collapse
Do you know what this tool does to the computer?
I would try it but honestly don't want to do it before I have info what it does to my PC settings. Unfortunately MS doesn't share with this knowledge.
Hi everyone!
I have a big problem with my new hd7.
Just bought, and wired for the very first charging but the phone continues to restart by itself.
Tried a hard reset, to set it in download mode and fix with Windows Phone Support Tool but still nothing to do. Even tried to install a new ROM but at the first start it continues with its loop.
In download mode zune tried to upgrade to nodo but it shows the error C101002E.
Don't know what else to do. Any idea? It's new!
MusicMan587 said:
Hi everyone!
I have a big problem with my new hd7.
Just bought, and wired for the very first charging but the phone continues to restart by itself.
Tried a hard reset, to set it in download mode and fix with Windows Phone Support Tool but still nothing to do. Even tried to install a new ROM but at the first start it continues with its loop.
In download mode zune tried to upgrade to nodo but it shows the error C101002E.
Don't know what else to do. Any idea? It's new!
Click to expand...
Click to collapse
No one had this problem? am i the only unlucky on the earth!?
Return for warranty replacement. Your phone is broken.
Thank you...i hoped i could solve it to not to wait september to have my phone back.
How many people have done it? I'm doing it right now. Step 2 of 9 for the actual beta update...my goodness..it takes a while but it should be worth it.
I'm doing it the way that doesn't require a dev unlocked phone or dev account btw.
Damn that texting bug!! It's still there (kinda). You can keep on typing after 160 characters..just can't send anything.
Hi, how do you get the mango realse?
Hi know that comes out to all developrs on market place, butt i see that you get it in other way...
Can you tell me how you get? E really want to put mango in my htc 7 pro.
Thanks
ms79723 said:
Damn that texting bug!! It's still there (kinda). You can keep on typing after 160 characters..just can't send anything.
Click to expand...
Click to collapse
Yeah for real right? I hope it's fixed by the time Mango goes gold
Update went off without a hitch on two Arrives. Developer unlocked them and then ran that provision.exe file to backup/flip the switch to flag the update to come down.
I think the texting thing is a sprint ROM issue. So yeah, I don't think a fix will come until the Sprint Mango update is released.
Trying this on my HTC Arrive right now.
The final 7661 build is installing now!
I will update you guys when complete, if all goes well...
Alex
EDIT: Successful, sweet!
Mine works great non unlocked method
Sent from my arrive using XDA Windows Phone 7 App
Update OK but
Update was OK, but I am seeing some issues, I am not sure if they are on all Mango phones.
a.) Screen does not go black (off) when taking a call. Thi is bad, because your ear is pressing buttons on the screen, mainly Hold
b.) custom ringtones work now, but they are still low in volume
c.) battery life, not as good as before Mango
d.) proboems with downloading email atatchements (does not work most of the time)
still missing some stuff:
a.) interface to configure phone network settings like, time before switching to voice box,...
b.) send a full contact to another phone
any other know issues or new features detected ?
drhoros said:
Update was OK, but I am seeing some issues, I am not sure if they are on all Mango phones.
a.) Screen does not go black (off) when taking a call. Thi is bad, because your ear is pressing buttons on the screen, mainly Hold
Click to expand...
Click to collapse
This one existed before the Mango update, though it rarely happened for me.
b.) custom ringtones work now, but they are still low in volume
c.) battery life, not as good as before Mango
d.) proboems with downloading email atatchements (does not work most of the time)
still missing some stuff:
a.) interface to configure phone network settings like, time before switching to voice box,...
b.) send a full contact to another phone
any other know issues or new features detected ?
Click to expand...
Click to collapse
I did see something I'd not seen before in email:
"This type of message is not supported by current version of Windows Phone."
As far as I can tell it's just a normal e-mail oddly enough, though I think it was digitally signed. I downloaded a picture attachment just fine though, maybe it's the type?
The no unlock process is on windowsphonehacker dot com Follow the directions. You actually update the phone 2 times. After the first time it says there is another update. The 2nd one is Mango. Literally takes an hour.
I'm using it on a HTC Arrive right now. No crashing or weird stuff for me yet.
done it yesterday, it took me about two hours, no problem
I am missing:
Czech QWERTY keyboard
different notifications for sms and IM (I don't want the phone to vibrate for every IM message, but it would be nice to vibrate when stand-by mode)
already put mango in my htc 7 pro and it is amazing, very fast, good performance and a lot of new things.
I like it very much, and the performance of the IE9 is amazing, very fast load the pages. i think is the best improvement in mango. The IE9 is the best browser i try until today.
i have no problem with the SMS about the number of character, until now everything i use must is running perfect.
think the wp7 is getting better and better.
Just gave Mango a shot on my Arrive. So far everything is working after a little setup and it all works flawelessly. Love it so far.
nohandle said:
done it yesterday, it took me about two hours, no problem
I am missing:
Czech QWERTY keyboard
different notifications for sms and IM (I don't want the phone to vibrate for every IM message, but it would be nice to vibrate when stand-by mode)
Click to expand...
Click to collapse
I have Czech on my arrive and for the chat thing u can just put it on away or appear offline.
eric12341 said:
I have Czech on my arrive and for the chat thing u can just put it on away or appear offline.
Click to expand...
Click to collapse
I have Czech too, but it is QWERTZ not QWERTY, and no option to change it, also when I pop out the HW keyboard the layout changes back to ENG - therefore preventing me from typing characters like čřžšě. Anyone else has problem with this??
Will try the different statuses behavior, but what I meant was: when you chat with someone and you are on the messaging screen it is not necessary to notify every message because you see what is happening.
Updated using non-dev process. Took 2 hours but works flawlessly. Posting from my Sprint HTC Arrive while eating phad tai...so spicy.
Any concerns by anyone that the unlock process (which I haven't read the steps yet) will lock you out of future updates in the same way that the previous WP7 unlocks did?
I've got a Dev account (a couple of free apps in the marketplace), but that's limited to three phones and I've got 5 phones at home.....want to upgrade everyone.
You mean looking before you leap? Thats crazy! Come on in, the waters fine. Maybe you remember that old tale from "Scary stories to tell in the dark" - Room for One More...muahahaha
LayneRobinson said:
Any concerns by anyone that the unlock process (which I haven't read the steps yet) will lock you out of future updates in the same way that the previous WP7 unlocks did?
I've got a Dev account (a couple of free apps in the marketplace), but that's limited to three phones and I've got 5 phones at home.....want to upgrade everyone.
Click to expand...
Click to collapse
If you're worried- september 22nd is the Mango drop date on the street. I'm sure we will see something non-beta around here shortly before that.
There is a process on windowsphonehacker to go back to NoDo.
I know this is very long to read but it's a very frustrating problem, hoping someone out there would be willing to help. I've searched a lot on it and haven't been able to find anything similar.
This is my original thread that's since been archived: http://forum.xda-developers.com/archive/index.php/t-1043323.html
I am using a Samsung Focus on AT&T, with the latest NoDo build (7390). The update went fine with no problems but the keyboard is slow to respond now. It seems like if I'm typing faster than a certain speed, it can't keep up and the buttons don't flash and make the click sound with every press, like I've reached some kind of threshold. I've tried turning off/on all the settings for sound on press, auto-correct, etc., and none of it has worked. This includes applying "reset text suggestions" in the keyboard settings menu.
I tried to reset the phone completely via the About > Reset Phone option, but that didn't help. I've also tried to reformat with the Power+Vol Down+Camera button combo but that didn't fix it either. It's happened with and without a memory card in the phone. The phone has plenty of storage space available...more than 50%.
This happens in the Messaging application, any email account, marketplace search, Bing search, etc. Every place I can type, the problem occurs. I downloaded the Text Text Revolution game to test that and it does NOT have the problem. This is an increasingly frustrating problem to deal with. It makes me think I've made mistakes when I really haven't and is very distracting. It's obvious the phone isn't broken or anything since the keyboard does JUST FINE in Text Text Revolution.
I've managed to revert my phone back to 7004 and 7008, using the stock AT&T Focus ROMs available over in the Samsung threads here. Those builds DO NOT have the problem and the keyboard works great. It works fine whether the phone is locked (stock) or dev unlocked (ChevronWP7). The problem only occurs after I upgrade to NoDo. Has anyone else noticed this problem when moving to 7390, AT&T or any other carrier? From all the work I've done it seems to be directly related to AT&T's NoDo update but I haven't been able to confirm this with anyone else yet. It can't be a problem with the phone since it works fine on pre-NoDo. Anyone willing to try and help me out?
Question to all Android gurus.
I really cannnot understand what is behind
Some time ago I reported here a bug with HTC 2.3.5 and Sense 3.0 upgrade when Power button did not bring a usual "Flight mode -- Switch off -- Reboot" menu. I also mentioned that HTC support confirmed that this is a bug and that an update is expected to come out soon. OK.
Now some interesting details appeared and I am a little bit confused, maybe somebody will explain what is happening.
Before the upgrade I was playing with Leap WiFi Free Utility that was supposed to create a CISCO LEAP Wifi profile, which is being used in our office. When creating the profile I was requested to enter corporate userID and password. Then I was asked to enter another ( second ) password, not part of wifi profile. I entered another password -- well, CISCO LEAP is quite secure protocol, why not to ask for second password to access this profile? Looks normal.
The profile was created successfully, I used it several times...
After some days or maybe even couple of weeks I upgraded to 2.3.5 which brought these issues with power-button menu...
The fix from HTC is still not available, as usual, everything is fine
Then I used my LEAP profile again... entering the password...
Later on suddenly I pressed power button longer than usual -- AND !!!! -- the missing menu is back again !!!
After some experiments I found that the key is this second password to access storage card or smth like this ( the message was too quick to read )
Who can explain -- what kind of password was it ? What for ? How it can affect the behavior of system menu ? How it can be connected ?
I am not very deep in Android, maybe the question is naive, sorry...
But please -- who has any idea what is behind ? Or maybe it is simply a bug on top of bugged bug ?
Sometimes the answer is best left unquestioned. It works now!
I don't think it is a bug. A factory reset is said to fix it and as someone who installed the Europe RUU and not the OTA update, I don't have the problem, so I assume it lies in the patch. If a factory reset fixes it and the routine you've described does the same, somehow that routine is circumventing some glitch which the update suffers from, but not the clean install or the factory reset
Hi, I can't find any thread about this topic, I hope I didn't miss anything.
The problem:
In October, I've bought Nokia 5.3 with Android 10 in Czech Republic (Europe, probably German or UK distribution) and I found out it doesn't vibrate. I tried an app that's dedicated to vibrating but it doesn't do anything and switching to vibrate-only mode using the menu invoked by volume keys switches the phone basically to a full DND mode.
I searched the Internet and found a few reports of other users of Android 10 phones with a similar problem. (None of them, however, with a Nokia phone, at least not concretely Nokia 5.3). I hence assume it's not a defect of my phone but rather a software bug in Android. I'm of course rather reluctant to test this by returning the phone and getting a new one thru warranty because I did put some time into setting this one up. I reached out to the Nokia support but they were unable to help me further than advising me to check a few settings (which were OK) and told me I probably need to wait for an OS update.
The question:
Do you have Nokia 5.3 and do you or do you not have the same problem?
Thank you very much for your experience and suggestions.
Hi,
I have Nokia 5.3, bought it recently. However I hate vibrations so that was the first thing I disabled in the settings. It was vibrating like hell . Check your phone settings, there is an option to turn it on and off.
Cheers!
Hi toppicks,
thanks for confirming that it's obviously not a software issue. I checked all the settings I could, none of them change anything.
edison23 said:
Hi toppicks,
thanks for confirming that it's obviously not a software issue. I checked all the settings I could, none of them change anything.
Click to expand...
Click to collapse
do a factory reset
T.Y.M.SAI said:
do a factory reset
Click to expand...
Click to collapse
Finally, I found time to do the factory reset, it didn't help. I tried with the SIM card and also without it, the phone still doesn't vibrate. I'll go return it to the vendor on Monday, hopefully, I'll get it resolved that way.