Develop Bugs

[UTIL] One Click Lag Fix

This software is currently in BETA status! This means that a lot of people have tested, and reported good results. There are still issues, but if you take note of the known issues and make sure to avoid them, you very likely will have no problems in using this fix. The worst this software should be able to do is force you to reflash your phone, by removing the battery and turning on the device with HOME+VOLDOWN+POWER + Odin and then following one of the many guides to flash a new firmware to your phone.
More questions about how this fix works? Check out the FAQ - http://forum.xda-developers.com/showpost.php?p=7620940&postcount=2
UPDATES:
There is currently a 2-3 version made by me that can be found here that has more features: http://forum.xda-developers.com/showthread.php?t=751864
Tayutama has made an update.zip version that is easy to install - http://forum.xda-developers.com/show...&postcount=208
Chainfire has a .NET version of this fix with some nice features - http://forum.xda-developers.com/showthread.php?t=751513
Ubuntu version is here: http://forum.xda-developers.com/showpost.php?p=7671640&postcount=583
[size=+2]DEPRECATED:[/size]
[size=+1]This lagfix is now marked as DEPRECATED and the following tool should probably be used in all circumstances that this one would be used in: http://forum.xda-developers.com/showthread.php?t=760571[/size]
Details about what this fix does:
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc. It allows only 1GB for application data at this stage, down from the 2GB of application data when running stock.
Folders that are currently supported:
/data/data
/data/system
/data/dalvik-cache
More folders can be added, and should help performance further.
Advantages for this fix over mimocan's fix
Does not require an external SD card.
Allows the external SD card to be removed and reinserted into the device.
Faster speed (Quadrant benchmarks of 2000+ vs 1700 for mimocan's fix)
Possible battery savings, by not requiring the external SD card to be always active.
Requirements for this fix
(Beta Release) The ability to reflash your device if something goes wrong.
Any firmware should work, including 2.2 froyo firmwares. (Tested!)
Rooted device - I used this: http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
Busybox 1.17.1 from http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229 -
You must have a busybox version installed that has mkfs.ext2. If unsure, install 1.17.1 from that thread!
That thread has an APK that you must sideload onto your device. Once installed, you will have a new application on your phone called "BusyBox Installer".
Run this application, and it will have a button to install busybox. Click the button, and it should install it for you!
If you have made a mistake and run this without the right busybox, there may be a solution for you! Check out this post: http://forum.xda-developers.com/showpost.php?p=7580071&postcount=187
A windows box to run the batch script. (Batch script does very little, you should be able to easily modify this to run in any enviroment.)
If you are already running mimocan's lag fix, check out this post: http://forum.xda-developers.com/showpost.php?p=7578137&postcount=85
How to run the one click fix
Place your phone into USB debugging mode: Settings->Applications->Development
Download the attached ZIP file.
Unzip to a folder of your choice.
Double click "lagfixme.bat"
Wait for it to complete.
How to remove the one click fix
Double click "unlagfixme.bat"
Wait for it to complete.
New Method for applying this lag fix
Tayutama has developed an update.zip version of this lag fix. I haven't tested it personally, but some people have had a lot of success with it. It should be more robust and less likely to cause you problems. I believe it avoids all rooting and busybox issues as well! Nice! Check out this helpful post by glockyboots for instructions. You must only use one lag fix, not both! http://forum.xda-developers.com/showpost.php?p=7587405&postcount=417
Known Issues
1) If you do not have 1GB of free space on /data, this fix won't be able to run. Looking into workarounds.
2) Script fails if your busybox does not have mkfs.ext2 - Solution is to update busybox - http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229
3) Script will not work if you have previously used mimocan's fix on your current firmware. Try this to revert mimocan's fix: http://forum.xda-developers.com/showpost.php?p=7578137&postcount=85
4) Make sure your device is plugged in, and that you have the correct drivers. Permission denied errors usually mean that your device is not in USB debug mode. Settings->Applications->Development
Credits
Big thanks to mimocan for putting us all on the right track in how to sort out lag problems!
Big thanks to ykk_five for showing us all how well loopback filesystem mounting works!
Warning, this software is BETA QUALITY, and is known to function on a lot devices! You must have busybox 1.17.1 !
This doesn't meant that this won't break your phone and force you to reflash. It does mean that if you do everything properly and you read everything a few times, you very likely will have no issues!

What if im using mimocans fix. Will it work?

heman1310 said:
What if im using mimocans fix. Will it work?
Click to expand...
Click to collapse
Won't currently work with mimocans fix. I can make a slightly altered version that will work with mimocan, but if you could install mimocan, you should be able to open the .txt files and check how this is done, and do it yourself in ADB!
It seems a bit strange to have two lag fixes installed at once anyway...

Nice! Looks ok at a glance! Though I see you have changed the directory name and the loop file..

kalpik said:
Nice! Looks ok at a glance! Though I see you have changed the directory name and the loop file..
Click to expand...
Click to collapse
I based this off my script from yesterday, so it has the names I used and not the names other people used. Feel free to just edit the text files to change the names.
Important part to note is that this fix is intended (eventually when all issues have been sorted out) for people who have no idea what linux is!

RyanZA said:
I based this off my script from yesterday, so it has the names I used and not the names other people used. Feel free to just edit the text files to change the names.
Important part to note is that this fix is intended (eventually when all issues have been sorted out) for people who have no idea what linux is!
Click to expand...
Click to collapse
EXACTLY! And good job for the effort! Too bad I already applied the fix manually, so don't feel like doing it all over again. Though if you really need to test it out, let me know, ill waste another half an hour

RyanZA said:
Important part to note is that this fix is intended (eventually when all issues have been sorted out) for people who have no idea what linux is!
Click to expand...
Click to collapse
nice work RyanZA but i think it wouldn't harm people to know that they ARE in fact using linux behind that fancy ui ... this is after all a dev-forum

Great job ............. I have a question (noob).... And the device? Should I connect it to my computer at what time, and in which way the usb cable?
Have I to save or transfer some file (extracted from lagfix) for the galaxy samsung s?
Tanks.

jodue said:
nice work RyanZA but i think it wouldn't harm people to know that they ARE in fact using linux behind that fancy ui ... this is after all a dev-forum
Click to expand...
Click to collapse
you are right, but be sure there will be lots of people that want this, that eaven dont know how windows works, they just want to use it ;-)
edit: the first proof ;-)
@bucklino connect your rooted galaxy s to usb...

FadeFx said:
you are right, but be sure there will be lots of people that want this, that eaven dont know how windows works, they just want to use it ;-)
Click to expand...
Click to collapse
hehe, yeah i guess so
... i'm already looking forward to "[Q] Will the new improved one click lagg-fix make my head explode?"

jodue said:
nice work RyanZA but i think it wouldn't harm people to know that they ARE in fact using linux behind that fancy ui ... this is after all a dev-forum
Click to expand...
Click to collapse
It actually looks more like they are using DOS at this point. The fancy ui is just a little coloured text window for now. I might make this into a proper GUI at some point if I'm bored!
bucklino said:
Great job ............. I have a question (noob).... And the device? Should I connect it to my computer at what time, and in which way the usb cable?
Have I to save or transfer some file (extracted from lagfix) for the galaxy samsung s?
Tanks.
Click to expand...
Click to collapse
You don't have to do anything! That's the point!
You put your device into debug mode. Settings->Applications->Development
You plug the device in.
You double click "lagfixme.bat"
Bang!
Just gotta make sure that its rooted, and has busybox (well, it needs mkfs.ext2 included in busybox).

