[Retired][ROM]Superclean 2.9.2 EA15/EB01/EB16/EC10 Based

Is touchdown a free app?

It's $19.99 but well worth it imho. I've used it for over a year and it's way ahead of the native email clients. There should be a trial in the market that you can test before you have to purchase the license. Just make sure you get the 2.x version.
 
Hate to say it but I don't think the lock is the issue. The 5 locks has been a part of superclean for a while now and there's nothing in the changelog that seems like it would conflict, especially with only one of the locks. And sbrissen, who came up with the 5 locks package worked closely with Adrynalyne or with some assistance from Adrynalyne when he made it if I'm remembering correctly from sbrissen's tread over at XDA.

I'm sure you're right about that. I just found something cool out about my phone though, for each reboot I've had it has stored the error on my SD card as a text file. Not sure what we can do with it but it's good to know that feature exists. And, from my count here I've had 6 random reboots (6 files all from today).
 
I'm sure you're right about that. I just found something cool out about my phone though, for each reboot I've had it has stored the error on my SD card as a text file. Not sure what we can do with it but it's good to know that feature exists. And, from my count here I've had 6 random reboots (6 files all from today).

Yeah we need to get in touch with Adryn so we can send those to him.
 
Yeah we need to get in touch with Adryn so we can send those to him.

I sent him a logcat earlier to go over. I saved a new one immediately after this last reboot, which I am going to fire off shortly. But these files I found are COMPLETE system dumps performed after each error reboot. Makes me curious as to why it would do that. Useful, but still curious. Plus, these files are MASSIVE, at least by txt standards. They can't be sent the way Adrynalyne wants them to be.
 
Yeah we need to get in touch with Adryn so we can send those to him.

I sent him a logcat earlier to go over. I saved a new one immediately after this last reboot, which I am going to fire off shortly. But these files I found are COMPLETE system dumps performed after each error reboot. Makes me curious as to why it would do that. Useful, but still curious. Plus, these files are MASSIVE, at least by txt standards. They can't be sent the way Adrynalyne wants them to be.

I just checked and he's logged off right now, probably so he won't be disturbed while he's working on your problem, or he's just resting, he has been working his arse off lately putting 2.9 together. But he'll get whatever you send him once he logs back in.
 
I just checked and he's logged off right now, probably so he won't be disturbed while he's working on your problem, or he's just resting, he has been working his arse off lately putting 2.9 together. But he'll get whatever you send him once he logs back in.

He definitely deserves a good rest, heck if I was rich I'd send the man on a vacation for all the work he's done.

Just curious shark, what are you running right now? All I've been doing is comparing with phones that are affected, not unaffected ones.
 
I'm sure he'll be here in a bit. He just posted on xda that it may be the lock screen because of the music controls
 
jcom, can you PM me however Adryn told you to contact him and how to send the logs so I can just send them now?
 
He definitely deserves a good rest, heck if I was rich I'd send the man on a vacation for all the work he's done.

Just curious shark, what are you running right now? All I've been doing is comparing with phones that are affected, not unaffected ones.

Running 2.9 nonvoodoo with NitroComb theme, nuance patch, tw clock patch, Launcher Pro, Beautiful smaller home weather widget.
 
Running 2.9 nonvoodoo with NitroComb theme, nuance patch, tw clock patch, Launcher Pro, Beautiful smaller home weather widget.

Thanks. Besides Beautiful widgets home we're not running anything else similar. I'm voodoo with no themes, asop launcher, no TW, no nuance, no extra widgets. This has me baffled.

Edit: never mind, it seems the issue has been partially solved. I'm glad too, I'm really digging the battery life and stability of this build.
 
Two things. I swear I saw a patch somewhere that would fix the text messaging issues (SMS over 160 characters converting to MMS)... but after searching multiple threads I can't seem to find it. Can anyone point me in the right direction or supply the link please?

Secondly,

Anyone interested in trying a GPS mod (for those with bad GPS)?

