hotalings
Android Enthusiast
Agreed there is no need for task killers all the do is take UP MORE ram
-
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)
- Thread starter Whyzor
- Start date
-
- Tags
- motorola triumph
Agreed there is no need for task killers all the do is take UP MORE ram
Android1993
Well-Known Member
Few questions. How would I go about fixing the video flicker issue and how would I use Titanium Backup before flashing the rom so I don't have to download all my Gameloft game data allover again or lose any progress in games.
Followed the video on how to flash this to the second as I did it. Now restoring all of the apps and system data through titanium backup. I have read on a few sites that it then needs to be rebooted after the titanium backup restoration. Is this true? I have been having problems getting this on stably so trying to get all of my ducks in a row.
marc12868
Android Expert
There is no fix for the video flicker unless you use a stock rom. I can't remember exactly with titanium backup as I haven't used it in a while, but there should be an option in there to backup apps+data... The downloaded data will stay on your sdcard unless you delete it so you don't have to worry about that... Just backup app+data if you want to keep your progress.
i clicked the show button, and you gotta point lol. if i can click the show button, i can click the thanks button
marc12868
Android Expert
i clicked the show button, and you gotta point lol. if i can click the show button, i can click the thanks button
And that's the point!
lolFollowed all of the directions. Got everything reloaded. TT said to reboot so I did. Now the phone is rebooting itself every few minutes. Whyzor - earlier you mentioned Incredicontrol and adjusting some of the voltage settings. Any suggestions of what to adjust as I have never used that app before (and can't actually get the phone to stay up long enough for the app to finish loading right now)? Switched to a different battery so I don't think it is to warm of a battery. Based off of what you said before, it is either the voltage I can adjust with incredicontrol or the phone itself.
Any tips would be great. Hoping to avoid having to get a new phone and start all over again. When I had it working for a couple of days before the reboots started I loved the Rom and it worked great. I just want to find a way to get it to be stable on my phone.
Any tips would be great. Hoping to avoid having to get a new phone and start all over again. When I had it working for a couple of days before the reboots started I loved the Rom and it worked great. I just want to find a way to get it to be stable on my phone.
Whyzor
Android Expert
New kernel for those who want to try the latest touchscreen update.
WhyKernel-01-17.zip
Let me know if you notice any differences.
For those curious, the last kernel (01-16) disabled toggling IRQ on & off for the touchscreen every time it gets an interrupt from the hardware (not sure why it was needed in the first place, it now leaves it on until screen turns off). This version (01-17) also optimizes the interrupt service request to not create new struct pointers every time to an existing struct.
UPDATE: It STILL ignores touches occasionally. I have another idea I'll try (learning new things along the way, will try to create a dedicated workqueue for processing touchscreen interrupts instead of sharing a global one with the rest of the kernel).
WhyKernel-01-17.zip
Let me know if you notice any differences.
For those curious, the last kernel (01-16) disabled toggling IRQ on & off for the touchscreen every time it gets an interrupt from the hardware (not sure why it was needed in the first place, it now leaves it on until screen turns off). This version (01-17) also optimizes the interrupt service request to not create new struct pointers every time to an existing struct.
UPDATE: It STILL ignores touches occasionally. I have another idea I'll try (learning new things along the way, will try to create a dedicated workqueue for processing touchscreen interrupts instead of sharing a global one with the rest of the kernel).
marc12868
Android Expert
I would do a full wipe (factory reset, wipe cache, dalvik cache) and then reflash the rom (as well as gapps right after if you want access to the market of course
) see if that helps...
Whyzor
Android Expert
Try the newer version (01-17) and let me know if you notice any differences.
If you used any app to restore your old apps & settings, that may be what's causing problems. You should do a fresh wipe & re-flash the ROM + Gapps. Then reinstall the apps manually. Only need to do this once, going forward upgrading just needs cache & dalvik-cache wipes, which keeps apps and data settings. The ROM by default runs at default 245-1024 Mhz CPU clock at regular OEM voltages. So no need to mess with those if they ran fine. May want to check in the Settings - CM settings - Performance to see that they are on default values, sometimes flashing ROMS introduces random setting changes.
Whyzor
Android Expert
Restore from market. Don't use titanium backup to restore. This is a general problem with Android. The OS itself is pretty good, battery efficient and smooth. It's usually apps that are poorly written that cause most problems.
Whyzor
Android Expert
Find them from the market again. I've never used Titanium backup at all. Do make NANDROID backups in recovery mode when flashing new ROMs or kernels, that makes an EXACT copy of your ROM for backup. Titanium tries to pick what apps & settings to backup & restore, and can make mistakes and cause weird problems.
Whyzor
Android Expert
If you're not going to use Titanium backup (or any app), uninstall it, it could slow down the system overall on startup since Android caches apps even if they're not active. The restart is abnormal, uninstalling may or may not help. Make sure everything is stable with CM - Settings - Performance - 245-1024 Interactive, and not many other apps are installed, at least then you know the system is ok, then reinstall apps and if a problem develops, you'll know what apps could be causing the problems. having everthing installed at once from the start makes it harder to narrow down what's causing the problem. Same concept as troubleshooting problems on a PC.
Whyzor, thanks so much for your continuing hard work on this ROM. I am waiting eagerly to read about your new release that has the functionality that I so need.
Basically, without the ability to run bluetooth and wifi together, I am sunk.
This isn't a compliant or anything, I am just looking for an idea of priority. I know you are working through some battery drain issues and whatnot. Is the bluetooth and wifi together fail a priority for you? Is it even on your radar?
I am just trying to get a feel for the near term outcomes...
Basically, without the ability to run bluetooth and wifi together, I am sunk.
This isn't a compliant or anything, I am just looking for an idea of priority. I know you are working through some battery drain issues and whatnot. Is the bluetooth and wifi together fail a priority for you? Is it even on your radar?
I am just trying to get a feel for the near term outcomes...
agentc13
Daleks Über Alles
It is a big mess (some sort of interrupt storm, iirc) in the code. It is quite a project to undertake. I can't speak for Whyzor, but I wouldn't hold my breath.
Whyzor
Android Expert
I'm trying to fix the touchscreen reliability issues. The random disconnect between human and machine gets annoying and kinda ruins the experience on the phone (Apple understands this very well). I will look into the BT + Wifi problem after this is resolved, but don't get your hopes high, more experienced people have looked into it than me before and haven't resolved it yet. Both BT & Wifi uses the same physical chip, and if the bug is inside the binary file that we don't have source for, then there's not much that can be done until Motorola/Huawei/VM releases new source code or new binaries (maybe for another phone in the same family as the MT).
Whyzor
Android Expert
BTW, there are really only a few specific scenarios that I can think of where BT & Wifi need to be used simultaneously, like during a VoiP call over Wifi. Even then using a wired headset would still work. And setting up CM7's notification bar to have shortcuts to toggle both functions makes it easy to turn on/off.
As for the HDMI, unless one uses it all the time (in which case maybe they should consider getting another dedicated media player with HDMI output). Can always have a Nandroid backup of a Froyo ROM to go back to that has HDMI functionality, then when it's not needed anymore, flash back to this ROM. (Takes less than 5 minutes total).
It's natural to think "oh this ROM doesn't have a certain functionality that I need", but all phones & ROMs have problems, most are just not obviously listed on the main page and one will eventually come to them after some use. By then most will just stick with it because it's too much hassle to go back, just like it's a hassle to go to a new ROM.
As for the HDMI, unless one uses it all the time (in which case maybe they should consider getting another dedicated media player with HDMI output). Can always have a Nandroid backup of a Froyo ROM to go back to that has HDMI functionality, then when it's not needed anymore, flash back to this ROM. (Takes less than 5 minutes total).
It's natural to think "oh this ROM doesn't have a certain functionality that I need", but all phones & ROMs have problems, most are just not obviously listed on the main page and one will eventually come to them after some use. By then most will just stick with it because it's too much hassle to go back, just like it's a hassle to go to a new ROM.
dsmryder
Android Expert
Is it wrong/rude/illegal to decompile/reverse engineer the drivers?
I'm sure there is a reason that it's not done.
To be quite honest, I thought HDMI was cool, but I only used it once. I probably wont use it again. This fix is low on my own wish list.
My scenario is this: I use tasker to turn on wifi while at my house. So when I am home it is always on. I like having the internet available for scores and quick references. I also leave bluetooth on all the time for convinience when I get into my car, it connects to my stereo automatically. Also, my alarm clock has bluetooth to talk to my phone. -> Plug for Philips Fidelio! It connects automatically!
To have the ability to do both is why it pains me to not have adopted your ROM. I am really chomping at the bit because I do want the ability to TEHTER to my IPAD 2. Unfortunately, I cannot change the MTU values on the ipad to function with other tether apps that work with the stock rom. Plus all the bells and whistles of CM are appealing.
You've heard my story. Maybe I change my usage habits to make your ROM more realistic. Changing ROMs on the fly to suit my needs sounds appealing, but don't you have to replace your widgets every time?
Any suggestions?
My scenario is this: I use tasker to turn on wifi while at my house. So when I am home it is always on. I like having the internet available for scores and quick references. I also leave bluetooth on all the time for convinience when I get into my car, it connects to my stereo automatically. Also, my alarm clock has bluetooth to talk to my phone. -> Plug for Philips Fidelio! It connects automatically!
To have the ability to do both is why it pains me to not have adopted your ROM. I am really chomping at the bit because I do want the ability to TEHTER to my IPAD 2. Unfortunately, I cannot change the MTU values on the ipad to function with other tether apps that work with the stock rom. Plus all the bells and whistles of CM are appealing.
You've heard my story. Maybe I change my usage habits to make your ROM more realistic. Changing ROMs on the fly to suit my needs sounds appealing, but don't you have to replace your widgets every time?
Any suggestions?