It worked well for me thanks

[Q] will this lag fix also fix the delivery lag of my galaxy s?
it was supposed to arrive last wednesday, today i caled the guy and he told me i get it this week... however he´s a friend of mine and i trust him. just cant wait so long...............

RyanZA said:
It actually looks more like they are using DOS at this point. The fancy ui is just a little coloured text window for now. I might make this into a proper GUI at some point if I'm bored!
You don't have to do anything! That's the point!
You put your device into debug mode. Settings->Applications->Development
You plug the device in.
You double click "lagfixme.bat"
Bang!
Just gotta make sure that its rooted, and has busybox (well, it needs mkfs.ext2 included in busybox).
Click to expand...
Click to collapse
Tanks again!!!!

FadeFx said:
[Q] will this lag fix also fix the delivery lag of my galaxy s?
it was supposed to arrive last wednesday, today i caled the guy and he told me i get it this week... however he´s a friend of mine and i trust him. just cant wait so long...............
Click to expand...
Click to collapse
hm, that sux! i had to wait about 2 weeks when i ordered my htc magic because they f***** it up. terrible 2 weeks of watching/reading reviews and crying. this time i ordered from amazon and got it 3 days later ...
good luck for your lagging problem

how to confirm tat its completed without any problem ?
it shows "
Setting up permissions
All Complete!
Script complete!
Press any key to continue . . ."
but i did a benchmark test its still 899 same as before i do this.

hq83 said:
how to confirm tat its completed without any problem ?
it shows "
Setting up permissions
All Complete!
Script complete!
Press any key to continue . . ."
but i did a benchmark test its still 899 same as before i do this.
Click to expand...
Click to collapse
have you applied any other fix previously?
have you rebooted since you applied the fix?

hq83 said:
how to confirm tat its completed without any problem ?
it shows "
Setting up permissions
All Complete!
Script complete!
Press any key to continue . . ."
but i did a benchmark test its still 899 same as before i do this.
Click to expand...
Click to collapse
Huh... hmm..
Do you still have the log window open? If you could paste the full log here I can take a look. Like I said, alpha...
Your files may be in different locations than mine, or you may not have the right busybox.

FadeFx said:
[Q] will this lag fix also fix the delivery lag of my galaxy s?
it was supposed to arrive last wednesday, today i caled the guy and he told me i get it this week... however he´s a friend of mine and i trust him. just cant wait so long...............
Click to expand...
Click to collapse
[A] If you apply this fix to the delivery/schedule systems of goods transporters, delevery times will be halved worldwide .

jodue said:
have you applied any other fix previously?
have you rebooted since you applied the fix?
Click to expand...
Click to collapse
nope.
was on JM2 without any fix.
yes did a reboot after that.

[DEV] ArchLinux on the TF300T(G)

I've always been more of an Arch than Ubuntu person (how do you know if someone uses ArchLinux? Don't worry, they'll tell you)
This requires you to be unlocked and on the JB bootloader. I disclaim all responsibility if it somehow turns your tablet into a pile of ashes...
What works:
Dual boot with Android.
Internal storage and MicroSD Card
X11, with compositing
Audio
Mouse and keyboard on the dock, as well as dock hotplugging.
Touchscreen
Playing videos (full 1080P works great.) using Xfce's media player
Sensors (Light, compass, accelerometer, gyro). These are all exposed under sysfs.
Charging / Dock charging. This appears to be managed by the kernel.
USB gadget (as a RNDIS device for network access via USB)
CPU frequency scaling / Tegra LP core. The LP core is automatically used you can see its status in /sys/kernel/cluster/active (when that file reads LP) and its use is simply what the current CPU1 use appears to be.
WiFi, with NetworkManager
3G, on the TF300TG model, with NetworkManager
Battery (and dock) status in Xfce
USB port on the dock
Some sensible key remapping (Back -> Escape, Search -> Alt, Home -> Super)
What doesn't work:
Bluetooth
Two finger scrolling with the mouse
Rebooting from Linux (have to do a sync then hard power off)
Basic framebuffer console - to get dual boot working I had to remove the FB console
Using "standard" xv (as in, mplayer -vo xv). Untested really, use gstreamer.
Cameras
Current priorities:
Get Bluetooth working
Get two finger scrolling working.
Get rebooting working
Anything else is untested. Currently, I'm using the TF300TG's kernel source at https://github.com/cb22/tf300tg_jb_kernel - which is just the standard source from ASUS with a patch or two.
Dual booting:
At the moment, my "hybrid" initramfs checks for a file ".boot_linux" on the internal SD card (/data/media/.boot_linux or /storage/sdcard0/.boot_linux - same thing). If it exists, it boots Linux, otherwise, Android starts up. It wouldn't be difficult at all to make a simple Android app with a "Reboot into Linux" button, and vice versa one for Linux with "Reboot into Android"
Important note:
Currently, the provided kernel / initramfs is built for the TF300TG. It does seem to work fine on the TF300T however.
Downloads:
Kernel + Initramfs blob: https://rapidshare.com/files/2827313479/hybridkernel.blob
RootFS with Xfce: https://rapidshare.com/files/201953815/linux.tar.gz
Installation:
Flash the blob to staging using fastboot.
Untar the rootfs to /data/linux/. The easiest way to do this is probably to copy it across to the Transformer via adb or MTP, then run
Code:
$ su
# mkdir /data/linux
# tar -xzvf /storage/sdcard0/linux.tar.gz -C /data/linux
Issues:
Apparently permissions aren't set properly when untar-ing. This can be "fixed" by a chmod 755, apparently. As soon as I can, I'll make a better way of installing this (update.zip style)
Credits:
This work is based off the Arch Linux ARM distribution

Sounds good, I think would be nice together with a dual boot kernel :good:

AWESOME! This is what I've been looking for. Thanks for kick starting this, I'm flashing the recovery right away. I suppose I'll start playing around with the .config and see where that takes me.
C'mon people! lets get this done so we can then try out dualboot options and bring some GNU/Linux flavor to the Transformer Pad.

Good work. Im waiting for a working Ubuntu so I can install Blackbuntu.
Shame Im on ICS bootloader as I would have tried it.
The Prime Ubuntu project aint had any updates recently sadly.

if you get this working, would you then maybe get the win8 tablet version also working? Loving linux, but Win8 on tablets even a bit better :good:

Valantur said:
AWESOME! This is what I've been looking for. Thanks for kick starting this, I'm flashing the recovery right away. I suppose I'll start playing around with the .config and see where that takes me.
C'mon people! lets get this done so we can then try out dualboot options and bring some GNU/Linux flavor to the Transformer Pad.
Click to expand...
Click to collapse
That's the aim! It would be really nice to have Android for tablet mode, and GNU/Linux for dock mode.
Nekromantik said:
Good work. Im waiting for a working Ubuntu so I can install Blackbuntu.
Shame Im on ICS bootloader as I would have tried it.
The Prime Ubuntu project aint had any updates recently sadly.
Click to expand...
Click to collapse
You can always use NVflash to backup your bootloader and such, then freely flash away. That's what I did (I'm on the TF300TG, and no one has uploaded their JB dlpkgfile *hint* *hint* and it's not available on ASUS's site yet) so I simply restored using NVflash to get my ICS with 3G back for when I'm not dev'ing.
Also - the ideas port over to any GNU/Linux system fairly easily once figured out - getting Ubuntu running wouldn't be much more effort. I'm using Arch to start since I understand it better (and prefer it)
-angel* said:
if you get this working, would you then maybe get the win8 tablet version also working? Loving linux, but Win8 on tablets even a bit better :good:
Click to expand...
Click to collapse
Highly unlikely, sorry, and definitely not my field of expertise!

