• 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

Is anyone having trouble with the compass? I'm running 9/26 and the new Cherry kernel
When you say the new Cherry kernel are you referring to the CM7 kerenel that I updated or the M410 kernel that I posted a zImage for? Cause, I didn't change much in the CM7 kernel, just what I listed in the post with the download link. I only touched on the camera, touchscreen, and hdmi, as far as code goes. So, I doubt that the kernel would make a difference as far as the compass is concerned. I am working on a fully merged kernel with all the drivers, but haven't finished yet.
 
Really? I haven't tested it. I'm going to test that tonight.

OK, I have tested out the compass on both CM7 and stock and they aren't any different. It seems to be a hardware issue. I think I can reach out to the sister phones to see if they have working compasses and try to consentrate on their code.
 
camera doesn't work for me on 11.28.2012_Test_B
and looks like i can't connect to wifi going to try test A

Thanks for the feedback. I know chairshot is working on updating the device files and he's working like a madman. I am in the process of downloading test b on the DEV phone right now and I'm going to test the other ROM on my main phone. I'll post back later.

LATER: I just tested test B and it does break the camera. And it did connect to my network, but didn't allow internet access.
 
Is anyone having trouble with the compass? I'm running 9/26 and the new Cherry kernel

Should I assume that you, and everyone else who have responded, are aware of calibration issues inherent to the type of magnetometer used in these phones? It's not specific to the Triumph, but is common in most phones.

In general, any time you're going to do anything that depends on a useful result from the magnetometers, you need to conduct a calibration procedure. The proper way simply consists of rotating the phone about three or four times around each axis. There's an alternate that many consider simpler, that involves waving the phone in a figure-eight pattern; but I don't understand that procedure myself.

I find the Moonblink Tricorder app to be very useful in connection with this calibration procedure. Switch to the
 

Attachments

  • 2012-12-15-15.27.23.jpg
    2012-12-15-15.27.23.jpg
    36.3 KB · Views: 93
I haven't seen this withany of my phones. I know for sure that the DEV phone is on 10-15 code, plus the things that I have added recently. When did you load the ROM? Did you factory reset before loading the ROM? Did you check the checksum?

I loaded it in early November. When i did, i did the factory reset and wiped the davlik cache. I have never heard of the checksum.
 
When you say the new Cherry kernel are you referring to the CM7 kerenel that I updated or the M410 kernel that I posted a zImage for? Cause, I didn't change much in the CM7 kernel, just what I listed in the post with the download link. I only touched on the camera, touchscreen, and hdmi, as far as code goes. So, I doubt that the kernel would make a difference as far as the compass is concerned. I am working on a fully merged kernel with all the drivers, but haven't finished yet.
I misspoke it's this guy http://androidforums.com/triumph-al...tdev-cm7-build-20121015-a-24.html#post5301546
 
I loaded it in early November. When i did, i did the factory reset and wiped the davlik cache. I have never heard of the checksum.

A checksum is a value that is used to confirm the data is the same as when the chucksum was created. Basicly when we make a ROM there's also a MD5 checksum made at the same time. That helps us make sure that the downloads aren't corrupted and causing issues that can't be fixed. If you use ES File explorer you can go to the file and long press it and get the properties screen. On that screen you can get the checksum. Another way is to use a terminal emmulator and type
Code:
md5sum (full path to the file)
and you'll get the same thing.
 
Should I assume that you, and everyone else who have responded, are aware of calibration issues inherent to the type of magnetometer used in these phones? It's not specific to the Triumph, but is common in most phones.

In general, any time you're going to do anything that depends on a useful result from the magnetometers, you need to conduct a calibration procedure. The proper way simply consists of rotating the phone about three or four times around each axis. There's an alternate that many consider simpler, that involves waving the phone in a figure-eight pattern; but I don't understand that procedure myself.

I find the Moonblink Tricorder app to be very useful in connection with this calibration procedure. Switch to the
 
im wondering how often do you guys got random reboot..?
mine reboot at least once every 2-3 times i use it..
and sometime even worst got into continuous random reboot
im pretty sure i installed the rom properly, just making sure im not the only one having this problem.
 
