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

Root [ROM][Beta][FINAL] CM7 Android For Triumph [Tickerguy Edition, Kernel: mine] 11/19

tickerguy said:
If you format /system GAPPS will be wiped as it resides in.... /system. In this case you must reload GAPPS.

If you format /data then all the data (login information, etc) is gone.

If you're coming from anywhere beyond where I separated GAPPS from the build then you should not need to format /system or /data - update "in-place" should be ok. I noted this in the top posts if you read them.

However, no promises on that as I have no idea what you did with your phone. This is especially true if you have replaced ANYTHING in the /system area or run anything that tampers with the /system configuration, including things like the "V6 supercharger" and similar.

In other words if you're doing other than loading ordinary applications then what you did might be incompatible with the ROM in some way, and if you try to load over the top of that all bets are off as I have no way to know what you did and how it might interact with the base load.

I load over the top on my phone all the time - when I'm actively developing I might do it a dozen times in a day. If I KNOW there's an incompatibility I'll note it in the NOTES section in the first few posts, but in the general sense if you're following the upgrade path and are not tampering with the /system area yourself it's fine.

The thing is that most of the people here are tampering with the base configuration in some form or fashion for various reasons (e.g. minimum CPU speed, etc) and as such I have no clue what you're doing or what might be causing it. This ROM is what I run on my phone and while I'm usually a code build ahead of what's posted here because I'm working on it the version posted here is what I had on the phone a few days previous and was happy enough to use, or I wouldn't post it.
Click to expand...

Thanks, that explains it:)
 
cdtatum08 said:
I think SamuraiFox is having the same issue as I am. When I try to take a picture with the front camera (landscape and portrait) I get a pop up saying "Activity Camera (in application Camera) is not responding." In stock it works fine. I have had the issue with all of the builds but I figured since it was in alpha-beta release that is was a fix in the process.
Click to expand...
I cannot reproduce this.

If you are holding /data (configuration of various things) across builds and you have been attempting to use other camera apps or the old one that was present previously there are settings present in some of those that the hardware does not support.

If those are selected the camera hardware will hang. Not might: WILL.

This was the cause of the hangs previously on the FFC - if you had "auto focus" or "touch focus" selected you were dead as the FFC has no focus capability at all. The code would tell the camera to do it and never got back the status that it had finished or failed from the driver. At that point you're screwed as there's a pending operation that never clears and the camera is for all intents and purposes inaccessible. This incidentally is bad design in the Android code; you should never send down a command to a piece of hardware without some sort of timeout if it never returns a completion interrupt or status bit, and if you get a timeout on something that isn't supposed to be able to fail you should immediately send a reset to the offending hardware device (and see if THAT fails) so you can either fix the lockup or declare the device "dead" and ignore it from that point forward.

If you connect using USB debugging and look at both "dmesg" (from the shell) and the logcat output you will see this if it's happening. Once it does, you're fooked as the camera hardware is wedged; there's no way out other than a reboot to force a hardware-level reset down the line to the chip.

I just ran a Nandroid on my phone (so as not to lose everything!), formatted /system, /data and /cache, then loaded the base code. That's a CLEAN installation with nothing on the phone at all - not even GAPPS.

The front camera works fine on my phone in that environment; I was able to both preview and take (a very ugly) picture of my mug.
 
TealDream said:
I have an issue that just started when i flashed the Beta. Never had the problem with the Alpha builds.

My phone shuts down between 35-40% and says the battery is dead. i can't restart it. when i plug it in and restart it, as it's loading it shows between 1-5% battery, then when the SD card mounts, it jumps up to 35-40%. but, if i unplug it, it dies before it gets to 35%. i've tried wiping the battery stats, but it didn't seem to make a different. anyone know how i can fix this?
Click to expand...
Try using a different SD card, if you have one, and see what happens.

Chingling said:
So before when I set the sleep CPU minimum back to 122 I got A LOT of lock ups where the screen would light up but nothing would appear. If I put the sleep CPU minimum back to 245, could this possibly solve the lock ups issue?
Click to expand...
Try it and find out.
 
tickerguy said:
I cannot reproduce this.

If you are holding /data (configuration of various things) across builds and you have been attempting to use other camera apps or the old one that was present previously there are settings present in some of those that the hardware does not support.

If those are selected the camera hardware will hang. Not might: WILL.

This was the cause of the hangs previously on the FFC - if you had "auto focus" or "touch focus" selected you were dead as the FFC has no focus capability at all. The code would tell the camera to do it and never got back the status that it had finished or failed from the driver. At that point you're screwed as there's a pending operation that never clears and the camera is for all intents and purposes inaccessible. This incidentally is bad design in the Android code; you should never send down a command to a piece of hardware without some sort of timeout if it never returns a completion interrupt or status bit, and if you get a timeout on something that isn't supposed to be able to fail you should immediately send a reset to the offending hardware device (and see if THAT fails) so you can either fix the lockup or declare the device "dead" and ignore it from that point forward.

