Skip to main content

Vibration vanishes on Samsung galaxy s2 after ICS update

Some users have reported that, after they update their Samsung Galaxy S2 to ICS 4.0.3, vibration completely vanishes on the phone. I also faced the same problem. Till now, no specific reason why it happens and any update has been given by Samsung that recifies the problem. I rectified the problem using the following steps:

a. Firstly put the phone in silent mode. (Even if doesnot vibrates).
b. Switch off the phone.
c. Switch on the phone. While the operating system loads, you will notice a small vibration at the start. If this happens, the phone's vibration facility will function properly.

Normally the problem doesnot occur again. But if it occurs, repeat the same steps again. Why it happens, there is no logical reason to explain, but in my case it worked. Please try this method if you face this same problem and share your experience.

Comments

Unknown said…
Dont tell me sir , you are using STOCK ROM on your dual core S2,
Find some custom ROMs on XDA-DEVELOPERS.COM

You will get 4.0.4 with whole lot of tweaks, You can even try AOKP which is one of the best

And Finally My Team ROM ..
Its called PARANOIDANDROID..
You will be able to use tablet/ phone mode at the same time..It feature PAL , PAD For the first time in Android History

More Details : http://betadan.com/paranoid

Official XDA -Thread For S2 : http://forum.xda-developers.com/showthread.php?p=26264894

My Website : www.blindndumb.com

I am Rakesh aka blindndumb
A student of LPU, B.Tech CSE 3rdYear (waiting for results to move to 4th year ;), Currently struggling to make v3 kernel for android )

Cheers :)
June 11, 2012 at 12:12 PM
Unknown said…
This is the correct xda link for galaxy sII

http://forum.xda-developers.com/showthread.php?t=1580070
June 11, 2012 at 12:17 PM
Rohit said…
Rakesh,

Tried every custom rom on the samsung galaxy s2. Custom rom's etc. But the vibration didn't work. That's I posted the solution.
June 11, 2012 at 8:59 PM
Burhan said…
Thanks a lot for the solution...It worked for me as well
June 12, 2012 at 8:39 AM
madhav_c said…
No sir this doesnt work for me
June 19, 2012 at 6:49 AM
Geeky2Core said…
Thanks alot :)
It worked for me but while restarting there was no vibration.
September 25, 2012 at 2:54 AM
Gelásio said…
not working for me
November 6, 2012 at 6:46 AM
Unknown said…
For me work.When no vibration,turn phone on silent mode,restart and then work:)
Thanks
February 2, 2014 at 10:18 AM
Post a Comment

Popular posts from this blog

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc . In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations. 1. Installation of required packages In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation: i. npm install knex ii. npm install mssql Once the packages are installed, we can write the following code to connect: //Code to KNEX connection settings. var knex = require('knex')({ client: 'mssql', connection: { user: 'sa', password: 'pwd', server: 'localhost', database: 'Test' } }); //Code to query the Table DEPT knex.select("*").from("dept") .then(function (depts){ depts.forEach((dept)=>{ //use of Arrow Function console.log({...dept}); }); }).catch(function(err) { ...
Post a Comment
Read more

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.
1 comment
Read more

MAX pool size reached in ASP.NET

If you are handling large databases and big application(s) that are running on servers in a cluster, then probably this error might have occurred. In an ASP.NET app, we can use connection pooling that helps to share the connection between multiple request(s) rather than creating more connections. The settings relating to connection pool are defined in web.config file. Max pool size reached error in ASP.NET occurs, when the number of connections go beyond the maximum defined limit in Web.config file. Following are the various settings of the Connection Pooling: Name Default Description Connection Lifetime 0 When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span (in seconds) exceeds the value specified by  Connection Lifetime . This is useful in clustered configurations to force load balancing between a runnin...
Post a Comment
Read more