I went ahead and let my phone update itself and since then it's been really SLOW. Phone calls take 5-45 seconds to connect, which is beyond aggravating. Apps don't run as fast as they use to. And I am constantly reconnecting the Mobile network because it keeps losing it. Anyone have similar and get around it??

I have a Samsung Galaxy S23 Ultra running Android 13. Does upgrading a Samsung Galaxy S23 Ultra phone from Android 13 to Android 14 decrease the phone's performances?

I would like to backup over 100 GB of photos and videos stored on an Android phone to a local external drive (SSD or HDD). Unfortunately, the Android phone does not have a microSD card (which would make this task trivial). I do not want to upload anything to the cloud. As a first attempt, I connected the Android phone via USB 3.x to a Windows 11 box using the MTP protocol. I also connected an external SSD via USB 3.x to that same box. I configured FreeFileSync to copy the desired folders, and began the copying process. After about 5 minutes of process stabilization, FreeFileSync reported that it would take another 2 days to complete the operation! That's no good. What's the fastest way to complete this task? It's important that, if possible, file timestamps are preserved (in addition to Exif timestamps, of course). I would prefer to use a Windows 11 box for the transfers, but I can instead use a Linux box if Windows is the problem. In this particular case, the Android device is a Google Pixel 6 phone, but I would like to be able to quickly handle the same task for other devices, including Samsung, Motorola, LG, and Sony phones.

Everything was working fine for a long time. But suddenly the device is getting slower than usual (e.g. apps react slowly when starting an action -- like the RSS reader takes "ages" to open an article). Also, several apps start crashing: force-closes as well as unexpected restarts. Sometimes this even involves some automatic reboot of the device. Is there anything I can do, besides doing a factory-reset? Preferably it should work on un-rooted devices. Remark: not all described problems may occur together, so on one device e.g. there might be no automatic reboot involved. Question remains the same, nonetheless.

I enabled developer options on my Samsung Galaxy Grand Duos and then changed "Limit background process" option from *Standard limit* to *No background process*. After that my phone is working fine, with no hanging problems or no slowness as before. But my doubt is, will this change affect any process, updates, applications or anything which might cause an error or failure?

So Samsung decided to factor in a feature that I have only seen work on desktop PCs called RAM plus and it's supposed to let the system use internal storage for to keep more background processes running. So does this add us more RAM and will there be a significant improvement in performance for enabling this option. Will it necessarily result in more processes running in the background being kept alive or?

Galaxy S20 5G This started happening a few months ago. Not sure if it was an android update or not. When I try to open password manager in chrome it spins and I have to wait 2+ mins- it eventually does open. I've noticed this with other apps like youtube as well. I don't think my phone is under load. Could it have been a recent update? What is the best way to troubleshoot this kind of thing? My phone isn't crashing, while it spins my pod cast app continues to play audio without hiccups so I don't think its the OS lagging. Its like it just wants to wait several minutes before loading some apps.

I'm using the Android Emulator from IntelliJ on Kubuntu. I noticed in plasma-systemmonitor that qemu-system-x86_64 continuously does on the order of a few MB/s of disk writes even as I'm not using the emulator at all, it's just open. Sometimes it goes below 1 MB/s, sometimes up to a few dozen MB/s. Is this level of activity normal? I'm starting to wonder if this amount of writes can shorten the life of my SSD if I leave it running all the time. Or could it be another type of writes that are not disk writes? I'm not 100% sure what plasma-systemmonitor measures. I'm emulating a Pixel 4 with Google Play.

I am using Musicolet player which has an option to use Musicolet scanner or system scanner for media scanning. I wonder why scanning some single huge file is so slow? Does the scanner have to scan each file byte by byte or what takes so long?

Every since my Nokia 5.3 was upgraded to Andoid 12 recently, the battery suffers from processes com.android.phone and qcrild using the CPU a fair amount. It is not completely reproducible, but it happens especially when the the phone is locked, or at least the screen is off. I observe that increased CPU usage via adb shell top -u radio. At that same time adb shell dumpsys phone shows a lot of the following:

