[Galaxy S II Original Android Development] HardCorePawn:
Ok... so for all those having bad call durations... blame Google or whomever did all the language translations!!?! :silly: :eek:

The default english definition for the Call Duration looks like this:

<string name="callDetailsDurationFormat"><xliff:g id="hours" example="5">%s</xliff:g> hrs <xliff:g id="minutes" example="42">%s</xliff:g> mins <xliff:g id="seconds" example="28">%s</xliff:g> secs</string>

However, I have found that most of the languages only specify minutes and seconds for the call duration:

<string name="callDetailsDurationFormat" msgid="8157706382818184268">"<xliff:g id="MINUTES">%s</xliff:g> mins <xliff:g id="SECONDS">%s</xliff:g> secs"</string>

(ps. that is the definition for English (United Kingdom))

but the call to format the duration is like this:

return mContext.getString(R.string.callDetailsDurationFormat, hours, minutes, seconds);

which essentially gets the string and replaces the "3" values in it with hours/minutes/seconds... unfortunately, if you language specification only has minutes and seconds, then minutes gets filled with hours value and seconds with minutes value... hence the error you're all getting... a quick look shows that out of the 50 language files, only DEFAULT English has hours specified. Every other language is just minutes and seconds...

This is why it is working fine here... as English (New Zealand) doesn't have a translation file listed, so it just uses default English... unlike United Kingdom, which has values_en_rGB/strings.xml... :rolleyes:

So, the good news is that we will be able to fix this at some point :good: The bad news, is that it won't be in 2.0... as we're on a code freeze ;)

I've been testing this... and vibration pattern seems to work fine... multiple shorts, multiple longs, medium, long etc... they all work as intended... And when the phone hits quiet hours, the sounds don't come out but an SMS will still vibrate on the vibration pattern I have set??

Perhaps the custom SMS app you have installed is intercepting SMS notifications?? Have you tried removing the 3rd party SMS app and just tested with only stock SMS app?

I've been investigating this... apparently a user on DorimanX kernel thread seems to think it was fixed... so I posted a question to Dori to see if he had done anything to fix it (as I couldn't see anything obvious in his kernel github), but unfortunately I haven't had a response... :(

if I find time, I'll try out his latest kernel and see if it does it... if it doesn't I'll need to try and figure out how his touchkey backlight code is different from CM :eek:

Yes, as mentioned by Fronti, the new MALI code seems to fix a lot of graphics glitches that were present... vertical continuous in Holo Launcher seems to work fine now, the daydream and nightmode clock updates the digits properly now... :victory:

I believe you mean from inside Contacts -> Groups... Unfortunately NO... the only way to send to multiple contacts is to add them one at a time in the stock Messaging app :rolleyes:

Yeah... I wouldn't say "All bugs and FC's fixed"... :p

We have fixed a lot of stuff... :fingers-crossed: but there will still be bits and pieces that aren't quite 100%... but we're working on it :)

Perfomance and Developer Options were never removed, just hidden... search/read the thread... if you can't do that, you probably shouldn't be messing about with Performance/Developer Options anyway! :p