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

Root [ROM] CM7 TG-Reloaded (Final: 03-25)

I'm assuming the standard path to toggling the wifi is the same as the notification bar/settings for wifi. Juice Defender may be using another path. Just curious, The code to check for & release wakelocks is run every time the power button is pressed to put it to sleep & back. If cycling through that still doesn't release the wakelock. (can also be seen in terminal emulator with: 'cat /proc/wakelocks' last section), then the wifi flag may not be recognized. I may look into putting setting & resetting that flag somewhere more noticeable in the kernel than where Tickerguy has it.

Maybe JD only disables or blocks traffic through the wifi, instead of actually powering it down. I just checked, the libra_loaded flag is being set & reset in the kernel:

drivers/net/wireless/libra/libra_sdioif.c
libra_sdioif_init()
libra_sdioif_exit()
 
moonknightus said:
Any idea what causes the glitchy video in portrait mode? I know it's a known issue but it doesn't just affect video players (ie. youtube, etc.). If it was just a matter of needing to switch to landscape to watch videos, I'd have no problems but this also affects my favorite weather apps, BeWeather and GoWeather! The animated in-app backgrounds apparently use video and it skips and stutters and in general ruins the feel of the app. I love this ROM and really don't want to go back to stock just to use these weather apps...
Click to expand...


Funny thing I noticed is that if you flip the phone upside down 180 degrees with the video still in portrait then the video does not flicker.
 
This may or may not be a CM7 issue, but I noticed that the dates associated with the camera images (EXIF) are almost all incorrect. Most have a date (camera, ditigized, and file date) of 12/8/2002.

Does anyone have a similar issue? Suggestions appreciated. Thanks.
 
samhande said:
This may or may not be a CM7 issue, but I noticed that the dates associated with the camera images are almost all incorrect. Most have a date (camera, ditigized, and file date) of 12/8/2002.

Does anyone have a similar issue? Suggestions appreciated. Thanks.
Click to expand...

You mean the image EXIF data, yes that's a problem with the camera app. It's always been broken. The image filename has the correct date. You can use PC apps to go through picture batches and set that info like this one.
 
Funny, sometimes the EXIF info is correct, most of the time it is not. Thanks for the suggested GUI interfact to ExifTool, makes this program much easier to work with. Do you know if all MT camera apps suffer from this issue? Would using Xoom fix the EXIF error?

And a big thanks Whyzor for making the MT a MUCH better phone!
 
samhande said:
Funny, sometimes the EXIF info is correct, most of the time it is not. Thanks for the suggested GUI interfact to ExifTool, makes this program much easier to work with. Do you know if all MT camera apps suffer from this issue? Would using Xoom fix the EXIF error?

And a big thanks Whyzor for making the MT a MUCH better phone!
Click to expand...

Zoom Fx has the same problem.
From my experience, the GPS date is correct (if available) but the exif data is always the same (incorrect) date.
 
I'm not sure if anyone else has this problem but when I'm on the 1-26 version my headphone jack doesnt seem to work, ill plug something in and it won't recognize that and only plays sound from the phone's speakers. Is there a setting that I may have shut off or something?
 
f4lloutdiablo said:
I'm not sure if anyone else has this problem but when I'm on the 1-26 version my headphone jack doesnt seem to work, ill plug something in and it won't recognize that and only plays sound from the phone's speakers. Is there a setting that I may have shut off or something?
Click to expand...
yes i think headphone jack was brokein that build becuase of kernal.i flash #18 kernal to fix that hope that help
 

Attachments

Whyzor, I just wanted to chime in here and say that my battery life seems to be substantially better with the new 1-31 kernel. You rock!
 
Updated to 02-02 build and everything works except when I go into CyanogenMod settings and select "Input", I get a force close.. something about "com.cyanogenmod.cmparts". I wiped and formatted everything on my phone, downloaded the rom again from my laptop this time and installed fresh and get the same result. Anyone else have this problem? Went back to 01-26 build for now.
 
