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

Root [rom] pac-man

<ThreadHighjack!!!>
[You started this, IMUcarmen! :D]

Two of my sons live down that way. My oldest in Williamsburg and my youngest in Newport News. Will be heading down there in mid-June to visit.
</ThreadHighjack!!!>

Not had many reboots or lagginess since on RC1. I've had it freeze up on me only once since I went back on the stock (TDM's) kernel (thank's again, Yoinx!). It's been a real workhorse for me.

I haven't been doing the nightlies since RC1, though - mostly because it's summer and I've just had too much going on.

Don't thank me... thank TDM. I just pointed out that he had put in the man hours to fix your issue. He deserves the thanks for the countless hours he's devoted to us... Not me for the minute it took me to draft the reply ;)
 
  • Like
Reactions: tdm
Don't thank me... thank TDM. I just pointed out that he had put in the man hours to fix your issue. He deserves the thanks for the countless hours he's devoted to us... Not me for the minute it took me to draft the reply ;)
I agree. TDM deserves the thanks.

@TDM: THANK YOU!!!
 
  • Like
Reactions: tdm
i'll try and get around to it sometime this week.

I think TDM setup the roms at one point in time to log like the last 10 kmsgs somewhere. I can't remember where it was though either.

IF you wanted to though, you could always do something in an init.d script like...

I haven't tested this yet, but I'm thinking about using something like this myself.

[high]
#!/system/bin/sh
# Make directory if it doesn't exist
mkdir -p /cache/kmsgs
# Log last kmsg with timestamp.
cat /proc/last_kmsg > /cache/kmsgs/$(date +%Y.%m.%d-%T).kmsg.log

[/high]


of course, this will write the last_kmsg everytime you boot regardless of if there was a crash or not... but at least you can keep a record if you know about when the phone crashed since it will record it by time
 
I think TDM setup the roms at one point in time to log like the last 10 kmsgs somewhere. I can't remember where it was though either.

IF you wanted to though, you could always do something in an init.d script like...

I haven't tested this yet, but I'm thinking about using something like this myself.

[high]
#!/system/bin/sh
# Make directory if it doesn't exist
mkdir -p /cache/kmsgs
# Log last kmsg with timestamp.
cat /proc/last_kmsg > /cache/kmsgs/$(date +%Y.%m.%d-%T).kmsg.log

[/high]


of course, this will write the last_kmsg everytime you boot regardless of if there was a crash or not... but at least you can keep a record if you know about when the phone crashed since it will record it by time

Seems my reboots are increasing the past couple of days. I think I got 3 today and a couple yesterday. I've been building a deck outside in the heat so maybe thats why.
 
No reboots here but I am starting to get a lot of lag and delay. Sometimes it takes about 9 or 10 seconds for my sms to open after I tap the icon. Up until about 2 days ago it was instantaneous
 
I haven't updated PAC rom in a while. I am going to do that using latest nightly. I wanted to know if the init.d with v6 supercharger (or something similar to reduce lag) changes have been incorporated yet.

Also are some battery saving tweaks included or I still need to use Pimp My ROM?

Any information on these is greatly appreciated.
 
I haven't updated PAC rom in a while. I am going to do that using latest nightly. I wanted to know if the init.d with v6 supercharger (or something similar to reduce lag) changes have been incorporated yet.

Also are some battery saving tweaks included or I still need to use Pimp My ROM?

Any information on these is greatly appreciated.

Any nightlies or official builds are straight builds. They don't incorporate anything like that.
 
I've been running RC1 since it was posted and for a few weeks it was running fantastic. But within the past two weeks, it's become very laggy and the notification bar disappears at least once a day causing me to reboot to get it back. Actually, just this time it came back on its own - first time ever.

Hate to go through the pain of a clean install. Tried going back to old CWM backups without any real success.

Any help would be appreciated.

EDIT: So I spoke too soon. I noticed this last time when the notification bar came back on its own, that the navigation bar also appeared. I had been "disabling" it by setting the height to zero in the Paranoid Android settings screen under interface.

I found that by setting the navigation bar height to >0, the notification bar appears, but disappears anytime the navigation bar height is "0".

So I guess my question is, how do you properly disable the navigation bar?
 
I've been running RC1 since it was posted and for a few weeks it was running fantastic. But within the past two weeks, it's become very laggy and the notification bar disappears at least once a day causing me to reboot to get it back. Actually, just this time it came back on its own - first time ever.

Hate to go through the pain of a clean install. Tried going back to old CWM backups without any real success.

Any help would be appreciated.

