yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] robertogl:
Well, thanks and sorry for that, i didn't imagine something like that. If this happens again, check the errors before doing such number of screenshot: they are always the same. So, try this. It seems that Google change something on Nexus Player...
[Xposed Framework Modules] GabbyWC:
Ha ha, I wish I had realized that earlier but at least I can feel relieved about knowing that I won't need as many screenshots for upcoming testing. [MENTION=613602]robertogl[/MENTION], I installed your test2 version and rebooted but there are still no forced 3 dot menus showing up yet. I attached screenshots of the first 3 pages from the Xposed log this time around which I think should be enough.

Google definitely changed something in the Nexus Player code that affected menus starting with Android 5.1. The Android 5.0 software builds for this device (LRX21M and LRX21V) allowed the 3 dot menus in all apps. One possible explanation for the change was discussed at http://xdaforums.com/showpost.php?p=59786949&postcount=3. There are some Android apps (such as Google Chrome and DroidMote server by [MENTION=1469500]zulu99[/MENTION]) that have 3 dot menus in Android TV 5.1 and higher but those apps had to be updated by their developers to maintain that functionality. These changes are not likely to happen with all sideloaded apps that were not designed for Android TV so that's where your module can really help out if it becomes fully compatible with the Nexus Player.
[Xposed Framework Modules] robertogl:
I will need some time to work on it. I don't know even if it will be possibile...

I'm busy this weeks so don't expect a fix soon...
[Xposed Framework Modules] GabbyWC:
Okay, that's understandable. I hope that it is possible to fix so whenever you have time to continue development on this project, just notify me if you need further testing. Thanks.
[Xposed Framework Modules] kurtextrem:
May I ask what's different to the 3dot menu module?
[Xposed Framework Modules] robertogl:
That module changes the navbar size (or something similar). It isn't an elegant solution if you only want the 3 dots menu. Also, that doesn't work on some apps (like Samsung system apps) and i don't know if it works on all versions of Android.
[Xposed Framework Modules] robertogl:
If you are still interested, could you please upload yours 'framework.jar', 'framework.odex', 'framework-res.apk' from '\system\framework'? Thanks.
[Xposed Framework Modules] GabbyWC:
Hey, [MENTION=613602]robertogl[/MENTION], of course I'm still interested. I found the framework.jar and framework-res.apk in that folder but there's no framework.odex in there. There's an x86 folder in there which contains .odex files but no framework.odex. Do you still want me to upload 2 out of the 3 files you asked for?
[Xposed Framework Modules] robertogl:
Yes, please.
[Xposed Framework Modules] GabbyWC:
Here you go, as requested. These files are from my Nexus Player running Android 5.1.1 Build LMY48N. A developer on these forums, [MENTION=1469500]zulu99[/MENTION], recently told me that in order to make apps display the 3 dots menu on Android TV with Android 5.1 or higher, the apps have to use the toolbar instead of the actionbar. I don't know if that advice helps you with your module but I thought I should mention it here, just in case.
[Xposed Framework Modules] robertogl:
Well, have you 'framework-res.odex'?
[Xposed Framework Modules] GabbyWC:
There's no framework-res.odex file on this device either. I did a search of the entire /system directory using ES File Explorer (which has root access and shows hidden files and folders) but no file by that name was found.
[Xposed Framework Modules] robertogl:
Have you 'framework2.jar'?
[Xposed Framework Modules] GabbyWC:
There is no framework2.jar file on this device either.
[Xposed Framework Modules] GabbyWC:
Has there been any progress since we last spoke about the Nexus Player / Android TV support, [MENTION=613602]robertogl[/MENTION]?
[Xposed Framework Modules] robertogl:
Nope, sorry. I don't know what Google has changed here... :(
[Xposed Framework Modules] GabbyWC:
It's okay. I appreciate that you tried. I guess users will just have to hope for more apps to be developed with proper toolbar (instead of actionbar) support in order to display their full menus in Android TV.
[Xposed Framework Modules] Hung0702:
Unfortunately doesn't work on 6.0.1 :(

