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

ok, and i dumped to a file, but I cannot find the file.

If you downloaded it on your phone, use a file manager app and check /sdcard/Downloads. if downloaded on PC, transfer it to /sdcard on your phone then install the .apk & run the app.
 
Any chance you can play with the camera at all? I use to use LGcamera (the LGcamcorder portion) to record video and it let me adjust the audio settings so well that audio would record crystal clear. LGcamera has problems in cm7 so recording with the stock app makes audio sound like muffled garbage covered in a pile of horse poop. The settings should be:

Source: microphone
Audio encoder: AAC
Audio samplerate: 44100
Audio bitrate: 256000

It made for incredible difference back on the stock rom, but no luck working in cm7 for some reason.
 
Any chance you can play with the camera at all? I use to use LGcamera (the LGcamcorder portion) to record video and it let me adjust the audio settings so well that audio would record crystal clear. LGcamera has problems in cm7 so recording with the stock app makes audio sound like muffled garbage covered in a pile of horse poop. The settings should be:

Source: microphone
Audio encoder: AAC
Audio samplerate: 44100
Audio bitrate: 256000

It made for incredible difference back on the stock rom, but no luck working in cm7 for some reason.

I do plan on looking into the video camera stuff once I get my build env working again (github is having problems, and Isaac's repo is out of sync with CM).

Any pointers to other variants of the MT where the camera performs better, especially source code would be helpful. The MT is based on the Huawei Ideos X6 design, uses Qualcomm MSM 8655 Snapdragon SoC.
 
Would updating the graphic drivers to the new ones that Qualcomm released for the Adreno 205 help in any way??
 
Would updating the graphic drivers to the new ones that Qualcomm released for the Adreno 205 help in any way??

Possibly, but I believe there has to be kernel mods to use the new drivers, I'd have to dig for those and see if they'd work for the MT.
 
I know but still :(, the changes are on both the kernel and ROM side. They'll work if you do it right.

Right now Im working on two project, my kernel and 'something' else.
 
Possibly, but I believe there has to be kernel mods to use the new drivers, I'd have to dig for those and see if they'd work for the MT.

Would an updated kernel say 2.6.35.7 help in any way? There's a new rom thread over on the xda forum for the ideos X6. Its the stock rom from the Taiwan Sharp SH8188U and has an updated kernel in it... 2.6.35.7 compared to the 2.6.32.9 we have now... The rom is an .nb0 file as well so... I don't know how to work with stuff like this, but I thought I might throw this out there for you to try and mess with incorporating...
 
Would an updated kernel say 2.6.35.7 help in any way? There's a new rom thread over on the xda forum for the ideos X6. Its the stock rom from the Taiwan Sharp SH8188U and has an updated kernel in it... 2.6.35.7 compared to the 2.6.32.9 we have now... The rom is an .nb0 file as well so... I don't know how to work with stuff like this, but I thought I might throw this out there for you to try and mess with incorporating...

I work with source code (except the proprietary binaries that all devices need & don't have source code for). All companies that use linux kernel are legally bound to release the source, so maybe a version will come out for that phone soon. The binaries (esp .nb0 files) are not very useful for the MT. They use slightly differen't components (such as different touchscreen or radio drivers).
 
I work with source code (except the proprietary binaries that all devices need & don't have source code for). All companies that use linux kernel are legally bound to release the source, so maybe a version will come out for that phone soon. The binaries (esp .nb0 files) are not very useful for the MT. They use slightly differen't components (such as different touchscreen or radio drivers).

Ahhh... Dang...
 
I spoke too soon, like other people mentioned, it started showing me as somewhere in the middle of the ocean but then it returned me to my actual location. Here is one more thing, GPS actually hasn't locked but it indicates as it is locked. I don't know, if I am explaining this correctly: GPS indicator doesn't blink and stays on which means it is locked, but it isn't yet.

BTW, there is thread going on about increasing data speed.
Can you add this line to my prop.build file:
ro.product.rat=EvDo only
on your next built?
Some says it marginally improve data speed.

Thanks
 
Streaming music doesn’t work well when not using either Interactive or Ondemand Governors once the screen turns off. At least out of those that can be used for general everyday use. Gets really bad using a governor that locks onto a frequency like either of the smartass governors? Especially if you are streaming and they lock into the lower frequencies once the screen turns off. If using Juice Defender its also important to enable connectivity for any streaming apps under the trigger settings.


Have had issues with some HD games freezing up back in the day and after following Isaaks recommendation of installing the Chainfire 3D driver from the Market a majority of those games either stopped freezing up altogether or the amount of time before freezing improved.

Whyzor,

would it also be safe in removing the Music, File Explorer, News & Weather and Voice Recorder APK's if they are not used or other more preferred Apps are used in their place? Figure it would be ok as I generally Freeze them in Titanium but just wanted to ask before finding they are used in other processes that are not necessarily visible.

Lastly, would you mind explaining the reasoning behind removing some of the lower CPU frequencies? I had always just assumed that having more frequencies available would help with battery consumption. Only thought this for example that if at the time a call that could use 356 MHz would now call for 576 MHz and use a bit more power? Am new to overclocking and fine tuning device CPU's so an explanation of how this actually works would be greatly appreciated. Never had much of an interest in doing these things with my PC but in the Mobile world there is nothing like the feeling of tuning a midrange device to perform as a more expensive higher end device. My Kindle only has 4 frequencies available, 300, 600, 800 and 1008. Thanks again for the Hotplug explanation, been using it as my default for a few days now, what a difference it has made.
 
I spoke too soon, like other people mentioned, it started showing me as somewhere in the middle of the ocean but then it returned me to my actual location. Here is one more thing, GPS actually hasn't locked but it indicates as it is locked. I don't know, if I am explaining this correctly: GPS indicator doesn't blink and stays on which means it is locked, but it isn't yet.

Disable intermediate_pos reporting like I explained earlier will fix this. I'll disable this by default next version.

BTW, there is thread going on about increasing data speed.
Can you add this line to my prop.build file:
ro.product.rat=EvDo only
on your next built?
Some says it marginally improve data speed.

Thanks
I think this breaks other parts of the radio/3G from what I remember. you can try it yourself, by editing build.prop and rebooting.

Streaming music doesn’t work well when not using either Interactive or Ondemand Governors once the screen turns off. At least out of those that can be used for general everyday use. Gets really bad using a governor that locks onto a frequency like either of the smartass governors? Especially if you are streaming and they lock into the lower frequencies once the screen turns off. If using Juice Defender its also important to enable connectivity for any streaming apps under the trigger settings.

One of the reason I'm not a fan of any governor that locks to a low freq when screen is off (I recommend interactive). It's like putting shackles on. The governor doesn' t know what the user's intent is. So just let it ramp up if it needs to. It should really be in deep sleep mode anyway (instead of at min freq) if there isn't anything going on.

would it also be safe in removing the Music, File Explorer, News & Weather and Voice Recorder APK's if they are not used or other more preferred Apps are used in their place? Figure it would be ok as I generally Freeze them in Titanium but just wanted to ask before finding they are used in other processes that are not necessarily visible.
Yes I believe all of those can be removed if you have replacements. But like any system mods, make Nandroid backups in recovery mode often and copy those backups to your computer too.

Lastly, would you mind explaining the reasoning behind removing some of the lower CPU frequencies? I had always just assumed that having more frequencies available would help with battery consumption. Only thought this for example that if at the time a call that could use 356 MHz would now call for 576 MHz and use a bit more power? Am new to overclocking and fine tuning device CPU's so an explanation of how this actually works would be greatly appreciated. Never had much of an interest in doing these things with my PC but in the Mobile world there is nothing like the feeling of tuning a midrange device to perform as a more expensive higher end device. My Kindle only has 4 frequencies available, 300, 600, 800 and 1008. Thanks again for the Hotplug explanation, been using it as my default for a few days now, what a difference it has made.
I kept the expanded range 61 mhz to 2 ghz (still better than stock 122-1024) Just less steps in between. There's not a whole lot of difference between say 576 and 768, so I just removed the ones in between. There's an overhead in changing the cpu frequency and it's done very often (20-100 ms for some governors). So the less fine steps to go through, the less "wasted" cycles.
 
I just wanted to report my battery life is very impressive with this latest build using interactive governor 61-1024 mhz.. I'm at 31% after 13 hours with 3g on all day normal use even some youtube usage.. wifi off. Keep up the good work!
 
Would updating the graphic drivers to the new ones that Qualcomm released for the Adreno 205 help in any way??

Is there source code for the new drivers? or are you referring to the already compiled files mentioned in that previous thread about the updated drivers?
 
I updated to the latest version (1-07) yesterday and I am seeing steeper battery drain plus 3 random resets in one day. Wiped clean before the install and same apps/settings.

Going back to one of the older version (I'm not sure which date). I'll try again with the next version. Thanks.
 
I updated to the latest version (1-07) yesterday and I am seeing steeper battery drain plus 3 random resets in one day. Wiped clean before the install and same apps/settings.

Going back to one of the older version (I'm not sure which date). I'll try again with the next version. Thanks.
I haven't had any random reboots since one of the early builds. If you restored data/settings with Titanium that may have potentially borked something. Your battery drain could possibly be related to the MMC kernel wakelocks which have been discussed a little bit earlier in the thread.
 
I don't know if this is a ROM issue or my phone.
In the morning today, I unpluged the charger and the battery drained like crazy, more than 10% within an hour, but at around 70% it became steady.

Second issue I had was, this morning the phone data was dead, I've notice this because I didn't get any e-mail notification, and the 3g logo and the bar was colored gray, it should be green when it is on and working, so I open the browser and was getting 'can not connect' page. I don't know if the voice signal was also dead, I didn't try it. I had to reboot to get this thing work again.

FYI. I didn't do anything last night, just plug in my charger as usual and went sleep.

When will be the next version due?

Thanks Whyzor for all your work.
 
Back
Top Bottom