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

Root [rom] pac-man

Root access was broken a few days ago when we switched some repos around. I think it's fixed starting with today's build.
 
I'm not having these root problems. Its just that this ROM isn't as stable as CM.

After being back on it for 2 days, I don't like how unstable it is.

Tumblr, Shuttle+(my main music player), Reddit is fun, and the Stock browser all crash so hard so I couldn't go on Tumblr and had to switch Reddit apps and also I had use Apollo(ugh).also I had to use Opera mini as it is my backup because chrome just sucks...

I'm going to AOKP to see what the fuss is about. Also, video playback is completely fudged in this ROM. Can't watch my pr0n and can't go on YouTube at all because weird lines appear all over the videos and black out half the screen. And usually it froze my phone requiring a battery pull.

Also Halo sucks IMO. I put it there so I could have a quick way to text really fast and it sucks up other notifications so my alarm always shows up in because I have a persistsnt notification for my alarm app. Also when I get Reddit mail from my Reddit News app, it shows up in Halo and wont go away from halo until I swipe up halo to make it go away then tap the halo button up top. This also happens for any other notification like market installs requiring me to swipe up and away halo and get it back again.

So Halo isn't worth the hassle(maybe my settings are wrong or something) and the ROM is really unstable, and Video playback is compleltly broken. Maybe its the halo introduction that messed up this ROM because when I was on it 2-3 months ago it was better but actually got unstable over the 2-3 weeks I was on it for some reason. Now its been unstable since day one. Goodbye PAC-man.
 
SilentSmoke11 said:
I'm not having these root problems. Its just that this ROM isn't as stable as CM.

After being back on it for 2 days, I don't like how unstable it is.

Tumblr, Shuttle+(my main music player), Reddit is fun, and the Stock browser all crash so hard so I couldn't go on Tumblr and had to switch Reddit apps and also I had use Apollo(ugh).also I had to use Opera mini as it is my backup because chrome just sucks...

I'm going to AOKP to see what the fuss is about. Also, video playback is completely fudged in this ROM. Can't watch my pr0n and can't go on YouTube at all because weird lines appear all over the videos and black out half the screen. And usually it froze my phone requiring a battery pull.

Also Halo sucks IMO. I put it there so I could have a quick way to text really fast and it sucks up other notifications so my alarm always shows up in because I have a persistsnt notification for my alarm app. Also when I get Reddit mail from my Reddit News app, it shows up in Halo and wont go away from halo until I swipe up halo to make it go away then tap the halo button up top. This also happens for any other notification like market installs requiring me to swipe up and away halo and get it back again.

So Halo isn't worth the hassle(maybe my settings are wrong or something) and the ROM is really unstable, and Video playback is compleltly broken. Maybe its the halo introduction that messed up this ROM because when I was on it 2-3 months ago it was better but actually got unstable over the 2-3 weeks I was on it for some reason. Now its been unstable since day one. Goodbye PAC-man.
Click to expand...

Wow. I haven't had any of these with Pac. Though I'm not a huge fan of halo either. Neat idea... lot of hassle. Maybe it would be nice on a tablet though.

The rest of the stuff though... crazy. I've only had a couple times that I hard locked and most of those were because I was testing different voltages which don't always work.

Sorry that you're having all these issues. Sucks.

Sent from my VS920 4G using Tapatalk 2
 
I've had so many weird issues with the nightly builds on both CM & PAC that I've decided to stick with just the RC builds.

And after spending the day trying to break it (to find the cause), that weird problem with my notifications bar disappearing has all but gone - for now.
 
Stackrat said:
I've had so many weird issues with the nightly builds on both CM & PAC that I've decided to stick with just the RC builds.

And after spending the day trying to break it (to find the cause), that weird problem with my notifications bar disappearing has all but gone - for now.
Click to expand...

Here's an idea to fix the disappearing notification bar. This I don't believe will stick through reboots... but it might be good to try.

I've been reading the V6 supercharger thread a bit, since it discusses OOM groupings a bit. It seems like the higher the number, the more likely it is to get killed and suggests Auto Memory Manager (oom manger, not a task killer). Using apex launcher with it locked in memory I noticed that it's OOM setting is at 3. This means that the lowmem killer will kill it if need be. This could also be happening during cleanups. In that app, if I tell it to keep the launcher alive, it sets it to -17. Pretty sure that'll do it. Yep.

Try that and see if you get redraws... you shouldn't.
 
Yoinx said:
Here's an idea to fix the disappearing notification bar. This I don't believe will stick through reboots... but it might be good to try.

