• 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

Bsydz, it may be a good idea to do that debugging kernel for CM9 and CM10, too. Although I wouldn't recommend using CM10 yet, I'm sure rukin would have an easier time fixing things with some debugging, unless of course he has a custom debugging kernel already. I wouldn't try the camera tweaks on CM9 or 10 though, we want a clean slate for fixing that thing. If possible, the newer drivers may assist CM9 too. At least I suggest you put out debugging kernels for all the CMs so bug reporting and log collecting would be easier on MTDEV. You'd probably even save yourself some headaches down the road.
 
Thank you all Devs for all your hard work. Of course I'm sad to hear of g60's decreased activity with the Triumph, but I know the rest of you will carry on where he left off.

I've had a couple issues that I've been experiencing at least since the 1015 update and was waiting for a new version to get released to fix them.

Multiple texts received. This was mentioned in another thread so I know there are at least a few other people experiencing this. I've been receiving anything from 1-10 duplicate message from friends. There doesn't seem to be any rhyme or reason to it: signal strength, carrier of sender, etc.

Sleep of death. I've heard this term tossed around a few other places, so hopefully I'm using it properly. I'll go to check the time on the Triumph and it doesn't immediately light up. I also once noticed the Triumph won't even accept a charge (or at least not show a notification light indicating such) when it's in SOD. Obviously the only solution has been to pull the battery and restart.

Any help is greatly appreciated. I'll probably wait a little longer in hopes a new update, if none appears I guess I'll wipe all caches and such and do a fresh flash.
 
w2rl0rd said:
Thank you all Devs for all your hard work. Of course I'm sad to hear of g60's decreased activity with the Triumph, but I know the rest of you will carry on where he left off.

I've had a couple issues that I've been experiencing at least since the 1015 update and was waiting for a new version to get released to fix them.

Multiple texts received. This was mentioned in another thread so I know there are at least a few other people experiencing this. I've been receiving anything from 1-10 duplicate message from friends. There doesn't seem to be any rhyme or reason to it: signal strength, carrier of sender, etc.

Sleep of death. I've heard this term tossed around a few other places, so hopefully I'm using it properly. I'll go to check the time on the Triumph and it doesn't immediately light up. I also once noticed the Triumph won't even accept a charge (or at least not show a notification light indicating such) when it's in SOD. Obviously the only solution has been to pull the battery and restart.

Any help is greatly appreciated. I'll probably wait a little longer in hopes a new update, if none appears I guess I'll wipe all caches and such and do a fresh flash.
Click to expand...

I need to look into how the logcat works. This will be esential infiguring out certain things, like SoD. Maybe someone who knows can start a new thread before I get home to help short cut the research for me.

Hey g60. I think this could be a good app idea for us. Something that will copy the logcat periodicly so it doesn't get lost because of a crash.
 
chilz said:
running super smooth on 1015 build and switching between cameras are super smooth good job bsyds im loving it do u plan on porting the mi410 rom if all works out
Click to expand...
Thanks, this may help, but editing smali code is a pain, the framework will have to be modified to work with our 3G/Data. Also, we have to put together a Ramdisk for the boot.img, cause I am working on the zImage (kernel), you need both to be able to create a boot.img. Basically, there is a bunch of stuff that needs to be worked out. I knew we were using the Cherry camera lib and after comparing all the X6 ROMs there were no differences in anything that mattered, look at the third post here http://androidforums.com/triumph-all-things-root/655402-dev-bsydz-triumph-x6-port-encylopedia.html
So I saw some differences in the CM7 kernel and the M410 kernel, that sounded related to some of the issues that have been talked about, and essentially updated the kernels drivers. That is where the touchscreen drivers came from for the Sharp custom kernel also. So, most of this is a factory upgrade cause the kernel history is the same as our stock kernel, up to a certain point, and the 410 kernel had like five months of updates beyond.

