Senior Member - OP
Thanks Meter 4531
Posts: 2,399
Join Date: Sep 2011
Location: Immokalee/Tampa FL
DONATE TO ME
|
Quote:
Originally Posted by Jnoles07
I get system UI closes constantly while in any app, including this one. The nav bar disappears for a couple seconds then comes back. Cleanest install possible. Launcher shouldn't matter since it is only while in an app but I'm running the standard nova Launcher, unhacked.
Edit: I found a fix. In rom control in the navigation bar just enable four buttons instead of the standard three. I chose to make the fourth button menu. No force closes, and it comes in handy actually.
Oh, this is hands down the best mod/theme for our phone. Thank you.
Sent from my SPH-D710 using xda premium
|
NP man, if this works for the other guy getting System UI FC's, I'll add to OP. Make sure to thank the mod creator also!
Quote:
Originally Posted by flaheat88
This is Killer.. working flawlessly on AOKP build 33...
|
NP, enjoy.
Quote:
Originally Posted by sjsharksfan420
This tabletUI is freakin SICK! It actually makes your phone sicker on AoKP or NV! I tested on NV and as long as you use b32 for now, its good to go, now since I updated and nandroided NV, gonna do the same for AoKP now..
sj
Sent from my sgs2e4gt on AoKPb33 FD19 aOS 4.0.4 using Tap@Talk 2 Beta 5
|
It does look pretty sick, have fun.
Quote:
Originally Posted by Carbajal3009
Yes fresh install on everything. So far I've tried go launcher.. nova launcher.. adw ex and I get random UI fcs  I can live with it for now.. but gets annoying...  that's my only problem. Other than that all is good.  thanks for such a great find
Sent from my SPH-D710 using Tapatalk 2 Beta-5
|
Try doing what Jnoles07 did. In rom control settings under nav bar options, set 4 buttons instead of the standard 3. Your choice on what it controls. If you are doing so already, idk what to say since I have had no FC's since I flashed it. Enjoy.
Sent from my SPH-D710 using Tapatalk
I don't answer rom support questions through PM! You will be ignored! Post your question in the relevant thread instead.
|