Database Users

[FIX] Auto brightness fix for JVP based ROMs

Here is the autobrightness FIX that should work on any deodexed JVP based ROM (NOT on stock).
Maybe not on some custom kernels - I have not found one yet, but just to warn you
[EDIT]: I've updated the zip with dependant twframework.apk. Now it should work.
HOW TO INSTALL:
- put the zip on your SD card
- Go to recovery (should be CWM compatible)
- install zip from your SD card
- ENYJOY!
With this fix you'll have 5 auto brightness levels.
I've set the following settings that work best for me (and my phone's HW).
5 - at dark (sensor level lower than 20)
35 - inside low light (sensor level lower than 330)
75 - inside at normal light (sensor level lower than 650)
155 - inside at daylight or outside when cloudy or getting darker (sensor level lower than 2610)
255 - outside at daylight (sensor level greater than 2610)
You can monitor the sensor level and changed backlight values with logcat.
I've done the fix based on information from this thread: http://forum.xda-developers.com/showthread.php?t=1130336 (thanks to Lukiqq)
Here are my values in framework-res.apk\res\values\arrays.xml
Code:
<integer-array name="config_autoBrightnessLevels">
<item>20</item>
<item>330</item>
<item>650</item>
<item>2610</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>5</item>
<item>35</item>
<item>75</item>
<item>155</item>
<item>255</item>
</integer-array>

Applied this to Stock JVP on K15H-T12 with Jkay theme, entered reboot loop, had to restore phone !!!!

gsw5700 said:
Applied this to Stock JVP on K15H-T12 with Jkay theme, entered reboot loop, had to restore phone !!!!
Click to expand...
Click to collapse
YOur phone is not actually on stock as you are using speedmod's kernel which is definitely a custom one...

When opener says: haven't found kernel that isn't compatible I think he has tried the most often used one like speedmod, voodoo and so on.
I tried it too with JVP and voodoo(stock samsung kernel just with ext4): doesn't work and messed up my battery symbol by somator and his gb mod. Had to reinstall the mod.
Think this thread here is not so useful as I thought.

OK, Was worth a go;-)

flypubec said:
Here is the autobrightness FIX that should work on any JVP based ROM (also on stock).
Click to expand...
Click to collapse
Services.jar in this package is deodexed, stock rom is odexed so it won't work on pure stock ROM. I've already made working package for stock ROM's with Lukiqq settings:
http://forum.xda-developers.com/showthread.php?p=14915073#post14915073

@Bo$s
Will my mod by Somator will be gone after applying ur fix?
I mean things like Battery icon and power menue?
greetz
EDIT: tried ur fix and have to say it didn't work too.
As I assumed all mods by Somator were gone.
Had only crashes and power menue was completely gone.

usefull
/install thanks

Works on my rom kitchen build of JVP with stock theme..
Only downside is that I actually like the stock battery but this comes with one of the % modded ones..
Marty

Bo$s said:
Services.jar in this package is deodexed, stock rom is odexed so it won't work on pure stock ROM. I've already made working package for stock ROM's with Lukiqq settings:
[...]
Click to expand...
Click to collapse
lukiqq so called fix is a bigmess, he is not aware what is he doing
i strongly advise not to use lukiqq fix
MasterJam882 said:
@Bo$s
Will my mod by Somator will be gone after applying ur fix?
I mean things like Battery icon and power menue?
greetz
EDIT: tried ur fix and have to say it didn't work too.
As I assumed all mods by Somator were gone.
Had only crashes and power menue was completely gone.
Click to expand...
Click to collapse
yes it will be gone as it uses same files - i am a bit bored so maybe i will do my version of this fix based on some other lib =) will think about it
but this fix looks way better then lukiqq one - if you cant wait use it