MikeRL said:
Bsydz, it may be a good idea to do that debugging kernel for CM9 and CM10, too. Although I wouldn't recommend using CM10 yet, I'm sure rukin would have an easier time fixing things with some debugging, unless of course he has a custom debugging kernel already. I wouldn't try the camera tweaks on CM9 or 10 though, we want a clean slate for fixing that thing. If possible, the newer drivers may assist CM9 too. At least I suggest you put out debugging kernels for all the CMs so bug reporting and log collecting would be easier on MTDEV. You'd probably even save yourself some headaches down the road.
Click to expand...
I may do some builds, I'll have to look and see what I can do. A lot of debugging isn't needed, some of it was turned off to thin the logs to find errors easier, if I remember correctly. It was a long time ago that most of that happened. I'm just trying to help where I can. I left the debugging in my custom kernel and don't see any real impact, I used the stock source and ran with that, so all of the debugging is intact. I don't really know the origin of the kernel source for MTDEV CM7, I just knew it was working and didn't want to go crazy changing stuff.

As far as CM9 goes, it all depends on which camera lib is used in the ROM. If we use the same camera lib in CM9 then this may help, if it can be done that way. The device files have been configured so many different ways since Isaac first started that it is hard to keep up. I'm still picking away at getting this phone to at least GB or higher, that is my goal. I just want to see our phone at least with a solid platform above Froyo. It has nothing to do with hating Froyo, I have been running the Sharp 2.2.2 on my good phone for months now, I am pissed that all our sister phones got GB and ours and one or two of the 10 variants didn't. They all work except data, and the one we have the best shot at getting to work doesn't, because of a kernel/firmware update, that doesn't affect the phones with SIM cards.

Any way we'll get it some day.
 
So, if anyone tried BSydz's kernel, can you please confirm that it fixes issues with camera (FCC, video recording click and etc.)
 
Izzard said:
So, if anyone tried BSydz's kernel, can you please confirm that it fixes issues with camera (FCC, video recording click and etc.)
Click to expand...

I am running the new kernel. No fc on FFC. I do still have the over-active auto focus while in video mode, which causes clicking. Touch screen seems more responsive. Thanks
 
dsmryder said:
I could look into what Whyzor did to remove the auto focus while in video mode if enough people say so.

Holla
Click to expand...
That might be a good idea for a test. Not trying to be lazy, but if somebody could let me know exactly what is happening when the clicking occurs, it might help. I haven't spent a whole lot of time on CM7 and haven't experienced it. Like which camera and what types of shots(far, close, action), and which version of CM7 cause I know some people are using some of the test builds. It should be compatible across most CM7s but some older ones may have had a different ramdisk in the kernel. Like I said I don't know exactly where the kernel came from or who has done what, so I didn't want to go through changing a bunch of stuff.

I added in things that were missing like continuous auto focus and a bunch of other stuff. There were settings for the camera throughout the kernel not just the individual driver files. I also edited all the files by hand, it wasn't a big deal as they were almost the same , so I may have missed something. He may have removed what he was seeing as errors but were missing calls in the kernel and not the system, or I may be wrong. I didn't start developing til after CM7 was handed over to g60, so while I read most of the threads back then, it never went in to my working knowledge of the system.


Thanks for the feedback everybody.
 
BSydz said:
That might be a good idea for a test. Not trying to be lazy, but if somebody could let me know exactly what is happening when the clicking occurs, it might help. I haven't spent a whole lot of time on CM7 and haven't experienced it. Like which camera and what types of shots(far, close, action), and which version of CM7 cause I know some people are using some of the test builds. It should be compatible across most CM7s but some older ones may have had a different ramdisk in the kernel. Like I said I don't know exactly where the kernel came from or who has done what, so I didn't want to go through changing a bunch of stuff.

I added in things that were missing like continuous auto focus and a bunch of other stuff. There were settings for the camera throughout the kernel not just the individual driver files. I also edited all the files by hand, it wasn't a big deal as they were almost the same , so I may have missed something. He may have removed what he was seeing as errors but were missing calls in the kernel and not the system, or I may be wrong. I didn't start developing til after CM7 was handed over to g60, so while I read most of the threads back then, it never went in to my working knowledge of the system.


Thanks for the feedback everybody.
Click to expand...

