3 dots for menu won't go away after lollipop topic

The three menu dots are showing up in apps that don't have it built in even though I have my home button set to open the menu on a long press. It's especially annoying now because it's an overlay that covers screen elements. Any ideas on how to fix it?

one global invite to give away topic

comment or thank, invite to be randomly given. Also, only apply ifyou have paypal ready :)

Stay Away From Multirom Systems topic

Multiroms are based on kexec kernel patch. Apart from being used for purposes it was NOT designed for, its implementation on Android creates glaring security holes. In addition, those roms are developed by those who have absolutely no concept of device security and most of the time don't know what they are doing. In some cases multiroms are "developed" by 16 year olds. Not that I have anything against 16 year olds, but you are not going to place teenagers in charge of OS security. To show you how dumb some of those "devs" are, here is an excerpt from boiler plate explanation regarding security:

"All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it."

This folder is unaccessible in Android?!. Well, yes, if your Android is on system partition as in regular roms, but your Android is on SD card, the same card you claim is inaccessible. LOL.

Multiroms are based on Kexec, a linux kernel patch, which allows to put another kernel into ram and have a different operating system on your device.

First of, Kexec was created for large systems where rebooting is a lengthy process and big headache, as opposed to 20-40 seconds that is needed to reboot a smartphone. Contrary to popular beliefs, kexec is not designed to have dual boot, such as Windows and Linux on the same system. The standard way is where your drives are partitioned and can have separate and independent operating systems with their own kernels.

Another myth is that kexec can go around locked bootloaders and allow to have custom roms on those devices. Nothing can be further from the truth. Kexec has to be enabled in the original kernel which cannot be modified on locked bootloaders. Nor can you create a module outside of the original kernel that can work. By the way, to have a custom rom on locked bootloaders is possible without multiroms and it was successfully done on several devices including Xperia S and ION: just head for the development thread and see CM10, Slimbean, AOKP and Pacrom all for locked bootloaders. It works without multiroms.

Third and the main one: multiroms run from SD cards, which are wide open on an active device whether encrypted or not. By the way, that is one of the reasons that Google, in whose mind privacy is priority number 100001, has restricted access to SD in Kitkat. Nothing could be easier to get malware on sd card while browsing and out of there, it can take control of the entire system. So, if your rom is running on SD card, you have no security, your device is fully open to the whole world.

A minor point. Since multiroms use TWRP recovery, what is the benefit of having multiroms (even if there was no security threat), as compared to having several roms backed up and restored as needed. For example, I have Dirty Unicorn as my main rom, but I also have Carbon and Beanstalk saved on SD card. If I am tired of Dirty Unicorn, I can go to TWRP and restore Carbon, then Beanstalk, then return to Dirty Unicorn. The time difference is 3 minutes it takes to restore a backed up rom. But unlike multiroms, my roms are reasonably secure.

Triangle away support for SM-N910H? topic

Does the triangle away app by chainfire support the Note4 SM-N910H?
I needed the app on my note2 which worked perfectly, the allshare dongle by Samsung wont connect on a rooted phone.
And i want to be able to use mine with my note4, might not root my note4 if this doesn't work!

Sent from my SM-N910H using XDA, powered by appyet.com

Screen input delay after moving away from face topic

Ok, so lately I've noticed when I've had to call a few numbers that need me to Press 1, 2, 3 etc on the dialpad that I can't do it right away. When I put the phone to my ear, as I would expect the screen switches itself off. When I pull the phone away from my face the screen comes on again immediately, but there's about a 5-7 second delay before I can actually press anything. In those seconds after the screen comes on, it wont accept any touch input whatsoever. It's not delayed, presses I make during those seconds just aren't registered at all, then suddenly it begins accepting input as normal. It isn't just number keys either, it's the entire screen, so I can't press End Call until nearly 10 seconds after I've actually pulled the phone away from my face, nor can I move the phone away and press the Speaker Phone button quickly.
This only happens when the screen comes on after being against my face though. If the screen is just turned off and I press the power button, or double tap to wake, it accepts input immediately, so I don't believe it's a hardware problem.

Currently running 4.4.4 rooted, image was made from stock and pre-rooted prior to being flashed onto the phone.
Has anyone else experienced this issue?

One INDIAN Invite to give away topic

Hello All,

I have One INDIAN invite to buy from Amazon India.
Already claimed it, thus having very less time to rush for the sale.

PM for getting it.
Pls dont sell it...
Kindly use it for self or family or friends.

Pls dont sell..

Regards

[Q] Region lock away fail topic

I have a samsung note 3 usa t-mobile n900t, i rooted the phone, downloaded chainfire’s region lock away and I continue to get the same error: the result of updating the modem was unexpected-can’t be sure if the patch worked or not! Rebooting and trying again sometimes fixes the problem……..I tried rebooting and running the program several times but nothing. Can anyone please help I really need to fix this. I am using a straighttalk sim for at&t. Hoping that someone:( can get back to me soon:
Michael