i can confirm, you have to be careful by using lukiqq's fix - but i don't think its totaly useless, because without his initial thoughts i wouldn't have come to an functional autobrighness result. (it didn't work well in stock-jvp)
i did my own research and i came to the conclusion that investigating the behaviour of sensors.default.só does the trick....(im combination with PROPER values in framework-res)
following both jvp-autobrightness-fix-threads i compared stock sensors.so, the one provided by darkky, the one provieded by lukiqq etc..... i realized that stock jvp-sensors (it doesn't matter which "release") floods my logcat (and/or it recognized only some light-ambients resulting in bright or dark - but nothing in between....)
the sensors.default.so provieded by lukiqqq (i guess, it was part of cm-files) recognize more.. 10-160-225-320-640-1280-2600-10240 i think so i started with that and edited my framework-res with that settings
Code:
<integer-array name="config_autoBrightnessLevels">
<item>640</item>
<item>1280</item>
<item>2600</item>
<item>10240</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>1</item>
<item>70</item>
<item>116</item>
<item>177</item>
<item>253</item>
</integer-array>
and feel quite good with it.....
(btw: i like the first line in lcdbacklightvalues! now don't need screenfilter anymore bacause its darker than setting the backlight to 0% )
@$omator: if you get a sensors.default.so with better/more/ recognized light-values as the one described above - please tell me!!

and OP maybe use cm7 lib, it should have 10 readings
10, 40, 90, 160, 225, 320, 640, 1280, 2600, 10240
Click to expand...
Click to collapse
still i was able to register 8 of them only - 40, 90 missing
//edit oh so you are using this one - so why not use all 8/10 values =)
//edit2 it was useless, lukiqq values are still a chaos not related much to sensor redings - he is like blindman on a narrow road - i am amazed that he compiled a kernel and let people test it - i would not risk blowing up my phone by this pyromaniac =)

okay, lets say there are 10 readings!
@edit:
i used only the last 4 values (so 5 settings alltogether) because i'm too lazy to patch my services.jar (i think its useless eyecandy with that 10 reading lib!)
i realized that readings 10, 40, 90, 160, 225, 320 are completely nonsense in daily use because the physical light-differents between 10 to 225 are sooo minimalistic imho!
does anyone know if the following scenario is possible: (according to a 10 reading restriction in lib [or kernel..i don't know if its also kernel realated stuff])
instead of using these values
10, 40, 90, 160, 225, 320, 640, 1280, 2600, 10240
the lib should be "forced" to use certain values like these
10, 160, 320, 640, 1280, 2600, 5200, 10240, 15000 (like in stock lib), 20480 (if thats still realistic..i dont like to travel to the sun for testing)
or maybe we could add readings so we get a lib with 20 or even more values (mmhh.. i would love to see a FLUENT change of brightness..so gimme 255 readings xD )
@edit2:
^^
i didn't test his kernel either but i read his topic and most of the pyro-testers were fine with it because of its list of features (including bln)
offtopic: i'm still on dark core, does speedmod have bln support yet?

have no idea - i see no sense in using kernels for 2.3.4 based on 2.3.3 sources mix that produces such bugs as front facing camera bug, brighteness and who knows what else - as for values well sure i see no point in using so much of them but it would be very cool to see smooth smooth changes in brighteness =) question is what is this sensors maximum reading possible, stepping is every 1 lux but the 3000 for max is a myth - even stock .so goes up to 100000 so thats probably the upper limit

@flypubec,
Thanks for pointing me in the right direction. Since, I am running non-stock kernel (Talon 0.31) and ROM (Criskelo v75 + Galaxy Blue theme), I knew your CWM zip file won't work, so finally decided to try my hand in decompiling the apk (from the theme).
However, after copying the .apk file to /system/framework (followed all the steps mentioned in the thread you had linked to, for copying the unsigned framework), after reboot, I am getting tons of reboots and force closes ..
@anyone,
Can someone tell me what the issue could be ? Is it because this method, won't work with themed apk's? If so, what is the alternative?
UPDATE :
Checked the logcat. The following is the error coming related to framework:
D/PackageManager( 1387): scanPackage : /system/framework/framework-res.apk
I/PackageManager( 1387): /system/framework/framework-res.apk changed; collecting certs
D/dalvikvm( 1387): GC_CONCURRENT freed 167K, 41% free 3843K/6407K, external 1710K/1988K, paused 2ms+3ms
D/dalvikvm( 1387): GC_FOR_MALLOC freed 389K, 43% free 4038K/6983K, external 1710K/1988K, paused 19ms
D/dalvikvm( 1387): GC_FOR_MALLOC freed 275K, 43% free 4094K/7111K, external 1710K/1988K, paused 18ms
D/dalvikvm( 1387): GC_FOR_MALLOC freed 349K, 42% free 4243K/7303K, external 1710K/1988K, paused 18ms
D/dalvikvm( 1387): GC_FOR_MALLOC freed 88K, 41% free 4339K/7303K, external 1710K/1988K, paused 19ms
D/dalvikvm( 1387): GC_CONCURRENT freed 253K, 35% free 4921K/7559K, external 1710K/1988K, paused 2ms+3ms
D/dalvikvm( 1387): GC_CONCURRENT freed 435K, 34% free 5507K/8327K, external 1710K/1988K, paused 2ms+3ms
W/PackageManager( 1387): Signature mismatch for shared user : SharedUserSetting{40551fa0 android.uid.system/1000}
D/PackageManager( 1387): scanPackage : /system/framework/twframework-res.apk
W/PackageParser( 1387): /system/framework/twframework-res.apk (at Binary XML file line #2): <manifest> specifies bad package name "touchwiz": must have at least one '.' separator

seems liek a typo in framework-res.apk ?

$omator said:
seems liek a typo in framework-res.apk ?
Click to expand...
Click to collapse
Thanks, for replying..
Seems like the, issue is persisting with the same error ,even after reapplying the theme. (getting the same error in logcat..)..
Is it possible that , the first time I applied this, there was some minor typo, after which none of the flashes, is solving the issue?
(I have tried pushing via adb, cwm and none of them is working?)
I guess, I'll have to reflash the ROM and see, if that works, and then probably continue from there..?

@Somator
Hey m8.
I'm very interested in tiny_gb_mod with brightness fix by you.
Do u think it will come soon?
This would be just awesome.
Thx and greetz

i think easiest way is to fix is to use .so sensor extracted from any 2.3.3 gb out there - try this for first - no changes in framework are needed if you use my tinymod

where do I have to search in such a ROM?
Do I have to flash a 2.3.3 first to extract such a file or is this file accessable in a .tar file?
Maybe someone can send me such a file in here and tell me where I have to move it.
Thx to all here for ur help.

[Q] Nexus 4 (white) random reboots

Hi there everyone.
I appologize for this repetitive post, but I have some questions that I can't find an answer.
I have 4.3 up to the latest. I received my nexus yesterday and it updated automatically to the latest version. After that the device started to randomly reboot.
I tried:
- Factory reset (from menu)
- Factory reset from recovery + wipe cache.
Still does not work. Now I heve 2 more questions :
- Can I flash the factory image without root/coustom recovery ? Is there any probability it will solve my problem ? Will I lose OTA ?
- This is a 16 gb model. I also have a black 8 Gb model that does not have this problem. Can I backup my 8gb nexus and install my recovery on the other 16 gb nexus, with the hope It will fix the problem ?
Thank you very much. It's kind of urgent. I can't return it to google because I bought it on a internet store (white edition no more). :crying:

It is a 4.3 thing. Try flashing 4.2.2 factory image and report back.
Sent from my Nexus 4 using xda app-developers app

What I can't get Is why only some devices are affected ... My 8GB nexus 4 runs pretty smooth.
Later on ... It does the same on 4.2.2. So I think this is a more serious problem.

My brand new black nexus 4 is also rebooting, I was wondering couldn't you just reflash android 4.3 and wipe your existing android 4.3 and see if that helps?
Sent from my Nexus 7 using Tapatalk 4

Ulyan said:
What I can't get Is why only some devices are affected ... My 8GB nexus 4 runs pretty smooth.
Later on ... It does the same on 4.2.2. So I think this is a more serious problem.
Click to expand...
Click to collapse
I tried to set it back to android 4.2.2 and it does the same so I'm going to send mine back to O2 and ask for a replacement.
Sent from my Nexus 7 using Tapatalk 4

Since a week or so, my Nexus 4 reboots randomly every hour as well. I'm on stock 4.3 (JWR66Y) which ran perfectly before. I did try to find the cause/trigger of the problem but had no luck so far.
cat /proc/last_kmsg shows that there was a kernel panic at the end of the output, but I can't find any backtrace. Also my /data/dontpanic folder is empty so I don't know where to look any further.
Code:
[ 1026.690462] PM: suspend exit 2013-09-12 13:27:04.015709352 UTC
[ 1026.690553] suspend: exit suspend, ret = 0 (2013-09-12 13:27:04.015831337 UTC)
[ 1026.690645] suspend: enter suspend
[ 1026.690645] PM: Syncing filesystems...
[ 1026.690920] PM: suspend entry 2013-09-12 13:27:04.016197294 UTC
[ 1026.803997] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 1026.839310] sync done.
[ 1026.839371] PM: Syncing filesystems...
[ 1026.874835] sync done.
[ 1027.079230] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 1027.101449] Suspending console(s) (use no_console_suspend to debug)
No errors detected
Boot info:
Last boot reason: kernel_panic
Is there another method to get a backtrace of what triggered the kernel panic?
I found a thread on the google product forums where a lot of people are experiencing a similar issue, but no solutions so far.
Any hints on how I can debug this problem any further would be greatly appreciated!

I have the same problem with this, doesn't matter what version of android I install, custom or not.
THe phone is basically unusable now

[Q] Nexus 10 hangs every night - something in libEGL/OpenGL?

Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?

_anarion_ said:
Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?
Click to expand...
Click to collapse
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?

rlrbjr said:
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?
Click to expand...
Click to collapse
Hi!
I was able to find some old threads about this aptly named Sleep of Death issue, here for example.
Unfortunately no conclusion, most people seem to return their devices :/
Now I think this is indeed some massive memory leak, becasue I was able to see ADB logs with all processes stopping, and the screen blinking with lock screen once when this happened.
As for MovieMaker, this might be misleading - I froze it in TitaniumBackup but the issue still exists.
My plan now is to write a script that would run
Code:
adb shell dumpsys meminfo
every couple seconds/minutes and plot the memory usage until the issue strikes.
I will report here if I find anything.
Best regards,
anarion

I uninstalled Movie Editor (rather than freezing it) and my system is much better (so far). I have not had a single lockup. It still too early to know if this is a god long term solution but I will keep you informed.
Sent from my Nexus 10 using Tapatalk 4

high CPU usage

Hi
I got galaxy note 4 ,wanam ROM,xposed, 910c
When I connect to wifi or mobile internet cpu usage suddendly raises dramatically from about 5% or 6% to 30% or 40% (some times even more) and I'll get UI lag , superfast battery drain and superhot phone.. When I check "3c toolbox " I got this on the top of the list :
/system/bin/dhcpcd 99.88%
/system/bin/surfaceflinger 1.70%
kworker/0:2 1.60%
xposed_service_app 1.35%
/system/bin/mediaserver 1.31%
Swype + Dragon 1.31%
AFWall+ (Donate) 1.01%
zygote 0.96%
kworker/0:1 0.68%
kworker/0:0 0.58%
kworker/0:3 0.54%
/system/bin/servicemanager 0.43%
[/system/bin/dhcpcd 99.88%
/system/bin/surfaceflinger 1.70%
kworker/0:2 1.60%
xposed_service_app 1.35%
/system/bin/mediaserver 1.31%
Swype + Dragon 1.31%
AFWall+ (Donate) 1.01%
zygote 0.96%
kworker/0:1 0.68%
kworker/0:0 0.58%
kworker/0:3 0.54%
/system/bin/servicemanager 0.43%
I have AFWALL firewall but disabling that didn't help...
The only option I got is to kill the process manually (which is a rough option you know )and after that every thing will be normal...
What's the problem?
Thanks in advance
Click to expand...
Click to collapse

ether try a full wipe and reflash rom or change the rom. when you do full wipe i would strongly recommend to do wipe on internal sd card as well cause it often stores left overs from previous roms which can cause issues on next rom so just keep the rom you want to flash on external sd card.

Google App stops responding and forces a Soft reboot! I have a logcat!

For weeks now my Google App randomly stops responding and forces a Soft reboot.
I have no idea how its triggered. I have a logcat where I think I caught all of the error.
I have no idea how to read it and see whats causing the error!
Logcat:
https://mega.nz/#!7ZRwkIrS!FL1oeP6udLer__2g6TZoOvU1O_oHTKBolJwShypgoB0

Have you flashed any Gapps for your device and ROM? It could be that your current version is not rhe right version for your device/rom.. Try google search gapps for Nexus 6P marshmallow, or whatever rom you're on. Hope that helps
Sent from Sony Xperia Z5 E6653

TheTecXpert said:
Have you flashed any Gapps for your device and ROM? It could be that your current version is not rhe right version for your device/rom.. Try google search gapps for Nexus 6P marshmallow, or whatever rom you're on. Hope that helps
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
Again this is an error thats been happening for weeks! Prior to that I had 0 problems with the same setup.
I am using OpenGapps Arm64 6.0 just like the Official Cyanogenmod site says. Those are the officially supported gapps!

If im seeing the logcat correcly, you seem to be having SU issues... has your device given you any SuperSU errors/crashes??
If possible,
Boot in to Recovery.
Reflash your Gapps.zip file via recovery
before rebooting out of recovery make sure to clean/wipe cache data and dalvik cache first
then reboot to system.. you may need to download your Apps Again though which shouldnt be a problem..
another way to fix the issue is ONLY able to be done if your device doesnt keep force rebooting your device..
other wise the quickest way would be just to navigate to Settings>Apps>Google Play Store> Clear App Data and Restore App Defaults... Then navigate to Settings>Apps>Google Play Services> Clear App Data and Restore App Defaults, then clear your memory cache..
Then reboot phone and viola.. You should be all good .

TheTecXpert said:
If im seeing the logcat correcly, you seem to be having SU issues... has your device given you any SuperSU errors/crashes??
If possible,
Boot in to Recovery.
Reflash your Gapps.zip file via recovery
before rebooting out of recovery make sure to clean/wipe cache data and dalvik cache first
then reboot to system.. you may need to download your Apps Again though which shouldnt be a problem..
another way to fix the issue is ONLY able to be done if your device doesnt keep force rebooting your device..
other wise the quickest way would be just to navigate to Settings>Apps>Google Play Store> Clear App Data and Restore App Defaults... Then navigate to Settings>Apps>Google Play Services> Clear App Data and Restore App Defaults, then clear your memory cache..
Then reboot phone and viola.. You should be all good .
Click to expand...
Click to collapse
Thing is as I mentioned above. Again this is one of the dozens of clean installs ive done! Cyanogenmod has Root built in. Its permanent and a part of the system. This is a problem on clean install you see. There is literally no cache or data to be deleted. Even after I wipe those and I go and set the phone up again it happens again... over and over. I have tried multiple versions etc.
Can you please give me more detailed info from the logcat! This has been really helpful.

Well a new version just got released...
download and flash this Gapps Package (Latest Release) 3rd of September 2016 .(Less than a day old). let me know how it goes..
http://opengapps.org/ (Select Arm64>6.0>Stock) (DOnt choose micro, full or any of the others).. its just over 600MB
Put it on your external sdcard... flash it Via recovery.. clear cache/dalvik... reboot ..
i hope that fixes the issue for you, there were others complaining about the same problem in other forums/sites.. and some said the NEW google APP version 9 is causing FCs.. some have fixed the problem by reverting the Google APP back to version 8.0.xxxx (Previous version)..
good luck (for now) its 5am here need some sleep.. will get back to u asap when im back on the pc .. til then good luck
09-03 02:07:54.837 947 961 I ActivityManager: Killing 16280:com.google.android.googlequicksearchbox:search/u0a36 (adj 1): bg anr
09-03 02:07:54.879 947 3618 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ], [email protected])
09-03 02:07:54.880 947 3522 D WifiService: Client connection lost with reason: 4
09-03 02:07:54.880 947 3523 D ConnectivityService: releasing NetworkRequest NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]
09-03 02:07:54.881 947 3523 E ConnectivityService: RemoteException caught trying to send a callback msg for NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]
09-03 02:07:54.884 947 4683 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.service.SearchService in 1000ms
09-03 02:07:54.884 947 4683 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.BroadcastListenerService in 11000ms
09-03 02:07:54.884 947 4683 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.sidekick.main.remoteservice.NowService in 21000ms
09-03 02:07:55.900 947 961 I ActivityManager: Start proc 16912:com.google.android.googlequicksearchbox:search/u0a36 for service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.service.SearchService
09-03 02:07:55.994 16912 16912 W System : ClassLoader referenced unknown path: /system/priv-app/Velvet/lib/arm64[/B]
Your Google Search Box seems to be causing the ANR (App Not Responding) Issues.. and it seems like you're missing most of your system files and some apps and paths cannot be found files cannot be found etc..a lot of things seem to be missing lol..
I think your version of gapps you have installed is corrupted.. try the one i mentioned.. Good luck
I think you should download the gapps from the link above and make sure its the STOCK one.. nothing else..
---------- Post added at 07:09 PM ---------- Previous post was at 06:55 PM ----------
sorry for the double post, but also forgot to mention this..
try and boot the phone into Safe Mode, do the issues/crashes still show up?
have a read of this site what other people with the same device as you have tried, etc etc..
https://productforums.google.com/forum/#!topic/nexus/uhvZVgK2zz0