yeah nP - was just a think if they would have similar kernels...
Video looks very good, but as you say in the first post, nothing for ppl who don't know how to flash it and as I need the tablet for school I'd need dual boot at all... :/
But get on your working, really nice, but unfortunately I don't know anything about developing such things, so I can't help you...

This is awesome i'm gonna have to read up on this to see how it works! great work! Always wanted something like this.

cb22 said:
You can always use NVflash to backup your bootloader and such, then freely flash away. That's what I did (I'm on the TF300TG, and no one has uploaded their JB dlpkgfile *hint* *hint* and it's not available on ASUS's site yet) so I simply restored using NVflash to get my ICS with 3G back for when I'm not dev'ing.
Also - the ideas port over to any GNU/Linux system fairly easily once figured out - getting Ubuntu running wouldn't be much more effort. I'm using Arch to start since I understand it better (and prefer it)
Click to expand...
Click to collapse
Yeah.
Might try when I get some spare time.

Great initiative! I'd personally prefer a native debian distro over Arch but I figure once you've laid the groundwork the road's paved for more distro's.

Finally, a real reason to unlock the tab. When this works and it's dual boot, I will be unlocking and installing this.

Amazing! I just hope that it will be possible to dualboot with normal android installed. If so, it would be absolutely perfect. Keep going, buddy!

Would it be possible to get it dualboot with an external HDD's? Because you can only get external SD's only up to 64gb (as I know and not all of them work) and external HDD's usually have a bit more storage

I've been playing around with this today, and I was wondering if you could upload a barebones arch system (without KDE) but with any other improvements you might have been working on.
Thanks

