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

Root Redux 2 Frequent Crashes

The random crashes I was suffering from were due to flashing a modded kernal and messing around with undervolting and overclocking.
So nothing to do with the rom as I have used it for best part of 2 months and not had a problem apart from when I messed it up.
 
Paul Anderson said:
The random crashes I was suffering from were due to flashing a modded kernal and messing around with undervolting and overclocking.
So nothing to do with the rom as I have used it for best part of 2 months and not had a problem apart from when I messed it up.
Click to expand...

Agreed, I now believe my issues were due to the fact I had not done a full wipe before moving from 1.2 to v2, and should not be taken as a criticism of the ROM. It's the fastest ROM I've tried, and I can't recommend it enough!
 
Paul Anderson said:
Really fancy undervolting so may try again to get better battery life.
Click to expand...

What do you mean by this statement? You should already be undervolted if you're not on a stock rom. See my kernel info thread for details (accessible via my signature).
 
What I meant was that I tried tweeking it even further using incredicontrol and guess I just pushed it to far which caused even more issues. Had no issues with the rom and its kernal. Problems only arose when I flashed the mod 6 of the thalamus kernal and pushed the undervolting & overclocking resulting in instability
I will check your guides for further info. On a different subject can I use your rom with standard h boot or is this pointless as wont gain from the space saving?
 
UPDATE:

Since doing a complete wipe and reinstall, the phone worked fine for about a week. However, in the last few days, I've had a few reboots of the same sort, not as frequent, but still as random. Today, I think I managed to capture a log of the exact moment when the crash took place, but I'm not well versed enough in what the log entries mean, so I thought I'd post an extract here, for more clever minds to investigate (apologies for the length):
09-30 15:47:16.700 W/Watchdog(14305) : *** WATCHDOG KILLING SYSTEM PROCESS: com.android.server.am.ActivityManagerService
09-30 15:47:16.760 I/ActivityThread(8782) : Removing dead content provider: settings
09-30 15:47:16.760 I/ActivityThread(8370) : Removing dead content provider: settings
09-30 15:47:16.760 I/ActivityThread(8326) : Removing dead content provider: settings
09-30 15:47:16.770 I/ActivityThread(4576) : Removing dead content provider: settings
09-30 15:47:16.780 I/ActivityThread(3787) : Removing dead content provider: settings
09-30 15:47:16.780 I/ActivityThread(2708) : Removing dead content provider: settings
09-30 15:47:16.780 I/ActivityThread(24986) : Removing dead content provider: settings
09-30 15:47:16.780 I/ActivityThread(24762) : Removing dead content provider: settings
09-30 15:47:16.780 I/ActivityThread(20816) : Removing dead content provider: settings
09-30 15:47:16.780 I/ActivityThread(14400) : Removing dead content provider: settings
09-30 15:47:16.780 I/ActivityThread(14424) : Removing dead content provider: settings
09-30 15:47:16.790 I/ActivityThread(8208) : Removing dead content provider: settings
09-30 15:47:16.790 I/ActivityThread(7593) : Removing dead content provider: settings
09-30 15:47:16.800 I/ActivityThread(7877) : Removing dead content provider: settings
09-30 15:47:16.800 I/ActivityThread(8791) : Removing dead content provider: settings
09-30 15:47:16.800 I/ActivityThread(7992) : Removing dead content provider: settings
09-30 15:47:16.810 I/ActivityThread(7052) : Removing dead content provider: settings
09-30 15:47:16.810 I/ActivityThread(639) : Removing dead content provider: settings
09-30 15:47:16.890 E/AndroidRuntime(8808) : FATAL EXCEPTION: main
09-30 15:47:16.890 E/AndroidRuntime(8808) : java.lang.NullPointerException
09-30 15:47:16.890 E/AndroidRuntime(8808) : at android.app.ActivityThread.attach(ActivityThread.java:3603)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at android.app.ActivityThread.main(ActivityThread.java:3676)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at java.lang.reflect.Method.invokeNative(Native Method)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at java.lang.reflect.Method.invoke(Method.java:507)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at dalvik.system.NativeStart.main(Native Method)
09-30 15:47:16.890 E/AndroidRuntime(8808) : Error reporting crash
09-30 15:47:16.890 E/AndroidRuntime(8808) : java.lang.NullPointerException
09-30 15:47:16.890 E/AndroidRuntime(8808) : at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:854)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:851)
09-30 15:47:16.890 E/AndroidRuntime(8808) : at dalvik.system.NativeStart.main(Native Method)
09-30 15:47:24.047 I/SystemServer(8831) : Entered the Android system server!
09-30 15:47:24.057 I/SystemServer(8831) : Entropy Service
09-30 15:47:24.107 I/SystemServer(8831) : Power Manager
09-30 15:47:24.117 I/SystemServer(8831) : Activity Manager
09-30 15:47:24.137 I/ActivityManager(8831) : Memory class: 32
09-30 15:47:24.628 I/SystemServer(8831) : Telephony Registry
09-30 15:47:24.628 I/SystemServer(8831) : Package Manager
09-30 15:47:24.648 I/Installer(8831) : connecting...