I've been reading the V6 supercharger thread a bit, since it discusses OOM groupings a bit. It seems like the higher the number, the more likely it is to get killed and suggests Auto Memory Manager (oom manger, not a task killer). Using apex launcher with it locked in memory I noticed that it's OOM setting is at 3. This means that the lowmem killer will kill it if need be. This could also be happening during cleanups. In that app, if I tell it to keep the launcher alive, it sets it to -17. Pretty sure that'll do it. Yep.

Try that and see if you get redraws... you shouldn't.
Click to expand...
I think you may be on to something. If I recall, the V6 Supercharger script detects the launcher app and allows you to set the OOM ("bullet-proof", "hard to kill", options like that - which I assume sets the OOM level). Your settings likely set the OOM level for your launcher (Apex), which isn't the same one I'm running (Holo - though I'm not sure why yours is "3" unless you were running another launcher when you initially ran the V6 script).
 
Stackrat said:
I think you may be on to something. If I recall, the V6 Supercharger script detects the launcher app and allows you to set the OOM ("bullet-proof", "hard to kill", options like that - which I assume sets the OOM level). Your settings likely set the OOM level for your launcher (Apex), which isn't the same one I'm running (Holo - though I'm not sure why yours is "3" unless you were running another launcher when you initially ran the V6 script).
Click to expand...

Actually, I hadn't ran V6 this time. That's the setting that the launcher itself gives itself when you tell it to lock in memory. I believe that V6 now doesn't set it below 0 either.

If that's teh case, yours may be getting killed still.
 
Not sure if I'm the only one with this going on. But I've always had bluetooth issues, so it wouldn't surprise me if I am.

When trying to connect via bluetooth to my laptop I get an odd error.

E/bt-btif (13198): ## btif_config_get assert section && *section && key && *key && name && *name && bytes && type failed at line:182 ##
Click to expand...


Here's the relative section around it:

D/BluetoothAdapterService(1088608608)(13198): getState(): mAdapterProperties: com.android.bluetooth.btservice.AdapterProperties@40e2e9e0
I/bt_userial_vendor(13198): userial vendor open: opening /dev/ttyHS0
I/bt_userial_vendor(13198): device fd = 56 open
I/GKI_LINUX(13198): gki_task_entry: gki_task_entry task_id=0 [BTU] starting
I/bt_hwcfg(13198): bt vendor lib: set UART baud 4000000
D/bt_hwcfg(13198): Chipset BCM4330B1
D/bt_hwcfg(13198): Target name = [BCM4330B1]
I/bt_hwcfg(13198): Found patchfile: /etc/firmware//BCM4330B14.hcd
I/bt_hwcfg(13198): bt vendor lib: set UART baud 115200
D/bt_hwcfg(13198): Settlement delay -- 100 ms
I/ActivityManager( 602): No longer want com.android.exchange (pid 13112): empty #2
D/BluetoothMasReceiver(13198): Bluetooth STATE CHANGED to 11
I/bt_hwcfg(13198): bt vendor lib: set UART baud 4000000
I/bt_hwcfg(13198): Setting local bd addr to 00:AA:70:49:25:9F
I/bt_hwcfg(13198): vendor lib fwcfg completed
I/ (13198): BTE_InitTraceLevels -- TRC_HCI
I/ (13198): BTE_InitTraceLevels -- TRC_L2CAP
I/ (13198): BTE_InitTraceLevels -- TRC_RFCOMM
I/ (13198): BTE_InitTraceLevels -- TRC_AVDT
I/ (13198): BTE_InitTraceLevels -- TRC_AVRC
I/ (13198): BTE_InitTraceLevels -- TRC_A2D
I/ (13198): BTE_InitTraceLevels -- TRC_BNEP
I/ (13198): BTE_InitTraceLevels -- TRC_BTM
I/ (13198): BTE_InitTraceLevels -- TRC_PAN
I/ (13198): BTE_InitTraceLevels -- TRC_SDP
I/ (13198): BTE_InitTraceLevels -- TRC_BTAPP
I/ (13198): BTE_InitTraceLevels -- TRC_BTIF
D/dalvikvm(11653): GC_FOR_ALLOC freed 1651K, 73% free 3154K/11420K, paused 24ms, total 24ms
E/bt-btif (13198): Calling BTA_HhEnable
E/bt-btif (13198): ## btif_config_get assert section && *section && key && *key && name && *name && bytes && type failed at line:182 ##
E/bt-btif (13198): btif_storage_get_adapter_property service_mask:0x140040
D/BluetoothManagerService( 602): Bluetooth Adapter name changed to VS920 4G
D/BluetoothManagerService( 602): Stored Bluetooth name: VS920 4G
E/BluetoothRemoteDevices(13198): devicePropertyChangedCallback: bdDevice: BC:77:37:49:CD:A6, value is empty for type: 10
I/bt_hwcfg(13198): SCO PCM configure {0, 4, 0, 0, 0}
D/ (13198): bta_pan_co_init
I/bte_conf(13198): Attempt to load did conf from /etc/bluetooth/bt_did.conf
I/bte_conf(13198): [1] primary_record=1 vendor_id=0x000F vendor_id_source=0x0001 product_id=0x1200 version=0x1436
I/bte_conf(13198): Attempt to load did conf from /etc/bluetooth/bt_did.conf
I/bte_conf(13198): Attempt to load did conf from /etc/bluetooth/bt_did.conf
Click to expand...


Just figured I would toss it out there.
 
anyone had anything like this before? I'm running a nightly from about 2 weeks ago.... I'm going to try updating it now. But sometimes when I reboot, I get this in my logcat and the boot never finishes. No matter how many times I reboot. Ultimately, I end up having to restore a backup to get it to boot.

Code: 
E/System  (  597): ******************************************
E/System  (  597): ************ Failure starting core service
E/System  (  597): java.lang.NullPointerException
E/System  (  597): 	at android.app.ActivityThread.acquireProvider(ActivityThread.java:4652)
E/System  (  597): 	at android.app.ContextImpl$ApplicationContentResolver.acquireProvider(ContextImpl.java:2135)
E/System  (  597): 	at android.content.ContentResolver.acquireProvider(ContentResolver.java:1085)
E/System  (  597): 	at android.provider.Settings$NameValueCache.lazyGetProvider(Settings.java:782)
E/System  (  597): 	at android.provider.Settings$NameValueCache.getStringForUser(Settings.java:829)
E/System  (  597): 	at android.provider.Settings$Secure.getStringForUser(Settings.java:4940)
E/System  (  597): 	at android.provider.Settings$Secure.getIntForUser(Settings.java:5000)
E/System  (  597): 	at com.android.server.pm.Settings.getPackageLPw(Settings.java:447)
E/System  (  597): 	at com.android.server.pm.Settings.getPackageLPw(Settings.java:198)
E/System  (  597): 	at com.android.server.pm.PackageManagerService.scanPackageLI(PackageManagerService.java:3916)
E/System  (  597): 	at com.android.server.pm.PackageManagerService.scanPackageLI(PackageManagerService.java:3462)
E/System  (  597): 	at com.android.server.pm.PackageManagerService.scanDirLI(PackageManagerService.java:3241)
E/System  (  597): 	at com.android.server.pm.PackageManagerService.<init>(PackageManagerService.java:1279)
E/System  (  597): 	at com.android.server.pm.PackageManagerService.main(PackageManagerService.java:968)
E/System  (  597): 	at com.android.server.ServerThread.run(SystemServer.java:271)
I/SystemServer(  597): Input Method Service
F/SystemServer(  597): BOOT FAILURE starting Input Manager Service
F/SystemServer(  597): java.lang.NullPointerException
F/SystemServer(  597): 	at android.app.PendingIntent.getBroadcastAsUser(PendingIntent.java:459)
F/SystemServer(  597): 	at android.app.PendingIntent.getBroadcast(PendingIntent.java:443)
F/SystemServer(  597): 	at com.android.server.InputMethodManagerService.<init>(InputMethodManagerService.java:637)
F/SystemServer(  597): 	at com.android.server.ServerThread.run(SystemServer.java:386)
F/SystemServer(  597): BOOT FAILURE starting Accessibility Manager
F/SystemServer(  597): java.lang.NullPointerException
F/SystemServer(  597): 	at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1381)
F/SystemServer(  597): 	at android.app.ContextImpl.registerReceiverAsUser(ContextImpl.java:1356)
F/SystemServer(  597): 	at com.android.internal.content.PackageMonitor.register(PackageMonitor.java:95)
F/SystemServer(  597): 	at com.android.server.accessibility.AccessibilityManagerService.registerBroadcastReceivers(AccessibilityManagerService.java:293)
F/SystemServer(  597): 	at com.android.server.accessibility.AccessibilityManagerService.<init>(AccessibilityManagerService.java:210)
F/SystemServer(  597): 	at com.android.server.ServerThread.run(SystemServer.java:394)
F/SystemServer(  597): BOOT FAILURE making display ready
F/SystemServer(  597): java.lang.NullPointerException
F/SystemServer(  597): 	at com.android.server.ServerThread.run(SystemServer.java:402)
F/SystemServer(  597): BOOT FAILURE performing boot dexopt
F/SystemServer(  597): java.lang.NullPointerException
F/SystemServer(  597): 	at com.android.server.ServerThread.run(SystemServer.java:408)
W/SystemServer(  597): ***********************************************
E/AndroidRuntime(  597): Error reporting WTF
E/AndroidRuntime(  597): java.lang.NullPointerException
E/AndroidRuntime(  597): 	at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:329)
E/AndroidRuntime(  597): 	at android.util.Log$1.onTerribleFailure(Log.java:103)
E/AndroidRuntime(  597): 	at android.util.Log.wtf(Log.java:278)
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.reportWtf(SystemServer.java:91)
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.run(SystemServer.java:389)
I/SystemServer(  597): Accessibility Manager
W/SystemServer(  597): ***********************************************
E/AndroidRuntime(  597): Error reporting WTF
E/AndroidRuntime(  597): java.lang.NullPointerException
E/AndroidRuntime(  597): 	at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:329)
E/AndroidRuntime(  597): 	at android.util.Log$1.onTerribleFailure(Log.java:103)
E/AndroidRuntime(  597): 	at android.util.Log.wtf(Log.java:278)
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.reportWtf(SystemServer.java:91)
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.run(SystemServer.java:397)
W/SystemServer(  597): ***********************************************
E/AndroidRuntime(  597): Error reporting WTF
E/AndroidRuntime(  597): java.lang.NullPointerException
E/AndroidRuntime(  597): 	at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:329)
E/AndroidRuntime(  597): 	at android.util.Log$1.onTerribleFailure(Log.java:103)
E/AndroidRuntime(  597): 	at android.util.Log.wtf(Log.java:278)
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.reportWtf(SystemServer.java:91)
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.run(SystemServer.java:404)
W/SystemServer(  597): ***********************************************
W/dalvikvm(  597): threadid=12: thread exiting with uncaught exception (group=0x40b2d930)
I/Process (  597): Sending signal. PID: 597 SIG: 9
E/AndroidRuntime(  597): Error reporting WTF
E/AndroidRuntime(  597): java.lang.NullPointerException
E/AndroidRuntime(  597): 	at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:329)
E/AndroidRuntime(  597): 	at android.util.Log$1.onTerribleFailure(Log.java:103)
E/AndroidRuntime(  597): 	at android.util.Log.wtf(Log.java:278)
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.reportWtf(SystemServer.java:91)
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.run(SystemServer.java:410)
E/AndroidRuntime(  597): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime(  597): java.lang.NullPointerException
E/AndroidRuntime(  597): 	at com.android.server.ServerThread.run(SystemServer.java:414)
E/AndroidRuntime(  597): Error reporting crash
E/AndroidRuntime(  597): java.lang.NullPointerException
E/AndroidRuntime(  597): 	at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime(  597): 	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime(  597): 	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
I/Zygote  (  220): Exit zygote because system server (597) has terminated
I/Netd    (  720): Netd 1.0 starting
 
