Develop Bugs

Samsung Galaxy Tab Pro S

Hello,
I just tried to install Remix OS 2.0.205 64-bit UEFI boot on my brand new Samsung Galaxy Tab Pro S. The procedure went well and I could boot ok. Unfortunately the touch screen and the wireless are both not working. Rest seems to be ok, but without wireless, there is not much I can do...

Hello....we're you ever able to get this running on your tabpro s? I'm contemplating buying a tabpro.
Sent from my SM-P905V using XDA-Developers mobile app

I just bought this tablet and I would like to know too. I feel like remix on this would be amazing...

Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.

mrDmola said:
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
Click to expand...
Click to collapse
How can this be sorted out as I would love to have this on my Tabpro S!

mrDmola said:
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
Click to expand...
Click to collapse
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?

nielo360 said:
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
Click to expand...
Click to collapse
I'm going to install it on my Tabpro S tonight and will report back.

Biggenz said:
I'm going to install it on my Tabpro S tonight and will report back.
Click to expand...
Click to collapse
EDIT2: or these methods also from the xda remix 3.0 threads
In /system/build.prop change ro.remixos.box=true to false (should give brithness icon on the bottom)
or
Use Fn+left or right key combination
or
Edit: try this https://play.google.com/store/apps/details?id=com.curvefish.widgets.brightnesslevelGreat!
it was mentioned on another xda remix 3.0 thread.
looking forward to it Im waiting for my usb adapter but might consider the partition method if brightness can be lowerd via a work around to save battery or fixed.

I installed it last night and can confirm what mrDmola said. Everything works fine apart from wifi and screen brightness. For me the keyboard and track pad DID work. Such a shame as it's a brilliant OS.
Are there any developers who can sort this out for some beer money?

I'd donate if someone was willing to fix WiFi and brightness as its an excellent device for dual booting. Currently I use splashtop windows store version to stream ami duo os android from my desktop. It works flawlessly lag free with most games and touch screen works well with splashtop. I'd prefer remix however as a native os.

nielo360 said:
I'd donate if someone was willing to fix WiFi and brightness as its an excellent device for dual booting. Currently I use splashtop windows store version to stream ami duo os android from my desktop. It works flawlessly lag free with most games and touch screen works well with splashtop. I'd prefer remix however as a native os.
Click to expand...
Click to collapse
I tried installing Android-x86 but that doesn't even boot. I just get a black screen and my Tabpro S becomes unresponsive. I couldn't switch it back on and nearly got worried. A soft reset sorted it out.
Then I also tried Phoenix OS which works fine on my PC, but same again on the Tabpro, it won't boot. Just goes black screen and then nothing.
Nielo have you tried Phoenix OS by any chance? If not could you try to install it and let me know your findings please?

Biggenz said:
I tried installing Android-x86 but that doesn't even boot. I just get a black screen and my Tabpro S becomes unresponsive. I couldn't switch it back on and nearly got worried. A soft reset sorted it out.
Then I also tried Phoenix OS which works fine on my PC, but same again on the Tabpro, it won't boot. Just goes black screen and then nothing.
Nielo have you tried Phoenix OS by any chance? If not could you try to install it and let me know your findings please?
Click to expand...
Click to collapse
I haven't tried that OS, I will try remix os if I can find a wifi fix. I'm still waiting for my Samsung usb adapter to boot via usb

nielo360 said:
I haven't tried that OS, I will try remix os if I can find a wifi fix. I'm still waiting for my Samsung usb adapter to boot via usb
Click to expand...
Click to collapse
Phoenix OS is very similar but I prefer Remix OS.
Why is it so hard for someone to tell us how to fix this problem?

nielo360 said:
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
Click to expand...
Click to collapse
I installed on a partition It automatically gave me the option to boot into windows or remix OS. I had to change the boot settings in my bios first before I was able to do any of this though

Without wifi most games wont work so trying it would not be useful, but its good to see the touchscreen working. 2.0 had issues with touchscreens

WiFi drivers needed
Hey, I just installed the latest version of 3.0 as of 12th october 2016
Touch screen WORKS! (Unlike Surface Pro 4)
Touch pad now works
Keyboard works
*But the deal breaker remains Wifi*
Tab Pro S uses a Qualcomm wifi chip and obviously there are no drivers for it installed in the build of Android x86 that Remix OS are using.
Can't we just add these ourselves? Or do the drivers simply not exist for Android on x86?
Other quibbles but not as problematic...
No bluetooth
No screen brightness control
No battery info or charge levels
All again just driver issues.
It really would be wonderful to get this working as there are no other premium Android tablets on the market with a faster chipset than an iPad Pro and an AMOLED screen for 750 euros