❯ adb shell dumpsys phone
------- PhoneGlobals -------
  mPrevRoamingNotification=0
  mDefaultDataSubId=1
  mDataRoamingNotifLog:
  isSmsCapable=true
    2022-11-23T13:56:23.510818 - dataAllowed=true, reasons=Data allowed reason: NORMAL
    2022-11-23T13:56:23.512116 - dataAllowed=true, reasons=Data allowed reason: NORMAL
[snip rest of the output]

And that seems to always immediately follow these adb shell logcat -d phone warnings about ...without a qualified user and Permission Denial to read the phone state:

11-23 13:56:23.460  1681  3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1206 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2880 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 android.os.Binder.execTransactInternal:1184
11-23 13:56:23.461  1681  3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2884 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 
11-23 13:56:23.462  1681  3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2891 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 
11-23 13:56:23.463  1681  2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.READ_PHONE_STATE due to sender android (uid 1001)
11-23 13:56:23.463  1681  2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.ACCESS_FINE_LOCATION due to sender android (uid 1001)
11-23 13:56:23.464  1681  3481 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1256 android.content.Context.sendBroadcastMultiplePermissions:2215 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:2895 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1608 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:455 
11-23 13:56:23.465  1681  2031 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver requires android.permission.READ_PHONE_STATE due to sender android (uid 1001)

And that results in a lot of logging that seems to be about refreshing the data about my mobile carrier (onRefreshCarrierInfo()), which may be where the CPU time is actually spent (following log capture is from a later occurrence):