spenat said:
Amazing! I just hope that it will be possible to dualboot with normal android installed. If so, it would be absolutely perfect. Keep going, buddy!
Click to expand...
Click to collapse
That's what I've been working on! I have a kernel that supports full features of both Android and Arch (well sorta - no FB console, so no boot messages or such) and an initramfs that allows you to select (at the moment its hard coded, but I'll make a simple interface to select which one to boot, as well as things like telling Android to reboot into Linux, or vice versa). In terms of implementation, essentially it's just an initramfs chain loader.
Valantur said:
I've been playing around with this today, and I was wondering if you could upload a barebones arch system (without KDE) but with any other improvements you might have been working on.
Thanks
Click to expand...
Click to collapse
I shall - I've gotten WiFi working (works great with NetworkManager even) - I just have a very busy week with varsity work, I'll try and put the latest stuff online over the weekend.

Hello,
Can you use the package manager and install other DM the same way we would on a X86pc?

aachour said:
Hello,
Can you use the package manager and install other DM the same way we would on a X86pc?
Click to expand...
Click to collapse
I guess you could, once you get wifi working. We are waiting for cb22 to upload a new kernel+rootfs with a working wifi interface.

cb22 said:
That's what I've been working on! I have a kernel that supports full features of both Android and Arch (well sorta - no FB console, so no boot messages or such) and an initramfs that allows you to select (at the moment its hard coded, but I'll make a simple interface to select which one to boot, as well as things like telling Android to reboot into Linux, or vice versa). In terms of implementation, essentially it's just an initramfs chain loader.
I shall - I've gotten WiFi working (works great with NetworkManager even) - I just have a very busy week with varsity work, I'll try and put the latest stuff online over the weekend.
Click to expand...
Click to collapse
This project looks awesome. i have a tf300t and intermediate arch linux experience( have made multiple working setups, compiled drivers etc, and would love to do anything i can to help this project, let me know if there is anything i can do

yeah! always looked for linux on this tablet! keep up the development guys

Valantur said:
I guess you could, once you get wifi working. We are waiting for cb22 to upload a new kernel+rootfs with a working wifi interface.
Click to expand...
Click to collapse
Unfortunately I didn't have time over the weekend to get things tidied up and uploaded - I start writing exams soon so things are a bit hectic on my side (coupled with the fact that I actually use my TF for varsity). I'll try to sort things out as soon as I can

[Q] USB Masst Storage ? UMS ...

How to get UMS on HTC M8 ?
I have been reading many things about it; I am not interessed in alternatives. I WANT USB MASS STORAGE.
I have stock rom. But ... maybe I may reflash if it can help getting UMS. But I would prefer just change the kernel, and keep the rest of my stock ROM.
Also, I am very disapointed that TWRP does not offer UMS. Are there other recovery that can do it ? I am fine with a reboot if recovery can help.

The phone doesn't offer UMS. Be disappointed all you want, it's not going to happen mate.

doublehp said:
How to get UMS on HTC M8 ?
I have been reading many things about it; I am not interessed in alternatives. I WANT USB MASS STORAGE.
I have stock rom. But ... maybe I may reflash if it can help getting UMS. But I would prefer just change the kernel, and keep the rest of my stock ROM.
Also, I am very disapointed that TWRP does not offer UMS. Are there other recovery that can do it ? I am fine with a reboot if recovery can help.
Click to expand...
Click to collapse
Recovery can't do it anymore; it was removed from the kernel completely (it seems).
To answer your question from the other thread, I have UMS on the Stock Sense 6 ROM. The screenshots I took were from Bad Boyz HK Edition. I have a non-HK M8, Sprint variant. I'm not sure what other information you want from me, or how I could've "pretended" to have it by my screenshots. Believe what you want, I guess.

This topic is NOT a dead end road.
I have been said by various people that:
- it had been removed around android 4.2, and re-added later.
- some people have it with recent devices
- it is possible to add it manually, several ways
- presence of UMS in a phone may depend on manufacturer: a given Android version may have it in some ROM by some people, or not in other ones ...
What I am going to try soon:
skulldreamz said:
there is a something you can do to keep USB mass storage. Its called Linux + permissions
Click to expand...
Click to collapse
nodiaque said:
Install latest HTC sync manager with drivers, then remove HTC sync manager but not driver. Connect your phone, it will appear as an mtp device (like a camera). Double click on it and browse sd and internal mass storage. That's your problem, Windows issue.
Click to expand...
Click to collapse

Captain_Throwback said:
Recovery can't do it anymore; it was removed from the kernel completely (it seems).
To answer your question from the other thread, I have UMS on the Stock Sense 6 ROM. The screenshots I took were from Bad Boyz HK Edition. I have a non-HK M8, Sprint variant. I'm not sure what other information you want from me, or how I could've "pretended" to have it by my screenshots. Believe what you want, I guess.
Click to expand...
Click to collapse
Android version, kernel version, hardware version, ROM version ...
Sens 6 is ambiguous; I have 6.0, so I assume there could be Sense 6.1 or 6.2.
Stock does not mean anything, because if your phone is branded by some company, the ROM can contain any modification, including kernel changes. When you say stock, you must specify "stock from where ?". I thought I had a pure HTC stock ROM, but in fact, I have found it was slightly modified by the phone provider who sold it to me (found my provider's name somewhere in some part of the ROM; twice in fact; once in the system ROM, and one in the GSM network lock. Network lock was expected; but brand name in ROM version was not). That's why exact ROM version is very important, with kernel version. Since you have one HK edition, and one Sprint, both your M8 seem very different from mine. So, your ROM and kernel versions probably differ from mine.
So, you have access to both HK and non HK editions ?
And recovery has nothing to do with /system. Absolutely unrelated. Dev who write recovery make their own kernel, and can do anything with it. Son whatever the system can't do, recovery could still do it. They just use different kernels, and different bins. To the point ... one friend used his recovery partition to ... install a legacy Debian in it (it was a failure, but that's not my point: at some time, he could get a classic shell, and even initiate phone calls ... from a pure legacy Debian ... 0% Android; it was a classic dual boot, with two systems as much different as Linux can be from Windows).

You must understand one thing: UMS is available only if you have an SDCard. You cannot have UMS for the internal SDCard (the one that you can't remove, like M7). The internal is only accessible through MTP.

doublehp said:
Android version, kernel version, hardware version, ROM version ...
Sens 6 is ambiguous; I have 6.0, so I assume there could be Sense 6.1 or 6.2.
Stock does not mean anything, because if your phone is branded by some company, the ROM can contain any modification, including kernel changes. When you say stock, you must specify "stock from where ?". I thought I had a pure HTC stock ROM, but in fact, I have found it was slightly modified by the phone provider who sold it to me (found my provider's name somewhere in some part of the ROM; twice in fact; once in the system ROM, and one in the GSM network lock. Network lock was expected; but brand name in ROM version was not). That's why exact ROM version is very important, with kernel version. Since you have one HK edition, and one Sprint, both your M8 seem very different from mine. So, your ROM and kernel versions probably differ from mine.
So, you have access to both HK and non HK editions ?
And recovery has nothing to do with /system. Absolutely unrelated. Dev who write recovery make their own kernel, and can do anything with it. Son whatever the system can't do, recovery could still do it. They just use different kernels, and different bins. To the point ... one friend used his recovery partition to ... install a legacy Debian in it (it was a failure, but that's not my point: at some time, he could get a classic shell, and even initiate phone calls ... from a pure legacy Debian ... 0% Android; it was a classic dual boot, with two systems as much different as Linux can be from Windows).
Click to expand...
Click to collapse
Android version: 4.4.2
Kernel version: 3.4.0 (the one that comes with the stock ROM)
Hardware version: 0005
ROM Version (I think you mean software version?): 1.54.651.10, 1.54.654.15 (these are the same, one is just for HK, the other is technically not)
Carrier: Sprint
To clarify, I do not have multiple devices. I have one Sprint device. I was simply running the HK software on my regular M8 because it's available. There are no hardware differences between the versions; it's just some software & firmware.
I know /system has nothing to do with recovery. I never said the two were related. I can use the same kernel from the stock ROM where UMS works in recovery, but there is still no UMS available there (the lun device simply doesn't mount). The recovery I use (TWRP, which I build from source) uses the same kernel source as the ROM, so no difference there.
Currently I'm running my GPE port which doesn't have UMS (only MTP), but I'm going to flash my stock rooted 1.54.651.10 and take a screen recording of the "USB File Sharing" mode I referred to previously. I don't like being accused of being a 'pretender' so that should alleviate any doubt. If it doesn't, then I'll have to say that you're beyond convincing and move on.

I am perfectly clear with what an SD card is. A cat is not a dog. M7 does *NOT* have SD card. M7 does software emulation to comply with previous android standards; and this software emulation is not about emulating an SD reader; only about emulating the "classic mount point". Emulation of hardware would provide some /dev/block/mmcblk1 . M7 does not emulate a virtual mmcblk1. It only emulates /mnt/sdcard as being a moint point, by ... creating apropriate symlink.
By UMS, I am talking about ... converting the physical SD card reader into a SD-USB adapter.
And ... to go even further ... if I was an android dev (I am a linux dev; I just never installed the Android SDK), I could EASILY create an SD emulator for the M7, and implement UMS for M7, three ways:
- for fully unlocked phones, put the full mmcblk0 device in UMS via home made recovery
- for partly unlocked devices, at least /data partition via recovery
- for rooted devices, create a virtual block inside /data filesystem, and use it as source block for UMS
As of now, I know ebough about UMS to know that even the M7 could have UMS in various ways.
But, I don't want to install Android SDK, and, I don't want to dig in Android dev; I am not in mood to heavily hack my ROM; and I will try to stick to classic solutions, and stop doing things manually on my new phone. On my previous phones, I fixed many android issues wth home made shell scripts. I want to stop doing that. Use official kernels, and public projects.
If I just wanted my phone to be an SD adapter, i could build my own kernel, and do it in a few hours. But I decided that this phone would stay being a phone, and NOT become a hacking box like the previous one.

Captain_Throwback said:
Android version: 4.4.2
Kernel version: 3.4.0 (the one that comes with the stock ROM)
Hardware version: 0005
ROM Version (I think you mean software version?): 1.54.651.10, 1.54.654.15 (these are the same, one is just for HK, the other is technically not)
Carrier: Sprint
To clarify, I do not have multiple devices. I have one Sprint device. I was simply running the HK software on my regular M8 because it's available. There are no hardware differences between the versions; it's just some software & firmware.
I know /system has nothing to do with recovery. I never said the two were related. I can use the same kernel from the stock ROM where UMS works in recovery, but there is still no UMS available there (the lun device simply doesn't mount). The recovery I use (TWRP, which I build from source) uses the same kernel source as the ROM, so no difference there.
Currently I'm running my GPE port which doesn't have UMS (only MTP), but I'm going to flash my stock rooted 1.54.651.10 and take a screen recording of the "USB File Sharing" mode I referred to previously. I don't like being accused of being a 'pretender' so that should alleviate any doubt. If it doesn't, then I'll have to say that you're beyond convincing and move on.
Click to expand...
Click to collapse
Ah !!! VALUES !!!
Andro 4.4.2, same.
kernel 3.4.0-g0c47a10, [email protected] #1, SMP PREEMPT, you probably forgot the last part, or used a tool that does not provide it.
I don't have HW version in my phone (this is probably my ROM) - I know what it looks like, I had it on my previous phone. The thing that most looks like your HW version has for me the value "002"
ROM 1.54.1020.10 CL325784
Before update, I had ROM 1.54.1020.5
So, we do not have the same hardware (my HW is ver 01 or 002), and ... completely different ROM.
Would need you exact kernel version. If we have the same kernel, and your phone can do UMS, then, it's just a matter of messing stuff in /system (the two guilines I wuoted above may work). If we do not have the same kernel ... I won't even try those tricks: my kernel probably can't do it.
If TWRP is available from sources ... I will ask a friend to rebuild it for me ... including the stuff required for UMS (he can do it, 100% certain). Once he does the kernel, the rest is peace of cake in a recovery ROM.
Don't flash again. Just give me your kernel version. If the kernel is the same for your two ROMs, then, your two roms can have UMS; just a matter of tweaking the right things at the right place; in short, find the APK or system script that handles it, and copy it to the other ROM.
I would be interessed in downloading your two ROMs. Especially if one can do UMS, but not the other one. Whether they share the same kernel or not. I just don't know if I would have the patience to push them in my phone to see things by myself; but if I took the time, I may be able to extract the relevant bit of code, and try to copy it to my ROM. Issue is that I have only one phone; and it would mean ... spending 2 days on it, and not be able to use GSM at all for 2 or 3 days (no phone, no SMS). It would be interesting, but I am not sure I would really take time and efforts to do it.

Captain_Throwback said:
Android version: 4.4.2
Kernel version: 3.4.0 (the one that comes with the stock ROM)
Hardware version: 0005
ROM Version (I think you mean software version?): 1.54.651.10, 1.54.654.15 (these are the same, one is just for HK, the other is technically not)
Carrier: Sprint
To clarify, I do not have multiple devices. I have one Sprint device. I was simply running the HK software on my regular M8 because it's available. There are no hardware differences between the versions; it's just some software & firmware.
I know /system has nothing to do with recovery. I never said the two were related. I can use the same kernel from the stock ROM where UMS works in recovery, but there is still no UMS available there (the lun device simply doesn't mount). The recovery I use (TWRP, which I build from source) uses the same kernel source as the ROM, so no difference there.
Currently I'm running my GPE port which doesn't have UMS (only MTP), but I'm going to flash my stock rooted 1.54.651.10 and take a screen recording of the "USB File Sharing" mode I referred to previously. I don't like being accused of being a 'pretender' so that should alleviate any doubt. If it doesn't, then I'll have to say that you're beyond convincing and move on.
Click to expand...
Click to collapse
Sir, if you can figure out how to get ums on gpe m8 I'll give you twenty bucks, maybe more depending on my mood.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

doublehp said:
Ah !!! VALUES !!!
Andro 4.4.2, same.
kernel 3.4.0-g0c47a10, [email protected] #1, SMP PREEMPT, you probably forgot the last part, or used a tool that does not provide it.
I don't have HW version in my phone (this is probably my ROM) - I know what it looks like, I had it on my previous phone. The thing that most looks like your HW version has for me the value "002"
ROM 1.54.1020.10 CL325784
Before update, I had ROM 1.54.1020.5
So, we do not have the same hardware (my HW is ver 01 or 002), and ... completely different ROM.
Would need you exact kernel version. If we have the same kernel, and your phone can do UMS, then, it's just a matter of messing stuff in /system (the two guilines I wuoted above may work). If we do not have the same kernel ... I won't even try those tricks: my kernel probably can't do it.
If TWRP is available from sources ... I will ask a friend to rebuild it for me ... including the stuff required for UMS (he can do it, 100% certain). Once he does the kernel, the rest is peace of cake in a recovery ROM.
Don't flash again. Just give me your kernel version. If the kernel is the same for your two ROMs, then, your two roms can have UMS; just a matter of tweaking the right things at the right place; in short, find the APK or system script that handles it, and copy it to the other ROM.
I would be interessed in downloading your two ROMs. Especially if one can do UMS, but not the other one. Whether they share the same kernel or not. I just don't know if I would have the patience to push them in my phone to see things by myself; but if I took the time, I may be able to extract the relevant bit of code, and try to copy it to my ROM. Issue is that I have only one phone; and it would mean ... spending 2 days on it, and not be able to use GSM at all for 2 or 3 days (no phone, no SMS). It would be interesting, but I am not sure I would really take time and efforts to do it.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 07:54 PM ---------- Previous post was at 07:37 PM ----------
The kernel source for this is available on HTCDev, as it is with all the M8 variants. None of the kernels (as-is) will get UMS working in recovery, though.
The Sprint variant uses a different defconfig than the GSM version, so perhaps whatever is different between the two is what is making the difference. It's also possibly a userspace difference, since the CDMA carriers like/need to customize the ROM a bit more for everything to work.
I'm just surprised that not all of the M8 Sense ROMs include the Disk Drive option.

DeathmonkeyGTX said:
Sir, if you can figure out how to get ums on gpe m8 I'll give you twenty bucks, maybe more depending on my mood.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have asked Galoula ( https://play.google.com/store/apps/developer?id=Galoula ) if he can help us. Explaind him what I think about the topic. The easiest way, to me, is to take TWRP from sources, and rebuild kernel, adding the required symbols; TWRP being a recovery, the rest should be peace of cake. It's small, and actions have low impact; in a recovery, if things break, you see it at once; there are no 32th level side effects you discover 6 months later. Yes, requires reboot; that's acceptable to me. I prefer fixing this in few days of work, and keep my ROM as is, rather than spending weeks or months tracking side effects of messing MTP in /system.
Galoula is busy for now; may take 2 or 3 weeks before he rebuilds TWRP.
The aim of recovery is to flash /system. I can't see how re-adding UMS to TWRP could possibly break flashing /system; it may break other things; but I really don't mind. It would break more things if we try to fix /system. So, if I bring you a new TWRP, it's Galoula you shall thank. He is going to do the dirty work.

Captain_Throwback said:
The kernel source for this is available on HTCDev, as it is with all the M8 variants. None of the kernels will get UMS working in recovery, though.
The Sprint variant uses a different defconfig than the GSM version, so perhaps whatever is different between the two is what is making the difference. It's also possibly a userspace difference, since the CDMA carriers like/need to customize the ROM a bit more for everything to work.
I'm just surprised that not all of the M8 Sense ROMs include the Disk Drive option.
Click to expand...
Click to collapse
UMS used to work in recovery in my previous phone (htc sensation, stock with android 2.2). Why do you think it could not work in recovery for M8 ?
Very interesting screens; mine is completely different. I don't think any one is interessed in detailed screenshots from a non working phone.
If you say that both yours, and my kernels can be downloaded from HTC ... *with the conf*, then I will have a look. But build will be done by Galoula anyway.

P.S. The reason UMS works on one of my ROMs and not the other is because one is Sense and the other is not. The AOSP code got rid of UMS a while ago, but HTC preserved it (at least for Sprint) in Sense.

Gpe isn't aosp so I had some hope. My m8 is a gpe from the play store, not a rom or ruu. Even if it just worked in a version of twrp that would be fine, it's rare when I need ums but often enough to where I'd gleefully spend $20 on it.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

In case any of you is interested taking a look, I think the apk which is responsible for MTP and UMS is MediaProvider.apk
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Hello. I have a semi good news.
My view of the world changed tonight.
I received a message from andreasyeah telling me to try https://play.google.com/store/apps/details?id=com.softwarebakery.drivedroid&hl=en ... and it's amazing. He also recommends to use ElementalX kernel.
First, what UMS was for me untill yesterday ? Use my phone as SD to USB card adapter, and, make my PC able to read and write on SD, as if SD was in a legacy USB card reader. Plug phone, android unmounts sd, and pushes SD to USB, and PC can mount the SD, and do whatever it wants to it.
Whatever used to include .. repartition, reformat, and, some some of my friends like Galoula ... install a MBR on SD, so that, when any PC is broken, he can boot the PC by just plugging the phone. His phone became a classic external disk. Android could partly read the SD, with limitations (legacy android can only read first partition in FAT; having fat on non first part, and, reading non FAT partitions requires ... manual operations).
This app does things a completely differen way. To make the story short ... it downloads an ISO over internen, store it in your phone (at any place you like, any folder), and, presents this ISO as a USB-CD. Emulates the USB-CD, and provides the media inside. App let you choose amongst large choice of distributions, install CD, and live CDs. The last option is to ask the app to create an empty drive, and, eventually, format it in FAT.
Negs:
- phone is no more a SD adapter
- copying files from phone to PC requires to manually mount the FAT block, copy, unmount; then, the app will show it as a CD
- copying from PC to phone requires a CD burning soft, and will erease the whole block
- the process can fail at many places. Phone can fail to emulate the CD. PC can fail to detect it. But, in most case, PC will fail to see partitions inside the CD. Also, for me, boot failed on two computers (BIOS could see the USB CD drive, but boot failed without reason)
- apps only emulates a CD; so, in short, the volume is READ ONLY. Except for CDRW softs.
Advantages:
- can work for phones that do not have SD slot
- can store as many boot sections as you want.
- include a large pannel of distributions, live CD, and other similar stuff
- provides partial workaround for people like us who are limited to MTP by default.
- UMS independant from SD
- images can be stored at any place in the phone (or even over network for me ^^ my phone mounts NFS, Samba, CIFS, SSHFS ... )
Apps has good design, and offers a variety of UMS implementations, and a blacklist for phones known to not work.
Success is heavily ROM and kernel dependant.
So, depending on the reasons why you want UMS ... this could be an alternative. Or not
I am going to test related apps over night; first needed to make my report for this one.

https://play.google.com/store/apps/details?id=com.nextersoft.myusb
For Mac people who just want to transfer a few files. Free version is limited to 5MB/ day. It's a webserver with integrated upload service. Apk file is small. Nothing to setup. Start app on phone, open browser on PC. Does the job. Pro version is only $1 ... On phone side, it works in folder /mnt/sdcard/myusb/ .
There are other ways to do this. There are free webservers in which you can setup upload. This app does it all in one for you. At home, I do everything via NFS, sshfs, cifs, rsync, scp ... but ... when I am not home ... this app provides an EASY solution for file exchange. Especially when you just need to copy 2 or 3 files. It's fully compatible with just any network device. Did not try it, but I guess it shall work over wifi AP mode. Can be used as proxy, or temp host space between two other devices.
It could be done other ways, more efficiently, and for free. But, what I like in this app is ... works easily, defaults are fine, all in one, does the job, ultra easy upload (compared to other web-upload solutions I have seen). Not to be used daily for regular work; but very good rescue method when you need 100% compliance with exotic stuff. So, dispite the fact it looks completely off topic regarding ... UMS ... I still consider this as a relevant alternative. Previous post was about helping a PC to boot. This one is about "hell, my MAC does not stand MTP". The companion you need with this app is probably a zip archive software, when you need to work on large number of files.

Here is a quick tuto from a friend:
echo 0 > /sys/class/android_usb/android0/enable
echo 22D9 > /sys/class/android_usb/android0/idVendor
echo 2767 > /sys/class/android_usb/android0/idProduct
echo adb,mass_storage > /sys/class/android_usb/android0/functions
echo /storage/sdcard1/debian.iso > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file
echo 1 > /sys/class/android_usb/android0/enable
Here is the interesting part:
[email protected]_m8:/storage/emulated/legacy # cat /sys/class/android_usb/android0/functions
mtp,adb,mass_storage
This means ... my kernel can do UMS. I will dig this later.
Sounds like this method can be used to simulate several devices at the same time: several HDD, several CDs ...

Not sure if you're still trying to figure this out, but I got UMS working in TWRP . Link is in my sig.

[DEV/WIP] Kexecboot Bootloader for Galaxy Note 3 N900T - Boot Multiple Kernels

This is a development thread at the moment. I'm going to start working on porting the kexec-hardboot patches to the N900T (actually CyanogenMod hlte) kernel. With the kexec-hardboot patch applied, the kernel will be able to act as a second stage bootloader and boot other kernels. Combined with the kexecboot program, it can act as a second stage bootloader, allowing you to boot kernels from any storage device without flashing them. Ultimately the goal here is to dual-boot Android and non-Android Linux without having to re-flash kernels constantly. Like with my Note i717 port I will be focusing on kexec first, then getting Debian to boot on the device with the Freedreno graphics driver. The Note 3 is a very powerful ARM device and with Freedreno working it could play many of the 3D FOSS games.
Here is my modified kexecboot that I will be using:
https://github.com/CalcProgrammer1/kexecboot
Here is a video showing how it works on the Note i717 (it will work the same way on the Note 3):
https://www.youtube.com/watch?v=qtb-TSGumNo
My Note i717 thread:
http://forum.xda-developers.com/showthread.php?t=1787856
Here is the kexec-hardboot porting guide I will be using:
https://github.com/Tasssadar/multirom/wiki/Porting-kexec-hardboot
For anyone inclined you could also get MultiROM working with this. I am not familiar with that framework but have used kexecboot many times on many devices in the past, so I am going with that.
EDIT 1: I've got the main patch applied and I've found some numbers for the addresses that I think might work. Everything compiles and I'm able to build a boot.img and flashable zip, but I'm sure it won't work in its current state. The Note 3 uses a DSI command-mode panel which is different than the Note 1's video-mode panel in that it doesn't continuously refresh (i.e. at 60Hz). Instead, screen updates must be forced manually by using an ioctl for the framebuffer device. There are several ways to handle this - I could add this ioctl into kexecboot any time it draws to the screen but this would only work for kexecboot. Alternatively I could write a background program that sits in a 60Hz waiting loop and calls the ioctl repeatedly, simulating a video-mode panel. I've talked to some other people on the #freedreno Freenode IRC channel and the refreshing background program has been done with some success on other devices (2013 Nexus 7) so I think I'll take this route first as it will hopefully let me get a framebuffer console up for debugging with.
EDIT 2: I found a way to make kexecboot refresh the screen. I call the FBIOPAN_DISPLAY ioctl in kexecboot's framebuffer refresh function and that makes the kexecboot GUI appear on screen. Now to figure out how to build a kernel and pack a boot.img.
EDIT 3: I figured out how to make boot images, it requires a device-tree supporting mkimage tool such as this: https://bitbucket.org/itsmikeramsay/mkbootimg/src I was able to build a boot.img with a precompiled kernel and my new ramdisk with kexecboot, it worked enough to show the kexecboot GUI. Now to build my modified kernel into the mix and create a kexec-bootable kernel for CM11.
EDIT 4: I might put the Note 3 kexec on hold for a bit as I clean up the Note 1 and TouchPad port of Debian. I ran into an issue on the Note 1 with Kexec where CM wouldn't mount the internal storage when booted via kexec-hardboot. I still need the Note 3 as my primary phone so I can't hack on it without a backup plan.
EDIT 5: The issue with storage not mounting appears to be related to having an ext-formatted SD card inserted (which is where I keep Debian). Booting without the card inserted works fine. Hopefully the same applies to the Note 3.
EDIT 6: I got the kexecboot kernel builder scripts for the Note 1 up on github now and released the first version of it, so I'm going to look into the Note 3 some more. I didn't realize that the Note 3 uses device tree until I messed with it earlier. I'm not sure if kexec needs to reserve a dtb image for the kernel or not, that could be a major roadblock if so as the patch I ported didn't take device tree into account. I'm not entirely sure how device tree and atags work but somehow they're related apparently, at least in terms of kexec.
EDIT 7: I think I have my build root mostly set up for Note 3. Initial test was a failure, though it did at least attempt to boot my new kernel rather than drop into download mode like my earlier attempts. I need to figure out what device tree stuff is required in order to boot a compiled kernel with the new mkboot tool and then enable fbconsole so I can see when the display changes.
EDIT 8: I think I figured out how to make a dt.img file now for the device tree stuff, but I've found that my ramdisk doesn't work on the stock CM11 kernel binary nor my custom compiled one. It did, however, work when patched into LeanKernel's boot.img (replacing the default ramdisk). This was the result of that: http://i.imgur.com/c2racE1.jpg I may try using the leankernel defconfig as a base instead of the CM11 defconfigs.
EDIT 9: Derp herp derp herp didn't look at the boot partition size...it's 11.0MB. My cm-based boot.img was 12.3MB. Of course that ain't gonna work.
EDIT 10: WOOT! Kernel has booted, xz compression is some wizard level magic, it shaved off like 3MB without changing anything else. Now to reapply the kexec-hardboot stuff and see how it fares.
EDIT 11: I spent some more time looking into kexec-hardboot on the Note 1 (as it's a ton easier to debug since it has a video-mode panel) and figured out how to properly reset it. The important code is in relocate_kernel.S, an assembly function that does the very last wrap-up stuff before rebooting. On the Note I was letting the watchdog timer kick the reset after hanging on an infinite loop, but the Note 3 doesn't seem to have this watchdog in place and will loop endlessly. The important thing to note from this is that relocate_kernel.S uses physical addressing. The Note had a pretty in-depth reboot procedure and it looks like the Note 3 may be a bit simpler. I'll be looking into this soon to see if I can get it rebooting correctly.
EDIT 12: I'm going to use USB serial for debugging instead of messing with the stupid fbconsole. To initialize the USB you need to set up the ID fields in /sys/class/android_usb/android0 and set functions to acm. Then use getty (part of busybox) to open a bash shell on the port with "getty -n -l bash 115200 ttyGS0 linux". Then use minicom or other terminal on PC to connect to the ttyACMx interface.
EDIT 13: I was able to get a working shell through USB and play around with kexec tools directly. It would not boot when I did kexec -e, whether or not I used hardboot or not. I may need to apply a patch to load dtb images for the kexec'd kernel.
EDIT 14: Looks like I'll need to build my own kexec-tools based off the newest release (v2.0.7) which has device tree image support. I'm still looking for a hardboot implementation that uses dtb images.
EDIT 15: I dug through the stack of calls up from machine_kexec to figure out why machine_kexec was never called. It appears that kernel_restart_prepare (kernel/kexec.c, line 1595) might be hanging and keeping the system awake instead of dropping through to machine_kexec() like it should. Since we're rebooting with hardboot anyways it should be reasonably safe to just forget a clean shutdown and cut straight to the machine_kexec() function. The bootloader will reinitialize the hardware anyways. This is hopefully almost the end, as I'm sure my reboot code is being called and it is successfully rebooting. It hasn't booted the new kernel yet but it could be an address issue.
EDIT 16: Something's happening...I think I may be right on the edge of getting it working but not quite there yet. I got it to lock up after rebooting which means that the redirection was successful (redirecting to the kexec kernel instead of the kexec-boot kernel) but the kexec kernel is crashed or something. Probably something to do with device tree. It might require a dt.img passed in or it might require the command line being set.
EDIT 17: I managed to get Tasssadar's MultiROM kexec-tools to build. I talked to XDA user flar2 who had done some work on the HTC One M8 and ran into a similar issue with device tree kernels not booting. He mentioned that there may be some custom device tree entries that aren't being picked up by kexec-tools and gave me a link to a repository to look at. For now, here's my kexec-tools branch based on Tasssadar's work with the fixed-up Makefiles that compile correctly: https://github.com/CalcProgrammer1/kexec-tools/tree/kexec-tools-2.0.2 I will look into this more this weekend or so.
EDIT 18: So the Note 3 kernel doesn't have last_kmsg (RAM console) enabled for some reason, or at least it isn't appearing despite being enabled in config. RAM console shows the dmesg (kernel log) of the previous kernel run so long as the reserved RAM area isn't erased. This is important as it allows viewing any logs left behind by failed-to-boot kexec'd kernels. I'm guessing both the host (kexecboot) and guest kernel will need RAM console to be working for any meaningful debugging. Samsung has all sorts of goofy debug stuff (SEC_DEBUG_) but the RAM console doesn't appear to be part of that.
EDIT 19: After a lot of printk's and a lot of failures I got last_kmsg support working! This means booting a last_kmsg supporting kernel and then rebooting into another last_kmsg supporting kernel will grant you a /proc/last_kmsg file that contains the previous boot's dmesg log. This will be incredibly helpful for kexec testing. For any other kernel devs who want this capability, you need to register a platform_device for ram_console using the start and end addresses already included for the persistent_ram ram_console registration. For some idiot reason it reserves the persistent RAM but it doesn't set up a ram_console device to use said RAM.
EDIT 20: New Tools! With the help of some users in the S4 forum, I have some new debugging tools available to better see what's going on with reboots. First is viewmem (http://blog.maurus.be/2011/01/23/samsung-i9000-irom-dump/) which dumps memory to stdout. The Note 3 kernel has sec_debug which logs boot messages from the bootloader and optionally kernel to address 0x10000008 in memory. Viewmem is able to read this log as well as inspect other memory locations to see if things are where they should be. The other debugging tool is a physical serial port, hidden on the USB data pins. Putting a 615K resistor between GND and the ID pin of the USB connector as well as shorting the VCC and GND pins causes the port to go into serial debug mode on reboot. The D+ and D- pins become TX and RX, and hooking up a 3.3V serial interface (PL2303 USB serial breakout in my case) you can dump bootloader and kernel messages to a PC running a serial console.

cant wait to give it a shot
this sounds amazing for the note 3

sounds like Ubuntu will be coming soon
Cant wait to dual boot AOSP and TW
I'm so proud to be the same t mobile person as you
I take off my hat and bow!
only if I had a bank account I would so donate to you
Just keep doing what your doing
And you will become famous a xda
I will so make this Thread a Newsworthy Thread!

Update 4
Im crying
Well best of luck

Definitely worth waiting for, we'll be here

Robbdreality said:
Definitely worth waiting for, we'll be here
Click to expand...
Click to collapse
+1

I got framebuffer console working on the Note 1 a bit better last night, though it's still not great. I really need to get framebuffer console working on the Note 3 before anything because it makes debugging a whole lot easier. The super-high DPI might become a problem though, the text was already hard to read on the Note 1's 800p screen. This is what I'm looking forward to seeing on the Note 3: http://i.imgur.com/1kmKDOw.jpg

CalcProgrammer1 said:
I got framebuffer console working on the Note 1 a bit better last night, though it's still not great. I really need to get framebuffer console working on the Note 3 before anything because it makes debugging a whole lot easier. The super-high DPI might become a problem though, the text was already hard to read on the Note 1's 800p screen. This is what I'm looking forward to seeing on the Note 3: http://i.imgur.com/1kmKDOw.jpg
Click to expand...
Click to collapse
Same there But ubuntu
What linux is that one

Debian (testing). I chose it over Ubuntu because it works better in a chroot from within Android. Upstart (Ubuntu's init system) doesn't like chroot or running services from in a chroot as well. Ultimately the idea is to be able to use it both as a chroot within Android (to host ssh and samba and such while still being an Android phone) as well as a full blown reboot into Debian system for playing with the GPU and using hardware that Android normally locks. My TouchPad setup is exactly this, where the Debian rootfs is located within Android's data partition as /data/debian and the initramfs init script on my kernel bind-mounts that directory as the root directory before passing over to the Debian init. You could do the same with Ubuntu as well. The biggest issue is the kernel which you can put whatever distro you want on top of.

i wish you all the luck in the world hmm!?! No, ?!? I wish you all the luck in the whole cosmos! @CalcProgrammer1

update 10
im so happy

Agreed, love the progress

Update 11
Keep up the good work

USBhost said:
Update 11
Keep up the good work
Click to expand...
Click to collapse
+1

This is really cool
Sent from my SM-N900T using XDA Free mobile app

iakeco said:
This is really cool
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
ii there

Update 14, rootin for you

Robbdreality said:
Update 14, rootin for you
Click to expand...
Click to collapse
+1

Robbdreality said:
Update 14, rootin for you
Click to expand...
Click to collapse
Just now root'in? You should've rooted a long time ago! Using Android without root is a nightmare!

CalcProgrammer1 said:
Just now root'in? You should've rooted a long time ago! Using Android without root is a nightmare!
Click to expand...
Click to collapse
I will never get a device without root
The vary day that i got ny N7 i unlocked the bootloader and rooted it lol
But i think he meant something like im cheering for you

Has anyone installed an ARM Linux distro like Arch Linux ARM...

...onto this device? It's the perfect size for an ARM laptop and Arch Linux is a great Linux distro too. I'm helping some devs port/get running natively Arch Linux ARM on the semi-ancient/underrated HP TouchPad from 2011. If it could run natively on this tablet, then I'd highly consider getting it to play with it on it.

I'm looking to do this also, I just rooted my pixel and tried "Linux Deploy" but it failed at "mounting /dev/loop0", looks like the stock kernel doesn't support mounting loop devices so this will be impossible until we get a new kernel.
edit: /dev/loop0 exists so I don't know why mounting fails...
Sent from my Pixel C using Tapatalk

So I've finally got it to install Ubuntu! Here's the steps I took to get it to install successfully:
First mount the system partition as read/write and generate /etc/mtab by accessing the shell and switching to the root account and typing mount -o remount,rw /system; cat /proc/mounts > /etc/mtab
Then install Meefik's (the guy that created LinuxDeploy) version of BusyBox (Stericon's version apparently doesn't have the ar command)
In LinuxDeploy's settings, change the BusyBox Directory to /data/data/ru.meefik.busybox/files/bin and hit Update Environment
After that, go into the preferences and select Ubuntu, then whatever version you want, and ARM64 instead of ARMHF and hit Install and let it finish. If it screws up and you need to re-attempt the installation process make sure to delete /etc/mtab and regenerate it, otherwise LinuxDeploy will think the /sdcard/linux.img file is already mounted, fail and won't tell you why. This kept screwing me up for a while also.

it's interesting that your ubuntu is arm64 and not armhf. i can't understand how that would work. i have a nvidia tx1 which runs armhf ubuntu 14.04 so i would have guessed that the pixel would be the same. i guess i need to read into linuxdeploy a bit and see what that is about.

It's ARM64 because the Tegra X1 is a 64 bit processor ARMHF will work too. All it does it create a chroot easily, a little difficult to look deep into it because a large amount of it is done using a binary he created.

brando56894 said:
So I've finally got it to install Ubuntu! Here's the steps I took to get it to install successfully:
First mount the system partition as read/write and generate /etc/mtab by accessing the shell and switching to the root account and typing mount -o remount,rw /system; cat /proc/mounts > /etc/mtab
Then install Meefik's (the guy that created LinuxDeploy) version of BusyBox (Stericon's version apparently doesn't have the ar command)
In LinuxDeploy's settings, change the BusyBox Directory to /data/data/ru.meefik.busybox/files/bin and hit Update Environment
After that, go into the preferences and select Ubuntu, then whatever version you want, and ARM64 instead of ARMHF and hit Install and let it finish. If it screws up and you need to re-attempt the installation process make sure to delete /etc/mtab and regenerate it, otherwise LinuxDeploy will think the /sdcard/linux.img file is already mounted, fail and won't tell you why. This kept screwing me up for a while also.
Click to expand...
Click to collapse
How is everything working out so far? I'm tempted to pop the screen off mine when it shows up to flip a switch for some chrome os fun (if I can figure out a way to do it gracefully) but might also just roll with ubuntu. Really interested in hearing how your experience has been... Thanks for sharing.

Youre welcome! I did it just for the hell of it, haven't really used it much since I got it working. A native install would be much better, I plan on seeing if I can get it to connect to a local X server, VNC works but Ive always found it to be odd when controlling the cursor. I always install Linux on my Android devices just because I can, once I have it working I'm like "now what can I use it for?" and I always come to the same conclusion, pretty much all the stuff I want to do in Linux I can do in Android lol Also since I've been at my parents all week since I've figured this out I don't have my Bluetooth keyboard which has a trackpad, which would make navigation far easier than controlling the cursor with the touchscreen. Since I have it working now with LXDE I may try to install KDE on it and then install virt-manager as an easy GUI way for me to control my KVMs since doing it via SSH is kind of a pain in the a$$ and the only Android app just allows you to start and stop your domains.
If you are actually ballsy enough to pop the screen off and flip the dev switch on yours you'd probably be praised far and wide since no one has done it yet hahaha
Sent from my Pixel C using Tapatalk

brando56894 said:
Youre welcome! I did it just for the hell of it, haven't really used it much since I got it working. A native install would be much better, I plan on seeing if I can get it to connect to a local X server, VNC works but Ive always found it to be odd when controlling the cursor. I always install Linux on my Android devices just because I can, once I have it working I'm like "now what can I use it for?" and I always come to the same conclusion, pretty much all the stuff I want to do in Linux I can do in Android lol Also since I've been at my parents all week since I've figured this out I don't have my Bluetooth keyboard which has a trackpad, which would make navigation far easier than controlling the cursor with the touchscreen. Since I have it working now with LXDE I may try to install KDE on it and then install virt-manager as an easy GUI way for me to control my KVMs since doing it via SSH is kind of a pain in the a$$ and the only Android app just allows you to start and stop your domains.
If you are actually ballsy enough to pop the screen off and flip the dev switch on yours you'd probably be praised far and wide since no one has done it yet hahaha
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I've only seen one paywalled teardown so far in some brief searching to give any hints / clues. After seeing cheep5k8's posts my interest has peaked and I am digging your posts as well. I need to run through the chromium os git and doc stuffs first before I fire up my heat gun and spudgers though...

Hi !
Me too i'm interessed on a linux instalation for my "ryu"
...Pretty interessed on ubuntu touch : the Pixel C seems to be the perfect item for the distro to combine tablet and pc in one.
Sadly i'm not a developper, but i hope somebody will think like me ^^

will this work with ARM64 Fedora GNU/Linux? or are there special instructions for that?

I have been working on this, please see http://forum.xda-developers.com/pix...ux-pixel-c-running-ubuntu-xenial-lxc-t3410655 if you want to run ubuntu xenial on pixel C

kxra said:
will this work with ARM64 Fedora GNU/Linux? or are there special instructions for that?
Click to expand...
Click to collapse
I was just using whatever distros were provided by Linux Deploy, half of them don't work anyway, for example Arch. I was only successful with Ubuntu IIRC.
Sent from my Nexus 6 using Tapatalk

For those who are interested :
https://www.youtube.com/watch?v=4B8unHrbZK4
Weston and XWayland are running quite well on Pixel C (without acceleration until now)
I will try to publish something quite soon (there are still stabilities issues)