Related
How hard would this be to build or tweak this to work on all these imported ipad clones. Most use a arm varient processor.
I am relatively new to android and linux. I would like to learn the process. What would be the best place to start understanding linux(android)?
Forgot link
gohere debian.org/ports/arm/
good linux resource sites
if you're looking for basic linux questions or help, I would check out linuxquestions.org
android, there are a couple really good sites, the wiki here is very helpful, androidcentral.com
and i'm not even talking for becoming developer, I havn't even made any apps yet, but its helpful to get a good handle on the OS.
Ubuntu linux you can download and run off the CD without installing it on your PC if you want to just poke around, there are some other distributions that do the same, but Ubuntu is a good version for someone either new to linux, or with no time for endless configurations.
I've been reading up on this subject ... I really want to try Ubuntu but I hear it has major bugs ...which on in y'all opinions do you prefer and why?
Sent from my SGH-T959 using XDA Premium App
i recocmend u try a dual boot its actually really easy if u follow the instructions.
i installed ubu about 3weeks ago and i love it because u can customize it to no end and it really dosnt have that many bugs.
i installed inside of windows and did a 20gig partition so its defiantly not my daily, but its still fun to mess around with.
and if you need help with the installation feel free to pm me.
You can try the live image, to test if it suits your purpose. Also, you can use virtual machine to install ubuntu with Windows to test it.
Id reccomend the liveCD or as mentioned running in a virtual machine if your pc can handle it.
This will allow you to explore Ubuntu without any major bugs or chances of wiping your hard drive
Personally i prefer Windows for a development environment, but Ubuntu has its advantages.
I suggest you to choose windows, the best ever, ubuntu is good but not like windows
I have test Linux one times per Year. I will never love it. I use Windows since 3.1. Linux/Ubuntu is not Windows. If you know how windows work use this.
Tri boot OSX Lion, Arch Linux, and Windows 7.
Ubuntu is bloated, and Unity is TERRIBLE.
actually ive been hearing really good things about linux mint isadora its pretty much the same as ubu but has a cleaner overlay and more user freindly.
arch linux just has way more repositorys than ubu and arch linux is more complicated to install.
man the geek radar just went off the charts with that one lmao.
I'm standing at the edge on this one as well. I really like the way Ubuntu looks and how it operates, I'm just not 100% sold yet.
it is what it is, its a love hate relationship with me i love the open source like android but i hate how it looks.
i would definitely recommend running it in virtual machine to try it first before you do any hdd partitions.
if you like mac youll probably like linux since mac is pretty much linux on steroids lol.
Bierce22 said:
actually ive been hearing really good things about linux mint isadora its pretty much the same as ubu but has a cleaner overlay and more user freindly.
arch linux just has way more repositorys than ubu and arch linux is more complicated to install.
man the geek radar just went off the charts with that one lmao.
Click to expand...
Click to collapse
LinuxMint is based off of Ubuntu, but, is much more user-friendly for beginner Linux users (comes will all codecs and what not pre-installed, saves having to play around with the Package Manager, etc).
With Linux, there are several different desktop environments. KDE, is the Windows look-a-like, so, choose a KDE version if you prefer and are used to the Windows layout.
I suggest to the OP to go to http://www.linuxmint.com/download.php and download the DVD edition. Burn it to a blank DVD disc, put it into the computer and restart, and start trialling Linux from there (yes, it's that simple). To get the best of both worlds, dual boot (we can help you with that if you're having difficulty ).
It's entirely up to you though. There are advantages and there are disadvantages for choosing one over another. But, there is a learning curve to Linux. It isn't like Windows and you'll just be asking yourself for a recipe for disaster if you just go straight in and expect it to be the same.
man i almost crapped myself the first time i installed ubu i did it without anyones help and the first time i did it i did what u said and restarted with the dvd then hit escape for options then somehow crashed my system it seriously took 2hrs for my computer to restore its self after that one but thankfully it did. once it fully booted again i just popped the dvd into the tray and ran wubi installer on my desktop and i was done in about 5min i was seriously punching myself on that one lol.
also if u dont have any blank dvds laying around im pretty sure you can use daemon tools to mount the iso if your installing inside windows like i did.
If you have to ask then I suggest Windows 7 (if you have sufficient hardware). If you're interested in getting to know Linux then Ubuntu, Mint or any other variation of Ubuntu would be best. Granted there are better distros out there but they require a fair bit of knowledge.
Someone suggested Arch to a noob!?! Why not Slackware??
I'm running Lubuntu on an old machine only because XP is too heavy for it. Bottom line as a Desktop I still like Windows (let the hazing begin...)
heres kde or kubuntu in action.
http://www.youtube.com/watch?v=iyEx3hVTGDk&feature=related
and heres ubu in action
http://www.youtube.com/watch?v=oFCnNs8jbgw
both are not my videos fyi
just out of curiosity has anyone got tethering to work on ubu 11.0.4 because for me itll recognize the ssid but will never connect to it usb tether works fine though.
ApplesRevenge said:
Id reccomend the liveCD or as mentioned running in a virtual machine if your pc can handle it.
This will allow you to explore Ubuntu without any major bugs or chances of wiping your hard drive
Personally i prefer Windows for a development environment, but Ubuntu has its advantages.
Click to expand...
Click to collapse
Hi, everyone has his/her own taste of OSs (and any other things ), so I suggest you should answer by yourself.
In my oppinion, there no bug in Ubuntu. One difficult thing when using Ubuntu is: it cannot run our Windows software (for instance: MS Office, IDM, WinRar, etc)
You can try Ubuntu by use Live CD (download from ubuntu.com) or install it in dual mode. This way you can use Ubuntu w/u effecting your Win 7.
Enjoy.
I think window 7 is really good. Relatively easy to operate.
for common use windows,
for developing, ubuntu
Hello I'm new here.
Many years ago I saw Slackware Linux ROM for HTC HD2 which was basically plain Slackware with touchscreen support and KDE voice modem software installed making it functional phone OS. I wonder if maybe there is similar thing for S3 available. I'd be interested in as generic ARM Linux as possible (distro doesn't matter) yet still bootable on phone and somewhat usable (touch screen or at least usb keyboard support out of box).
If it's not out there but should be (relatively) easily doable I might be up for some challenge. I've had experience with Arch chroot linux on S3 including running bare X server on framebuffer (with killed android graphics system) so I think I should be able to make Arch ARM usable on phone as soon as I get it to boot and get something with ANY access to command line after boot.
Good day all. Hope this messages finds you safe and well in these challenging times.
I'm hoping to find some help a goal I have to have a single tablet PC that serves as both my daily driver PC running my OS of choice (Linux) and having the ability to dual-boot into Android for things like media consumption, reading books, etc.
I was fortunate to be gifted a Lenovo X1 Tablet 3rd Gen PC from a family member, and I'm truly enjoying it from the perspective of the form factor (it's similar to probably a Microsoft Surface tablet). Spec's can be found here:
[https://www.lenovo.com/gb/en/tablet...es/ThinkPad-X1-Tablet-3rd-Gen/p/22TP2CP0113#)
But it's essentially an 8th Gen Core i7 with vPro, Intel 620UHD Graphics driving a 3:2 aspect ratio 3000x2000 native resolution touch screen with WACOM digitizer, 16GB RAM, 1TB NVMe SSD, etc.
I have tried just about every ISO that BlissOS offers (as well as other such as Android X86) and simply cannot get anywhere in the installation. Occasionally the boot process will get as far as displaying some of the boot sequence, and then he screen will go black and either have a flashing or solid cursor in the upper left corner. On the newer ISO's, I could get to the point where I can hear some audio. And in some cases, the screen will sort of flash lighter and then darker (like the backlight is getting brighter and then dimmer). But at no point did I ever see an Android desktop.
I tried to boot the ISO as a Qemu VM, and this does seem to work (as I can see the full boot sequence and get to a point where I'm looking at an Android desktop). Unfortunately, I'm not sure how to configure the VM for proper touch support. Ideally, I'd rather have Android running natively on the device.
I'm finding references to others who have tried this on the Lenovo X1 Tablets and had either moderate or no success. A no point could I find a guide or reference on what combination would allow BlissOS (or any Android X86 based solution) to boot and install on this hardware.
To anyone who could help me get BlissOS running and installed on this tablet, I'd be truly in your debt.
Thanks in advance.
---
Update:
After some more research and experimentation, I was successful in getting Bliss OS installed and running on the bare metal of my Lenovo X1 tablet 3rd gen. However, the install isn't ideal as I leveraged an install script from JAXPARROW on Github (https://github.com/jaxparrow07/Android-x86-Installer-Linux) to complete the install. While this allows me to install and boot BlossOS (and other Android X86 releases) on the tablet, it's installing into a folder of the existing Linux ext4 filesystem and using the existing grub to boot. Ideally, I'd want the Android install in its own partition and ultimately use something like Refind as the boot manager.
I've attached an image of the grub entry that the JAXPARROW scripted install creates. Unfortunately, I cannot figure out what his script is doing that allows me to boot and install Android X86 on this hardware that a native boot and install won't work (black screen with a non-blinking cursor).
If anyone has any thoughts or feedback, I'd be grateful. I'm excited by the prospect that at least now I know I can run Android X86 on this hardware. And BlissOS is an amazing desktop implementation of Android.
Hardware is 2018 edition of the Lenovo Thinkpad X1 Tablet 3rd Generation:
ThinkPad X1 Tablet Gen 3 | 2-in-1 Laptop Tablet
The ThinkPad X1 Tablet Gen 3 delivers the best 2-in-1 tablet performance with a large 13" screen, detachable keyboard, and premium security features for work.
www.lenovo.com
Graphics are Intel 620 HD
3:2 aspect ratio
3000x2000
Thanks in advance.
[Image of grub entry ](https://photos.app.goo.gl/ysssaikm54cyhMpF8)
Hi @tech101, I am interested in buying a used thinkpad x1 tablet 3rd gen and planned to dual android or chrome os with windows.
Have you been able to successfully make android work?
this link https://github.com/jaxparrow07/Android-x86-Installer-Linux does not exist anymore.
Hello, I'm the developer of the mentioned project. I'm glad to see you're able to boot after installing via the installer. The installer has been updated recently with bug fixes and other distro support ( comes as a single executable instead of an installer ).
@tech101 said:
While this allows me to install and boot BlossOS (and other Android X86 releases) on the tablet, it's installing into a folder of the existing Linux ext4 filesystem and using the existing grub to boot. Ideally, I'd want the Android install in its own partition and ultimately use something like Refind as the boot manager.
Click to expand...
Click to collapse
You can do that by mounting them beforehand via cli or by a FileManager and then choosing in the Installation Partition in the installer.
Mounting a partition e.g : In Dolphin, you can do that by right clicking a partition
Basic help such as finding your filesystem name ( sda5 etc.,. ) is available in the installer's help menu
Help menu ( Ctrl + H or Help > Help in the menu)
@tech101 said:
I've attached an image of the grub entry that the JAXPARROW scripted install creates. Unfortunately, I cannot figure out what his script is doing that allows me to boot and install Android X86 on this hardware that a native boot and install won't work (black screen with a non-blinking cursor).
Click to expand...
Click to collapse
If you take a look at the line which has linux in it. It loads the kernel. With some parameters, it's possible to boot the android.
Bash:
linux /{name}/kernel quiet root=/dev/ram0 androidboot.selinux=permissive SRC=/{osname}/ noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off intel_pstate=disable mitigations=off
As explained by @Night(SG) in this commit. We removed the unnecessary ( in most cases ) kernel parameters ( ig which used to help you boot in this case ).
You can test the latest release and let us know if you're able to boot. If not, I'll add an option to enable the extra parameters while installing.
yeahman45 said:
this link https://github.com/jaxparrow07/Android-x86-Installer-Linux does not exist anymore.
Click to expand...
Click to collapse
OP made a typo, here's the correct link :
https://github.com/jaxparrow07/Androidx86-Installer-Linux
( unnecessary "-" after Android caused this )
If you guys have any questions related to androidx86, ask us on our forum : AOPC ( formerly SupremeGamers )
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.