Trying to Hellraise Chameleon v1.2 - Samsung/AOSP hybrid?

[Simba501]

Ditto... using flashaholics and using rockratt's fix didn't help either. Something in the hellraising must be reverting some change that jazzk made to get his ROM running Samsung+aosp

Sent from my SGH-I777 using xda app-developers app

That's what I was thinking. Was that with 1.3?

Sent from my Galaxy S2

 

[stone_ship]

Ditto... using flashaholics and using rockratt's fix didn't help either. Something in the hellraising must be reverting some change that jazzk made to get his ROM running Samsung+aosp

Sent from my SGH-I777 using xda app-developers app

I think it happens when Android is trying to update the signal strength status, and/or the battery meter. The following appears in logcat before every crash:

09-25 18:44:37.922 E/JavaBinder(2237): *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
09-25 18:44:37.922 E/JavaBinder(2237): java.lang.ArrayIndexOutOfBoundsException: length=5; index=5
09-25 18:44:37.922 E/JavaBinder(2237): 	at com.android.internal.os.BatteryStatsImpl.updateAllPhoneStateLocked(BatteryStatsImpl.java)
09-25 18:44:37.922 E/JavaBinder(2237): 	at com.android.internal.os.BatteryStatsImpl.notePhoneSignalStrengthLocked(BatteryStatsImpl.java)
09-25 18:44:37.922 E/JavaBinder(2237): 	at com.android.server.am.BatteryStatsService.notePhoneSignalStrength(BatteryStatsService.java:212)
09-25 18:44:37.922 E/JavaBinder(2237): 	at com.android.server.TelephonyRegistry.broadcastSignalStrengthChanged(TelephonyRegistry.java:576)
09-25 18:44:37.922 E/JavaBinder(2237): 	at com.android.server.TelephonyRegistry.notifySignalStrength(TelephonyRegistry.java:337)
09-25 18:44:37.922 E/JavaBinder(2237): 	at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java)
09-25 18:44:37.922 E/JavaBinder(2237): 	at android.os.Binder.execTransact(Binder.java)
09-25 18:44:37.922 E/JavaBinder(2237): 	at dalvik.system.NativeStart.run(Native Method)
09-25 18:44:37.927 E/AndroidRuntime(12165): FATAL EXCEPTION: main
09-25 18:44:37.927 E/AndroidRuntime(12165): java.lang.ArrayIndexOutOfBoundsException: length=5; index=5
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at com.android.systemui.statusbar.policy.NetworkController.updateTelephonySignalStrength(NetworkController.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at com.android.systemui.statusbar.policy.NetworkController.access$000(NetworkController.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at com.android.systemui.statusbar.policy.NetworkController$1.onSignalStrengthsChanged(NetworkController.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at android.telephony.PhoneStateListener$2.handleMessage(PhoneStateListener.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at android.os.Handler.dispatchMessage(Handler.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at android.os.Looper.loop(Looper.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at android.app.ActivityThread.main(ActivityThread.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at java.lang.reflect.Method.invokeNative(Native Method)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at java.lang.reflect.Method.invoke(Method.java:511)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
09-25 18:44:37.927 E/AndroidRuntime(12165): 	at dalvik.system.NativeStart.main(Native Method)
09-25 18:44:37.947 E/android.os.Debug(2237): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error

That was tonight on the new 1.3. What to do with this log is really beyond me at this point. Full log here for anyone interested: http://pastie.org/4801216

 

[mapobean]

RockRatt, I have tried to port the new Chameleon 2.0 Experimental and was not successfull doing so, i kept getting system ui crash. I downloaded your update zip and it works perfect after clearing the android.phone crash twice. Thank you

 

[stone_ship]

Nice that you got it working. Can you update us if you do get System UI crashes after a day or two? I noticed you are near me (geographically) so I'd be interested if you have this ROM running stably. For some reason, I keep thinking my crashes are something related to the firmware not being able to understand how AT&T's netwok is set up. Or something...

RockRatt, I have tried to port the new Chameleon 2.0 Experimental and was not successfull doing so, i kept getting system ui crash. I downloaded your update zip and it works perfect after clearing the android.phone crash twice. Thank you

 

[ChefAnt]

Why don't people just manually hellraise roms? It's quicker and easier! I do it on with every I9100 rom I try. No offense to any of the porters but I don't trust a non dev making a rom that could potentially turn my phone into a very high tech paper weight. If I screw it up I have no one to blame.

 

[stone_ship]

Why don't people just manually hellraise roms? It's quicker and easier! I do it on with every I9100 rom I try. No offense to any of the porters but I don't trust a non dev making a rom that could potentially turn my phone into a very high tech paper weight. If I screw it up I have no one to blame.

Well, people have done it both manually and with Flashaholic with this ROM. It's a stability issue we're talking about. Specifically, I can't get this to be stable on my phone even though virtually every other i9100 ROM works fine for me.

 

[mapobean]

Update on Chameleon 2.0 Experimental: I have run this Rom for approximately 8 hrs yesterday without 1 system ui issue until i moved my location (i.e. while driving). It seems as if it is a roaming issue that causes the not responding issue but after manually overwriting the apns-conf.xml with a stock one with ATT 3G SIM, ATT MMS, and ATT PHONE, the issue persisted this morning while driving through areas of little coverage. I was however able to use the phone and all its functions (camera is awesome + video) even Bluetooth audio and phone connected no problem. While i did get the system.ui not responding it did not force close my Bluetooth audio (i was listening to The Adam Corolla Show podcast on Pocket casts). If anyone has any ideas i am going to run this for another day or so trying to narrow down the cause. It seems as though the problem only happens when moving to different cell reception area.

 

[Spacemonkie4207]

I think flashing the wrong kernel or modem is most dangerous. Can a ROM do harm? As long as you flash proper kernel before booting system?

 

[RockRatt]

I think flashing the wrong kernel or modem is most dangerous. Can a ROM do harm? As long as you flash proper kernel before booting system?

Flashing a modem in cwm is never dangerous. Flashing a rom can be an issue if something in it is not compatible. Same for a kernel.

We can usually flash a i9100 kernel and usually we just lose our buttons properly. We can flash a i9100 modem and just lose the ability for making calls. Flashing a rom can put you in a boot loop as well. Now USUALLY if you know what your doing to any extent all the above can be fixed by flashing the CORRECT kernel, modem, rom for our phone.

Where we get in trouble is if we flash sometjing that changes either of the bootloaders or flashing a rom, kernel from a device NOT EVEN CLOSE to our phone. For example all the Skyrocket people flashing something from our forum onto their phone. Or flashing or trying to flash something with rom manager.

Sent from My SGH-I777 Running Spiderman Themed AOKP or Spiderman Themed CM10

 

[shri_chanakya]

has anyone tried 3.0 version? any luck?

 

[stone_ship]

has anyone tried 3.0 version? any luck?

I have tried. No luck, same issues.

 

[jthatch12]

I'll hellraise it for 5 doll hairs . Side note RockRatt got 2 NFC JB patches for you to try on my thread. One is a remover and one is just latest update

Sent from my SGH-I777 using xda premium

 

[shri_chanakya]

I was able to hell raise it. steps i followed.

1. flash 3.0 beta
2. flash key libs hellraiser to map key.
3. flash jeboo kernel from shostock3 thread.
4. flash modem.

booted up fine with FC on system ui for some time. after multiple fc on system ui it is working fine with no fc so far.
this is without any notification toggle so real pain. would try to see if i can get another system ui flashed on it.