i run latest stable cm7 not the tests with bsyds revamped cm7 kernal and havent had a reboot yet not even while playing games
 
im wondering how often do you guys got random reboot..?
mine reboot at least once every 2-3 times i use it..
and sometime even worst got into continuous random reboot
im pretty sure i installed the rom properly, just making sure im not the only one having this problem.

I think I have had one random reboot, like two sleep of deaths, and just a handful of minor issues on my main phone. On that I one I am running the code that I build from what was current on 10-15 at 16:33. That's what I am running and what my wife is running. On my DEV phone, forget about it. I tourcher that thing LOL. I normally don't have to reboot the for around 150 hours+.

Even then I may have just ran it too hard with some games or stuff and it dies.

My wife on the other hand, has way more apps and won't let me play doctor on her phone too much. And of corse she has more issues than me. She hasn't complained of rendom reboots sence I updated her, just weak battery life. And that's due to apps keeping the phone awake.
 
OK, I was looking at our kernel version and it's listed as 2.6.35.9-perf. I think the group of changes were do to patching that b_random was doing a while back. That and what g60 and mantera and Whyzor... I wouldn't be surprized to find more like darklord. I'm sure you have looked at our github.
 
Reboots are almost always caused by apps. Apps sometimes won't run as well on certain versions of Android, I think. Consider which ones are most active, run all the time, and of course which app you have up when the reboot occurs. Uninstall the ones you suspect until the phone becomes stable.

My Triumph, when running stock ROM, used to reboot often when I had Words With Friends installed. As soon as I removed it, no more reboots. I tried it again once a week for a month with the same results. After rooting and changing to CM7 I no longer had problems with WWF.
 
Should I assume that you, and everyone else who have responded, are aware of calibration issues inherent to the type of magnetometer used in these phones? It's not specific to the Triumph, but is common in most phones.

In general, any time you're going to do anything that depends on a useful result from the magnetometers, you need to conduct a calibration procedure. The proper way simply consists of rotating the phone about three or four times around each axis. There's an alternate that many consider simpler, that involves waving the phone in a figure-eight pattern; but I don't understand that procedure myself.

Thanks for the post!

I have tried the figure-eight pattern several times and never had a working compass. Your suggestion of rotating around each axis WORKED.
 
Did anyone have an issue with the test B ROM not having the camera working?I tried using my camera on the B ROM and it doesn't work.Did a restart then did a wipe then did wipe and reinstall still no camera.Is it just me?
 
Did anyone have an issue with the test B ROM not having the camera working?I tried using my camera on the B ROM and it doesn't work.Did a restart then did a wipe then did wipe and reinstall still no camera.Is it just me?

Yeah, I think it's in the new codecs. I am wondering if some new links need to be made or something. I think with Christmas and all that the development may slow down for a bit. I know that it will on my end. I barely have had time to kick on the main computer lately. I'm not even going to turn on the DEV machine for the next couple of days.

In case I miss some of you,
AFG-100902-008.jpg
 
I don't know if this has been mentioned before but when zooming into pictures in gallery forces the phone to reboot every time. It's not just me, my girl had the same problem. We're on the 1015 build.
 
I don't know if this has been mentioned before but when zooming into pictures in gallery forces the phone to reboot every time. It's not just me, my girl had the same problem. We're on the 1015 build.

I haven't seen that yet. Just to be sure, are you using the gallery that somes with the ROM?
 
Damn, I gotta solute you guys at MTDEV! Technically, I am supposed to assist with support. But you guys devved until Christmas and are still answering support questions. That is fing amazing! I will do some work on my end when I get some stuff sorted out on my end. My Desktop has a dying hard drive and Nexus 7 a failing power circuit (the Google Play team sure is knowledgeable!) I have extended warranties on both, so as soon as the mess is taken care of (hopefully this week) I will be on here a lot more than normal and will finally update my FAQ. Maybe even create one for CM9 as well. Perhaps sharp too, if time permits. My helper with redesigning the FAQ has dropped off the internet for some reason, so it may take a while. I don't mind working over the holiday season since I am off from college until the end of January. I need something to do, so I guess might as well help out.
 
Back
Top Bottom