TheTecXpert said:
Well a new version just got released...
download and flash this Gapps Package (Latest Release) 3rd of September 2016 .(Less than a day old). let me know how it goes..
http://opengapps.org/ (Select Arm64>6.0>Stock) (DOnt choose micro, full or any of the others).. its just over 600MB
Put it on your external sdcard... flash it Via recovery.. clear cache/dalvik... reboot ..
i hope that fixes the issue for you, there were others complaining about the same problem in other forums/sites.. and some said the NEW google APP version 9 is causing FCs.. some have fixed the problem by reverting the Google APP back to version 8.0.xxxx (Previous version)..
good luck (for now) its 5am here need some sleep.. will get back to u asap when im back on the pc .. til then good luck
09-03 02:07:54.837 947 961 I ActivityManager: Killing 16280:com.google.android.googlequicksearchbox:search/u0a36 (adj 1): bg anr
09-03 02:07:54.879 947 3618 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ], [email protected])
09-03 02:07:54.880 947 3522 D WifiService: Client connection lost with reason: 4
09-03 02:07:54.880 947 3523 D ConnectivityService: releasing NetworkRequest NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]
09-03 02:07:54.881 947 3523 E ConnectivityService: RemoteException caught trying to send a callback msg for NetworkRequest [ id=22, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]
09-03 02:07:54.884 947 4683 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.service.SearchService in 1000ms
09-03 02:07:54.884 947 4683 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.BroadcastListenerService in 11000ms
09-03 02:07:54.884 947 4683 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.sidekick.main.remoteservice.NowService in 21000ms
09-03 02:07:55.900 947 961 I ActivityManager: Start proc 16912:com.google.android.googlequicksearchbox:search/u0a36 for service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.service.SearchService
09-03 02:07:55.994 16912 16912 W System : ClassLoader referenced unknown path: /system/priv-app/Velvet/lib/arm64[/B]
Your Google Search Box seems to be causing the ANR (App Not Responding) Issues.. and it seems like you're missing most of your system files and some apps and paths cannot be found files cannot be found etc..a lot of things seem to be missing lol..
I think your version of gapps you have installed is corrupted.. try the one i mentioned.. Good luck
I think you should download the gapps from the link above and make sure its the STOCK one.. nothing else..
---------- Post added at 07:09 PM ---------- Previous post was at 06:55 PM ----------
sorry for the double post, but also forgot to mention this..
try and boot the phone into Safe Mode, do the issues/crashes still show up?
have a read of this site what other people with the same device as you have tried, etc etc..
https://productforums.google.com/forum/#!topic/nexus/uhvZVgK2zz0
Click to expand...
Click to collapse
I dont know if I mentioned this but this is a clean install done a day ago. The gapps package is as new as it can get. Also YES! This started AFTER a Google App update. Before a certain update Nothing like this happened at all!
I have a Nexus 6P which obviously comes with Stock Gapps package. Id flash nothing less than that. I am using a Nexus Phone and as that I love the Google Now Launcher. Sadly because of that I NEED to use the latest Google App to be able to use the phone fully.
As for the missing System files I have no idea how thats happening. Can I just ask you if there is any way to find out if The missing system files messages are caused by GAPPS apps. If so then I think flashing Gapps over Cyanogenmod as system apps when its not stock android and is obviously modified might cause the thing to happen.
I dont know how GAPPS cam ever be corrupt since as I said this has been happening over the past month and ive clean installed it many times with different versions of TWRP, OpenGapps and Cyanogenmod to take the same result. In the Recovery Log file I get no errors so that is strange.
Also god damn /system/priv-app/Velvet/lib/arm64/ is the Google Search app.... I literally think it jus cant use it since its installing things as SYSTEM apps ona System that is not Stock android and thats why this is happening.
Hey I just opened the location in this part of my crash report:
09-03 02:07:55.994 16912 16912 W System : ClassLoader referenced unknown path: /system/priv-app/Velvet/lib/arm64[/B]
I opened the Google search APK file. .... Its not arm64. The folder inside the APK is called arm64-v8a!
Can that cause the problem?

