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

Root [MTDEV] CM 7.2.0 [git updated @ 7/25/2012 4:14 PM MST]

G

g60madman

Guest
README:
This is developmental thread based on CM7.2.0. Listed below are the current working features. If it's not listed it's currently not working.

MTDEV-CM7 is managed by:
Chairshot215
dsmryder
g60madman

------------------
GREEN = SOLVED
ORANGE = WORK IN PROGRESS
BLUE = NEW ITEM / FIX
------------------

ACCELEROMETER
Works

AUDIO
Audio playback is perfect / headset now registers after soft, and hard reboot with out replug

BLUETOOTH
Bluetooth works / Scanning is faster but could be even faster / Reconnect is much faster now after paired, from 6 seconds to 1 second

CAMERA
Camera works including color effects / front facing needs work still / Video for both front & rear do not work

GPS
Works - Faster lock speeds now

HDMI
HDMI registers with cable / Only blue output over screen / Reboot needed to restart HDMI service

KERNEL
Removed Adreno video updates from kernel as there is no codec for drivers

KEYBOARD
Keyboard & Haptic work

LIGHT SENSOR
Automatic brightness is now instant, with out delay

PROXIMITY SENSOR
Works

RIL
Phone works / 3G works / SMS works / MMS now works

USB/SD CARD
Works

VIDEO
Rolled back drivers to Froyo / Flicker is back / Portrait & Landscape fixed / Audio to video sync is perfect

WIFI
Works
------------------

GITHUB
https://github.com/MTDEV-CM7
 
I'll be able to do the occasional testing. Mostly on the weekends. I haven't loaded a new ROM and stuck with it in like a week sense you left for XDA, been crazy busy.:D

EDIT: WOW! That's all that's needed to build? I bet it downloads and builds faster too!
 
While I was testing the Cherry 2.3.4 ROM I built, I tried some kernels and Bkernel CM7 2.3 worked fine except wifi and bluetooth, I didn't test hdmi and stuff but I will tomorrow. The OC kenel wouldn't boot and the other kernels were not triumph kernels. I'll do some testing and see what is working and what is not working. If wifi, BT and ril are working now, how hard would it be to use those drivers to build CM7? Just some thoughts before they get pushed out of my head. I mean they work with our kernel on our phone and are built for GB. Granted, it was on a X6 ROM but... I will test them out in CM7, just putting this out there. :D

Edit: The only thing that doesn't work on the Cherry Kernel is BT.
 
dsmryder said:
I'll be able to do the occasional testing. Mostly on the weekends. I haven't loaded a new ROM and stuck with it in like a week sense you left for XDA, been crazy busy.:D

EDIT: WOW! That's all that's needed to build? I bet it downloads and builds faster too!
Click to expand...

Yeah it downloads much faster since I broke it down to directory structure and it's not hitting like 130 repo's any more. The build time for me is now up to 22 minutes so they changed some stuff from RC1.
 
BSydz said:
While I was testing the Cherry 2.3.4 ROM I built, I tried some kernels and Bkernel CM7 2.3 worked fine except wifi and bluetooth, I didn't test hdmi and stuff but I will tomorrow. The OC kenel wouldn't boot and the other kernels were not triumph kernels. I'll do some testing and see what is working and what is not working. If wifi, BT and ril are working now, how hard would it be to use those drivers to build CM7? Just some thoughts before they get pushed out of my head. I mean they work with our kernel on our phone and are built for GB. Granted, it was on a X6 ROM but... I will test them out in CM7, just putting this out there. :D

Edit: The only thing that doesn't work on the Cherry Kernel is BT.
Click to expand...

Yeah I was messing with the new following kernel from TJ
https://github.com/tjstyle/FIH-Kernel-MSM7x30/

I didn't have any luck with it yet. I have also tried to use some of the libs from the Sharp 2.3.4 Rom you created from nandriod backup. I did have some success with some of the files, but some didn't work at all. Originally when TickerGuy setup the camera he was using the Cherry 2.3.4 libs
https://github.com/tickerguy/android_system_core/commit/1d07b76bafa6d9ca8544aa039530d47f43f7a705

I am still slowly adding in his fixes to the source I have setup. It's still a work in progress as I want to make sure to fix everything to be as perfect as possible. I did try and apply his RIL fixes and it didn't work as CM changed some stuff to frameworks/base so I need to spend some time on it but I will get there.
 
g60madman said:
I have also tried to use some the libs from the Sharp 2.3.4 Rom you created the nandriod on. I did have some success with some of the files, but some didn't work at all. Originally when TickerGuy setup the camera he was using the Cherry 2.3.4 libs
https://github.com/tickerguy/android_system_core/commit/1d07b76bafa6d9ca8544aa039530d47f43f7a705
Click to expand...
There are about ten or so drivers that are the same between Sharp 2.3.5 and Cherry 2.3.4, those are probably the ones that worked. :D Most of them wouldn't work with the Cherry ROM either. I'm gonna extract the Wellcom and a few others to compare the drivers and kernels. I will get back to you when I have more info.
 
