Related
I'd like to use this app but I'm curious if there's any current bugs with it working on the Tilt. For example, does the device slow down? Are multiple presses of the power key sometimes needed? Does the performance decrease over time (requiring a reboot every few days)?
guitarlp said:
I'd like to use this app but I'm curious if there's any current bugs with it working on the Tilt. For example, does the device slow down? Are multiple presses of the power key sometimes needed? Does the performance decrease over time (requiring a reboot every few days)?
Click to expand...
Click to collapse
It works fine.
Please post these questions in A_C's orginal thread in future. The current discussion of any issues takes place there.
Ta
Dave
ALL SOURCE CAN BE FOUND HERE
Concerns about XDA rules:
We will never charge for our forum. Our forum is read only to anyone without registering... you must register to post. Getting downloads of the advertised kernels will be listed on both XDA and forum.savage-zen.org. Savaged-zen's download site will always be publicly accessible, and nothing we have will ever be closed source or have any fees. This meets XDA's rules.
Our team consists of 5 guys. (in order of Name(real name))
NyghtGT (Anthony) Website, Graphics
Bbedward (Brandon) Kernel
Jsseidel1 (Josh) ROM/Kernel
Luisrcastillo (Luis) Kernel
mwielgosz (Mike) ROM/nonSBC Builds
Credits
Cyanogen and team --> various code bits
toastcfh --> various commits from .35 version of CM-Kernel
#teamwin --> wimax drivers in kernel and HDMI changes in kernel for full HDMI mirror (using the HDMwIn app)
erasmus --> smartass gov
intersectRaven --> HAVS
ms79723 --> SBC Mod
Zen-Kernel team --> various modifications
If we forgot anyone or you think you should be added to credits please PM us
(credits are given to the dev's where we got some code from, may no be original designer)
Please visit http://mirror.savaged-zen.com for the download.
you can give the progress of the builds @ http://buildbot.savaged-zen.org/builders one there all green you will see them on the mirrors.
Changelog is listed on the homepage: http://www.savaged-zen.org/?page_id=57
We request that you look for updates on our forum. We will post links to download there, as well as updates to the changelog.
Keep note : We will still update OP title, and answer questions on XDA, but as we all have admin rights on the forum we dont have to depend on one person to keep updated, and it will also make it easier for us to create a WIKI
our forum is located at
http://forum.savaged-zen.org
Check out our homepage at http://www.savaged-zen.org
If you like our kernel and want to support us... donate (supports the homepage payments and then beer!!)
nonSBC Versions can be found here
SBC WARNING:The Savaged-Zen team takes no responsibly for any issues to your phone or battery, including but not limited to, battery derogation or failure. SBC has been rumored to have caused issues with battery's and claims have been made that it actually causes physical damage to your phone. It is the users responsibility to review any opinions or warnings about such claims, and by flashing kernels that include the SBC mod, the user is taking the responsibility for any issues or failures to their phone. Please research this Modification, review the code, and come to your own decision before using such modification.
reservedaaaaaaaaaa
Sweeeet! Bringing the inc out of the dark ages. We'll finally be on par with the nexus one and supersonic
Sent from my ADR6300 using XDA App
I'd love to test. Just PMed you
Just pm'd you. Im so excited!
Sent from my DROOOOOID Incredible using XDA App
running GB cm7... I will test it out!
Just responded to all the PMs, once a couple people report back i'll just make it available to the public
All i heard so far was that it booted, the first build i forgot the atmel touch screen driver, but the test2 build (the one i just sent out in the masses) includes it, so hopefully most everything works.
*EDIT*
Everyone who PM'd got a build, i'm going to wait to hear back before sending out anymore so please don't PM, if the results are good i'm going to update the OP with both test builds.
Didnt work for me. It splash looped for me.
Sent from my full_inc using XDA App
flashing now. will report back
did not work for me either, I got stuck at the incredible screen, pulled battery it got past that, the screen went black and then I noticed green/red/blue bars running vertical down my screen
dang, i was too late
I got it to boot but no touch capabilities
Updated the OP
The builds there fix the touch screen issue and probably the wifi and BT issues, although as a tendency in the newest bcm4329 drivers wifi sleep policy should probably be set to never
The people who can't boot I suspect cache/dalvik arent being wiped properly (depending on recovery, usually clockworkmod is the one with the issues). Other than that all I can think of is there's some difference between incredible and incrediblec (but i don't think it necessarily matters?)
Anyway, as I don't have an incredible i'm relying on the testers
bbedward said:
Updated the OP
The builds there fix the touch screen issue and probably the wifi and BT issues, although as a tendency in the newest bcm4329 drivers wifi sleep policy should probably be set to never
The people who can't boot I suspect cache/dalvik arent being wiped properly (depending on recovery, usually clockworkmod is the one with the issues). Other than that all I can think of is there's some difference between incredible and incrediblec (but i don't think it necessarily matters?)
Anyway, as I don't have an incredible i'm relying on the testers
Click to expand...
Click to collapse
I got a newer incredible with SLCD screen
Touchscreen works now, way to go! Now for things that don't work:
- Wifi attempts to turn on, but fails
- Bluetooth also attempts to turn on, but fails
- LED notification light doesn't seem to function for alerts, charging, or anything
Other things that work:
- GPS locks on in about 5 seconds (sitting inside of a house)
- 3G data
- Voice calls
- SMS/MMS
- Still camera
- Camcorder
- Battery charge counter
neur0tk said:
I got a newer incredible with SLCD screen
Click to expand...
Click to collapse
Could be just a missing driver then, should be easily rectified, i suspect the same with LEDs, and wifi is strange unless for some reason the module isn't probing, maybe the module goes in a different place for the incredible who knows
bbedward said:
Could be just a missing driver then, should be easily rectified, i suspect the same with LEDs, and wifi is strange unless for some reason the module isn't probing, maybe the module goes in a different place for the incredible who knows
Click to expand...
Click to collapse
Want me to modprobe for the wifi? I'll need the module name.
jonesh said:
Want me to modprobe for the wifi? I'll need the module name.
Click to expand...
Click to collapse
it's bcm4329, it's built and in there, unless something funky in the makefile is changed it should work fine.
bbedward said:
it's bcm4329, it's built and in there, unless something funky in the makefile is changed it should work fine.
Click to expand...
Click to collapse
$ su
# modprobe bcm4329
modprobe: chdir(2.6.37-Savaged-Zen-INC-0.0.1-alpha+): No such file or directory
#
Something else peculiar... I'm not sure if the phone's charging. I have it plugged into a wall outlet, and while the LED is not lit as reported before, my charge percentage is dropping. That said, the battery icon is displaying the 'animating' charge. Thoughts?
I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)
chipsharpdotcom said:
I am posting here because I haven't made the requisite 10 posts to get access to post to the development forum. Is there a developer that would be willing to help me here?
Wanted:
Dev assistance with a persistent sleep-lock and/or full-charge lock issue experienced with nearly all non-stock roms on a Samsung i897 with a fresh flash of CM 10. (CM 10 is not the relevant detail, this issue has happened with every non-stock-based rom based on anything newer than and including GB. (so GB/ICS/JB suffer this issue)
What are we calling sleep-lock?
Sleep-lock in this case is being defined as a spontaneous shutdown, lockup (requiring removal of battery to restart), or spontaneous restart of the Android OS. I understand that these three results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to be randomly happening when the phone is in a sleeping state.
What are we calling full-charge lock?
Full-Charge lock in this case is being defined as a spontaneous shutdown or lockup (requiring removal of battery to restart; I do not seem to suffer spontaneous restarts while on the charger). I understand that these two results may or may not be the product of the same root cause (in fact they're probably not) but I'm throwing them in the same bucket because they seem to all happen when the device is on the charger, but most often when the phone reaches or is near a full charge.
Troubleshooting done to date:
I have tried various ROMs over a long period of time, some were better than others, but they were all victims of this behavior. It doesn't seem to be device-specific (read as hardware) related but ever since DarkyRom that I tried shortly after I got this device a couple years ago, I have had this behavior. Stock ROMs do not suffer this behavior.
Who are you working with?
I am a Sr. Technical Team Leader for a Fortune 1000 VoIP software company and am well versed in troubleshooting methodology. I am somewhat newbish in the ways of logcat so I would ask for a little patience there, but am well versed in Windows, Linux, and many parts of the Android OS and flashing process including Odin, Hiem. and CWM. I'm seeking developer assistance because I am completely inept at code development.
The device that we're working with is a non-production (not relied upon for daily use) and I have no problem leaving it running with a logcat on it, or flashing any ROM you would ask for troubleshooting purposes. That said, the goal is to get the stable CM10 running without reboots or lockups.
Thank you in advance for your time and assistance.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)
BWolf56 said:
There are many things that can cause what we call SoD (sleep of death). First off, if you have deep idle checked on, remove that (in your ROM options).
What are the changes/mods you made after flashing CM10 (assuming stable version)?
Do you OC/UV?
And finaly, after checking for those things, there's a possible fix. It seems to have work on those who don't have a hardware issue, flashing I9000 bootloaders. The link in my sig guides you through it for the I897. (I9000 being the international version of the captivate)
If you end up going that route, I would do a clean flash. So flash stock software (KK4 no BLs) through Odin or Heimdall, flash the BLs, flash corn kernel to get root and finally flash CM10.
There are no real fix if it's a hardware issue that I'm aware of but hopefully it isn't. Also, I know you want to run CM10 on it but some people reported that running Mosaic 9 fixed their SoD problem. (It is the last I9000 ported ROM)
Click to expand...
Click to collapse
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)
chipsharpdotcom said:
Thanks for this information. I have read most of this information before, but I appreciate the info nonetheless.
Post install I don't do any customization in terms of OC/UV. So I'm fairly certain that's not it.
I'll run through what you've suggested here in order and see what I get. The specific order is the part that I've found unique. It may take a couple days to get back to you as my test cases involve a couple of charges/discharges, some "normal use" cases etc. I'll let you know my results.
Thank you again for your willingness to help. I'd like to maintain the usefullness of this device and I appreciate your assistance to that end.
--ChipSharp(DotCom)
Click to expand...
Click to collapse
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.
BWolf56 said:
If you tried the other stuff and the I9000 bootloaders don't work, chances are that it's a hardware problem.
Click to expand...
Click to collapse
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.
chipsharpdotcom said:
I'm going to give it a try right now....I'm less inclined to buy into the hardware theory though without having these problems on the Stock ROM.
Click to expand...
Click to collapse
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe
billyjed said:
Try upping the voltage/minimum clock speed. That worked for me when I was running cm9 with the glitch kernel.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for the tip...I'll try that if all of the above doesn't work. At this point, I'm all flashed up and running test cases.
So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.
chipsharpdotcom said:
So none of the suggestions here (unfortunately) provided me any different results. That said, I have discovered a couple of different variables that may play a part in this.
1.) This issue only seems to come up when I have the device plugged into power only, not when I have it plugged into a computer.
2.) I think this may be related to trying to sleep while still maintaining the clock application. It seems that when I see this most often, it is when I am plugged into the wall, and I have an alarm set. I was able to be plugged into the wall overnight last week and have no problems without the alarm set, but when I set the alarm, I had the sleep-lock issue (and moreover as you would expect, my alarm did not sound).
Again, I have none of these problems with the stock ROM. I'm going to continue to test on this and hack around on it to see if I can hunt this down, but my concern is that the very things that allow me to troubleshoot are the same things that keep the device from reproducing the error.
You can subscribe to this thread if you care to continue watching the progress, or if you have any similar experiences or potential solutions, but this is one of those issues that if I don't find the root cause, it's going to drive me bat-s%#$-f&@!#%-crazy. I'm aware that even if I get to the root cause I will likely never see a fix for the problem being that this device is so old, but this is caught in my teeth now, and I'm going to have a hard time letting it go.
As always thank you all for your assistance and participation.
Click to expand...
Click to collapse
Have you tried it with a different clock app? I mean, if I understand this correctly, it seems to be narrowed down to your current clock apk, which is different than the stock GB one. So I would suggest freezing (or unistalling) your current one with Tibu and trying a different one.
That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.
chipsharpdotcom said:
That's actually my next step.
I'm not sure it's accurate to say that I have it narrowed down to the clock app, I simply noted that I reproduced the issue on wall power and with the alarm set. That could all be coincidence. I need to try to reproduce those scenarios more reliably and in a more controlled method.
Do you know of an app I could install that would cause my battery to discharge fairly quickly? It would speed up my troubleshooting.
Click to expand...
Click to collapse
Haha first time I ever get that question but leaving your camera on should do the job (or video playing)
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
SpGG said:
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
Click to expand...
Click to collapse
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
optimumpro said:
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
Click to expand...
Click to collapse
I didn't change anything. Same thing when I went for a new nightly of cm12.1 I did nothing out of the ordinary. Since I did not have new problems since the above mentioned, I didn't delve any further. Today I had another, interesting issue. No one was able to call the phone and I wasn't able to call out, even though the network showed up as fine with full bars. This lasted for several hours. I went into flight mode and back out of flight mode and the issue was fixed. Several SMS arrived about calls missed. And again, I have no idea if this was caused by the hardware, an issue with the software or even the network.
And that is the frustrating thing: How can I find out who the culprit is? Are there good system crash diagnostic tools? Because so far I haven't seen anything.
Greetings,
No matter where I look I see developers just ignoring us across multiple sites on a fix for this for us guys without f2fs format. Be straight with us, is there a fix for this? Or do we have to continue to install our modules with TWRP. It's very inconvenient and annoying. But, I believe we do deserve an answer to this infamous question. None of the "clear cache blahblahblah" answers work. I've been struggling with this issue across 4 seperate devices since Magisk v15.1 and I'd like a resolution as I have been patiently asking and waiting for over 5 months. The only resolution I have found is to completely format my phone and not update anything. I encourage others to help this post reach the developers. Thank you!
Perfect opportunity for you to gather all the necessary data in one single place.
Post all the device details, ROM info, logs, what doesn't work, what does work, what used to work, etc, even if you or anyone else have posted it before elsewhere. XDA is a big place and things get lost in the noise. Personally I've tried to keep a record of some of these issues, but it's much better if that's kept by someone who knows and experiences them.
And a couple of notes:
Very few things are ignored around here. If it is, that's usually because there's not enough info to troubleshoot.
And, you write "developers", in plural. Magisk only has the one, and he's very busy with real life at the moment. That he takes the time to do any coding at all during the weekends is just a bonus.