11-23 14:18:08.592  2936  2936 D ServiceStateProvider: subId=1
11-23 14:18:08.592  2462  2640 I CustomizedNetworkIcon: getConfigValueByKey: oem_key_rat_name_of_4g_int=0
11-23 14:18:08.595  2462  2640 I CustomizedNetworkIcon: getConfigValueByKey: oem_display_lte_icon_int=1
11-23 14:18:08.597  2936  2936 I Telephony: TelecomAccountRegistry: onSubscriptionsChanged - reregister accounts
11-23 14:18:08.598  1676  2040 D CompatibilityInfo: mCompatibilityFlags - 0
11-23 14:18:08.598  2936  2936 D Telephony: isEmergencyPreferredAccount: subId=1, activeData=1
11-23 14:18:08.598  1676  2040 D CompatibilityInfo: applicationDensity - 280
11-23 14:18:08.598  2936  2936 D Telephony: isEmergencyPreferredAccount: Device does not require preference.
11-23 14:18:08.598  1676  2040 D CompatibilityInfo: applicationScale - 1.0
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: onReceive Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 cmp=com.google.android.cellbroadcastreceiver/com.android.cellbroadcastreceiver.CellBroadcastReceiver (has extras) }
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: onServiceStateChanged, ss: 0
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: networkOperator: 20416
11-23 14:18:08.600 31066 31066 D CellBroadcastReceiver: update supported roaming operator as
11-23 14:18:08.601  2936  2936 I Telephony: isRttCurrentlySupported -- regular acct, hasVoiceAvailability: false
11-23 14:18:08.601  2936  2936 I Telephony:  isRttSupported: false
11-23 14:18:08.601  2936  2936 I Telephony:  isUserRttSettingOn: false
11-23 14:18:08.601  2936  2936 I Telephony:  alwaysAllowWhileRoaming: false
11-23 14:18:08.601  2936  2936 I Telephony:  isRoaming: false
11-23 14:18:08.601  2936  2936 I Telephony:  isOnWfc: false
11-23 14:18:08.607  2462  2640 E CustomizedImsIcon: customizedVoLTEandVoWiFiIcon:
11-23 14:18:08.608  2462  4440 I CustomizedImsIcon:  customizedImsIcon:++
11-23 14:18:08.608  2462  4440 D CustomizedImsIcon: isAirplaneModeOn: false
11-23 14:18:08.608  2462  4440 D CustomizedImsIcon: customizedImsIcon:clear all vowifi icon which is added with TAG when airplane is off
11-23 14:18:08.608  2462  4440 I CustomizedImsIcon:  isOperaterCustomized:mccmnc=20416
11-23 14:18:08.609  2462  4440 I CustomizedImsIcon:  isOperaterClaroCustomized:mccmnc=20416
11-23 14:18:08.609  2462  4440 I CustomizedImsIcon:  isCustomizedBySkuId:isCustomized=false
11-23 14:18:08.609  2462  4440 D CustomizedImsIcon: getSimCount: simCount=1
11-23 14:18:08.610  2462  4440 I CustomizedImsIcon:  isWifiCallingAvailable: isImsRegistered is false
11-23 14:18:08.610  2462  4440 I CustomizedImsIcon:  isShowVoWiFiIcon: isAllowed=false
11-23 14:18:08.612  2462  4440 I CustomizedImsIcon:  isAllowShowVoLteIcon:OEM_ALLOW_SHOW_VOLTE_ICON_BOOL=false  phoneId=0
11-23 14:18:08.612  2462  4440 I CustomizedImsIcon:  isShowVolteIcon: isAllowed=false
11-23 14:18:08.613  2462  4440 I CustomizedImsIcon:  customizedImsIcon:--
11-23 14:18:08.615  2936  2936 I Telephony: reRegisterPstnPhoneAccount: subId: 1 - no change
11-23 14:18:08.615  2936  2936 D CallNotifier: updatePhoneStateListeners: update CF notifications.
11-23 14:18:08.616  2936  2936 I NotificationMgr: updateCfi: subId= 1, visible=N
11-23 14:18:08.616  2936  2936 I NotificationMgr: updateMwi(): subId 1 update to false
11-23 14:18:08.618  2462  2462 D KeyguardUpdateMonitor: received broadcast android.intent.action.SERVICE_STATE
11-23 14:18:08.618  2462  2462 V KeyguardUpdateMonitor: action android.intent.action.SERVICE_STATE serviceState={mVoiceRegState=0(IN_SERVICE), mDataRegState=0(IN_SERVICE), mChannelNumber=1656, duplexMode()=1, mCellBandwidths=[], mOperatorAlphaLong=Simpel, mOperatorAlphaShort=Simpel, isManualNetworkSelection=false(automatic), getRilVoiceRadioTechnology=14(LTE), getRilDataRadioTechnology=14(LTE), mCssIndicator=unsupported, mNetworkId=-1, mSystemId=-1, mCdmaRoamingIndicator=-1, mCdmaDefaultRoamingIndicator=-1, mIsEmergencyOnly=false, isUsingCarrierAggregation=false, mArfcnRsrpBoost=0, mNetworkRegistrationInfos=[NetworkRegistrationInfo{ domain=CS transportType=WWAN registrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[VOICE,SMS,VIDEO] cellIdentity=CellIdentityLte:{ mCi=70817281 mPci=66 mTac=527 mEarfcn=1656 mBands=[] mBandwidth=2147483647 mMcc=204 mMnc=16 mAlphaLong=Simpel mAlphaShort=Simpel mAdditionalPlmns={} mCsgInfo=null} voiceSpecificInfo=VoiceSpecificRegistrationInfo { mCssSupported=false mRoamingIndicator=1 mSystemIsInPrl=-1 mDefaultRoamingIndicator=-1} dataSpecificInfo=null nrState=**** rRplmn=20416 isUsingCarrierAggregation=false}, NetworkRegistrationInfo{ domain=PS transportType=WWAN registrationState=HOME roamingType=NOT_ROAMING accessNetworkTechnology=LTE rejectCause=0 emergencyEnabled=false availableServices=[DATA] cellIdentity=CellIdentityLte:{ mCi=70817281 mPci=66 mTac=527 mEarfcn=1656 mBands=[] mBandwidth=2147483647 mMcc=204 mMnc=16 mAlphaLong=Simpel mAlphaShort=Simpel mAdditionalPlmns={} mCsgInfo=null} voiceSpecificInfo=null dataSpecificInfo=android.telephony.DataSpecificRegistrationInfo :{ maxDataCalls = 20 isDcNrRestricted = false isNrAvailable = false isEnDcAvailable = false LteVopsSupportInfo :  mVopsSupport = 3 mEmcBearerSupport = 2 } nrState=**** rRplmn=20416 isUsingCarrierAggregation=false}], mNrFrequencyRange=0, mOperatorAlphaLongRaw=Simpel, mOperatorAlphaShortRaw=Simpel, mIsDataRoamingFromRegistration=false, mIsIwlanPreferred=false} subId=1
[...snipping a lot more similar logging...]

