Status Update
Comments
co...@gmail.com <co...@gmail.com> #2
Information redacted by Android Beta Feedback.
[Deleted User] <[Deleted User]> #3
kl...@google.com <kl...@google.com> #4
Thank you for reporting this issue. We have a fix rolling out now.
lu...@gmail.com <lu...@gmail.com> #5
Thanks for the update.
ba...@gmail.com <ba...@gmail.com> #6
What
Feature request
The option on the top is not displaying properly, it's hidden under menu header
Where
Build and device data
- Build Number: google/cheetah_beta/cheetah:15/BP11.241121.010/12780007:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 244961035 (24.49.61 (260400-705672791))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683404342 (132.0.6834.43)
System App (Updated)
Network operator: Hutch
SIM operator: Hutch
Network operator: Mobitel
SIM operator: Sri Lanka Telecom Mobitel
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ba...@gmail.com <ba...@gmail.com> #7
This UI change is different than the fix that is rolling out
co...@gmail.com <co...@gmail.com> #12
lu...@gmail.com <lu...@gmail.com> #13
issue in comment#6
- investigation is still in progress.
b/389208485#comment15
wa...@gmail.com <wa...@gmail.com> #14
gdbserver output:
run-as: Package '<my.apps.packagename>' is unknown
Verify if the application was built with NDK_DEBUG=1
[Deleted User] <[Deleted User]> #15
gd...@gmail.com <gd...@gmail.com> #16
I did Debug as Native Application in Eclipse,
and since 4.3 update, it does not work anymore.
(NEXUS 4 / BUILD JWR66V)
ha...@google.com <ha...@google.com> #17
We are aware of the issue and working on a fix.
Once we find a workaround I will also post it here.
Sorry for an inconvenience.
Regards,
el...@gmail.com <el...@gmail.com> #18
ga...@gmail.com <ga...@gmail.com> #19
ng...@gmail.com <ng...@gmail.com> #20
st...@gmail.com <st...@gmail.com> #21
jp...@gmail.com <jp...@gmail.com> #22
pr...@gmail.com <pr...@gmail.com> #23
de...@gmail.com <de...@gmail.com> #24
Thanks in advance
or...@gmail.com <or...@gmail.com> #25
er...@gmail.com <er...@gmail.com> #26
el...@gmail.com <el...@gmail.com> #27
vs...@google.com <vs...@google.com> #28
ni...@gmail.com <ni...@gmail.com> #29
ry...@bissell.org <ry...@bissell.org> #30
For NDK r9:
Find this line in ndk-gdb:
run adb_cmd shell run-as $PACKAGE_NAME lib/gdbserver +$DEBUG_SOCKET --attach $PID &
replace it with these 4 lines (assuming you have $NDK defined, and assuming your target device is ARM):
run adb_cmd forward tcp:5039 tcp:5039
run adb_cmd remount
run adb_cmd push $NDK/prebuilt/android-arm/gdbserver /system/bin/gdbserver.temp
run adb_cmd shell /system/bin/gdbserver.temp --attach :5039 $PID &
I am working from memory above, didn't actually test exactly what I've written just now, so I apologize for any mistakes, but that is the general idea.
Again, this requires rooted device.
pa...@gmail.com <pa...@gmail.com> #31
ni...@gmail.com <ni...@gmail.com> #32
cl...@gmail.com <cl...@gmail.com> #33
*Do not forget to add NDK_DEBUG=1...
gd...@gmail.com <gd...@gmail.com> #34
kl...@google.com <kl...@google.com>
nn...@google.com <nn...@google.com>
eo...@gmail.com <eo...@gmail.com> #36
nn...@google.com <nn...@google.com> #37
eo...@gmail.com <eo...@gmail.com> #38
bo...@gmail.com <bo...@gmail.com> #39
jo...@gmail.com <jo...@gmail.com> #40
1. remount /system rw
2. chmod 4750 /system/bin/run-as
3. remount /system ro
4. enjoy debugging native code
jo...@gmail.com <jo...@gmail.com> #41
jo...@gmail.com <jo...@gmail.com> #42
bi...@gmail.com <bi...@gmail.com> #43
I had a hard time figuring out how to run those commands. I tinkered around and finally got it.
For rooted devices running a custom recovery:
- reboot to recovery
- find the mount system and check it
- open a terminal and type: adb shell
- type: chmod 4750 /system/bin/run-as
- uncheck the System mount and reboot!
ze...@gmail.com <ze...@gmail.com> #44
anyone has any idea on how to fix that?
ti...@gmail.com <ti...@gmail.com> #45
ze...@gmail.com <ze...@gmail.com> #46
ze...@gmail.com <ze...@gmail.com> #47
eo...@gmail.com <eo...@gmail.com> #48
Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:5039
Error message from debugger back end:
Remote communication error. Target disconnected.: No error.
Remote communication error. Target disconnected.: No error.
jo...@gmail.com <jo...@gmail.com> #49
BTW. I've confirmed that flashing the factory image works as a workaround for this issue too. It's probably the preferred method to using the steps I put in #41.
nn...@google.com <nn...@google.com> #50
jo...@gmail.com <jo...@gmail.com> #52
m8...@gmail.com <m8...@gmail.com> #53
nn...@google.com <nn...@google.com> #54
kl...@gmail.com <kl...@gmail.com> #55
In my case update to 4.4.2
ki...@gmail.com <ki...@gmail.com> #56
I currently have 4.4.2 OTA upgraded and I can't run adb gdb.
nn...@google.com <nn...@google.com> #57
If you can't run gdb, you should file a new bug. It's likely unrelated to this issue.
gi...@gmail.com <gi...@gmail.com> #58
sl...@gmail.com <sl...@gmail.com> #59
So I decided to share my one week hell with OTHER developers.
The reason behind all this are definitely permissions to directories and files in kernel.
So for this fix to work you really need to have rooted device to change permissions on folders and files.
1) You have to change permissions on run-as file in /system/bin folder by following these commands
adb -s <your device id> shell
su
mount -o rw,remount /system
chmod 4750 /system/bin/run-as
mount -o ro,remount /system
In the end run-as has rwsr-x--- permissions, owner is root, group is shell
2) Make sure /data folder has rwxrwx--x permissions, owner system, group system
3) Make sure /data/data folder has rwxrwx--x permissions, owner system, group system
4) Make sure /data/data/<packagename> folder has rwxrwx--x permissions, owner is uid from packages.list, group is uid from packages.list
In my case I did not have to change any permissions to packages.list file because run-as temporarily switches effective GID to allow read the packages file and also
8Kb is not the case, because run-as reads all the lines from packages.list until it finds package provided by arguments.
example from my packages.list
com.example.native_activity 10234 1 /data/data/com.example.native_activity default
package name: com.example.native_activity
uid: 10234
debuggable: 1
directory path: /data/data/com.example.native_activity
some info: default
uid is used for checking user permissions on /data/data/com.example.native_activity directory
I hope these steps help others too.
ab...@gmail.com <ab...@gmail.com> #60
Has the issue reappeared?
bo...@gmail.com <bo...@gmail.com> #61
I am also seeing this issue on Samsung Galaxy S4 with both Android 4.3 and Android 4.4.2. If anybody can find an appropriate Samsung-specific issue tracking location for this issue, please do link to it here!
bo...@gmail.com <bo...@gmail.com> #63
bo...@gmail.com <bo...@gmail.com> #64
So this issue appears to have resolved in Android 4.4.2 on Samsung devices, as well as on Nexus devices.
ki...@gmail.com <ki...@gmail.com> #65
I was experiencing the issue even though my phone was updated to 4.4.2 months ago. This was particularly aggravating because everywhere I looked, I would find other people celebrating the fact that the 4.4.2 update fixed everything for them.
It turns out reinstalling 4.4.2 and wiping all data on the phone is the answer, but you can't just do that from the recovery image already present on the phone; the bug will just remain.
I had to download a dump of the exact version of 4.4.2 used by my mobile provider for my phone model from some shady website (same exact build number / baseband version / ISP code), and flash it from Download mode. Then, when I rebooted and reinstalled, native debugging simply worked.
So, just to be clear, for some reason, if you HAD a bugged version before and you updated to 4.4.2 through your mobile provider ("OTA"), it's possibly still affected by this particular issue, and the only way to fix it is to reflash -- the procedure is the same as a downgrade.
ss...@gmail.com <ss...@gmail.com> #66
ki...@gmail.com <ki...@gmail.com> #67
ss...@gmail.com <ss...@gmail.com> #68
ki...@gmail.com <ki...@gmail.com> #69
ss...@gmail.com <ss...@gmail.com> #70
vi...@gmail.com <vi...@gmail.com> #71
ba...@gmail.com <ba...@gmail.com> #72
Google fixed it months ago.
vi...@gmail.com <vi...@gmail.com> #73
vi...@gmail.com <vi...@gmail.com> #74
co...@gmail.com <co...@gmail.com> #75
kr...@gmail.com <kr...@gmail.com> #76
On reading this thread, i thought it was due to the OTA update and so installed the factory OS from
But even after doing this, it didn't work. The permissions for package.list are still bad.
1|shell@mako:/ $ ls -al /data/system/packages.list
-rw-rw---- system package_info 13286 2014-05-26 19:15 packages.list
Can anyone point out what am i doing wrong?
vh...@google.com <vh...@google.com> #77
problem.
I would build 4.4.2 from source and flash it onto your device.
after update to 4.3
installed the factory OS from
instructions for installing the factory image were taken from
package.list are still bad.
ki...@gmail.com <ki...@gmail.com> #78
This is normal -- apps are not supposed to be able to read packages.list anymore, and that shouldn't interfere with run-as.
Note that this issue is characterized by the error message "run-as: Package '...' is unknown." If you don't get that particular message, the issue might be different.
The message can also pop-up if you forget to set the "android:debuggable" flag in the manifest -- see
kr...@gmail.com <kr...@gmail.com> #79
[2014-05-27 12:00:54 - ImageCoreTest] Unable to find a compatible ABI
[2014-05-27 12:00:54 - ImageCoreTest] ABI's supported by the application: x86
[2014-05-27 12:00:54 - ImageCoreTest] ABI's supported by the device: armeabi-v7a, armeabi
This was not correct as when i run the same app, it works fine. The Application.mk file had
APP_ABI := armeabi-v7a
Please note, we also build X86 binary for faster debugging in android emulator.
However when i put "APP_ABI := armeabi-v7a" in Android.mk file, i can debug. This is not where it is supposed to be according to android docs but it works :(
Also, when we put "android:debuggable" in manifest, it gives an error that it should not be hardcoded. Even without it, debugging it working fine.
ci...@gmail.com <ci...@gmail.com> #80
ci...@gmail.com <ci...@gmail.com> #81
Thanks.
jm...@gmail.com <jm...@gmail.com> #84
nn...@google.com <nn...@google.com> #85
ad...@gmail.com <ad...@gmail.com> #86
ad...@gmail.com <ad...@gmail.com> #87
cr...@gmail.com <cr...@gmail.com> #88
I know this problem and even don't want to upgrade system,
but today I just carelessly touched the update button.
Samsung Galaxy S6 upgraded from 5.0 to 5.1.1 and damn!
eh...@gmail.com <eh...@gmail.com> #89
vh...@google.com <vh...@google.com> #90
This issue is closed. If you are currently having issues, please file a new bug.
Description
Best regards,
Dmitry