按我的手动步骤一步步输入命令,看下是哪一步出问题了。iloveola 写了:自己改了下daemonize文件的权限,全部执行打了√,然后回车没有任何反应。也没黑屏也没重启。好奇怪,我就是把xfdesktop.zip里面的全部文件跟Linaro.img(用的ext4)一共六个文件用RE复制进了根目录下的sdcard里,daemonize复制到了system/bin同时所有执行权限打√。
求指导o_o
安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
-
- 帖子: 262
- 注册时间: 2008-09-12 12:32
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
-
- 帖子: 262
- 注册时间: 2008-09-12 12:32
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
参考本贴第116-120楼吧。FrankCo 写了:运行后出现
p /sdcard/linaro.img /data/li
naro startlubuntu<
sh: daemonize: can't execute: Permission denied
然后就没了。。。
-
- 帖子: 2
- 注册时间: 2014-09-20 16:48
- 系统: Android
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
运行后正常显示界面,时间栏能正确更新,但是只要我触摸屏幕,就会立刻死机,3秒后自动重启进安卓。
有一次界面都没正确显示,屏幕狂闪,触摸屏幕后自动重启
有一次界面都没正确显示,屏幕狂闪,触摸屏幕后自动重启
-
- 帖子: 2
- 注册时间: 2014-09-20 16:48
- 系统: Android
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
过了一会重试,情况又不一样了。自动重启并且屏幕狂闪,重启完了照样狂闪,强行再次重启后恢复正常
-
- 帖子: 262
- 注册时间: 2008-09-12 12:32
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
Nukepayload2 写了:运行后正常显示界面,时间栏能正确更新,但是只要我触摸屏幕,就会立刻死机,3秒后自动重启进安卓。
有一次界面都没正确显示,屏幕狂闪,触摸屏幕后自动重启
估计触摸屏输入驱动不合适,考虑换一换试试?
-
- 帖子: 262
- 注册时间: 2008-09-12 12:32
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
可能是上次的一些进程没有妥善的结束,可以参考脚本中的kill那条,自己在命令行里再输一遍。硬重启一遍更为稳妥。Nukepayload2 写了:过了一会重试,情况又不一样了。自动重启并且屏幕狂闪,重启完了照样狂闪,强行再次重启后恢复正常
-
- 帖子: 2
- 注册时间: 2014-10-01 20:08
- 系统: Windows 7旗舰版 32bit
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
我已经可以看到桌面了,但是无法操作,点击屏幕没有反应怎么办?
机型是三星 P3110,1G内存,1.0GHZ双核处理器,频幕分辨率1024x600
机型是三星 P3110,1G内存,1.0GHZ双核处理器,频幕分辨率1024x600
-
- 帖子: 262
- 注册时间: 2008-09-12 12:32
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
你说的应该是触摸没反应吧Poccere 写了:我已经可以看到桌面了,但是无法操作,点击屏幕没有反应怎么办?
机型是三星 P3110,1G内存,1.0GHZ双核处理器,频幕分辨率1024x600
1. 换驱动,按我的帖子来做。
2. 接键盘鼠标。
-
- 帖子: 2
- 注册时间: 2014-10-01 20:08
- 系统: Windows 7旗舰版 32bit
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
能告诉我怎么安装驱动吗?从哪里下载?脚本我倒是会改,但是不知道怎么下载安装驱动。。。。。
-
- 帖子: 262
- 注册时间: 2008-09-12 12:32
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
忠实的windows用户么?Poccere 写了:能告诉我怎么安装驱动吗?从哪里下载?脚本我倒是会改,但是不知道怎么下载安装驱动。。。。。
ubuntu命令行方式安装软件:
apt-get install xserver-xorg-input-*
*换成任意一个驱动名称,mtrack、mulltitouch或tslib。
- 懒蜗牛Gentoo
- 论坛版主
- 帖子: 7353
- 注册时间: 2007-03-02 17:36
- 系统: Linux Mint
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
虽然有挖坟的嫌疑,但还是特地来支持一下,终于找到了让我的Xoom换发第二春的方案了
虽然世上没有完美的东西,但这并不影响我们追求完美,因为只有偏执狂才TMD能成功。
10.04新手入门——笨兔兔讲述自己的故事
10.04新手入门——笨兔兔讲述自己的故事
-
- 帖子: 1
- 注册时间: 2015-01-11 12:49
- 系统: centos
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
进不去,说not found
-
- 帖子: 262
- 注册时间: 2008-09-12 12:32
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
什么进不去,请提供详细信息。administrator_ 写了:进不去,说not found
-
- 帖子: 1
- 注册时间: 2015-03-23 18:14
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
LZ你好,我的触摸屏驱动是多点的,触摸无效,把驱动改为单点以后就可以用了,用的driver是Evdev
怎样才能使用多点,尝试装了mtrack也不行,多点的驱动在Android里是正常使用的~
这是报点情况:
root@localhost:/mnt/sdcard# evtest /dev/input/event4
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x2 version 0x100
Input device name: "touch_zet6221"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 102 (KEY_HOME)
Event code 139 (KEY_MENU)
Event code 158 (KEY_BACK)
Event type 3 (EV_ABS)
Event code 53 (ABS_MT_POSITION_X)
Value 0
Min 0
Max 800
Event code 54 (ABS_MT_POSITION_Y)
Value 0
Min 0
Max 480
Event code 57 (ABS_MT_TRACKING_ID)
Value 0
Min 0
Max 10
Properties:
Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1427105946.688233, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105946.688341, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1427105946.688406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 128
Event: time 1427105946.688468, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.688528, -------------- SYN_REPORT ------------
Event: time 1427105946.699625, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105946.699723, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1427105946.699790, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 128
Event: time 1427105946.699854, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.699914, -------------- SYN_REPORT ------------
Event: time 1427105946.711012, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105946.711117, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1427105946.711183, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 128
Event: time 1427105946.711244, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.711301, -------------- SYN_REPORT ------------
Event: time 1427105946.722400, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105946.722484, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1427105946.722550, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 128
Event: time 1427105946.722610, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.722669, -------------- SYN_REPORT ------------
Event: time 1427105946.733143, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.733218, -------------- SYN_REPORT ------------
Event: time 1427105948.404505, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.404599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 448
Event: time 1427105948.404668, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 154
Event: time 1427105948.404731, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.404790, -------------- SYN_REPORT ------------
Event: time 1427105948.416410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.416495, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 442
Event: time 1427105948.416561, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 157
Event: time 1427105948.416623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.416682, -------------- SYN_REPORT ------------
Event: time 1427105948.429751, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.429834, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 435
Event: time 1427105948.429899, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 160
Event: time 1427105948.429959, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.430017, -------------- SYN_REPORT ------------
Event: time 1427105948.442644, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.442728, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 427
Event: time 1427105948.442794, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 164
Event: time 1427105948.442855, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.442914, -------------- SYN_REPORT ------------
Event: time 1427105948.454156, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.454239, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 417
Event: time 1427105948.454330, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 168
Event: time 1427105948.454393, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.454451, -------------- SYN_REPORT ------------
Event: time 1427105948.465702, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.465781, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 407
Event: time 1427105948.465873, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 172
Event: time 1427105948.465936, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.465995, -------------- SYN_REPORT ------------
Event: time 1427105948.477289, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.477371, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 393
Event: time 1427105948.477459, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 177
Event: time 1427105948.477524, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.477583, -------------- SYN_REPORT ------------
Event: time 1427105948.488769, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.488851, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 381
Event: time 1427105948.488920, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 181
Event: time 1427105948.489007, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.489068, -------------- SYN_REPORT ------------
Event: time 1427105948.497770, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.497846, -------------- SYN_REPORT ------------
怎样才能使用多点,尝试装了mtrack也不行,多点的驱动在Android里是正常使用的~
这是报点情况:
root@localhost:/mnt/sdcard# evtest /dev/input/event4
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x2 version 0x100
Input device name: "touch_zet6221"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 102 (KEY_HOME)
Event code 139 (KEY_MENU)
Event code 158 (KEY_BACK)
Event type 3 (EV_ABS)
Event code 53 (ABS_MT_POSITION_X)
Value 0
Min 0
Max 800
Event code 54 (ABS_MT_POSITION_Y)
Value 0
Min 0
Max 480
Event code 57 (ABS_MT_TRACKING_ID)
Value 0
Min 0
Max 10
Properties:
Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1427105946.688233, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105946.688341, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1427105946.688406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 128
Event: time 1427105946.688468, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.688528, -------------- SYN_REPORT ------------
Event: time 1427105946.699625, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105946.699723, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1427105946.699790, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 128
Event: time 1427105946.699854, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.699914, -------------- SYN_REPORT ------------
Event: time 1427105946.711012, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105946.711117, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1427105946.711183, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 128
Event: time 1427105946.711244, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.711301, -------------- SYN_REPORT ------------
Event: time 1427105946.722400, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105946.722484, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 562
Event: time 1427105946.722550, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 128
Event: time 1427105946.722610, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.722669, -------------- SYN_REPORT ------------
Event: time 1427105946.733143, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105946.733218, -------------- SYN_REPORT ------------
Event: time 1427105948.404505, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.404599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 448
Event: time 1427105948.404668, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 154
Event: time 1427105948.404731, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.404790, -------------- SYN_REPORT ------------
Event: time 1427105948.416410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.416495, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 442
Event: time 1427105948.416561, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 157
Event: time 1427105948.416623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.416682, -------------- SYN_REPORT ------------
Event: time 1427105948.429751, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.429834, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 435
Event: time 1427105948.429899, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 160
Event: time 1427105948.429959, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.430017, -------------- SYN_REPORT ------------
Event: time 1427105948.442644, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.442728, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 427
Event: time 1427105948.442794, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 164
Event: time 1427105948.442855, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.442914, -------------- SYN_REPORT ------------
Event: time 1427105948.454156, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.454239, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 417
Event: time 1427105948.454330, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 168
Event: time 1427105948.454393, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.454451, -------------- SYN_REPORT ------------
Event: time 1427105948.465702, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.465781, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 407
Event: time 1427105948.465873, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 172
Event: time 1427105948.465936, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.465995, -------------- SYN_REPORT ------------
Event: time 1427105948.477289, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.477371, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 393
Event: time 1427105948.477459, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 177
Event: time 1427105948.477524, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.477583, -------------- SYN_REPORT ------------
Event: time 1427105948.488769, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1427105948.488851, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 381
Event: time 1427105948.488920, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 181
Event: time 1427105948.489007, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.489068, -------------- SYN_REPORT ------------
Event: time 1427105948.497770, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1427105948.497846, -------------- SYN_REPORT ------------
-
- 帖子: 3
- 注册时间: 2015-06-09 22:44
- 系统: android
Re: 安卓系统流畅体验Linux桌面[自制镜像和脚本已发布]
红米为什么不行呢?