Andrew,

Thanks very much for the very detailed explanation on the character of the 
init.generic*.rc files pushing.

In regarding to the navigation bar, I am using an element14 BBB with 
Circuito LCD4. So I don't have leisure to change the resolution. However I 
can using the LCD panel on-board buttons to navigate back. So it is not a 
big deal at this moment.

As Adam Singer mentioned, I am really looking forward to the kernel 
3.10/3.14 version with SGX support. Because kernel 3.10 adds much improved 
robustness to the USB driver.

Thanks again!

Lei



On Sunday, October 12, 2014 10:41:47 PM UTC-4, Andrew Henderson wrote:
>
> One thing that I should note is that if you use ADB to push files over to 
> the BBB, you must be sure that the permissions of the file that you pushed 
> are set correctly after the transfer.  If you are pushing the 
> init.generic*.rc files over, you must do something like:
>
> $ adb shell
> root@beagleboneblack:/ # chmod 750 init.genericam33xx\(flatteneddevicetr.rc
>
> If the permissions are too "permissive", the "import" command in init.rc 
> will refuse to include the init.generic*.rc file because it is a security 
> risk.  If the init.generic*.rc file isn't included, then ADB won't start, 
> and you are effectively prevented from using ADB at that point.  You'll 
> have to mount the EXT4 partition under Linux to fix the permissions.  Be 
> careful!
>
> Andrew
>
> On Sunday, October 12, 2014 9:50:55 PM UTC-4, Andrew Henderson wrote:
>>
>> The "rootfs" filesystem (the / filesystem) is set to read-only once you 
>> reach the post-fs phase of boot.  This is why you can't ADB push to it.  
>> I've been on the fence as to whether I should remount this as read-write, 
>> and I suppose that I probably should.  Since I'm trying to open up this 
>> Android a bit to make it easier for people to experiment with, it is 
>> reasonable to do so.  It also allows the Windows people who can't easily 
>> mount EXT4 to make changes to their Android system via ADB.
>>
>> Look at your init.genericam33xx(flatteneddevicetr.rc file at around line 
>> 36:
>>
>>     # we will remap this as /storage/sdcard0 with the sdcard fuse tool
>>     mkdir /data/media 0770 media_rw media_rw
>>     chown media_rw media_rw /data/media
>>
>>     # Set indication (checked by vold) that we have finished this action
>>     setprop vold.post_fs_data_done 1
>>
>> Right before that "# Set indication ..." line, add these two lines:
>>
>>     # BBBAndroid: Remount the rootfs as rw for ADB push of files to /
>>     mount rootfs rootfs / rw remount
>>
>> This will remount / as read-write.  The original remount to read-only 
>> occurs in init.rc, but you generally don't want to change the standard .rc 
>> files, so I override all of the defaults in the platform-specific .rc 
>> files.  I just pushed this change up to the repo: 
>> https://github.com/hendersa/bbbandroid-vendor-ti-beagleboneblack-aosp
>>
>> I have not checked into the nav bar issue, but I know that I have seen it 
>> in some resolutions and not in others.  Maybe try a different resolution?  
>> I'll see it at 720x480, for example, when using HDMI.  But I won't see it 
>> at the much higher resolutions (1920x1080, I think).  
>>
>> Andrew
>>
>>
>> On Monday, October 13, 2014 1:13:44 AM UTC, Lei Wang wrote:
>>>
>>> Hi Andrew,
>>>
>>> I rebuild the BBBAndroid and created my own image. The ADB USB does work 
>>> after I replaced those (3) files you attached earlier. It is a very good 
>>> news. 
>>> But I did find out that I couldn't push file thru the ADB push. I tried 
>>> both the eclipse ADT and command line. Neither works. I've got some 
>>> information like,
>>>
>>> E:\Program Files\Android\android-sdk\platform-tools>adb push 
>>> "init.genericam33xx
>>> (flatteneddevicetr.rc" /init.genericam33xx(flatteneddevicetr.rc
>>> failed to copy 'init.genericam33xx(flatteneddevicetr.rc' to 
>>> '/init.genericam33xx
>>> (flatteneddevicetr.rc': Read-only file system
>>>
>>> Another minor issue is that the navigation bar is not shown in the 
>>> interface. I double checked the images you attached. I couldn't find 
>>> navigation bar either. I had same issue with TI's stock image (Kernel 3.2 
>>> based). I added a line to the  
>>> init.am335xevm.rc: "setprop lcd.landscape true", which fixed the problem 
>>> (
>>> https://gitorious.org/rowboat/vendor-ti-am335xevm/commit/53391ade1b440e94c73db59444bf72529ce9ff32).
>>>  
>>> I did the same to the init.generic*.rc file. However it didn't work this 
>>> time. I wonder if you know how to bring the navigation bar back.
>>>
>>>
>>>
>>> Thanks a lot!
>>>
>>> Lei
>>>
>>>
>>> On Sunday, October 12, 2014 1:03:54 PM UTC-4, Andrew Henderson wrote:
>>>>
>>>> I'll have to make the next pre-made image a little smaller than the 
>>>> full capacity of my microSD cards because so many of the manufacturers are 
>>>> being very liberal on exactly how many bytes they consider 8GB to be...
>>>>
>>>> I have a Realtek RTL8188CUS USB wifi dongle sitting here (an Edimax 
>>>> EW-7811 of some sort, I believe), so I'll check into getting it set up for 
>>>> you when I have a few minutes.  The kernel modules are actually already 
>>>> sitting in the image, so you should be able to insmod them from within the 
>>>> init.{ro.hardware}.rc file.
>>>>
>>>> Andrew
>>>>
>>>> On Sunday, October 12, 2014 12:45:54 PM UTC-4, Altaf wrote:
>>>>>
>>>>> Hello, 
>>>>> Great work appreciate. 
>>>>> It would be awesome if you can add USB WiFi Support for Atheros AR9271
>>>>>   or Realtek RTL8188CUS Based Device
>>>>>
>>>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to