What could be wrong? Or at least, how can I further debug this?

If I am having performance problems, what tools can I use to identify where my performance lags are coming from? I have used a System Panel Task Manager , Android System Info , System Manager Free and some others but none of them have really identified the problem children. System Panel Task Manager came the closest with it's historical look at CPU and memory usage but it didn't let me look at *which apps* were using how much resources over time.

Recently I got a new Android smartphone and I want to know if it's necessary to update Android apps frequently. The reason for asking this is 1) Does updating Android apps reduce battery usage? 2) Should I update my apps if I don't have much internal memory? Will it slow down my phone if there isn't enough internal memory? 3) Will there be any (real) performance improvement if we update apps? I know that certain updates provide new features, bug fixes (I hope it means errors), and changes in the background/layout. Without considering the added feature, bug fixes, and layout, is it necessary to update? Also, each update takes a good amount of internal memory in my phone as well as a lot of valuable mobile data.

First of all, hopefully this is the right place to post this type of question - if it isn't, do let me know. I have a relatively new PC with 16 GB RAM, 10th Gen Core i3, 4 physical and 4 virtual cores (hyperthreading), I do not have an SSD. It runs Linux Mint and uses the KVM. The first year or so after buying my computer, the emulator worked great - it was fast and I was having a great time working on my apps. A couple of weeks ago, I realized that the emulator would occassionally become slower (around 50-60 percent, to be exact) for around a minute or two, before then becoming very fast for around 1-3 minutes. It's very strange, it goes like so: - Boot up emulator - Starts off blazingly fast - 2 minutes later it suddenly drops by around 50-60 percent in speed for around 1-2 minutes - Becomes blazingly fast again for some time Here is my emulator configuration stats: (I sometimes use AOSP emulators, but in this case I will just give an example of the Google API emulator.) This is incredibly frustrating - I use the emulator so many times, and I have a relatively new PC. PC info:

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  8
  On-line CPU(s) list:   0-7
Vendor ID:               GenuineIntel
  Model name:            Intel(R) Core(TM) i3-10105 CPU @ 3.70GHz
    CPU family:          6
    Model:               165
    Thread(s) per core:  2
    Core(s) per socket:  4
    Socket(s):           1
    Stepping:            3
    CPU max MHz:         4400.0000
    CPU min MHz:         800.0000
    BogoMIPS:            7399.70
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
                         a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss 
                         ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art
                          arch_perfmon pebs bts rep_good nopl xtopology nonstop_
                         tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cp
                         l vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1
                          sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsav
                         e avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault
                          epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced 
                         tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase t
                         sc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed a
                         dx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsa
                         ves dtherm ida arat pln pts hwp hwp_notify hwp_act_wind
                         ow hwp_epp md_clear flush_l1d arch_capabilities
Virtualization features: 
  Virtualization:        VT-x