Hey guys I have been making some progress with a rooted custom build of Remix OS.
The WiFi adapter chipset in the Tab Pro S is the Qualcomm QCA6174. The Linux drivers which come packaged with the Remix OS kernel as it stands do not work.
There are the same QCA6174 issues with Linux based OS - https://bbs.archlinux.org/viewtopic.php?id=204871
Following from that research I downloaded a few different versions of the QCA6174 driver from Github and it appears the filenames need to be a certain way for it to be picked up by Remix OS / Android x86 (see guide below).
The result is I can now get the WiFi hardware to be detected OK by Remix OS and it switches on, starts searching for access points... However we are not quite there yet. It does not actually detect any SSIDs or connect to the internet. So I need to figure out from the error logs why that is.
Bluetooth seems to now work as well - was able to show a list of discoverable devices and pair with my phone, but not pick up a LTE personal hotspot for the internet.
Seems something basic to do with TCP/IP or Ethernet connectivity is broken?
By the way all this needs root access to Remix OS. I used this guide to root - http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Also I had to install a custom version of Remix OS with the bloatware removed and a more powerful File Manager along with Super User app pre-installed. I used this version based on Jide's v3.0.202 -
http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
You also need to edit a file on the EFI partition in Windows before rebooting to get proper root access. To add the REMOUNT_RW=1 flag to the kernel you are going to be editing the grub.cfg file in the /BOOT directory of your EFI partition and this won't be mounted in Explorer. To mount this using the guide I linked to above in Windows 10 it is important to run the command prompt as an administrator (right click, run as...) even if you are logged in as admin. By default it will run in user mode and you won't get permission to access the EFI partition at all.
So in summary -
1. In Windows install the custom version of Remix OS from here:
2. You do NOT need to install it on a separate partition, put it on C:/ drive
3. Do not reboot Windows after the installer finishes, instead run the Command Prompt (right click, run as admin)
4. Type command and enter - taskkill /im explorer.exe /f
5. Type command and enter - mountvol X: /s
6. Type command and enter - explorer.exe
7: Type command and enter X: and then cd to directory boot/grub
8: Edit the grub.cfg file in X:/boot/grub (command prompt - notepad grub.cfg) - please note DOS edit command removed from Windows 10 so it will open in Notepad
9. Add the line REMOUNT_RW=1 in the kernel commands, the line should look like this -
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
10. Reboot
11. At dual boot option screen select Remix OS and it will finalise installation, before booting to Remix OS desktop
12. Run Super User app, ignore message about it needing to search for an update
13. At the desktop run cyanogenmod File Manager (not the Mac OS style Remix OS one as it has no root access) and go to the root /system folder, grant full read/write privileges in Super User app when prompted
14. You will need to copy the QCA6174 driver files from a USB drive. These files you should download from here on a machine with internet access:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
In Remix OS these belong in the following folder:
/system/lib/firmware/ath10k/QCA6174/hw3.0/
In the driver package downloaded from github the file "firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1" needs to be renamed firmware-4.bin
Make sure files are named as follows:
firmware-4.bin
board-2.bin
board.bin
15. Reboot and the WiFi hardware will now switch on in Remix OS and begin searching for access points, bluetooth should detect nearby devices.
Other stuff which I found currently works:
Touchscreen (it does not on Surface Pro 4 so big reason to use Tab Pro S!!)
Trackpad
Keyboard
Audio, with reservations (system sounds audible like tapping in calculator app, but MP3 media audio didn't work in bundled player)
To do:
Final fixes to WiFi
Screen brightness control
Battery charge level and standby (it can only tell if connected to A/C, no battery polling levels detected)
Further check audio and app compatibility once WiFi is working

Great job thanks for your work on the issues looking forward to working wifi!

Is Remix OS better in terms of battery life?
My ProS doesnt last long with screen switched off, unless I shutdown windows.

commanderspike said:
Hey guys I have been making some progress with a rooted custom build of Remix OS.
The WiFi adapter chipset in the Tab Pro S is the Qualcomm QCA6174. The Linux drivers which come packaged with the Remix OS kernel as it stands do not work.
There are the same QCA6174 issues with Linux based OS - https://bbs.archlinux.org/viewtopic.php?id=204871
Following from that research I downloaded a few different versions of the QCA6174 driver from Github and it appears the filenames need to be a certain way for it to be picked up by Remix OS / Android x86 (see guide below).
The result is I can now get the WiFi hardware to be detected OK by Remix OS and it switches on, starts searching for access points... However we are not quite there yet. It does not actually detect any SSIDs or connect to the internet. So I need to figure out from the error logs why that is.
Bluetooth seems to now work as well - was able to show a list of discoverable devices and pair with my phone, but not pick up a LTE personal hotspot for the internet.
Seems something basic to do with TCP/IP or Ethernet connectivity is broken?
By the way all this needs root access to Remix OS. I used this guide to root - http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Also I had to install a custom version of Remix OS with the bloatware removed and a more powerful File Manager along with Super User app pre-installed. I used this version based on Jide's v3.0.202 -
http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
You also need to edit a file on the EFI partition in Windows before rebooting to get proper root access. To add the REMOUNT_RW=1 flag to the kernel you are going to be editing the grub.cfg file in the /BOOT directory of your EFI partition and this won't be mounted in Explorer. To mount this using the guide I linked to above in Windows 10 it is important to run the command prompt as an administrator (right click, run as...) even if you are logged in as admin. By default it will run in user mode and you won't get permission to access the EFI partition at all.
So in summary -
1. In Windows install the custom version of Remix OS from here:
2. You do NOT need to install it on a separate partition, put it on C:/ drive
3. Do not reboot Windows after the installer finishes, instead run the Command Prompt (right click, run as admin)
4. Type command and enter - taskkill /im explorer.exe /f
5. Type command and enter - mountvol X: /s
6. Type command and enter - explorer.exe
7: Type command and enter X: and then cd to directory boot/grub
8: Edit the grub.cfg file in X:/boot/grub (command prompt - notepad grub.cfg) - please note DOS edit command removed from Windows 10 so it will open in Notepad
9. Add the line REMOUNT_RW=1 in the kernel commands, the line should look like this -
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
10. Reboot
11. At dual boot option screen select Remix OS and it will finalise installation, before booting to Remix OS desktop
12. Run Super User app, ignore message about it needing to search for an update
13. At the desktop run cyanogenmod File Manager (not the Mac OS style Remix OS one as it has no root access) and go to the root /system folder, grant full read/write privileges in Super User app when prompted
14. You will need to copy the QCA6174 driver files from a USB drive. These files you should download from here on a machine with internet access:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
In Remix OS these belong in the following folder:
/system/lib/firmware/ath10k/QCA6174/hw3.0/
In the driver package downloaded from github the file "firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1" needs to be renamed firmware-4.bin
Make sure files are named as follows:
firmware-4.bin
board-2.bin
board.bin
15. Reboot and the WiFi hardware will now switch on in Remix OS and begin searching for access points, bluetooth should detect nearby devices.
Other stuff which I found currently works:
Touchscreen (it does not on Surface Pro 4 so big reason to use Tab Pro S!!)
Trackpad
Keyboard
Audio, with reservations (system sounds audible like tapping in calculator app, but MP3 media audio didn't work in bundled player)
To do:
Final fixes to WiFi
Screen brightness control
Battery charge level and standby (it can only tell if connected to A/C, no battery polling levels detected)
Further check audio and app compatibility once WiFi is working
Click to expand...
Click to collapse
Great work! Hope we will see the wifi working soon. I bought the tab pro s to replace my ipad pro, now it basically sit in dust, was thinking about selling it until I see this post.

Defy - A 2016 Experience

Since this Defy Forum is getting a bit old, I thought I'd give my recent experience with my defy. This is quite a lengthy thread but there is so much information on this forum that it becomes confusing so thought I'd share my experience so you can cut through a lot of the information. I've had my defy for over 5 years with the stock froyo 2.2.2 and its served me well until recently its beginning to bug me with how laggy it is. Also I wasn't sure if the battery was running out a faster than it used to.
The first thing I thought I'd do is do a factory reset which I successfully did however when I went to put back on some of the apps that I had before such as Runkeeper, Telstra 24/7 and RSA Security token, none of them were compatible with my old phone. I was able to find old versions of some of the apps but not Telstra 24/7 which I use to recharge. At this point I decided on installing a custom rom which I'd done before on other devices. If it didn't work out then phones with the same specs were selling for $29 at a local supermarket so no real damage if I get it wrong.
The first thing was to root the phone which I found something called Superoneclick. I had to turn off my antivirus on my PC use it as there are some files that appear corrupt but doing some searching gave me confidence it was just an overzealous AVG and appeared safe.
Once this was done it was a matter of picking a Rom which I went for CM11 Kit Kat it seemed ok but not heaps better. The thing was I'd now picked up a real battery problem. I tried various Calibration apps to no avail. My battery was experiencing quite large drops of 20% ie it would go from 89% to 50% and then later from about 35% to 20%. It would then stay on 1% for quite some time.
Thinking this was due to the ROM, I tried several ROMs but they all had the same problem. Eventually i found a thread on the battery problem and although I didn't change all the permissions as advised I did so some of the other stuff to no avail.
At this stage I thought my main issue was now the battery and thought I'd read someone that perhaps a stock based rom might sort it out. I installed MS4Ginger which was really smooth however was still a bit laggy at times. Also I noticed that it wasn't able to support various apps being Android 2.3. After a bit more reading, my minimum requirement was Jellybean 4.1 and I'd read that the more recent the ROM the more RAM intensive so I decided to try ROMs with my minimum requirement ie 4.1
I'm not a fan particularly the way the Cyanogen type rom look so was looking for something with a different look and feel. The main ones were:-
Miui based ones (Wiui, Jiui) which I quite liked however lag was still there and the occasional sudden reboot. Battery problem still there.
Xperia ROM which was also nice but also did a sudden reboot then stuck in a bootloop.
There was still lag which I couldn't really understand.
Last Rom I tried was Motor Gun Ice 4.1, it still had the Cyanogen look about it but seemed to run pretty smooth. One thing I had to do was change the Baseband to Telstra in the 'Advanced' section of settings. This made the phone and internet connection work faster.
At this point I ordered a new battery. While I was waiting for that to arrive I read that Facebook app is really bad at taking up RAM. In found another app called Facebook lite and uninstalled the standard Facebook app. All of a sudden Lag Fixed.
This got me searching other 'Lite' apps. Now for web browsing i use Opera Mini and the launcher I now use is Holo Launcher. I also tried to find a replacement for Messenger but no luck and its not been an issue.
So now my phone is running better than ever. Web searching is fast and apps are running well, not that I use my phone for much more than a phone.
A few days later my new battery arrived and comparing to the old one, it appeared that the old one had a slight bulge. I charged the new one right up, discharged and charged again and now no more battery drops.
One last tweak I wanted was to try change the status bar icons. I found Xposed Installer and was able to change the icon colours to white but not the icon pictures. Good enough for me.
So now I'm very happy with my 5 year old defy, took a bit of trial and error but got there in the end. So in a nutshell: -
- If your battery is dropping upon installation of a Rom, likely need a new battery.
- If you phone is lagging, look what is taking all the Ram and look for a lite option or uninstall. Facebook is bad for that.
Note that there are many old links to roms and other mods so finding things that work was at times a challenge but here's the process that I found worked for me and works if bricked as well, which I did a couple of times.
If Bricked or to get back to stock
Download RSD Lite
Install drivers for the phone
Download an SBF for your region, I used Telstra with 2.2.2
To install custom rom
Install and use Superoneclick to root (may need to turn off antivirus)
Install 2ndinit.apk then run it. May need to reboot phone first
Download the Rom and Gapps and put on SD card of phone
Get into custom recovery
Wipe Data and Cache
Install Rom and Gapps
Wipe Cache and Dalvik Cache (for all but one Rom, I forget which one, read instructions)
Reboot and enjoy.

the gun rom link is down, where you downloaded it?

That was one of the few that worked. I accessed from the defy wiki page then I think downloaded from the XDA thread.
Yep, there some links in the last post of the MG ROM thread. Post #222.

Good someone still use defy. I give up after digitizer gone mad. Time run over this device... Uuuh, just if it had 1 gb ram and dual core...

Good to hear that someone else still have this cute little thing. I have too, as my second device. The ROMs I tried on this device! Man, it's countless. I had dropped it on all the different terrains you can think of, yet it's still fully healthy (save the jack and usb covers - they are loose now) without a single crack. I didn't have any covers or screen guards. It stayed true to its name. I will never regret spending money to buy this, it is one of Moto's legendary devices. I think I'm drunk, but it feels good to say all this. I'll keep this device forever with me - a product from a time when smartphones weren't made in an oven, but carefully and delicately cooked up.

Digitizer gone mad me too, the upper line is not working, but it is a good phone, for kids.
Which seller you order the battery?
Can you suggest ROMs to watch videos on Kodi, or Youtube?
I liked this phone, this is the best size phone, what i ever had.
Why the companys not make phone like this size, one hand controlled, with 2GB/32GB, and quad cpu??
Now i have Samsung S4 mini, and it is big for me

Battery was off eBay, can't remember seller but was Australian selling genuine batteries.
Just try all the roms possible, that's part of the fun
Sent from my SM-T210 using Tapatalk

I've been wanting to play around w/ my old defy again. This thread may have got the ball rolling. What do you all use as your daily driver? I've got a xperia z3 compact, but want a new phone. unfortunately, I think my best bet is to just get another z3 compact cheap and save it as a backup?

Hi tronjojo, I was still using my Defy until recently I found an old 4 year old Samsung Galaxy SII of my wife's. The problem for her was that it was switching off all the time so she got an S5. I've now flashed various roms and fixed the random reboot issue. The only thing I wish it has is the notification LED.
Sent from my SM-T210 using Tapatalk

I bougnt a Defy + battery on my Defy Red Lens, made my own BL7 fixed SBF and nandroid with 720p patch which made it a Defy Plus, then I rooted it and repartitioned to install CM11 and has made it very usable in 2016.

Make that Defy in 2018
I'm still using a Defy, since 2011. The battery still lasts longer than that in my wife's new Sony Experia X Compact, about as long as in my daughter's Xiaomi Redmi 4X. I will probably have to move to another device somewhere in 2018 as one of the more important apps - the Swedish BankID app - will cease support for Android 4.4 but that is more or less the only reason. For the rest the thing still does what it did 7 years ago so were it not for this I'd keep on using it until it gave up from sheer old age or electron migration or whatnot.

Make that Defy in 2020
I've recently tried if my Defy+ could learn some new tricks and I thought I'd share my findings.
CM11 build
I tried to build CM11 from Quarx repository, but it seems that many of its dependencies no longer exist and whole project is no longer buildable.
3.0 kernel
This one builds fine, however I was unable to boot it - there's one frame or random pixels followed by a reboot. I checked many branches and put the output into most probable directories. I wish there were any instructions as to what actually do with a built kernel. TWRP zips found here didn't work either. Anyone?
SD card size
Defy supposedly shouldn't work with SD cards larger than 32GB. But did anyone try bigger cards? My Defy mounts 256GB cards without any problems.
Debian on chroot
I set up a Debian environment with debootstrap. Unfortunately outdated kernel puts a limit on a Debian version that could be run. For 2.6.32.9 it is Debian Jessie.
With XServer XSDL it is possible to run a full graphical environment.
2.6.32.9 kernel modules
I also succeeded with building kernel modules for the old kernel. These are mostly filesystem modules and cryptographic ciphers. Now I could use whole Debian Jessie repository (49GB) locally from a squashfs filesystem.
Another nice feature is encryption with dm-crypt/LUKS.
I uploaded modules that insmod loads without any error.
CA certificates
These should be updated with system updates, but we won't have new CM/Lineage/stock releases anymore, so I did it by hand. If you want to try it for yourself, remount /system as writable, remove contents of /system/etc/security/cacerts/ (they could be expired) and copy certificates from the archive. Certificates are same as Debian's ca-certificates version 20200601.
Mirror
I also uploaded tools and images - self contained with instructions to go back and forth between stock and CM11, because many links here are spread across many threads or simply dead. Kernel modules and certificates are for CM11. I didn't try them with anything else.
I can't post a link to these files, because this is my first post. Search for ybea in Motorola Defy section at AndroidFileHost.

Another 2020 Defy warrior
ybea said:
3.0 kernel
This one builds fine, however I was unable to boot it - there's one frame or random pixels followed by a reboot. I checked many branches and put the output into most probable directories. I wish there were any instructions as to what actually do with a built kernel. TWRP zips found here didn't work either. Anyone?
Click to expand...
Click to collapse
Hello! Did you check on /bootstrap/bootstrap/binary and other folders? There seem to be a zImage (and the recovery one).
I tried to flash and boot the ROM at http://blechdose-live.de/download/kernel/3.0.x/:
Tried flashing from TWRP 2.8: failed.
Extracted the update-binary, copied it to /tmp and executed it from ADB shell (/tmp/update-binary 3 0 /sdcard/cm11-blah.zip) and flashed with some things, mostly partition related errors. After rebooting, it stays on black screen (turned on), ADB available but unauthorised (just look on Github how to enable ADB from recovery to solve that) and that's all; the ROM doesn't work. I'll try debugging this to check if I can do something.
ybea said:
CM11 build
I tried to build CM11 from Quarx repository, but it seems that many of its dependencies no longer exist and whole project is no longer buildable.
Click to expand...
Click to collapse
What a sad thing, this year even quarx2k.ru became offline...

MaicoLinuX said:
Hello! Did you check on /bootstrap/bootstrap/binary and other folders?
Click to expand...
Click to collapse
Files extracted from 20131213 version did not work for me. I tried swapping /bootstrap/ (and /system/bootstrap/) zImages, binaries, edited cmdline, anything I could think of. Always with the same outcome - black screen.
Flashing in TWRP (v2.6.3.0) initially also failed. Fix_TWRP_and_boot_kernel3.0_v2.zip (on AndroidFileHost) makes it succeed. It is 3.0.8 kernel. It froze during the boot, restarted and finished eventually.

ybea said:
Files extracted from 20131213 version did not work for me. I tried swapping /bootstrap/ (and /system/bootstrap/) zImages, binaries, edited cmdline, anything I could think of. Always with the same outcome - black screen.
Yeah, it did the same for me. Did you read the logcat while device was in that screen? I saw something crashing there (can't remember), anyway that's not so useful if you need a whole new ROM just for the new kernel version. Maybe modules are causing problems?
Pretty offtopic, did you try the OTG function? I can't get it to work, most people say it should work out of the box but I wasn't able to use my USB mouse. Didn't check dmesg, though.
Click to expand...
Click to collapse

MaicoLinuX said:
ybea said:
Always with the same outcome - black screen.
Click to expand...
Click to collapse
Did you read the logcat while device was in that screen?
Click to expand...
Click to collapse
How could I? Android isn't running yet. It it Linux that either fails to load or silently panics. That is my understanding anyway.
The right thing to do would be to check how cm11 build compiles the kernel and the 2nd-init (or whatever it is), but I am not knowledgeable enough, nor keen enough to do that.
OTG is buggy, but usable. If it doesn't work, unplug and plug it again. It is quite normal for my defy to recognize a device on a second or third attempt. No problems with mice, keyboards, flash drives, usb hubs. On the picture in the previous post you can see it with a wireless keyboard+touchpad. If I remember correctly, the driver is set to output 200mAh max. Maybe you mouse draws more (rather unlikely for a mouse). It works for me with cm11-20161124. Also, I think the port outputs 5V even after a device is disconnected, so it unnecessary drains power, but I am not so sure about it.
dmesg should definitely log any new device. Even if android stays quiet. If there's silence, perhaps your cable may of wrong type. USB A to USB micro varies with resistancy across two pins. I don't remember the details. If it is OTG cable, then it should work.
Or simply you have dirty socket/plug pins.

ybea said:
How could I? Android isn't running yet. It it Linux that either fails to load or silently panics. That is my understanding anyway.
Click to expand...
Click to collapse
AFAIK 2ndInit keeps adbd running so you can take a logcat/dmesg from there, also faced the same issue while flashing CM10.2 OTG kernel on CM11 (what was I thinking?) and from there was able to see that something was crashing.
ybea said:
The right thing to do would be to check how cm11 build compiles the kernel and the 2nd-init (or whatever it is), but I am not knowledgeable enough, nor keen enough to do that.
Click to expand...
Click to collapse
Nah, I think just taking some time to understand the 2ndInit boot process is enough, anyway when I get some free time I'll check about this all.
About OTG things, now will install CM11 3.0 kernel and see how it works (I expect some unstability) but don't really need to use the Defy, it's just there for experiments
Anyway, my main goal now is to install Debian natively (on /data partition because of the size) and get X running. As you said, the 2.6.32 kernel puts the limit at Jessie, but that's not a problem as it's still mantained IIRC. I'm using a prebuilt rootfs but it keeps throwing Segmentation Fault whenever I try to chroot there, don't know what happens with this.
I'm doing the same on other 2 phones (Galaxy Y and Pocket Plus, ARMv6 and v7 respectively) but one doesn't boot my compiled kernels (?) and the other complains about the buggy framebuffer driver (thanks Samsung/Broadcom). I went pretty offtopic...
PD: tried to flash some JB Ice Gun Edition v2.02 from CWM and after reboot the phone just is stuck on boot splash, but WIUI runs fine. Maybe the JB IGE BootMenu is broken or something like that.

MaicoLinuX said:
About OTG things, now will install CM11 3.0 kernel and see how it works (I expect some unstability)
Click to expand...
Click to collapse
I didn't have any luck with flashing zips with only the kernel. This 20131213 rom is the only way i know of. But frankly, there's more instability then stability in it. For example only home and power buttons work. OTG also non functional.
MaicoLinuX said:
As you said, the 2.6.32 kernel puts the limit at Jessie, but that's not a problem as it's still mantained IIRC. I'm using a prebuilt rootfs but it keeps throwing Segmentation Fault whenever I try to chroot there, don't know what happens with this.
Click to expand...
Click to collapse
Jessie is no longer maintained. It stopped being oldstable about a month ago. AFAIK it changes little - apt continues to work; unless your applications have dependencies to newer libc, they should at least compile.
I build Debian root with debootstrap. On host machine:
Code:
debootstrap --arch armhf --foreign stable /debian http://http.debian.net/debian
Then mounting on Defy:
Code:
# Mount an sd card partition
mount -o remount,rw /
mkdir -p /debian
mount -o remount,ro /
mount -t ext3 -o noatime,suid,exec /dev/block/mmcblk0p2 /debian
mkdir -p /dev/shm
mount -t tmpfs -o rw,nosuid,nodev,noexec none /dev/shm
mount -t proc proc /debian/proc
mount -t sysfs sysfs /debian/sys
mount -o bind /dev /debian/dev
mount -o bind /dev/pts /debian/dev/pts
mount -o bind /dev/socket /debian/dev/socket
mount -o bind /dev/shm /debian/dev/shm
Then debootstrap second stage:
Code:
LD_PRELOAD= TMPDIR= PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOME=/root SHELL=/bin/bash /system/bin/chroot /debian /debootstrap/debootstrap --second-stage
Done. To login:
Code:
chroot /debian /bin/su -
Don't chroot into bash. It will leak Android's shell environment into Debian's.
Android has its own groups and users. To make Debian adapt:
Code:
dpkg -i android-permissions_0.2_all.deb
Edit /etc/group, so that it contains:
Code:
inet:x:3003:root,_apt
net_raw:x:3004:root
Edit /etc/passwd/:
Code:
-_apt:x:104:65534::/nonexistent:/bin/false
+_apt:x:0:65534::/nonexistent:/bin/false
Edit /etc/adduser.conf:
Code:
-LAST_SYSTEM_UID=999
+LAST_SYSTEM_UID=99900
-LAST_SYSTEM_GID=999
+LAST_SYSTEM_GID=99900
-FIRST_UID=5000
+FIRST_UID=500000
-LAST_UID=8999
+LAST_UID=899900
-FIRST_GID=5000
+FIRST_GID=500000
-LAST_GID=8999
+LAST_GID=899900
Then:
Code:
apt-get update
apt-get install dialog
apt-get install locales
dpkg-reconfigure locales
apt-get install less man
If apt can't resolve hostnames select a nameserver in /etc/resolv.conf.
This how I setup Debian on chroot. Some of these steps may be unnecessary - they got accumuated over the years and I don't fully remember reasoning behind them. Debian inside /data/ should work too. I can imagine there would be problems with permissions on fat32 /sdcard, but /data/ is ext3.

My experience with Remix OS on my Asus T100HA

Here' s my general experience with Remix OS (v 3.0.206) on my Asus T100. Not surprisingly, it's much the same to my Android x86 experience.
First, a big thanks to the team members at Jide and Anroid x86! And now on to my experience...
The install to my hard drive didn't proceed smoothly. I'm not sure it was because I already had Android x86 installed or because I have my Z drive mapped to my LAN and the install program tries (and fails) to mount my EFI partition there in order to install grub. To get past the failed install, I manually modified my EFI partition to add a menu item for Remix OS alongside Android x86.
After resolving the installation woes, Remix booted fairly quickly and the setup option worked fine. The OS works pretty well and seems to allow all my Android apps to run. I haven't installed and tried them all yet though.
Not all the hardware works. Here's what works and doesn't:
Working
Touchscreen - works
WiFi - 2.4 and 5 GHz both work. WiFi seems to stop working and can't be re-enabled if the tablet sleeps.
Track pad - works, but can't be disabled using the keyboard function key
Keyboard function key volume up and down
Keyboard function key brightness up and down
Dock USB
GPS
Suspend. (The notification light did not go out, so it wasn't fully suspended.) I didn't fully test suspend, so it may or may not be working properly.
Battery icon
External speakers
Accessing my dock hard drive
Not working
Auto brightness
Camera. It doesn't work at all.
HDMI Out. Video displayed does not fully fill width of screen. Audio still comes out of the T100. Booting will not complete if HDMI is connected; it stalls at the command line.
Notification/camera on light - stuck permanently on.
Auto rotate (and no manual rotate either)
Keyboard function key volume mute
Keyboard function key to disable/enable the track pad
Esc key doesn't always behave as the back key.
After putting the tablet into the keyboard dock, Remix launches its File Manager *every time*. It's annoying.
Not tested
Bluetooth
I had freezing issues with a previous Release Candidate of Remix, so this version is usable by comparison. However, with so many non-working items, Remix on the T100 is just passable and not quite ready for a daily driver for me. v 3.0.206 fixed an issue with not being able to use WiFi after it was turned off (and back). If auto-rotate was working, I'd consider using it as a daily driver...

Can you please share your installation procedure?

awyeong said:
Can you please share your installation procedure?
Click to expand...
Click to collapse
Hi, I must have missed the notification of your reply...
I purposefully omitted the installation procedure because it was a pain, I started with android-x86, and I don't really recall the exact steps. Are you having a specific issue?

Hi,
I also have a T100ha & was thinking about putting Remix on it. Actually i was debating buying a Chuwi hibook pro 2 to play with (windows 10 + remix). But its really identical to the T100HA I already have in terms of hardware specs (or at least close).
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?

RichTJ99 said:
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
Click to expand...
Click to collapse
You don't need to create a new partition or resize an existing partition. It gets installed on your C Drive, most of it being installed in C:/RemixOS or whereever you choose. Your MBR will be modified to allow it to boot to WIndows or Remix.
Remix does not "run on top of" WIndows 10, like an emulator or VM. It is installed on the same hard drive, but is booted separately. But that reminds me...if you power on your tablet, it will boot straight to Windows. In order to boot to Remix, you have to a) hold power/Volume down to get to grub where you can select Remix, or b) Use Advanced Startup within Windows 10 to boot to Remix. It would be better if the Grub menu was presented on boot without the button mashing. Thanks, Microsoft/Asus!
You can/should try out a USB install to test it out. You can see what works/doesn't work for yourself and judge whether you want to install it to your hard drive or not. I still have it installed, but only use it occassionally.

So this isnt like Bluestacks which runs within windows? What I dont like about Bluestacks is the resources it uses even when its not running. The T100HA has very limited ones.
I see a number of posts on reddit with people trying to figure out how to install this on the T100HA.
Because I am a little fuzzy - Can you live install the ISO on a USB drive (like Ubuntu) for testing?
Anything not working for you on Remix?

So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.

RichTJ99 said:
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
Click to expand...
Click to collapse
This is the part that I don't exactly remember what I did to get it working.
You've probably disabled Secure Boot in Windows (required). I used Rufus to make my USB stick. I had problems when I made it with LiLi. So, if you didn't use Rufus, give it a whirl. Try the resident mode too.
Also, I think I used the Android-x86 USB install and copied the RemixOS files over top of it. Alternatively, go to http://www.jfwhome.com/2016/01/04/latest-steps-to-install-ubuntu-on-the-asus-t100ta/ and follow Step 1 only... First Steps: Prepairing for the Ubuntu Install

I'm stuck on logo...can you put your grub.cfg file here?
or al least the remix os entry...in other PCs, changing parameter I solve that...but now I can't in my asus T100taf...thanks.

Touch screen dying - coincides with Linage reflash and GApps Install

So my 10 was working fine yesterday on an older LinageOS release. However, today it had a software issue, so i thought it time to update and do a clean to the latest linage release and open gapps.
Now, i cannot swipe the notification bar down and using a screen test app, it appears the top of the touch screen is not registering touches.
I think it must be hardware, but thought id shout out here incase any one else has ever had this issue and managed to resolve in software?
As a work around, ive setup Nova and down swipe to open the notification bar, not great but at least its usable.

Mine is fixed yaaay
I had the same issue the upper 15% doesn't work...
A week ago I did a command from the PC to lower the screen so i can use the device:
adb shell wm overscan 0,0,0,260
Today I wanted to revert back to full screen instead of using only 85% so i did the command with default values:
adb shell wm overscan 0,0,0,0
Now it is working with no issues so i can confirm it is not hardware fault must be software.
If anyone has the same issue try the first command and reboot the phone the use the second command. (You need a PC with adb installed)
Good luck

Thanks, tried and it dosnt work on mine. Here is a image of a screen draw test, is this the same area that failed on yours?
best image host

Development [ROM][10.0][UNOFFICIAL] LineageOS 17.1

LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Known issues:
You tell me
Instructions :
1. Boot into twrp
2. Advanced -> ADB Sideload -> Swipe
3. adb sideload copy-partitions.zip
4. Go back into sideload mode
5. adb sideload lineage.zip
6. Wipe Data
7. Reboot to bootloader
8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads :
https://build.lolinet.com/file/lineage/ginna/
Source Code: https://github.com/motoe7
ROM OS Version: LineageOS 17.1
ROM Kernel: Linux 4.9
Version Information
Status: Stable
Credits:
Electimon - The entire device bringup
Rohan Hasabe - TWRP bringup, helped with device bringup
betaxab - Gave devices, helped with TWRP and device bringup
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip

Thanks to everyone who contributed to these bits, I'm hopeful that by the end of the year I will be using my new moto-e-2020 as my main phone to replace my aging moto-g-2015. I've got a couple first bugs/issues/showstoppers to report, but first I think it's important to note-
Finally I'm able to go to walmart (in the usa) and buy a sub $100 ($70) 'roid (boostmobile) phone (meeting some other criteria as well) which I can immediately install a (mostly?/sdks/tools) non-google-built os on. I erred a bit by doing lots of research (to avoid paying more for a moto g7) and forgetting that the moto-e-2020 is *not* at the moment on motorola's list of models their registered (free) dev program will give bootloader unlock codes for. However after thinking I was going to have to return the phone, I parsed the verbiage on their page and decided to just try 'fastboot oem get_unlock_data'. Then tried going through motorola's unlock code process. To my pleasant surprise, they did give me an unlock code. My next hiccup happened when I was disappointed to discover the 'allow oem unlucking' option was greyed out. I netsearched and found a similar samsung issue that was resolved on phones that hadn't been updated/activated by setting their date back a week. That didn't work here, but what did work was giving my new phone access to wifi and letting it start an update. After a few minutes, while it was still updating, the 'allow oem unlocking' was no longer greyed out, and the rest of the install was straightforward enough (getting used to a and b slots for recovery).
Anyway, as for the first glaring issues-
1) random reboots, seemed at first yesterday it would average less than 10 minutes of uptime and rarely an hour. Seems a bit better right now, I'm seeing if I can get some adb logcat output of interest. Let me know if there are other tests/logs I should do. I haven't yet tried the modded lineageos18. The image I used was lineage-17.1-20210119-UNOFFICIAL-ginna.zip.
2) mobile data won't work. I note that I first activated after installing this rom. I wonder if it would have helped to activate with stock android like I probably did long ago with my moto-g-2015. Note that it shows up as 't-mobile', however given my moto-g with boost showed up as 'sprint' and boost using sprint infra which merged with t-mobile recently...? My aboutphone:simstatus shows 'network:t-mobile', 'mobile network state:disconnected' (but mobile data enabled). If I uncheck automatic network selection, I can click on 'boost' by name on a list (that doesn't include t-mobile) and it will say 'connected' right away, but with no change I see otherwise. There was a weird thing with activation as an additional line, boost first charged me $20, then later charged me $30. And the confirmation sms for the activation happened hours later, but mobile data still isn't working.
3) I'd like to know if twrp is really necessary. I noticed a recovery.img in the download directory, guessing that might be the lineageos17.1 version I was happy to see available for my moto-g-2015. I'm guessing I could try it myself, but I would like to avoid brick-risky things.
4) I wonder if the 'your phone has an unlocked bootloader / can't be trusted' post unlock splash screen can be changed (with the same?) images that are available for the moto-g-2015 (that I read can be used on some other models as well). At least with the moto-e-2020 the splash has a black background.
Feel free to let me know if there are tests I can do or logs I can provide to help. Looks very promising, but not quite usable for me so far.

