• 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]

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?

Usually what I do is get to the point of working with an app and then run the following with the phone plugged

# adb logcat -c
that clears the log form the phone

# adb logcat

Then I run the app or what ever I'm doing. When I'm done testing I throw a Ctrl+c to stop the log.

If you need to setup adb just Google "lazy man adb setup" the user on xda did a nice write up.
 
Usually what I do is get to the point of working with an app and then run the following with the phone plugged

# adb logcat -c
that clears the log form the phone

# adb logcat

Then I run the app or what ever I'm doing. When I'm done testing I throw a Ctrl+c to stop the log.

If you need to setup adb just Google "lazy man adb setup" the user on xda did a nice write up.

I was running the log naked. I didn't know about sending it to a file.
logcat | Android Developers
https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file
I did find those pages on how to use it.
 
I love watching this thread for updates, can't wait until public builds are ready. A couple questions:

You say you rolled back to Froyo video drivers and removed the adreno kernel updates, does this mean we won't have the video performance boost that we got when Whyzor or whoever it was updated the adreno drivers? Not that it really matters to me, I hardly play games. Also, is there any hope of getting Wifi to enable a bit faster over the ~15 seconds it takes to kick in now?

Regardless, amazing work, both of you.

Edit:

Just remembered that a while back someone posted a tweak about renaming /data/data/com.android.providers.telephony/databases/telephony.db and that this would greatly increase the reliability of MMS:

http://androidforums.com/triumph-all-things-root/442626-removing-telephony-db-fix-mms.html

Perhaps something worth trying out while working on MMS.
 
I love watching this thread for updates, can't wait until public builds are ready. A couple questions:

You say you rolled back to Froyo video drivers and removed the adreno kernel updates, does this mean we won't have the video performance boost that we got when Whyzor or whoever it was updated the adreno drivers? Not that it really matters to me, I hardly play games. Also, is there any hope of getting Wifi to enable a bit faster over the ~15 seconds it takes to kick in now?

Regardless, amazing work, both of you.

Edit:

Just remembered that a while back someone posted a tweak about renaming /data/data/com.android.providers.telephony/databases/telephony.db and that this would greatly increase the reliability of MMS:

http://androidforums.com/triumph-all-things-root/442626-removing-telephony-db-fix-mms.html

Perhaps something worth trying out while working on MMS.

Yeah the FPS has slowed down to about 13FPS from about 17-20FPS. It's not a huge loss and I even fired up Temple Run and it plays super smooth. Thanks for the link I will check that out. There was some calls in one of TG's files that uses the db file. I will need to dig into it more. It's getting pretty close for release. It's much more stable than g60 and much more smooth with transitions when using Holo Launcher. However when you switch to the front facing camera it causes some FC's and you need to reboot. If we (me and Chairshot) can get MMS fixed I think it will be ready for at least beta. Even if the camera is not 100% it's pretty darn close.
 
Yeah the FPS has slowed down to about 13FPS from about 17-20FPS. It's not a huge loss and I even fired up Temple Run and it plays super smooth. Thanks for the link I will check that out. There was some calls in one of TG's files that uses the db file. I will need to dig into it more. It's getting pretty close for release. It's much more stable than g60 and much more smooth with transitions when using Holo Launcher. However when you switch to the front facing camera it causes some FC's and you need to reboot. If we (me and Chairshot) can get MMS fixed I think it will be ready for at least beta. Even if the camera is not 100% it's pretty darn close.

Sounds great! If you don't mind me asking, what are your plans once this ROM is stable in all (possible) areas? Do you intend on working on CM9/10 next?

Sent you a :beerglass: :-)
 
Sounds great! If you don't mind me asking, what are your plans once this ROM is stable in all (possible) areas? Do you intend on working on CM9/10 next?

Sent you a :beerglass: :-)

Maybe? I haven't completely decided yet. Will see if we can just get through CM7 first :D
 
I am using your g60 CM7 right now and loving it! I'm glad this ROM is working out well so far and can't wait to use it once it goes into beta. Is there any particular reason you rolled back the video drivers though?
 
I am using your g60 CM7 right now and loving it! I'm glad this ROM is working out well so far and can't wait to use it once it goes into beta. Is there any particular reason you rolled back the video drivers though?

Thanks :D

The main reason is because the drivers are simply the drivers for video. However there was no codec supplied for any of the for /bin/mm* files or /lib/omx* files. There is some petition where users are asking for the codec from Qualcomm. However even with the drivers removed you can not tell the difference unless you run a hardware test to see the FPS. All games I have used, and video's I have played seem to work just fine with no lag what so ever. Also by removing the drivers it's one less variable we need to worry about in stabilizing the ROM. If we can resolve the flicker issue with video playback on portrait we may add the drivers back in.
 
Back
Top Bottom