-
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
Do you have a registered payment method? Amazon won't let you download anything, even free apps without one. I have amazon on my phone running this and have never had a problem downloading apps.
After I make purchase, I delete my credit card information. I don't like to leave that information online. Maybe that was the problem. Thanks.
Whyzor
Android Expert
Most of the time I connect to wifi fine, including hidden SSIDs, encrypted, & open. It could be a number of variables, including your router & its settings.
Whyzor
Android Expert
No, my phone never reboots unless I do it intentionally (undervolting or overclocking can cause it though).
Whyzor
Android Expert
If others aren't reporting the same issue, I'm guessing there's something wrong with your phone's hardware, and you'll have to ask VM to send you a free replacement.
Whyzor
Android Expert
Too low of a min frequency would only result in extremely slow at waking up from screen off, not a reboot (crash). The default is 245-1024 btw if you haven't changed anything.
The other thing is maybe try to increase the voltage with "incredicontrol" app to see if the phone is not getting enough voltage at certain frequencies (You'd be raising them from default OEM specs). Reboots are definitely related to hardware problems, either too hot of a battery, memory corruption due to low voltage or just plain manufacturing errors.
frdmspoplr
Well-Known Member
The past couple days I've encountered the no deep sleep bug. I flashed this release the day it was updated and it's been fine. Then about 2 days ago I pull my phone out and it's half-drained and really warm. After some trial and error I figured out it wasn't going into deep sleep. If i reboot it fixes it, but several hours later it starts again. I'll try a clean reflash at some point, but just a heads up for you.
Whyzor
Android Expert
The fix I added was to prevent MMC kernel wakelocks, it's entirely possible that you have an app or a setting that has another wakelock that prevents deep sleep (such as the known wifi or BT on bugs). The only helpful app that I know of that shows "partial wakelocks" and "kernel wakelocks" is BetterBatteryStats, and in the 'kernel wakelock' menu, you'd see how many hours it was awake and should show 'MMC2', MMC1, MMC0 (to prove my particular fix still needs work). Any other leftover kernel wakelocks (and there may be a lot) would require a new fix. But I haven't encountered any other type yet, I don't install a lot of unused apps on my phone either, so that's a good baseline to gauge whether the ROM has issues.
Using CPU Spy app can also clue in what's going on, if it doesn't enter deep sleep but idles at the lowest frequency, then that's the same problem as my MMC fix was supposed to address. But if majority is spent at higher than min freq, then it points to an app or runaway process that's keeping the phone awake, which is a different problem.
You may have a runaway app that's keeping the phone running all the time. Use BetterBatteryStats, or Settings -> Battery Usage to try to narrow down the app. The scope of this process should be in another thread.
Here's a general breakup of what the typical Android phone abstraction layers, from highest level to lowest:
5 - Apps
4 - Operating system (ROM)
3 - kernel
2 - drivers
1 - hardware
Any of the levels can cause problems, this thread is for dealing with level 4 ROM & maybe some level 3 kernel issues. Hardware, drivers, and apps are beyond my control. I understand for the typical user, it's hard to know what's at what level, but I'm just writing this for informational purposes.
I would also suggest making Nandroid backups, then flashing to Froyo, or a clean CM7 or MIUI ROM to try to repeat the problem to determine which components are common (hardware, most drivers, apps), and which are different (OS & kernel). Also don't be afraid to experiment with changing settings (just Nandroid restore if things get really hosed) It's the typical process of troubleshooting problems.
Whyzor
Android Expert
Just curious, what did you notice differently with theOC's touchscreen fix? I've been looking at the code & the stock (TG's B08 version) of the driver works the same as theOC's (Isaac's new version). If anything the older version is more reliable.
Austrie
Android Expert
A user were talking about the old one being more reliable, (I think it was you), but the new one is better for dual stick, and the new one cleans up the garbage build up that was in the driver.
frdmspoplr
Well-Known Member
I'm the same way. I like to keep as little crap running in the background as possible. Just to make sure, I installed watchdog and there are indeed no runaway apps running. And I have been checking cpu spy regularly. When it does stop going into deep sleep, it idles at my min frequency, 122. I'll check out BetterBatteryStats and report back when I encounter it again.
Austrie
Android Expert
Well it seems like you can not deep sleep while charging. As for MIUI, when you hold the home window, a window pop ups with a app killer button at the bottom, after using app killer you can enter deep sleep for sure; it kills any unnecessary app. Do it while at launcher, because it doesn't kill the app your using at the moment, so there will be a left over app if you don't.
Anyone else having the screen flashing on/off during a call?
I had this problem with earlier TG builds, as did many others. He did something to fix it and it worked fine (at least in the 0.8, I don't recall when it started working again). Now the problem seems to happen again (to me) using this ROM.
I had this problem with earlier TG builds, as did many others. He did something to fix it and it worked fine (at least in the 0.8, I don't recall when it started working again). Now the problem seems to happen again (to me) using this ROM.
Whyzor
Android Expert
Could it be because the proximity sensor toggles on & off because your head distance is at the cutoff distance, and the MT has that problem of flickering the screen when it turns off and then turned back on again within about 5 seconds.
I'm not sure if it was me, because I just came to this conclusion yesterday. Up until yesterday I had been using kernels that had Isaac's updates, then for kicks I switched back to stock touchscreen driver (used in TG's B.08 kernel). They're both functionally the same (see Isaac's comments here). The Touchscreen interrupt service call gets run many times a second, so a more efficient code path is actually better for smooth gameplay & overall use (at least in theory, and somewhat confirmed with my limited testing so far). Here are two kernels, for those who want to test differences between the two, make a Nandroid backup, then flash one, test playing some games, & use a multitouch test app, then flash the other one, and repeat the same test procedure, let me know if you notice any differences.
Kernel using Isaac's Touchscreen driver (used in previous builds so far)
Kernel using stock Touchscreen driver w/ optimization (going into the next build)
dsmryder
Android Expert
Would it be hard to create a .zip for the two drivers? I was playing a game and it seemed that the new driver made it harder, the two points seemed to merge. I need to find that screen tester again...
oops. you already did
Austrie
Android Expert
So you know how to code, that nice. Where did you learn from? I would test it for you, but, i'm on MIUI.
Whyzor
Android Expert
lol, yes I know how to code. I have a degree in computer engineering, my day job is a software engineer, but only dabbled in some embedded systems as an intern in college years ago. I haven't done much with C/C++/Java in a while, my day job uses mostly scripting languages. This project is really pushing me to keep my skills sharp
punkmaxx
Android Enthusiast
lol, yes I know how to code. I have a degree in computer engineering, my day job is a software engineer, but only dabbled in some embedded systems as an intern in college years ago. I haven't done much with C/C++/Java in a while, my day job uses mostly scripting languages. This project is really pushing me to keep my skills sharp
It's really good to have someone as knowledgeable and experienced as yourself here on the Triumph forums. Thanks for all your continuing support of the Triumph Development Community; not to mention your current presence on the ICS DEV Thread. Looking forward to all the possible things to come.
bobloadmire
Android Enthusiast
anyone else still having deep sleep problems? Even in airplane mode a lot of the time it won't deep sleep. Until I reboot, it just won't deep sleep. I'm using the latest update.