Caches (sum of all):     
  L1d:                   128 KiB (4 instances)
  L1i:                   128 KiB (4 instances)
  L2:                    1 MiB (4 instances)
  L3:                    6 MiB (1 instance)
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-7
Vulnerabilities:         
  Itlb multihit:         KVM: Mitigation: Split huge pages
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Mitigation; Clear CPU buffers; SMT vulnerable
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
                          and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer
                          sanitization
  Spectre v2:            Mitigation; Enhanced IBRS, IBPB conditional, RSB fillin
                         g
  Srbds:                 Mitigation; Microcode
  Tsx async abort:       Not affected

Things I've tried: - allocate more RAM to the emu (5 GB and 8 GB) it actually felt slower and more incosistent with more ram - turn off other programs - different tweaks (none of which worked) I am looking for help as to how I can improve the emulator speed, as it feels as though you need some sort of NASA computer or 32 GB RAM Core i9 12th generation with an RTX 3090 these days to actually get **consistent** QEMU performance - very frustrating! Any help would be appreciated -- the only fault I can think of with my PC is that I'm using a HDD, which may or may not be the root cause of this issue.

I read that it is used on the computer. It has been coming up on my Samsung Galaxy S2. It is on at least 3 times at once and up to 7 or 8 at once. They are called kworker/0:1 through kworker/0:4 and/or kworker/u:1 through kworker/u:4 Occasionally, it comes up as using about 80 % of the CPU. My phone also regularly crashes as of recently. Could kworker be the problem? The virus I have also is kind of trojan-based and has popups when I restart my phone sometimes. Also, when my phone is asleep, and I turn it back on, it says kworker is using 100% of my CPU data.

Every once in a while my phone gets very sluggish when I'm multitasking, which is annoying but fine. Is there any way for me to set it so that the Dialer app takes priority over everything else, quickly stealing whatever resources it needs to run as fast as possible? Also, I am aware of the plethora of task killers available but I'm not interested unless it specifically allows me to set the dialer as a VIP or in some way make sure that the dialer gets first dibs on resources. Unrooted Moto Droid on 2.2

For Android devices, is internal storage memory typically faster, slower, or equal to microSD card storage? For example, let's take the Samsung Galaxy S10 Android phone. It comes in 128GB, 512GB, and 1TB storage configurations. It also has a single microSD card slot. The cost difference between the different tiers of integrated storage is slightly more than cost of a comparable microSD card, but not a big difference. Which will result in better performance: An Android device with only integrated storage, or one with an equivalent amount of storage in the form of integrated storage + a quality microSD card?

I have configured experiments to test which among 10 launched apps impacts performance the most. But I can't make an objective comparison, because if I launch the experiment twice with the same configuration, I get very different performance degradation, in terms of memory occupied and launch times. This is a piece of code from one of the workload scripts. I set the seed to always generate the same events, I wipe the cache at the end of each experiment and clean up the apps before starting another, yet in two experiments with the same settings I get a memory occupancy that grows up to three times faster in one than in the other. while true; do adb shell monkey -p com.android.chrome -s 1 --pct-appswitch 100 --ignore-crashes --ignore-timeouts --ignore-security-exceptions --monitor-native-crashes -v -v 1 sleep 1 adb shell monkey -p com.facebook.katana -s 1 --pct-appswitch 100 --ignore-crashes --ignore-timeouts --ignore-security-exceptions --monitor-native-crashes -v -v 1 sleep 1 adb shell monkey -p com.google.android.apps.maps -s 1 --pct-appswitch 100 --ignore-crashes --ignore-timeouts --ignore-security-exceptions --monitor-native-crashes -v -v 1 done Is there a way to get similar performance degradation in two experiments? Is it just me doing something wrong or is this something that can't be achieved because there are too many random factors at play?