I'd been holding off on updating from 4.4.4 since I'm extremely doesn't on various Xposed mods for workflow. Just got a N6 and decided if I couldn't get 4.4.4, I might as well update to 6 and hope all my mods work. Capability is about 50/50. Marshmallow is great, but updating is never without its sacrifices. Goodbye 3-for menu convenience :crying:
[Xposed Framework Modules] robertogl:
I don't have marshmallow yet so I can't try, sorry...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] droidmark:
I have a Moto X Pure which still has 3 dot menu but just got a Galaxy S7 Edge which does not. I was really hoping Xposed with this module would help but I guess I should have read to the end of the thread before installing!

Have you had the chance to do any work with Marshmallow yet?
[Xposed Framework Modules] robertogl:
Yes, i'm using with marshmallow without problem :)
[Xposed Framework Modules] droidmark:
That's good news, although it's not working for me. This is the first device (S7 Edge) I've ever installed Xposed on, and it was just to use this one module. But I'm not seeing any 3-dot menus in any apps.

Is there some information I can provide that would help you troubleshoot it? Thanks!
[Xposed Framework Modules] robertogl:
You could give me xposed log, but I think that you should see the 3dots without any module, on S7 edge. Does it have a menu button?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] droidmark:
No, there is no menu button and long press of the recent apps button does split screen.
[Xposed Framework Modules] robertogl:
You should have an option to get into the menu. How every person without root is doing?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] droidmark:
Well, if you google Galaxy S7 3 dot menu you'll see that people are very frustrated about it!

I think some newer apps will work with long press of the back button or recent apps button, and some provide their own menu button, but for many apps there is no way to access the menu.

The only other workaround I have found is to go to Settings → Accessibility → Dexterity and Interaction → and turn on Assistant Menu. This will add a floating button to the screen that you can press to reveal a menu containing the old Menu button. But this floating menu is not an elegant solution.
[Xposed Framework Modules] robertogl:
Amazing, I didn't believe it could happen... Well, I don't know if my module can help, send me xposed log and we could try.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] droidmark:
OK, error.log attached. Thanks.
[Xposed Framework Modules] robertogl:
Nothing wrong here.

I've to say that sometimes the module doesn't work even on my device, but a reboot always fixed that. I don't know what is Samsung doing with their roms...
[Xposed Framework Modules] droidmark:
Well that's disappointing! Thanks for taking a look.
[Xposed Framework Modules] saleem121:
I install it , every thing works perfectly except contact " phone app " , it's overlap the form , and the clock app , see the attached photo ,,,, please anyone can help ?
[Xposed Framework Modules] seventieslord:
I need help in a big way! I just installed this module and after enabling it, I rebooted. Upon rebooting, I get a popup loop of "unfortunately, system UI has stopped."

This happens even in safe mode. I know that it is because I installed this module, because it's the only thing I did that would have had any effect like this.

I have messed up my phone this way before, and typically, these popup loops can be overcome by hitting ok while still navigating through and doing what you need to do in between. but in this case, the only thing that comes up is my edge menu, and the apps in the edge won't open when I click on them. I'm stuck.

I think what I need is a way to uninstall this module (or disable xposed) without booting.
[Xposed Framework Modules] robertogl:
You can disable xposed from recovery. There is an empty file to create, you can find the name googling it (I don't remember now).

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] DarkSJ1998:
Is it compatible with Xposed for Android 7.1.1?
[Xposed Framework Modules] robertogl:
I'm not sure, in not using the module anymore. You can try.
[Xperia Z3 Compact Original Android Development] someone755:
Device page on the TWRP website:

Mirror 1

There is no Mirror 2.

Due to the way Sony devices function, you will need to have an unlocked bootloader.

Your options, as far as ROMs go, are the following:

Any ROM with this commit

OR just use the new bootloader (with a proper recovery partition)

All credit goes to the TWRP team. I just annoyed the fools until they built the recovery.
[Xperia Z3 Compact Original Android Development] jug6ernaut:
Awesome! Very glad to see this.
[Xperia Z3 Compact Original Android Development] omnomnomkimiiee:
After flashing through fastboot, its impossible for me to boot into recovery, my phone stays stuck on the Sony screen with the pink/orange led.

