Im starting to port the sony ericsson arc rom to our desire s and i just wanted to know who would be intrested in my rom ????? let me know what u think of the sony ericsson arc and what new things you would like to see in this port. like timescape and other things. its going to be good porting and i hope your all intrested and i aint doing this for nothing lol
paul.robo said:
Im starting to port the sony ericsson arc rom to our desire s and i just wanted to know who would be intrested in my rom ????? let me know what u think of the sony ericsson arc and what new things you would like to see in this port. like timescape and other things. its going to be good porting and i hope your all intrested and i aint doing this for nothing lol
Click to expand...
Click to collapse
Yup. More choice is always a good thing!!
I vote for a port. Do your thing!
LOG CAT
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Users\paul\Desktop\DOWNGRADE.SAGA.AND.GUIDE
C:\Users\paul\Desktop\DOWNGRADE.SAGA.AND.GUIDE>adb logcat
* daemon not running. starting it now *
* daemon started successfully *
--------- beginning of /dev/log/main
I/DEBUG ( 1175): debuggerd: Nov 29 2011 12:52:30
--------- beginning of /dev/log/system
I/Vold ( 1173): Vold 2.1 (the revenge) firing up
D/AK8975 ( 1182): AK8975 daemon 1.0.8 Start
D/AK8975 ( 1182): (Library version : 1.2.1.1125)
I/rmt_storage( 1183): rmt_storage user app start
I/rmt_storage( 1183): rmt_storage open success
I/rmt_storage( 1183): rmt_storage shared memory ioctl success
I/rmt_storage( 1183): rmt_storage mmap addr = 40009000
D/Vold ( 1173): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1173): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 1173): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted
)
THIS SHOWS ERRORS SO NOW IM GOING TO CHANGE MY APPROACH AND GET A DIFF SONY ROM AND FROM THE X10 NOW THAT WAS FROM ARC S WHICH IS GOING TO BE MUCH MUCH HARDER SO ILL STICK WITH THE X10 FOR NOW.
I'm trying to find resources for building Jelly Bean from AOSP for Nexus S 4G. I realize that updated binaries haven't been posted yet, and I've been trying to use the proprietaries from ICS. I've pulled down AOKP, CM and a JB ROM ported to the NS4G for reference. I've tried using the extract-files.sh from AOKP against ICS as well. Right now, my rom, built using make otapackage, doesn't boot. It goes into a loop. I'm excluding the recovery. I guess that I'm looking for a little guidance into how people build ROMs for any device, whether or not binaries are explicitly delivered. I've been comparing sources, makefiles and reading logs, attempting to find some direction, but nothing has jumped out at me. Here's the beginning of the log...
Code:
?:??: W/?(?): --------- beginning of /dev/log/system
07-19 11:44:02.054: I/Vold(81): Vold 2.1 (the revenge) firing up
07-19 11:44:02.070: D/Vold(81): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
07-19 11:44:02.070: D/Vold(81): --------- beginning of /dev/log/main
07-19 11:44:02.082: I/DEBUG(85): debuggerd: Jul 18 2012 16:25:56
07-19 11:44:02.136: I/Netd(84): Netd 1.0 starting
07-19 11:44:02.191: D/Vold(81): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
07-19 11:44:02.191: D/Vold(81): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.195: W/Vold(81): Duplicate state (1)
07-19 11:44:02.808: D/AndroidRuntime(88): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
07-19 11:44:02.808: D/AndroidRuntime(88): CheckJNI is OFF
07-19 11:44:02.812: I/SurfaceFlinger(87): SurfaceFlinger is starting
07-19 11:44:02.820: I/SurfaceFlinger(87): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
07-19 11:44:02.851: E/FramebufferNativeWindow(87): couldn't open framebuffer HAL (Not a typewriter)
07-19 11:44:02.851: E/FramebufferNativeWindow(87): couldn't open gralloc HAL (Not a typewriter)
07-19 11:44:02.851: E/SurfaceFlinger(87): Display subsystem failed to initialize. check logs. exiting...
...but I've not found any help regarding it. I've found several guides for porting roms, but not many for how to build from source for devices or versions not directly supported in AOSP. Does anyone know of a good resource for me? I promise to share anything that I learn or produce from this project! Thank you!
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
Code:
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/DEBUG ( 1389): tid 15467 does not exist in pid 15467. ignoring debug request
I/ServiceManager( 1385): service 'media.audio_flinger' died
I/ServiceManager( 1385): service 'media.player' died
I/ServiceManager( 1385): service 'media.camera' died
I/ServiceManager( 1385): service 'media.audio_policy' died
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/mediaserver(15513): ServiceManager: 0x2a00b448
I/AudioFlinger(15513): Using default 3000 mSec as standby time.
E/MediaPlayerFactory(15513): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15513): calling dlsym on pFactoryLib for FACTORY_CREATE_FN
E/MediaPlayerFactory(15513): registering DASH Player factory...
I/CameraService(15513): CameraService started (pid=15513)
I/CameraService(15513): Loaded "BCM21553 Camera HAL" camera module
D/BcmCamera(15513): HAL_get_number_of_cameras: numCameras:1
I/AudioPolicyManagerBase(15513): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
I/AudioFlinger(15513): loadHwModule() Loaded primary audio interface from Samsung BCM21553 audio HW HAL (audio) handle 1
I/AudioFlinger(15513): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer(15513): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger(15513): Using module 1 has the primary audio interface
D/AudioPolicyManagerBase(15513): setOutputDevice() changing device from (2) to (2) force (1) delayMs (0) on Output (2)
I/AudioFlinger(15513): AudioFlinger's thread 0x40f53008 ready to run
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
D/audio_hw_primary(15513): call=n, earpiece=n hp=n speaker=y sco=n a2dp=n out_device=2
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
I/audio_a2dp_hw(15513): adev_open: adev_open in A2dp_hw module
I/AudioFlinger(15513): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger(15513): loadHwModule() Loaded usb audio interface from USB audio HW HAL (audio) handle 4
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
E/AudioFlinger(15513): no wake lock to update!
I/r_submix(15513): adev_open(name=audio_hw_if)
I/r_submix(15513): adev_init_check()
I/AudioFlinger(15513): loadHwModule() Loaded r_submix audio interface from Wifi Display audio HAL (audio) handle 5
I/AudioPolicyService(15513): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/AndroidRuntime(15512):
D/AndroidRuntime(15512): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime(15512): CheckJNI is OFF
D/dalvikvm(15512): Unable to stat classpath element '/system/framework/core.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm(15512): DexOpt: --- BEGIN 'conscrypt.jar' (bootstrap=1) ---
E/dalvikvm(15640): Fatal error: java/lang/Object
E/dalvikvm(15640): VM aborting
F/libc (15640): Fatal signal 6 (SIGABRT) at 0x00003d18 (code=-6), thread 15640 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
I/DEBUG ( 1389): Revision: '0'
I/DEBUG ( 1389): pid: 15640, tid: 15640, name: dexopt >>> /system/bin/dexopt <<<
[A bunch of seemingly random (at least for such a noob like me) numbers]
W/dalvikvm(15512): DexOpt: --- END 'conscrypt.jar' --- status=0x0006, process failed
E/dalvikvm(15512): Unable to extract+optimize DEX from '/system/framework/conscrypt.jar'
D/dalvikvm(15512): Unable to process classpath element '/system/framework/conscrypt.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/dalvikvm(15512): DexOpt: --- BEGIN 'okhttp.jar' (bootstrap=1) ---
E/dalvikvm(15692): Fatal error: java/lang/Object
E/dalvikvm(15692): VM aborting
F/libc (15692): Fatal signal 6 (SIGABRT) at 0x00003d4c (code=-6), thread 15692 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
knuxfanwin8 said:
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
Click to expand...
Click to collapse
Yeah. You need to Deodex both ROM BASE and PORT BEFORE you build. That is the reason you keep getting dex errors. Use ASSAYYED Kitchen or @superR's Kitchen or similar to accomplish this ?
Hi,
I updated my phone to the June 2019 security patch via factory image.
I then rooted the phone via patched boot image method.
Root is working (Safetynet passes, Magisk Hide is working etc) but I am having two major issues.
1. If I try to hide Magisk Manager (repackeg apk) I lose root. Uninstalling Magisk Manager and reinstalling fixes the issue
2. If I click the superuser tab, Magisk crashes.
Any ideas? I also posted in the general Magisk help thread.
Thanks in advance!
EDIT: I was able to fix 2 by force stopping Magisk Manager, deleting cache/app data and restarting. I dont really have a need for 1 at the moment so I think i'll leave it as is for now.
EDIT 2: Seems like the issue only happens when using the light theme? I am using the dark theme now and dont experience the same issues.
EDIT 3: NVM... the issue is back. Doesnt matter if I clear cache/app data or which theme I use.. it keeps randomly crashing when going to the superuser tab
Below is the logcat if its at all helpful
Code:
[ 06-19 19:07:14.546 1162: 1200 I/ActivityManager ]
Start proc 4487:com.google.android.apps.maps/u0a101 for broadcast com.google.android.apps.maps/com.google.android.apps.gmm.navigation.service.detection.StartDetectionReceiver
--------- beginning of crash
[ 06-19 19:07:14.701 2386: 2386 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.topjohnwu.magisk, PID: 2386
java.lang.IndexOutOfBoundsException: Inconsistency detected. Invalid view holder adapter positionViewHolder{348cd71 position=1 id=-1, oldPos=0, pLpos:0 scrap [attachedScrap] tmpDetached not recyclable(1) no parent} androidx.recyclerview.widget.RecyclerView{9833892 VFED..... ......ID 0,0-1080,1868 #7f09016f app:id/superuser_content}, adapter:[email protected], layout:[email protected], context:[email protected]
at androidx.recyclerview.widget.RecyclerView$v.a(SourceFile:55)
at androidx.recyclerview.widget.RecyclerView$v.b(SourceFile:1)
at androidx.recyclerview.widget.LinearLayoutManager$c.a(SourceFile:4)
at androidx.recyclerview.widget.LinearLayoutManager.a(Unknown Source:0)
at androidx.recyclerview.widget.LinearLayoutManager.a(SourceFile:3)
at androidx.recyclerview.widget.LinearLayoutManager.c(SourceFile:22)
at androidx.recyclerview.widget.RecyclerView.e(SourceFile:2)
at androidx.recyclerview.widget.RecyclerView.d(Unknown Source:29)
at androidx.recyclerview.widget.RecyclerView.onLayout(Unknown Source:5)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at a.w60.b(SourceFile:2)
at a.x60.a(Unknown Source:0)
at androidx.coordinatorlayout.widget.CoordinatorLayout.onLayout(Unknown Source:42)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at androidx.drawerlayout.widget.DrawerLayout.onLayout(Unknown Source:56)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1812)
at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1656)
at android.widget.LinearLayout.onLayout(LinearLayout.java:1565)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1812)
at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1656)
at android.widget.LinearLayout.onLayout(LinearLayout.java:1565)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at com.android.internal.policy.DecorView.onLayout(DecorView.java:753)
at android.view.View.layout(View.java:20672)
at android.view.ViewGroup.layout(ViewGroup.java:6194)
at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:2799)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2316)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1463)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7190)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:949)
at android.view.Choreographer.doCallbacks(Choreographer.java:761)
at android.view.Choreographer.doFrame(Choreographer.java:696)
[ 06-19 19:07:14.701 2386: 2386 E/AndroidRuntime ]
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:935)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6718)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
[ 06-19 19:07:14.705 1162: 1911 W/ActivityManager ]
Force finishing activity com.topjohnwu.magisk/a.b
[ 06-19 19:07:14.731 1162: 3000 I/ActivityManager ]
Process com.topjohnwu.magisk (pid 2386) has died: vis +99TOP
TLDR: random freeze (for 10-15s) followed by reboot, tried everything, it's getting worse (can't use the phone at all), no idea what to do, probably throw to bin and not buy samsungs anymore
Hello everyone,
My daily phone started having crashes yesterday: in (arguably random) moments while using it, it just hangs for ~10s then reboots immediately. After some tinkling/searching/trying stuff, I found out it crashes with 95% probability if I go to settings, debugging options and click on running services, it also crashed a few times while loading the app list, and a few times while using waze.
The phone is completely official, not even custom recovery, no root, nothing. I didn't install anything new right before the crashes, but I still deleted all the recent apps I've downloaded for the last weeks and it still crashes. It also crashed in SAFE MODE which is pretty disturbing as it seems to me it's something very serious and not just some random app.
The story:
The very first crash happened while using the Waze app and trying to open Samsung music and connecting to my bluetooth headphones (which I usually do without problems, last time I did this was 2 days ago for a 1h trip without problems), a few seconds after my headphones connected the screen just froze and the phone rebooted. My first reaction was it probably got overheated (as It was really hot outside) so I just put it in the air vent and continued driving with google maps. About 30 mins later I switched again to waze, no crashes, also powered on my headphones, again no crashes. 1h later I got a phone call and immediately after finishing the call and the phone tried to switch back to the homescreen (or waze app, not sure), it crashed.
After getting home I uninstalled waze (the main suspect here) and turned off bluetooth and it just crashed after 5-10 mins of randomly trying to see what's wrong. I kept having more and more frequent crashes (it seems that not touching the phone right after rebooting for at least 10 mins is helping here as it otherwise would crash again). It also got stuck in the Samsung logo for a while and I thought I completely lost it but it seems like to force reboot the combination is 8seconds of power+volume up (not just power). At this point I started deleting most of the apps I didn't have for more than a few months and even tried safe mode but still going through settings, app list and into the services menu almost always crashed the phone. I also removed the microsd card (which seemed to help temporarily as I could see the services now, but the crashes came back after a very short while even without the card and sim) and cleaned up recent photos (took some raw photos the night before for the first time in a long while, moved them to the pc and deleted them from the phone).
Debugging:
After having no luck with removing the microsd card, the sim and deleting all the recently installed apps (from the last 2-3 weeks) and also wiping cache (and some data) to most of the bigger apps, I installed adb and tried some adb logcat > file.txt and used the phone to try to get to the crash.
The logcat files are huge, but trying to look at the last few seconds (hundreds of lines) the only obvious error is this one regarding memory/memtrack:
Code:
[ 07-19 12:47:22.389 3666: 4249 W/android.os.Debug ]
failed to get memory consumption info: -1
[ 07-19 12:47:22.409 3666: 4249 E/memtrack ]
Couldn't load memtrack module
[ 07-19 12:47:22.409 3666: 4249 W/android.os.Debug ]
failed to get memory consumption info: -1
[ 07-19 12:47:22.429 3666: 4249 E/memtrack ]
Couldn't load memtrack module
[ 07-19 12:47:22.429 3666: 4249 W/android.os.Debug ]
failed to get memory consumption info: -1
Searching for memtrack in the 5 logcat files I got (only 3 of them had the crash) results in about 3400+ hits for this word.
---------
I just tried again to get a crash for fresh logs and this time I couldn't get it in the settings services/app list but while opening and closing a few apps, last one gmail and yahoo mail, before the samsung's game launcher. There seems to be something new with thousands of hits:
Code:
07-19 22:35:26.904 9074 9074 W ResourceType: For resource 0x7f0607f8, entry index(2040) is beyond type entryCount(533)
07-19 22:35:26.904 9074 9074 W ResourceType: For resource 0x7f1405f5, entry index(1525) is beyond type entryCount(385)
07-19 22:35:26.904 9074 9074 W ResourceType: For resource 0x7f1406bd, entry index(1725) is beyond type entryCount(385)
07-19 22:35:26.904 9074 9074 W ResourceType: For resource 0x7f1406a2, entry index(1698) is beyond type entryCount(385)
07-19 22:35:26.904 9074 9074 W ResourceType: For resource 0x7f1406a3, entry index(1699) is beyond type entryCount(385)
07-19 22:35:26.904 9074 9074 W ResourceType: For resource 0x7f1406ba, entry index(1722) is beyond type entryCount(385)
07-19 22:35:26.904 9074 9074 W ResourceType: For resource 0x7f14073e, entry index(1854) is beyond type entryCount(385)
filtering for 9074 gives some weird stuff (20.000+ search results):
Code:
07-19 22:35:27.913 9074 9074 W ResourceType: For resource 0x7f06033a, entry index(826) is beyond type entryCount(533)
07-19 22:35:27.972 3653 3795 D MdnieScenarioControlService: packageName : com.google.android.gm className : com.google.android.gm.ConversationListActivityGmail
07-19 22:35:27.973 3653 3795 V MdnieScenarioControlService: setUIMode from UI function(3)
07-19 22:35:27.990 9074 9074 V InputMethodManager: Starting input: [email protected] nm : com.google.android.gm ic=null
07-19 22:35:27.990 9074 9074 I InputMethodManager: startInputInner - mService.startInputOrWindowGainedFocus
07-19 22:35:27.990 3653 10860 D InputMethodManagerService: startInputOrWindowGainedFocus : startInput
07-19 22:35:27.991 3653 10860 D InputMethodManagerService: setCurrentInputInfo - inputContext : null eidtorInfo : [email protected] missingMethods : 0
07-19 22:35:27.991 23401 23401 I InputMethodWrapper: call dispatchStartInputWithToken
07-19 22:35:27.992 23401 23401 I InputMethodService: dispatchStartInputWithToken
07-19 22:35:27.992 9074 9074 W Gmail : RVGmail:Problem with folder list cursor returned from loader
07-19 22:35:28.004 9074 9074 W Gmail : RVGmail:Problem with folder list cursor returned from loader
07-19 22:35:28.013 3323 3602 D DnsProxyListener: DNSDBG::dns addrinfo af 2
07-19 22:35:28.014 3323 3602 D DnsProxyListener: DNSDBG::dns addrinfo af 2
07-19 22:35:28.039 9074 9074 W Gmail : AccountUtils:For b/73513912, load account <.................removed some id that looked private.....................> from MailAppProvider. Is account valid result: 2.
07-19 22:35:28.055 9074 9079 I zygote64: Do partial code cache collection, code=243KB, data=138KB
07-19 22:35:28.056 9074 9079 I zygote64: After code cache collection, code=236KB, data=135KB
07-19 22:35:28.056 9074 9079 I zygote64: Increasing code cache capacity to 1024KB
07-19 22:35:28.070 9074 9246 I zygote64: Deoptimizing void bcel.a(java.lang.Object) due to JIT inline cache
07-19 22:35:28.093 9074 9252 I zygote64: Deoptimizing void beuy.run() due to class hierarchy analysis
07-19 22:35:28.098 9074 9074 W atvt : FirebaseCrash1p.isCrashCollectionEnabled threw an exception
07-19 22:35:28.098 9074 9074 W atvt : java.lang.IllegalStateException: FirebaseCrash1p not initialized. Call FirebaseCrash1p.initFirebase() first.
07-19 22:35:28.098 9074 9074 W atvt : at yap.b(Unknown Source:4)
07-19 22:35:28.098 9074 9074 W atvt : at yap.a(Unknown Source:0)
07-19 22:35:28.098 9074 9074 W atvt : at atvt.<init>(PG:2)
07-19 22:35:28.098 9074 9074 W atvt : at osj.aI(PG:3)
07-19 22:35:28.098 9074 9074 W atvt : at orv.b(PG:75)
07-19 22:35:28.098 9074 9074 W atvt : at bhwj.b(PG:1)
07-19 22:35:28.098 9074 9074 W atvt : at osj.aK(PG:7)
07-19 22:35:28.098 9074 9074 W atvt : at osj.dX(PG:4)
07-19 22:35:28.098 9074 9074 W atvt : at orv.b(PG:187)
07-19 22:35:28.098 9074 9074 W atvt : at zmc.run(Unknown Source:4)
07-19 22:35:28.098 9074 9074 W atvt : at android.os.Handler.handleCallback(Handler.java:789)
07-19 22:35:28.098 9074 9074 W atvt : at android.os.Handler.dispatchMessage(Handler.java:98)
07-19 22:35:28.098 9074 9074 W atvt : at android.os.Looper.loop(Looper.java:164)
07-19 22:35:28.098 9074 9074 W atvt : at android.app.ActivityThread.main(ActivityThread.java:6944)
07-19 22:35:28.098 9074 9074 W atvt : at java.lang.reflect.Method.invoke(Native Method)
07-19 22:35:28.098 9074 9074 W atvt : at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
07-19 22:35:28.098 9074 9074 W atvt : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
07-19 22:35:28.113 3653 8233 D PowerManagerService: [api] setMasterBrightnessLimit : minBrightnss : -1 maxBrightness : 230 (uid: 1000 pid: 3653)
07-19 22:35:28.113 3653 8233 D PowerManagerService: mDisplayReady: false
07-19 22:35:28.113 3653 3687 D DisplayPowerController: animateScreenStateChange: target2
07-19 22:35:28.113 3653 3687 D DisplayPowerController: getFinalBrightness : Summary is 90 -> 90
but to me it just looks like gmail crashing down due to somethng else happening with the phone.
and before this there's a worrysome database error:
Code:
07-19 22:35:22.655 8740 8740 D SamsungAnalytics111040: cf feature is supported
07-19 22:35:22.656 3653 10860 D SamsungAlarmManager: setInexact Intent (T:2/F:0/AC:false) 20200719T223536 - CU:10024/CP:4569
07-19 22:35:22.656 3653 10860 I SamsungAlarmManager: setLocked to kernel - T:2 / 20200719T223536, SetElapsed=19355515, nowELAPSED=19341270
07-19 22:35:22.659 8740 8740 D SamsungAnalytics111040: [Tracker] Tracker start:1.11.040
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: Error inserting period=10000 preferred_charging_state=1 preferred_network_type=1 target_class=com.google.android.gms.measurement.PackageMeasurementTaskService required_network_type=0 runtime=1595187322643 required_idleness_state=0 source=16 service_kind=0 target_package=com.google.android.gms persistence_level=1 source_version=202414000 last_runtime=0 user_id=0 job_id=-1 requires_charging=0 tag=Measurement.PackageMeasurementTaskService.UPLOAD_TASK_TAG flex_time=4000 task_type=0 retry_strategy={"maximum_backoff_seconds":{"3600":0},"initial_backoff_seconds":{"30":0},"retry_policy":{"0":0}}
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: android.database.sqlite.SQLiteConstraintException: UNIQUE constraint failed: pending_ops.tag, pending_ops.target_class, pending_ops.target_package, pending_ops.user_id (code 2067)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: #################################################################
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: Error Code : 2067 (SQLITE_CONSTRAINT_UNIQUE)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: Caused By : Abort due to constraint violation.
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: (UNIQUE constraint failed: pending_ops.tag, pending_ops.target_class, pending_ops.target_package, pending_ops.user_id (code 2067))
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: #################################################################
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId(Native Method)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId(SQLiteConnection.java:953)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at android.database.sqlite.SQLiteSession.executeForLastInsertedRowId(SQLiteSession.java:788)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at android.database.sqlite.SQLiteStatement.executeInsert(SQLiteStatement.java:86)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.insertWithOnConflict(SQLiteDatabase.java:1904)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.insert(SQLiteDatabase.java:1771)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at aqui.a(:[email protected]@20.24.14 (040408-319035315):175)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at aqtk.a(:[email protected]@20.24.14 (040408-319035315):182)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at aqtk.a(:[email protected]@20.24.14 (040408-319035315):23)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at aqtk.a(:[email protected]@20.24.14 (040408-319035315):177)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at aqpu.run(:[email protected]@20.24.14 (040408-319035315):9)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at soy.b(:[email protected][email protected] (040408-319035315):12)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at soy.run(:[email protected]@20.24.14 (040408-319035315):7)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at sux.run(:[email protected]@20.24.14 (040408-319035315):0)
07-19 22:35:22.659 4569 5388 E SQLiteDatabase: at java.lang.Thread.run(Thread.java:764)
07-19 22:35:22.660 8740 8740 I GameTools: SCPMHelper : load from saved.
07-19 22:35:22.661 8740 8740 I GameTools: GameToolsApplication : BootCompleteReceiver enabled.
07-19 22:35:22.662 3653 10860 I SamsungAlarmManager: setLocked to kernel - T:2 / 20200719T223718, SetElapsed=19457296, nowELAPSED=19341276
07-19 22:35:22.662 3653 10860 D SamsungAlarmManager: setExact Intent (T:2/F:0/AC:false) 20200719T223532 - CU:10024/CP:4569
07-19 22:35:22.663 3653 10860 I SamsungAlarmManager: setLocked to kernel - T:2 / 20200719T223532, SetElapsed=19351257, nowELAPSED=19341276
07-19 22:35:22.663 8740 8740 I GameTools: GameToolsApplication : initNotificationChannels
07-19 22:35:22.665 8726 8726 I FirebaseInitProvider: FirebaseApp initialization successful
07-19 22:35:22.669 8740 8740 I GameTools: GameToolsApplication : touchScreenLockSecureRecovery
----------------------------
Searching for this on google doesn't really bring in anything helpful so I'm trying my luck with you guys even though it's a really long shot to have anyone with this same exact error and this same exact phone. Any thoughts?
The attached photo is what I see before the reboot, I was trying to enter the My files app and it froze there. It looks like a small graphical artifact but I don't know if it's a cause or the result of the freeze.
My next step at this point would be to back up whatever I can (how do I even backup the 2FA on authenticator apps? ...) and do a factory reset and see how that goes. A new phone really wasn't in the plans right now as the S7 was actually holding up great.
Btw, does google cloud backup/samsung cloud backup even backup anything from the apps?
UPDATE: one week later and after factory default + full reinstall rom via Odin (from sammobile) i still have the freezes&reboots.
It's actually way worse now, even though yesterday I got about one hour of intensive app installs and restores without one reboot (it did reboot 3 times in a row before this), today I actually didn't have a single full minute of phone usage... It just froze inside recovery module while going through some logs.
I assume it's something hardware at this point, most likely internal memory, is there any way to test this with some low level tool?
dany123i said:
UPDATE: one week later and after factory default + full reinstall rom via Odin (from sammobile) i still have the freezes&reboots.
It's actually way worse now, even though yesterday I got about one hour of intensive app installs and restores without one reboot (it did reboot 3 times in a row before this), today I actually didn't have a single full minute of phone usage... It just froze inside recovery module while going through some logs.
I assume it's something hardware at this point, most likely internal memory, is there any way to test this with some low level tool?
Click to expand...
Click to collapse
Your battery is dying. The issues will get worse and worse.
That would be weird as it happens even while plugged in charger. Also I did cpu/gpu benchmarks of >10 minutes on battery, no crash until I started changing apps or at the end when it showed the results, also I used the phone last night at under 30% battery in 4G+GPS navigation. This is why I think it's internal flash corruption, I can do intensive stuff if I'm lucky but I need to use one app at a time. Thanks for the suggestion though.
Right now I've reflashed the ROM and cancelled all cloud restore app requests, I just manually installed 10 apps that I really need and it seems to do acceptably fine for now (except camera, there's a 50% change of crashing after taking a photo, slow motion seems to do well for some reason :-s) until I get a good deal on a new phone. I still have some completely random reboots though (about 1h ago it froze in google keep while writing a note).
Omg, I have this issue in my g930f too. I bought this phone new, I rooted and everything was running normal until 18-24 hours passes(after rooting). Some applications starts giving crashes without any reason? Why this happening? I used A5 2015, j7 2016 and more Samsung phones and any of them didn't gave me issue.
Also, my phone's old battery was almost dead (closing at %10 charge and more) and I changed battery with newer one I don't have closing issues now.
I fixed app crashing and etc. issues with flashing custom rom. I'm on 9.0 Note FE rom and app crashing are gone...
(Sorry for my bad English)
I think we have different issues, my phone seems to be worse than yours. But I will try to root soon and install custom rom like you.
Good luck!
dany123i said:
I think we have different issues, my phone seems to be worse than yours. But I will try to root soon and install custom rom like you.
Good luck!
Click to expand...
Click to collapse
I think we have same issue man, today when I woke up I saw my phone was rebooted and asking for SIM Password, it was charging all night. then when I wanted to open messages app or Gallery app (Samsung apps) they giving same crashes with yours.. Memtrack failed and SQLite errors. I tried to open SMS Database file at "/data/user_de/0/com.android.providers.telephony/databases/mmssms.db" I can able to see the contents db file, So .db file wasn't corrupted.
There is the output of System's messages app crash.
https://imgur.com/a/08ERYBM
I'm downloading latest stock rom and I'll use it for 1-2 weeks for testing...
Update 10.08.20
I installed The Stock rom two days ago and now 15 minutes ago my phone rebooted it self while i'm watching video on youtube app.
then after rebooted I saw some app's data corrupted very bad :/
System started to give memtrack errors
Messages App's Database has been corrupted. I can't open messages app.
Android Account Manager's Database has been corrupted ("/data/system_ce/0/accounts_ce.db")
Look how badly google search app corrupted :/
https://imgur.com/a/jwE2v71
Memtrack errors
Code:
2020-08-10 16:37:56.853 3666-3704/? E/memtrack: Couldn't load memtrack module
2020-08-10 16:37:56.853 3666-3704/? W/android.os.Debug: failed to get memory consumption info: -1
2020-08-10 16:37:56.904 3666-3704/? E/memtrack: Couldn't load memtrack module
2020-08-10 16:37:56.904 3666-3704/? W/android.os.Debug: failed to get memory consumption info: -1
2020-08-10 16:37:56.944 3666-3704/? E/memtrack: Couldn't load memtrack module
2020-08-10 16:37:56.945 3666-3704/? W/android.os.Debug: failed to get memory consumption info: -1
and this's logcat output of messages app's crash;
Code:
2020-08-10 16:38:55.342 3666-4385/? E/SQLiteLog: (10) unixRead() /data/system_ce/0/accounts_ce.db fd (427) errno (5)
2020-08-10 16:38:55.343 3666-4385/? E/SQLiteLog: (266) statement aborts at 22: [SELECT key, value FROM ceDb.extras WHERE accounts_id=(select _id FROM accounts WHERE name=? AND type=?)] disk I/O error
2020-08-10 16:38:55.343 3666-4385/? E/SQLiteLog: (1) Force to rollback the active transaction caused by the special error (10), during 'SELECT key, value FROM ceDb.extras WHERE accounts_id=(select _id FROM accounts WHERE name=? AND type=?)'
2020-08-10 16:38:55.345 3666-4385/? E/SQLiteQuery: exception: disk I/O error (code 266)
#################################################################
Error Code : 266 (SQLITE_IOERR_READ)
Caused By : Disk I/O error occurred during 'read' operation.
(disk I/O error (code 266))
#################################################################; query: SELECT key, value FROM ceDb.extras WHERE accounts_id=(select _id FROM accounts WHERE name=? AND type=?)
2020-08-10 16:38:55.348 3666-4385/? E/AccountManagerService: Account Manager Crash
android.database.sqlite.SQLiteDiskIOException: disk I/O error (code 266)
#################################################################
Error Code : 266 (SQLITE_IOERR_READ)
Caused By : Disk I/O error occurred during 'read' operation.
(disk I/O error (code 266))
#################################################################
at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(Native Method)
at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:1018)
at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:836)
at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:152)
at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:141)
at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)
at android.database.AbstractCursor.moveToNext(AbstractCursor.java:268)
at com.android.server.accounts.AccountsDb.findUserExtrasForAccount(AccountsDb.java:447)
at com.android.server.accounts.AccountManagerService.readUserDataInternal(AccountManagerService.java:6188)
at com.android.server.accounts.AccountManagerService.getUserData(AccountManagerService.java:1657)
at android.accounts.IAccountManager$Stub.onTransact(IAccountManager.java:76)
at com.android.server.accounts.AccountManagerService.onTransact(AccountManagerService.java:1094)
at android.os.Binder.execTransact(Binder.java:682)
Android Account Manager's error outputs:
Code:
2020-08-10 17:06:48.003 3666-3919/? E/SQLiteLog: (10) unixRead() /data/system_ce/0/accounts_ce.db fd (427) errno (5)
2020-08-10 17:06:48.004 3666-3919/? E/SQLiteLog: (266) statement aborts at 22: [SELECT key, value FROM ceDb.extras WHERE accounts_id=(select _id FROM accounts WHERE name=? AND type=?)] disk I/O error
2020-08-10 17:06:48.004 3666-3919/? E/SQLiteLog: (1) Force to rollback the active transaction caused by the special error (10), during 'SELECT key, value FROM ceDb.extras WHERE accounts_id=(select _id FROM accounts WHERE name=? AND type=?)'
2020-08-10 17:06:48.007 3666-3919/? E/SQLiteQuery: exception: disk I/O error (code 266)
#################################################################
Error Code : 266 (SQLITE_IOERR_READ)
Caused By : Disk I/O error occurred during 'read' operation.
(disk I/O error (code 266))
#################################################################; query: SELECT key, value FROM ceDb.extras WHERE accounts_id=(select _id FROM accounts WHERE name=? AND type=?)
2020-08-10 17:06:48.009 3666-3919/? E/AccountManagerService: Account Manager Crash
android.database.sqlite.SQLiteDiskIOException: disk I/O error (code 266)
#################################################################
Error Code : 266 (SQLITE_IOERR_READ)
Caused By : Disk I/O error occurred during 'read' operation.
(disk I/O error (code 266))
#################################################################
at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(Native Method)
at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:1018)
at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:836)
at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:152)
at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:141)
at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)
at android.database.AbstractCursor.moveToNext(AbstractCursor.java:268)
at com.android.server.accounts.AccountsDb.findUserExtrasForAccount(AccountsDb.java:447)
at com.android.server.accounts.AccountManagerService.readUserDataInternal(AccountManagerService.java:6188)
at com.android.server.accounts.AccountManagerService.getUserData(AccountManagerService.java:1657)
at android.accounts.IAccountManager$Stub.onTransact(IAccountManager.java:76)
at com.android.server.accounts.AccountManagerService.onTransact(AccountManagerService.java:1094)
at android.os.Binder.execTransact(Binder.java:682)
2020-08-10 17:06:48.012 3666-3919/? E/JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
android.database.sqlite.SQLiteDiskIOException: disk I/O error (code 266)
#################################################################
Error Code : 266 (SQLITE_IOERR_READ)
Caused By : Disk I/O error occurred during 'read' operation.
(disk I/O error (code 266))
#################################################################
at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(Native Method)
at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:1018)
at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:836)
at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:152)
at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:141)
at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)
at android.database.AbstractCursor.moveToNext(AbstractCursor.java:268)
at com.android.server.accounts.AccountsDb.findUserExtrasForAccount(AccountsDb.java:447)
at com.android.server.accounts.AccountManagerService.readUserDataInternal(AccountManagerService.java:6188)
at com.android.server.accounts.AccountManagerService.getUserData(AccountManagerService.java:1657)
at android.accounts.IAccountManager$Stub.onTransact(IAccountManager.java:76)
at com.android.server.accounts.AccountManagerService.onTransact(AccountManagerService.java:1094)
at android.os.Binder.execTransact(Binder.java:682)
2020-08-10 17:06:48.013 4585-5402/? W/GLSActivity: [GmsAccountAuthenticatorImpl] [B]Services not available! [/B]
I'm thinking this as a hardware problem.