Tasker (And maybe other apps) issues with MIUI after changing to 2.3.* Source

[Rcocchiararo]

Dunno WHAT miui developers did with the SMS database or sms subsystem or WHATEVER.

But after they started using the 2.3.3 source, SOMETHING changed, and at least for TASKER, it became imposible to use SMS related triggers.

After some testing, i verified that tasker can no longer READ from the message database (i guess thats why it never learns that a new message arrives,)

Vlingo works fine.

Tasker is an EXELENT app for me, but not reason enough to leave MIUI... and tasker developer PENT decided that fixing this is not worth it, so.. my only hope is that someone from here can talk to the chinese devs, to make the SMS database/whatever "standard" again

 

[Chilling_Silence]

What happens if you go into the Superuser app and give Tasker permissions to SMS?

 

[Rcocchiararo]

Nothing, already did that.

http://groups.google.com/group/tasker/browse_thread/thread/0ad752e8957214a0#

there he says investigating and fixing this is not worth his while.

http://groups.google.com/group/tasker/browse_thread/thread/0ad752e8957214a0#

there i tried to convince him otherwise, but i failed, and he has NO idea why tasker is no longer working with miui, so MAYBE if we can get the specific change from the chinese devs, he might wanna fix "me"

 

[rousseauxy]

Would indeed be nice to see this fixed

 

[Giru]

Hi,

It's not really realted to gingerbread, but after version of 1.5.17, MIUI team did something with the global notification vibration. Since that, Tasker (and none of the 3rd party applications) are not able to manage to turn on and off the vibration on the notifications.
Seems to me, MIUI separated all the notification types, SMS and MMS from the main menu, and for the rest of the applications I only can manage it from their own menu. (or on the program tab)
Did anyone experience the same?

 

[Rcocchiararo]

mm, i have not tested that, since i use a plugin for controlling audio manager pro for this.

i know its not gingerbread, per se, but i also know it started arround the time they migrated to gingerbread source.

 

[Giru]

I think they started to use different api calls from base android, and thats why these issues are there.

 

[David Tr]

I'm seeing same thing, and didn't see this thread before contacting the developer Pent.

Yep, doesn't look like he's going to troubleshoot. If we could find the .apk that's doing something different we might be able to replace with the android stock one.

 

[rignfool]

It's not an apk... It's framework...

Sent from my HTC Holiday using Tapatalk 2

 

[M@ttiS]

I think I found a solution:

As a trigger I set Notification for messaging app, then I copy Notification variable to my variable lets say notyf_txt. Then Variable search and replace, search for New message arrived, tick replace, but leave the field empty. the Misc -> Say -> Message from %notyf_txt and it should work Both for senders from your contact and for unknown numbers

Have a good day