@TheTecXpert Thank you so much! I feel like Im finally getting somewhere wherever that is.
Whatever 09-03 02:07:55.994 16912 16912 W System : ClassLoader referenced unknown path: /system/priv-app/Velvet/lib/arm64[/B] means and from wherever it is its looking in the wrong place! The Google App that came with OpenGapps has arm64-v8a instead of arm64. I checked in the Opengapps archive as well!
Its like that on all my previous backups from months ago as well. It was fine back then so:
Is there ANY way you can tell me what is trying to referenced unknown path: /system/priv-app/Velvet/lib/arm64 ? Is it the Quick Search Box relaunching?

bogomil4e said:
I dont know if I mentioned this but this is a clean install done a day ago. The gapps package is as new as it can get. Also YES! This started AFTER a Google App update. Before a certain update Nothing like this happened at all!
I have a Nexus 6P which obviously comes with Stock Gapps package. Id flash nothing less than that. I am using a Nexus Phone and as that I love the Google Now Launcher. Sadly because of that I NEED to use the latest Google App to be able to use the phone fully.
As for the missing System files I have no idea how thats happening. Can I just ask you if there is any way to find out if The missing system files messages are caused by GAPPS apps. If so then I think flashing Gapps over Cyanogenmod as system apps when its not stock android and is obviously modified might cause the thing to happen.
I dont know how GAPPS cam ever be corrupt since as I said this has been happening over the past month and ive clean installed it many times with different versions of TWRP, OpenGapps and Cyanogenmod to take the same result. In the Recovery Log file I get no errors so that is strange.
Also god damn /system/priv-app/Velvet/lib/arm64/ is the Google Search app.... I literally think it jus cant use it since its installing things as SYSTEM apps ona System that is not Stock android and thats why this is happening.
Hey I just opened the location in this part of my crash report:
09-03 02:07:55.994 16912 16912 W System : ClassLoader referenced unknown path: /system/priv-app/Velvet/lib/arm64[/B]
I opened the Google search APK file. .... Its not arm64. The folder inside the APK is called arm64-v8a!
Can that cause the problem?
Click to expand...
Click to collapse
Nah I don't think that would be causing the problem. Because you ARE on an ARM64 chipset.. And i dont even think gapps comes with v7 v8 specifically (not that I have seen)..
Its usually categorised as arm And arm64.. Yeah while looking through the logcat, there are actual system specific files that a missing and also writing to device permissions are being blocked.. I read somewhere that the problem with the 2 most latest gapps packages were causing all sorts of problems with peoples nexus 6p devices.. Thats why initially I thought that your actual rom build or the gapps package itself could have been corrupt.. If you look carefully in your logcat.. You will see letters and then the log event description..
D/debug
E/error
W/warn
I/information
F/fatal
You will notice a bizarre amount of errors, and quiet a few fatals and most of them are android.google. Related, and system related..
Now if you look further in to your logcat.. You will see are very unpleasant error (any several of them) where the system is trying to write data to the disk/filesystem, but it is giving you SU errors and unable to write data to disk as you dont have permission to do so. Meaning somewhere along the line, su issues CAN infact cause reboots since theres no permission to write to the system/disk..
In recovery do you have the system partition mounted as read only Or mounted with read and write enabled?
If the above mount settings doesn't make any difference even with r/w permissions.
Then try the following.
Boot to recovery, uninstall your current superSU version.. or just simply flash/Reflash SuperSU V2.76, update the binaries etc. Hopefuly that will atleast fix the w/r permissions.
The reason why im suggesting to Reflash superSU IS because in your logcat, you are receiving constant sigpipe errors (aka sigfaulting) which is a sign that something is wrong with your root
Sent from Sony Xperia Z5 E6653