When the camera focuses it will reach a certain point where the lens either hits the cover or the mechenisim unseats. Like a car's side view mirror. I'm sure almost everyone has had a car with a mirror that clicks and bounces instead of moving.
 
dsmryder said:
When the camera focuses it will reach a certain point where the lens either hits the cover or the mechenisim unseats. Like a car's side view mirror. I'm sure almost everyone has had a car with a mirror that clicks and bounces instead of moving.
Click to expand...
Thanks, I remember that part, but is it the front or back cam? Also, does this affect all phones or just a handful? Sorry I just haven't run CM7 enough, so I am not up on everything. Now that I have more knowledge, I am just trying to fix what I can where I can. When I was testing for click I was using the FFC and just moving all around from close to far and everything in between and did not experience any clicks. Just trying to isolate the problem, I was under the impression that it was the FFC. I'm just jumping back in to CM7, the last time I really looked at it before recently, was around when g60 took over, and a lot has changed.
 
BSydz said:
Thanks, I remember that part, but is it the front or back cam? Also, does this affect all phones or just a handful? Sorry I just haven't run CM7 enough, so I am not up on everything. Now that I have more knowledge, I am just trying to fix what I can where I can. When I was testing for click I was using the FFC and just moving all around from close to far and everything in between and did not experience any clicks. Just trying to isolate the problem, I was under the impression that it was the FFC. I'm just jumping back in to CM7, the last time I really looked at it before recently, was around when g60 took over, and a lot has changed.
Click to expand...

The FFC is a fixed focus camera. The back one can focus. I wonder if the people who have a clicking camera will have the clicking under stock. Something else to test.
 
I have found the date where Whyzor released the update where the camera focus was disabled for video. I can't find the commit in his github, though. And it's late. I also downloaded your Sharp (I think) source and was just starting to glance at it.

EDIT: There are a bunch of updates to things that are outside the kernel. I wonder if we can find those updates and maybe intergrate them also?

EDIT2: I just finished my test. I have added a five second delay before the phone will shut down on a critical battery state. I'll make sure chairshot knows about it and maybe adjust it as five seconds seem to be too long just to make sure a picture is captured. Let us know before the next release.
 
dsmryder said:
I have found the date where Whyzor released the update where the camera focus was disabled for video. I can't find the commit in his github, though. And it's late. I also downloaded your Sharp (I think) source and was just starting to glance at it.
Click to expand...
I have 2 kernels in my github, both are built up from stock source, one is the Sharp kernel(Triumph source code) and one is the stock M410 source with all the stuff from the Sharp kernel added in and a few fixes to make it work on our phone. I pulled the stock CM7 the other day, so I'll look in to it also. Good luck.
 
I'm currious which versions the best of cm7 i haven't updated since the 9-26-12 i know there's the 10-something one and the two betas which one's the best? my data speeds kinda suck in some areas i know thats kinda normal but when u have -90dBm or i think that would be 3 bars idk haven't used bars in a while lolz but had no data connection at all well that was working with 3g icon in top so figure i'd try fresh install and read some changes to gps were made again better lock times would be great lolz thanks for help :D
 
going to try beta 2 figure why not backed up all apps and data that i needed with titanium backup pro :D so should be fine if not i'll go to the 10-15 one
 
I've noticed a very small issue which may not even merit addressing. On 10-15, when in a text message with the keyboard up, hitting the home button will bring up the home screen moved half way up the screen. As in, you see the bottom bar running across the middle of the screen with the bottom of the screen being black. Pressing the home key two more times fixes this, but I haven't seen it mentioned anywhere else so I thought I'd mention.
 
rpm14 said:
I've noticed a very small issue which may not even merit addressing. On 10-15, when in a text message with the keyboard up, hitting the home button will bring up the home screen moved half way up the screen. As in, you see the bottom bar running across the middle of the screen with the bottom of the screen being black. Pressing the home key two more times fixes this, but I haven't seen it mentioned anywhere else so I thought I'd mention.
Click to expand...

I haven't seen this with any 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?
 
You must log in or register to reply here.
Back
Top Bottom