Just flash in cwr, and disable/re-enable all your agps and gps settings on next reboot.

gps_fix_2.zip

How exactly do you disable/re-enable agps/gps? Is this done through Settings > Location & Security > Standalone GPS Services / Google Location Services? I'd love to apply the GPS mod and give it a try since I use the Navigation often.

Thanks in advance ;):D
 
I'm just scratching my head at the lockscreen being the cause. I've been using the rotary unlock for a while now and haven't had any issues with 2.9. And I loaded it up within 5 minutes of Adry releasing it yesterday.
 
I'm just scratching my head at the lockscreen being the cause. I've been using the rotary unlock for a while now and haven't had any issues with 2.9. And I loaded it up within 5 minutes of Adry releasing it yesterday.

After reading through the XDA thread on SC 2.9 it seems that this issue is hit or miss. As of right now there is no EXACT cause as to why those lockscreens are the issue, but the best guess is something related to the music controls since those are REALLY the only difference.
 
For those who doubt the lockscreen causing it:

E/AndroidRuntime( 4032): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy
E/AndroidRuntime( 4032): java.lang.NullPointerException
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.LockScreen.<init>(LockScreen.java:231)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.LockPatternKeyguardView.createLockScreen(LockPattern
KeyguardView.java:1191)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.LockPatternKeyguardView.<init>(LockPatternKeyguardVi
ew.java:541)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.LockPatternKeyguardViewProperties.createKeyguardView
(LockPatternKeyguardViewProperties.java:48)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.KeyguardViewManager.show(KeyguardViewManager.java:16
3)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.KeyguardViewMediator.handleShow(KeyguardViewMediator
.java:1464)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.KeyguardViewMediator.access$2200(KeyguardViewMediato
r.java:103)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.KeyguardViewMediator$4.handleMessage(KeyguardViewMed
iator.java:1304)
E/AndroidRuntime( 4032): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4032): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 4032): at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:62


There is a patch on the front page.
 
Well, actually, it was mine :D

Someone tweeted me a hint to follow up, and I started connecting the dots. I never saw your logcat. If you pm'ed me on XDA, thats why. I've been under the weather today. So I'm not purposely ignoring anyone.

I'll talk with sbrissen tomorrow, and look closer at the issue. I just feel horrible tonight.
 
For those who doubt the lockscreen causing it:

E/AndroidRuntime( 4032): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy
E/AndroidRuntime( 4032): java.lang.NullPointerException
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.LockScreen.<init>(LockScreen.java:231)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.LockPatternKeyguardView.createLockScreen(LockPattern
KeyguardView.java:1191)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.LockPatternKeyguardView.<init>(LockPatternKeyguardVi
ew.java:541)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.LockPatternKeyguardViewProperties.createKeyguardView
(LockPatternKeyguardViewProperties.java:48)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.KeyguardViewManager.show(KeyguardViewManager.java:16
3)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.KeyguardViewMediator.handleShow(KeyguardViewMediator
.java:1464)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.KeyguardViewMediator.access$2200(KeyguardViewMediato
r.java:103)
E/AndroidRuntime( 4032): at com.android.internal.policy.impl.KeyguardViewMediator$4.handleMessage(KeyguardViewMed
iator.java:1304)
E/AndroidRuntime( 4032): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4032): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 4032): at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:62


There is a patch on the front page.

Not doubting at all. Your word is gold in my book and would have been good enough. Just scratching my head, because I don't understand the technical side.
 
I don't either, until i decompile and take a look.

I'm just not up to it tonight.

Go take care of yourself and get some rest. And when I say I don't understand I mean I really don't understand all that stuff :p What you posted may as well have been posted in Farsi, Urdu, Chinese, Polish, or any of the multitude of languages I don't understand. I'm just a guy who's been able to learn and understand how to root and flash pretty quickly. Thanks again for all you do.
 

Trending Posts

Forum statistics

Threads
957,080
Messages
6,971,384
Members
3,163,709
Latest member
texmaster