-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM] MTDEV-CM7 build 2013-03-03
- Thread starter Chairshot215
- Start date
-
- Tags
- motorola triumph
dsmryder
Android Expert
We have our own kernel preloaded. It has driver that have been set up specificly for the ROM, but most GB kernels for the MT will work with it.
Is there a sertain feature you're looking for?
dsmryder
Android Expert
triumph18299
Lurker
Thanks dsmryder. Reflash did the trick for the vibrate only incoming calls issue. Not a problem since, except for random shutdown....say weekly. 0926 build related or something with the increased capacity e-bay purchased battery? Pulling the battery is the only way the phone will boot when this happens.
dsmryder
Android Expert
I'm glad I could help. As for the reboot? I don't get random reboots. I have had my phone running for over a week at a time, my wife hasn't had a reboot yet. She's running on code from 9-9, though. The only time I get a reboot is when I get crazy with the kernel (another on the way to test, by the way). And on that note. I know that the kernel won't respect voltages below 800mV. Maybe if I find another part of the code or figure out the 3.0 patch I found.
I hope I didn't double post that
b_randon14
Android Expert
Hey g60, that fix for muting calls in the phone apologize is already in our source tree. So it must be something else causing this to happen. Just thought I'd give a heads up.
Chairshot215
Android Expert
Anyone down for some beta testing??
Trying to get as much feedback as possible but put this build together over the weekend. For the most part added a bunch of permissions I found why unpacking the boot.images from Bsidz experiment Nandroids including a few media related. Also have replaced the init.qcomm scripts with those used in Sharp 2.3.5 inside etc and removed a few proprietary files that have been added in from Triumph Stock I have only otherwise seen in Froyo Roms among our device family tree. Anyhow have been testing now for a few days along with others but have limited access to Bluetooth devices so would feel more comfortable with more feedback in that area or in general before officially pushing or adding.
FOR Testing Only
MTDEV-CM7-20121006.zip
Trying to get as much feedback as possible but put this build together over the weekend. For the most part added a bunch of permissions I found why unpacking the boot.images from Bsidz experiment Nandroids including a few media related. Also have replaced the init.qcomm scripts with those used in Sharp 2.3.5 inside etc and removed a few proprietary files that have been added in from Triumph Stock I have only otherwise seen in Froyo Roms among our device family tree. Anyhow have been testing now for a few days along with others but have limited access to Bluetooth devices so would feel more comfortable with more feedback in that area or in general before officially pushing or adding.
FOR Testing Only
MTDEV-CM7-20121006.zip
M
mr0chris
Guest
I have a few devices I can test with this build, I'll report back once I flash and try it out
Edit: Working like a charm! No issues with my bluetooth speakers
Cool, I just downloaded the CM7 code and was gonna start from scratch and see what I could do, the MTDEV team CM7 source is soooo different than the CM7 code I had on my HD from like 4 months ago. We should be able to use most of the qualcomm stuff from the zues device file setup, I think G60 was talking about it sometime ago. I wanted to use the ICS kernel from the Xperia Play, and camera drivers, to see if we could get something going on the ICS camera issue, but at that point I had never looked at kernel source before. I have high hopes for getting the Sharp 2.3.5 kernel on our phone, I just need some more time with the kernel. I have found the baseband issues in all of the X6 kernels I have source for, Mi410_v3.18D_kernel_source_2.6.32.9 and both tj_styles kernels. Also after flashing some nb0s again, I found that bluetooth worked fine with an nb0 flash but just the kernel and ROM from the X6 variants bluetooth doesn't work. It has to be a firmware mismatch in the kernel, that is one issue in the 2.6.35 kernel. Hopefully we can get a rock solid system that every single thing works (up to hardware limitations of course) above Froyo on our device soon.
Chairshot215
Android Expert
I have on the side been working on allot of the same but more for learning and haven't been expecting much as I know nothing on the Kernel side. Have tried messing with the Sharp 2.3.5 Kernel the last few days but as far as I have gotten is the M logo and being able to run a few adb commands like reboot recovery lol, no logcat. Found a few lines in the Sharp 2.3.5 init.rc mentioning adb and the Kernel I was going to play around with tonight along with a few board.config tweaks as a blind shot in the dark attempt at getting a logcat . Have been doing some comparisons with TJ Styles Kernel and Doomloards x6 Kernel based I believe from the Spice Kernel source. Was just now looking over past commits for why allot of the bluetooth permissions for CM7 in the init.triumph.rc have been commented out. Otherwise has been a side project starting over to see if I have learned enough to be able to do so and identify the gaps in what I still need schooling. Have stayed pretty far away from the Kernel up until this point.
Edit: Will definitely let you know if I stumble upon anything of value why poking around.
thangfish
Android Expert
I just want to say that I have been running this since Sunday and haven't had time to test BT.
I apologize for that, but I WILL give it a thorough work out this weekend if not sooner, and report back.
Thanks for this build btw.
tmicrd68
Member
Flashed ROM last night & had no issues with Bluetooth connecting & using my RF-MAB2 headphones as well as monster iclarity speakerphone.
On another note, while still on mtdev 7.2 9/21 build earlier yesterday , I was unable to download opera mobile update via play store (had the 'not compatible with this version...' message). However, had no problem doing so with this ROM.
Overall ROM is snappy works well for me.
dsmryder
Android Expert
Were you you useing a thunderprop of some sort?
b_randon14
Android Expert
Just want to let everyone know I had been having wifi issues where it would connect to a network but would never obtain the ip address and therefore I never had internet, and I read a post somewhere saying that on another phone the video.accelerate.hw build.prop line had been causing wifi issues, so I commented it out and wifi will connect and so far I haven't had any issues with wifi staying on even when trying to turn off after a reboot with wifi on. Not sure how this is correlated but if I were you all I would remove this line anyways as we don't know if it really even helps. Just thought I'd put that out there!
dsmryder
Android Expert
I've had some issues, but I wasn't able to track it down. I also just bought a new router and wasn't sure if it was that or not. Too busy at work to play with my phoneLOL
I've had a couple of things happen with WiFi on the most recent build.
First is, sometimes when enabled from the widget WiFi never actually turns on. It's a solid line on the bar and should be on, but for some reason never actually kicks in. Going to the Settings menu and turning it off then back always fixes this.
Second, sometimes when enabled the WiFi icon will appear on the bar and then immediately disappear after a second or two, be replaced by the 3G icon, which after a few seconds itself disappears, then the WiFi icon comes back and stays as it is meant to.
Both of these have only happened a couple of times so far.
First is, sometimes when enabled from the widget WiFi never actually turns on. It's a solid line on the bar and should be on, but for some reason never actually kicks in. Going to the Settings menu and turning it off then back always fixes this.
Second, sometimes when enabled the WiFi icon will appear on the bar and then immediately disappear after a second or two, be replaced by the 3G icon, which after a few seconds itself disappears, then the WiFi icon comes back and stays as it is meant to.
Both of these have only happened a couple of times so far.
tmicrd68
Member
No.
jmulvay
Member
Mrsdl cm7 cyan mixer theme is a very nice theme
For cm7.
By far nicest icons, keyboard, even the
Menu, and apps store are themed.
I'll try and leave the link.
Hope android forum alows it.
https://play.google.com/store/apps/...medium=organic&utm_term=mrdsl+cm7+mixer+theme
For cm7.
By far nicest icons, keyboard, even the
Menu, and apps store are themed.
I'll try and leave the link.
Hope android forum alows it.
https://play.google.com/store/apps/...medium=organic&utm_term=mrdsl+cm7+mixer+theme
I experienced a problem today that probably is not related the ROM, but I thought I'd share it in hopes of getting it resolved. I've been using Holo Launcher and Holo Locker almost from the first day I loaded the ROM. It has always worked great and never really had any issues with it. The launcher is still working fine, but the locker started FC'ing immediately after updating to v 1.1. I uninstalled / reinstalled, cleared the app cache, fixed permissions, etc. Finally I went back to Titanium and restored the previous app version. Works fine. Updated to the new version and back FC'ing. I'm back on the previous app version and everything is fine. I've turned off update notifications, but still get them sometimes. Sounds like it is the app, but I wanted to make sure it was not "just me" and my configuration. Anyone else out there running 20120926 and Holo Locker v1.1?
Also found a tip on using multiple lockers.... Tablet Tweaks. There is a setting to turn off the stock locker. Tablet Tweaks doesn't show up under our CM7 Settings, so I d/l AnyCut and created a shortcut to TT. Now I can call up TT anytime.
Link to Anycut, which is becoming harder to find:
Also found a tip on using multiple lockers.... Tablet Tweaks. There is a setting to turn off the stock locker. Tablet Tweaks doesn't show up under our CM7 Settings, so I d/l AnyCut and created a shortcut to TT. Now I can call up TT anytime.
Link to Anycut, which is becoming harder to find:
thangfish
Android Expert
In my testing BT connects and works without issue...
However (you knew it was coming) settings don't seem to stick.
I have to re-pair devices (moto hands free device and moto stereo headset). Also I always change my device name to "Thangfish's Triumph" and that doesn't stick either.
Can anybody else corroborate?
Could be just me.
I use extra batteries, so it could be after a reboot.
Edit:
Looks like simply turning off BT looses device name
Chairshot215
Android Expert
Thats funny because I don't think the MTDEV CM7 has ever had them. Thought the menu looked nice and sleek without them or the system update settings that FC when selected so removed them from the menu. Also for the same reason you had mentioned, took 3 or 4 month for someone to have noticed. Can still be accessed if desired by selecting a short-cut by pressing anywhere on the home screen.