I'm running stress tests on Android using Monkey to generate the workload. For the type of analysis I have to do, I need to generate the same sequence of events for each experiment. So, in every experiment, I always use the adb shell monkey command with the same seed. For instance: while true; do adb shell monkey -p com.android.chrome -s 1 --pct-appswitch 100 --ignore-crashes --ignore-timeouts --ignore-security-exceptions --monitor-native-crashes -v -v 1 sleep 1 adb shell monkey -p com.facebook.katana -s 1 --pct-appswitch 100 --ignore-crashes --ignore-timeouts --ignore-security-exceptions --monitor-native-crashes -v -v 1 sleep 1 adb shell monkey -p com.google.android.apps.maps -s 1 --pct-appswitch 100 --ignore-crashes --ignore-timeouts --ignore-security-exceptions --monitor-native-crashes -v -v 1 done The applications I launch are ten in total. However, looking at the measurement data, it seems to me that the system is stressed differently with each run. In particular, I find that the average launch time of applications degrades to a different extent in each experiment. Is everything normal or is it possible that I am doing something wrong? I realize that in different executions the system may respond differently. But by always setting the same seed (-s 1), shouldn't the extent of performance degradation be similar for each experiment?

My Sony Reader PRS-T1 based on Android 2.2 is acting funny. I had rooted it in the past but is now in the "original" state, upgraded with the latest official firmware. The problem is that many times, the unit becomes unresponsive. This happens after putting the unit on sleep and waking it again. The dictionary hangs, changing dictionaries hangs even worse and sometimes highlighting text as well (this makes the dictionary pop up. I managed to get logs and I found the following error messages, just after waking from sleepmode:

2013-01-22 17:15:06.391 W dalvikvm (2308:2308) [log_main    ] ERROR: Unable to find decl for native Lcom/sony/drbd/ebook/system/Identifier;.getProductName ()Ljava/lang/String;

2013-01-22 17:15:06.391 W dalvikvm (2308:2308) [log_main    ] ERROR: Unable to find decl for native Lcom/sony/drbd/ebook/system/Identifier;.getSkuName ()Ljava/lang/String;

2013-01-22 17:15:06.391 W dalvikvm (2308:2308) [log_main    ] ERROR: Unable to find decl for native Lcom/sony/drbd/ebook/system/Identifier;.getSerialNumber ()Ljava/lang/String;

2013-01-22 17:15:06.391 W dalvikvm (2308:2308) [log_main    ] ERROR: Unable to find decl for native Lcom/sony/drbd/ebook/system/Identifier;.getServiceId ()Ljava/lang/String;

2013-01-22 17:15:06.391 W dalvikvm (2308:2308) [log_main    ] ERROR: Unable to find decl for native Lcom/sony/drbd/ebook/system/Identifier;.getMacAddress ()Ljava/lang/String;

2013-01-22 17:15:06.391 W dalvikvm (2308:2308) [log_main    ] ERROR: Unable to find decl for native Lcom/sony/drbd/ebook/system/Identifier;.getPsn ()Ljava/lang/String;

2013-01-22 17:15:06.391 E JNIHelp (2308:2308) [log_main    ] RegisterNatives failed for 'com/sony/drbd/ebook/system/Identifier'

Any ideas on how to diagnose and restore my system?

I have a Galaxy S5 running 4.4.2. I am trying to send a text message to a certain contact. When I select their name from the list of messages, there is a 30 second delay. While typing, sometimes there will be a 10-15 second delay for each letter. If they send me a message while I'm trying to type, there will be a 30-60 second delay. Texting this person is so slow it is almost unusable. Other contacts are slow as well, but still usable. This is with no other apps running. My guess is that this could be caused by the lengthy text message history for this particular contact, but I doubt this is the case for the following reason: It seems extremely unlikely that I should be unable to store and display several megs of text on hardware made in 2014. I want to preserve this text history in any case, but I don't necessarily need to display it all on the screen at once. Thanks! Edit: I have tried clearing the cache, no effect.