If you connect using USB debugging and look at both "dmesg" (from the shell) and the logcat output you will see this if it's happening. Once it does, you're fooked as the camera hardware is wedged; there's no way out other than a reboot to force a hardware-level reset down the line to the chip.

I just ran a Nandroid on my phone (so as not to lose everything!), formatted /system, /data and /cache, then loaded the base code. That's a CLEAN installation with nothing on the phone at all - not even GAPPS.

The front camera works fine on my phone in that environment; I was able to both preview and take (a very ugly) picture of my mug.
Click to expand...

I thank you for everything you are doing in making this phone kick-A! After looking through the settings of the FFC I noticed the "restore default settings" option. I have no idea what I changed in a past FFC settings because I haven't used it much at all. Whatever I did WAS hanging up the system though. After the restore it was/is working fine.
 
I am getting the clicking noise in the google goggles application, then it can extend to the camera one if you switch back from camcorder to camera, this happens after using google goggles for me.
 
Teal: Your battery statistics are corrupted. Discharge the phone entirely and let it charge until full. Even better, LEAVE IT ON CHARGE overnight when the light is green with the operating system running (powered up.) An AC charge is materially better than a USB one as the AC charge can deliver a full 1A down the wire while a USB charger is limited to 500ma by the port itself.

The low-battery protection circuit will kill the power when the voltage goes below a critical level no matter what the statistics or the phone thinks. This is to prevent the battery from entering an over-discharged state which can cause battery fires (literally) when it is later charged and is not under the phone's control - the BATTERY has a protection circuit in it that cuts the power off when that happens. Clearing statistics does not do you a bit of good unless you allow the battery's actual state to equalize with what the phone thinks it is. All the phone can see itself is the voltage from the cell; if it starts to fall off rapidly (which is what happens when a lithium cell reaches exhaustion) the protective circuit will cut off the power.

I've seen this happen on other devices before when you switch ROMs and don't fully charge and allow equalization against the actual battery state. Plug it in and let it charge overnight from dead-flat "off" and see if the problem goes away.

I have no problem like this on mine; my battery will run all the way down to the red warning and well into it before it kills it with single-digit percentages left.

