三星 Galaxy Tab 10.1 16BG 仅 Wifi，零售（非 I/O）版本，运行 3.1。
直到几天前，我还可以从 Eclipse DDMS 角度毫无问题地访问 /data/data/com.my.app/{databases,...}。这有助于开发，例如让我拉取 sqlite 文件以确保我的数据库代码正在执行我认为应该执行的操作，从 Linux 命令行访问 sqlite 文件。
几天前，我来到办公桌前，发现标签处于一种奇怪的状态：好像卡在启动过程中，摸起来很热，表明 CPU 正在旋转。
我以为这是一次崩溃，然后重新启动了它，并没有再多想，直到今天早些时候，我无法再通过 DDMS 访问 /data。 /system 和 /mnt 可以访问。
有谁知道可能导致这种变化的原因是什么，以及是否/如何可以逆转？我之前没有root过该选项卡，虽然我知道root它可能会带回对/data的访问（通过DDMS？），但我宁愿在继续之前尝试了解发生了什么。
还有其他人看到过相同/相似的行为吗？
更新：这是 ADB shell 的样子：
shell@android:/ $ ls -ld data
drwxrwx--x系统系统 2011-07-05 15:49 数据
shell@android:/ $ cd 数据
shell@android:/data $ ls
opendir 失败，权限被拒绝
255|shell@android:/数据 $
Samsung Galaxy Tab 10.1 16BG Wifi-only, retail (not I/O) edition, running 3.1.
Up until a few days ago, I could access /data/data/com.my.app/{databases,...} from the Eclipse DDMS perspective without issues. This helped with development by e.g. letting me pull sqlite files to make sure my DB code was doing what I thought it should be doing, accessing the sqlite files from the Linux command line.
A few days ago I came to my desk and found the tab in a strange state: as if stuck in the boot process, and warm to the touch, suggesting that the CPU was spinning.
I assumed it was a crash, rebooted it and thought nothing more of it until, earlier today, I can no longer get DDMS access to /data. /system and /mnt are accessible.
Is anyone aware of what might have caused that change, and if/how it can be reversed? I had not rooted the tab before, and although I understand rooting it may bring back access to /data (over DDMS?) I'd rather try to understand what happened before proceeding.
Has anyone else seen the same/similar behavior?
Update: Here's what this looks like from an ADB shell:
shell@android:/ $ ls -ld data
drwxrwx--x system system 2011-07-05 15:49 data
shell@android:/ $ cd data
shell@android:/data $ ls
opendir failed, Permission denied
255|shell@android:/data $
发布评论