Related
Hey guys!
Hoping someone might be able to help. My camera stopped working about a year ago and I haven't been able to get it to work. Every time I try to use it my phone reboots. I've tried running every ROM available here, every radio, every SPL. At this point I figure it's probably hardware but I want to rule out every other possibility before I give up on it. Any suggestions ?
TY in advance.
PS. 32a Rogers - current radio is 6.35.16.19 - playing with gingerbread atm
I have the same issue with a Vodafone htc magic 32b. It started after the OTA of Vodafone to go to Android 2.2.1. I hoped it would work in Cyanogenmod 6.1 but it still gives reboots.
This is the log cat when I start the camera:
Code:
I/ActivityManager( 155): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera }
I/ActivityManager( 155): Start proc com.android.camera for activity com.android.camera/.Camera: pid=771 uid=10011 gids={1006, 1015}
I/WindowManager( 155): Setting rotation to 1, animFlags=1
I/ActivityManager( 155): Config changed: { scale=1.0 imsi=206/1 loc=nl_BE touch=3 keys=1/1/2 nav=3/1 orien=2 layout=18 uiMode=17 seq=8}
I/GPSButton( 155): Update State
I/ActivityManager( 155): Start proc com.ramesp.amissed for service com.ramesp.amissed/.LockWatchDog: pid=779 uid=10093 gids={1015}
E/mm-camera( 123): mt9t013_process_start: ioctl(MSM_CAM_IOCTL_ENABLE_OUTPUT_IND) error Invalid argument
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
D/RAMES ( 779): Registering--------------
D/Camera ( 771): app passed NULL surface
D/CameraSettings( 771): [antibanding-values=off,50hz,60hz,auto, antibanding=auto, effect-values=none,mono,negative,solarize,sepia,posterize,whiteboard,blackboa
rd,aqua, effect=none, exposure-compensation-step=0.5, exposure-compensation=0, focal-length=3.72, focus-mode-values=auto,infinity, focus-mode=auto, horizontal-v
iew-angle=51.6, jpeg-quality=90, jpeg-thumbnail-height=384, jpeg-thumbnail-quality=90, jpeg-thumbnail-size-values=512x384,0x0, jpeg-thumbnail-width=512, max-exp
osure-compensation=4, max-zoom=12, min-exposure-compensation=-4, picture-format-values=jpeg, picture-format=jpeg, picture-size-values=2048x1536,1600x1200,1024x7
68,512x384, picture-size=2048x1536, preview-format-values=yuv420sp, preview-format=yuv420sp, preview-frame-rate-values=15, preview-frame-rate=15, preview-size-v
alues=800x480,720x480,640x480,576x432,480x320,384x288,352x288,320x240,240x160,176x144, preview-size=384x288, vertical-view-angle=39.7, whitebalance-values=auto,
incandescent,fluorescent,daylight,cloudy-daylight, whitebalance=auto, zoom-ratios=100,102,107,109,114,117,123,128,131,138,141,148,155, zoom-supported=true, zoom=0]
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
E/mm-camera( 123): vfe_util_sendcmd: MSM_CAM_IOCTL_CONFIG_VFE error: No such device
V/camera ( 771): startPreview
It also reboots if I start any application that uses the camera e.g. goggles, barcode scanner,...
Would really like to have this fixed. Any suggestions?
my fix
try to reflash your rom if all else fail do a restore or flash of your stater rom and send it back to your carrier don't forget to unroot after that flash change your boot image back if not changed double check your fastboot
I've had this same issue. It looks from your logcat that the camera hardware works, it's just not loading properly.
The problem is that the camera's preferences file needs to be rewritten by the system. the solution is to adb shell into your phone, then go into /data/data/com.android.camera (or your Rom's specific directory; different Roms will likely have different directory names, but it shouldn't vary too much) and look for camera_hardware_preferences.xml (or your Rom's specific hardware preferences XML file for the camera) and move this to camera_hardware_preferences.xml_, then reboot.
Doing this will make your phone have to rewrite it's profile for camera hardware. Once done, it should work.
Findulmundo. I tried this and now my camera no longer crashes but is stuck on a black screen when starting the camera app. The camera_preferences.xml file is not being generated either. Any ideas?
Guys im having a similar issue, my camera will start normally but when i try to take a picture it will get stuck and wont shoot the pic. I can exit the app normally, no force close but im unable to take any pics any ideas?
Currently on cm5, already tried different sd cards, fastboot wipe and then reflashed the ROM, tried different roms also its still a no go though
Sent from my HTC Glacier using XDA Premium App
I'm not sure, but you should try to flash a new kernel - you'll find it in the dev section...
Btw. I'm using Ginger Yoshi RC 6.1 - to use it I needed to flash a new radio hboot and kernel - you can find the instructions in the ROM's thread step-by-step!
Hello,
I have a problem with the rom CM 10.2 Engle_mars. I use actually CM10.1 and i send correctly sms but with CM10.2, directly i send a sms response is error 254
I check smsc with *#*#4636#*#* and for my smsc operator (mobistar = +32495002530 ) is correct.
someone has an idea?
Hi,
Same problem here.
And there s a third person, who has the same bug too, with CM 10.2 ROM.
Engle_Mars had the information (see the thread in Development Forum), and have to watch the log. We are waiting for a next answer.
Sent from my ME722 using xda app-developers app
thank's for this information . I'm feeling less alone
Same problem in Engle_Mars-CM10.2-20130816-UNOFFICIAL-milestone2 . :crying:
I don't found anything about this problem.
I test "DEFY Baseband Switcher 4.0" with baseband 2.3.4 (Great Britain). the phone work correctly but sms don't ...
:fingers-crossed: crossed fingers:fingers-crossed:
petri3 said:
thank's for this information . I'm feeling less alone
Same problem in Engle_Mars-CM10.2-20130816-UNOFFICIAL-milestone2 . :crying:
I don't found anything about this problem.
I test "DEFY Baseband Switcher 4.0" with baseband 2.3.4 (Great Britain). the phone work correctly but sms don't ...
:fingers-crossed: crossed fingers:fingers-crossed:
Click to expand...
Click to collapse
I don't know really what the cause was, but I solved the problem by reinstalling the ROM with full wipe data...
then just test to send a sms with the native application without configuring anything.
hope it will help...
mattheoh said:
I don't know really what the cause was, but I solved the problem by reinstalling the ROM with full wipe data...
then just test to send a sms with the native application without configuring anything.
hope it will help...
Click to expand...
Click to collapse
Hi!
I did full data wipe during initial 10.2 install, as well as cache/dalvik cleanup, and the problem was there from the beginning. I also force-closed the SMS/MMS app and cleared all its data and cache, and it also didn't help.
The following appears in the logcat during SMS send attempt:
Code:
V/SmsReceiverService( 7423): onStart: #1 mResultCode: -1 = Activity.RESULT_OK
D/dalvikvm( 1877): GC_EXPLICIT freed 414K, 30% free 5389K/7684K, paused 3ms+10ms, total 77ms
I/ ( 1335): opprofdaemon: OPPROF_DAEMON_translate_message(): Enter
I/ ( 1335): opprofdaemon: handle_bp_message(): Enter
I/ ( 1335): opprofdaemon: handle_log_all_ind(): Enter
I/ ( 1335): opprofdaemon: OPPROF_TRANSPORT_P.cc: handle_log_all_ind(): line=522: BP log all event=c
I/ ( 1335):
I/ ( 1335): opprofdaemon: OPPROF_TRANSPORT_P.cc: handle_log_all_ind(): line=557: Error: Incorrect BP log all data size: 48
I/ ( 1335):
I/ ( 1335): opprofdaemon: OPPROF_TRANSPORT_P.cc: handle_log_all_ind(): line=568: OPPROF TL: log_all
I/ ( 1335): opprofdaemon: handle_log_all_ind(): Exit
I/ ( 1335): opprofdaemon: handle_bp_message(): Exit
I/ ( 1335): opprofdaemon: OPPROF_DAEMON_translate_message(): Exit
V/SmsReceiverService( 7423): onStart: #1 mResultCode: 1 = SmsManager.RESULT_ERROR_GENERIC_FAILURE
Regards, Pavel
I wipe all : /data /system /cache and the rest ... Now, i send sms correctly ... :good:
thanks for the solution :victory:
petri3 said:
I wipe all : /data /system /cache and the rest ... Now, i send sms correctly ... :good:
thanks for the solution :victory:
Click to expand...
Click to collapse
thanks a lot for this funny post you made my day!
wipe all -> espacially "system" is my favourite
but don't cry when no rom is installed afterwards
by the way... system is formatted by script in engle_mars's rom zip. so a data wipe is enough. cache and dalvik cache are on the data partition and are wiped automatically when you wipe data....
mattheoh said:
I don't know really what the cause was, but I solved the problem by reinstalling the ROM with full wipe data...
then just test to send a sms with the native application without configuring anything.
hope it will help...
Click to expand...
Click to collapse
This usually helps. back up the data with titanium and restore after reflashing.
linxiafeibai said:
This usually helps. back up the data with titanium and restore after reflashing.
Click to expand...
Click to collapse
Or use Wondershare MobileGO to backup everything
Dear Sirs, I was trying to to understand installing on Engle_Mars-SELinux-CM10.2-20131021. Now I have Retail British MILS2_U6_4.1-22_SIGNED_UCAMILESTONE2B1B80E1014.0R_UCXMILE2GBQWRTGB_P016_A006_HWp2a_Service1FF.sbf.gz. What should I do?
Root?
clockworkmod 6???
Or Team Win Recovery Project????
Thank You
I got it, I had to first get root and burn for cm10.
battery are lasting many hours?
Not very long.
About 60% battery supports about 22h. This is a backup battery which had been in storage mode for months.
For a "Active" battery, I could get about 70% battery for about 2 days.
I'm having trouble updating applications play in store, the 403 error appears on all updates. I looked for solutions on google without success. Someone with the same problem? How to solve?
hi,when i touch bluetooth phone will be reboot and allway live at the cm logo.
Pacau said:
I'm having trouble updating applications play in store, the 403 error appears on all updates. I looked for solutions on google without success. Someone with the same problem? How to solve?
Click to expand...
Click to collapse
I updated via OTA to android 4.4 and everything is working again perfectly. Thank you Engle_Mars!
Sorry for the OT, but how does kitkat feel?
Sent from my A953 using xda app-developers app
dat00 said:
Dear Sirs, I was trying to to understand installing on Engle_Mars-SELinux-CM10.2-20131021. Now I have Retail British MILS2_U6_4.1-22_SIGNED_UCAMILESTONE2B1B80E1014.0R_UCXMILE2GBQWRTGB_P016_A006_HWp2a_Service1FF.sbf.gz. What should I do?
Root?
clockworkmod 6???
Or Team Win Recovery Project????
Thank You
Click to expand...
Click to collapse
Hi dat00,
See the steps bellow:
1) Root your phone (you may use SuperOneClick root method)
2) Install Droid2 Bootstrap Recovery
3) Open Droid2 Bootstrap Recovery and tap "Bootstrap Recovery", then "Reboot Recovery" granting root privileges. The phone should reboot into recovery. Use volume buttons to navigate, camera button to accept, power button to go back. You will install files by selecting "Install zip from sdcard".
4) Optionally: create a backup of your data
5) Install latest CM ROM image file.
6) Optionally: install Google Apps
7) Select "Wipe data/factory reset"
8) Reboot and enjoy
Credits from tezet's cm10 topic: http://forum.xda-developers.com/showthread.php?t=1827801
After install the CM10 tezet's version you should be able to instal any custom rom like KitKat from Eagle or czechop version. Refer's to Yet another CM10.2 (http://forum.xda-developers.com/showthread.php?t=2451742)
Every time I try to activate wifi the following error appears in logcat:
Code:
I/WifiManager( 1421): setWifiEnabled : true
I/WifiService( 879): setWifiEnabled: true pid=1421, uid=10141
E/WifiHW ( 879): ##################### set firmware type 0 #####################
E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 879): ==========[WIFI] Station firmware load ===========
D/SSRMv2:Monitor( 879): SIOP:: AP = 400 (read only)
E/WifiHW ( 879): return of insmod : ret = -1, No such device
E/WifiStateMachine( 879): Failed to load driver
D/WfdService( 879): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 1421): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-NetworkController( 1421): Nothing, mRoamingIconId = 0
I/elm ( 2716): MainReceiver.onReceive() : android.net.wifi.WIFI_STATE_CHANGED
E/WifiStateMachine( 879): sendErrorBroadcast code:10
E/WifiController( 879): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
I/elm ( 2716): MainReceiver.onReceive() END - - - - - : android.net.wifi.WIFI_STATE_CHANGED
D/elm ( 2716): ELMEngine.getInstance().
I/DownloadNowBroadcastReceiver( 3770): onReceive
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.TMNetworkReceiver() Enter 1 main
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - exit
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() UnHandled
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Exit
D/MTPRx ( 4799): DRIVER_TIME_OUT 60s lapsed
and I tried all sorts of wifi fixers available in the forum without success. After some research I found the following post:
http://forum.xda-developers.com/showthread.php?t=1652702
what makes me think it's a problem with the driver.
The solution was found by this user:
I fixed this issue by copying libhardware_legacy.so from my OEM ROM to the ported ROM. Rebooted and WiFi worked just fine
Click to expand...
Click to collapse
I would like to know how to apply this solution to the GT-I9505. I must confess I do not think there is a solution to my problem, so any suggestion will be very welcome.
I am using Stock 4.3
Thanks in advance
Must have something similar I've gone 3 days without WiFi
I'll give this a go and get back to you. :good:
Edit: What a random series of events!
I looked at the line in your Logcat 'E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory' and when I looked I did have this file so deleted it and tried Wifi, nothing.
So I tried to replace that 'libhardware_legacy.so' file, but without thinking about it I'd taken it from a stock TW rom when I'm on a AOKP based rom. Doh!
Of course, it didn't boot and then I was left thinking "Oh ****"
I then tried flashing an old Android 4.2 rom I had on my SDCard but I did it lazily by only formatting the system and clearing Cache and Dalvik.
When I restarted it showed the boot image and then did nothing, so I went back into recovery and restored the system partition from a backup I created the other day (But whilst it was broken) of the same ROM I was on at the beginning of this post.
When it booted again it had a weird corrupted image, from my experience that's normally Kernel related, I also had a copy of KT Kernel on my SDCard, so flashed that, then wiped Cache and Dalvik
Low and behold when it finally booted, I went into settings and there was Wifi switched on and had found all my local Wifis. I got it to connect and ran some speed tests. Also restarted the phone and switched it on and off to make sure it wasn't just a fluke or hoax and now it seems I'm all sorted!
.... But for how long....
Pulse654321 said:
Must have something similar I've gone 3 days without WiFi
I'll give this a go and get back to you. :good:
Edit: What a random series of events!
I looked at the line in your Logcat 'E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory' and when I looked I did have this file so deleted it and tried Wifi, nothing.
So I tried to replace that 'libhardware_legacy.so' file, but without thinking about it I'd taken it from a stock TW rom when I'm on a AOKP based rom. Doh!
Of course, it didn't boot and then I was left thinking "Oh ****"
I then tried flashing an old Android 4.2 rom I had on my SDCard but I did it lazily by only formatting the system and clearing Cache and Dalvik.
When I restarted it showed the boot image and then did nothing, so I went back into recovery and restored the system partition from a backup I created the other day (But whilst it was broken) of the same ROM I was on at the beginning of this post.
When it booted again it had a weird corrupted image, from my experience that's normally Kernel related, I also had a copy of KT Kernel on my SDCard, so flashed that, then wiped Cache and Dalvik
Low and behold when it finally booted, I went into settings and there was Wifi switched on and had found all my local Wifis. I got it to connect and ran some speed tests. Also restarted the phone and switched it on and off to make sure it wasn't just a fluke or hoax and now it seems I'm all sorted!
.... But for how long....
Click to expand...
Click to collapse
You are lucky!
Can you explain the process of extract 'libhardware_legacy.so from a stock ROM and flash it on lhe device?
About lhe kernel, i Tried them all with no success.
Thank tou!
arleybarros said:
You are lucky!
Can you explain the process of extract 'libhardware_legacy.so from a stock ROM and flash it on lhe device?
About lhe kernel, i Tried them all with no success.
Thank tou!
Click to expand...
Click to collapse
Well I actually took it from a ROM that was in zip format, that you can flash in CWM so was quite easy. I've included it for you to try. It may not work the same as mine so make sure you have a backup to revert to!
And the KT kernel I used was KT-SGS4-JB4.3-AOSP-INTL-11.14.2013, but you'll need the TW version if you're on stock ROM? That version can be downloaded Here.
Pulse654321 said:
Well I actually took it from a ROM that was in zip format, that you can flash in CWM so was quite easy. I've included it for you to try. It may not work the same as mine so make sure you have a backup to revert to!
And the KT kernel I used was KT-SGS4-JB4.3-AOSP-INTL-11.14.2013, but you'll need the TW version if you're on stock ROM? That version can be downloaded Here.
Click to expand...
Click to collapse
I really appreciate the help, but this also did not work. I'm starting to think I have a hardware problem. is possible to diagnose it via ADB?
I'm thinking that I must have a problem with the permissions of folders and partitions, because the file "/ data / .cid.info" should be created automatically (if I'm not mistaken) and here, no matter what I do, this file is not available.
Could someone show me how to check the correct permissions for the folders and partitions?
Yeah that's really odd. The file is recreated for me when I was deleting it before and restarting. I'm not sure which file browser I'm using atm. 2 secs and I'll get some pictures up and the permissions for folders.
This is the file manager I'm using, should work ok. Hopefully it works with root features.
I've included pictures of permissions for folders, hopefully they help.
Whoops mis interpreted the pictures
Cat you give an example of what should be in the .cid.info?
Hello XDA
How are you ?
I have a phone S5(SM-G900F).
What happened is that suddenly I started to get camera failed warning once i open the camera app ... And it force the camera app to shut... Even it happens when i try to use snapchat backcamera ( front one work fine ).
I searhed for a fix and i did everything ( FR, delete cache, chanhed app) nothing helped.. So i decided to check the firmware for the camera ... I found some are written as null for the rear camera i dont know why ??any one know of any way to solve this?
Thanks
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