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

ecarlson said:
And, not as important, since I like my brightness set at about 30% most of the time, and I can adjust it manually if necessary, but is there a way to get the auto-brightness to act more like stock: When I had auto-brightness on in CM7, it seemed to vary brightness very often, which was distracting, and it was a lot more subtle on stock. In any case, I generally only need 3 levels: Lowest, when it's totally dark; 30% most of the time; and 100% in bright sunlight, so if there is a way to set that up, please let me know.
Click to expand...

Try customizing the settings in Settings - CM Settings - Display - automatic backlight - Use custom - Enabled & Edit other levels

yashwantsingh said:
Hey, this rom touch drivers are not seem's to working with other fig_fbo devices.
Click to expand...

You didn't make it clear at first that it DID work before my latest updates. I just found that out reading the xda thread. Since I don't have a non-MT FB0 device to test, I can only guess at what broke things. I have a new flashable zip that you can flash & test. If it does work, I'll push the updates to the source code on github and let edowar know to include it in his ROMs too. Here's the 02-19 kernel with what I think will fix the touchscreen on other FB0 devices. It also includes new CRYPT flags set.

http://www.mediafire.com/download.php?rv7kdd11lwpmec5
 
viskon said:
Just had a third SOD since flashing the latest build. Had to pull battery to reset. I am using the interactive governor with my frequency setting 245 and 1024. Anyone having a similar experience?
Click to expand...

Yes. Occassionally the screen will not come out of standby and I have to battery pull. Other than that, last update (2-18) is very smooth! Videos have no issues either.
 
Just flashed the 2/18 build and in both my media players all my music is duplicated. Restored the build before that and no duplication. I'll try a clean install and report back.
 
Generic loopback or folder based encryption was always something I intended to look into. Well today I did some searching and found something called LUKS Manager that looks promising, but LUKS requires DM_CRYPT and CRYPTO_AES enabled in the kernel.

The following URL indicates the kernel params needed.

Using dm-crypt to Encrypt the SD Card...? - CyanogenMod Forum

Has anyone else found a better solution, that works with this ROM?

I believe there are plenty of reasons to want to secure ones data, but just in case you can't think of any I'll provide my some ideas. A secure folder would be useful for obscuring any sensitive data like: personal information, international espionage, and the number one answer hiding of porn.:rolleyes:

Unless I find something else, I'll probably look into this further. Whyzor, if I submit the changes would this be something you would include?
 
Clean install fixed music problem but home button stopped functioning. It would vibrate but not work. Flashed back to 2/16 build and everything is back to normal. But that's just me, maybe others will have better luck but I'll stay on 2/16 for now.
 
RedAnt said:
Generic loopback or folder based encryption was always something I intended to look into. Well today I did some searching and found something called LUKS Manager that looks promising, but LUKS requires DM_CRYPT and CRYPTO_AES enabled in the kernel.

The following URL indicates the kernel params needed.

Using dm-crypt to Encrypt the SD Card...? - CyanogenMod Forum

Has anyone else found a better solution, that works with this ROM?

I believe there are plenty of reasons to want to secure ones data, but just in case you can't think of any I'll provide my some ideas. A secure folder would be useful for obscuring any sensitive data like: personal information, international espionage, and the number one answer hiding of porn.:rolleyes:

Unless I find something else, I'll probably look into this further. Whyzor, if I submit the changes would this be something you would include?
Click to expand...

I re-updated the 02-19 kernel above with a few config flags set, only a couple were changed, the rest were already set.

CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
CONFIG_CRYPTO_SHA256=y (previously n)
CONFIG_CRYPTO_AES=y (previously m)
CONFIG_CRYPTO_CBC=y
 
i cant seem to play order and chaos with this rom it loads but then crashes
 
Luks appears to work. Md5sum values match for original and encrypted files.

Accessing encrypted data. is slow enough to make some applications not see the content. Photos and video do not get seen by apps for awhile, but eventually both worked. I can see storing some data in this format as long as quick access is not important.

Thanks for the amazing response time.

As long as this stays in the kernel I will make a new thread for it, and post what I find.
 
