• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][ALPHA] Triumph CM9 v0.6.17.0 [FINAL]

I'm not a fan of haptic vibrations anyway, it drains a lot of power to run the motor and causes physical stress to the device that could rattle loose weak solder joints over time. The MT is already pretty finicky. Just my personal opinion.
 
To me it just gives me assurance that i hit the button the first time. If it vibrates i know it picked it up. When i don't have haptic feedback i end up hitting the button too many times cause I dunno if it picked it up or not. Especially on the triumph when sometimes it doesn't pick up the first press.
 
Whyzor said:
I'm not a fan of haptic vibrations anyway, it drains a lot of power to run the motor and causes physical stress to the device that could rattle loose weak solder joints over time. The MT is already pretty finicky. Just my personal opinion.
Click to expand...
Whzyor you're always scared of everything :rolleyes:
 
jbarbourx said:
To me it just gives me assurance that i hit the button the first time. If it vibrates i know it picked it up. When i don't have haptic feedback i end up hitting the button too many times cause I dunno if it picked it up or not. Especially on the triumph when sometimes it doesn't pick up the first press.
Click to expand...

Exactly! I would have to agree with you 100%.
 
Success!

My build is working.

  • Compiled from Mantera's latest source
  • Fixed Hapatic feedback on capactive buttons based on yumbrad's fix
  • Includes fixed GPS
  • Home key works
  • Enabled facebook sync hack

update-cm-9.0.0.Triumph-Alpha-0.6.2+FB-Sync-signed.zip

@Mantera The fix for the hapatics is simple. Yumbrad was on the right track. I added "VIRTUAL" to the lines for the 4 buttons in the generic.kl and qwerty.kl file. Let me know if that doesn't make sense.
 
The proper solution to that would be to find the bug that ignores touches, I've only experienced this on the MT on my last 3 android devices and it is very annoying. Haptic is just a workaround for this defect. Or try turning on sound feedback.
 
So far the haptic feedback seems to be fixed in nates build. Also has anyone gave any thought to putting Nova launcher as the default launcher? It fixes the wallpaper scrolling issue and seems to run alot smoother. I know they did it in CM7 with the ADW launcher. Just a thought.
 
jbarbourx said:
So far the haptic feedback seems to be fixed in nates build. Also has anyone gave any thought to putting Nova launcher as the default launcher? It fixes the wallpaper scrolling issue and seems to run alot smoother. I know they did it in CM7 with the ADW launcher. Just a thought.
Click to expand...


Go launcher works too.
 
I think I just found my new daily I don't know what the team did but I can now use Bluetooth and wifi at the same time without wifi cutting out :D onlive runs nice now..other than the force closes every now and again I'm happy :D

Thanks guys!
 
Whyzor said:
I'm not a fan of haptic vibrations anyway, it drains a lot of power to run the motor and causes physical stress to the device that could rattle loose weak solder joints over time. The MT is already pretty finicky. Just my personal opinion.
Click to expand...


I'm with whyzor. If u need confirmation that u did indeed hit the correct button or widget or whatnot, then I suggest turning on audible selection. It can be annoying, I know, but with our finicky triumphs, best to be safe rather than sorry.
 
To each his own. Its working now. Thanks nate, yumbrad, mantera and errybody else involved. I can now use this along with NovaLauncher as my daily rom without goin back to CM7.

Still wondering why the cpu clock speeds are different than before. Shouldn't 1017 MHz be 1024 MHz?
 
jbarbourx said:
To each his own. Its working now. Thanks nate, yumbrad, mantera and errybody else involved. I can now use this along with NovaLauncher as my daily rom without goin back to CM7.

Still wondering why the cpu clock speeds are different than before. Shouldn't 1017 MHz be 1024 MHz?
Click to expand...

They're different because I updated the frequencies to be directly based on 19.2 MHz without needing to be fixed up. It was an experiment to see if that made any difference.
 
sharpe351 said:
Down here in Florida, it found my locale in about 5 minutes the first time. GPS seems to work better if I connect with a Wifi connection first, then go by satellites alone. It takes 1-2 minutes for a good link now.
Click to expand...

What part of Florida..? I'm west central Florida. (Tampa area) haven't got to test ICS GPS because I'm out of state, but on cm7 it takes about a minute.
 
Whyzor said:
I'm not a fan of haptic vibrations anyway, it drains a lot of power to run the motor and causes physical stress to the device that could rattle loose weak solder joints over time. The MT is already pretty finicky. Just my personal opinion.
Click to expand...

Can I turn the Vibration OFF? i am not a fan either.
 
evanrobinson85 said:
What part of Florida..? I'm west central Florida. (Tampa area) haven't got to test ICS GPS because I'm out of state, but on cm7 it takes about a minute.
Click to expand...

Orlando/Apopka area. Tested first with Wifi and sat connection to calibrate, then with sat alone. Takes a minute or two after the initial hit.
 
I know that at one point hardware acceleration was not worked and effected video...but is this still not fixed..i still cant use Netflix or adobe flash. even with the unofficial 0.6.2 someone posted late night. i DID flash 0.6.2 alpha over 0.5.2 alpha without a data wipe(tho i did read instructions) but just because i wanted all my widgets and settings to stay the same... it seems to have updated the os seamlessly even "updating android..." at first boot.

what i wanna know is does hardware acceleration work? Netflix? or in-browser Adobe Flash? should I data wipe then flash the rom again?

PS THANKS FOR MAKING THIS I'm not going back to 2.2!
 
Devs -

Whyzor mentioned in a post (that I can't find again) that you're missing a few binary drivers.

Which drivers are you missing/lacking the source code for, exactly?
 
NateMckn said:
Success!

My build is working.

  • Compiled from Mantera's latest source
  • Fixed Hapatic feedback on capactive buttons based on yumbrad's fix
  • Includes fixed GPS
  • Home key works
  • Enabled facebook sync hack

update-cm-9.0.0.Triumph-Alpha-0.6.2+FB-Sync-signed.zip

@Mantera The fix for the hapatics is simple. Yumbrad was on the right track. I added "VIRTUAL" to the lines for the 4 buttons in the generic.kl and qwerty.kl file. Let me know if that doesn't make sense.
Click to expand...

My keymapping seems to still be off starting with 6.1 and continuing with this one. Whenever I press the Home button it doesnt go home and highlights whatever is on the top left of my screen. Just curious if anyone else is having this problem?
 
Does anybody know if AAC audio is enabled in the camera app? If not, can devs PLEASE enable it!

Also, do I NEED to do a factory reset and wipe all data coming from CM7, or can I simly wipe caches and install?
 
wanfaltm said:
My keymapping seems to still be off starting with 6.1 and continuing with this one. Whenever I press the Home button it doesnt go home and highlights whatever is on the top left of my screen. Just curious if anyone else is having this problem?
Click to expand...

well you quoted the solution....
 
You must log in or register to reply here.
Back
Top Bottom