ATTENTION
This project is currently dead, for more information have a look at http://code.google.com/p/archos-gen8-dvb/
SUCCESSOR IS ONLINE, check it out at http://github.com/chrulri/droidtv
-- old content:
As the Archos 101IT has a full size USB port, why shouldn't we plug a dvb-t stick in and watch tv? (without internet!)
For more information see Roadmap
Any comments / suggestions?
Testers:
chulri: A101IT + Hauppauge WinTV-NOVA-T-Stick
raminator: A32IT + TerraTec Cinergy T USB XE
cajl: A101IT, A70IT, A32IT + ???
fullthrottleenergy: A70IT + Hauppauge WinTV HVR-950Q
MGUS: A??IT + "bunch of different dvb-t and a dvb-s2 stick"
usrname: A101IT + TerraTec Cinergy T USB XE
bkortleven: A101IT + Pinnacle PCTV 73e
Onliner09: A101IT + TerraTec Cinergy T USB XE (Rev.2)
andbroe: A???IT + TerraTec Cinergy Piranha
Kashban: A101IT + Terratec Cinergy T USB XXS
godashram: A???IT + Hauppauge WinTV HVR-950Q
umberto.sulla: A101IT + AVerMedia AVerTV Volar Black HD (A850)
Links:
Download List: http://code.google.com/p/archos-gen8-dvb/downloads/list
code.google.com: http://code.google.com/p/archos-gen8-dvb/
kernel source: https://gitorious.org/~chrulri/archos-dvb-gen8-kernel
linuxtv.org dvb-t usb device list: http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices#DVB-T_USB_Devices
howto set up your own archos gen8 build environment: http://forum.xda-developers.com/showthread.php?t=891056
Videos:
A101IT + DVB-T (archos-gen8-dvb release v0.6)
UrukDroid 0.6 with LiveTV and DVB-T
UrukDroid 0.7RC1 with LiveTV and DVBT TV
Click to expand...
Click to collapse
i would volunteer to test it on my A32IT (have dvb-t stick and USB-adapter)
thank you!
raminator said:
(have dvb-t stick and USB-adapter)
Click to expand...
Click to collapse
which one do you have?
me too
on Archos 10.1, 7.0 and 4.3
chulri said:
thank you!
which one do you have?
Click to expand...
Click to collapse
terratec cynergy xte or something like that...4 years old
After analyzing the archos froyo source package I've found out that they already have a package for the linuxtv-dvb-apps project but disabled it This makes building a lot easier, as I don't have to write my own configs and makefiles
I updated it to the newest HEAD checkout of linuxtv-dvb-apps and then I've wrote some script which make the build process so much easier (unpack one tar archive, copy the froyo release package into same folder and run a script..)
I'm currently testing the build process and try to minimalize it (for fixing and upgrading, in the end I only have to build it once)
edit: update in OP
would a micro usb host cable work to connect a hauppage 950q? Not sure if there's enough power.
edit: talking about the a70
I don't know if power could be an issue at all.
Is the HVR-950Q supported by linux kernel?
you can count me as a tester...
have a bunch of different dvb-t sticks and a dvb-s2 usb and have some experience in LinuxTV especially with vdr.
very interesting. would like to test with my A101IT and Cinergy Hybrid T XE.
got my dvb-t (hauppauge nova-t) stick yesterday, works great with windows AND linux (ubuntu 10.10). looking forward to next steps in a few days.
btw: great solution for (possible) perm root: http://forum.xda-developers.com/showthread.php?t=880321
I wasn't able to sleep so I kept working
built dvb kernel modules and wrote a script doing all the insmod stuff
copied firmware for my dvb tuner
baaam! device gets recognized!!!!
crossbuilt w_scan
YAY! Now I can scan for channels and I finally have found all of them!
hi guys, it's me again
still not sleeping (3:55 AM local time) ...
here is my first package (so far only dvb-t drivers) for some early pre-alpha testers:
install SDE
install custom kernel+initramfs from dogmaphobia: http://forum.xda-developers.com/showthread.php?t=880321
copy content of zip file to internal storage or sd card, don't forget to disconnect usb
boot SDE (rooted android)
start terminal -> run "su"
run "sh .../setup_dvb-core.sh"
run "sh .../load_xxx.sh" (create your custom script if you need another module than me)
plug in dvb-t stick
check "dmesg" if your device got recognized (don't forget firmware if needed!)
run "w_scan -ft -c$$ -X > channels.conf" where $$ is your country code (CH for switzerland for example, see w_scan help)
check channels.conf if all channels got recognized
post feedback in this thread (!!)
package download: --obsolete--
I just donated you a 10.
Even though I can't test as I don't have SDE installed yet, I wanted to say thanks for all your efforts for this! It is always ppl like you who make our devices worth a lot more for us with functions I didn't even think of when I bought it.
THANK YOU! Keep up the amazing pace!
/schaze
Volunteering too.
Archos 101, latest froyo updates, pctv usb 73e which works on recent linux kernel
Would looooove to see this working. Thanks
@schaze thank YOU very much, I appreciate this!
@bkortleven great! I'm currently working on a first TV app so we can see for the very first time if it is really working.
omg.. I start loving sleepless nights
another little step for mankind but a big step for this project
explanation:
after writing several bash scripts, I got an easy cross build environment for maybe any kind of source code.. so I managed to cross compile tzap (and szap / czap) for tuning and guess what...... IT'S WORKING!
here is a short recording (# cat /dev/dvb/adapter0/dvr0 > test2.ts) of swiss television. recorded using an A101IT and Hauppauge Nova-T stick
http://www.mediafire.com/?1artz78aarly34g
PS: a new package for testing will be released soon, v01 has a huge bug because of how it mounts /lib/firmware .. don't use it
Amazing work man! Looking forward to this, do you think it might work on my Archos 70 Internet Tablet ? or does it need more power than the 70 can give out? (might be able to do it anyway with a powered hub)
Thanks. I don't know, are there any hardware differences between A101IT and A70IT?
UPDATE:
v02 is available
Download
+ = new in this version
dvb-t usb driver kernel modules
setup: setup dvb_usb core driver and install dvb utils
+ loadmod: shell script for easy firmware and kernel module load (only insmod -> no modprobe on this system)
+ rmmods: shell script for unloading kernel modules
+ ..zap: zapping utility
w_scan: scanning utility
HowTo use:
install sde and permroot by dogmaphobia (read this)
boot rooted android
copy content of zip file to internal storage ( e.g. /mnt/storage/dvb )
run terminal
Code:
# su
# sh
# cd /mnt/storage/dvb
# sh setup
# sh loadmod mod/<KERNEL_MODULE>.ko
plug in dvb-t usb stick
# w_scan -ft -c<COUNTRY_CODE> -X > channels.conf
# tzap -c channels.conf -rSp "<CHANNEL_NAME>" &
# cat /dev/dvb/adapter0/dvr0 > test.ts
cancel with ctrl+c after some seconds or minutes
# killall tzap
[# sh rmmods] (optional)
# exit
now you should have some recording of your selected channel under /mnt/storage/dvb
copy it to your computer and watch it with VLC or some other video player
Don't forget to report your issues or success here! Thanks in advance!
Related
Just saw some interest for Fedora install on Nook in another thread to my surprise. I thought I am the only pervert interested.
Anyway this is pretty raw at the moment. You need to know your way around Linux and have a Linux box (naturally).
Just not to disappoint you later on, here's what not working:
Only based on Fedora13 from upstream (F14 work is ongoing by Fedora-Arm team and I am just tracking them).
Wifi (still did not get to look into it)
BT (same)
accelerated graphics
Don't know of any touch-friendly WM, so defaults to Gnome.
Multitouch (disabled in driver at the moment since no userspace support anyway).
backlight control does not work, need to rewrite the kernel driver
Xorg does not know what to do with accelerometer input.
Probably tons of other things I forgot about.
You must be out of your mind if you want to try it on a tablet at this stage. Or just super curious.
You will need a microSD (at least 2G) card that you can dedicate to this.
Instructions:
Get "base" fedora sdcard image: http://nook.handhelds.ru/fedora/fedora-sdcard-v0.1.img.gz
Get base Fedora 13 beta3 rootfs: http://lists.fedoraproject.org/pipermail/arm/2011-May/001271.html
Get kernel modules for the kernel: http://nook.handhelds.ru/fedora/modules-2.6.32.9-fc13.tar.bz2
Unzip the base sdcard image and write it to your sdcard with dd.
run fdisk on the sdcard and add another partition covering the rest of sdcard in addition to the one already there. Write changes
do mkfs.ext4 /dev/yoursdcard2 (basically format the second partition you just created as ext4)
mount the /dev/yoursdcard2 somewhere as root (/mnt/somewhere later on)
untar the F13-beta3 rootfs to the /mnt/somewhere
Now you are almost ready, just need to fill some configs.
Edit /mnt/somewhere/etc/sysconfig/network-scripts/ifcfg-usb0 and add this there:
Code:
DEVICE=usb0
#BOOTPROTO=dhcp
BROADCAST=192.168.2.255
IPADDR=192.168.2.2
NETMASK=192.168.2.0
NETWORK=192.168.2.0
GATEWAY=192.168.2.1
ONBOOT=yes
Edit /mnt/somewhere/etc/resolv.conf and change "nameserver" there to 8.8.8.8
Add multitouch config in /mnt/somewhere/etc/X11/xorg.conf.d/touchscreen.conf
Code:
Section "InputClass"
Identifier "touchscreen"
MatchIsTouchScreen "on"
MatchProduct "cyttsp-i2c"
Driver "mtev"
Option "SendCoreEvents" "On"
Option "SwapAxes" "true"
Option "InvertY" "true"
EndSection
cd /mnt/somewhere/lib/modules and untar the modules file there.
umount /mnt/somewhere
Ok, now you are ready to do some stuff on the nook.
Insert your sdcard into the nook and boot it. You'll see Fedora text console. The installation is pretty basic.
Plug the nook into your Linux PC usb port. It should see a new network device
On the linux PC as root execute: ifconfig usb0 192.168.2.1 netmask 255.255.255.0
Enable ip forwarding on your host if you have it disabled (typically in /etc/sysctl.conf, the setting is ...ip_forward, make it =1. Run sysctl -p for the changes to make effect.
Enable internet access to internet for your nook via IP masquerading: iptables -t nat -I POSTROUTING -s 192.168.2.2 -j MASQUERADE ; iptables -I FORWARD -s 192.168.2.2 -j ACCEPT ; iptables -I FORWARD -d 192.168.2.2 -j ACCEPT
Now use ssh to login to your Nook: slogin [email protected] the root password is "fedoraarm" (no quotes)
Once logged into the nook, time to install some packages.
rpm -Uvh http://hongkong.proximity.on.ca/yum/base/12/arm/fake-kernel-provides-1.0.0-0.fc12.armv5tel.rpm
update the system: yum update ; yum install tar openssh-clients
Install the gnome environment: yum groupinstall 'GNOME Desktop Environment' --skip-broken
The gnome installation will take a while and will download everything from the net.
Now install the multitouch Xorg driver, get it at http://nook.handhelds.ru./fedora/xf86-input-mtev-0.1.12-1.armv5tel.rpm
Ok. Now you are ready to go. Run "startx &" and the Gnome will start on the nook. You can play with it a bit, use your finger as the mouse pointer.
You can add startx & at the end of e.g. /etc/init.d/rc.local to make it start on system startup or you can do it in a more pretty way.
There are some virtual keyboards in the repo. I tried gko and it sucks.
the "onboard" seems to be the one working best for me. "xvkbd" is a bit hard to operate.
The best one of them all is fvkbd, but it needs libfakekey missing from the repo, grab it at http://arm.koji.fedoraproject.org/p...3/armv5tel/libfakekey-0.1-6.fc13.armv5tel.rpm
Enjoy.
Fedora-arm homepage: http://fedoraproject.org/wiki/Architectures/ARM
I intend to include all the missing pieces into the fedora repo so that you don't need to install all those extra things. Also eventually I plan to add more hardware support and then hopefully migrate to a much newer kernel.
Ha, cool. Glad to see that not everyone thinks that only Ubootoo should be thrown on devices. I'll give this a twiddle for fun.
13 had Moblin, I wonder if that's any better for touch input..
Now i don't feel near as silly for working on my gentoo install for the nook!
Nice, I am still waiting on OpenSuSe
Why not try using Gnome 3? I just poked around in Fedora 15 today and saw the new UI, and I loved it. Bigger buttons, launcher dock, etc. Give it a look!
pts69666 said:
Why not try using Gnome 3? I just poked around in Fedora 15 today and saw the new UI, and I loved it. Bigger buttons, launcher dock, etc. Give it a look!
Click to expand...
Click to collapse
Fedora15 is not available for arm arch yet. But there is some work in that direction. So sure, once it's available I'd give it a try.
Great stuff here. I knows its early development, but fun none the less to see what our nooks can do.
And thanks verygreen for all your developments lately
Sent from my NookColor using Tapatalk
verygreen said:
Fedora15 is not available for arm arch yet. But there is some work in that direction. So sure, once it's available I'd give it a try.
Click to expand...
Click to collapse
in fedora 13,
Code:
su
yum install gnome-shell
...
============================================================================================================
Package Arch Version Repository Size
============================================================================================================
Installing:
gnome-shell i686 2.28.0-3.fc12 fedora 301 k
Installing for dependencies:
gjs i686 0.4-1.fc12 fedora 126 k
mutter i686 2.28.0-2.fc12 fedora 1.2 M
Transaction Summary
============================================================================================================
Install 3 Package(s)
Upgrade 0 Package(s)
...
gnome-shell -replace
I haven't tested it myself; however, it is something I found. My linux hard drive had hard drive failure. So, I am on windows in the meantime. Will report back later after testing it myself.
pts69666 said:
in fedora 13,
Code:
su
yum install gnome-shell
...
============================================================================================================
Package Arch Version Repository Size
============================================================================================================
Installing:
gnome-shell i686 2.28.0-3.fc12 fedora 301 k
Installing for dependencies:
gjs i686 0.4-1.fc12 fedora 126 k
mutter i686 2.28.0-2.fc12 fedora 1.2 M
Transaction Summary
============================================================================================================
Install 3 Package(s)
Upgrade 0 Package(s)
...
gnome-shell -replace
I haven't tested it myself; however, it is something I found. My linux hard drive had hard drive failure. So, I am on windows in the meantime. Will report back later after testing it myself.
Click to expand...
Click to collapse
No "gnome-shell" package in Fedora-arm repo at this moment,
Quite excited to see some work in bringing Fedora to the Nook Color! I <3 Fedora.
I just wish ARM had the same support as the full Fedora. Or that they would skip releases for Fedora ARM and go yearly... aka, skip to 15 next, then 17.
Could this be used to help port Ubuntu Touch?
moocow1452 said:
Could this be used to help port Ubuntu Touch?
Click to expand...
Click to collapse
No, Ubuntu Touch is based on CM and has very little in common with a full Linux port.
I just wanted my Archos Gen8 to have the latest stock firmware, root access, iptables support (for Droidwall) and a 1GB ext4 data partition. I will show you how to create this setup yourself. This howto describes all steps for a Linux PC with a working adb connection to the Archos Gen8. I am sure all steps can be done from a Windows PC too, but I cannot help you there: I only speak linux. [edit: Harfainx has written a thread on http://forum.archosfans.com/viewtopic.php?f=76&t=54637 that explains how to do these steps on windows; if you to do this from windows and have iptables and ext4, use my attached kernel and ext4 modifications instead of Harfainx' suggested chulri kernel]
[Archos] = do on tablet
[Linux] = do on PC
[Shell] = do in a terminal on PC
[ADB] = do in a adb shell from PC
[GParted] = do in gparted in PC
[Editor] = do in your favorite text editor on PC
All credits for this procedure go to other people (see end of this post); my only contribution is this write up, and the compilation of the new kernel.
1. Use chulri's root method to obtain root+rw with the latest Archos firmware on your Archos Gen8 (download the proper firmware version, and take care to rename the downloaded firmware file to firmware_archos_android_gen8.aos).
2. Install the matching version of my kernel + initramfs (see links below)
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Flash Kernel and Initramfs"
connect your Archos device by USB to your computer
upload zImage and initramfs.cpio.gz to your device
safely disconnect the USB connection
press ok on Archos device
reboot
3. Repartition your internal SD card
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Repair system” ->"Start USB MSC"
Connect tablet to your linux pc
Resize interal SD card and add an ext4 partition:
[Shell] sudo gparted
[GParted] find Archos device. For me it is found on /dev/sdc
[GParted] select the Archos partition and resize to have 1024MiB at the end left
[GParted] create a new primary partion using all the space you just created, filesystem ext4 and align to MiB
[GParted] apply all selected actions, let it finish and quit gparted.
unplug and reconnect your device so Linux finds it again.
Format the ext4 partition with some nice settings (if your device was on /dev/sdb replace /dev/sdc2 with /dev/sdb2 below):
[Shell] sudo mkfs.ext4 -b 4096 -E stride=64,stripe-width=64 -O extent,^huge_file -m 0 -L data /dev/sdc2
[Shell] sudo tune2fs -c -1 -i 0 -m 1 -O ^huge_file -o journal_data_writeback /dev/sdc2
[Shell] sudo e2fsck /dev/sdc2
press ok on Archos device
reboot
4. Make your new ext4 partition your /data partition
Boot up your Archos and proceed through the startup wizard; do not put too much effort in this because all information you enter now will be lost after this step.
Open options->applications and enable debugging support.
Connect the Archos to your linux PC
[Shell] adb shell
[ADB] su; stop; cp /init.rc /sdcard/
[Shell] adb pull /sdcard/init.rc
Modify init.rc:
[Editor] Open the just downloaded init.rc
[Editor] Replace the "mount ext3 /dev/block/mmcblk0p4 /data noatime nosuid" with "mount ext4 /dev/block/mmcblk1p2 /data rw noatime nosuid nodev barrier=0 data=writeback nobh"
[Editor] save file and close
[Shell] adb push init.rc /sdcard/
[ADB] cp /sdcard/init.rc /init.rc
[ADB] start
reboot
5. Now your device should start up and use your new ext4 partition as /data. In my case after reboot I had to force another reboot (hold on/off for 10sec) for the system to properly boot and come up with the Archos startup wizard again (the previous startup’s data is lost because we have a new /data partition).
6. Enjoy!
All credits for this procedure go to other people; my only contribution is this write up, and the compilation of the new kernel.
Rooting method: chulri
1GB data partition: chulri and wdl1908
Ext4 format flags: Sibere
Proper compilation of iptables and ext4: $aur0n and woti23
Howto compile the kernel yourself
Compiling this kernel yourself is not very hard.
1. Set-up chulri's development enviroment
2. Configure the new kernel
[Shell] cd $ARCHOS
[Shell] make kernel-config
[Config] In Networking support -> Networking options -> Network packet filtering framework (Netfilter)
Core Netfilter Configuration -> Netfilter Xtables support: y; Xtables -> "owner" match support: y
IP: Netfilter Configuration -> IP tables support: y; Packet filtering: y; REJECT target support: y; LOG target support: y
[Config] In Filesystems
The Extended 4 (ext4) filesystem: y
Ext4 extended attributes: y
[Config] save changes and exit
[Shell] make kernel-build
After compilation, locate your kernel zImage and flash it together with chulri's initramfs.cpio.gz (which is also provided in the zip in the first post).
Recommendations to speed up your tablet
Now that you have your Archos Gen8 as you want it, I can recommend two additions to speed up your system.
1. You now have a fast, big ext4 data partition which you should use for all applications:
[Shell] adb shell pm setInstallLocation 1
2. Replace the default Launcher *ANY* launcher but the Archos one. Personally I recommend the Zeam launcher, since it is really lightweight:
Get your copy of zeam, install it, press "home" button and make it default to zeam.
[ADB] su; cd /system/app; mv Launcher2.apk Launcher2.apknot
The last step makes sure that the Archos launcher does not startup anymore, saving your memory. The last steps also removes the default Archos wallpapers, so make a copy of the one you want or get some nice new ones.
Since the device setup of this thread uses unionfs to make changes to the /system, you could also just remove /system/app/Launcher2.apk. To restore it you can remove /mnt/system/unionfs/system/app/.wh.Launcher2.apk. (Thanks to skeeterfood for pointing it out.)
Great work! Thumbs up!
Thanks for this awesome tutorial!!!!!!
Thanks to all the people who work on our Archos Gen8 devices!!!!
is the performance comperable to urukdroid? i really like urukdroid but the mediascanner issue drive me nuts .
Anyway great work and thanks for the tutorial, now a kernel to be able to overclock and it would be awesome
cHarOn99 said:
is the performance comperable to urukdroid? i really like urukdroid but the mediascanner issue drive me nuts .
Anyway great work and thanks for the tutorial, now a kernel to be able to overclock and it would be awesome
Click to expand...
Click to collapse
I don't know if performance is comparable to UrukDroid; I've used Uruk 1.0 for some months but I haven't run any benchmarks. The reason for that is that Quadrant keeps giving errors in fixed landscape mode and I always used fixed landscape because the stock Archos launcher takes for ever to redraw on screen rotation.
Now of course I replaced the Archos launcher with Zeam, and now redraws on screen rotation are very fast. Replacing the Archos launcher in UrukDroid with Zeam would of course give you the same improvement. Anyway, with the configuration described above @800MHz (I could set it at 1GHz but I didn't) I get Quadrant scores of 1810. If you run it on UrukDroid, we can compare.
Definitely my system is booting much faster now than than it did before, but that might just be Zeam.
Right now sibere is making kernels for UrukDroid which give a nice performace improvement; perhaps he is willing to make kernels for stock too, or help me a bit along? Also when I have some more time, I hope to port some of Ardatdat's kernel improvements to the latest firmware kernel. Maybe someone else is working on that already?
WhoDunnit said:
I don't know if performance is comparable to UrukDroid; I've used Uruk 1.0 for some months but I haven't run any benchmarks. The reason for that is that Quadrant keeps giving errors in fixed landscape mode and I always used fixed landscape because the stock Archos launcher takes for ever to redraw on screen rotation.
Now of course I replaced the Archos launcher with Zeam, and now redraws on screen rotation are very fast. Replacing the Archos launcher in UrukDroid with Zeam would of course give you the same improvement. Anyway, with the configuration described above @800MHz (I could set it at 1GHz but I didn't) I get Quadrant scores of 1810. If you run it on UrukDroid, we can compare.
Definitely my system is booting much faster now than than it did before, but that might just be Zeam.
Right now sibere is making kernels for UrukDroid which give a nice performace improvement; perhaps he is willing to make kernels for stock too, or help me a bit along? Also when I have some more time, I hope to port some of Ardatdat's kernel improvements to the latest firmware kernel. Maybe someone else is working on that already?
Click to expand...
Click to collapse
I agree with you, Zeam is the best Launcher for Archos . When installing UrukDroid, my Archos is longer battery life, LCD is more sensitive and it very fast . Another devices, when you increase speed of cpu, battery life is softer .
I don't think Uruk firmware had been cooked with stock kernel, stock kernel's not stability.
thanks for the reply, personally i don't care about quadrant which is the worst benchmark at all , you already answered the question good enough for me, you said booting is faster and general the feel is fast, thats for me a better benchmark result then any syntetic test which gives you results like in the lottery .
I use Golauncher on the A43 and it works also good, i never used the stock launcher .
I think i will try your solution out and look forward to some kernel improvements if you make one, if not then also fine.
Thanks again
i prefer VTL.Launcher. it is based on adw, but better configurable. i remove ALL soft buttons, all panels and the notificationbar. instead i use Button Savior to have HOME/BACK/SEARCH/MENU buttons.
runs pretty smooth and i can use fullscreen.
any launcher goes
Right, that's the beauty of android: Anything can be replaced and modified to your own taste. I modified my recommendations above about replacing the default launcher with Zeam: *ANY* launcher is better that the Archos default one. My only reason for recommending Zeam is because it is lightweight.
Bottom line: replace the launcher with any alternative and you will have a smoother system.
I love open source and, of course, linux(android) and the power of freedom it has. i hope it will never become mainstream as Windows or Mac is.
Thats the reason why i donate as much as i can to oss projects instead buying expensive Windows software.
And thats why i have big respect to all people who made our computerworld a little bit better to use! Call me a idealist, i am proud to be one! If we were no idealists things like Android wouldn´t exist.
OK, enough
back to topic!
WhoDunnit said:
Now that you have your Archos Gen8 as you [*] [ADB] su; cd /system/app; mv Launcher2.apk Launcher2.apknot
[/LIST]
Click to expand...
Click to collapse
Might as well just do:
[ADB] su; cd /system/app; rm Launcher2.apk
since it's really not deleting the file, but instead creating a .wh.Launcher2.apk file in /mnt/system/unionfs/system/app/ that causes unionfs to hide the file. You can always get it back by removing the /mnt/system/unionfs/system/app/.wh.Launcher2.apk file.
-John
Is the ext4 1 gig of data for extra app space?
skeeterfood said:
Might as well just do:
[ADB] su; cd /system/app; rm Launcher2.apk
since it's really not deleting the file, but instead creating a .wh.Launcher2.apk file in /mnt/system/unionfs/system/app/ that causes unionfs to hide the file. You can always get it back by removing the /mnt/system/unionfs/system/app/.wh.Launcher2.apk file.
Click to expand...
Click to collapse
Right, thank you. I added it to the steps to follow.
darren1 said:
Is the ext4 1 gig of data for extra app space?
Click to expand...
Click to collapse
That's the idea: All (non-system) apps and data will be stored in the 1GB ext4 partition.
WhoDunnit said:
That's the idea: All (non-system) apps and data will be stored in the 1GB ext4 partition.
Click to expand...
Click to collapse
Great, thanks.
A70H Compatible?
Thanks for all the work. Looks great and I'm about ready to try it but need to know first, will this work on the A70H (250gb version)?
H_Scrappy said:
Thanks for all the work. Looks great and I'm about ready to try it but need to know first, will this work on the A70H (250gb version)?
Click to expand...
Click to collapse
It's been suggested that you shouldn't perform this operation on the hard-drive versions. Constant app re-writes on the hard-drive could be a cause for early drive failures.
Nice write-up here WhoDunnit. I did a Windows-based write-up last month over at the ArchosFans forum. Now it looks like people have some options for methods to create their partitions on both Linux and Windows. More information is always a good thing
http://forum.archosfans.com/viewtopic.php?f=76&t=54637
Harfainx said:
I I did a Windows-based write-up last month over at the ArchosFans forum. Now it looks like people have some options for methods to create their partitions on both Linux and Windows. More information is always a good thing
http://forum.archosfans.com/viewtopic.php?f=76&t=54637
Click to expand...
Click to collapse
OK, great. I added a link to your thread so people can find answers if they want to do this from windows.
Good day...
Im wanting to connect a USB camera to my ViewSonic G Tablet... I have 3 different USB models. When I plug them in (individually,) I get the /dev/video0 device but I don't seem to be able to use the device...
Why a second camera? I'm thinking I can use my G Tab in my car with a USB camera connected for a Baby Cam (since the baby faces the other way so I can't see and most of my traveling is at night so the normal mirror won't work unless I blind the poor child...) -- In theory, it could be used as a backup camera as well. (Same effect)
The internal camera works, but I don't need to see myself, I'd rather see something behind me.
Ideas?
I've scoured the Forums in more detail... Several ask the questions and someone made it work on the Nook, but it looked Nook specific. =/
Is there a more appropriate place to ask? This would affect all Android Devices that have a USB Host Port...
Now, the G Tablet, VEGAn mod at least... has the UVC Driver for WebCams. When I plug a camera in I get the /dev/video0 device (which doesn't exist until I plug in a camera.) - could it be permissions or is the driver not fully implemented?
The mplayer app that was released sets the root path to /sdcard so I can't point it at /dev/video0... I've tried to use the stream part, but it just exits the video - no error that I can see...
adamsoutherland said:
Now, the G Tablet, VEGAn mod at least... has the UVC Driver for WebCams. When I plug a camera in I get the /dev/video0 device (which doesn't exist until I plug in a camera.) - could it be permissions or is the driver not fully implemented?
Click to expand...
Click to collapse
The device appearing is a good first sign. Can you get me a dmesg output after you've plugged the webcam in? Run a Terminal Emulator app, then type in the window:
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
The mplayer app that was released sets the root path to /sdcard so I can't point it at /dev/video0... I've tried to use the stream part, but it just exits the video - no error that I can see...
Click to expand...
Click to collapse
Is this app an Android port of the standard mplayer for Linux? If yes, then it will use the V4L (Video 4 Linux) API to grab video frames, and if you can start it on the command line (or supply an input file name), then you can try "tv://" as the input file name.
Run this command first, though, to give everybody read-write access to /dev/video0:
Code:
$ [B]su[/B]
# [B]chmod 666 /dev/video0[/B]
I'm attaching a dmesg prior to plugging in the camera, and one after... I'm also inserting the text of the "diff" in the post...
Code:
[ 189.574313] usb 1-1.1: new high speed USB device using tegra-ehci and address 3
[ 189.657223] usb 1-1.1: New USB device found, idVendor=18ec, idProduct=3299
[ 189.664506] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 189.671944] usb 1-1.1: Product: USB2.0 PC CAMERA
[ 189.677125] usb 1-1.1: Manufacturer: ARKMICRO
[ 189.685907] usb 1-1.1: configuration #1 chosen from 1 choice
[ 189.695760] uvcvideo: Found UVC 1.00 device USB2.0 PC CAMERA (18ec:3299)
[ 189.708989] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
[ 189.732392] input: USB2.0 PC CAMERA as /devices/platform/tegra-ehci.2/usb1/1-1/1-1.1/1-1.1:1.0/input/input7
[ 190.318832] SO340010: gpio_val=0xc0a50000, button_val = 0xdbaf0002
[ 190.445387] SO340010: gpio_val=0xc0a50000, button_val = 0xdbaf0000
and this:
Code:
/data/data/berserker.android.apps.sshdroid/home # ls -lh /dev/vid*
crw-rw---- 1 0 1006 81, 0 Sep 2 18:22 /dev/video0
I've also done this:
Code:
/data/data/berserker.android.apps.sshdroid/home # chmod 666 /dev/video0
/data/data/berserker.android.apps.sshdroid/home # cat /dev/video0 /mnt/sdcard/test.mpg
cat: read error: No such device
/data/data/berserker.android.apps.sshdroid/home # ls -lh /dev/vid*
crw-rw-rw- 1 0 1006 81, 0 Sep 2 18:22 /dev/video0
/data/data/berserker.android.apps.sshdroid/home #
The mplayer was an APK from someone on the forums... I've opened it up only to find a "mplayer.so" as I thought it might contain the mplayer binary... (I don't have a machine (with sufficient space) to load the Android SDK at the moment...) (It's on my todo list.)
Am I right to try "cat /dev/video0" before I find the proper mplayer or event ffmpeg binary? (It generally works in linux when I do it...)
PS - I have 3 WebCams, I can give you a dmesg of each one if you need it... They all appear to do the same thing (they are by different manufacturers... iMicro, Sabrent and Agama.) -- also note that these 3 web cams work in Linux (each slightly different, but they work.)
adamsoutherland said:
The mplayer was an APK from someone on the forums... I've opened it up only to find a "mplayer.so" as I thought it might contain the mplayer binary... (I don't have a machine (with sufficient space) to load the Android SDK at the moment...) (It's on my todo list.)
Click to expand...
Click to collapse
Attach the APK so I can have a look at it.
Am I right to try "cat /dev/video0" before I find the proper mplayer or event ffmpeg binary? (It generally works in linux when I do it...)
Click to expand...
Click to collapse
I'm surprised that that works even on standard Linux! You have to setup the frame capture parameters first using ioctl()s before you can start reading data from /dev/video0. Even after that, you get raw frame data, and not mpeg video from the device.
PS - I have 3 WebCams, I can give you a dmesg of each one if you need it... They all appear to do the same thing (they are by different manufacturers... iMicro, Sabrent and Agama.) -- also note that these 3 web cams work in Linux (each slightly different, but they work.)
Click to expand...
Click to collapse
Attach all the 3 webcams to your desktop machine, check that each one works and get me a dmesg and a lsmod command output for each one. I want to see what drivers are loaded for each one. We'll have to load the same drivers on the gTablet too after compiling them.
Code:
[I]Attach Camera1 and make sure its working, then,[/I]
desktop$ [B]dmesg > dmesg1.txt[/B]
desktop$ [B]lsmod > lsmod1.txt[/B]
[I]Attach Camera2 and make sure its working, then,[/I]
desktop$ [B]dmesg > dmesg2.txt[/B]
desktop$ [B]lsmod > lsmod2.txt[/B]
[I]Attach Camera3 and make sure its working, then,[/I]
desktop$ [B]dmesg > dmesg3.txt[/B]
desktop$ [B]lsmod > lsmod3.txt[/B]
Caveats: Even if we get all the drivers to load on the gTablet (the V4L drivers, the main camera driver, and, possibly, its support drivers), we still have the problem of displaying the video stream on Android. While I'm happy to write whatever systems code is required, writing the Java UI code for the Android app is beyond my ken. We'll have to ask someone else (try in the main Android development forums on XDA, or, ask user herbert1 here who's helped out before with custom Java apps) once we've checked that we can read data from the V4L device (I'll send you a test prog which'll output .jpg files once every second once we have the drivers sorted out).
It would be great if someone has already ported mplayer for Android.
I'm attaching the APK I found...
Side note:
After looking deeper at 'cat /dev/video0'; it does not work with these webcams... I think this works on my TV Cards that natively displayed mpeg2 video (it's been a while).
See the attached dmesg-*.txt and lsmod-*.txt. Each is named after the company logo on the camera. (I can get the model numbers if the dmesg isn't enough.) Between each dmesg I rebooted the linux box for clarity. (They can all work at once, but I get confused on what is doing what.)
The command I used to test:
Code:
ffmpeg -f alsa -i hw:0,0 -f video4linux2 -s 320x240 -i /dev/video0 test-agama.mpg
(Each of these cameras has audio - The audio is not important for what I am attempting to do...)
About the UI... I've been avoiding this but it maybe time to start work on this =P -- I just realized that the box I'm testing the cameras on has space... I may have to reload linux for 64bit but then I can install the Android SDK and get to UI Development.
All three webcams seem to depend on only 3 kernel modules: uvcvideo, videodev and v4l1_compat.
If all 3 drivers are loaded on the gTablet too, then we should be able to get the video frames from /dev/video0 (or whatever the device).
I'll send you a test program this evening. In the mean time...:
That .apk file contains the application too--the classes.dex file contains the Dalvik executable bytecode. Just install the .apk, then run the app and provide a file name as input. Try "tv://" as the file name once all 3 drivers have been loaded. Do the "chmod 666 /dev/video0" before running the app.
Try the webcam test program in the attachment. The program reads from a user-specified V4L device and outputs JPEG images until you stop it with CTRL-C. Run as:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]mkdir /mnt/sdcard/tmp[/B] [I]Make a tmp dir. for storing imgs[/I]
# [B]./webcam -o /mnt/sdcard/tmp[/B] [I]Capture webcam images until stopped with CTRL-C[/I]
Get usage instructions with "./webcam --help".
EDIT: I actually didn't test the program out because I couldn't locate my webcam. Report if you encounter any bugs.
Quick Update:
I will be trying this tonight... I've been busy trying to get things done. (Little one is going to be born tomorrow!)
Sorry I haven't been able to respond sooner...
rajeevvp said:
Try the webcam test program in the attachment. The program reads from a user-specified V4L device and outputs JPEG images until you stop it with CTRL-C. Run as:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]mkdir /mnt/sdcard/tmp[/B] [I]Make a tmp dir. for storing imgs[/I]
# [B]./webcam -o /mnt/sdcard/tmp[/B] [I]Capture webcam images until stopped with CTRL-C[/I]
Get usage instructions with "./webcam --help".
EDIT: I actually didn't test the program out because I couldn't locate my webcam. Report if you encounter any bugs.
Click to expand...
Click to collapse
I copied it to /mnt/asec (because I can execute things there without remount)
When I run it, i get:
Code:
/mnt/asec # ./webcam -o /mnt/asec/tmp -d /dev/video0
./webcam: error getting video channel info. Invalid argument
I tried without the -d /dev/video0 and got the same result.
(Sorry for the LOOONG delay... Turns out a newborn takes more time and energy than I expected. I'm just now figuring that out... =P It's worth it though.)
Try this simple USB Webcam test app in the attachment which works on VEGAn-Tab 7.1 and GtabComb* (which have the pershoot kernel).
1. Plug the USB webcam in.
Assuming the kernel you're running has the correct USB webcam drivers compiled in--and, most of them do seem to have the V4L subsystem and the UVC camera drivers (which supports a lot of the common USB webcams) built into the kernel--you should see a new /dev/video0 device file pop up.
2. Run these commands to set correct permissions and owners on the device file (some ROMs--eg. GtabCombOver--don't need it):
Code:
$ [B]su[/B]
# [B]chown system.camera /dev/video0[/B]
# [B]chmod 660 /dev/video0[/B]
(Note that if you unplug and replug the webcam, you'll have to re-run the commands on ROMs which don't set the correct permissions and owners.)
3. Now install and run the SimpleWebCam app.
If, for some reason, no /dev/video0 device is created, then your webcam may need different device drivers, which have not been compiled in (or not been written!), in which case you'll have to compile a new kernel with the correct drivers either built-in or as loadable modules. Nothing else described in this post will need change.
adamsoutherland said:
When I run it, i get:
Code:
/mnt/asec # ./webcam -o /mnt/asec/tmp -d /dev/video0
./webcam: error getting video channel info. Invalid argument
I tried without the -d /dev/video0 and got the same result.
Click to expand...
Click to collapse
Looks like I'll have to update the code to make the program use the V4L2 API instead.
Nexus 7
Just tested this on my Google Nexus 7 tablet and it worked fine, I didn't have to modify the permissions either,
PS, it is rooted, of sure if that makes much difference, will test it on my friends stock nexus 7 tomorrow
USB Camera App
I was able to get the app working on my rooted Nexus 7 4.2 and an unrooted Galaxy SIII . How hard would it be to add a video record function to the app?
droidoso said:
How hard would it be to add a video record function to the app?
Click to expand...
Click to collapse
If you want to do that, then it's better to compile a custom native camera-interface library which makes the USB webcam appear as a standard camera (--the rear one, usually). Then, you can use the standard apps to record videos.
See this thread for a precompiled binary and for the source.
Here is kernel module pack version 4.
The modules should load without any problems.
If you need more drivers, PM me the module name or the .config changes.
Installing:
Create a directory /data/local/modules and copy the *.ko files to /data/local/modules via your method of choice (e.g., Root Explorer)
Fix for hangs/stalls/lags, because of background disk I/O
Code:
su
cd /data/local/modules
insmod cfq-iosched.ko
echo cfq >/sys/block/mmcblk0/queue/scheduler
Modules for some Logitech Joysticks:
Code:
su
cd /data/local/modules
insmod ff-memless.ko
insmod hid-logitech.ko
Modules for IPSec VPN support:
Code:
su
cd /data/local/modules
insmod tun.ko
insmod ah4.ko
insmod xfrm_user.ko
insmod xfrm4_mode_tunnel.ko
Modules included are:
Code:
adi.ko
ah4.ko
cifs.ko
cfq-iosched.ko
deadline-iosched.ko
ff-memless.ko
gameport.ko
hid-logitech.ko
iforce.ko
ipip.ko
md4.ko
tun.ko
xfrm4_mode_tunnel.ko
xfrm_user.ko
The file config.txt in the zip archive is the actual .config used.
Howto build them?
Install chroot Ubuntu or any other distribution on your Prime.
chroot to the distribution
wget the kernel source from Asus
$ mkdir linux; cd linux
unpack the kernel source here
modify Makefile, Find the CFLAGS_MODULE line, add -fno-pic this flag to the end of the line: CFLAGS_MODULE = -fno-pic
$ zcat /proc/config.gz > .config
$ make oldconfig
modify .config or use "make menuconfig"
$ make -j5 modules
$ make modules_install
$ depmod -a
$ find /lib/modules/$(uname -r) -name '*.ko'
Module description:
+CONFIG_INET_XFRM_MODE_TUNNEL=m
+CONFIG_XFRM_USER=m
Support for IPsec user configuration interface used by native Linux tools.
Module: xfrm4_mode_tunnel.ko xfrm_user.ko
+CONFIG_NET_IPIP=m
IP tunneling
http://cateee.net/lkddb/web-lkddb/NET_IPIP.html
Module: ipip.ko
+CONFIG_INET_AH=m
Support for IPsec AH.
Module: ah4.ko
+CONFIG_TUN=m
http://cateee.net/lkddb/web-lkddb/TUN.html
TUN/TAP provides packet reception and transmission for user space programs. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program.
+CONFIG_HID_LOGITECH=m
+CONFIG_INPUT_FF_MEMLESS=m
Modules for Logitech FF pads, wheels, joysticks
Module: ff-memless.ko hid-logitech.ko
+CONFIG_GAMEPORT=m
+CONFIG_JOYSTICK_ADI=m
Logitech ADI digital joysticks and gamepads
Might not be needed on the prime, because there is no gameport
Module: gameport.ko adi.ko
+CONFIG_JOYSTICK_IFORCE=m
http://cateee.net/lkddb/web-lkddb/JOYSTICK_IFORCE.html
vendor: 044f ("ThrustMaster, Inc."), product: a01c
vendor: 046d ("Logitech, Inc."), product: c281 ("WingMan Force")
vendor: 046d ("Logitech, Inc."), product: c291 ("WingMan Formula Force")
vendor: 05ef ("AVB, Inc. [anko?]"), product: 020a ("Top Shot Pegasus Joystick")
vendor: 05ef ("AVB, Inc. [anko?]"), product: 8884 ("Mag Turbo Force Wheel")
vendor: 05ef ("AVB, Inc. [anko?]"), product: 8888 ("Top Shot Force Feedback Racing Wheel")
vendor: 061c ("Act Labs, Ltd"), product: c084
vendor: 061c ("Act Labs, Ltd"), product: c0a4
vendor: 06f8 ("Guillemot Corp."), product: 0001
vendor: 06f8 ("Guillemot Corp."), product: 0003
vendor: 06f8 ("Guillemot Corp."), product: 0004
vendor: 06f8 ("Guillemot Corp."), product: a302
Module: iforce.ko
+CONFIG_CIFS=m
+CONFIG_CRYPTO_MD4=m
This is the client VFS module for the Common Internet File System (CIFS) protocol which is the successor to the Server Message Block (SMB) protocol, the native file sharing mechanism for most early PC operating systems. The CIFS protocol is fully supported by file servers such as Windows 2000 (including Windows 2003, NT 4 and Windows XP) as well by Samba (which provides excellent CIFS server support for Linux and many other operating systems). Limited support for OS/2 and Windows ME and similar servers is provided as well.
Module: cifs.ko md4.ko
ChangeLog:
v4:
cfq-iosched.ko
deadline-iosched.ko
v3:
added cifs.ko
v2:
stripped the modules from the debug symbols, package is much smaller now
Version 2 now a lot smaller, because the debugging symbols have been removed.
added cifs.ko
Could you attach the .config you're using?
Thanks
curreyr said:
Could you attach the .config you're using?
Thanks
Click to expand...
Click to collapse
It's in the zip-file ... "config.txt"
Any list as to what each of these new driver modules included goes with? are these like controller drivers or different/new USB drivers not included on stock prime. just trying to find out what each of them go to.
kind of surprised to see:
# CONFIG_CRYPTO_DEV_TEGRA_AES is not set
My initial looking indicates that unless that's baked in, android might not make use of it
I'll research a bit more tho.
Should be useful when we can get custom ROMs in the oven!
demandarin said:
Any list as to what each of these new driver modules included goes with? are these like controller drivers or different/new USB drivers not included on stock prime. just trying to find out what each of them go to.
Click to expand...
Click to collapse
Added some more information about the modules, what I could find quickly..
Did you explicitly use the NDK to cross-compile? Or did the package from Asus just work?
Noxious Ninja said:
Did you explicitly use the NDK to cross-compile? Or did the package from Asus just work?
Click to expand...
Click to collapse
The package from Asus just works for the modules at least.
Noxious Ninja said:
Did you explicitly use the NDK to cross-compile? Or did the package from Asus just work?
Click to expand...
Click to collapse
Oh, and I didn't cross compile... I compiled natively on the Prime in a chrooted Ubuntu.
saturn_de said:
Oh, and I didn't cross compile... I compiled natively on the Prime in a chrooted Ubuntu.
Click to expand...
Click to collapse
Since Asus had only release .7 kernel version, I assume this would not be with source from latest ota.
I plan to try it on .11ota. Have anyone successfully use it on latest ota?
Thanks.
warmRLS1+Anthrax
saturn_de said:
Oh, and I didn't cross compile... I compiled natively on the Prime in a chrooted Ubuntu.
Click to expand...
Click to collapse
Oh, cool. I didn't even think to try that.
Noxious Ninja said:
Oh, cool. I didn't even think to try that.
Click to expand...
Click to collapse
Yeah, you can "make modules_install; depmod -a" and afterwards you can "modprobe" any modules without thinking about the dependencies
huytrang90 said:
Since Asus had only release .7 kernel version, I assume this would not be with source from latest ota.
I plan to try it on .11ota. Have anyone successfully use it on latest ota?
Thanks.
warmRLS1+Anthrax
Click to expand...
Click to collapse
Well, it's kernel version 2.6.39.4 in all ICS Prime version so far.
saturn_de said:
Well, it's kernel version 2.6.39.4 in all ICS Prime version so far.
Click to expand...
Click to collapse
Yea the kernel is the same and the modules work fine for me on .11
This might not be the correct place for this and if so I apologize.
Is this thread about finding/compiling drivers for things so that they will work when plugged into the usb port on the keyboard dock? If so how would I go about making this usb headset work?
http://h10025.www1.hp.com/ewfrf/wc/...n&lc=en&product=4085832&task=prodinfoCategory
Again I am sorry if I have totally misunderstood the point of this thread. Thanks!
version 4 now with:
cfq-iosched.ko
deadline-iosched.ko
Fix for hangs/stalls/lags, because of background disk I/O
Code:
su
cd /data/local/modules
insmod cfq-iosched.ko
echo cfq >/sys/block/mmcblk0/queue/scheduler
Nico^APEX said:
This might not be the correct place for this and if so I apologize.
Is this thread about finding/compiling drivers for things so that they will work when plugged into the usb port on the keyboard dock? If so how would I go about making this usb headset work?
http://h10025.www1.hp.com/ewfrf/wc/...n&lc=en&product=4085832&task=prodinfoCategory
Again I am sorry if I have totally misunderstood the point of this thread. Thanks!
Click to expand...
Click to collapse
Ok, boot your PC/Laptop from a Linux Live CD or a locally installed Linux. Log in, start a terminal, plug in the headset and show me the output of:
# dmesg | tail -20
# lsusb
# lsmod
It is possible to get Google Play Store perfectly running on Acer CB C720P,
off the USB 3.0 port using a USB 3.0 bootable stick with the recovery rom for Acer Chromebook R11 - it needs adjustments, & a version of Chromium OS above 55 like https://www.dropbox.com/s/kebu46foi6quu96/Camd64OS_R55-8777.0-Special.7z?dl=0
(use WIndows Diskimager to map it to usb stick, then expand the data partition file system to use up all the disk)
A great how-to for this method & the chromefy method is in post 163 by Hnk1,
https://forum.xda-developers.com/showpost.php?p=78806350&postcount=163
Hnk1 said:
https://forum.xda-developers.com/ha...er-c720p-getting-google-t3805304/post78806350
Request : Can you put the link (one I mentioned above, post # 163 )in the first post mate ? So more people can install it on their CB and it will be easier to see. What you reckon?
Click to expand...
Click to collapse
Do not use this, latest cyan Acer C720P CB will not allow booting. Acer & Google teamed up to block this hack -
New recovery roms as per June 2018: https://www.dropbox.com/s/0lh7zamkntisdum/recovery2018_2.conf?dl=0
https://twitter.com/meNabster/status/1012024823885844488
https://twitter.com/inabster/status/1012029701119004673
Use this -
Recovery roms links as per May 2018 in this link: https://www.dropbox.com/s/zje8hlg7fmvp48d/recovery_2008.conf?dl=0
Up to date recovery roms are here:
https://dl.google.com/dl/edgedl/chromeos/recovery/recovery.conf
& adapting this script I hacked:
sudo apt-get install cgpt
# this is if you are doing it from a linux distro or via crouton, cgpt is available natively in the chronos shell...
image_file=chromeos_5841.98.0_link_recovery_stable-channel_mp-v4.bin # the rom you need is cyan for Acer Chromebook R11 (CB5-132T / C738T)
rootfs_start="`cgpt show -i 3 -n -b -q $image_file`"
rootfs_size="`cgpt show -i 3 -n -s -q $image_file`"
mkdir chrome_efi_mount
sudo mount /dev/sdb12 chrome_efi_mount -t vfat
mkdir chromium_efi_mount
sudo mount -ro loop,offset=$((`cgpt show -i 12 -n -b -q $image_file`*512)) $image_file chromium_efi_mount
sudo cp chromium_efi_mount/syslinux/vmlinuz.B chrome_efi_mount/syslinux/vmlinuz.B -f
sudo cp chromium_efi_mount/syslinux/vmlinuz.B chrome_efi_mount/syslinux/vmlinuz.A -f
sudo umount chrome_efi_mount
sudo umount chromium_efi_mount
sudo dd if=$image_file of=/dev/sdb3 bs=512 skip=$rootfs_start count=$rootfs_size
Sorry for now too lazy to write a full step by step how to...
Here are exhibits on my twitter feed
https://twitter.com/inabster/status/1007856882738978816
Hello,
The link to download the rom on dropbox was truncated - can you post it as code ?
Thanks.
guyome said:
Hello,
The link to download the rom on dropbox was truncated - can you post it as code ?
Thanks.
Click to expand...
Click to collapse
The link to recovery_2008.conf is in dropbox, I can access it, so should you.
look up for the rom link in the recovery_2008.conf file.
as I suspect you are lazy, here is the entry:
name=Acer Chromebook R11 (CB5-132T / C738T)
version=10323.62.0
desc=
channel=stable-channel
hwidmatch=^CYAN .*
hwid=
md5=27ae1147ec3984f698a7b7d17a19b676
sha1=e570292bb40155d9de96369e3c9f493369bbc7b5
zipfilesize=1100976852
file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
filesize=2271232512
url=https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin.zip
misc notes Google Play Store on USB stick Acer C720P
Some notes:
Kernel versions -
Official Kernel for Acer Chromebook C720P: (no Play Store)
Linux localhost 3.8.11 #1 SMP Sat Jun 16 19:11:45 PDT 2018 x86_64 Intel(R) Celeron(R) 2955U @ 1.40GHz GenuineIntel GNU/Linux
Official Kernel for Acer Chromebook R11 (CB5-132T / C738T) after Play Store update (which is already in the recovery rom):
Linux localhost 3.18.0-16509-gfd728222c3ad-dirty #1 SMP PREEMPT Tue Mar 20 23:42:10 PDT 2018 x86_64 Intel(R) Celeron(R) 2955U @ 1.40GHz GenuineIntel GNU/Linux
Official Kernel for Asus Chromebit CS10 as per latest update: (no Play Store yet, though planned)
Linux localhost 3.14.0 #1 SMP PREEMPT Fri Jun 15 04:13:16 PDT 2018 armv7l ARMv7 Processor rev 1 (v7l) Rockchip (Device Tree) GNU/Linux
To me Google is playing to force consumers to buy newer machines, it's a capitalist move, Play Store runs perfectly on Acer C720P, & Google Chrome OS is far more stable & snappy than with Kernel 3.8 they want to keep.
It will be cool if a good firmware coder could flash the firmware of C720P making it look like an Acer CB R11 - that will allow to install the R11 recovery rom onto the C720P SSD - so not having to go through putting it on a usb stick, though personally, it doesn't bother me.
This would be redundant if Google + Acer decide to officially support C720P - instead of being greedy.
https://twitter.com/inabster/status/1008526962439147520
Here are exhibits on my twitter feed
https://twitter.com/inabster/status/1007856882738978816
Hello,
Thank you for your answer, but I was speaking of this link : https://www.dropbox.com/s/kebu46foi6...pecial.7z?dl=0
Regards
---------- Post added at 10:24 AM ---------- Previous post was at 10:01 AM ----------
Ok, I found the recovery rom for Acer R11 thanks to your post - it was indeed in the conf file.
After, I put this Rom on a usb stick with Windows Diskimager - Ok
Then, I enter the recovery mode on the C720P by holding the Esc and Refresh keys then pressing the power button, and I restore the image on the USB key, so the Acer R11 image - OK
After, what do I do ? Restart the C720P ? Where should I use your script lines ?
Thanks !
guyome said:
Hello,
Thank you for your answer, but I was speaking of this link : https://www.dropbox.com/s/kebu46foi6...pecial.7z?dl=0
Regards
Click to expand...
Click to collapse
OK I regenerated the link, for some reason dropbox removed the share
https://www.dropbox.com/s/kebu46foi6quu96/Camd64OS_R55-8777.0-Special.7z?dl=0
this is what you need imaging to a usb stick.
then boot to the chromebook & apply the script from a shell, with the usb having chromium R55.
Here are instructions on how to do
step one - install chromium OS to the usb stick -
https://arnoldthebat.co.uk/wordpress/chromium-os/
step two - apply the script with assumed /dev/sdb being your usb device (with chromium OS in it, which you modify using the R11 Chrome OS image from Acer/Google.
Will this work on a standard C720 (not a touchscreen)
TheDevFreak said:
Will this work on a standard C720 (not a touchscreen)
Click to expand...
Click to collapse
Test it, & report
The odd bit:
Image recovery for C740 does not work, even though C720 & C740 are very similar.
Also using latest chromium OS 67 (arnoldthebat) will not work.
What I got working is Chrome OS R11 recovery with the arnoldthebat chromium OS rom I linked to above, others might work, but I posted what was successful, so I provided the links to them on my dropbox.
https://twitter.com/inabster/status/1009289981024702466
! @arnoldthebat latest special build Camd64OS_R67-10575.B-Special doesn't boot on Acer W700 hybrid tablet, Apple Macbook Air 2011, and Acer CB C720P (+only efi no mbr) -
your old build Camd64OS_R55-8777.0-Special works on all (efi+mbr) - I use it for this: https://forum.xda-developers.com/ha...er-c720p-getting-google-t3805304#post76864776
Thanks for the dropbox link
Ok, if I have understood everything :
- I install chromium OS on the USB key - the file is the one on Dropbox Camd64OS_R55-8777.0-Special.7z
- I copy the recovery image of the Acer R11 - link provided in the conf file - so chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
- I boot the chromebook, and plug the USB Key
- I launch a shell session (no need to be in developpper mode ?)
- I execute your script lines but should not the second line be "image_file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin" instead of "image_file=chromeos_5841.98.0_link_recovery_stable-channel_mp-v4.bin" , so the name of the downloaded recovery image ?
Thank you for your answers
Of course -
image_file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
guyome said:
Thanks for the dropbox link
Ok, if I have understood everything :
- I install chromium OS on the USB key - the file is the one on Dropbox Camd64OS_R55-8777.0-Special.7z
- I copy the recovery image of the Acer R11 - link provided in the conf file - so chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
- I boot the chromebook, and plug the USB Key
- I launch a shell session (no need to be in developpper mode ?)
- I execute your script lines but should not the second line be "image_file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin" instead of "image_file=chromeos_5841.98.0_link_recovery_stable-channel_mp-v4.bin" , so the name of the downloaded recovery image ?
Thank you for your answers
Click to expand...
Click to collapse
And no developpper mode needed to execute your script lines ? Thanks
And I have to boot on the usb stick with chromium ? With CTRL+U starting in developper mode ?
Wow I can't believe this! Can't wait to try on mine. I always thought it would be able to get android play store/apps on it! Waiting to see how it all works out and will try to install soon. Thanks so much to the OP for this, so stoked to see someone has managed to do this!
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
guyome said:
And I have to boot on the usb stick with chromium ? With CTRL+U starting in developper mode ?
Click to expand...
Click to collapse
How'd you get on installing this? Did you get it up and running?
I am trying to find how it works for the moment - I think I know almost all the steps to be done
guyome said:
I am trying to find how it works for the moment - I think I know almost all the steps to be done
Click to expand...
Click to collapse
Please let me know if/when successful. I believe I understand it in the main, but waiting to hear re your question whether we need the Chromebook in dev mode. Mine currently is as have Linux xfce on it as well as the stock dev chrome OS image. I assume though that as this installs on the USB as opposed to the internal SSD, that chances of breaking the Chromebook as pretty remote, as you can pull the USB and go back to the internal SSD...I await your attempt!
I think that you have to boot on the USB key containing Chromium OS and the image file you want to deploy, and then execute the command lines in a shell in order to install the image on the Chromebook. After, you should be able to remove the USB key and to boot on the SSD with the new deployed image (one of Acer R11)
You need to be in developer mode to boot from usb.
guyome said:
And no developpper mode needed to execute your script lines ? Thanks
Click to expand...
Click to collapse
No, ctrl-L
guyome said:
And I have to boot on the usb stick with chromium ? With CTRL+U starting in developper mode ?
Click to expand...
Click to collapse