[Q] Building Rom on External Hard Drive - PAC Q&A

I don't have much space on my computer anymore, but I do have a 1 TB external hard drive. WOuld it be possible for me to download all the PAC sources to it and build roms on it while its hooked up to my computer? I assume that builds would take a lot longer, but I just want to know if its possible

dragid10 said:
I don't have much space on my computer anymore, but I do have a 1 TB external hard drive. WOuld it be possible for me to download all the PAC sources to it and build roms on it while its hooked up to my computer? I assume that builds would take a lot longer, but I just want to know if its possible
Click to expand...
Click to collapse
Where you locate your source files really doesn't matter as long as you have all the necessary prerequisites to build, e.g. gcc, java, SDK, etc. You may have to play with your environment variables to get the system to locate stuff properly, though.

Related

[Android] AOSP 2.0.1 Proof-of-Concept Build. Assistance appreciated.

Tonight I managed to get my first Android build, 2.0.1, compiled myself from AOSP, up and running on the Vogue from NAND.
I made some small changes, most notably, updating the build.prop to adjust the DPI to 120 and adding the libhtcgeneric_ril.so library, as well as adding the necessary (or.. is it necessary?) build.prop entry to get the radio functioning.
I proudly present my first Android build.
NOTE: This is purely for testing/evaluation purposes.
Working:
Radio
Data
Screen resolution is accurate
Not Working:
Audio
Power Functionality (buttons do not wake the phone?)
GPS
Anyone up for pointing out what I need to do differently to get the non-working aspects functioning? Any tips on optimization? Clues to setup and take full advantage of build.prop?
Additionally, do we have a central repository of Vogue (or MSM7k) drivers that've been ported as source, ready to be compiled for different versions?
There's probably a lot missing here that I'm not even considering.. so please feel free to make any comments, give any advice, or point me towards any documentation.
All help is appreciated. Thanks!
I think this is the repo you're looking for:
http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi
It contains Audio & GPS drivers, among other things. Can you wake the phone over adb shell with the command echo "wake" > /sys/android_power/request_state ? I'm also interested in getting an AOSP build running from source, I'd like to get the camera working for Eclair.
EDIT: Also, in the zenulator's eclair mod, the /system/etc/keychars directory contains these files:
Code:
htcvogue-ts.kcm.bin
qwerty2.kcm.bin
qwerty.kcm.bin
sapphire-keypad.kcm.bin
trout-keypad.kcm.bin
trout-keypad-qwertz.kcm.bin
trout-keypad-v2.kcm.bin
trout-keypad-v3.kcm.bin
tuttle2.kcm.bin
vogue-ts.kcm.bin
Perhaps that vogue binary is needed? That's my shot in the dark.
Those files are just for the keymapping, nothing more..
polyrhythmic said:
I think this is the repo you're looking for:
http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi
It contains Audio & GPS drivers, among other things. Can you wake the phone over adb shell with the command echo "wake" > /sys/android_power/request_state ? I'm also interested in getting an AOSP build running from source, I'd like to get the camera working for Eclair.
EDIT: Also, in the zenulator's eclair mod, the /system/etc/keychars directory contains these files:
Code:
htcvogue-ts.kcm.bin
qwerty2.kcm.bin
qwerty.kcm.bin
sapphire-keypad.kcm.bin
trout-keypad.kcm.bin
trout-keypad-qwertz.kcm.bin
trout-keypad-v2.kcm.bin
trout-keypad-v3.kcm.bin
tuttle2.kcm.bin
vogue-ts.kcm.bin
Perhaps that vogue binary is needed? That's my shot in the dark.
Click to expand...
Click to collapse
What's responsible (or handles) power management, then?
And why are there so many keymapping files? According to AOSP, Android will default to qwerty.kl, and certainly with the Vogue being as simple as it is, a single qwerty.kl set up for the Vogue would be sufficient.
So what gives? Or are these files all leftover as this was "ported", and they existed to support previous devices, etc.?
first off great job. this is exactly how i started out by building my own builds from source and then taking apart others to see what fits together. if i have time this weeked i'll have a look at it.
There are an awful lot of moving parts in power management in Android (and any OS, really) - there's the kernel's power subsystem which controls deep sleep / suspend, and which Android attaches a "wakelock" system to, each radio lib (Bluetooth, WiFi, phone) has power management (which hooks up to kernel interfaces), there's the panel driver which controls brightness, etc.
I think the keymapping files are just there so that no matter which one the framework looks for, it always finds one, speeding things up - rather than having to try to find each one and failing down until it finds its eventual failsafe qwerty, it loads the Vogue one straight away.
Awesome man, way to go!
Can you throw in links for rootfs/zimage, I will try later today on my wife's phone.
Thanks sshark, I would, but I've been tweaking that image continuously and at it's current state, it's broken.
Here are the major hurdles I'm facing right now:
How do I determine which drivers are and are not necessary in a build? If we use an AOSP build, or someone else's port, obviously we don't want audio drivers from the Nexus One or generic Goldfish sensors from AOSP, so how can we know what we need to be able to keep images clean?
Along the same vein, how does one incorporate drivers accordingly, such as audio?
Is power management really a dark art right now? Plemen's AOSP build is fantastic, but I typically have to push the power button four times to get the OS to wake up, whereas a 2.1 build I just played with on the Vogue would power up right away on one click. What gives?
When compiling images using genext2fs, does 80000 vs 160000 matter, NAND vs HaRET booting? What's the maximum?
Lastly, I've recently tried unsquashing others images, making changes, and then trying to re-ext2 them, mount them, and squash them. However, when I do this, my images no longer boot fully on my Vogue--instead they'll get as far as the boot animation, it'll run for a bit, and then the boot animation will pause for a second or two, and restart. This happens endlessly. Is this a problem with my process, be it ext2, sqsh (sqsh version, perhaps?) anyone have an idea?
Shidell said:
Thanks sshark, I would, but I've been tweaking that image continuously and at it's current state, it's broken.
Here are the major hurdles I'm facing right now:
How do I determine which drivers are and are not necessary in a build? If we use an AOSP build, or someone else's port, obviously we don't want audio drivers from the Nexus One or generic Goldfish sensors from AOSP, so how can we know what we need to be able to keep images clean?
Along the same vein, how does one incorporate drivers accordingly, such as audio?
Is power management really a dark art right now? Plemen's AOSP build is fantastic, but I typically have to push the power button four times to get the OS to wake up, whereas a 2.1 build I just played with on the Vogue would power up right away on one click. What gives?
When compiling images using genext2fs, does 80000 vs 160000 matter, NAND vs HaRET booting? What's the maximum?
Lastly, I've recently tried unsquashing others images, making changes, and then trying to re-ext2 them, mount them, and squash them. However, when I do this, my images no longer boot fully on my Vogue--instead they'll get as far as the boot animation, it'll run for a bit, and then the boot animation will pause for a second or two, and restart. This happens endlessly. Is this a problem with my process, be it ext2, sqsh (sqsh version, perhaps?) anyone have an idea?
Click to expand...
Click to collapse
i cant answer all of those questions, with that said ill tackle the last two
4. when using genext2fs to compile builds it doesnt matter what the -b count is we just use
Code:
genext2fs -d ./system -b [B]180000[/B] -a system.ext2
to make sure we could fit a ~180 mb system so if your system folder is ~120mb(uncompressed), using -b 125000 should work.
5. make sure you arent using squashfs-tools 4.0 because it isnt supported in our kernel version. so use 3.3 or 3.1 .
5b. when you see the boot logo looping, that means the build has crashed and like i said to you before i strongly recommend you setup adb on you box so you can run logcat to see what the phone is actually doing and to debug what went wrong and why it is looping
Thanks Jamezelle. So NAND users need to make sure it's -b 90000 (or less), as NAND only supports 90 mb. max, correct?
Shidell said:
Thanks Jamezelle. So NAND users need to make sure it's -b 90000 (or less), as NAND only supports 90 mb. max, correct?
Click to expand...
Click to collapse
right i would keep it around 88 to be safe.
I'm trying to get ADB to work (using ubuntu 9.10) and I've followed the instructions here, including restarting udev, but even still when I try to start adb, I get "command not found" in terminal.
Any ideas on what I'm missing?
EDIT: I'm missing a ./. I'm really starting to wish I could do this natively in Windows.. geeze.
Shidell said:
I'm trying to get ADB to work (using ubuntu 9.10) and I've followed the instructions here, including restarting udev, but even still when I try to start adb, I get "command not found" in terminal.
Any ideas on what I'm missing?
EDIT: I'm missing a ./. I'm really starting to wish I could do this natively in Windows.. geeze.
Click to expand...
Click to collapse
did you make sure you added the path to adb in .bashrc
# On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ directory to it. If you don't see a line setting the path, you can add one:
Code:
export PATH=${PATH}:<your_sdk_dir>/tools
Click to expand...
Click to collapse
that should clear up the "Command not found" issue
jamezelle said:
did you make sure you added the path to adb in .bashrc
that should clear up the "Command not found" issue
Click to expand...
Click to collapse
Yep, that was the issue. It needs to be there, or launched as ./, I presume.
Thanks much for your help tonight, Jamezelle.. I'm happy to report that I'm steadily making progress for a working release.
Shidell said:
Yep, that was the issue. It needs to be there, or launched as ./, I presume.
Thanks much for your help tonight, Jamezelle.. I'm happy to report that I'm steadily making progress for a working release.
Click to expand...
Click to collapse
thats great to hear, also thanks for your additions to the libgps.so! its nice to still see some android enthusiasm in this community

