yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] chinarabbit:
but whats it even mean?

honestly, if you cant handle questions and answers, dont get on the internet.. it was created for no other reason than exchanging information, sharing knowledge, collaborating on projects, learning, and mentoring & helping others

if you are so sick and tired of all the questions, why dont you make a little secret password to your thread where you can work with a few other people on your massively intellectual brainiest project on earth.

or better yet, go use box.net or make your own site for yourself and the people you think get your little project enough to be worth your time or energy

ya, 20 years, and no, first time ever experiencing this particular problem.. I think its a google glitch, cause I dont know how a guy with this attitude ends up on the first page of the google search.

anyway, the last 5 posters have wasted more breath making excuses than anything..

wouldnt it have been easier to say, "hey, wrong thread, head over here, this is for one model of phone and one model of phone only. and nothing we've done or said here for 100 pages can possibly apply to anyone or anything else"

you want to talk about long winded.. how does one tiny problem for one model of one maker of phone run on for more than 100 pages anyway

you just cant be bothered to say anything nice to someone when you could try and make yourself feel smarter than you really are

dont waste more breath on me

go on with your 100 page thread about one single thing.. you are soooooo concise... and each of your words is just soooo very useful to behold.

you're a real treat
[Nexus 4 Original Android Development] xanthrax:
[MENTION=1416657]chinarabbit[/MENTION]

please stop all your non development posts right now right here !