EDIT: So I spoke too soon. I noticed this last time when the notification bar came back on its own, that the navigation bar also appeared. I had been "disabling" it by setting the height to zero in the Paranoid Android settings screen under interface.

I found that by setting the navigation bar height to >0, the notification bar appears, but disappears anytime the navigation bar height is "0".

So I guess my question is, how do you properly disable the navigation bar?

The same thing happens to me constantly. Don't know what to do about it.
 
The same thing happens to me constantly. Don't know what to do about it.

Whatever you're doing to make pacman angry... stop..

Really though. Stab on the dark but it Sounds like an issue when your launcher redraws itself that it's not redrawing the system ui correctly.

Are you using any tweaks or mods? Locking the launcher in memory?

Sent from my VS920 4G using Tapatalk 2
 
Whatever you're doing to make pacman angry... stop..

Really though. Stab on the dark but it Sounds like an issue when your launcher redraws itself that it's not redrawing the system ui correctly.

Are you using any tweaks or mods? Locking the launcher in memory?

Sent from my VS920 4G using Tapatalk 2

Nope. Not besides your init tweaks. But it was happening before that. Using adw ex.

Sent from my VS920 4G using Tapatalk 4 Beta
 
I played around with it some more last night and got it working.

PAC is HAPPY again - Notification Bar is visible, lag is gone and all the awesome has returned to my phone!!!

I tried PimpMyRom to disable it first, with no success.

Went to ParanoidAndroid (Hybrid Properties) => Interface. My "interface" is currently set to Phone (360p) [I know - boring]. I set the interface to Phablet, THEN set the NavBar to 0%, THEN set the interface back to Phone. All is awesome now.

I don't know if PMR had any effect on things. I see where it added the line "qemu.hw.mainkeys=1" in my build.prop. I know it wasn't there before - that was the first thing I checked. I'm not about to mess with success at this point.

@Yoinx: I do have my launcher (Holo Launcher) locked in memory and haven't had any issues with it in the past. Have there been issues that you're aware of? Is this something I shouldn't do. I does seem to help reduce the screen redraws. I expected them not to occur at all, but they do occasionally.
 
I don't know if PMR had any effect on things. I see where it added the line "qemu.hw.mainkeys=1" in my build.prop. I know it wasn't there before - that was the first thing I checked. I'm not about to mess with success at this point.

@Yoinx: I do have my launcher (Holo Launcher) locked in memory and haven't had any issues with it in the past. Have there been issues that you're aware of? Is this something I shouldn't do. I does seem to help reduce the screen redraws. I expected them not to occur at all, but they do occasionally.

That prop looks like the one that disables that soft nav keys. I've never had luck with it though.

Oh I definitely recommend locking launchers in memory. I meant that if you didn't and you were getting a lot of redraws that could have been the issue.


Sent from my VS920 4G using Tapatalk 2
 
That prop looks like the one that disables that soft nav keys. I've never had luck with it though.
From what I've read, that line ENABLES the Nav Bar and deleting it from build.prop removes the Nav Bar. That was the first thing I looked for and found it wasn't there. Now it's there with a comment saying it was added by PMR. For all I know, that could have been the missing link.
 
From what I've read, that line ENABLES the Nav Bar and deleting it from build.prop removes the Nav Bar. That was the first thing I looked for and found it wasn't there. Now it's there with a comment saying it was added by PMR. For all I know, that could have been the missing link.

Meh. It's a toggle 1 on 0 or deleted... off. I don't have it and haven't had issues.

What you did was turn it on then hide it. Can't really see how that would have helped... but hey whatever makes the powerful android gods happy right.

On a side note... these last few posts have made me realize that v6 supercharger hides more tweaks in /data/init.rc

Sent from my VS920 4G using Tapatalk 2
 
Weird question... Since using pac, the button on my headset to pause/skip/go back no longer has any effect. I tested on another phone to see if it was a headphone problem but it worked fine. Playerpro is set up to enable the controls like always but nada.
Any input?
 
Weird question... Since using pac, the button on my headset to pause/skip/go back no longer has any effect. I tested on another phone to see if it was a headphone problem but it worked fine. Playerpro is set up to enable the controls like always but nada.
Any input?

Pac my just not have the right configuration setup for it perhaps?
 
So with Halo going open source, is it possible to have it integrated into PAC?

I think it got merged. Look for it in the latest nightly builds

And speaking of nightly builds, we just got a new build server and I'm working to setup a distributed build farm that uses both old and new servers. This will let all devices get nightly builds and they will be available earlier in the day.
 
Back
Top Bottom