Related
Hey guys, I'm new here and new to Android Development. I would like to try my hand at it. Can you guys suggest the best OS for Developing Android Apps.
Linux (Which Distro)
Windows
Thanks
Andrew
I to have been curious as to the best linux distro for android development. I'm not looking for afull blown linus os...more along the lines of dsl for android and app development. I have only dabbled with linux, mainly dsl and phlak livecds. I want something a little more capable then that.
avacomputers said:
Hey guys, I'm new here and new to Android Development. I would like to try my hand at it. Can you guys suggest the best OS for Developing Android Apps.
Linux (Which Distro)
Windows
Thanks
Andrew
Click to expand...
Click to collapse
UBUNTU IS THE BEST OS because android is developed under linux with java base...
if you tray windoze you must to adjust a lot of thinks and make compatibilities... don´t complicate and try UBUNTU 10
An answer of one ubuntu lover!
sorry somtimes my english is poor
Linux is best os android development application. Android is an operating system based on Linux and a robot body or synthetic. It is open source as a Java library. It is a software stack for mobile devices because it includes an operating system and middleware, application key.
I think the best Linux for Developing Android is Ubuntu. There is a new version, 11.04. Try it
i know linux is the obvious choice for android development as it has the same base as android. i also understand ubuntu is the most popular of the linux brands, but i dont really need a full blown linux os. i curently use my mobile-ap for internet with about 2 bars if that...so internet speeds are slow. i dont want to spend alot of time and bandwidth downloading a linux os with features i will probably never use. or is there a light version of ubuntu with just a basic environment i need to develop for android?
as for my other computing needs, im still a windows fan!
Is Fedora on GNOME 3.0 a good platform for development?
yea i like linux mint its more user friendly than ubuntu
Since you might be using Eclipse as IDE, there shouldn't be too much difference using a windows or linux OS.
We're using windows and we're satisfied...
Just try different OSs. You'll notice windows is slow when compiling Java. Why is that - the OS, or the usual virus scanners sitting on it - don't know. I'm pulling my hair right know why my Macbook Pro on a 7000 rpm drive is much (3x) faster to compile than windows XP on a 10K rpm drive. My office buddy's telling me Linux is faster then windows.
Wow... some of the answers in this thread are just... wow...
Ok listen up people!
For just pure development it doesn't matter which OS you choose. You can code just as well in Linux, Windows or Mac since they all run the JDK, Eclipse and the Android SDK just as well. HOWEVER:
Linux has some advantages over the two:
1. The Android emulator will run better on certain versions of Linux depending on how they are set up. The AVD works by using an emulation technology called qemu which is now integrated in the Linux kernel giving it direct access to the processor thus improving the speed of the emulator significantly. Windows and MacOS don't have qemu integrated in their kernel as far as I know therefore the emulator works like S**t.
2. Linux distributions by default are optimised to work faster on hardware than Windows. Take note of the words "than Windows". MacOS is highly optimised to work as fast as possible on Macs therefore it can't really compete in this category. But for PC users, if you invest the time and effort to make your Linux machine tweaked accordingly to your hardware settings it will blow windows away when it comes to processing speed, therefore enhancing the quickness of your IDE as a result.
Now that we got that out of the way, I do have a warning: Linux Is Hard To Configure Properly! Unless you know exactly what you are doing you will brake it over and over and over again until you get it working. If you really must use Linux, here are the distributions I recommend for developing Android apps:
Linux Beginners: Ubuntu - any version above 10.04 I think. Take your pick at what works best for you
Linux Intermediate: Spend some time configuring a Slackware Machine with Eclipse + ADT + JDK + qemu. You won't be sorry.
Linux Advanced: Gentoo or Archbang depending on preferance
Linux Experts: The bloody hell are you doing on this thread?
taranasus said:
Wow... some of the answers in this thread are just... wow...
Ok listen up people!
For just pure development it doesn't matter which OS you choose. You can code just as well in Linux, Windows or Mac since they all run the JDK, Eclipse and the Android SDK just as well. HOWEVER:
Linux has some advantages over the two:
1. The Android emulator will run better on certain versions of Linux depending on how they are set up. The AVD works by using an emulation technology called qemu which is now integrated in the Linux kernel giving it direct access to the processor thus improving the speed of the emulator significantly. Windows and MacOS don't have qemu integrated in their kernel as far as I know therefore the emulator works like S**t.
2. Linux distributions by default are optimised to work faster on hardware than Windows. Take note of the words "than Windows". MacOS is highly optimised to work as fast as possible on Macs therefore it can't really compete in this category. But for PC users, if you invest the time and effort to make your Linux machine tweaked accordingly to your hardware settings it will blow windows away when it comes to processing speed, therefore enhancing the quickness of your IDE as a result.
Now that we got that out of the way, I do have a warning: Linux Is Hard To Configure Properly! Unless you know exactly what you are doing you will brake it over and over and over again until you get it working. If you really must use Linux, here are the distributions I recommend for developing Android apps:
Linux Beginners: Ubuntu - any version above 10.04 I think. Take your pick at what works best for you
Linux Intermediate: Spend some time configuring a Slackware Machine with Eclipse + ADT + JDK + qemu. You won't be sorry.
Linux Advanced: Gentoo or Archbang depending on preferance
Linux Experts: The bloody hell are you doing on this thread?
Click to expand...
Click to collapse
Awe but Archbang is easy, how about pure Arch Linux ;D
is ubuntu still best OS to develop android apps?
how to take back up of only videos on my Android device?
taranasus said:
Wow... some of the answers in this thread are just... wow...
Ok listen up people!
For just pure development it doesn't matter which OS you choose. You can code just as well in Linux, Windows or Mac since they all run the JDK, Eclipse and the Android SDK just as well. HOWEVER:
Linux has some advantages over the two:
1. The Android emulator will run better on certain versions of Linux depending on how they are set up. The AVD works by using an emulation technology called qemu which is now integrated in the Linux kernel giving it direct access to the processor thus improving the speed of the emulator significantly. Windows and MacOS don't have qemu integrated in their kernel as far as I know therefore the emulator works like S**t.
2. Linux distributions by default are optimised to work faster on hardware than Windows. Take note of the words "than Windows". MacOS is highly optimised to work as fast as possible on Macs therefore it can't really compete in this category. But for PC users, if you invest the time and effort to make your Linux machine tweaked accordingly to your hardware settings it will blow windows away when it comes to processing speed, therefore enhancing the quickness of your IDE as a result.
Now that we got that out of the way, I do have a warning: Linux Is Hard To Configure Properly! Unless you know exactly what you are doing you will brake it over and over and over again until you get it working. If you really must use Linux, here are the distributions I recommend for developing Android apps:
Linux Beginners: Ubuntu - any version above 10.04 I think. Take your pick at what works best for you
Linux Intermediate: Spend some time configuring a Slackware Machine with Eclipse + ADT + JDK + qemu. You won't be sorry.
Linux Advanced: Gentoo or Archbang depending on preferance
Linux Experts: The bloody hell are you doing on this thread?
Click to expand...
Click to collapse
Could you guide me how to take back up of only videos on my Android device
using own made program or application software.
Means from where to begin ?
What to cover first ?
File system of Android ?
Or direct using system calls I can copy videos directly ?
regards
matt
You suggested its worth time & effort to properly setup Slackware it would be worth our while. Ok found u page2. Let's see is the needed software list still valid 2015?
Where can I go for support setting up Slackware for android development.
Plus FYI can't watch tutorial video be.cause Flash no longer supports Linux.
I have UBUNTU 16.04.
I've noticed a lot of people saying to use Ubuntu 10. is that because the post is old or is the 10th generation Ubuntu the best for android development. i also am a noob. i can root, i have successfully flashed a lg stylo once with katana rom. i still use it to this day,,,,, bc my gf "accidentally" broke my 500gig hdd that i was booting windows ten from via usb on my dell inspiron. i was using mainly odin and lg flash tool which i rem was hard to get up and running on Ubuntu which if i rem correctly is why i went to windows when i am flashing. Any suggestions or refferences would help greatly. i fig if im starting over id better do it the correct way. My end goal is to try my hand at learning android development. Ty LOVE THE SITE
Hello gents and ladies,
Since the announcement that Canonical made on making Ubuntu on Android a release for OEMs to put on their devices, there has been quite a stir and interest on when we are getting to get this on our phones. Sadly, while the distro of Ubuntu is open-sourced, the programs that were created to achieve this method are not available to the public due to Canonical outsourcing the work to a 3rd party company.
Some users here may already say that we have Ubuntu on our phones but the method that is most commonly used by the community is to load up a virtual environment or Chroot inside of Android then remote into the interface via a VNC connection app. While this does work, it is a pretty sloppy method that is resource intensive and does not benefit from any hardware acceleration for the Linux desktop environment that is used. Plus, there is no way to pipe audio thru a VNC connection so using any audio/video programs in VNC is pointless.
Lastly, Ubuntu on Android is actually nothing new to the world of Android, as its been around for about a year and a half. It came in the form called Webtop that Motorola had launched on their Atrix/Bionic/RAZR lineup of phones. Webtop is essentially a stripped down version of Ubuntu with a lot of Linux tools taken out along with a very limited desktop environment. Webtop does everything that Ubuntu on Android does but in a neutered manner but there are different groups on each phone that have accomplished bringing back many of the linux tools that were taken out. Check out the thread below to see what I mean.
http://forum.xda-developers.com/showthread.php?t=1397583
It is believed that the same methods and tools that are present in Webtop are the same ones being used by Ubuntu on Android and possibly made by the same company. This can be seen in the demo video of Ubuntu on Android where the demonstrator had replaced the Webtop distro with a full Ubuntu 12.04 distro on a Motorola Atrix 2. So to debunk the myth that Ubuntu on Android can be easily loaded up on a phone as shown on video, no cause it was initially was setup with the required framework and partition space to load Ubuntu on Android even before Canonical announced Ubuntu on Android.
With all that is said, Canonical is targeted OEMs and Carriers to launch their Ubuntu on Android on select model phones and probably will not release the necessary tools as open-source code so the development community can compile their own working Ubuntu on Android. Now, all hope is not lost because some of the work has already been done but needs to come together into a package that can be ported from one phone to another.
Here are different parts that are needed:
1) Ubuntu image
There are many working images out there that run in a chroot environment but there is one universal image that is being implemented that is made by zacthespack that works on a variety of different devices - See attached thread
http://forum.xda-developers.com/showthread.php?t=1467811
2) X Server Port
Instead of using a VNC client and server model which is very resource intensive and does not benefit from GPU acceleration/Framebuffer. Using a X Server windows management system like they do on home PCs and laptop will greatly increase speed and functionality of a Linux distro opposed to VNC. This is how Webtop on the Motorola phones work is by using a port of X Server which pipes the display out to the HDMI port to be used with the Laptop dock or home dock. There is a group at AndroiX.org that is working on a port of X Server for Android that is looking very promising so hopefully anybody that can contribute to project to speed it up as it is the most crucial part for Linux in Android.
3) Sound
The biggest drawback of VNC is the lack of any sound processing which can be very annoying when trying to watch any videos or listen to sound clips on the web. What they are using on Webtop and Ubuntu on Android is a custom compiled version of PulseAudio module to pipe audio thru Android's audio manager system. No projects have yet been started on this so if anybody knows of one, feel free to post a link.
4) Android in Window
As demo'ed in the video and on Webtop, you have the ability to see whats on your Android display but in a window within Ubuntu when Webtop/Ubuntu on Android is engaged. This is a cool feature that maybe a X client app within android that pipes the display to a window in Ubuntu or maybe VNC client/server scenario. This is not really necessary to Linux in Android but non the less a cool feature to have.
5) Contacts/Text messages/Call logs
This is more shown in Ubuntu on Android opposed to Webtop where in Ubuntu mode, you can look at your Contacts or call logs in a program as opposed a Android view in a window. They also demo'ed a special program in Ubuntu to where you can send/receive text messages in a interface designed for Unity. They accomplished this by using a server application in Android, more commonly known as Motorola Phone Portal, that can relay information from the phone to applets inside of Webtop/Ubuntu on Android using a web interface API on localhost:8080 or on a remote computer on the same network. Like I said before, not really necessary but another cool function to have.
All and all, this pretty much sums up all the different parts for a project like this to take place. I am in no way a seasoned developer, just a person throwing out concepts that I have learned and done myself on the Bionic Webtop phone which hopefully some skilled individuals can run with as I am no Linux expert by any means. Anywho, let me know what you guys think about this and what can be improved.
Ubuntu on arm.
I've been looking into the development of something like this and have found a few resources that may prove beneficial:
Linux 4 Tegra (nVidia)
System Requirements
Host PC running Ubuntu Linux version 9.04 or higher.
Tegra Linux Driver Package providing a kernel image, bootloader, NVIDIA drivers, and flashing utilities. For more information, see the Release Notes.
Sample filesystem (example provided derived from Ubuntu 12.04)
Click to expand...
Click to collapse
Please note that nVidia currently provides driver packages for each model of the Tegra (Tegra 2 and 3).
As well as:
Ubuntu on Smartphones
Now. I've been playing with both an Ubuntu and Debian chroot and have ran into the issues you speak about (in a chroot with only vnc support is very limited, no sound, no camera, etc.) and would like the ability to dual boot at least.
[Q&A] Ubuntu on the Transformer (eMMC install) (xda-developers)
Basically, the creator of this thread is working from another dev's work to get ubuntu running on an Asus eeePad.
Description
Assimilation is a multi-call shell script, designed to manage Arch Linux chroots.
Open Source
Assimilation is open source and licensed under the Apache License 2.0. You can check out the source code at GitHub.
A More Descriptive Description
Assimilation is a shell script I wrote back in the summer of 2013. Since then I've turned it from an overnight project into an open source project on GitHub.
I've always hated using chroots on my Android device, until I wrote Assimilation that is.
Assimilation will automatically detect your CPU architecture (currently it supports ARMv5 - ARMv8, i686, and x86_64), download the corresponding Arch Linux image and extract it. From there it can automatically mount necessary resources and enter a chroot for you. Once you exit the chroot, it can automatically clean up all mounts for you.
Assimilation runs nicely on my Android smartphone and tablet, as well as my HP Chromebook 11.
What Can I Use Assimilation For?
Glad you asked!
Firstly, Assimilation is not for the faint of heart! You must have access to a Terminal and have root access.
I use Assimilation for a number of things...
- I've turned an old Galaxy S into a personal file server that runs surprisingly fast (will write a guide for this soon).
- I also use Assimilation to use programs like Git on my Chromebook.
If you encounter any problems using Assimilation, please use GitHub's Issue tool to bring it to my attention.
If you like Assimilation (or my other app, Epoch Launcher), please follow me on twitter @mirasmithy
Reserved!
What phones can boot into and run a desktop ARM Linux distro (such as Arch, Slackware, Ubuntu or Debian) natively, with call and messaging support?
Ubuntu Edge.
linuxphone said:
What phones can boot into and run a desktop ARM Linux distro (such as Arch, Slackware, Ubuntu or Debian)
natively, with call and messaging support?
Click to expand...
Click to collapse
The closet you can get is with Ubuntu Edge but it is still under development and will not be available for a some time.
I am sorry I can not post the links yet in the post but you can google for the "Ubuntu Edge" and you will get enough reading material about the project.
There are also some solutions with VNC and a VM in which you run a desktop Linux. Might not be what you want, but you would have a Linux running on your phone.
The main problem is going to be drivers, which is why a ARM Linux can't just be booted. Someone would need to be merging device specific drivers into the linux, test it, debug it and so on, which doesn't make sense if there are so few people really wanting it. And as you can see with Ubuntus try on that: It is a lot of development needed.
It's possible to dual boot Maemo (to use it for phone features) and Ubuntu (desktop) on Nokia N900.
It's also possible to dual boot Windows Mobile (for phone features) and Ubuntu (desktop) on HTC HD2.
On the other hand, these Indian tablets boot and run Linux:
w w w .youtube.com/watch?v=n1tC8uSR0og
And have phone features:
w w w .techulator.com/resources/9492-Datawind-UbiSlate-7C-Edge-tablet-Full-specifications-features-online.aspx
If anyone tested Linux with phone calls on those devices, please tell.
A long time ago I installed Gentoo Linux on an ARM based hx4700 iPaq; it worked but ran so slowly it wasn't much use. The specialised Linux distros Familiar and Angstrom ran much better, as they were specifically designed for handheld devices. Granted phone specs are way improved now, but is there any real advantage running a full-blown Linux on a phone.... surely Android is basically a Linux distro optimised for phone specs (and chargeable apps, etc...). Would it be less work to port apps you need to run on Android instead - if that's your aim? Although it may be worth doing just for the sake of it....
Full-blown Linux offers the advantage of being in control of the operating system. You choose the tools you need. Android is less secure (backdoors, apps reading your data) and mobile apps generally feel like crippled desktop apps. For example, apt-get is much more comfortable to use, you just type the packages you need and it downloads them, no need for searching inside categories of app market (and all of them are free with full functionality with no ads). You can use the same scripts you wrote for your PC. It can be tweaked to run really fast (low resource usage apps written in C vs Android's Java), and you choose your desktop environment (e. g. a tiling window manager with the right apps literally flies on an old machine, RAM used on system start with Xorg running equals 20 MBs). Also, there's full filesystem encryption.
Mobile hardware is more or less the equivalent of a Pentium 2 / 3 / 4 desktop PC, which is enough for full desktop app experience.
Im glad i found this topic.
Thats not new to me...
I think the questions to add are:
- How to fully remove Android to Install Linux
- Can i install all the Drivers needed?
So that i can use: Modem(phone); WiFi & GPS under Linux.
-Is it possible to revert to Android?
- Minimum Requirements to Run Linux and What Distro?
Sent from my GT-I9003 using XDA Free mobile app
Asking this question because the attempt to get TWRP on my device is becoming a compound problem as the distance to being able to build it approaches 1. Otherwise known as the law of inverse noobness: Hindsight is always 20/20. Personally, not even half way to 1 in being able to do this, as am fairly new to doing things at the operating system level of programming. Not brand-new though, and knowing how and where to look things up helps, so if you have hints or can point me in the right direction that'd be great. First question is sort of along the lines of "how do you setup your dev environment" if you want to make it modular? More precisely:
So right now, the build page for AOSP concerning my device says to use Ubuntu 14.04 and do all those things to set it up for that. Do I need to do that in order to get TWRP built for my device? To have it set up the same way as the AOSP advises? Having a different computer for each dev environment would be a bit much, but running them in qemu seems even more ridiculous. Perhaps a better idea is to set up a "build environment" on bootable USB sticks that do all the work? That would simply a lot of things, like not having to swap out hard drives, and being able to easily clone a USB drive to "just work" and build AOSP/TWRP at will on any computer.
For reference, it is the Moto G Power (2021) "Sofia" device. They've released sources for it, but not much development going on. So learning how to do this for my device might just unlock TWRP (and with it, probably the Nethunter kernel/chroot environment) for other devices not yet supported.
Help me, help you. Thanks.
(Have other questions, too).
Why not use WSL2?
How to install Linux WSL2 on Windows 10 and Windows 11
The latest version of the Windows Subsystem for Linux is a significant upgrade; for most, it's now easier than ever to install.
www.windowscentral.com
jwoegerbauer said:
Why not use WSL2?
Click to expand...
Click to collapse
I don't use windows.
Bump.
Asking this because it seems that, being new to programming and having no formal training, I'm missing something from tutorials (like the TWRP git page, or some of the tutorials here on this forum that haven't been updated since 2013) and other material that might be thought to be "known" or "implied" and I just can't seem to understand what. Because when I go to build projects or whatever, following tutorials to the letter, still end up with errors and other problems that aren't covered in the tutorial. Part of that problem is installing dependencies, and then having them conflict with other installed things, like having two of python and three versions of java. So having a "build environment" to prevent conflicts is something that wasn't taught, but learned through trial and error, but that isn't the only problem I'm having.
McChadwicke said:
For reference, it is the Moto G Power (2021) "Sofia" device.
Click to expand...
Click to collapse
Hmm. I have the same model, but it's "borneo".
Did you build TWRP for your device? Any pointers or tips?
I usually just modify stock recovery to have rooted, permissive ADB.
I really don't need more than that in a recovery.
I haven't done much with my GP21 since the Firehose loader is restricted.
Renate said:
I usually just modify stock recovery to have rooted, permissive ADB.
I really don't need more than that in a recovery.
I haven't done much with my GP21 since the Firehose loader is restricted.
Click to expand...
Click to collapse
Not sure why the last reply didn't quote you...
Setting up a build environment is an evolving problem. As of this writing it seems the Ubuntu team is switching to a "pro version" system, a paywall, for some services...
Also, AOSP recommends Ubuntu 14 for a build environment. Gave up trying to run it from USBs lol, it is running on a dedicated system. But android-sdk is no longer available in apt, while running Ubuntu 14.04 + latest updates? So went to check why and now AOSP is using its own system for build environment setup and management. Tried running it in Ubuntu 14, but gave errors with the setup script provided.
Seeing now if I can't get the android sdk to run in Mint-XFCE... Will check back. TWRP build page says I need these things to build it (TWRP), right?
Also, how much of the preinstalled vendor crud can be pruned before it breaks?
Thanks.
Edit: reference on the TWRP guide I'm using is https://forum.xda-developers.com/t/...ompile-twrp-from-source-step-by-step.3404024/ (posted 2016)
I think that all build environments are getting more restricted.
"Just do it OUR way" seems to be the new corporate slogan.
I build Android apps without Android Studio, Gradle or an IDE.
Renate said:
I think that all build environments are getting more restricted.
"Just do it OUR way" seems to be the new corporate slogan.
I build Android apps without Android Studio, Gradle or an IDE.
Click to expand...
Click to collapse
Does TWRP have its own build control system? Considering all these changes, should it?
To keep things isolated, clean and manageable on host system, that has no dev tools
or anything extra besides standard desktop stuff. (under main linux distros)
#1 For smallest , fastest deployment of various build/dev environments i use schroot
on devuan/debian , it is a system to manage/automate the use of chrootable containers.
like regular manual chroot but most thigs are automated/preconfigured with
just a few commands and config files.
Basicaly a new root filesystem (userspace) that is independent of hosts root filesystem and just
uses hosts kernel (or as much/little acces to kernel as you give it trough schroot config files)
has its own packages and dependencies and will only see specific sections of hosts filesystem sections you give it access to like say /src/myproject from host. can be a separate /home
or shared with host, all depends on your config.
Using debootstrap to create the filesystems for containers of specific distributions/verions.
Or can just manualy copy an install and rip out the kernel etc...
(Can install ubuntu userspace in debian with debootstrap , if need be.)
(like lineageOS was hard to find all the correct/matching dev tools under devuan, so ubuntu it was)
#2 For something a bit beefier LXC on top of libvirt.
(regular chroot wont run services, or have its own networking , LXCs can , with some extra configuration)
#3 For when you just need an actual full blown VM os installation use KVM/qemu on top of libvirt .
(like installing 15 year old redhat 5.1 in a container wont work, kernels and main libs too far apart)
(or anything that is just too different from current linux kernel , other OS s etc...)
virt-manager is nice for graphicaly managing VMs and LXCs
#1 But schroot is essential and will suffice for more then 90% if not whole 100% of your needs.
if you want a clean host system from being clobbered by constant installing and testing and such . Keeps the environment contained in its own filesystem namespace , have as many as you need .
start fresh,rollback,clone etc.............
Once configured just start another tab in a terminal emulator and schroot in to the container
and your main host system in unaffected, always clean .
#4 Running all of this on top of ZFS takes it a step up, to the next level of effeciency.
zfs helps quite a bit with cloning,branching,snapshots, rollbacks but not essential,
like git versioning for things that are too big for or are not made for git management
(but is another system on to itself to learn, so ignore it if new to linux )
just cloning a 300Mb-1Gb base bootstrap install folder takes no time on regular filesystem on ssds .
With these 3 tools , you can have 10s if not 100s of different environments on a single host
quickly deployable once you get to know the procedures. all usable at the same time without
reboot,
#5 The most important is learning how to hunt for the right version of tools and all of the
dependencies and the correct versions of those , as each project will have their own
and will base it on their own distribution of choice at a specific point in time.
(by being able to install/test/restart in container makes this whole process , easier)
you can test many different ideas at the same time , and merge what works in
to your own dev-build-env for a specific project.
(like hunting down correct tutorial for specific/old/obscure phone and a rom and recovery
and rooting tools associate from a time long past. using wayback machine to source
correct versions of each , as normal web has erased them )
even used schroot to install games for nephew from untrusted sources without hesitation,
and just delete the container when done, but that was a bit more involved as proprietary
nvidia drivers had to be installed on host and partially in containers.
dandudikof said:
To keep things isolated, clean and manageable on host system, that has no dev tools
or anything extra besides standard desktop stuff. (under main linux distros)
#1 For smallest , fastest deployment of various build/dev environments i use schroot
on devuan/debian , it is a system to manage/automate the use of chrootable containers.
like regular manual chroot but most thigs are automated/preconfigured with
just a few commands and config files.
(like hunting down correct tutorial for specific/old/obscure phone and a rom and recovery
and rooting tools associate from a time long past. using wayback machine to source
correct versions of each , as normal web has erased them )
Click to expand...
Click to collapse
neat. schroot looks like a solution. answers a lot of questions, anyway. that last part scares me though. using the wayback machine to source things jeez. there's gotta be a better way, but probably not unless i want to do it myself which will only add time to "the project".
McChadwicke said:
neat. schroot looks like a solution. answers a lot of questions, anyway. that last part scares me though. using the wayback machine to source things jeez. there's gotta be a better way, but probably not unless i want to do it myself which will only add time to "the project".
Click to expand...
Click to collapse
That was just worse case scenario if you get in to very obsolete/old/abandoned stuff (10-20 year old) projects/hardware etc...
dandudikof said:
10-20 year old
Click to expand...
Click to collapse
yeah some of the hardware is in that range. actually upgraded one of the old rigs (because parts are cheap) from an athlon to a phenom lmao thing has 16gb ram, it is stacked now with top of the line things from that era. keeping it around for nostalgia's sake at this point since it still works.
xmrig gets abysmal hash rates, not even worth running on older hardware.