one more post and you`ll be reported !
[Nexus 4 Original Android Development] prateek80:
Now, who is being rude and immature..? Can't you just let it go...? Is it that hard really..?

:eek:
[Nexus 4 Original Android Development] chinarabbit:
ok, sorry guys... I'm seeing the problem here

please allow me to contribute one last thing

When replying, dont include the entire text, then say something unrelated to what was posted

then your thread would be 5 pages long instead of 100

and people wouldnt mistakenly think there was useful information here

cheers
[Nexus 4 Original Android Development] karol1981:
I got otg y cable, my travel charger and everything working flawlessly, thank for your great work.

Wysłane z mojego Nexus 4 przy użyciu Tapatalk 4
[Nexus 4 Original Android Development] ziddey:
4.3: 2013.10.01 1652ET r186: [JWR] [JSS/JLS] Zipalign framework-res.apk

Also bumped force-fast-charge rate to 1.5A, inline with regular "AC" charge rate.
[Nexus 4 Original Android Development] Wis76:
Constant reboot after installing latest kernel (jvr). The phone seems to start fine up to the launcher but then hangs and reboot himself.

Solved reinstalling the previous one via recovery.

Nexus 4 unlocked and rooted (obviously).
[Nexus 4 Original Android Development] bmakk2055:
Yeah its doing the same thing on Franco Kernel!
[Nexus 4 Original Android Development] ziddey:
Thanks for the update. Here's r187:

4.3: 2013.10.01 1900ET r187: [JWR] [JSS/JLS]

edit: May or may not still be upstream issues with r187 JWR. Keep a prior version handy. Everything seems fine with JSS/JLS.

edit2: Here's r188:

4.3: 2013.10.01 1954ET r188: [JWR] [JSS/JLS]
[Nexus 4 Original Android Development] Wis76:
188 works flawlessly.

Thanks.

Haven't had time to flash the new 187.

TWRP is asking me to fix superuser permissions every time I install a new kernel. Is it supposed to do so? Fixing or not fixing does not change anything.
[Nexus 4 Original Android Development] ziddey:
I'm not sure what TWRP's mechanism is for detecting su. I get that message with Chainfire's SuperSU. If that's what you use, you could get his app to stay updated. I don't know how updated TWRP's su even is; I do remember people using older versions to try to root 4.3, only to come upon a disaster.

Either way, the patches are strictly for OTG support (well except for the CIFS module and an increase to the force-fast-charge rate) and would not cause this to happen. I imagine Franco's official kernel would have the same results.

That said, this seems more like a ROM-side "issue" anyway as I doubt TWRP would modify the ramdisk to add superuser access (semantics.. this seems more like a TWRP issue ;)).
[Nexus 4 Original Android Development] xanthrax:
SuperSU needs to be updated to the last version , no permissions needs to be fixed in recovery

Preferable via zip https://db.tt/IdffXJGk

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] Wis76:
Thank you very much.

Yes, I use Chainfire SU and I have the app to keep it updated.

I'm having a "msm_hsic_host" wakelock issue and at first I thought it was caused by a kernel update.

After some internet research about this problem and testing with older (Ziddey's) kernels I don't think it's a kernel problem (it should be Franco's problem, not yours, anyway ^__^) but some recurring coincidence is driving me to think that fixing permissions with TWRP has something to do with it, that's why I was asking infos about if the TWRP "fixing permission" behaviour is normal in the first place.

I don't know if what I'm addressing as a problem does actually make any sense, but it's not something to discuss here, so, never mind. ^__^

(And again, sorry for my english).
[Nexus 4 Original Android Development] ziddey:
Probably just a coincidence. Fixing permissions isn't something that needs to be done normally/regularly.
[Nexus 4 Original Android Development] bmakk2055:
I flashed the 188 and now my colors are like this. Anyone else?
[Nexus 4 Original Android Development] ziddey:
Screenshot turned out normal but from what I understand it's an issue with the latest cm nightly and custom kernels. I'm one nightly behind still so I can't comment yet.

Sent from my phone. Please forgive typos and brevity.
[Nexus 4 Original Android Development] Malnilion:
Apparently, CM switched to CAF video drivers for Nexus 4. Franco does not plan to rebase his kernel for CM, so if you want to compile based on the new CM code, I would definitely not complain lol
[Nexus 4 Original Android Development] ziddey:
I'm going to wait a little while to see what happens. I'm a CM user too for the time being.

As long as you use the old liboverlay.so (10/1 nightly), you'll be fine. You could add this to an existing addon.d script or create a new one. I made a copy of 50-cm.sh, and changed etc/hosts to lib/liboverlay.so. This way, every time CM is flashed, the old liboverlay.so is backed up and then restored.
[Nexus 4 Original Android Development] Noctophrenia:
It appears to me that there is varying levels of success, perhaps based on which ROM. I have mouse and keyboard working fine but cannot get any drives recognized.

I've tried Stickmount and it didn't change anything. I'm not committed to this ROM--is there a specific ROM that has had the most success? I see some saying CM10.2 nightlies, also PA3.99?

Could I be missing something in the mount process?
[Nexus 4 Original Android Development] :
I'm on PA 3.99 RC2 with zero failure rate.

Sent from my Nexus 4
[Nexus 4 Original Android Development] zman0900:
I can confirm that TWRP supports ext4 and exFat, which means it should also support ext3 and ext2. It also mounts ntfs, but read-only since that would need ntfs-3g.
[Nexus 4 Original Android Development] ziddey:
4.3: 2013.10.07 0115ET r189: [JWR] [JSS/JLS]

Maintenance release-- rebase to r189, which includes the kexec-hardboot patch for those who wish to use MultiROM.
[Nexus 4 Original Android Development] ziddey:
Nice, thanks for testing. I had a quick look a while ago at 2.6.0.0 and saw in etc/recovery.fstab:

/usb-otg vfat /dev/block/sda1 /dev/block/sda

So I assumed it would only support fat partitions.
[Nexus 4 Original Android Development] Reaper219:
+1 for the great work, Ziddey

I am on the CM 10.2 latest nightly and for some reasons the patch(v188) did not work at all, the USB drives weren't being recognized even though the phone was getting power. Picked up the older version(184) and it's all fine now. Though I can't get my 1TB HDD(NTFS) to work with it, cannot format the drive as it's nearly full and I don't have the means to make a backup so any workaround for that would be great.

Another thing is that, sometimes, the battery drains(very slowly) while I'm playing videos from the USB drives and the phone recharges really slow. And if I'm using a HDD(FAT) then the phone doesn't charge at all, which could be because the HDD takes a lot more power compared to the thumb drive. Is it supposed to be like that or not?

Again, thanks a lot for this mod, the 12 GB internal limit was a pain.
[Nexus 4 Original Android Development] ziddey:
Don't know what to tell you. The only change between r184 and r188 (other than upstream changes from Franco) was zipaligning framework-res.apk (didn't realize such a thing existed before).

I'm using usb storage practically full-time and haven't seen any issues.

As far as charge rate, host mode will trigger "ACA" charging, that is up to 1.5A less what any devices report as a maximum requirement. I haven't checked in a while to see if this data is still shown in kmsg (I've disabled verbose usb messages to cut down on log "spam" now that the mechanics are tested). To my knowledge, the max a device can request is 500mA (usb2 anyway), so if plugging in a single drive, it *should* still be able to pull up to 1A if it can be provided. It's been a long time since I've looked at that code, but I seem to remember a x2 multiplier for some reason (I always assumed I just misread it), in which case, it would limit charging to 500mA which could indeed not be enough when taxing the device.

Of course, in the event that sufficient power can't be provided, there's provisions to then limit charge rate, which could also be what's happening. Check the logs to see if there's any useful information available. Maybe I'll turn verbose usb messages on again.
[Nexus 4 Original Android Development] giebeka:
Hi, sorry for my English.

USB mouse and pendrive works fine for me but xbox controller is blinking (that 4 leds) every time. Need I drivers or something?

#Tapnięte z Nexusa 4
[Nexus 4 Original Android Development] Reaper219:
Okay. Any workaround for the NTFS bit, my main external HDD is NTFS, and I don't want to format it(it's full), the phone keeps on asking me to format the drive into a different file type.
[Nexus 4 Original Android Development] Polv89:
I can't read my USB on recovery, can someone tell me why?

Thank

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] codf4ther:
Your recovery comes with it's own kernel, so flashing this for your rom doesn't update the recovery kernel. Ziddey made a patch in the first post for patching the recovery kernel, but you need to apply it separately.
[Nexus 4 Original Android Development] Polv89:
I have flashed ziddey kernel..

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] Wis76:
Please read again codf4ther post.
[Nexus 4 Original Android Development] ziddey:
"Modules cifs.ko, ff-memless.ko, hid-dr.ko, hid-logitech.ko, and xpad.ko (/system/lib/modules). Manually insmod as needed or create an appropriate init.d script to load on boot. These are only required for certain gamepads. Refer here for more information."

xpad = xbox controller

may need ff-memless to load xpad. Refer to linked thread for more information.

"Stock Android only supports FAT for storage. NTFS/exFAT/ext4 partitions require the use of third party apps (CM now supports these partitions natively!). Exercise caution when using ntfs partitions, making sure to unmount before unplugging"

Read-only NTFS support is enabled in the kernel, but you'll have to manually mount or use an app like Stickmount. For RW access, you'd need to also get the appropriate ntfs-3g drivers. Search for the Stickmount thread for more information.
[Nexus 4 Original Android Development] punitthereddevil:
First of all I hope that ur using TWRP...coz other recoveries don't support OTG...

Next find the recovery.zip file from this thread and flash it via recovery...this replaces the recovery kernel too...flashing only the main kernel file replaces the kernel of the system...not the recovery...

------------------------------------------------------

| NEXUS 4

| SLIMBEAN 4.3 BUILD 1 OFFICIAL

| ZIDDEY'S OTG KERNEL r184

| TWRP 2.6.3.0

---------- Post added at 08:10 AM ---------- Previous post was at 07:55 AM ----------

I dunno if this has been reported before...

I have a couple of recovery files that are .IMG...but I'm unable to copy them to my flash drive...all other file formats have no problems...

I zipped the .IMGs and then was able to copy them...but no files in the .IMG form were able to get copied...

------------------------------------------------------

| NEXUS 4

| SLIMBEAN 4.3 BUILD 1 OFFICIAL

| ZIDDEY'S OTG KERNEL r184

| TWRP 2.6.3.0
[Nexus 4 Original Android Development] prateek80:
Can you add controller support in the kernel itself ??
[Nexus 4 Original Android Development] ziddey:
It's not something that the majority of OTG users will ever use, so there's no reason to "bloat" up the kernel, even if it'd realistically have practically no impact on memory/performance. Just create an init.d script to modprobe/insmod it on boot if it's a bother. It'll be effectively the same as building it into the kernel. Modprobe used to not be available, but more recent busyboxes seem to have it now.
[Nexus 4 Original Android Development] SpasilliumNexus:
Thank you for this. I've been on and off trying to figure this out myself, and seeing that the modules are already in your zip, I followed the instructions starting at "So open terminal" from the thread link you posted , along with finding this thread, and using the attachments provided has my wireless Xbox 360 Controller with a Xbox 360 Wireless Gaming Receiver working fine with system emulator apps after re-mapping the controls.

My controller does the same thing but still works after doing my above post.
[Nexus 4 Original Android Development] prateek80:
What about logitech F310 and other gamepad ?? Can they also work with same procedure..?
[Nexus 4 Original Android Development] fastolfi:
N4 AOSPA Ziddey : OTG DONT WORK

Nexus 4.

AOSPA 3.99RC2

Kernel Ziddey R189

Otg apparently ok, but if i insert a usb pendrive (with Y cable) DONT WORK! (es file explorer EMPTY, root explorer EMPTY, stickymount don't mount any)

Help me!!!!! thnks, Francesco
[Nexus 4 Original Android Development] ziddey:
4.3: 2013.10.09 2148ET r190: [JWR] [JSS/JLS] Re-enable USB debug messages
[Nexus 4 Original Android Development] bombadier:
Looking for some help with a strange problem,after flashing the r190 JWR zip my extented power menu (comes with the ROM) the expanded desktop has a strange icon/chrome icon,I had a look in your zip but cannot see what is causing this,I reflashed my ROM update and the icon reverts to normal,any ideas?
[Nexus 4 Original Android Development] ziddey:
Possibly a ramdisk incompatibility issue-- would occur with Franco's kernel as well.
[Nexus 4 Original Android Development] Toyotaspeed:
I have flashed Matr1x Kernel 11.0 and Paranoid Android 3.99RC1. I should be able to plug in a USB flash drive with a y-cable without any problems, right?
[Nexus 4 Original Android Development] ziddey:
Nope

Sent from my phone. Please forgive typos and brevity.
[Nexus 4 Original Android Development] Toyotaspeed:
Matr1x 11.0 feature log says it supports ziddey's USB OTG. Is my only option to run ziddey's OTG kernel?
[Nexus 4 Original Android Development] ziddey:
4.3: 2013.10.11 1730ET r191: [JWR] [JSS/JLS]
[Nexus 4 Original Android Development] parkedraccoon:
Having problem with this update - control of state manually via script is disabled?

[
[Nexus 4 Original Android Development] ziddey:
Manual control was not implemented for any 4.3 kernels since there really isn't a point. Any reason you want this?

Sent from my phone. Please forgive typos and brevity.
[Nexus 4 Original Android Development] parkedraccoon:
Externally powered USB hubs.
[Nexus 4 Original Android Development] ziddey:
Hubs should trigger host mode the same as a device. If it's not sending power upstream to the phone, manually toggling host mode shouldn't work either. I just re-tested my hub and it's working fine, regardless of whether any devices are attached to it. If it's really something that requires manual host mode, I'd be really curious to see the relevant dmesg! Maybe I overlooked something when "streamlining" for 4.3. I'll add manual mode again in a future release, although really it's only good for debugging purposes.

----

In other news, I just realized that there's an issue with TWRP and the zipalign binary, resulting in USB Storage not showing up in settings->storage. Will address this for the next release.

As well, it looks like a good amount of you guys are using CM or a derivative and have been affected by some recent CAF commits. A temporary solution has been to replace liboverlay.so with an earlier version. However, I've found that dmesg is constantly flooded with errors as a result. I didn't notice any drastic changes in performance / battery life as a result, but that's not something I'm thrilled with...

So for the time being, I've made some test builds with the two YCBYCR commits (from Oct 1) cherry-picked.

4.3: 2013.10.13 0401ET r191: [JWR] [JSS/JLS]

Again, these have the two relevant commits cherry-picked and will require the recent liboverlay.so. Users of ROMs other than CM or its derivatives need not apply.

It's just a temporary solution, but I am curious about how many derivatives are affected by this. If it's all JLS builds (non JLS/JWR hybrids), it may be worth including it for that branch. Nonetheless, I've made a JWR version as well since there's a lot of hybrid users as well (namely PA and Slimbean from what I understand).

This is just a personal test build, but I figured a lot of you guys are in the same boat right now.

AGAIN, THIS IS ONLY FOR THOSE WHO WOULD OTHERWISE NEED TO REVERT TO AN EARLIER LIBOVERLAY.SO.
[Nexus 4 Original Android Development] Malnilion:
Thanks, ziddey, it's working well for me so far.
[Nexus 4 Original Android Development] parkedraccoon:
I used to be able to use the manual toggle with this same USB hub before to make it work (before I got my y cable, it was the only way for me to use otg)

Plug in:

Unplug:

Whole setup:
[Nexus 4 Original Android Development] keyra74:
not working here, all i get is a black screen after boot finish

back to october 11

i'll logcat later if i have time
[Nexus 4 Original Android Development] ziddey:
Not really much relevant information there. Looks like you're not on r190 or above, which have usb debug messages re-enabled. The adb lines imply that it probably went into client mode (as opposed to wall charger or Apple-compatible charger/host mode). I've never seen that happen before, but manual host mode would indeed be the only way (short of figuring out how to trigger based on the ID pin like it's supposed to). Will add it back.

Did you reapply the new liboverlay.so? Account for the addon.d backup script if one was used?

edit: Judging by your post history, I'm guessing this does not apply to you, hence your issues.

-------

I just realized a lot of you guys' usage patterns are likely very different from mine. Does anyone have any complaints with the charge rate? If so, I'd be curious what your dmesg logs are showing. If it's intentionally restricting current needlessly based on reported usb device current draw, I could just keep the charger type as proprietary (1.5A). It looks like there's other code in place that can automatically restrict current draw if it detects it can't be provided. However, this still runs the risk of potentially starving a usb device of power momentarily (and for it to drop out). Either way, the current method (ha ha ha) docks from 1.5A regardless of the actual power source, which can be pretty pointless anyway, so... let's give doing away with docking a shot in the next build. /end ramble

Also figured out the issue with zipalign.
[Nexus 4 Original Android Development] keyra74:
that's why :D

i should have read before flashing

anyway i have nothing to complain about it works like a charm
[Nexus 4 Original Android Development] gustavobaezz:
For me it is working almost perfect with latest cm nightly.

The only thing worse on this update is that miracast works a bit crappy.

With r183 miracast went perfect but update by update it is getting worse and worse...it must be changes under governors made by Franco.

Multimedia server must have total priority to make miracast work flawless.

But always ...thanks Ziddey for your great work...I can not understand why other kernells doesnt incluye your otg and joystick support.
[Nexus 4 Original Android Development] Sacob:
can i use Multi ROM with this kernel?
[Nexus 4 Original Android Development] karol1981:
No u can't :-\

Wysłane z mojego Nexus 4
[Nexus 4 Original Android Development] ziddey:
and you say that, why?
[Nexus 4 Original Android Development] Sacob:
i think the original one works with multi rom
[Nexus 4 Original Android Development] karol1981:
I am writing this because I checked it on version JB 4.2.2 and did not work.

or maybe I did something wrong.

Ok it's working :) i had an old version multirom:)
[Nexus 4 Original Android Development] feeq13:
Hello, can u help me. Im using aospa rc2,cwm recovery. When i connect my phone to utg n usb hub, it cant read anything just toggling charge n discharge. Can u please guide me from the start.
[Nexus 4 Original Android Development] karol1981:
Read first post , and u will know what to do.
[Nexus 4 Original Android Development] ziddey:
I know people have long been requesting a stock JWR build. I finally got around to making one, but have not tested it.

ziddey-otg-STOCK-10171957.zip

It's compiled with arm-eabi-4.6 toolchain, mako_defconfig, and uses stock ramdisk (which will be patched accordingly during flash). Excepting OTG mods, the kernel should be bone-stock.

This is for stock roms only. No module support.

Uses two new commits for manual/automatic otg: https://github.com/ziddey/mako/commits/nightlies-4.3-JSS

Make sure you have some sort of backup in case something goes wrong.
[Nexus 4 Original Android Development] muyoso:
nevermind, figured it out.
[Nexus 4 Original Android Development] ziddey:
"MAKE SURE TO DOWNLOAD THE RIGHT VERSION FOR YOUR ROM."

Flash JWR...
[Nexus 4 Original Android Development] giebeka:
Ziddney can you make a build which is supporting CAF ROMS, like pacman? Your build from 13th of October isn't working since pac 091013 build.

Sorry for my English and thanks in advance.

#Tapnięte z Nexusa 4
[Nexus 4 Original Android Development] gustavobaezz:
Try this:

4.3: 2013.10.13 0401ET r191: [JWR] [JSS/JLS] from http://xdaforums.com/showthread.php?t=2181820&page=113

Search the last ziddey post on that page.

It is working perfectly.

Sorry for not to make a link... I am with the mobil and I am lazy
[Nexus 4 Original Android Development] giebeka:
Like I said this build from 13th of Oct is not working since PAC Nightly 101013.
[Nexus 4 Original Android Development] gustavobaezz:
You are not understanding me...that is an experimental kernel supporting caf drivers. It is not the normal ziddey's kernel different from what you can download on the first post.

I'm using latest cm nightly with that.
[Nexus 4 Original Android Development] giebeka:
I'm understanding you. I use this kernel for 9th Oct Pac (PAC has CAF drivers since 5th build) so I perfecty using this until 10th nightly (with this kernel gets bootloop).

Again sorry for my english.
[Nexus 4 Original Android Development] gustavobaezz:
Ok...then I can't help you.Sorry for misundertanding you.