What changes did you make to the boardconfig for gps?

**EDIT: and does the platform beign set to msm7k as opposed to msm7x30 break anything? As in where I am building off the old source from Whyzor/you/mantera/isaacj87/tickerguy, would it break anything to use the msm7k board or should I stick with the msm7x30
 
b_randon14 said:
What changes did you make to the boardconfig for gps?

**EDIT: and does the platform beign set to msm7k as opposed to msm7x30 break anything? As in where I am building off the old source from Whyzor/you/mantera/isaacj87/tickerguy, would it break anything to use the msm7k board or should I stick with the msm7x30
Click to expand...

The msm7k breaks proximity and also accelerometer still working on fixing that. Here is the GPS section I now have in the BoardConfig.mk

*EDIT the msm7k seems to fix the flicker issue with video. My guess is some kernel issues

*EDIT 7/19/2012
OK so I figured out the difference in msm7k and also msm7x30. It's simple calls into the code which compiles different things based on that call. Here is a good example of some code. There is snippets of code like this in tons of Androd.mk files through out all the source.

https://github.com/MTDEV-CM7/hardware/blob/cm7/msm7k/Android.mk

If you look at the code it clearly states to use one feature for msm7x30 and one feature for qsd8k and another for msm7k. The reason I choose to go with msm7k is an article I read on xda based on CM9 that users have been using stuff like msm7x30, however Qualcom has never used those features in source code so some one stated why would we redevelop the wheel. Anyways I honestly don't enough about the code to tell you what our phone needs and doesn't need.

What I do know is by using the msm7k I have fixed the flicker issue. Which means something is messed up on the msm7x30 side of the code. As for the video/audio out of sync issue, that is still something I am working on but the msm7k has nothing to do with the accelerometer which is now fixed and I am still using the msm7k.


# GPS
BOARD_USES_QCOM_HARDWARE := true
BOARD_USES_QCOM_LIBS := true
BOARD_USES_QCOM_LIBRPC := true
BOARD_USE_QCOM_PMEM := true
BOARD_USES_QCOM_GPS := true
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := triumph
BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION := 50001
BOARD_GPS_LIBRARIES := libloc_api
BOARD_GPS_LIBRARIES := libgps
BOARD_VENDOR_QCOM_GPS_NEEDS_LNA := true
BOARD_VENDOR_QCOM_GPS_HAS_BROKEN_XTRA := true
BOARD_VENDOR_QCOM_AMSS_VERSION := 1200

Some of these options are already used in the old BoardConfig.mk you are using, I simple restructured it. Also you can update the gps.conf. I have not pushed yet so use Chairshot215 as he is the one that fixed it.

https://github.com/Chairshot215/android_device_motorola_triumph/blob/gingerbread/files/etc/gps.conf
 
jhonka232 said:
MMS fix is easy, just use the CDMASMSDispatcher.java from here:
link
Click to expand...

The code is already there. The problem is I am updating our mms to the proper standard based on ufprofurl from VM. If you dive into the device files/overlay/packages/mms and drill down you will find an XML with new setting I'm working on. Basically I'm trying to fix mms so the images and attachments are larger based on VM settings.
 
b_randon14 said:
Hey g60, do you think having the device files setup this way will make it harder to pull in upstream changes?
Click to expand...

The whole idea for my madmanness is I broke off the main line. Since 7.2.0 is a final type release they wont be adding many more features now that its out of RC. My plan is to no longer upstream unless something major changes. That way we can work on the code and fix problems and build it specificly for the triumph. Sadly we will never get a nightly as there is just to many "triumph" type hacks needed to make our phone work which break others. Just like the audio hack. I honestly believe this the main reason VM and MOTO choose not to upgrade our phone.
 
Yeah it is sad. I still pull in upstream changes to my build but then again I run into problems here and there too. But I think some things will never be 100% like audio, video, wifi, Bluetooth, mainly because of inferior hardware ans horribly written drivers.

Like now I have wifi issues on my rom. I don't know if its upstream changes, or build.prop additions i added or both. I used chairshots build prop tweaks along with mine and now wifi is all borked. And for a while on.my rom if you rebooted with wifi turned on, then whenever you would go to turn it off it would constantly turn its self back on. You would have to basically turn it off then shut it down real quick before it turned back on. Craziness I tell ya.

GPS is much better now though!!

Ideally it would be cool to complete port all the hardware changes into a new kernel by hand, then rewrite the kernel modules, drivers and libraries got our hardware and say to hell with what Motorola gave us. Then we could tweak the libraries and modules the way we needed to so that they would always work right. Way to much work though and I wouldn't know where to begin!!
 