This is getting more and more complicated becauss sadly I can not. I never flashed SuperSU in the first place. Again its deeply integrated into Cyanogenmod itself. It comes with it on the ROM and its even deep in he settings.

bogomil4e said:
This is getting more and more complicated becauss sadly I can not. I never flashed SuperSU in the first place. Again its deeply integrated into Cyanogenmod itself. It comes with it on the ROM and its even deep in he settings.
Click to expand...
Click to collapse
Ok im on my phone at the moment so its hard to really focus on the screen for too long.. Ill get to my pc shortly and we are gonna go through this one step at a time, because clearly something IS wrong. Regardless of it working fine previously.. Something has been done differently/wrong etc. And im betting its something very basic.. Because it cannot be this complicated to boot your phone in system with a freshly installed rom and Still get google app crashing errors and su errors. Give me 5 minutes mate.
Sent from my Sony E6653 using XDA Labs
---------- Post added at 03:16 AM ---------- Previous post was at 03:01 AM ----------
Just a suggestion to try and make things a little easier/faster for you. But are you able to take a screenshot of the ext sdcard that contains your gapps and ROM?? I would just like to compare your files and to the ones im looking at infront of me
Sent from Sony Xperia Z5 E6653
---------- Post added at 03:32 AM ---------- Previous post was at 03:16 AM ----------
bogomil4e said:
@TheTecXpert Thank you so much! I feel like Im finally getting somewhere wherever that is.
Whatever 09-03 02:07:55.994 16912 16912 W System : ClassLoader referenced unknown path: /system/priv-app/Velvet/lib/arm64[/B] means and from wherever it is its looking in the wrong place! The Google App that came with OpenGapps has arm64-v8a instead of arm64. I checked in the Opengapps archive as well!
Its like that on all my previous backups from months ago as well. It was fine back then so:
Is there ANY way you can tell me what is trying to referenced unknown path: /system/priv-app/Velvet/lib/arm64 ? Is it the Quick Search Box relaunching?
Click to expand...
Click to collapse
Well.. Velvet is actually one of the colours for the color theme ..
That really isnt all that important.. im more concerned about the other errors..
im going over the logcat now as we speak
well Looky here..
--------- beginning of crash
09-03 01:40:04.974 8863 8863 F libc : Fatal signal 13 (SIGPIPE), code 0 in tid 8863 (su)
09-03 01:40:04.974 8961 8961 F libc : Fatal signal 13 (SIGPIPE), code 0 in tid 8961 (su)
09-03 01:40:04.976 8916 8916 F libc : Fatal signal 13 (SIGPIPE), code 0 in tid 8916 (su)
09-03 01:40:04.977 8945 8945 F libc : Fatal signal 13 (SIGPIPE), code 0 in tid 8945 (su)
Super User is most likely the cause... The Forced reboots that you are getting is common and 9times out of 10 it's caused by an APP that's either conflicting with your Android OS System, or from a system app that's incompatible with the current installed Rom, and also from any third party app thats installed..
And with Nexus 6P specifically, IF your device RUNS in SAFE MODE without any app crashes and reboots, then you KNOW for a fact that the culprit is one of the apps that you have installed and my bet is that your CYANOGENMOD might be corrupted, or a broken installation.. because custom recovery = Root.. SuperSU is an interface for the Root Binaries to allow your device to run properly and allocate all necessary permissions for apps etc etc..
So that should be the first thing to look in to.. start from the beginning of the crash, and try to narrow down the source of the problem .
dont worry ill help you all the way through, but because i dont have your device infront of me unfortunately, i have to make sure i ask as many questions as i can, even if i ask the same thing 2-3-4 times
ANyway...
So since you're telling me the SuperSU or superuser.apk is embedded in the rom already, is raising alarms in my head because that almost hits the nail on the head when i was saying to you it has something to do with your Root.. either youre not properly rooted and that will be the main cause of being denied permissions to open apps and read/write to the system partion and your storage..
so lets go 1 step at a time.
---------- Post added at 04:16 AM ---------- Previous post was at 03:32 AM ----------
Something else i just noticed... you ARENT using the latest release
09-03 01:40:05.089 527 527 F DEBUG : CM Version: '13.0-20160901-NIGHTLY-angler' <----- Latest release is 20160904
09-03 01:40:05.089 527 527 F DEBUG : Build fingerprint: 'google/angler/angler:6.0.1/MTC20F/3031278:user/release-keys'
09-03 01:40:05.089 527 527 F DEBUG : Revision: '0'
09-03 01:40:05.089 527 527 F DEBUG : ABI: 'arm64'
09-03 01:40:05.089 527 527 F DEBUG : pid: 8961, tid: 8961, name: su >>> /system/xbin/su <<<
09-03 01:40:05.089 527 527 F DEBUG : signal 13 (SIGPIPE), code 0 (SI_USER), fault addr --------