This phone's internal hardware switches to a much lower-output charge at 90% and turns the light green, even though it's not entirely full. If the stats are wrong it will enter this mode with the battery being WELL short of actually being full, and require many hours of additional charging (in some cases as long as overnight!) before it reaches an actual full charge. This is actually a good thing rather than a bad one (contrary to some people's views) as overcharging lithium cells both damages them and can cause overheating (which again can lead to fires!); I like how the Triumph manages the battery although it can easily lead to a situation where you think you have 100% when you really don't, especially if you're swapping batteries or ROMs around, and that in turn leads to surprises when the phone shuts down while you think it has plenty of battery left.
 
tickerguy said:
Teal: Your battery statistics are corrupted. Discharge the phone entirely and let it charge until full. Even better, LEAVE IT ON CHARGE overnight when the light is green with the operating system running (powered up.) An AC charge is materially better than a USB one as the AC charge can deliver a full 1A down the wire while a USB charger is limited to 500ma by the port itself.

The low-battery protection circuit will kill the power when the voltage goes below a critical level no matter what the statistics or the phone thinks. This is to prevent the battery from entering an over-discharged state which can cause battery fires (literally) when it is later charged and is not under the phone's control - the BATTERY has a protection circuit in it that cuts the power off when that happens. Clearing statistics does not do you a bit of good unless you allow the battery's actual state to equalize with what the phone thinks it is. All the phone can see itself is the voltage from the cell; if it starts to fall off rapidly (which is what happens when a lithium cell reaches exhaustion) the protective circuit will cut off the power.

I've seen this happen on other devices before when you switch ROMs and don't fully charge and allow equalization against the actual battery state. Plug it in and let it charge overnight from dead-flat "off" and see if the problem goes away.

I have no problem like this on mine; my battery will run all the way down to the red warning and well into it before it kills it with single-digit percentages left.

This phone's internal hardware switches to a much lower-output charge at 90% and turns the light green, even though it's not entirely full. If the stats are wrong it will enter this mode with the battery being WELL short of actually being full, and require many hours of additional charging (in some cases as long as overnight!) before it reaches an actual full charge. This is actually a good thing rather than a bad one (contrary to some people's views) as overcharging lithium cells both damages them and can cause overheating (which again can lead to fires!); I like how the Triumph manages the battery although it can easily lead to a situation where you think you have 100% when you really don't, especially if you're swapping batteries or ROMs around, and that in turn leads to surprises when the phone shuts down while you think it has plenty of battery left.
Click to expand...

thanks! i'll try this tonight. i wish i read this an hour ago...i just did a full wipe.
 
Awesome work so far, Tickerguy.

Can I put in a request? Could you put something about the wifi-sleep bug in the known broken section?

I believe that you've stated it's something to do with CM7 in general, and that you may not be able to fix it, but it'd be nice to let people know about it before they install the ROM.

I know for most people it's not a big deal, but I always set my wifi sleep policy to "always on".

Thanks, and keep up the great work!
 
I had the funniest bug today. I had my whole screen suddenly turn white, Though I could still see what was below it. I was like "Oh?" It just took the screen to be locked and unlocked again and it went away. Anyone else have this? I'm on 10/16. Think I need to put on 10/22. I'm just being incredibly lazy. >_> (Not so much, I have to work 86 hours without a day off due to my boss being on vacation)....
 
cdtatum08 said:
I thank you for everything you are doing in making this phone kick-A! After looking through the settings of the FFC I noticed the "restore default settings" option. I have no idea what I changed in a past FFC settings because I haven't used it much at all. Whatever I did WAS hanging up the system though. After the restore it was/is working fine.
Click to expand...
THANKS@! I too assumed the ffc didn't work because it was still in Alpha. After hitting the "restore default settings" option my ffc started to work for the first time on this rom. Thanks to you and especially TG.
 
septembersrain said:
I had the funniest bug today. I had my whole screen suddenly turn white, Though I could still see what was below it. I was like "Oh?" It just took the screen to be locked and unlocked again and it went away. Anyone else have this? I'm on 10/16. Think I need to put on 10/22. I'm just being incredibly lazy. >_> (Not so much, I have to work 86 hours without a day off due to my boss being on vacation)....
Click to expand...
I had this once. but yeah it went away after a lock/unlock so i didn't think much about it.
 
Is anybody having issues with the browser on the most recent beta? I'm having issues where the top bar loads and goes back and forth loading flashing.
 
septembersrain said:
I had the funniest bug today. I had my whole screen suddenly turn white, Though I could still see what was below it. I was like "Oh?" It just took the screen to be locked and unlocked again and it went away. Anyone else have this? I'm on 10/16. Think I need to put on 10/22. I'm just being incredibly lazy. >_> (Not so much, I have to work 86 hours without a day off due to my boss being on vacation)....
Click to expand...

Yeah that's the Motorola Triumph for you...does the white screen stock too...
 
tickerguy said:
If you are holding /data (configuration of various things) across builds and you have been attempting to use other camera apps or the old one that was present previously there are settings present in some of those that the hardware does not support.

If those are selected the camera hardware will hang. Not might: WILL.

This was the cause of the hangs previously on the FFC - if you had "auto focus" or "touch focus" selected you were dead as the FFC has no focus capability at all. The code would tell the camera to do it and never got back the status that it had finished or failed from the driver. At that point you're screwed as there's a pending operation that never clears and the camera is for all intents and purposes inaccessible. This incidentally is bad design in the Android code; you should never send down a command to a piece of hardware without some sort of timeout if it never returns a completion interrupt or status bit, and if you get a timeout on something that isn't supposed to be able to fail you should immediately send a reset to the offending hardware device (and see if THAT fails) so you can either fix the lockup or declare the device "dead" and ignore it from that point forward.
Click to expand...
This happens alot with apps, but I never tried it with a system app like camera, but most of the time I get a heavy lag then a Force Close.....
 
I'm not sure if I'm the only one facing this issue, but I'm using the final ALPHA release of the Rom. It looks like when the screen times out while connected to wifi, wifi disconnects. So when the phone wakes up I have to disable and re-enable wifi. Otherwise the phone has no wifi despite having the wifi screen shown on the status bar. Anyway else having this issue? Mine is 08/11 built Triumph.
 
Is there any other place where I can snatch the 10/22 update? Been trying since yesterday a.m. and just can't download from mediafire for some reason.
 
Tg: There is very little reason for me to put a large amount of effort into that; I do, however, review the commits related to the phone and pull those that matter. For instance, the USB tethering fix actually came out of CM7's commit chain.

Right now there is a serious problem with pulling and building a "base" copy from my manifest list. I don't know exactly why right now and am looking into it, but this poses extreme danger should I pull a full resync against the upstream, as it could leave me with an unholy mess that could take a very long time to sort out. I'll do it eventually, but everyone pestering me just because they want a silly revision number change is rather foolish - and that's being polite.
 
You must log in or register to reply here.
Back
Top Bottom