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

Root [ROM][FINAL] CM7 7.2 RC1 - g60 style [7.11.12]

well i know other CM7's had an Issue with the camera's only when switching from back to front, but i had thought it was fixed, maybe not tho


as for the person who has it stuck in the frozen state, you can try going into applications>manage applications> find Camera.apk and force close it

if it still loads in the frozen state do the above and force close it but also, clear data

Yeah that didn't work either. I ended up restoring a backup I had and switching back to the rear camera while on it. Switched back to this one and cameras working again. Probably try switching to front camera again to see what happens.
 
Yeah that didn't work either. I ended up restoring a backup I had and switching back to the rear camera while on it. Switched back to this one and cameras working again. Probably try switching to front camera again to see what happens.

You may want to stick with version r0.9. I personally find that to be the most stable. r0.10 and r0.11 seem to still have front facing camera issues. As I updated code from CM7 to fix one thing other things always broke. That is the problem with building from source code when the code is constantly updated for devices which are not fully supported. Such as our beloved Triumph. Who ever takes over CM7 will understand the pain. I believe that is why so many developers have moved on. While it's fun to work on it's always going to be an uphill battle until we can get the Triumph to be a fully supported device, which sadly may never happen.

This post is simply intended as an FYI as to let future developers know what they are getting their hands into, and not to scare them off :cool:
 
You may want to stick with version r0.9. I personally find that to be the most stable. r0.10 and r0.11 seem to still have front facing camera issues. As I updated code from CM7 to fix one thing other things always broke. That is the problem with building from source code when the code is constantly updated for devices which are not fully supported. Such as our beloved Triumph. Who ever takes over CM7 will understand the pain. I believe that is why so many developers have moved on. While it's fun to work on it's always going to be an uphill battle until we can get the Triumph to be a fully supported device, which sadly may never happen.

This post is simply intended as an FYI as to let future developers know what they are getting their hands into, and not to scare them off :cool:

That's why I wanted to setup my github. I saw that when Whyzor was DEVing. I think we have a limit for github, though I'm not sure how CyanogenMod does it. i think they have paid for their stuff

OH! I suggest we buy g60 a beer for the work he has done. I'm sorry I couldn't have been in IL to have enjoyed it with you, but you can think of my pixles when you drink one on me.
 
I also just noticed my camera also won't focus at normal distances, only macro shots, on r10. If restoring to stock still didn't fix it, does that mean there was an update somewhere down the line that permanently ruined some of our cameras? I used to be able to fix focus issues with my camera by simply pressing directly down on the sensor progressively more firmly until the focuser got unstuck, but that isn't working anymore. As noted by others, I have to shut off the screen so the camera unfocuses, unlock it and load Camera360 and set it to permanent "infinite distance" focus and then take the picture.

I think you and I have a similar issue, but mine won't focus macro shots either.
Once the camera tries to focus, it blur out, no matter how far or close objects are.
I noticed this on r0.11. I've tried on r0.7, r0.10 and stock, but no luck.
I do not know when this issue began since I don't use the camera much.
 
All,

I have posted one final CM7. This is my favorite version r0.09. I took out all the extra themes, and also updated the Launcher2 from r0.11 as it's cut down in size by 6MB, and has my favorite images. Just wanted to let everyone know this last version is not built from source as I edited an old version of the zip but it still works flawless...well as flawless as CM7 works ;)
 
All,

I have posted one final CM7. This is my favorite version r0.09. I took out all the extra themes, and also updated the Launcher2 from r0.11 as it's cut down in size by 6MB, and has my favorite images. Just wanted to let everyone know this last version is not built from source as I edited an old version of the zip but it still works flawless...well as flawless as CM7 works ;)

Ahhh thank you!! Camera works great now!! Thank you for all your hard work!!! Cheers :D

Now using this with your CynoCream theme and Holo Launcher and it's AMAZING!!
 
Ahhh thank you!! Camera works great now!! Thank you for all your hard work!!! Cheers :D

Now using this with your CynoCream theme and Holo Launcher and it's AMAZING!!

Yeah the Holo Launcher rocks! I will be updating the CynoCream theme in days to come to fix some things I found that are bugging me. I was rocking with the GB rom but I really need texting right now. I am still working on fixing the RIL but it's a son of a gun.
 
For those who care. I have begun the process of forking over the entire set of repos that I need to build our ROM. That way I can cherry pick the parts that get updated by the CM7 team and not break the ROM. I may need help in this because I think I have a limit to what I can have in my github. If it comes to that I'll post and ask.
 