Hey mate.. i have good news for ya.. I just found the factory image for your device which will COMPLETELY set your device back to COMPLETE factory stock.. the zip file has everything necessary to get your device back to working order as if it were straight out of the box..
First Download the file below on your PC.
https://dl.google.com/dl/android/aosp/angler-mtc20f-factory-4355fe06.zip
then..
Open your Adb & fastboot terminal program
Extract the downloaded zip file into it's own directory (by default it will create its own directory and folder structure)..
Next open the extracted folder and (twice) and you will see a bunch of files.. move ALL of the files to the Root directory of ADB and Fastboot Terminal program so that all the files are in the same folder as your terminal program.
Next just drag the "flash-all.bat" file into the terminal window with your mouse and hit enter..
the script should then execute and once it has completed your device will reboot.
I've attached screenshots just for a reference for ya..

TheTecXpert said:
Hey mate.. i have good news for ya.. I just found the factory image for your device which will COMPLETELY set your device back to COMPLETE factory stock.. the zip file has everything necessary to get your device back to working order as if it were straight out of the box..
First Download the file below on your PC.
https://dl.google.com/dl/android/aosp/angler-mtc20f-factory-4355fe06.zip
then..
Open your Adb & fastboot terminal program
Extract the downloaded zip file into it's own directory (by default it will create its own directory and folder structure)..
Next open the extracted folder and (twice) and you will see a bunch of files.. move ALL of the files to the Root directory of ADB and Fastboot Terminal program so that all the files are in the same folder as your terminal program.
Next just drag the "flash-all.bat" file into the terminal window with your mouse and hit enter..
the script should then execute and once it has completed your device will reboot.
I've attached screenshots just for a reference for ya..
Click to expand...
Click to collapse
I forgot to mention a few things. Im not really new to android. I know about the factory images from google. Tried the latest 6.0.1 image from Google a FEW times already as well as the OTA updates from google. I know it will flash everything and erase the partitions. I have even tried erasing the partitions myself and resizing them. It is not the problem. I have even flashed them all individually via fastboot and erased partitions as well that way. Im not new to android. Ive been here for a while now but THIS problem is beyond me.
For a reference of how much my Android knowledge is at this point refer to my guide where me and the TWRP devs found a bug in the latest TWRP version that was bricking the EFS partition of Nexus 6P devices by looking through the kernel logs and helpes people fix it by deleting the corrupt EFS partition via Shell : http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
I simply dont want to use stock android. I want my custom rom. I know my way around android a bit but understanding the logcat for some reason is beyond me. I just have no idea about this issue.
As you can see because im not new I have tried everything I know! And YES Stock Android for my device DOES NOT have this issue but its stock android after all. Im trying to fix it on Cyanogenmod.
The thing I forgot to mention was that its not really a clean install. Well it is BUT once I get to the First Time Google Setup I do choose to restore all the apps and homescreen layout from one of my previous Nexus 6Ps. All that does it it restores your homescreen layout and reinstalls all the apps freshly from Google play which is 216 apps so far. All the apps are freshly installed so I dont think it can cause harm.

after you restore your apps.. does your device start to boot loop?

