-
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]
- Thread starter mantera
- Start date
-
- Tags
- motorola triumph
boomer_jmoore
Android Enthusiast
Well I've never tried them on this build but apparently that launcher seems to work on this build for others (there's a thread here in the root section for the triumph my message was moved to). But in all honesty I tried the dragon go! on miui and could never get it to install cause it was constantly saying incompatible yet other people in the that thread (dragon go! thread here in the roots section of the triumph) claimed that it worked for them no problem. Also, the tsf launcher says its compatible with 2.2 or higher. I'm just totally confused...
thangfish
Android Expert
Not sure if this is related, but I'm back to having BT disconnect 2 minutes after screen off.
This doesn't affect BT headset when playing music... Only my Motorola hands free thing in my truck.
I have re-installed the Wake lock app to hold a PARTIAL_WAKE_LOCK and this fixes the problem.
This is on a clean install also.
@Todd612 -
Bluetooth audio profiles in DSPmanager are working on my BT stereo headset.
thebryceee
Android Expert
I can finally auto connect via wifi whoo hoo!! Still no luck with media controls via wired headset no biggie though. I just got a question though, any reason why I can't download dragon go! or tsf shell launcher? It keeps saying: this app is incompatible with your Motorola WX435. I'm just wondering why I could possibly be the oddball out. I appreciate all that you guys are doing on this rom. Thanks
I reloaded my Stock ROM just to see if TSF Launcher would show up and when I went into it in the market, I wasn't getting the message that said it's not compatible with my device. That message also appears with MIUI installed, so it seems like it's not compatible with the ROMs?
Raptor5150
Android Enthusiast
newest build completely knocks out wifi with bluetooth enabled and connected
i am a sad panda
i am a sad panda
MediocreBadGuy
Android Enthusiast
^same here
Ya I'm not sure OpenVPN is integrated into CM9 yet. I think all the threads I read were people using the (various) OpenVPN installers and going that route.
And clearly one of the settings in the CM7 integrated OpenVPN sets up routes to redirect all the traffic. I just have to figure out how to manually specify that in my ovpn config file. Hopefully upstream CM9 will get it integrated like in CM7 and then things are a lot easier!
Edit: yup, got it working finally. At least, when I am on wifi. When I am on 3G it only quasi works (weather channel loads, google and most sites dont, a couple sites load the html but no images). And I found the CM7 commit that added OpenVPN, but cant seem to find the same in CM9. Guess I need to nag upstream.
Raptor5150
Android Enthusiast
just reverted to a backup... maybe we can have mantera really look into this cause it shouldn't be this buggy
i mean i know the nexus S has better hardware but Bluetooth works flawlessly with wifi on with my sisters stock ICS build i just dont understand why its like a faulty water valve on our phones. Sometimes wifi is allowed in other times its completely blocked off when BT is on.. could someone explain?
piper_
Well-Known Member
just reverted to a backup... maybe we can have mantera really look into this cause it shouldn't be this buggy
i mean i know the nexus S has better hardware but Bluetooth works flawlessly with wifi on with my sisters stock ICS build i just dont understand why its like a faulty water valve on our phones. Sometimes wifi is allowed in other times its completely blocked off when BT is on.. could someone explain?
not to be a prick
alpha
alpha
people, this is NOT designed to be your daily rom "yet"
although it is kick arse for a alpha build, depending on "your needs" it's not ready for prime time yet.
just because something works well on one phone doesn't mean it works as well on the triumph.
the nexus is built by who ...
and the triumph is built by ...
source code anyone ?
Thank You Devs for your free time and effort.
frdmspoplr
Well-Known Member
My thoughts exactly. To be honest, it's a little annoying sometimes seeing all these complaints/bug reports regarding issues that are most likely due to it just being in alpha. If i was in charge, I'd have waited until it was a little more stable to release it (but that's just me
) On top of that, there are certain hardware quirks that may never be fully stable due to lack of driver source code. I haven't even bothered using this yet since its really not meant to be a daily, but to each his own.
Whyzor
Android Expert
I wonder how much of these "problem" reports is what drove Isaac & tickerguy away. These threads are turning out to be general "tech support" areas. Remember, the more you bug a developer about some inconsequential problem the more distractions it adds to prevent them from focusing on the important things. A lot problems are due to CM9, apps, settings, phone quirks...etc.
A good tester has to be able to do some analysis of the problem, reproduce it consistently and with other variables changed or not to narrow down the issue.
A good tester has to be able to do some analysis of the problem, reproduce it consistently and with other variables changed or not to narrow down the issue.
You make a good point and it is worth keeping in mind but on the other hand, it is important for people to give feedback.
The best thing people can do is to be more careful and thorough as you said in there testing before reporting in. Check the thread for answers first, try the common fix methods, etc.
Also didn't tg just want to switch to t-moible because he got a good deal? It seems kinda mean that you are blaming people for driving him away.
The best thing people can do is to be more careful and thorough as you said in there testing before reporting in. Check the thread for answers first, try the common fix methods, etc.
Also didn't tg just want to switch to t-moible because he got a good deal? It seems kinda mean that you are blaming people for driving him away.
This is not the first time you have had a bad attitude here, please understand this is an alpha, and that the developers here and working for free and on their own time. So far they have delivered us an excellent product. The triumph CM9 rom is a lot further along than a lot of other, even more popular phone.just reverted to a backup... maybe we can have mantera really look into this cause it shouldn't be this buggy
i mean i know the nexus S has better hardware but Bluetooth works flawlessly with wifi on with my sisters stock ICS build i just dont understand why its like a faulty water valve on our phones. Sometimes wifi is allowed in other times its completely blocked off when BT is on.. could someone explain?
Whyzor
Android Expert
Anything alpha really doesn't need a whole lot of end user problem reports, it needs contributors to help fix things, anyone can find a problem easily in alpha stage, it's more useful to find solutions than to see how long of a list of bugs can be generated. End user problem reports are really useful for stability stage (beta at least), when the developers can't find problems easily with their limited time, so needs others to help find them.
SamuraiFox18
Android Enthusiast
I agree we need to focus on the bigger problems and not the little ones. Those who complain and moan need to suck it up and grow up. The developers are working frantically on something we don't need to really worry about we need the main ones fixed then it will be a beta rom and the little problems will be fixed its like a new PC operating system coming out. Do you want the internet browser to work or windows explorer fixed up first??? Catch my drift. Camera, USB tether, hdmi, and other big problems not working come first. As they say goes patience is a virtue and those who complain make it harder for the devs. So please sit back relax and just help...please. And I am not trying to be mean just telling the truth.
pbf98
Android Expert
The feedback can be helpful, but theres no need for cluttering up the release thread with all your problems, being this is an Alpha release. There was a separate thread made to discuss things into more detail and get some guidance.
Link:
ICS Developement End User Discussion
As far as what they work on, I leave it up to their discretion. After all it is their time and effort being put into all of this. I am just thankful that there are people out there that can sort through all this and make it work, I look at enough code at work all day haha
Mantera said:
Link:
ICS Developement End User Discussion
As far as what they work on, I leave it up to their discretion. After all it is their time and effort being put into all of this. I am just thankful that there are people out there that can sort through all this and make it work, I look at enough code at work all day haha
lqcorsa
Well-Known Member
I won't install this ROM until it becomes a little more functional (tethering most importantly ...then camera.) I'm really curious though as to how CM9 runs on the Triumph. ICS is supposed to be a bit more cleaned up internally right? Are we seeing noticable differences? Scrolling performance any different? Portrait/landscape orientation change animations?
Intercepter
Well-Known Member
Off topic:
Then don't be
Back on topic:
Maybe the reason that some are having a problem with wifi and bluetooth working together has to do with the fact that the btwlancoex service has been disabled. I know it was maxing out the cpu in CM7 . Was it doing the same in CM9?
Then don't be
Back on topic:
Maybe the reason that some are having a problem with wifi and bluetooth working together has to do with the fact that the btwlancoex service has been disabled. I know it was maxing out the cpu in CM7 . Was it doing the same in CM9?
Raptor5150
Android Enthusiast
yeah i figured that too i mean the file is called bluetooth wirelesslan coexistence isnt it? maybe mantera could send me a hotfix with that file working and intact.. so i can continue to alpha test it
idc if it maxes out my cpu honestly. I kinda want to see if it fixes the issue.. is there anyway to reactivate the file from within cm9 or is it a has to be turned on when its built type of thing?
idc if it maxes out my cpu honestly. I kinda want to see if it fixes the issue.. is there anyway to reactivate the file from within cm9 or is it a has to be turned on when its built type of thing?
yeah i figured that too i mean the file is called bluetooth wirelesslan coexistence isnt it? maybe mantera could send me a hotfix with that file working and intact.. so i can continue to alpha test it
idc if it maxes out my cpu honestly. I kinda want to see if it fixes the issue.. is there anyway to reactivate the file from within cm9 or is it a has to be turned on when its built type of thing?
Try this and let me know if it makes any difference:
1. Using Root Explorer or ES File Explorer, make sure that you have root privileges and mount the file system as read/write and then browse to the root /.
2. In there, open up init.triumph.rc.
3. Change the following lines and remove all of the # symbols:
Code:
on property:init.svc.bluetoothd=running
write /sys/devices/virtual/bluetooth/hci0/idle_timeout 7000
# start btwlancoex
#on property:init.svc.bluetoothd=stopped
# stop btwlancoex
<snipped some code out>
#service btwlancoex /system/bin/sh /system/etc/init.qcom.coex.sh
# user shell
# group bluetooth net_bt_admin
# disabled
# oneshot3. Save the file and then reboot your phone.
I'm wondering if the wifi and bt will coexist better now that the bt is not holding the wakelock constantly.
Whyzor
Android Expert
The btwlancoex locked the CPU at 100% when both are on. The extra bt wakelock in CM7 I added was to keep bt more reliable, regardless of wifi. So far not sure if its needed for CM9, in my brief testing it seemed to always trigger it to be loaded and thats why it prevented deep sleep CM9.
I suspect it may have have something to do with some of the new commits to wifi.c in libhardware_legacy upstream. Since from some of the posts it seemed to have worked before and only acting odd recently. I reverted to using isaac's "outdated" repo and it seems a bit more reliable using both radios in the latest 03-04 CM7. But I dont use both bt and wifi very much to know for sure.
I suspect it may have have something to do with some of the new commits to wifi.c in libhardware_legacy upstream. Since from some of the posts it seemed to have worked before and only acting odd recently. I reverted to using isaac's "outdated" repo and it seems a bit more reliable using both radios in the latest 03-04 CM7. But I dont use both bt and wifi very much to know for sure.
Intercepter
Well-Known Member
so far with both radios on it does not seem to max out the cpu although I am not connected to any bluetooth devices yet
Yeah, in wifi.c in cm7, upstream added the preloader stuff that was in cm9. I don't know how you handled it in your cm7 but it didn't seem to affect anything if I left our previous stuff and just added the new preloader stuff since we didn't actually call it so that it won't break anything else. I just didn't have time to really change over all of our calls in the device repo to use the new preloaders instead of the sdio calls we were doing previously.
It sounds promising. However, we'll see the real test when you connect your BT devices also.
Raptor5150
Android Enthusiast
no changes for me atleased.. still having connection issues with wifi and bluetooth connected to my controller maybe you will have better luck