I can't update to 1.5 on any build, I can not figure it out. I wiped before going from Lucid's JFRC33 mod to trying JF ADP1.5 everything installed and booted fine, but as soon as I reboot it gets stuck at the first flash screen. I wiped and tried the update about 3 more times and same thing. I installed JF's RC33 and everything worked, I wiped and tried to update to 1.5 again and same thing, it boots, syncs and once i reboot thats it, it doesnt ever boot. Installed ADP1.1 from JF and everything worked, tried the update and same thing after reboot it doesnt boot. I installed the radio before I ever did anything. I have tried Haykuro's and am getting the same problem. I'd love to be able to update to 1.5
I went into adb and did adb logcat, its looping the same thing. If I wipe it boots, I sign into google, it syncs, one I reboot it never boots it just repeats this over and over in adb:
D/AndroidRuntime( 415):
D/AndroidRuntime( 415): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 415): CheckJNI is OFF
D/AndroidRuntime( 415): --- registering native functions ---
I/Zygote ( 415): Preloading classes...
D/dalvikvm( 415): GC freed 763 objects / 42128 bytes in 7ms
D/dalvikvm( 415): GC freed 278 objects / 17200 bytes in 6ms
D/dalvikvm( 415): GC freed 208 objects / 12664 bytes in 8ms
D/dalvikvm( 415): Trying to load lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Added shared lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Trying to load lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
D/dalvikvm( 415): Trying to load lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
D/dalvikvm( 415): Trying to load lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
D/dalvikvm( 415): GC freed 462 objects / 29168 bytes in 11ms
D/dalvikvm( 415): GC freed 3579 objects / 171120 bytes in 26ms
D/dalvikvm( 415): GC freed 11306 objects / 400568 bytes in 41ms
D/dalvikvm( 415): GC freed 10462 objects / 438128 bytes in 48ms
D/dalvikvm( 415): GC freed 11013 objects / 460640 bytes in 54ms
D/dalvikvm( 415): GC freed 14354 objects / 505928 bytes in 62ms
D/dalvikvm( 415): GC freed 11294 objects / 480800 bytes in 58ms
D/dalvikvm( 415): GC freed 5966 objects / 250056 bytes in 49ms
D/dalvikvm( 415): GC freed 343 objects / 36704 bytes in 44ms
W/dalvikvm( 415): Exception Ljava/lang/IndexOutOfBoundsException; thrown during Landroid/text/Html$HtmlParser;.<clinit>
D/AndroidRuntime( 415): Shutting down VM
W/dalvikvm( 415): threadid=3: thread exiting with uncaught exception (group=0x4000fe70)
D/dalvikvm( 415): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 415): DestroyJavaVM shutting VM down
D/dalvikvm( 415): VM cleaning up
D/dalvikvm( 415): LinearAlloc 0x0 used 1189684 of 4194304 (28%)
D/skia ( 415): purging 6K from font cache [1 entries]
Click to expand...
Click to collapse
Anyone have any ideas?
Update: I'm not sure if this is the real cause cuz I am scared to reboot, but I did notice something new. I reloaded all my apps and crap, and tried to update to 1.5 again. Since I have debian on my SD card, the script that does all the mounting, had a broken link to the /system/sd when I looked did busybox df -h the mounting for the /system/sd was /dev/block/mmcblk0p2 where as LucidREM's mod had it as /dev/mmcblk0p2. Does this seem like a reasonable cause to anyone?
Update: The Apps to SD was the cause. When I would wipe and install ADP1.5 after it booted, the ext2 was mounted /dev/mmcblk0p2, regardless of if I linked or not, the phone would never boot. After doing my backup and getting back al my files form Nandroid and having Lucid's JF RC33 Mod installed, I updated with NO wipe and connected the phone through adb and watched the logcat as it moved everything to /dev/block/mmcblk0p2. I rebooted and everything still works great
This sounds like it might be related to the problem I posted about here:
http://forum.xda-developers.com/showthread.php?t=511454
The "works on first boot but then breaks for subsequent boots" behavior seems similar, and I've also run into looping on "AndroidRuntime START" a couple times - although a battery pull + reboot has always gotten me out of it.
What happens if you go from, say JFv1.43 to JFv1.5 with no intermediate wipe?
-copy jfv1.42_rc33.zip from Jesus Freke to sd card how update.zip
-Turn off
-press home and Red
-wipe and install jfv1.42_rc33
-when wake up
copy jfv1.50_adp1.5 to sd card how update.zip
turn off
press home and red
install jfv1.50_adp1.5
wait and go
satru said:
-copy jfv1.42_rc33.zip from Jesus Freke to sd card how update.zip
-Turn off
-press home and Red
-wipe and install jfv1.42_rc33
-when wake up
copy jfv1.50_adp1.5 to sd card how update.zip
turn off
press home and red
install jfv1.50_adp1.5
wait and go
Click to expand...
Click to collapse
Ive done this, thats the problem, after the update it will boot into adp1.5 but once i reboot again, it just goes into an endless loop with the adb logcat message I posted above.
Now that I loaded the nandroid backup of my RC33 I can try without a wipe and see if it will work, At this point I'm willing to try anything
jairomeo said:
Ive done this, thats the problem, after the update it will boot into adp1.5 but once i reboot again, it just goes into an endless loop with the adb logcat message I posted above.
Now that I loaded the nandroid backup of my RC33 I can try without a wipe and see if it will work, At this point I'm willing to try anything
Click to expand...
Click to collapse
Wipe the SD card after the update. So it doesn't have any update files or recovery.img files in it's base directory.
SOLDIER [X] said:
Wipe the SD card after the update. So it doesn't have any update files or recovery.img files in it's base directory.
Click to expand...
Click to collapse
Unfortunately it has done it with a blank SD card also . Thats why Im hoping maybe someone knows from the logcat what is actually the issue
W/dalvikvm( 415): Exception Ljava/lang/IndexOutOfBoundsException; thrown during Landroid/text/Html$HtmlParser;.<clinit>
D/AndroidRuntime( 415): Shutting down VM
W/dalvikvm( 415): threadid=3: thread exiting with uncaught exception (group=0x4000fe70)
Click to expand...
Click to collapse
Looks like a HTMLParser fails and kill the VM. Not sure where that HTML file is. Have you tried wiping out the cache ?
lacostej said:
Looks like a HTMLParser fails and kill the VM. Not sure where that HTML file is. Have you tried wiping out the cache ?
Click to expand...
Click to collapse
I wiped the phone completely and have had no luck. After I wipe it will boot and I can sign into my account, it will sync and all is well, but whenever I decide to turn off the phone, thats when it no longer boots back up. Ive had adp1.5 running for 5+ hours, but after a reboot it happens. I even texted this by skipping the sign in and just rebooting after the update is complete and it still does the same thing
I'm running Nexus 5 stock ROM (latest Kitkat), rooted with TWRP recovery. I only have the following additional things I would consider "modifications":
Xposed installed with the following modules:
- Advanced power menu
- Exchange security bypass
When I boot up my phone, I am unable to turn my screen off at my lock screen by pressing my power button. It simply does nothing. If I set my phone on the table, the screen will not time out even though I have one set. My lock screen uses the pin pad. Another oddity I notice is that I have bluetooth enabled but it does not appear in the status bar until I unlock the screen. I also have a weather app that has temperature in the status bar, and that does not appear to be loaded until I unlock. So it seems that the OS is only partially loaded.
I attempted to look at logcats but I don't see anything useful. As I press the power button I do not see any feedback from logcat output at lockscreen after boot (I assume this is bad). Even though TAPPING power button does not turn off the screen, HOLDING power does bring up the power menu (wtf?).
Anyone know what is going on? I was skeptical to provide logcat data here since I am afraid it has personal info in it. I am not an android dev/logcat expert so please provide guidance. Thanks.
I have tried disabling Xposed and uninstalling the modules, but I still experience this problem.
EDIT:
Not sure if it helps, but log cat shows this when I hold down power button to activate power menu:
Code:
D/dalvikvm( 1544): GC_FOR_ALLOC freed 477K, 5% free 19074K/19960K, paused 36ms, total 36ms
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
W/ViewRootImpl( 815): Dropping event due to no window focus: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_POWER, scanCode=116, metaState=0, flags=0x8, repeat
Count=2, eventTime=798132, downTime=797581, deviceId=5, source=0x101 }
W/ViewRootImpl( 815): Dropping event due to no window focus: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_POWER, scanCode=116, metaState=0, flags=0x8, repeat
Count=3, eventTime=798183, downTime=797581, deviceId=5, source=0x101 }
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
I/SearchController( 1581): #onHotwordDetectorStopped
I/MicrophoneInputStream( 1581): mic_close
D/PhoneStatusBar( 992): disable: < EXPAND* icons alerts ticker system_info back home recent clock search >
V/SearchControllerCache( 1581): disposing SearchController
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
D/dalvikvm( 1581): threadid=36: thread exiting, not yet detached (count=0)
D/dalvikvm( 1581): threadid=34: thread exiting, not yet detached (count=0)
D/dalvikvm( 1581): threadid=33: thread exiting, not yet detached (count=0)
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
D/dalvikvm( 815): GC_CONCURRENT freed 2195K, 9% free 27240K/29776K, paused 3ms+4ms, total 83ms
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
Again, it shows nothing when I simply just tap it (which should normally just turn the screen off).
EDIT2
If I go into the Xposed app and close it, it unblocks the system and everything finishes loading up. Looks like it locks up the system somehow.
EDIT3
Ok going into Xposed app and exiting it doesn't always help... so I'm at a loss. At this point I've completely uninstalled the xposed app, removed it from recovery, and deleted all modules, and this issue still happens when I reboot. I'll keep testing some things.
EDIT4
Alright so I went to TWRP and did a factory reset (dalvik, cache, data), the problem still happens!!!! I'm going crazy!
Android.Addiction said:
I'm running Nexus 5 stock ROM (latest Kitkat), rooted with TWRP recovery. I only have the following additional things I would consider "modifications":
Xposed installed with the following modules:
- Advanced power menu
- Exchange security bypass
When I boot up my phone, I am unable to turn my screen off at my lock screen by pressing my power button. It simply does nothing. If I set my phone on the table, the screen will not time out even though I have one set. My lock screen uses the pin pad. Another oddity I notice is that I have bluetooth enabled but it does not appear in the status bar until I unlock the screen. I also have a weather app that has temperature in the status bar, and that does not appear to be loaded until I unlock. So it seems that the OS is only partially loaded.
I attempted to look at logcats but I don't see anything useful. As I press the power button I do not see any feedback from logcat output at lockscreen after boot (I assume this is bad). Even though TAPPING power button does not turn off the screen, HOLDING power does bring up the power menu (wtf?).
Anyone know what is going on? I was skeptical to provide logcat data here since I am afraid it has personal info in it. I am not an android dev/logcat expert so please provide guidance. Thanks.
I have tried disabling Xposed and uninstalling the modules, but I still experience this problem.
EDIT:
Not sure if it helps, but log cat shows this when I hold down power button to activate power menu:
Code:
D/dalvikvm( 1544): GC_FOR_ALLOC freed 477K, 5% free 19074K/19960K, paused 36ms, total 36ms
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
W/ViewRootImpl( 815): Dropping event due to no window focus: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_POWER, scanCode=116, metaState=0, flags=0x8, repeat
Count=2, eventTime=798132, downTime=797581, deviceId=5, source=0x101 }
W/ViewRootImpl( 815): Dropping event due to no window focus: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_POWER, scanCode=116, metaState=0, flags=0x8, repeat
Count=3, eventTime=798183, downTime=797581, deviceId=5, source=0x101 }
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
I/SearchController( 1581): #onHotwordDetectorStopped
I/MicrophoneInputStream( 1581): mic_close
D/PhoneStatusBar( 992): disable: < EXPAND* icons alerts ticker system_info back home recent clock search >
V/SearchControllerCache( 1581): disposing SearchController
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
D/dalvikvm( 1581): threadid=36: thread exiting, not yet detached (count=0)
D/dalvikvm( 1581): threadid=34: thread exiting, not yet detached (count=0)
D/dalvikvm( 1581): threadid=33: thread exiting, not yet detached (count=0)
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
D/dalvikvm( 815): GC_CONCURRENT freed 2195K, 9% free 27240K/29776K, paused 3ms+4ms, total 83ms
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
E/PowerHAL( 815): touch_boost: failed to send: No such file or directory
Again, it shows nothing when I simply just tap it (which should normally just turn the screen off).
EDIT2
If I go into the Xposed app and close it, it unblocks the system and everything finishes loading up. Looks like it locks up the system somehow.
EDIT3
Ok going into Xposed app and exiting it doesn't always help... so I'm at a loss. At this point I've completely uninstalled the xposed app, removed it from recovery, and deleted all modules, and this issue still happens when I reboot. I'll keep testing some things.
EDIT4
Alright so I went to TWRP and did a factory reset (dalvik, cache, data), the problem still happens!!!! I'm going crazy!
Click to expand...
Click to collapse
Since the Xposed modules (which one unknown) probbly did mess something to not allow the power button to stop the turn off. Did the power button work before the install of the Xposed? Did you make a Nandroid backup of the ROM pre-Xposed install? and, if factory reset did not work and you are still at a lose, try flashing the Stock Rooted ROM (untouched version that you are basically running) that is in the original development section by TWRP. Make sure you do a backup (even if messed up) so if the new ROM doesn't work for you or something happens, you are safe. WIPE everything before install (I sometimes do it multiple times to ensure wipe). Install the fresh ROM and nothing else (kernels, optimizations, etc) and test the button. If it works, you're set.
RevelationOmega said:
Since the Xposed modules (which one unknown) probbly did mess something to not allow the power button to stop the turn off. Did the power button work before the install of the Xposed? Did you make a Nandroid backup of the ROM pre-Xposed install? and, if factory reset did not work and you are still at a lose, try flashing the Stock Rooted ROM (untouched version that you are basically running) that is in the original development section by TWRP. Make sure you do a backup (even if messed up) so if the new ROM doesn't work for you or something happens, you are safe. WIPE everything before install (I sometimes do it multiple times to ensure wipe). Install the fresh ROM and nothing else (kernels, optimizations, etc) and test the button. If it works, you're set.
Click to expand...
Click to collapse
I flashed factory firmware through fastboot (and erased userdata/recovery/boot/etc). Phone is practically just as it was out of the box now. But it still happens. I've contacted Google for a replacement. I think there is some hardware failure, I doubt that Xposed could cause damage like this. Another thing that makes me think this is hardware related is that I see NO activity in logcat when I tap the hardware button!! Strange isn't it?
Android.Addiction said:
I flashed factory firmware through fastboot (and erased userdata/recovery/boot/etc). Phone is practically just as it was out of the box now. But it still happens. I've contacted Google for a replacement. I think there is some hardware failure, I doubt that Xposed could cause damage like this. Another thing that makes me think this is hardware related is that I see NO activity in logcat when I tap the hardware button!! Strange isn't it?
Click to expand...
Click to collapse
I agree, Xposed may have if it went away with everything newly flashed yet, even after fresh everything the problem still persists, that's a hardware issue I suppose as well. I haven't run into this issue so I hope this one was just a freak rare event. Good luck.
I know this thread is a bit dated, but I have the same problem and I am completely stock with no mods at all. I'm not even rooted. It seems to do this randomly and after a clearing cache in stock recovery it will allow me to turn the screen off immediately after a reboot...once. After that, it's back to the not turning off BS. I know it's a small issue, but it's driving me frickin nuts haha. Being completely stock, I think we can rule out it being an xposed issue. I love this phone dearly, but it's got a fair amount of annoying little problems.
I had replaced my phone and everything works solid now. However, I have only rooted my phone. I had a ton of stability problems with xposed so I have vowed to not install it ever again. My battery life is amazing now without it and I don't have any weird issues.
Holy hell, I found a thread with my exact issue. Its definitely not hardware related though, I can say that with some certainty. Still troubleshooting it as we speak. Definitely something hanging up in the system. It seems if you open one app, doesn't matter which one, you can turn the screen off.
unsivil_audio said:
Holy hell, I found a thread with my exact issue. Its definitely not hardware related though, I can say that with some certainty. Still troubleshooting it as we speak. Definitely something hanging up in the system. It seems if you open one app, doesn't matter which one, you can turn the screen off.
Click to expand...
Click to collapse
This is what I had. It seems to have gone away now though.
Sent from my Nexus 5 using Tapatalk
Having the exact same issue on a Lenovo phone that received the kitkat update yesterday; sorry for posting it here but there are very few threads regarding this problem. If anyone who had this issue can confirm that they were using Dynamic Notifications - it would help immensely. Another Galaxy SIV user on XDA posted in January about uninstalling DN and not experiencing this any longer. It would be great to have a confirmation even though this is a slightly old thread.
Hmmm...I thought I had posted the solution, must've been in a similar thread. Yes, the issue is from Dynamic Notifications, more specifically the "block home" feature; disable it and you'll be good to go. I emailed the developer but never received and reply or follow-up.
unsivil_audio said:
Hmmm...I thought I had posted the solution, must've been in a similar thread. Yes, the issue is from Dynamic Notifications, more specifically the "block home" feature; disable it and you'll be good to go. I emailed the developer but never received and reply or follow-up.
Click to expand...
Click to collapse
Thanks for the reply! I've uninstalled Dynamic notifications completely and using AcDisplay app instead (no block home setting) - now I know where to look and what to correct in case this problem recurs.
Workaround
I have this issue on my Nexus 5 and it drives me crazy. I thought I filed a bug report with Google about it, but I can't find it. It's definitely not a hardware problem because a long-press of the power button pops up the menu for muting sound, setting airplane mode, etc.
I found a work around: press the Multitask soft button at the bottom of the screen, then press the power button. For whatever reason, this locks and turns off the screen. :highfive:
I haven't found the cause of the problem in the first place. It seems to be random, but I suspect it is caused by a bug in an app that has permissions to prevent the screen from locking. BTW, I do not have Dynamic Notifications installed.
I actually believe it has to do with something taking control of the 'home' launcher spot. For example when I enable 'block home' feature in Dynamic Notifications, it asks me to select DN as my default home, then on the next prompt you select your actual home.
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 ?