This one is fun - I'm getting an FC every time an application requests keyboard input. If I hit the Google search icon on the top left of the home screen, it immediately FCs - that's what I'm using to test.
I downloaded aLogCat to the device via Google Play on my desktop, and ran it. Here is what I believe to be the relevant log section , from tapping the search icon, to re-entering aLogCat.
I believe the ClipboardEx service is causing the issue, possibly as an interference with another app I have installed - but I don't know what, or how to give you guys a list of apps installed without just typing each one.
This issue happened once to me, and a factory restore fixed it - two weeks later, and it's back. I'm not an experience Android guy, though I am a nerd and a developer. Surely this is something fixable. Does anyone have any thoughts on what could be causing this?
Code:
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=1, s=]
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/ActivityManager( 184): START {intent.toShortString} from pid 383
D/PowerManagerService( 184): acquireDVFSLockLocked : type : DVFS_MIN_LIMIT frequency : 1008000 uid : 1000 pid : 184 tag : ActivityManager
W/ActivityManager( 184): mDVFSLock.acquire()
D/Launcher.HomeFragment( 383): onPause
D/Launcher( 383): onPause
V/TaskCloserActivity( 3234): TaskCloserActivity onReceive()
D/KeyguardViewMediator( 184): setHidden false
D/ActivityManager( 184): Trying to launch applicationName
D/ControlPanelRemoteService( 3246): onDestroy()
D/OpenGLRenderer( 383): Flushing caches (mode 1)
D/dalvikvm( 3157): GC_CONCURRENT freed 259K, 5% free 6784K/7111K, paused 2ms+3ms
D/KeyguardViewMediator( 184): setHidden false
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/libEGL ( 3157): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 3157): Enabling debug mode 0
E/ClipboardServiceEx( 3157): Had failed to obtaining clipboardEx service.
D/AndroidRuntime( 3157): Shutting down VM
W/dalvikvm( 3157): threadid=1: thread exiting with uncaught exception (group=0x40bb01f8)
E/AndroidRuntime( 3157): FATAL EXCEPTION: main
E/AndroidRuntime( 3157): java.lang.NullPointerException
E/AndroidRuntime( 3157): at android.sec.clipboard.ClipboardExManager.updateData(ClipboardExManager.java:241)
E/AndroidRuntime( 3157): at android.widget.EditText.onFocusChanged(EditText.java:134)
E/AndroidRuntime( 3157): at android.view.View.handleFocusGainInternal(View.java:3727)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5420)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2113)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5370)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1598)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2459)
E/AndroidRuntime( 3157): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3157): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3157): at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
E/AndroidRuntime( 3157): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 184): Force finishing activity com.google.android.googlequicksearchbox/.SearchActivity
E/android.os.Debug( 184): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
I/dumpstate( 3272): begin
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{423f3fe0 com.google.android.googlequicksearchbox/.SearchActivity}
W/PowerManagerService( 184): Timer 0x7->0x3|0x0
I/PowerManagerService( 184): Ulight 7->3|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 0
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/InputReader( 184): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.70 ]
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/PowerManagerService( 184): Ulight 3->7|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 140
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
D/VoldCmdListener( 89): asec list
D/VoldCmdListener( 89): CommandListener::AsecCmd::runCommand -> --
I/dumpstate( 3272): done
D/KeyguardViewMediator( 184): setHidden false
D/Launcher( 383): onResume
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/myTest ( 383): [MonthTheme] onResume!!
D/KeyguardViewMediator( 184): setHidden false
D/myTest ( 383): firstDayOfWeek = -1
I/power ( 184): *** release_dvfs_lock : lockType : 1
D/myTest ( 383): [MonthView] updateView.mStartDay: 1
D/DEFERED_APP_VISIBILITY( 184): tweaking closing app
D/PowerManagerService( 184): releaseDVFSLockLocked : all DVFS_MIN_LIMIT are released
W/ActivityManager( 184): mDVFSLock.release()
D/Launcher.HomeFragment( 383): onResume
I've now removed all downloaded applications from my Tab. No dice.
I'm going to see if I can dig up any more logs, then reset it I guess.
I've discovered that copying something to the clipboard also causes the FC. This is definitely an issue with TouchWiz's clipboard as far as I can figure out.
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
jamesd86 said:
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
It works for me, too, until the whole thing starts crashing, lol.
I reset to factory and re-installed all my stuff; it seems to be working now. I guess it's Samsung's way of reminding me to keep regular backups...
My tab crashed and then this same exact thing started happening. The logs mentioned ClipboardServiceEx.
I am rooted, so I started an adb shell and found that /data/clipboard has all the persistent clipboard entries (I love that feature by the way).
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
This fixed it, although it cleared all my "held" info in the clipboard. A small price to pay. If you really had to, you could probably fish in /data/oldclipboard for it. Of course, now I will go delete oldclipboard.
Hope that helps someone.
Thanks for that info, you never know!
Pp.
Transmitted from another galaxy with an Infected P-5113.
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
dorkmo said:
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
Click to expand...
Click to collapse
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
wd5gnr said:
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
Click to expand...
Click to collapse
ok newbie here with samsung tabs having same problem, how do you boot into recovery and do an adb shell ? can see above how to clear the clipboard directory and i dont want to factory reset too hard to reload all the crap on ....
thanks
I had the same problem, I do not want to root my device, but I like to use the standard key board from Sumsung. I send a a-mail to a lot of dutch companies (resellers) to tell them about the problem. I think that Sansung must make a firware update to solve this problem. I what to ask all people who have problems with the keyboard to e-mail Samsung and there reseller to put preasure on Samsung to make a firmware.
I use a work a round, I use a 3e party keyboard untill Samsung makes a firmware update.
wd5gnr said:
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
Hope that helps someone.
Click to expand...
Click to collapse
YEZZZZZ THANK YOU VERY MUCH!!!:good::laugh:
This worked perfectly on my Samsung Galaxy Tab 2 10.1 (P5110)
Thanks wd5gnr for the solution, worked very well!
Regards.
Glad it helped. I noticed someone asked earlier for more details.
There are plenty of root tutorials here. As for installing ADB there are a few ways to go and it depends on your PC's OS and if you want to get someone's simplified package or not. Read: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and the comments on that page too. If you google something like "installing ADB" you should find lots of help.
Once you have adb installed and can get to a shell, you should be good with my earlier instructions.
I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Good work, Khizar. A very handy and usefull guide. Thanks.
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Pierre118 said:
Good work, Khizar. A very handy and usefull guide. Thanks.
Click to expand...
Click to collapse
daxgirl said:
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Thank you both but JFYI this isn't my work. I shared this guide on my previous phone and since it's so good and there is ALOT of need I shared it here as well. I mentioned that in the OP.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Due to the lack of mods, trolls can ruin the XDA forum's. Don't feed them...Instead report them.
Click to expand...
Click to collapse
daxgirl said:
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
agree !
Khizar said:
Thank you both but JFYI this isn't my work. I shared this guide on my previous phone and since it's so good and there is ALOT of need I shared it here as well. I mentioned that in the OP.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Though not pure your own work, but noobies will need it, especially to send a log back to devs to know what is the problem.
And it's a good thing to share here.
:good:
antique_sonic said:
agree !
Though not pure your own work, but noobies will need it, especially to send a log back to devs to know what is the problem.
And it's a good thing to share here.
:good:
Click to expand...
Click to collapse
Appreciate the support brother...
Sent From My SM-G900F-Morphed SM-N9005 With XNote Goodness To All You Wonder Nobodies!!
Due to the lack of mods, trolls can ruin the XDA forum's. Don't feed them...Instead report them.
Click to expand...
Click to collapse
Khizar said:
Appreciate the support brother...
Sent From My SM-G900F-Morphed SM-N9005 With XNote Goodness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
No worries Bro.
Sent from somewhere under the sky, at the corner of this rounded earth.
Great idea bro. We finally have a proper logcat thread for our Note3. ?
Sent from my SM-G900F using Tapatalk
fahadali2315 said:
Great idea bro. We finally have a proper logcat thread for our Note3. ?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
:good:
I would like to know what I need do for an old app to work on Android Pie and how can I do that too.
The developer abandoned the app but it is very useful to me. In my last smartphone (android Lollipop 5.1.1) the app worked well but in my new smartphone (android Pie 9) it installs but when I open it immediatlly is showed a message that it stoped and need to be closed.
I use "APK Easy Tool v1.56 Portable" to edit apks but I don't know what exactly to do.
I thought that was about this message: "This app was built for an older version of Android and may not work properly. Try checking for updates, or contact the developer."
So, I changed the API version to 28 and the message disappeared but the stop and close app problem continue.
Thank you for any help.
robrazil said:
I would like to know what I need do for an old app to work on Android Pie and how can I do that too.
The developer abandoned the app but it is very useful to me. In my last smartphone (android Lollipop 5.1.1) the app worked well but in my new smartphone (android Pie 9) it installs but when I open it immediatlly is showed a message that it stoped and need to be closed.
I use "APK Easy Tool v1.56 Portable" to edit apks but I don't know what exactly to do.
I thought that was about this message: "This app was built for an older version of Android and may not work properly. Try checking for updates, or contact the developer."
So, I changed the API version to 28 and the message disappeared but the stop and close app problem continue.
Thank you for any help.
Click to expand...
Click to collapse
Did you boot to recovery and wipe the cache partition after installing the modified app?
This isn't exactly what you are looking for, but it is very close, you just need to modify the method a little to go from Lollipop to Pie the way this video describes going from Oreo to Nougat. What you want is to port your older app to work with newer android instead of porting a newer app to work with older android as the video describes.
https://m.youtube.com/watch?v=kck1EyhFDm4
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Did you boot to recovery and wipe the cache partition after installing the modified app?
Click to expand...
Click to collapse
Thank you for answer me but my smartphone isn't root and haven't options on recovery boot mode.
This isn't exactly what you are looking for, but it is very close, you just need to modify the method a little to go from Lollipop to Pie the way this video describes going from Oreo to Nougat. What you want is to port your older app to work with newer android instead of porting a newer app to work with older android as the video describes.
https://m.youtube.com/watch?v=kck1EyhFDm4
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I saw the video.
Like I said, had already changed the API version to 28 using the "APK Easy Tool v1.56 Portable" and editing the apktool.yml file on lines:
PHP:
sdkInfo:
minSdkVersion: '26'
targetSdkVersion: '28'
Both lines had number '8'.
Even so, as explained in the video, I downloaded and installed the Apk Editor PRO app and following step by step, changing "Minimum SDK Version" from 8 to 26 and "Target SDK Version" from 8 to 29, but the same problem continues.
When I press the app icon, it not open and is showed this popup message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, only change the SDK version isn't solving.
I don't know if structure of folders or anything else is different between apps for Lollipop and Pie that block to be installed, because I have 2 others old app that I installed and despite the old app alert message they are working rigth.
robrazil said:
Thank you for answer me but my smartphone isn't root and haven't options on recovery boot mode.
I saw the video.
Like I said, had already changed the API version to 28 using the "APK Easy Tool v1.56 Portable" and editing the apktool.yml file on lines:
PHP:
sdkInfo: minSdkVersion: '26' targetSdkVersion: '28'
Both lines had number '8'.
Even so, as explained in the video, I downloaded and installed the Apk Editor PRO app and following step by step, changing "Minimum SDK Version" from 8 to 26 and "Target SDK Version" from 8 to 29, but the same problem continues.
When I press the app icon, it not open and is showed this popup message:
View attachment 4964951
So, only change the SDK version isn't solving.
I don't know if structure of folders or anything else is different between apps for Lollipop and Pie that block to be installed, because I have 2 others old app that I installed and despite the old app alert message they are working rigth.
Click to expand...
Click to collapse
There is a PC version of APKtool that can be used to modify the apk file, you don't need root or apps that use root or custom recovery to achieve this.
Yes, each android version has slightly different partition structure, you need to edit the apk file so that it references the correct partitions/folders and files to find and use the other software resources on your devive that it needs.
You just need to modify the apk file then transfer it to your phone's internal storage then install it using your phones file manager app. You will have to enable the "unknown sources" setting in system settings.
Sent from my SM-S767VL using Tapatalk
There is a PC version of APKtool that can be used to modify the apk file, you don't need root or apps that use root or custom recovery to achieve this.
Click to expand...
Click to collapse
Thank you but like I said, already use "APK Easy Tool v1.56 Portable" for windows:
https://forum.xda-developers.com/an...tool-apk-easy-tool-v1-02-windows-gui-t3333960
You just need to modify the apk file then transfer it to your phone's internal storage then install it using your phones file manager app. You will have to enable the "unknown sources" setting in system settings.
Click to expand...
Click to collapse
I already did some small modifications in some apps too.
Yes, each android version has slightly different partition structure, you need to edit the apk file so that it references the correct partitions/folders and files to find and use the other software resources on your devive that it needs.
Click to expand...
Click to collapse
That is the point.
I think some questions need to be answered to resolve this issue:
1- What is really happening to block, to stop the application from running?
2- What needs to be changed in the application?
3- How can changes be made?
4- This webpage content could help?
https://developer.android.com/about/versions/pie/android-9.0-migration
5- There is some windows program where an android app can be installed, choosing the sistem android who do you want to install it (lollipop, marshmallow, Pie, etc), and is showed the app errors that to be fix for it work on the android version choosen?
Thanks for any help.
I tested the apk in virtual android of webpage https://appetize.io/ and it worked in virtual Android 6.0, 7.1, 8.1 until on android 10. Only android 9.0 didn't work. I don't belive that. Seems a joke.
On android 10, after install, is showed the permission screen asking to give it to the camera and the storage. After press "next", the app is open and works right. I tried changing the permissions on Android 9 but didn't work to make the app opening.
Does anyone have any idea what might be happening?
This app was created to SDK 8 (android 2.2 - Froyo)
I don't know if that can be help but below I pasted the debug log of there. I simulated in Android 4.4, 9.0 and 10, to serve as comparison between the android versions. In 4.4 and 10 versions worked, but didn't on 9 version:
Code:
[B][COLOR="Red"]Log messages will follow once session has started... [U](ANDROID 4.4)[/U][/COLOR][/B]
W/GAV2 ( 2986): Thread[main,5,main]: Need to call initialize() and be in fallback mode to start dispatch.
E/SQLiteLog( 2986): (1) no such table: MOEDA
E/SQLiteLog( 2986): (1) no such table: boletos
D/dalvikvm( 2986): GC_CONCURRENT freed 176K, 9% free 3443K/3780K, paused 0ms+0ms, total 2ms
D/dalvikvm( 2986): GC_FOR_ALLOC freed 1K, 9% free 3441K/3780K, paused 4ms, total 4ms
I/dalvikvm-heap( 2986): Grow heap (frag case) to 5.931MB for 2536932-byte allocation
D/dalvikvm( 2986): GC_FOR_ALLOC freed <1K, 6% free 5919K/6260K, paused 3ms, total 3ms
D/dalvikvm( 2986): GC_CONCURRENT freed 0K, 6% free 5919K/6260K, paused 1ms+1ms, total 3ms
D/dalvikvm( 2986): GC_FOR_ALLOC freed 2K, 6% free 6087K/6420K, paused 3ms, total 3ms
I/dalvikvm-heap( 2986): Grow heap (frag case) to 7.287MB for 1249292-byte allocation
D/dalvikvm( 2986): GC_CONCURRENT freed 1K, 5% free 7306K/7644K, paused 2ms+1ms, total 5ms
W/ContextImpl( 2986): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:517 com.a.a.a.d.<init>:-1 br.com.magic.boletos.BoletosActivity.onResume:-1
W/ContextImpl( 2986): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:517 br.com.magic.boletos.b.a.d.a:-1 com.a.a.a.d.<init>:-1
D/ ( 2986): HostConnection::get() New Host Connection established 0xb84724c0, tid 2986
I/GAV2 ( 2986): Thread[GAThread,5,main]: connecting to Analytics service
W/ContextImpl( 2986): Implicit intents with startService are not safe: Intent { act=com.google.android.gms.analytics.service.START (has extras) } android.content.ContextWrapper.bindService:517 com.google.analytics.tracking.android.AnalyticsGmsCoreClient.b:-1 com.google.analytics.tracking.android.GAServiceProxy.j:-1
I/GAV2 ( 2986): Thread[GAThread,5,main]: connect: bindService returned true for Intent { act=com.google.android.gms.analytics.service.START (has extras) }
I/GAV2 ( 2986): Thread[GAThread,5,main]: No campaign data found.
D/GAV2 ( 2986): Thread[main,5,main]: service connected, binder: [email protected]
D/GAV2 ( 2986): Thread[main,5,main]: bound to service
I/GAV2 ( 2986): Thread[main,5,main]: Connected to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
[B][COLOR="red"]Log messages will follow once session has started... [U](ANDROID 9.0)[/U][/COLOR][/B]
W/m.magic.boleto( 5064): Unexpected CPU variant for X86 using defaults: x86
I/m.magic.boleto( 5064): The ClassLoaderContext is a special shared library.
W/m.magic.boleto( 5064): Suspending all threads took: 15.752ms
W/GAV2 ( 5064): Thread[main,5,main]: Need to call initialize() and be in fallback mode to start dispatch.
E/SQLiteLog( 5064): (1) no such table: MOEDA
E/SQLiteLog( 5064): (1) no such table: boletos
E/SQLiteLog( 5064): (1) no such table: MOEDA
W/ContextImpl( 5064): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:698 com.a.a.a.d.<init>:30 br.com.magic.boletos.BoletosActivity.onResume:5
W/ContextImpl( 5064): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:698 br.com.magic.boletos.b.a.d.a:31 com.a.a.a.d.<init>:55
E/SQLiteLog( 5064): (1) no such table: FAVORECIDO
E/SQLiteLog( 5064): (1) no such table: BOLETO
D/AndroidRuntime( 5064): Shutting down VM
E/AndroidRuntime( 5064): FATAL EXCEPTION: main
E/AndroidRuntime( 5064): Process: br.com.magic.boletos, PID: 5064
E/AndroidRuntime( 5064): java.lang.RuntimeException: Unable to resume activity {br.com.magic.boletos/br.com.magic.boletos.BoletosActivity}: android.database.sqlite.SQLiteException: no such table: BOLETO (code 1 SQLITE_ERROR): , while compiling: SELECT _id , vencimento FROM BOLETO GROUP BY vencimento ORDER BY vencimento ASC
E/AndroidRuntime( 5064): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3784)
E/AndroidRuntime( 5064): at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3816)
E/AndroidRuntime( 5064): at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
E/AndroidRuntime( 5064): at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
E/AndroidRuntime( 5064): at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
E/AndroidRuntime( 5064): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1808)
E/AndroidRuntime( 5064): at android.os.Handler.dispatchMessage(Handler.java:106)
E/AndroidRuntime( 5064): at android.os.Looper.loop(Looper.java:193)
E/AndroidRuntime( 5064): at android.app.ActivityThread.main(ActivityThread.java:6669)
E/AndroidRuntime( 5064): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 5064): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E/AndroidRuntime( 5064): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
E/AndroidRuntime( 5064): Caused by: android.database.sqlite.SQLiteException: no such table: BOLETO (code 1 SQLITE_ERROR): , while compiling: SELECT _id , vencimento FROM BOLETO GROUP BY vencimento ORDER BY vencimento ASC
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:903)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:514)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:58)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:37)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:46)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1408)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1347)
E/AndroidRuntime( 5064): at br.com.magic.boletos.d.f.a(Unknown Source:83)
E/AndroidRuntime( 5064): at br.com.magic.boletos.d.f.a(Unknown Source:136)
E/AndroidRuntime( 5064): at br.com.magic.boletos.BoletosActivity.b(Unknown Source:156)
E/AndroidRuntime( 5064): at br.com.magic.boletos.BoletosActivity.onResume(Unknown Source:10)
E/AndroidRuntime( 5064): at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1412)
E/AndroidRuntime( 5064): at android.app.Activity.performResume(Activity.java:7292)
E/AndroidRuntime( 5064): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3776)
E/AndroidRuntime( 5064): ... 11 more
I/Process ( 5064): Sending signal. PID: 5064 SIG: 9
[COLOR="red"][B]Log messages will follow once session has started... [U](ANDROID 10)[/U][/B][/COLOR]
W/m.magic.boleto( 6832): Unexpected CPU variant for X86 using defaults: x86
I/m.magic.boleto( 6832): The ClassLoaderContext is a special shared library.
W/GAV2 ( 6832): Thread[main,5,main]: Need to call initialize() and be in fallback mode to start dispatch.
W/main ( 6832): type=1400 audit(0.0:73): avc: granted { read } for name="u:object_r:net_dns_prop:s0" dev="tmpfs" ino=6662 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:net_dns_prop:s0 tclass=file app=com.ustwo.lwp
E/SQLiteLog( 6832): (1) no such table: MOEDA
E/SQLiteLog( 6832): (1) no such table: boletos
W/ContextImpl( 6832): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:705 com.a.a.a.d.<init>:30 br.com.magic.boletos.BoletosActivity.onResume:5
W/ContextImpl( 6832): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:705 br.com.magic.boletos.b.a.d.a:31 com.a.a.a.d.<init>:55
W/Gralloc3( 6832): mapper 3.x is not supported
D/HostConnection( 6832): createUnique: call
D/HostConnection( 6832): HostConnection::get() New Host Connection established 0xd47f4380, tid 6832
D/HostConnection( 6832): HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_YUV420_888_to_NV21 ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_gles_max_version_2
D/eglCodecCommon( 6832): allocate: Ask for block of size 0x1000
D/eglCodecCommon( 6832): allocate: ioctl allocate returned offset 0x3ffffa000 size 0x2000
D/eglCodecCommon( 6832): allocate: Ask for block of size 0x752000
D/eglCodecCommon( 6832): allocate: ioctl allocate returned offset 0x3ff0b2000 size 0x753000
W/System ( 6832): A resource failed to call close.
W/System ( 6832): A resource failed to call close.
I/GAV2 ( 6832): Thread[GAThread,5,main]: connecting to Analytics service
W/ContextImpl( 6832): Implicit intents with startService are not safe: Intent { act=com.google.android.gms.analytics.service.START (has extras) } android.content.ContextWrapper.bindService:705 com.google.analytics.tracking.android.AnalyticsGmsCoreClient.b:41 com.google.analytics.tracking.android.GAServiceProxy.j:55
D/GAV2 ( 6832): Thread[main,5,main]: service connected, binder: [email protected]
D/GAV2 ( 6832): Thread[main,5,main]: bound to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: connect: bindService returned true for Intent { act=com.google.android.gms.analytics.service.START (has extras) }
I/GAV2 ( 6832): Thread[main,5,main]: Connected to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: No campaign data found.
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
hello, you have source code or just apk? seems it has a bug appears as it's db sql excute on android 9. may be it doesn't adapter android 9.
if you are a developer and you have the source code(only apk can use decompile tool get a project code), you can fix it, but if you are not a developer, may be contact to the owner developer is the only way to help you!
@walker ice
Hi.
Thank you for answer me.
I am not a developer. I am "curiousloper" (curious + developer)... kkkk.
Well... I have only the apk. I spoke with the app developer (company) and they said that this app was abandoned a long time ago.
This app is a barcode reader that I use to pay my bank slips.
The app is installed in mobile and the server program in windows.
When the app read the barcode, it send that to PC where cursor was marked, in this case to my internet bank page.
I tested others apps similar but they read wrong the barcode.
I used the "APK Easy Tool v1.56 Portable" for window to decompile the apk. I changed the SDK to 28 but the issue continues.
I saw in some posts talking about the possible problem with data base bank on android pie and to rename the file adding .db in the end would solve but I did it too and no worked to me.
I searched for a solution but I didn't find.
Can be in my face but like I am not a developer, I cannot see the solution.
I don't need that someone do it for me.
I only need someone that look the apk and tell me what I should to do, what I need to change in apk to do it works on android pie.
I want to learn how to do.
Perhaps the app has two or more android projects.
Would you like to ask the app developer for the source code as the company has abandoned this app?
If you have the source code, you can check and modify it with ease in Android Studio by yourself.
Sorry. Duplication of post.
robrazil said:
@walker ice
Hi.
Thank you for answer me.
I am not a developer. I am "curiousloper" (curious + developer)... kkkk.
Well... I have only the apk. I spoke with the app developer (company) and they said that this app was abandoned a long time ago.
This app is a barcode reader that I use to pay my bank slips.
The app is installed in mobile and the server program in windows.
When the app read the barcode, it send that to PC where cursor was marked, in this case to my internet bank page.
I tested others apps similar but they read wrong the barcode.
I used the "APK Easy Tool v1.56 Portable" for window to decompile the apk. I changed the SDK to 28 but the issue continues.
I saw in some posts talking about the possible problem with data base bank on android pie and to rename the file adding .db in the end would solve but I did it too and no worked to me.
I searched for a solution but I didn't find.
Can be in my face but like I am not a developer, I cannot see the solution.
I don't need that someone do it for me.
I only need someone that look the apk and tell me what I should to do, what I need to change in apk to do it works on android pie.
I want to learn how to do.
Click to expand...
Click to collapse
can you provider me an apk download url? I will have a try and tell you whether there a way to make it work in android pie if possible
walker ice said:
can you provider me an apk download url? I will have a try and tell you whether there a way to make it work in android pie if possible
Click to expand...
Click to collapse
Of course yes.
Only to have an idea, I had to access the webcache (https://archive.org/) of the developer page of 2011 to download the apk file and the server program for windows. So, I upload the zip file to gdrive:
https://drive.google.com/open?id=0B_3XOrUkmIBMQlZhZExRTGZYVDQ
Thank you so much.
robrazil said:
Of course yes.
Only to have an idea, I had to access the webcache (https://archive.org/) of the developer page of 2011 to download the apk file and the server program for windows. So, I upload the zip file to gdrive:
https://drive.google.com/open?id=0B_3XOrUkmIBMQlZhZExRTGZYVDQ
Thank you so much.
Click to expand...
Click to collapse
hello robrazil, after I have a try, event decompile, it still have many crash for the project is too old(like some library of it, as zxing...) and the owner's progurad do well, so may be only the owner can help you but if they abandon it will be very hard to make it work in android pie. Sorry for not being able to help you
walker ice said:
hello robrazil, after I have a try, event decompile, it still have many crash for the project is too old(like some library of it, as zxing...) and the owner's progurad do well, so may be only the owner can help you but if they abandon it will be very hard to make it work in android pie. Sorry for not being able to help you
Click to expand...
Click to collapse
I appreciated your help.
What I don't understand is how is that works on Android 5, 6, 7, 8.1 and 10, but only 9 not ?
I used the virtual android on website https://appetize.io/ to test the installation and to open the app in each android version, and only in the PIE version it not opened.
What the PIE version has so different of others versions, including the 10 ?
Because the app open on the version 10 too.
For now, I am using the app in my old smartphone with Lollipop android.
robrazil said:
I appreciated your help.
What I don't understand is how is that works on Android 5, 6, 7, 8.1 and 10, but only 9 not ?
I used the virtual android on website https://appetize.io/ to test the installation and to open the app in each android version, and only in the PIE version it not opened.
What the PIE version has so different of others versions, including the 10 ?
Because the app open on the version 10 too.
For now, I am using the app in my old smartphone with Lollipop android.
Click to expand...
Click to collapse
Gotta be something to do with API or sdk/kernel version.
Sent from my SM-S767VL using Tapatalk
robrazil said:
I appreciated your help.
What I don't understand is how is that works on Android 5, 6, 7, 8.1 and 10, but only 9 not ?
I used the virtual android on website https://appetize.io/ to test the installation and to open the app in each android version, and only in the PIE version it not opened.
What the PIE version has so different of others versions, including the 10 ?
Because the app open on the version 10 too.
For now, I am using the app in my old smartphone with Lollipop android.
Click to expand...
Click to collapse
android pie add some "Non-SDK interface restrictions" may effect the there part method, and it's update in android 10 as google introduct below:
"To help ensure app stability and compatibility, the platform started restricting which non-SDK interfaces your app can use in Android 9 (API level 28). Android 10 includes updated lists of restricted non-SDK interfaces based on collaboration with Android developers and the latest internal testing. Our goal is to make sure that public alternatives are available before we restrict non-SDK interfaces."
so may be android the app not work in android pie, it cause by the Non-SDK interface restrictions.
About API or SDK/kernel or "Non-SDK interface restrictions", it has nothing to do with the old lines below, of apktool.yml file that I changed to
PHP:
sdkInfo:
minSdkVersion: '26'
targetSdkVersion: '28'
Has it ?
robrazil said:
About API or SDK/kernel or "Non-SDK interface restrictions", it has nothing to do with the old lines below, of apktool.yml file that I changed to
PHP:
sdkInfo: minSdkVersion: '26' targetSdkVersion: '28'
Has it ?
Click to expand...
Click to collapse
I'm not sure that editing the apk to change those lines isn't quite enough. I would say that you'd have to recompile the apk using the needed SDK version so that the apk itself is compiled correctly for that SDK version.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
I'm not sure that editing the apk to change those lines isn't quite enough. I would say that you'd have to recompile the apk using the needed SDK version so that the apk itself is compiled correctly for that SDK version.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you for answer me.
Well... if decompile the apk, to change the "minSdkVersion" and the "targetSdkVersion" informations to 26 and 28 respectively and recompile the apk again is not "recompile the apk using the needed SDK version", so, what means exactly "recompile the apk using the needed SDK version" and how can I do that ?
Where can I find something about "recompile the apk using the needed SDK version" to do that ?