[Dev] Native linux on Iconia

So, let's get linux installed natively on our Iconia.
As some of you I have been working on porting Iconia to chromeos 2.6.38 kernel (to get rid of Acer crappy moron-written drivers (well.. nothing personal, but most code written for commercial embedded devices is a pile of crap and you have to rewrite everything to update kernel or integrate upstream))
For now, I have hardcoded the kernel command line in the boot config to boot off /dev/mmcblk1p2 (that is, you must create ext4 (this is also hardcoded.. uhh)) second primary partition on your sd card with the root fs). For now, until all hardware is working fine and userland is ready, let's boot off micro sd. We don't have nvflash yet so let's leave repartitioning internal storage aside.
Flash the kernel image instead of boot.img to LNX or instead of recovery to SOS. And make sure to write your UID in a secure place before messing with the device - this is the only way to flash your device if you have checksum errors (you should contact sc2k in that case). Okay, even if you eff up here, there is still a way to get UID from a brick so take it easy. But if you do screw it, be prepared to work hard and use some command-line tools.
You should be able to use any armel rootfs. For X11, use fbdev driver and evdev for touchscreen.
For the proprietary NVIDIA accellerated drivers for X11, OpenGL ES and OpenMAX, download the nvidia-tegra package from AC100 PPA https://launchpad.net/~ac100/+archive/ppa (probably you have to manually download using this link http://ppa.launchpad.net/ac100/ppa/...dia-tegra_12-0ubuntu1~alpha1monson6_armel.deb as the package didn't show in aptitude for me after adding to sources.list.. or i was doing sth wrong) or the tarball from nvidia. A newer package of tegra drivers is available at https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-tegra. You may just add an alternative to mesa EGL/GLES library path via update-alternatives to always use nvidia libs.
precompiled kernel image [15 August 2012]
http://www.mediafire.com/?p32l949n2s7la43
xorg.conf
http://pastebin.com/0a6T6c18
Here is some video
http://www.youtube.com/watch?v=NlGHZ5VTAr8
And now - we need developers, developers, developers.
The git is https://github.com/astarasikov/iconia-gnu-kernel
The main branch is chromeos-2.6.38 that is more stable. The 3.0 branch is unstable (network traffic causes virtual memory trashing).
For now, the following stuff works
-Panel/framebuffer/backlight
-Touchscreen
-Internal eMMC
-microSD slot
-usb gadget
-usb host
-gpio keys/buttons [rotation switch acts as wifi/bluetooth power blocker. iirc, left position disables wireless, right - enables]
-charger
-battery
-shutdown
-LEDs
-bcm4329 wifi (don't forget to copy bcm4329-fullmac-4.bin to /lib/firmware/brcm and nvram.txt from android's /system/etc to the same dir as bcm4329-fullmac-4.txt) [causes lockups with 3.0 kernel]
-nct1008 temperature sensor for cpu throttling
-sound. external speakers and headphones.
-bcm4329 bluetooth. accessible at 115200 on /dev/ttyHS2. Look at http://htc-linux.org/wiki/index.php?title=Ubuntu/Leo/Bluetooth to get it running at higher speeds with proprietary firmware patches (hcd files from android)
-suspend. Although will probably drain a bit more power than android because mmc power is not disabled (due to a race condition in kernel. and because we have rootfs on micro sd). Two glitches are: sometimes, the device freezes for several seconds after suspend (will test later if playing with wifi clock fixes it) and fonts get corrupted after suspend if using proprietary nvidia X11 driver. [suspend works in 2.6.38 only]
-kxtf9 accelerometer
-mpu3050 gyroscope
-ak8975 magnetometer
The following stuff is broken or not implemented at all
-hdmi video. May be working but no one has tested. hdmi audio is not implemented.
-light sensor
-video cameras, focus, torch.
-gps. To turn on the chip, it should be enough to enable gpio 203 via sysfs. Unfortunately it uses the proprietary MEIF protocol which can probably be obtained from Nokia under NDA. And I don't feel like disassembling the whole megabyte of the gps daemon
-3G. I don't have the modem in my iconia. So I don't care. But should be easy to add.
And one notice for those who want to join in. I don't care if hardware works properly. I want 'beautiful' code. That is, please, when you make patches to add functionality, do not follow the path of corporate coders and do not invent custom interfaces and sysfs hacks. Use rfkill for bt/3g power control, for example. And don't be selfish - please share your patches and userland stuff.
TODO:
-fix framebuffer issues (no console till X boots, X fonts and window decorations get corrupted after suspend with proprietary drivers) it kinda works.
-video camera
-port meego or build the list of good software in ubuntu for handling sensors, virtual keyboard etc
I'm not currently working on the project and don't have the device anymore. Feel free to PM me if you need help with some tegra hackery
good job...
Hi sp3dev,
Cooooool, you rock
Thanks
FANTASTIC WORK!!!!
Guys... I'm not so clued up on the bootloader here, but is dual boot possible with this setup?
"so I guess I need to switch distro to try out this cool stuff"
What distro are you considering switching to?
tholmewood said:
FANTASTIC WORK!!!!
Guys... I'm not so clued up on the bootloader here, but is dual boot possible with this setup?
"so I guess I need to switch distro to try out this cool stuff"
What distro are you considering switching to?
Click to expand...
Click to collapse
Yes, dual boot is possible - the android is in internal memory, our stuff is on micro sd card. It should be possible to even dual boot from internal memory, but not right now
I am switching to ubuntu because it has a lot of packages prebuilt
sp3dev said:
Yes, dual boot is possible - the android is in internal memory, our stuff is on micro sd card. It should be possible to even dual boot from internal memory, but not right now
I am switching to ubuntu because it has a lot of packages prebuilt
Click to expand...
Click to collapse
Man I cant wait to get Netbook Remix dual booting on this badboy... Living the dream I tell ya...
Thanks again
Would booting a distro from say the usb work?
Sent from my HTC HD2 using XDA Premium App
M..N said:
Would booting a distro from say the usb work?
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
I see no reason why not. But you'd have to hardcode the uuid of the boot partition in kernel command line or build a ram disk. Anyway having to use a heavy and power consuming external storage sounds like an extremely stupid and useless idea
what about Gentoo?
This is great! i would love a dual boot. and ubuntu! i just got done reading that the asus got this and was like. i want it now. now we almost have it keep up the great work!
sp3dev said:
I see no reason why not. But you'd have to hardcode the uuid of the boot partition in kernel command line or build a ram disk. Anyway having to use a heavy and power consuming external storage sounds like an extremely stupid and useless idea
Click to expand...
Click to collapse
Not even from a USB flash drive? Wouldn't it be the same as say booting it from a microsd card?
Sent from my A500 using XDA Premium App
Have Anyone seen this LINK?
Hope it can help!
OrionBG said:
Have Anyone seen this LINK?
Hope it can help!
Click to expand...
Click to collapse
That sounds like the place to start!
Thanks
Thanks man you really rock !
I cant wait to try it out. Hope you will continue working onto this.
can you share the steps after compiling the kernel ?
I would like to try with different kernels but I'm still not confident on how to do this.
If I use dd if=zImage of=/dev/mmcblk00p1
will this effectively boot this kernel after pressing power and vol- keys ?
Hello, do you think that Dvb t is possible if Linux is running on the acer?
yodor said:
can you share the steps after compiling the kernel ?
I would like to try with different kernels but I'm still not confident on how to do this.
If I use dd if=zImage of=/dev/mmcblk00p1
will this effectively boot this kernel after pressing power and vol- keys ?
Click to expand...
Click to collapse
No.. You need to build boot image with android's mkbootimg and flash instead of recovery. And then, mkfs.ext4 on your sd card on partition mmcblk1p2 and untar rootfs there
Thanks man, this is really getting clear to me now.
I'm going to try and post results here. I will love to try and see how arch, fedora and ubuntu will run on A500.
http://dev.gentoo.org/~armin76/arm/tegra2/install.xml
There are two apps in the Android market that will install either Ubuntu or Backtrack for you- they are not native installs though I can confirm they perform well even if it is chroot and I can also confirm they work on the iconia great! Search ubuntu installer or backtrsck5 linux install in the mmarket....