I included a few lines before and after the crash event, in case they might be important, but I've also got a copy of the whole log, if that would be helpful, I'll post it as an attachment.
Do you guys think this is worth notifying ihlades about? I'm not able to post on his xda forum, but I can send him a PM if it looks fixable.

Cheers,
Erik
 
I don't know enough about Android to make much sense of that, but the exception looks internal to the ROM based and it looks like it could/should be caught by the OS even if it's being caused by an app. So yeah, I would say that is worth reporting to ihlades. He's been away on holiday apparently, so you probably won't get an immediate response.
 
adskankster said:
I don't know enough about Android to make much sense of that, but the exception looks internal to the ROM based and it looks like it could/should be caught by the OS even if it's being caused by an app. So yeah, I would say that is worth reporting to ihlades. He's been away on holiday apparently, so you probably won't get an immediate response.
Click to expand...

Thanks, I've just dropped him a PM. Yeah, saw his holiday notice on Twitter, hope he's having a great time! :)

Cheers,
Erik
 
Has anyone had issues receiving mms on redux 2. All I seem to get a force close on process.mms any ideas?
 
ernolander said:
UPDATE:


Do you guys think this is worth notifying ihlades about? I'm not able to post on his xda forum, but I can send him a PM if it looks fixable.

Cheers,
Erik
Click to expand...

FYI ihlades has said on twitter that he is giving up the Redux2 development due to personal issues.
Good luck to him
 
Paul Anderson said:
FYI ihlades has said on twitter that he is giving up the Redux2 development due to personal issues.
Good luck to him
Click to expand...

That is a great shame, indeed, but best of luck to him, as said. It's a pity, as I've managed to record a couple of more instances of the reboot behaviour, and it does look like a ROM bug, to my untrained eyes at least.
I did send him a log of the first instance I recorded, but it doesn't look very probable that it will get picked up now, I guess...
 
Pity. Jumped ship from LeeDroid roms as he's moved on to other devices. Redux 2 looked like it could be quite active but seems not :(

Hopefully someone will pick up the development

Only had one 'reboot' in the 5 days I've been using Redux. Only knew about it as I go the SIM unlock screen, the hours up counter did not register it either. I can certainly cope with that happening one a week.
 
dGB isn't going to detract from a loyal Redux user base and tbh, it's not intended it. Its just that Redux is a great base to start on which is why I chose it when designing dGB. It was my favourite but it had some fairly obvvious hangups. Most notably Rastamans image quality issue (which we all had but only he paid enough attention to notice it). But once you knew about it, it was very annoying.
 
SUroot said:
dGB isn't going to detract from a loyal Redux user base and tbh, it's not intended it. Its just that Redux is a great base to start on which is why I chose it when designing dGB. It was my favourite but it had some fairly obvvious hangups. Most notably Rastamans image quality issue (which we all had but only he paid enough attention to notice it). But once you knew about it, it was very annoying.
Click to expand...
rastavision, its a bitch lol
 
hahaha. Oddly, as I would normally expect rastavision to be like normal vision but a bit hazy ;)
 
You must log in or register to reply here.
Back
Top Bottom