RedAnt said:
Luks appears to work. Md5sum values match for original and encrypted files.

Accessing encrypted data. is slow enough to make some applications not see the content. Photos and video do not get seen by apps for awhile, but eventually both worked. I can see storing some data in this format as long as quick access is not important.

Thanks for the amazing response time.

As long as this stays in the kernel I will make a new thread for it, and post what I find.
Click to expand...

Thanks for testing, your posts are usually detailed and informative so it helps me take action when possible. This was a quick kernel config change, and I was already going to recompile a test version for other FB0 devices (still waiting for someone to confirm it's working now before I keep those changes).
 
Whyzor said:
\\You didn't make it clear at first that it DID work before my latest updates. I just found that out reading the xda thread. Since I don't have a non-MT FB0 device to test, I can only guess at what broke things. I have a new flashable zip that you can flash & test. If it does work, I'll push the updates to the source code on github and let edowar know to include it in his ROMs too. Here's the 02-19 kernel with what I think will fix the touchscreen on other FB0 devices. It also includes new CRYPT flags set.

WhyKernel-02-19.zip
Click to expand...

Thx downloading it write know, i will test it & report you back...!!
 
It's still the same, touch screen is not working...!!
I have tried your update on cm7 from edowar & i also had tried your update on my port of your rom...!!
 
dsmryder said:
I've had like one freeze ever. And I've been on sence TG bata .7

I have crashed my phone over and over though. Undervolting!
Click to expand...

It is my first experience of Sleep of Death on my phone since I first switched to CM7.

Had an SOD on the 02/02 build as well. Wiped data, flashed the 02/18 build,set up the phone and keeping my fingers crossed.
 
What is this sleep of death I am reading about on this forum???

So far i have not had a problem with any of the roms,may just be
very lucky.
 
nate115 said:
What is this sleep of death I am reading about on this forum???

So far i have not had a problem with any of the roms,may just be
very lucky.
Click to expand...


I believed there talking about where you make a phone call and the screen doesn't wake up when you move your face away from the phone
 
nate115 said:
What is this sleep of death I am reading about on this forum???

So far i have not had a problem with any of the roms,may just be
very lucky.
Click to expand...

I seem to be the only one having SOD lately. No one else seems to have it.

SOD is when the phone fails to wake up after it goes to sleep. It does not respond to any of the buttons. The only way out is to remove the battery, put it back in and boot the phone.

After wiping data and reflashing the 02/18 build, I have not had any SODs yet.
 
ziggy46 said:
I believed there talking about where you make a phone call and the screen doesn't wake up when you move your face away from the phone
Click to expand...

Exactly the same problem as I have. Quite inconvenient, after finishing the talk, you have to move your face away, and press power button to wake up the screen(some delay here too), only then you can press "End" button to disconnect the call.
 
Try adding this line to the end of /system/build.prop:

mot.proximity.delay=150

I was going to add that by default, but then noticed it was working properly in the latest build. It could be a timing issue depending on what background apps & services are running on each person's phone. The problem I'm talking about (I wouldn't call it Sleep of Death), is when the other side disconnects a call first before you pull the phone away, it remains sleeping for up to a minute or two. Pressing the power button or anything doesn't do anything. But it does eventually come back (at least for me). I'm not sure how long some of you waited, probably not long enough and just pulled the battery and calling it SOD.

I'll add that line in the next build just to be sure, wasn't sure if it could cause side effects for some people.
 
viskon said:
I seem to be the only one having SOD lately. No one else seems to have it.

SOD is when the phone fails to wake up after it goes to sleep. It does not respond to any of the buttons. The only way out is to remove the battery, put it back in and boot the phone.

After wiping data and reflashing the 02/18 build, I have not had any SODs yet.
Click to expand...


Under accessibility, there's an option for "hang with the power button"
Menu--> settings--> Accessibility--> power to hang up
 
Anyone else had camera problems with 2_18 kernel? My camera would not work on that kernel and even caused the phone to reboot. Went back to 08 kernel and the camera is fine.
 
You must log in or register to reply here.
Back
Top Bottom