Looks like you flashed the ROM without clearing caches and data.
No, some people even get it as soon as it boots up and I have seen it myself too. I dont have to install anything to get it and other times it takes a few hours to get one after I turn on wifi or bluetooth or make a call.Very strange, our beta users dont have this issue. Are you doing anything after flashing the ROM? any backups etc?
As I said, not a bug we've encountered in testing./No, some people even get it as soon as it boots up and I have seen it myself too. I dont have to install anything to get it and other times it takes a few hours to get one after I turn on wifi or bluetooth or make a call.
Thanks for the reply, we have all tried that too. Just about every combo you can think of. If you you look at the logcat file it appears that inside the function "updateTelephonySignalStrength" at line 494 is the culprit, it is trying to adjust the signal strength and going beyond the length. Here is a snipit of the logcat:try t oflash it again clear dalvik and cache partition and then flash the rom
I dont mind doing it since you guys have so many ROM's to maintain but any way. I have attached a link to the files I replace every week. The files are in /com/android/systemui/statusbar/policy directory after a baksmali of SystemUI.apk. Basically I expand the the arrays by 1 to accomadate the return of the 6th element (index 5). If you do a diff between the stock and mine you will see that a few constants are changed and add an array element to all arrays that duplicates the 5th element. Again as I said I know you guys always have your hands full and I dont mind doing it if you guys need to be on more important things.If you can provide the smali edits and what changed i will implement your fix.