I'll take a lookWhat version of USB MIDI driver is used in the firmware?
I'm trying to connect a synthesizer via USB-OTG, but MODALapp does not see the device, although there is MIDI support in Android 6. More information here.
At the same time, G-Stomper app detects MIDI devices, but according to the manual below, it looks like the classic Android 5.x based USB MIDI driver.
More information here.
Dear @Rortiz2, if the firmware uses an old version of USB MIDI driver, could you please implement a new version of the driver in next updates so that USB MIDI devices work properly? Thanks in advance.
While I backported all the necessary 3.18 sdcardfs commits, people complained about internal storage problems so I ended up disabling it as it's not enforced until Android 9.
Yeah, douglas (and giza) can support anything at this point (even 18.1). I'll start with 17.1 as soon as I fix the last bugs here.
Why stick to an outdated version when you can upgrade to a lot newer version where you have much more configurations. Also, yes, you can optimize the apps and stuff so that it uses the same amount of memory in the end.
You are right that we should focus on the newest version. I mentioned about A9, because this version seems compact to fit to tablets equipped only with 1.5G Ram. If A10 or later runs well on douglas, absolutely no need to pay attention to A9. Another reason is up to A9, we can build Rom with 8G Ram PC. Ofc, this is pretty personal reason, no need to have further consideration.Why stick to an outdated version when you can upgrade to a lot newer version where you have much more configurations. Also, yes, you can optimize the apps and stuff so that it uses the same amount of memory in the end.
BTW: My problem is solved, thanks for any feedback!
Oh god, RAM is not my only problem. I'm building with a 2011 PC with a 2nd Gen I7 + 16GB DDR3 RAM.You are right that we should focus on the newest version. I mentioned about A9, because this version seems compact to fit to tablets equipped only with 1.5G Ram. If A10 or later runs well on douglas, absolutely no need to pay attention to A9. Another reason is up to A9, we can build Rom with 8G Ram PC. Ofc, this is pretty personal reason, no need to have further consideration.
Let us enjoy new version of Android. Thank you @Rortiz2 for your endless effort.
Been dealing with that my whole life. My current PC is a 2009 ThinkPad with a Core 2 Extreme dual-core and 8GB RAM... but I digress.
Run the following commands with ADB on TWRP and PM me the results.Hey, not sure what happened, but I turned my Douglas on after a few days and it was stuck in a boot loop or something. It got stuck on the LineageOS boot animation for a while and then rebooted to TWRP automatically. This happened every time.
1. I tried to clear cache, but it said2. Then i tried re-flash this rom zip, that I already had on the internal storage and it said "Failed to mount (No such device)" for `/cache`, `/system` and `/data`.Code:
Failed to mount '/cache' (No such device)
Now I seem to have lost everything that was on the internal storage, and it cannot mount anything. It won't connect to my computer either. It says "No media storage found. Make sure device is unlocked and MTP is enabled." It seems like the data partition does not have any file system format. And am unable to create one either. It says
failed to mount and unable to recreate `/data/media`
I would try to flash the old Fire OS image, but can't seem to mount the internal storage on to my Linux pc. Any ideas?
Edit: I also tried the repair file system, but it gives me the same "Failed to mount" error. And I found an old TWRP backup that i've been trying to copy onto the tablet using adb, but it keeps rebooting after like 20%. Maybe the internal storage is dead?
Edit2: Okay, so I successfully copied the backup to the mounted SD card. But it during restore using twrp, it says This /data backup was made with ext4, so i need to change it back to ext4 to ensure it boots. But it won't let me change file system using twrp
Formatting Data using mke2fs Done. Failed to mount '/data' (No such device) Unable to recreate /data/media folder Updating partition details... Failed to mount '/system' (No such device) Failed to mount '/cache' (No such device) Failed to mount '/data' (No such device) ...done
adb shell cat /sys/class/block/mmcblk0/device/cid adb shell cat /sys/class/block/mmcblk0/device/csd adb shell mount -t debugfs none /sys/kernel/debug adb shell cat /sys/kernel/debug/mmc0/mmc0:0001/ext_csd
/proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: