[ROM][OFFICIAL][KitKat 4.4.4][TENDERLOIN] PAC-man KK RELEASE [WEEKLY]]

[shumash]

Thanks for all you do to extend the life and use of the TP.....like a couple of others just did a an factory reset clear cahes install of 11/3 and total boot time was 4:45, about 1 minute of dark screen and then 3:45 minutes of pacman boot animation. Thanks for taking the time to work on a new build.

The problem is that I experienced everything that you and others are having with the 11/02 build. I fixed the permissions on /data in the 11/03 build, and I don't have the problem. Those of you that are experiencing this, please use a root browser and check the permissions of /data. It should show as 0777 or rwxrwxrwx. If it doesn't, you've got a problem with your file system. Check the /data/local folder. You should have a PACLogs folder, a tmp folder, and an init.d.cfg file.

 

[shumash]

[ROM Update] 08 NOV 2014

An updated ROM is available at the OP and OTA download links.

• Merge upstream
  -- Nothin' much

Enjoy

I've posted this in the hope that it may clear up some user issues, but if you're not having problems with 11/03, there's nothing here that would shake your world by installing it. Boot time for me with this build is 50 sec after the first.

 

[mattman5000]

Thanks for your help shumash.

I checked the permissions. All looks okay. I also see the three files in /data/local. I didn't see them earlier because i was using ES File Manager and didn't have root enabled (my mistake).

I deleted init.d.cfg and rebooted. Boot time is now normal ~50 seconds.

Edit: I meant to add that I'm still running 1103 build. Have not installed the new update yet.


127|root@tenderloin:/ # ls -l -d /data
drwxrwxrwx system system 2014-11-08 13:52 data
root@tenderloin:/ # ls -l -d /data/local
drwxr-x--x root root 2014-11-08 18:30 local
root@tenderloin:/ # ls -l /data/local
drwxr-xr-x root root 2014-11-08 13:52 PACLogs
-rw-r--r-- root root 1586 2014-11-08 18:30 init.d.cfg
drwxrwx--x shell shell 2014-10-12 13:49 tmp
root@tenderloin:/ #

Sent from my TouchPad using Tapatalk

 

[nevertells2]

The problem is that I experienced everything that you and others are having with the 11/02 build. I fixed the permissions on /data in the 11/03 build, and I don't have the problem. Those of you that are experiencing this, please use a root browser and check the permissions of /data. It should show as 0777 or rwxrwxrwx. If it doesn't, you've got a problem with your file system. Check the /data/local folder. You should have a PACLogs folder, a tmp folder, and an init.d.cfg file.

Seems like to me these guys that are having long boot times should use the CWM Wipe data/Factory reset/Clean to Install a New ROM function.

NT

 

[shumash]

Seems like to me these guys that are having long boot times should use the CWM Wipe data/Factory reset/Clean to Install a New ROM function.

NT

Seems to me like you are right, but all change is perceived as loss.

 

[Moronig]

DELETED, should've been posted 5 hours ago, had some internet problems. Will install the new build fresh. Thanks for all the support! I hope I didn't come out as being ungrateful for all the great work you have done!

 

[35russ]

Installed 11/8 after complete wipe and boot time now 50 seconds. Thanks shumash.

Sent from my TouchPad using XDA Free mobile app

 

[nevertells2]

Hey Shumash, is the 11/08 build based on the 3.0 or 3.4 kernel? In my experience the 3.0 based builds seem less problematic. Thanks

NT

 

[shumash]

Hey Shumash, is the 11/08 build based on the 3.0 or 3.4 kernel? In my experience the 3.0 based builds seem less problematic. Thanks

NT

http://xdaforums.com/showthread.php?p=55327211&highlight=3+0+kernel#post55327211

 

[nevertells2]

http://xdaforums.com/showthread.php?p=55327211&highlight=3+0+kernel#post55327211

Thanks, must have missed that post.

NT

 

[shumash]

[ROM Update] 11 NOV 2014

An updated ROM is available at the OP and OTA download links.

• Merge upstream
• Kernel:
  - Enable 1914 MHz maximum cpu frequency

Enjoy

WARNING!: Boosting frequencies this high is very device dependent. Yours may not be capable of the maximum frequency, may freeze or be unstable. I have tested this ROM up to the maximum, and it's stable on my device. If you don't want to play around, keep the frequency at the default 1512MHz. If you do, increase it in steps; don't start with the maximum.

 

[nightfireblaze8]

An updated ROM is available at the OP and OTA download links.

• Merge upstream
• Kernel:
  - Enable 1914 MHz maximum cpu frequency

Enjoy

WARNING!: Boosting frequencies this high is very device dependent. Yours may not be capable of the maximum frequency, may freeze or be unstable. I have tested this ROM up to the maximum, and it's stable on my device. If you don't want to play around, keep the frequency at the default 1512MHz. If you do, increase it in steps; don't start with the maximum.

Thank you for the update. I haven't had a single SOD yet with this build.

 

[shumash]

3.4 oc'd kernel available.

 

[suzib6sw]

3.4 oc'd kernel available.

Thanks @shumash
Installed the 3.4 on my 16G TP.. Updated the PS-Gapps Modular mini..
This was flashed over the 11/3 build.. Cleared Cache and Dalvic before flashing.
Unfortunalty it reboots frequently when Idle or off the lock screen..
Went back to the 11/3.. No reboots and very stable.

Thanks for all your work..
Pete

 

[gtallmadge]

Same here with 3.4 on my 32G TP. Shuts down when idle and difficult to to restart. Will revert back to the 11-3 as well.

 

[nevertells2]

Thanks @shumash
Installed the 3.4 on my 16G TP.. Updated the PS-Gapps Modular mini..
This was flashed over the 11/3 build.. Cleared Cache and Dalvic before flashing.
Unfortunalty it reboots frequently when Idle or off the lock screen..
Went back to the 11/3.. No reboots and very stable.

Thanks for all your work..
Pete

Same here with 3.4 on my 32G TP. Shuts down when idle and difficult to to restart. Will revert back to the 11-3 as well.

Did you try a clean install to see how stable it is?

NT

 

[suzib6sw]

Did you try a clean install to see how stable it is?

NT

Not yet, Will try again unless Shumash wants anything from a catlog?

 

[shumash]

Not yet, Will try again unless Shumash wants anything from a catlog?

As you might have guessed, 3.4 is kind of leftovers for me. I don't intend to spend much time on it, but a logcat will certainly help. I suspect it's more sensitive to the overclocking, 'cause that's the only change I made, unless something upstream broke it, Incidentally, if you're using the ondemand governor, don't. It's broken. I intend to disable it in both ROMs in the next update.

 

[gtallmadge]

Didn't work very well for me. Got some SOD on the 3.4 so went back and did a clean install of the 3.0 11-11 and it is working fine..no problems.
Great work!

 

[suzib6sw]

As you might have guessed, 3.4 is kind of leftovers for me. I don't intend to spend much time on it, but a logcat will certainly help. I suspect it's more sensitive to the overclocking, 'cause that's the only change I made, unless something upstream broke it, Incidentally, if you're using the ondemand governor, don't. It's broken. I intend to disable it in both ROMs in the next update.

Hi @shumash
Ok.. the reboot seems to be more likely to occur when its inactive.. .. Ie, when it goes to sleep.. Up till this point, I had a 3x3 lockscreen and it was working prior to the O/C kernel..
I removed the lock screen and the same reboot happens but only when it goes idle.
.. I hope I managed to grab the logcat.. I set catlog to record ..
I managed a couple.. at
http://1drv.ms/1qdOWzY

Hope that helps..