THink i know why Vibrate isnt working

[Guest zerosignull]

right ..

Browsing through the init.rc from the kernel. found this reference to vibrate

chown system system /sys/class/timed_output/vibrator/enable

had a look in that directory and we have a file called enabled which has a single value of 0. Which is false ....

[Guest Josh04]

/sys/ is a virtual folder, because in UNIX all actions should be accessible as files. It's a representation of all the devices the kernel can address. The vibration driver is loaded, as we have that folder, but it doesn't work, because all android does to turn it on is "echo 1 > /sys/class/timed_output/vibrator/enable" and that doesn't do anything.

[Guest Cheadle]

Can we not just get the driver from the 1.5 build or will this be vastly different for 2.1.

Personally I dont get why this is a big issue. Bigger issues need to be stability and getting in APN settings for all networks and sorting out that annoying menu that doesnt work properly when you dont pop a T Mob sim in.

[Guest Bendolfc]

It's a big issue for people who have to work and can't have their phone volume on.

[Guest eckengucker1]

Can we not just get the driver from the 1.5 build or will this be vastly different for 2.1.

Personally I dont get why this is a big issue. Bigger issues need to be stability and getting in APN settings for all networks and sorting out that annoying menu that doesnt work properly when you dont pop a T Mob sim in.

stability = fixed

apn settings = use "wpa_supplicant.conf" from 1.5 stored in system\cust\t-mobile\XX

menu= use vanilla 2.1 version (see forum)

[Guest Cheadle]

Well stability isnt really fixed, its better - however every day its getting better and better.

What I dont get is why we cant just build the APN into one of the roms. It makes no difference to T mob users, but allows everyone else to use the phone.

I confess to reading about the menu after writing that comment! (ooops) :)

[Guest eckengucker1]

Well stability isnt really fixed, its better - however every day its getting better and better.

What I dont get is why we cant just build the APN into one of the roms. It makes no difference to T mob users, but allows everyone else to use the phone.

I confess to reading about the menu after writing that comment! (ooops) :)

Ask the rom-modders ;)

[Guest Josh04]

Can we not just get the driver from the 1.5 build or will this be vastly different for 2.1.

It's compiled into the kernel, the driver doesn't seperate out.

[Guest le_lutin]

Can we not just get the driver from the 1.5 build or will this be vastly different for 2.1.

Personally I dont get why this is a big issue. Bigger issues need to be stability and getting in APN settings for all networks and sorting out that annoying menu that doesnt work properly when you dont pop a T Mob sim in.

Vibrate not working is a massive issue for a lot of people on here.

Let's stay on topic.

[Guest robertopero]

Vibrate not working is a massive issue for a lot of people on here.

Let's stay on topic.

Yes, this is a very big problem. I need vibrate, but I love the 2.1 ROM other things, like the speed, new applications. So I can't decide which ROM I use. :)

[Guest starkos]

Yes, this is a very big problem. I need vibrate, but I love the 2.1 ROM other things, like the speed, new applications. So I can't decide which ROM I use. :)

Lol I know what u mean, but after making my own partially-vanilla rom yesterday I'm sticking with it as it feels faster and as (if not more) reliable than the cupcake MCRs.

The only thing missing is the damn vibration ;)

[Guest gusthy]

Lol I know what u mean, but after making my own partially-vanilla rom yesterday I'm sticking with it as it feels faster and as (if not more) reliable than the cupcake MCRs.

The only thing missing is the damn vibration :)

But how did you manage to make phone calls?

[Guest Jan M]

But how did you manage to make phone calls?

probably by keeping the original t-mo phone packages...

[Guest gusthy]

probably by keeping the original t-mo phone packages...

Ok, but which are they? Since both vanilla roms (r1 and r6) suffer from not being able to use the phone as a phone. And if it is so simple, it would be nice to see the solution

[Guest Josh04]

I use the default dialer to make calls. Is there a problem with it?

[Guest starkos]

probably by keeping the original t-mo phone packages...

Yea pretty much, most apk's with telephony or something similar I kept the t-mob versions but they don't affect colour schemes or anything anyway. I think the main reason the mic failed in the calls was because phone.apk had been replaced

Edited May 17, 2010 by starkos

[Guest zerosignull]

Yea pretty much, most apk's with telephony or something similar I kept the t-mob versions but they don't affect colour schemes or anything anyway. I think the main reason the mic failed in the calls was because phone.apk had been replaced

Indded it has. I tried to repack the t-mobile phone app with the resources from the standard phone app to give it the vanila custom look and feel .... but it kept crashing when taking phonecalls:(

[Guest starkos]

Indded it has. I tried to repack the t-mobile phone app with the resources from the standard phone app to give it the vanila custom look and feel .... but it kept crashing when taking phonecalls:(

That's a shame, it would have been nice to see! By the way, thanx for all the help/instructions you've posted about all this, it's appreciated :)

[Guest Andy Stormont]

I've just followed the instructions to get vibrate working on 2.1 and it worked great, but 'cat sys/devices/virtual/timed_output/vibrator/enable' still returns '0'.

So I guess this was not related after all.

[Guest eckengucker1]

If the phone is vibrating Android sets this value to "1"

[Guest Andy Stormont]

If the phone is vibrating Android sets this value to "1"

Either way... no changes to the kernel were required.

[Guest eckengucker1]

Yep, was a problem caused by firmware