For those who care. I have begun the process of forking over the entire set of repos that I need to build our ROM. That way I can cherry pick the parts that get updated by the CM7 team and not break the ROM. I may need help in this because I think I have a limit to what I can have in my github. If it comes to that I'll post and ask.

If you are forking you have unlimited space. That is the sweet thing of github it's just a copy of a copy but it all goes back to the same place.
 
I just wanted to give a big THANK YOU to g60madman for all his work on this ROM!

I had TG-Reloaded installed on my MT, and while I really liked the look, feel and overall performance of that ROM, I was getting, on average, 6 hours of battery life per charge. I almost drove myself crazy tweaking apps, disabling autoruns, carrying a portable charger, etc. etc. I installed g60madman's ROM and the battery life is significantly better (I typically have 30% remaining after 17-18 hours of average use). I feel like you gave me my phone and sanity back, so.. THANKS! :)
 
I have the same issue.

Mine also goes out of focus when I try to take a picture or switch to the camcorder mode. Initially, it is focused, but as soon as hit the button to take a picture, instead of becoming a clear image, the image become blurry.
I have to turn the auto focus off to get a clear picture.
I just get blurry image for camcorder.

The strange thing is: I went back to r0.7, r0.10 and stock rom. All fresh installed from factory reset and out of focus persist. I wonder if this is my phone.

Anyways, g60madman, I sincerely appreciate the effort you put into this rom.
You made my triumph wonderful. Thanks again man. Are you moving onto Evo?

I've also had this problem. Thankfully I had it once before with Backside IHO on my OV and here's how I solved it, mostly. I looked into the version of the rom beforethe problem surfaced. That was r0.9. I downloaded that version into my PC and extracted the files to open them. Opened up the systen>apps files to find the Camera.apk and save it to my desktop. I uninstalled the disfunctional version in my phone using ROM Toolbox.I use it for maintenance. Then hook the phone up via usb to load the Camera.apk from the desktop to the sd card. Save it to a folder where you keep important stuff. you may need it to fix later screw ups. Unhook you phone, then just run the camera.apk like a regular install app. Once installed, reboot the phone. your camera will work fine now, but the front camera won't be as clear as the back one. you shouldn't have any force closing issues. The camcorder will work without lag as well.
 
Thanks for all you've done g60. I've exclusively used your roms and look forward to your new project. Your work has made the MT into a useable device.

Now for a question. Is it possible to change my MT's Bluetooth MAC with your rom?
 
Thanks again! This will work on other devices, but unfortunately it seems that bdaddr uses manufacturer specific commands, and our Qualcomm chip is unsupported.
 
The audio problem is not fixed. The audio is always on the low setting and it can't be "tricked" into the high volume mode.
 
The audio problem is not fixed. The audio is always on the low setting and it can't be "tricked" into the high volume mode.

Are you using the final version? The audio problem I resolved is the fact that when you have an incoming alert it drops the sound way down. As for the high volume mode I am not aware of that.
 
Is there a fix for the video flicker? I saw something about that somewhere and wanted to ask


im pretty sure its like that with all CM7's try this, its from page 1 of this thread

KNOWN PROBLEMS:
∙ Some videos in portrait mode flickers. (Enable CM settings 180 orientation & flip upside down)

as for something like an official fix, or a permanent fix im not sure
 
Any idea why Sims Freeplay would work on r11 but not your final version? I've tried installing bKernel but it didn't work either. Would it be the kernel then? Do you happen to have the separate kernels to download so I could test it out?
 
Works great for me

Sims Free play works for you? Are you over clocking? Are you under volting? If so, are you using incredicontrol? I wonder why it's crashing on me after the EA symbol... Dunno if it's the over clocking or under volting..

EDIT: Yea I just tried to see if with r11 it would work but it doesn't.. Any ideas as to what could be causing this?
 
Sims Free play works for you? Are you over clocking? Are you under volting? If so, are you using incredicontrol? I wonder why it's crashing on me after the EA symbol... Dunno if it's the over clocking or under volting..

EDIT: Yea I just tried to see if with r11 it would work but it doesn't.. Any ideas as to what could be causing this?

When you are flashing, are you doing a factory reset? Or are you flashing over your old load? It could be a cache issue.
 
OOPS I accidentally hit the thanks button instead of quote. Anyways, I always do data/factory reset then delete cache partition then delete dalvik cache..
 
Back
Top Bottom