MediocreBadGuy said:
Updated to 02-02 build and everything works except when I go into CyanogenMod settings and select "Input", I get a force close.. something about "com.cyanogenmod.cmparts". I wiped and formatted everything on my phone, downloaded the rom again from my laptop this time and installed fresh and get the same result. Anyone else have this problem? Went back to 01-26 build for now.
Click to expand...

I had the exact same problem, I'm probably not going to go to the 01-26 build cause I'm too lazy, and Settings> CyangoenMod > Input is not that important to me
 
I get that as well on the update. I don't really mess with that much but tried it and got the force closes as well.
 
First off, thanks a lot for this ROM; I've been following this and TG's mod since October and it's been (mostly) an improvement on every release.

That being said, this might be unrelated, but ever since flashing the 1-31 kernel I'm unable to mount my phone with the USB storage on my computer (Late 2011 Macbook Pro).

Actually, I don't remember any issues before yesterday, when I updated to 10.7.3, so that could also be a possible source of issues.

edit: nevermind, it seems to have fixed itself. It wouldn't mount by default for some reason.
 
If i have the TG-Reloaded do i have to wipe everything in order to install the updated builds,or can i flash right over the previous? and if i can flash right over,will i have to re flash gapps?

(one more no0b q?) if i can flash right over the previous build will i lose all the apps and themes or will everything still be there?

thanks.
 
I can confirm the CM settings - input FC. It may be something wrong with CM7's latest changes, probably some language translations. If you don't use that setting much, I recommend still upgrading to build 02-02 or at least kernel 1-31. it should keep your settings from previous builds.
 
Whyzor,
Can you post a link for just the new kernels? I have been using my own CM7 build, but would like to try your kernel. I did not see it in the first few posts. Did I just miss it, or is it only in the ROM download?
 
agentc13 said:
Whyzor,
Can you post a link for just the new kernels? I have been using my own CM7 build, but would like to try your kernel. I did not see it in the first few posts. Did I just miss it, or is it only in the ROM download?
Click to expand...

I updated post #2 with a flashable kernel link. For reference, you can also pull the boot.img from the ROM zip file and replace it into your own ROM build, flash with signature verification off, which is default for CWM.
 
Whyzor said:
I updated post #2 with a flashable kernel link. For reference, you can also pull the boot.img from the ROM zip file and replace it into your own ROM build, flash with signature verification off, which is default for CWM.
Click to expand...

Thanks, I was trying to avoid pulling it out of the ROM zip. :)
 
Whyzor:

Which of your github repos contain your modifications for the kernel wakelocks? I'd like to learn how the wakelocks are created and released. Are tickerguy's changes clearly commented?
 
hamfactorial said:
Whyzor:

Which of your github repos contain your modifications for the kernel wakelocks? I'd like to learn how the wakelocks are created and released. Are tickerguy's changes clearly commented?
Click to expand...

It's right here:
https://github.com/Whyzor/WX_435_Kernel-CM7
https://github.com/Whyzor/WX_435_Kernel-CM7/commits/master

Tickerguy's one has the name kernel in it too. BTW I believe apps like JD aren't allowed to control wifi module loading/unloading in the kernel. Also TG's workaround was to keep a wakelock as long as the wifi module is loaded, otherwise it can go into sleep and never wakeup. That's the original issue that required this.
 
I searched through the thread and read the opening post and didn't see this asked yet forgive me if it has been addressed.

The camera shutter sound is turned on and there is no setting to turn it off.

The only way I was able to do it is by silencing all sounds except alarm and media.

Is there a fix coming for this soon?
 
jt415105 said:
I searched through the thread and read the opening post and didn't see this asked yet forgive me if it has been addressed.

The camera shutter sound is turned on and there is no setting to turn it off.

The only way I was able to do it is by silencing all sounds except alarm and media.

Is there a fix coming for this soon?
Click to expand...
CM Settings > Sound > Mute camera shutter
 
You must log in or register to reply here.
Back
Top Bottom