TheTecXpert said:
after you restore your apps.. does your device start to boot loop?
Click to expand...
Click to collapse
No. It does not. After a few min of it working fully fine with all my apps then the problem happens. The Google app stops responding and it causes a reboot. I havent gotten any reboots! Its not on a timer as well. Right now Its been a whole 10 hours with no reboot or crash! It will happen again however. It always does.
Ususally with things like these there is an app that is causing it or 2 apps that dont play well witch each other who cause the problem. Thats why I also posted the logcat. To see if 2 apps didnt play well with each other but since that is not the case its super confusing.

bogomil4e said:
I forgot to mention a few things. Im not really new to android. I know about the factory images from google. Tried the latest 6.0.1 image from Google a FEW times already as well as the OTA updates from google. I know it will flash everything and erase the partitions. I have even tried erasing the partitions myself and resizing them. It is not the problem. I have even flashed them all individually via fastboot and erased partitions as well that way. Im not new to android. Ive been here for a while now but THIS problem is beyond me.
For a reference of how much my Android knowledge is at this point refer to my guide where me and the TWRP devs found a bug in the latest TWRP version that was bricking the EFS partition of Nexus 6P devices by looking through the kernel logs and helpes people fix it by deleting the corrupt EFS partition via Shell : http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
I simply dont want to use stock android. I want my custom rom. I know my way around android a bit but understanding the logcat for some reason is beyond me. I just have no idea about this issue.
As you can see because im not new I have tried everything I know! And YES Stock Android for my device DOES NOT have this issue but its stock android after all. Im trying to fix it on Cyanogenmod.
The thing I forgot to mention was that its not really a clean install. Well it is BUT once I get to the First Time Google Setup I do choose to restore all the apps and homescreen layout from one of my previous Nexus 6Ps. All that does it it restores your homescreen layout and reinstalls all the apps freshly from Google play which is 216 apps so far. All the apps are freshly installed so I dont think it can cause harm.
Click to expand...
Click to collapse
At this point it is highly likely that something amiss happened to your backup of the google app, as the issue only kicks in after you restore it. If you have automatic backup enabled in the past then there's a possibility that onecof the backup points for the app got compromised.
I don't use the backup/restore feature that much, but if i recall correctly during initial set-up you have the option to manually choose which apps to restore correct? If that's the case restore everything except for the google app. If you come from a totally clean install (which includes setting up the phine as new/not restoring app from cloud) I'm fairly certain the reboot issue with the google app won't happen.

blitzkriegger said:
At this point it is highly likely that something amiss happened to your backup of the google app, as the issue only kicks in after you restore it. If you have automatic backup enabled in the past then there's a possibility that onecof the backup points for the app got compromised.
I don't use the backup/restore feature that much, but if i recall correctly during initial set-up you have the option to manually choose which apps to restore correct? If that's the case restore everything except for the google app. If you come from a totally clean install (which includes setting up the phine as new/not restoring app from cloud) I'm fairly certain the reboot issue with the google app won't happen.
Click to expand...
Click to collapse
The backup isnt really a backup. Google simply saves the name of the app and ten cleanly reinstalls them from Google Play. Its not restoring one of my previous apps. Its just installing them straight from Google Play cleanly.
Once Cyanogenmod 14 based on Android 7.0 comes out I plan to do a FULL clean wipe with no restores and set it up as a brand new phone. That seems to be the best option. Till then im just going to live with it. If THEN it causes the same problems with no restored settings or things we will know what the problem is.
Thank you a lot for the help! @TheTecXpert Is it a problem for me to write here again and reference you if I need more help? After a month of searching and people trying to help and failing you were the only person who was able to read the logcat and provide some insight on what TF has been happening inside! Its gonna be a few weeks/months since Cyanogen takes time.

bogomil4e said:
The backup isnt really a backup. Google simply saves the name of the app and ten cleanly reinstalls them from Google Play. Its not restoring one of my previous apps. Its just installing them straight from Google Play cleanly.
Once Cyanogenmod 14 based on Android 7.0 comes out I plan to do a FULL clean wipe with no restores and set it up as a brand new phone. That seems to be the best option. Till then im just going to live with it. If THEN it causes the same problems with no restored settings or things we will know what the problem is.
Thank you a lot for the help! @TheTecXpert Is it a problem for me to write here again and reference you if I need more help? After a month of searching and people trying to help and failing you were the only person who was able to read the logcat and provide some insight on what TF has been happening inside! Its gonna be a few weeks/months since Cyanogen takes time.
Click to expand...
Click to collapse
I did try to read your log as well yesterday out of curiosity but I did not fully understand everything in it What I was able to pinpoint was what happened right before your phone did the soft reboot :
09-03 02:05:20.676 947 961 I ActivityManager: Killing 4473:com.google.android.googlequicksearchbox:search/u0a36 (adj 0): bg anr
09-03 02:05:20.717 947 958 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ id=5, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ], [email protected])
09-03 02:05:20.718 947 3522 D WifiService: Client connection lost with reason: 4
09-03 02:05:20.718 947 3523 D ConnectivityService: releasing NetworkRequest NetworkRequest [ id=5, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]
09-03 02:05:20.719 947 3523 E ConnectivityService: RemoteException caught trying to send a callback msg for NetworkRequest [ id=5, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]
09-03 02:05:20.725 947 4958 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.service.SearchService in 1000ms
09-03 02:05:20.726 947 4958 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.BroadcastListenerService in 11000ms
09-03 02:05:20.726 947 4958 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.sidekick.main.remoteservice.NowService in 21000ms
09-03 02:05:20.733 16099 16099 E ReflectionService: Message dropped: the service handler is null.
09-03 02:05:20.737 14183 14183 I Finsky : [1] com.google.android.vending.verifier.PackageVerificationReceiver.onReceive(2102): Skipping verification because own installation
09-03 02:05:20.946 947 971 I PackageManager.DexOptimizer: Running dexopt (dex2oat) on: /data/app/vmdl962661913.tmp/base.apk pkg=scd.lcex isa=arm64 vmSafeMode=false debuggable=false oatDir = /data/app/vmdl962661913.tmp/oat bootComplete=true
I don't have enough technical knowledge though to know what caused the crash to happen. Just a thought did you make any changes to privacy guard settings related to google play services in the past?