Last night's nightly (7/13) resets the battery icon after it locks to the default regardless of which you choose in the settings. (at least for me)

*edit*

Interestingly enough, it's not related to SystemUI.apk or ROMControl.apk as I restored both of these from a previous build and it still does it. It also changes back to the default while the screen's on and you're using it. Not a major thing, but annoying none the less.
 
@TDM,

Not sure if I'm messing up somewhere. But I'm trying to build PAC, so that I can start trying to modify it. (If I manage to...)

I'm pretty sure that their build script is messed up... specifically, right here:

# start compilation
mka bacon
echo -e ""

rm -f out/target/product/*/pac_*-ota-eng.*.zip

# finished? get elapsed time
res2=$(date +%s.%N)
echo "${bldgrn}Total time elapsed: ${txtrst}${grn}$(echo "($res2 - $res1) / 60"|bc ) minutes ($(echo "$res2 - $res1"|bc ) seconds) ${txtrst}"
Click to expand...

Either I'm crazy... or they're removing the zip that you just finished building before echoing the time back to you.
 
Yoinx said:
@TDM,

Not sure if I'm messing up somewhere. But I'm trying to build PAC, so that I can start trying to modify it. (If I manage to...)

I'm pretty sure that their build script is messed up... specifically, right here:



Either I'm crazy... or they're removing the zip that you just finished building before echoing the time back to you.
Click to expand...

I don't use that script. But nobody else has reported problems with it.
 
Bummer to hear that the 3.4 kernel isn't going well, but hopefully he's able to bring the 3.0 up to spec for 4.3.
 
You must log in or register to reply here.
Back
Top Bottom