Running resurrection remix and m5 kernel, theme has been updated for 2.8.7, previously was on 2.6.0
[Xperia Z3 Compact Original Android Development] rich2007:
Can this be install on LB?
[Xperia Z3 Compact Original Android Development] funiewski:
it should work with andropluskernel, not with stock
[Xperia Z3 Compact Original Android Development] someone755:
Works fine here. Did you check the md5 before installing? Does it work without the theme?

You need a custom boot image to boot into it (since our bootloaders don't really support a separate recovery partition, and we rely on a boot.img script to boot into one), which means you'd have to unlock the bootloader.

On this note, if anyone can provide me with stock boot images, I'll try and keep them up-to-date with the extract_elf_ramdisk utility, so that users on stock may still boot into TWRP if they don't opt for the AndroPlus kernel.
[Xperia Z3 Compact Original Android Development] pityu100:
Hello everyone,

Flashed this with "fastboot flash recovery", still getting the cm12.1 recovery.

BL unlocked, USB debugging enabled, CM 12.1 installed.

Anyone have a solution?

Thanks

Edit:

tried the twrp manager, no Z3C here, aswell the dd method, nothing changed.
[Xperia Z3 Compact Original Android Development] GuestK00283:
Same here, there is no Z3C in the list on TWRP Manager, and the 'dd' method leaves an unusable recovery (stuck on orange led). I'm happy with official TWRP support, but do you guys even test your stuff before releasing it.....? The steps with TWRP manager app don't even exist (there is no 'advanced' to tap).
[Xperia Z3 Compact Original Android Development] pityu100:
Flashed twrp.img as boot: fastboot flash boot twrp.img. -> TWRP starts every time i power on the phone. Flashed CM12.1 from this state, and TWRP got overwrited again with CM12.1 recovery. /sigh

Is the CM kernel counts as "Any custom kernel" ?
[Xperia Z3 Compact Original Android Development] someone755:
Thanks both of you for reporting your issues. Your reports sparked an investigation, and we were able to identify several issues that have thus far been overlooked (for whatever reason).

The "stuff" was tested before it was released, yes, but we're now facing limitations in the form of unmerged patches to the CM device trees. The issues should have been resolved several years ago, but instead they are now wreaking havoc on Sony msm8974 recovery setups. I've gotten some of the elite TWRP and CM people on this, as well as smaller fellow rhine and shinano developers (though Myself5 and oshomun could hardly be classified as small nowadays).

I personally have already uploaded four changes to the CM gerrit (that should have been applied years ago); One of them got denied (though is now being discussed for the near future (possibly as soon as cm-13.0); the result of that discussion is, among others, that the Cyanogen Recovery is now available for download alongside the ROM zip over at https://download.cyanogenmod.org/?device=z3c ), two are still pending any input whatsoever, and the last one was promised a merge, but the device maintainers have gone quiet, at least on the outside.

(If you wish, you can view the patches and their progress at their links: patch1, patch2, patch3, patch4, patch5.)

However, both teams are also having issues with other matters (such as Z3 not building, or adding new features to TWRP), and there is also the fact that school starts around this time of year (which impacts both the younger developers as well as those who already have children).

To conclude, there really isn't a unified guide I can give you to get to TWRP. It works, and you can use it if you have the correct setup. However achieving that setup is not a simple walkthrough away, and it would differ ever so slightly for every person's preferences, not to mention it would be overwritten with each new ROM update.

Such is the state of affairs at this point in time. This may or may not change, but be assured that everything we can do about this, we will do.

EDIT: A quick note that some ROMs may already include fixes for these issues. I don't know which those ROMs could be, so I won't go into listing them, but the possibility exists.
[Xperia Z3 Compact Original Android Development] pityu100:
someone755,

thanks for your quick reply and your investigation.

Hope for the best, but time will tell.

Thanks again :)
[Xperia Z3 Compact Original Android Development] GuestK00283:
Someone, here is a build that actually works, maybe you guys can base on that?: http://xdaforums.com/z3-compact/development/recovery-twrp-2-8-6-0-fota-recovery-t3093537

I'm on Cyanogen 12.1 nightlies with M5 (=Cyanogen-based) kernel btw.
[Xperia Z3 Compact Original Android Development] someone755:
The thing is that if you flash a cm-12.1 boot image (completely stock, without kernel or ramdisk modifications that M5 or Kernel12 perform), it won't work. It works with some setups, but not with others, and is, for some reason, very specific -- to get rid of these errors, CyanogenMod would have to (at the very least) accept my changes.

If you feel like you have to try this for yourself, here's a link to the boot image: https://www.androidfilehost.com/?fid=24052804347797955 Getting out of the mess created once you flash this can be a pickle though, so unless you have a boot image on hand with which you know TWRP works, do not flash the file I linked.

I've had somebody say it started working for him after flashing r_02 of Kernel12, though sadly I'm not very sure that's a permanent solution (it is, however, a working temporary one).

Unfortunately the man who was supposed to review the changes is on leave from development, so waiting is the only option available right now (unless we come up with a zip file to flash after each nightly install, but that would only increase the chaos of this already-confusing situation).
[Xperia Z3 Compact Original Android Development] jenkins-84:
Had no issues with my 2.8.7.0 twrp built into my ROMs boot.img been working with no issues so far
[Xperia Z3 Compact Original Android Development] someone755:
The goal of FOTA recoveries was to let the user boot into a recovery regardless of what recovery is in the boot image. If you flash a CM nightly over your setup, you won't be able to get to TWRP again unless you perform various modifications to the CM boot image.

Packing recovery inside boot is what's causing all these issues in the first place, so doing what you suggest would be a step forward, but two steps back as well.
[Xperia Z3 Compact Original Android Development] jenkins-84:
Yeah maybe but I don't care to much for CM based ROMs was for people using slimlp based mainly
[Xperia Z3 Compact Original Android Development] someone755:
That's all fine and dandy until you realize most people are sticking with CM (for some unexplainable reason). Other ROM gerrits are much more likely to have already merged the needed changes (and are much more lenient and open when it comes to accepting new changes in general, and all this is the only reason this waiting game is now on).
[Xperia Z3 Compact Original Android Development] jenkins-84:
Yeah but I don't wait on slim or use its device trees etc I build for my own and use commits I want, I don't really care what people use or do. I build ROMs for myself and a friend. I just happened to share a ROM that I don't care if people use or not. If I'm happy with what I build and use then that's all I care about
[Xperia Z3 Compact Original Android Development] GuestK00283:
You do realize TWRP is meant to work for everyone, not just for 'me and my bros'?

On topic:

Someone, that FOTA TWRP I linked does (or at the very least did, I've been on M5 Kernel for a few weeks now) work with a stock Cyanogenmod boot image. Before M5 kernel I could already reach TWRP. I really think it worth a closer look to see what that guy did because it works/worked for some reason..

My full sequence (the first time anyway):

Unlock Bootloader

Unpack boot.img from Cyanogenmod nightly zip

Flash boot.img in fastboot

Boot to Cyanogenrecovery

Wipe

Flash Cyanogenmod in recovery

Boot Cyanogenmod, Setup Wizard yadda yadda

Shut down and go to fastboot

Flash FOTA TWRP from said link

Test FOTA TWRP, Be happy

----Few days later----

Flash M5 through FOTA TWRP
[Xperia Z3 Compact Original Android Development] someone755:
Nope, won't work for me, it just boots straight to CNR. Tried multiple times.

I mean if you can get it working, that's great and all, but I need to figure out why others cannot.

On another note, this was discussed last night with the men of TWRP (and some of their close omnirom friends). A great thing to consider about recoveries is the future of Sony kernels; we are getting closer to switching to 3.10 with each day, and recoveries built with a 3.4 kernel won't work on a 3.10 kernel (simply because of the way recoveries are handled, with the whole ramdisk extraction thing).

That said, the recovery in boot is going to remain the main and preferred way of dealing with recoveries (though the option for a fota kernel will still exist). There were some ideas thrown around, including some good ones on how we could bypass certain issues, but the general consensus was that we'd need to wage war on CM to get some changes in, and we're definitely not doing that (because Cyanogen, the company, has an effect on CyanogenMod, the ROM).

So in short, if you want a recovery thag really works, you'll need one in your boot image. Meaning you'll have to find a ROM with TWRP inside.

I don't know what happens with the official state of TWRP for z3c after this. You can get it to work with the right setup, so it's probably going to stay. How long, I don't know, and I'm honestly afraid of what the future might bring for Sony devices (because anything but a new bootloader is probably going to just make things worse).
[Xperia Z3 Compact Original Android Development] funiewski:
You don't think the changes in bootloader like in z1c will come for z3c?there is twrp compiled for it which works nicely with z1c
[Xperia Z3 Compact Original Android Development] someone755:
When that might arrive, we'll never know.

Z3 got the new bootloader with the leaked Sony concept. Z3C and Z2 are still in the dust.
[Xperia Z3 Compact Original Android Development] laufersteppenwolf:
Alright guys, thread cleaned.

Please remember, this is a development thread, so non development related posts do not belong in here, especially when it comes to fighting. XDA is no place at all for fighting ;)
[Xperia Z3 Compact Original Android Development] DanielMalmgren:
Hi.

When I look in TWRP Manager today there actually IS a choice for z3c in the device dropdown, which is a step in the right direction. However when I click "Recovery Version to Install" the app force closes. Is this wip?

/Daniel
[Xperia Z3 Compact Original Android Development] someone755:
I tried it just now, and it doesn't FC on my end, but it also doesn't bring up any options after tapping "RecoveryVersion to Install".

Quite honestly I don't know how or why the TWRP app does whatever it does. I've had issues with it on several other devices (including Nexus). But people say it works, so there's that. If you want to report it your best bet is contacting someone higher up in the TWRP team (or posting a log of the issue on the TWRP IRC).

The last good TWRP installer was, as far as I'm concerned, GooManager, but that one stopped working after goo.im was shut down...
[Xperia Z3 Compact Original Android Development] apollus:
Looking good!
[Xperia Z3 Compact Original Android Development] :
True that. It still amazes me that TW advises TWRP Manager use when they know its rife with issues. Any message from the TWRP or CM team about progress, btw?
[Xperia Z3 Compact Original Android Development] someone755:
Like I said a few posts ago, there are two main factors to consider. One are the limitations presented by the buffer extract_elf_ramdisk can work with -- as TWRP grew, that buffer has become too small (leading to such workarounds as compressing the recovery with LZMA, as with the MultiROM TWRP published by Myself5). A crucial piece of information, however, is that CyanogenMod is the most widely used ROM on the z3c (whether you like it or not) and most ROMs are based directly off it meaning that if we want any changes to get to the majority of z3c users we have to push them through CyanogenMod (which has, for reasons unknown, been proven difficult to achieve). Other ROMs have a much easier time accepting new people and new changes. The TWRP maintainers are getting tired of this and they pretty much agree that pushing any changes to CM would require a war. One that we couldn't win even if we were dumb enough to participate. In other words, seek out a ROM with these patches in already, if you want to use FOTA.

The other issue comes in the form of an all-new kernel base approaching -- the 3.10 kernel by Sony. If a recovery is built using a 3.4 kernel, it cannot, due to header mismatches, be booted with a 3.10 kernel, and since many ROMs are considering a move to 3.10, this is a very big problem indeed, making extract_elf_ramdisk obsolete in that respect. Leaving only one solution left, and that is the recovery-in-boot setup. Again though, CM will not allow for anything but CM recovery being used in their builds, so if you want a TWRP-in-boot you need a different ROM.

In my opinion, the only thing that can save us now is a new bootloader, but who knows how the CM team will react to that.
[Xperia Z3 Compact Original Android Development] :
Will custom CM kernels (3.10, when that comes) like the kernel by M5 support booting of FOTA like I am doing right now?
[Xperia Z3 Compact Original Android Development] someone755:
That's harder to give you an answer to than you might think. Especially since we don't know when the new bootloaders will get here. (And if anyone will do anything about it.)

My guess? Probably, but that's when you'll learn the hard way that this whole FOTA hack isn't very stable when it comes to end-users with the potential header mismatches etc. The way Myself5 handles the ramdisk during installing his kernel, it's really up to him.