Linux Distro dev edition

This distro was created with all the tools needed for android development. After you install this os, you're ready to start developing for Android.
GreenRom Dev Kt is now available. It has Android SDK/NDK, Eclipse, ADB(from any location!), ThemerStudio, all required dependencies for compiling roms, repo init for pulling source code from github, and Gimp for theming/editing graphics.
Q:Why is this important?
A:Because all you need to do is install this OS, plug in your phone, and begin having fun as you dev. There's no need to try and download and install ANYTHING for Android development because it's all been done for you. Do you need to run ADB Logcat? Go ahead. Now there's no need to make sure you're in a certain directory because you can run ADB from anywhere.
Some common questions might be:
Q:Do I have to install GRPdevkit to my HDD?
A:No, you can run it from live mode and store your progress on a pen drive. Alternately, you can install it on a pen/usb drive and run it from that if your bios detects usb drives.
Q:Will I be able to install this alongside another OS?
A:Possibly, although LivLogik and I haven't had any luck with dual booting this nor Ubuntu.
Q:Will this screw up my computer?
A:As with any Linux OS that's experimental, the possibility is there, although LivLogik and I have been testing this OS extensively to ensure all the bugs have been work out before making it available to you. Nevertheless, we are in no way responsible for your actions!
Q:What if I don't want to dev and just want to use this for an every day system?
A:That's quite fine as this OS is built from Linux Mint 11 and has all the stuff you probably use such as Brasero, X-Chat, Transmission, Libre Office, Movie Player, Calculator, Pidgin, G-Thumb, and much more!
Q:What if I can't burn an installation disk?
A:As with the majority of mainstream Linux Distros, we will be offering an installation disk for a small fee + s&h. LivLogik and I have to come up with a design for the cd decal as I have access to a cd printer. We will post the availability when we come up with it.
Q:How do I use the tools that are in this?
A:There is a get started guide on the desktop that you can move to your home folder or delete that explains briefly how to use the tools, however, I didn't include instructions on Eclipse as I've never used it. For Eclipse just go to it's website here: http://eclipsetutorial.sourceforge.net/totalbeginner.html and learn how to use it. Eclipse is used to make programs for Android.
LivLogik will be making a video so that you can see it in action. Enjoy!!
Note: you may need to right click on the desktop and change the wallpaper mode setting from zoom to whatever fits your screen best. -Fixed in update
**EDIT** if you have problems signing in to gtalk on the messanger... go to software manager and in the search box type in gtalk and download that plugin and it should work and if you have problems with anymore accounts like facebook do the same and it should work fine -Fixed in update
CLICK HERE TO VIEW THE VIDEO !!!! (it shows a run through of it and also sorta where everything is and a little how to - livlogik
Video #2 Updates For v1.1
============> grpdevkit.iso - 2.0 GB <============
MIRROR >>>---------------> http://dev-host.org/fj1lh8zu4g60/grpdevkit.iso <-----------------<<<
Code:
[color=green]Change Log: [/color]
(07-22-11 v1.1) :
~Added Chrome Browser
~Added plugin for Gtalk
~Shortcut for SDK/NDK in home folder
~Added shortcut for GRP forum
~Added different wallpaper([color=blue]thanks LivLogik[/color])
(6-?-11 v1) :
~Linux Mint 11(Katya) as Distro base [URL=http://www.linuxmint.com/]Linux Mint11[/URL]
~Remastersys(for building the distro [url]http://remastersys.sourceforge.net/[/url])
~Added GRP custom default wallpaper([color=blue]thanks LivLogik[/color])
~Added Android NDK
~Added Android SDK
~Added all required dependencies for compiling Android OS as follows:
git-core, gnupg, flex bison, gperf, libsdl1.2-dev, libesd0-dev, libwxgtk2.6-dev, squashfs-tools, build-essential zip curl, libncurses5-dev, zlib1g-dev,
sun-java6-jdk, pngcrush, schedtool, lib32z1-dev, lib32ncurses5-dev, lib32readline5-dev
~Added ADB( thanks to Tahl:[URL=http://www.rootzwiki.com/showthread.php?589-Android-SDK-NDK-Eclipse-and-ADB-Auto-Installer-(Ubuntu-Linux-Mint)]Tahl's tread[/URL])
~Added Gimp
~Added ThemerStudio(thanks to CorCor67:[URL=http://corcor67.blogspot.com/p/themer-studio.html]CorCor's blog[/URL])
~Added Repo Init to home directory
[color=red]Testers:[/color]
LivLogik
SlashDW
whoever else has tested or is running the Dev Kit let me know so I can include you in the testers credits. ;-)
epic!? I think so.
Treken said:
This distro was created with all the tools needed for android development. After you install this os, you're ready to start developing for Android. Check it out here: http://greenromproject.com/showthread.php?188-GreenRom-Dev-Kit-is-here!!-64bit(updated-7-23-11)
And, of course, enjoy!
Click to expand...
Click to collapse
Nice! This should save a ton of setup time when I install a new distro
Sent from my ADR6300 using XDA App
AWESOME! Finally, I can run Linux simply. Expect ROM's from me!
EASY Set-up! Now to figure out how to do everything else..... :/
Smokeey said:
EASY Set-up! Now to figure out how to do everything else..... :/
Click to expand...
Click to collapse
If you need some help with anything just let me know.
Wow. downloaded.
vassskk said:
Wow. downloaded.
Click to expand...
Click to collapse
how was the download speed? The server will be getting a make-over tomorrow and should beef up the download speed.
I'm assuming I can make this into a persistent usb and take it anywhere and work on it? Regardless I'm going to give it a shot.
DL started at 700 and dropped 1kB/s every 2 seconds continuously, then dropped out. I thought it was an artifact of the averaging done by Google Chrome; except it was linear, 2 seconds every time.
bogwurm said:
I'm assuming I can make this into a persistent usb and take it anywhere and work on it? Regardless I'm going to give it a shot.
Click to expand...
Click to collapse
Please see #2
Q: Do I have to install GRPdevkit to my HDD?
A: No, you can run it from live mode and store your progress on a pen drive. Alternately, you can install it on a pen/usb drive and run it from that if your bios detects usb drives.
vassskk said:
Please see #2
Q: Do I have to install GRPdevkit to my HDD?
A: No, you can run it from live mode and store your progress on a pen drive. Alternately, you can install it on a pen/usb drive and run it from that if your bios detects usb drives.
Click to expand...
Click to collapse
And boom goes the dynamite
/Dinc
Very nice work. Thanks for this.
Sent from my ADR6300 using XDA App
vassskk said:
DL started at 700 and dropped 1kB/s every 2 seconds continuously, then dropped out. I thought it was an artifact of the averaging done by Google Chrome; except it was linear, 2 seconds every time.
Click to expand...
Click to collapse
The server went down for a little bit. They beefed up the server speeds so it should download faster now. It should be up and running now
Great.. now I have to stop & get more DVDs. My old laptop doesn't boot from usb. Looking forward to trying it out. Thanks!
OP,
You said you were having trouble paralleling it with other os's? Any ideas why? i was very much hoping to throw it alongside joulicloud (ubuntu based) on my ssd.
vassskk said:
OP,
You said you were having trouble paralleling it with other os's? Any ideas why? i was very much hoping to throw it alongside joulicloud (ubuntu based) on my ssd.
Click to expand...
Click to collapse
I wasn't having any luck dual booting Linux Mint or Ubuntu. I have Windows 7 Ultra that I wanted to dual boot but couldn't get it worked out and just gave up since I have to have Linux for most of the development I do.
beard0 said:
And boom goes the dynamite
/Dinc
Click to expand...
Click to collapse
Dino-mite? Faq said run live and store on usb. Assumption was run live from dvd. Second part of answer was run from usb if BIOS allowed it. That's why I assumed I could run a live usb with a dedicated partition on the same usb. If we didn't have questions then we wouldn't have Devs. But thanx for your input Mr Dynamite.
bogwurm said:
Dino-mite? Faq said run live and store on usb. Assumption was run live from dvd. Second part of answer was run from usb if BIOS allowed it. That's why I assumed I could run a live usb with a dedicated partition on the same usb. If we didn't have questions then we wouldn't have Devs. But thanx for your input Mr Dynamite.
Click to expand...
Click to collapse
You should be able to install on a usb pen drive and save your files on a dedicated partition. Just make sure you have enough room on your pen drive. Look here: Link and see the requirements for doing so. I've never actually installed on a pen drive myself but theoretically speaking it's plausible. Let me know if it works out for you.
Will do thanx for the reply. I know how to set up a persistent live distro but some of them are tricky. I like this idea because all I need is the flash drive to do work on any computer.
"Here and now, boys, here and now."-Aldous Huxley

[Q] Dual Booting (from SDCARD) WM6.5 and a NAND based ROM? (eg. HyperDroid CM7)

Hi,
Might by NOOBISH but I have searched and searched for a way to do this, I love Hyperdroid-CM7 but I need to be easily able to access my home network and home pc with WM6.5 and stream video, file exchange etc...
How do you make a NAND based ROM like Hyperdroid CM7 run in dual boot using Haret/Loader off your SDCard?
I have read some details on the Hyperdroid development page, but nothing step by step that I could follow or easily understand.
As far as I get it you unzip the NAND ROM .zip into /Android on your SDCARD, then put haret and CLRCAD on either SDCard or in the /Android folder too...
Done this but when I run Haret it asks for a default.txt file??
Any Help would be much appreciated...
magicianhumphrey said:
I need to be easily able to access my home network and home pc with WM6.5 and stream video, file exchange etc...
Click to expand...
Click to collapse
?? why you think that with Android you wont be possible to stream video file exchange etc? i think you should take a deeper look on Android OS
and to be able to boot from SD a NAND based ROM i believe you have to do some coding cause haret all its do is just run the rom, now if the rom is coded to boot in NAND its differed. (Don't believe me in this part haha don't know much but i will advise you to take a better look on ANDROID cause it can co-operate with you pc for your files,video,media etc )
Dakargr said:
?? why you think that with Android you wont be possible to stream video file exchange etc? i think you should take a deeper look on Android OS
and to be able to boot from SD a NAND based ROM i believe you have to do some coding cause haret all its do is just run the rom, now if the rom is coded to boot in NAND its differed. (Don't believe me in this part haha don't know much but i will advise you to take a better look on ANDROID cause it can co-operate with you pc for your files,video,media etc )
Click to expand...
Click to collapse
Thanks, Yeah I thought that Android would have a network file manager, as it's Linux based, and my daughters net book runs Linux NetBook Remix (which highly recommend btw!) - but that allows me to go straight on to my Windows Network via wi-fi and mess around with files on my PC and stream etc.
OK so here's the question, if I go 100% Android to run my fave NAND build, what App/Apps do I need to stream music/video and move files around on my PC via my phone?
(I don't mean remote desktop, although some idea of apps for remote desktop would be nice too )
Cheers.
- Again I searched a lot for decent network file manager I can run from the Droid, not much luck, I heard VLC can be good to Stream Videos etc, looking into this one...
Please Recommend some Apps somebody!
Look at THIS:
http://forum.xda-developers.com/showthread.php?t=1094372
Qnkel said:
Look at THIS:
http://forum.xda-developers.com/showthread.php?t=1094372
Click to expand...
Click to collapse
Your a star mate, that looks like just what I need!!
-------------------
Again *bump* if anyone does have any ideas of actual APPS that allow network file management from the Android phones that would be great!..? (Then my need for a dual boot would be nill)...
you can use every filemanager (es, mega, oi, etc.) which supports smb-shares. simply connect to your windows-networkshare and use what ever app (mediaplayer, gallery, etc.) to "stream" your files. you can even mount those smb-shares as folders into your folder-structure of android. if you do so you can use the share like the files where on your phone. at least esfilexplorer can mount smb-shares to local folders. i am not sure about the others.

QUESTION= Root so I can write Access to Removable drive?

Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.
robjbw said:
Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.
Click to expand...
Click to collapse
Hope this helps... looks like newest update on 1/18/17 (v5.0.1)
"Other Enhancements
*Added ability to write to attached USB or SD card storage."
forums.geforce.com/default/topic/988354/shield-tv/shield-experience-upgrade-5-01-feedback-thread-for-shield-2017-/
I assume you mean network access to the attached storage
SHIELD TV Gen. 2015
write access was, for me, only possible through root and a SMB/samba server.
Root via http://download.chainfire.eu/supersu from chainfire
SMB server via https://play.google.com/store/apps/details?id=com.icecoldapps.serversultimate + https://play.google.com/store/apps/details?id=com.icecoldapps.serversultimate.packb for a native SMB server, normally i use a FTP-server like https://play.google.com/store/apps/details?id=lutey.FTPServer but was not able to get it running on the shield
SHIELD TV Gen. 2017
As of 5.0 i was not able to write to the storage
Actual there is no way to root the 2017 and therefore no SMB server.
The bootloader was updated and ca be unlocked but does not allow to flash the recovery, even if it tells you so (fastboot).
Android 7 recognize a manipulation and reflashes the stock recovery
But i am not sure if 5.0.1 added the network write access storage feature.
robjbw said:
Hi all. Only reason I am thinking of rooting my Shield TV is so I can write to my removable drives. From my understanding is that SDFix does not work with marshmallow. Is this correct? I Would love to access my non adoptable drive from my network. Or if rooted, can i also use FTP to read and write? Thank you.
Click to expand...
Click to collapse
Assuming we're talking a 2017 Shield, I actually managed to access my non-adapted storage over FTP. Without root.
I have a 5TB external HDD hooked up to my Shield, and sideloaded an FTP app. I set my external HDD as root-folder for said app, and could both read/write to it (most recent software update, 5.0.1). I wanted easy management/streaming from my PC though, so I installed WebDrive so I could mount the FTP server as a local drive.
Works like a charm, can post a how-to if required.
Radnu said:
Works like a charm, can post a how-to if required.
Click to expand...
Click to collapse
Yes please!
twe69 said:
Yes please!
Click to expand...
Click to collapse
Updated: We still need FTP to write to an external, non-adopted storage. Viewing can be done over SMB though!
Alrighty then, here goes nothing, please do keep in mind the "fix" you'll find down below is a quick and dirty one. It will allow you to both read and write to your external storage over FTP, without actually needing to have root.
Requirements
1. Sideload Launcher by Chainfire
2. A file manager, preferably with cloud access. I prefer X-plore myself.
3. FTP Server by The Olive Tree (others may work, your mileage may vary).
4. Any FTP client to access your shiny new server.
Step 1
- Install the Sideload Launcher if you haven't done so yet, it will allow us to open APKs that weren't designed for AndroidTV. You can just grab it from the PlayStore.
Step 2
- We're going to need an APK from FTP Server. The easiest way so far seems to be to install it on another device (in my case, my trusty Note3), and "backup" the APK to your Google drive using X-plore as you can see *here*.
- After we've gotten the APK there, hop back to the Shield and open X-plore. Go to your Google drive and install the FTP Server we just put there.
Step 3
- Use the Sideload Launcher to open our FTP server and set it up. Tapping your D-pad "up" once gets us to the settings of the app. Open it, and scroll down till you're looking at something like *this*.
- Most of these settings are up to your own discretion, but I strongly advice to untick "anonymous login" and set a username/pw. The most important bit is to set the home-directory to your non-adapted HDD.
- Close the settings, and tap your D-pad "down" once. Click [ A ], and we should get a nice green icon saying we're up and running! Should be something like *this*.
- The app will "survive" Sleep-mode, but after a restart you'll have to toggle it on again.
Step 4
- Profit!
- You should be able to access your FTP server on your specified local port, and using WebDrive you can even access it easily on a PC. It'll look something like *this*.
- You can use your regular SMB share to view your files over your local network, the catch is that you'll need to use FTP to write to it.
Final note!
It looks like setting X-plore as "default handler" for the non-adapted storage makes it disconnect from your shield. Don't tick it!
I read that writing to the external usb HDD is now fixed in the latest update v5.0.2?
In which case enable the following Settings > Device > Storage & reset > SHIELD storage access > Over local network > On and map the drive to the laptop.
Is this correct? I need to test it out still.
twe69 said:
I read that writing to the external usb HDD is now fixed in the latest update v5.0.2?
In which case enable the following Settings > Device > Storage & reset > SHIELD storage access > Over local network > On and map the drive to the laptop.
Is this correct? I need to test it out still.
Click to expand...
Click to collapse
Don't think so yet. I *can* view and play it, but can't write to it. Screeny over here: imgur,com/ieuhlB0
Any one have luck with this yet? Really hoping to be able to write easy to the external storage.
candymann said:
Any one have luck with this yet? Really hoping to be able to write easy to the external storage.
Click to expand...
Click to collapse
As I explained above, you actually can write to it using FTP (non-adopted storage, no root required whatsoever). Currently I would just advice using the regular SMB share to view it on other devices (since you don't want to download anything before viewing).
I've edited the instructions to clarify.
Here is something I discovered. When you hook up a USB flash drive or HD, it creates some folders on that drive. Android nvidia shield(something like that)
The nvidia folder it creates is writable. I am using a flash drive as non adoptable to play ROMs on with emulators. On the root of the drive I had issues. But once I moved my ROMs folder inside the nvidia folder all was well. No my emulators can load the ROMs from the nvidia folder created on the drive and write the save files to the same folder the ROMs are located in.
Hope this helps. Only issue is that when u restart, you get the annoying pop up asking to adopt the drive. I just hit browse each time.. Because I don't want to adopt it.. I just want it to store files..
Android went plum retarded post kitkat with drives and SD cards and write permissions.. Its very annoying and makes me long for the good OK days where u could just insert something and do with it slas you please... In my opinion they have over complicated what should be a rather simple procedure.. But it looks like this is the direction they have choose..
adam_ky said:
Here is something I discovered. When you hook up a USB flash drive or HD, it creates some folders on that drive. Android nvidia shield(something like that)
The nvidia folder it creates is writable. I am using a flash drive as non adoptable to play ROMs on with emulators. On the root of the drive I had issues. But once I moved my ROMs folder inside the nvidia folder all was well. Now my emulators can load the ROMs from the nvidia folder created on the drive and write the save files to the same folder the ROMs are located in.
...
Click to expand...
Click to collapse
Checked this and the [\\SHIELD\ExternalStorage\NVIDIA_SHIELD] folder is writable over SMB indeed.
Now it's just a matter of whether or not you're willing to put up with the popup.
Hope that helps ya. The android folder is most likely writable as well.
I remember this work around when lollipop came out and apps were not built with the proper permissions. You could use the apps folder in android on the SD card to circumvent this.
But yea I'm good for now just using the shield folder on my flash drive... I do wish there was a way to remove the popup on boot asking to adopt storage though....
I'm beginning to loathe nougat....
The later android versions are hardly usable for me without the use of xposed.
Anyways, hope that trick helps you and anyone else
If you have root couldn't you just mount the drive as writeable using a file explorer? I'm interested in writing to a removable drive in general (don't care about network access specifically).
Any news here?
I am on Nvidia Shield 2017 with 8.0.1 rooted.
I can only READ my attached NAS (network storage).
But I want to get WRITE access too
The workaround with the NVIDIA_SHIELD folder did not work... And Apps like SDfix ends up in error ??!
I own two Shields and need them to write to my NAS.
Does anyone can help me how to get this working?
Both Shields are rooted
Anyone know, if THIS is still actual? (4 years old)
Thank u very much
Kamikaze01 said:
Any news here?
I am on Nvidia Shield 2017 with 8.0.1 rooted.
I can only READ my attached NAS (network storage).
But I want to get WRITE access too
The workaround with the NVIDIA_SHIELD folder did not work... And Apps like SDfix ends up in error ??!
I own two Shields and need them to write to my NAS.
Does anyone can help me how to get this working?
Both Shields are rooted
Anyone know, if THIS is still actual? (4 years old)
Thank u very much
Click to expand...
Click to collapse
Same setup as you. I have been searching everywhere on a way to do this and no luck.

Categories

Resources