Maybe something in the Build.prop Tweaks causing the wifi turning on issue. Not sure though, received a PM from someone telling me their wifi had been turning itself on but then he also told me he flashed again and had not been able to reproduce the issue. Had not been able to reproduce it myself so had just figured it was one of those off things and it would definitely be an issue I would have gotten an ear full over.
 
dsmryder said:
I have been poking around. I probably should have looked at your system.prop first, huh?
link
Click to expand...

Since my device files are still in alpha it's hard to just copy and paste since I have moved things around. Here is what you should add for GPS on my g60madman github.

# GPS
BOARD_USES_QCOM_GPS := true
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := triumph
BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION := 50001
BOARD_GPS_LIBRARIES := libloc_api
BOARD_GPS_LIBRARIES := libgps
BOARD_VENDOR_QCOM_GPS_NEEDS_LNA := true
BOARD_VENDOR_QCOM_GPS_HAS_BROKEN_XTRA := true
BOARD_VENDOR_QCOM_AMSS_VERSION := 1200
 
g60madman said:
Since my device files are still in alpha it's hard to just copy and paste since I have moved things around. Here is what you should add for GPS on my g60madman github.

# GPS
BOARD_USES_QCOM_GPS := true
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := triumph
BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION := 50001
BOARD_GPS_LIBRARIES := libloc_api
BOARD_GPS_LIBRARIES := libgps
BOARD_VENDOR_QCOM_GPS_NEEDS_LNA := true
BOARD_VENDOR_QCOM_GPS_HAS_BROKEN_XTRA := true
BOARD_VENDOR_QCOM_AMSS_VERSION := 1200
Click to expand...

I saw in your system.prop you have your gsm.operator.numeric and your ro.cdma.home.operator.numeric set like tickerGuy's befor he had mms working.
gsm.operator.iso-country=us -gsm.operator.numeric=311490 +gsm.operator.numeric=310000 ro.telephony.gsm.ecclist=110,112,119,911 ro.telephony.cdma.ecclist=110,112,119,911 ro.telephony.ecclist=08,000,110,112,118,119,911,999 ro.telephony.num.auto.hyphen=true ro.telephony.gsm.spn.shortname=true-ro.cdma.home.operator.numeric=311490 +ro.cdma.home.operator.numeric=310000
 
dsmryder said:
I saw in your system.prop you have your gsm.operator.numeric and your ro.cdma.home.operator.numeric set like tickerGuy's befor he had mms working.
gsm.operator.iso-country=us -gsm.operator.numeric=311490 +gsm.operator.numeric=310000 ro.telephony.gsm.ecclist=110,112,119,911 ro.telephony.cdma.ecclist=110,112,119,911 ro.telephony.ecclist=08,000,110,112,118,119,911,999 ro.telephony.num.auto.hyphen=true ro.telephony.gsm.spn.shortname=true-ro.cdma.home.operator.numeric=311490 +ro.cdma.home.operator.numeric=310000
Click to expand...

Yeah I have gotten that far with the code yet. I based a lot of rebuilt device files off Tickerguy's and some of issac/mantera/whyzor device files. It's still a work in progress. My focus right now is figuring out the video which I have a beat on, and will see if I can fix it. Trial & Error, lots of logcat's and google searches out the whazoo :D pretty soon we should have a stabilized CM7 for our device! Now where is the fixed camera :) :) :) :)
 
g60madman said:
Yeah I have gotten that far with the code yet. I based a lot of rebuilt device files off Tickerguy's and some of issac/mantera/whyzor device files. It's still a work in progress. My focus right now is figuring out the video which I have a beat on, and will see if I can fix it. Trial & Error, lots of logcat's and google searches out the whazoo :D pretty soon we should have a stabilized CM7 for our device! No where is the fixed camera :) :) :) :)
Click to expand...

If you post them on the week end, I can run some tests for you. Just tell me what you are looking for. That way you can get a confirmation or more test ROMs out of the way.
 
dsmryder said:
If you post them on the week end, I can run some tests for you. Just tell me what you are looking for. That way you can get a confirmation or more test ROMs out of the way.
Click to expand...

Yeah right now it's just fixing and testing. Hows the camera coming? Be nice to get a working camera (hint hint). Right now I have nothing but fail for the default camera.apk. Hows your code coming?
 
g60madman said:
Yeah right now it's just fixing and testing. Hows the camera coming? Be nice to get a working camera (hint hint). Right now I have nothing but fail for the default camera.apk. Hows your code coming?
Click to expand...

The camera works fine using the code I forked from your g60style. I wonder if the issues with the camera have less to do with the camera and more to do with a shared library:confused:
 
g60madman said:
Honestly I need to run a logcat

This maybe the case have to spend some more time on it.
Click to expand...

What would be the right way to do a logcat. I think I can connect to the phone, if not I think I can figure that part out.
What I mean is, would I start it, then try to open the camera and see what happens?
 
You must log in or register to reply here.
Back
Top Bottom