Of course you can mate.. Feel free to call upon me whenever you need to.
Oh by the way, did i mention that this line
09-03 02:05:20.676 947 961 I ActivityManager: Killing 4473:com.google.android.googlequicksearchbox:searc h/u0a36 (adj 0): bg anr <--- bg anr = Background App Not Responding (so your searchbox is crashing).. uninstall it and clear all of the leftover app cache and data.. then reboot the device.. then reinstall your Google Search App from google play store.. don't restore it from a backup..
then take another logcat and see where the NEXT crash starts.. is that making sense ??? its an effective way of narrowing down the root cause of the problem..
try that first, then get back to me with the result..

LOL i kept reading through the logcat and come across what i believe to be the issue. and it still goes back to what i was telling you all this time..
You're definitely doing something wrong.. and im not saying it to offend you.. im just trying to get this sorted out for you otherwise i wont be satisfied
If you're still up for it.. then lets proceed..
But first, I'm going to tell you the same thing i told you earlier and i was spot on... After reading through your logcat even further i came across so many errors and fatals errors especially packagemanager errors.. I stopped reading half way because there were literally soooo many..
Scenario 1.
You either have a corrupted backup, or a corrupted/buggy system (rom)..
Because not only are you restoring your apps, but you also might be restoring settings that you may have backed up along with your apps..
So therefore what you have done is you have done a clean installation of your rom.. then you flashed your gapps... then you proceeded with the initial phone setup... once you were all setup you went ahead and restored all of your backed up apps.. did you backup your systems settings along with your apps?? and if you did, did you restore your system settings as well??
--------------------------------------------------------------------------------
these errors,warning and fatals that im seeing in your logcat is a clear indication that there is definitely something very wrong within your kernel, settings, rom and/or apps..
In all honesty mate start completely from scratch...
-----------------------------------------------------------------------
here are some errors i cherry picked out of your logcat which i saw as Relevant..
09-03 02:29:41.539 18945 19172 W MountService: No primary storage mounted!
09-03 02:29:41.550 18945 19172 W PackageManager: Unknown permission com.google.android.voicesearch.SHORTCUTS_ACCESS in package com.google.android.googlequicksearchbox
09-03 02:29:41.550 18945 19172 W PackageManager: Unknown permission com.google.android.voicesearch.ACCESS_SETTINGS in package com.google.android.googlequicksearchbox
09-03 02:29:41.550 18945 19172 W PackageManager: Unknown permission com.android.browser.permission.PRELOAD in package com.google.android.googlequicksearchbox
09-03 02:29:41.550 18945 19172 W PackageManager: Unknown permission com.google.android.ears.permission.WRITE in package com.google.android.googlequicksearchbox
09-03 02:29:41.550 18945 19172 W PackageManager: Unknown permission com.google.android.apps.googlevoice.permission.AUTO_SEND in package com.google.android.googlequicksearchbox
09-03 02:29:41.550 18945 19172 W PackageManager: Unknown permission com.android.chrome.PRERENDER_URL in package com.google.android.googlequicksearchbox
09-03 02:29:41.551 18945 19172 W PackageManager: Not granting permission android.permission.INTERACT_ACROSS_USERS_FULL to package org.cyanogenmod.snap (protectionLevel=258 flags=0x3858bc45)
09-03 02:29:41.551 18945 19172 W PackageManager: Not granting permission android.permission.SET_ORIENTATION to package org.cyanogenmod.snap (protectionLevel=2 flags=0x3858bc45)
09-03 02:29:41.569 18945 19172 W PackageManager: Unknown permission com.android.launcher.permission.READ_SETTINGS in package com.google.android.launcher
09-03 02:29:41.569 18945 19172 W PackageManager: Unknown permission com.android.launcher.permission.WRITE_SETTINGS in package com.google.android.launcher
09-03 02:29:41.572 18945 19172 W PackageManager: Unknown permission android.permission.READ_OWNER_DATA in package com.google.android.setupwizard
09-03 02:29:41.572 18945 19172 W PackageManager: Unknown permission android.permission.WRITE_OWNER_DATA in package com.google.android.setupwizard
09-03 02:29:41.572 18945 19172 W PackageManager: Not granting permission android.permission.STATUS_BAR to package com.intangibleobject.securesettings.
09-03 02:29:41.582 18945 19172 W PackageManager: Unknown permission android.permission.READ_OEM_UNLOCK_STATE in package com.google.android.gms
09-03 02:29:41.582 18945 19172 W PackageManager: Unknown permission com.google.android.wh.supervisor.permission.ACCESS_METADATA_SERVICE in package com.google.android.gms
09-03 02:29:41.799 18945 19172 W MountService: No primary storage defined yet; hacking together a stub
09-03 02:29:41.800 18945 19172 W MountService: No primary storage defined yet; hacking together a stub
09-03 02:29:42.268 18945 18976 E KernelCpuSpeedReader: Failed to read cpu-freq: /sys/devices/system/cpu/cpu4/cpufreq/stats/time_in_state: open failed: ENOENT (No such file or directory)
09-03 02:29:43.328 551 551 E fingerprintd: Wrong fp version. Expected 512, got 256
09-03 02:30:04.916 531 531 E installd: Unable to unlink boot marker at /data/dalvik-cache/arm/.booting, error=No such file or directory
09-03 02:30:04.916 18945 18995 E ActivityManager: Unable to mark boot complete for abi: armeabi-v7a
You get the idea.. Have you considered using TWRP as your recovery and flashing a custom rom through twrp ??
Anyway it all comes down to you at the end of the day.. If you're willing to try out a differetnt solution in the mean time, just let me know..
Just, whatever you do decide to do... I highly advise you NOT to restore your backup yet, if at all.. you need to make sure your ROOT app is working properly and that your SU Binaries are all up to date first.. and also make sure busybox is installed as well..
well.. i think im worn out for tonight.. lol.. im gonna take a break from thinking for a while ..
take care, and let me know what you end up doing
EDIT: before i forget
***NOTE*** Make sure you enable the developer options, enable oem unlock, allow unknown app sources (if option is available).. (you probably have already, but i thought id remind you incase you had forgotten)
---------- Post added at 03:37 PM ---------- Previous post was at 03:24 PM ----------
here's something you might like to have a read of... even just for your own leisure
http://www.androidcentral.com/how-get-android-70-nougat-your-nexus-right-now