hi yes please do
adb logcat > logcat.txt
and send me the logcat.txt after around 10 seconds of it running

i've fixed the random crashes.
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip

Electimon said:
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Click to expand...
Click to collapse
Confirmed (so far, but I'm optimistic). Also I'm quite happy to report that mobile data is now working for me as well (maybe just a reinstall would have fixed?).
The most glaring (new?, not sure) issue/bug now is that speaker output doesn't seem to work except during calls. If I plug in headphones I do get output. Jacksensing failure could be an explanation?
Then after that, I'm getting the sense that the microphone level/gain is not good. Testing by leaving a vmail on my moto-g-2015 the level of the audio on the message seems too low. That is seperate from the longstanding issue I have had with the moto-g-2015/lineage output level. Long ago there was a known issue with a mixer_paths.xml workaround, though I've just lived with seeming lower, but barely tolerable, level since then. I've always planned on going full aosp rebuild with removing whatever softvol max limits are in place whereever. But the mote-e-2020 definitely doesn't have that problem (side by side comparison of same vmailbox checking). But it does seem with this rom the mote-e-2020 has too low mic/gain level. Seems like there could be a standardized testrig used for lineageos qa that could report expected decibel levels/metric on the devices wiki so people know what to expect.
In any event this update will definitely let me get to more serious testing.
Also worth noting, I did the upgrade by repeating the install steps. I noticed that on the copy partitions sideload it ends with an error after doing a lot of partitions fine, then ending with vendor(_b) "dd /dev/block/dm-2: write error: no space left on device". I think that may have happened on my initial install and I just ignored it, and it doesn't seem to matter (yet, afaict).

Ok, can you post a logcat while trying to play audio? Thanks

also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.
Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.

Not gonna lie, super excited about this! I never thought that this device would gain traction on XDA due to it being a very low budget device but boy am I glad it's getting some love.

I'm having some trouble here. I can flash Lineage no problem in TWRP the phone just won't boot. So then I try to follow the instructions exactly and get this...
So my moto e booted into Lineage unexpected (I didn't think it would). Nevertheless I'm going to share the command lines I followed since some suggest they failed and I find that strange since Lineage is thus far working.
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.049s
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>adb sideload copy-partitions.zip
serving: 'copy-partitions.zip' (~47%) adb: failed to read command: No error
V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Total xfer: 1.00x
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.015s]
Finished. Total time: 0.023s
V:\Everything Android\platform-tools>
Also, about half the internal storage is apparently taken, I must've done something wrong in the flashing process?

Cyb3rSl4v3 said:
also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.
Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.
Click to expand...
Click to collapse
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.

Lahpyrcopa said:
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.
Click to expand...
Click to collapse
This morning my first recompile from source finally finished (took a solid couple days and an impressive swap storm on an 8G system (and cough 18G of swap used that I saw. perhaps mka -j 2 will help (default -j left 4 massive java processes running, metalava something or other)). I'll post more as I progress. I had to comment most of device/motorola/ginna/libshims/Android.mk to get it to compile. I was guess/expecting wifi tethering not to work, it seems to say no sim / phone service, though I had let my plan lapse.
But the cool thing is that I do now get speaker out. Another issue is that the recovery.img doesn't want to flash (preboot verification failed, I'll see if I can still reflash twrp next). And now that I've verified I can can compile moto-e-2020/17.1 (after having gotten moto-g-2015/17.1, with CPU_SSE42=false and JAVA_TOOL_OPTIONS=-Xmx6g, kept for e-2020), I'll go try 18.1 again to see if I can get it built without gapps (though I did recently renotice a /d/gapps app on f-droid). I had an issue with libllvm_android/LegalizeIntegerTypes there on my last attempt, but perhaps a fresh start (and reposync) will help me there as it did on 17.1 (which I'm quite optomistic I'll be happy enough with if need be soon enough).

also, I discovered that MotoBootLogoMaker from another xda thread does work (on linux/debian/mono to boot), and while I haven't tried replacing the untrusted/orange unlocked bootloader warning yet, I was able to extract that image with the tool, so I'm hopeful it can be replaced (perhaps excepting the small 'N/A' rendered font text which could perhaps be obscured by some whiter pixels in a custom logo/splash/background, or maybe the font/color is tweakable with that tool too).

Damn, it must take a very beefy machine to operate on android to take days to compile the system.
Well like I said before I only really need the headphone jack working for audio and that creepy message that Moto gives about having an unlocked phone that can't be trusted is absolutely hilarious . Look, I get it Motorola if you read this, you don't want to be liable for jack all nor do any of these even bigger empires. Just tone the scare tactics down a smidge so I can breathe!
To the developer, thanks for your effort. I thought that given the price of the device no one would bother with it.

clarifying a few points above-
- i had forgotten the twrp install step of via .zip (including magiskboot and ramdisk-recovery.cpio stuffs). I.e. I was just able to use the lineage171 recovery to install its build, but just not to install itself as twrp can (perhaps an a/b magisk thing, not sure maybe I saw that was a known thing until lineage adds that functionality? Perhaps I could reuse the twrp zip, or presumably better start building twrp from github now that I'm past the point of having a building lineage tree to use for that purpose)
- indeed MLBM can replace the orange bootloader unlocked splash/logo (which unlike moto-g-2015, is shown after a few milliseconds of the normal seperate logo image). But it doesn't look like there is a way (yet?) with MLBM to effect the 'N/A' text/font/color which remains (again, presumably obscurable if you put an area of white pixels over it on your custom replacement)
- my specific 17.1(and 18.1) build issue with device/motorola/ginna/libshims/Android.mk not-so-much-of-a-workaround-because-simdetection/calling-no-longer-works was a result of this-
"
FAILED: finishing build rules ...
Error: makefile error
Output:
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm64) missing libqsap_sdk (SHARED_LIBRARIES android-arm64)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm) missing libqsap_sdk (SHARED_LIBRARIES android-arm)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mbuild/make/core/main.mk:972: ESC[31merror: ESC[0mESC[1mexiting from previous errors.ESC[0m
"
At one point, still even earlier in noob mode, I guessed and tried treating (iirc) /vendor/{lib,lib64}/libqsap_sdk.so as perhaps missing device blobz, and/or went with ALLOW_MISSING_DEPENDENCIES=true. Maybe I'll try again now that I've otherwise got a successful build. I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.

Cyb3rSl4v3 said:
I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.
Click to expand...
Click to collapse
github.com/LineageOS/android_system_qcom seems to be the answer to my libshims/libqsap_sdk.so issue. I now have a build that at first glance at least is a good reproduction with the addition that speaker out now works for me. Still no in-call volume control. Though as I typed that I see that I seem to be getting crashes similar to what I first reported here but were fixed with the update build. I'll skim my logs a bit...

and seeing the recent git commits and motog7/17.1/nightlies thread (and my log) it seems I can live without MotoActions for the timebeing. I may try toggling some of the recentish audiofx things at some point to see if that gets the in-call volume control working. Also, /d/gapps seems to not apply without root, but I'll try building 18.1 again.

Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.

googleverifysux said:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
Click to expand...
Click to collapse
From my experience it is 80% stable with certain glitches that occur.

I've tried flashing multiple different build of this ROM, and everything is working great, except when I try to flash GAPPS (anything besides pico) and I get an error about having no space on my /system partition.
When flashing PICO gapps, the installation finishes, but the OS fails to boot afterwards.
Any ideas? I've tried Lineage 17 and 18 now and can't get either to work.

googleverifysux said:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
Click to expand...
Click to collapse
It is gapps free, and everything is working on my Moto E. Can't get GAPPS to flash for the life of me though.