yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] taqi110:
Hello,

I found this app Confirm2Proceed for Iphone which ask for permission before sending any message or making calls. But this is for Iphone is there any similar app for Android ?

To be precise I need an app like this for WhatsApp

Thanks.
[General Questions and Answers] taqi110:
Bump
[Nexus 6 Q&A, Help & Troubleshooting] pure1water:
Hey guys just a quick question,

as the title says,

What's the best rom for battery life, smoothness and updates?

I'm on Ressurection remix right now,

But I interested on Pure nexus project too.

Which one is better?

Or are there any other roms to recommend that are better than those?

Thanks!
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
no such thing as best rom for battery life. battery life is determined by your use, your setup, your choice of apps inatalled, and your signal quality.
[Nexus 6 Q&A, Help & Troubleshooting] seabro01:
Pure Nexus for smoothness and updates. Battery life can be great on Pure Nexus depending on usage. I'm getting 6-7 hrs SOT with PN and ElementalX.
[Galaxy Note 4 Q&A, Help & Troubleshooting] willone2:
[deleted]
[Galaxy Note 4 Q&A, Help & Troubleshooting] LTE-X:
VoLTE implementation is unique for every carrier. You need to flash Three UK firmware on your N910F Note 4 device in order use voLTE on their network.
[Galaxy Note 4 Q&A, Help & Troubleshooting] willone2:
[Deleted]
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] BeyondtheTech:
I really wanted the front camera, but wasn't willing to spend upwards of $400 for it, comparing a non-contracted TyTN II and a contracted Tilt, or even a$200 difference for a non-contracted Tilt.

So, I'm thinking... Is there any way to get the front half of the unit with the screen and the front camera, just so I can get the full TyTN II?

I'm already CID unlocked and SIM unlocked, just thought I'd try to see if I can take it to the next level...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] PDADoc:
Yes it can be done, I believe. I did this very same thing with my 8525 after getting my hands on a broken JasJam from someone I know and then performing the necessary surgery (funny, because I really am a surgeon!). Now, there ARE a few caveats here: one, I knew for a fact that the AT&T 8525 and the i-mate JasJam were fundamentally the same hardware, and that the 8525 actually had the socket for the camera, so I just took the JasJam's camera, plugged it in, and replaced my 8525's faceplate with the JasJam's.

Because this device is new, however, you're going to have to wait for some time before spare parts become available. And because most mobile device people are highly neurotic, I don't expect that they're going to part with even a broken device, but you never know.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jasafar:
PDADoc, that's a cool story about the camera surgery. I love it!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] PDADoc:
Glad you enjoyed it, lol! I just got bored and since I already had my Kaiser device I figured why not? It worked out well enough, so it's in the desk drawer for use as a backup device. I'm vascillating on whether to sell it or not in the meantime.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] paulesport:
love the surgery story too..wish you filmed it. "Vascillating"? LOL Yeah you're definitely a Doctor!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] s'pht:
FCC photos on the Kaiser: https://fjallfoss.fcc.gov/prod/oet/forms/blobs/retrieve.cgi?attachment_id=791306&native_or_pdf=pdf
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ziddey:
interesting. I'd personally much rather transplant a speaker there though. It'd be especially useful for playing videos. Having the speaker on the back for that job is just silly.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ken0150:
does anyone knows if a hermes cam is the same of a tilt cam? i wanna do same as the "surgeon" but on ebay i can only find hermes cams... thank you
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fone_fanatic:
I think a couple guys over at hofo have done this with the Kaiser.. Ofcourse the hard part is finding the camera.

Once you do find the camera, cnn.cn has the front faceplate with the camera hole so if you do get a damaged kaiser with a marked up front cover, you can pick that one up for 12.99 plus shipping.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ken0150:
but now i need to know if the hermes front cam is the same as kaiser's 'cuz i cant find kaiser's one.thank you
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ken0150:
bump

sorry for doing this but i desperately need to know it.thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Daemos:
The best way would be to buy it and find out if it works?

I don't know if anyone could give you the answer 100% as most people who have Kaisers with cameras own HTC TyTN IIs and not Tilts. Unless if someone has access to the part numbers for both the Hermies and the Kaiser I don't know if you'd get the information you are looking for.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ken0150:
I think this is the best answer i got till now. tomorrow my tilt will arrive and i will check if there is a front cam slot
[Note Edge Q&A, Help & Troubleshooting] cyyong95:
How can I do that on SM-N915F?

I've reverted from custom roms since each and every developer has given up on the device.

Thanks
[G3 Q&A, Help & Troubleshooting] mechanicalbmx:
I recently switched from CM13 official nightlies to Fulmics 5.0 on my D852. When I have the network set to GSM/WCDMA/LTE Auto, it disconnects randomly and goes into searching for network. I have to throw the phone into airplane mode and back out to get it to reconnect. It doesn't stay connected for very long though.

This issue seems to go away when it is set to GSM/WCDMA auto.

Any ideas?
[G3 Q&A, Help & Troubleshooting] RapHaeL_4_4_4_:
The problem is with LTE, I can't make it work too. For now I guess we will have to stay on GSM/WCDMA
[G3 Q&A, Help & Troubleshooting] some guy1701:
What carrier are you using?
[Samsung Galaxy S7 Questions and Answers] stevevetter:
Hey everyone, has anybody experienced significantly poorer bluetooth performance with the S7 than with others? At first I thought it was my headphones as I had gotten a new pair or inexpensive but well reviewed headphones (Mpow Wolverine) at the same time as the new phone. They barely keep their connection and clip audio with the most minor of obstruction or even being @ 10' away. I then tried an older set of BT headphones which worked flawlessly with my previous phone (Moto X Pure) and I was having the EXACT same problem. I don't have problems pairing with devices; my car, Echo, watch. These are very close and line of site when in use and they don't move relative to the phone when in use.

Does the BT radio in this phone just suck, or do I have a defective unit?
[Samsung Galaxy S7 Questions and Answers] woodydog:
I use Bluetooth every day and have never had an issue.
[Samsung Galaxy S7 Questions and Answers] phoenix_rizzen:
There's several threads on this subject here in the S7 forums.

Some people have issues, others don't. Some have issues with Wi-Fi if Bluetooth is enabled, others don't. Some have issues with new BT headphones, others only with old, others don't.
[Samsung Galaxy S7 Questions and Answers] fredriks:
Use bt headset every day and haven't had any problem.
[Samsung Galaxy S7 Questions and Answers] WheresTrent:
I had issues with my Sennheiser Momentum 2 wireless, sent them back to Sennheiser to see if they can fix it. They also had similar issues on an iPhone but not as bad as with the S7.
[Samsung Galaxy S7 Questions and Answers] oplix:
I'm noticing static when wearing BT headphones and making any sort of twisting motion with my head even though the phone is like 1 foot away in my pocket. I'm very concerned how this will affect using the BT headset while bikeriding
[Samsung Galaxy S7 Questions and Answers] FreddieP:
I'm having bluetooth pairing issues with my 930F international exynos S7 flat. It won't detect most of my devices. My S6 Active detected & paired with them all and connected quickly to all paired devices.

Elsewhere I read to force stop Bluetooth Sharing then clear app data & cache. Did so and haven't noticed any difference.
[Xperia Z5 Original Android Development] Myself5:
Important Notice

This Posts includes Important Notices you need to read if you want to use MultiROM on your Z5.

You need to a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by [MENTION=2605798]nkk71[/MENTION] here: http://xdaforums.com/showpost.php?p=64248526&postcount=4 (Be sure to leave him a like!)

Recovery Notice: The Recovery is working with init_sony. If your Kernel is using a older way to load recoverys, then it wont work. Talk to your Kernel dev about using init_sony.

MOST IMPORTANT: When installing MultiROM on Stock, USB Connections will be broken (Charging is fine). It's caused by MultiROM screwing up the permissions of a init file which is responsible for USB. There are Kernels where USB is fixed already. A list of them is in post 3. For intrested Devs, this is how to fix it:

Just add

chmod 750 /init.usbmode.sh

to the on init step inside of init.sony.usb.rc. It will fixup the permissions MultiROM screwes up.
[Xperia Z5 Original Android Development] Myself5:
CHANGELOGs

General MultiROM Changelog can be found here:

Changelog

XperiaMultiROM Specific Changelog is here:

Recovery Changelog

MultiROM Changelog

DOWNLOAD

https://dl.myself5.de

The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.

SUPPORTED KERNELs

Basically you can use any Kernel you want, if you can live without Touch Support in MultiROM and use the no-kexec workaround.

However, if you want Touch Support as well as fixed USB and kexec-hardboot, use one of these kernels:

OM5Z Kernel

AndroPlus Kernel (not sure if AP Kernel has fixed USB)

If you want your favorite kernel to support kexec or at least working touch and USB, tell the dev to merge my commits.
[Xperia Z5 Original Android Development] nkk71:
Nice work mate :good::good:

Though every effort has been made to ensure some form of safeguards and redundancy, MultiROM has always been a "hack", and the no-kexec-workaround is as well.

The no-kexec-workaround is working nicely on HTCs (well at least M7, M8, and M9) and I've seen some other devices using it successfully as well.

As always, have your backups safely tucked away somewhere fully safe.

Happy testing, and feel free to mention me (easiest way for me to get notified), if you think there's an issue to be addressed with the workaround.... I've personally only used it on HTC M7, M8 and M9, so there may be device specific issues, which I cannot account for.

Special thanks to [MENTION=1162986]Captain_Throwback[/MENTION] , [MENTION=921816]ljjehl[/MENTION] and [MENTION=1238555]MassStash[/MENTION] for all the help and encouragement :o

And a very special thanks to [MENTION=2719389]z31s1g[/MENTION] not only for the official TWRP theme, but all the help he provided bringing it to MultiROM in a very quick way, thanks :good:
[Xperia Z5 Original Android Development] zate27:
Wow this is so nice I was waiting for this! I still have a few questions tho:

-Will this work with stock 6.0 with the modified stock kernel (DM-Verity disabled/ Sony RIC disabled / DRM-FIX) ? I'm worried if it will brick my device since you wrote you have a hard time with stock.

-What is no-kexec? Why do I need it?

-About the USB connection bug on stock so if I install your dirty fix everything will work as before? If I uninstall multiROM I assume the USB bug will go away right?

Thank you for your time sorry I'm a noob :)
[Xperia Z5 Original Android Development] Myself5:
1. Yes, it will work (You just won't have touch in the MultiROM menu (don't worry, you can setup the kexec workaround to work automatically in TWRP, as well as navigate with the volume buttons inside the MRom Menu). The hard time I get is with porting kexec to the stock kernel.

2. The No-kexec workaround is a (ha, who tought that :P) workaround to not use kexec-hardboot. Kexec hardboot is a technology to load a kernel into the RAM using an other kernel. This is how MultiROM usually works. Read more about that here if you're intrested: http://xdaforums.com/showthread.php?t=2104706 . Now, the no-kexec workaround is doing it on a rather dirty (but nicely working) way. It flashes the secondary ROMs boot.img to your boot partition, and then modifies the mount points to link to the ROM files in your internal/external storage (whereever you installed your secondary ROMs). It is needed, because of (1.), and because stock will probably not able to load a AOSP Kernel once kexec is working (so stock can only load stock, and AOSP can only load AOSP. For everything else, you need the no-kexec workaround).

3. Yes. USB is not working, because a script (which is responsible to start the USB Service) has the wrong permissions after booting from the MultiROM Menu (I was not able to include a proper fix for it inside the MultiROM code itself, maybe I will be some day). My App just fixes the permissions and executes the script (which else would be done by the system automatically) (It's basically just executing these 2 commands when pressing the button (or at boot when you turn the autofix on) https://github.com/Myself5/andoid_p...ava/de/myself5/stockusbfix/FixIt.java#L31-L34). Once you remove MultiROM, the script will get its proper permissions back as its a ramdisk file, inside the ramdisk it actually has its proper permissions, it just doesnt when getting extracted from the ramdisk at boot and MultiROM follows (MultiROM messes up the permissions).

I hope that answers your questions, if not, feel free to ask again :)

P.S. Be sure to read nkk71s Info about how to enable the kexec-workaround in the post I linked in the important notices post, it might shed some more light on what is the non-kexec workaround.
[Xperia Z5 Original Android Development] zate27:
Thank you very much for your quick answer!

So if I understood this right the detailed instructions would be:

Flash TWRP-Multirom-20160507-00-sumire.img or the recovery.img or both(?) with fastboot(?) to get the modified TWRP w/ MultiROM support

Now with this Modded TWRP I need to enable that no-kexec workaround in the settings?

Flash the actual multiROM: multirom-20160507-v33x-UNOFFICIAL-sumire.zip in TWRP

Flash e.g. CM13 (Finally :P) from here: http://xdaforums.com/xperia-z5/development/rom-cyanogenmod-13-sony-xperia-z5-t3356163" via the MultiROM menu.

Install the usbfix.

Does the CM13 Rom need to be modified to work with MultiROM or will it work as it is?

Thank you in advance :)
[Xperia Z5 Original Android Development] Myself5:
1. TWRP-Multirom-Stock-20160507-00-sumire.img is the recovery you need. Flash it via

fastboot flash recovery TWRP-Multirom-Stock-20160507-00-sumire.img

(If the Stock is not working, use the other one, I don't know which of the 2 existing recovery loading tools your kernel is using).

2. First flash multirom, then enable it in the MultiROM Settings Tab inside TWRP (see important notices on how to do that, nkk71 describes it in the thread)

3. yes.

4. Exactly.

5. Yes, only needed for stock roms, don't forget that. Oh, and it requires root, so depending if you have root already, you also need to install SuperSU (use 2.71 beta, it worked fine for me)

6. No, the secondary Roms don't need any changes at all.

BTW, your questions seem to be common, do you mind if I copy them together with my answers to a little FAQ in post 2?
[Xperia Z5 Original Android Development] zate27:
Thanks for answering all my questions. That should have cleared it up for noobs like me :P

The instructions seem a bit summarily written so your answers help a lot.

Yes sure go ahead FAQ is always nice :)
[Xperia Z5 Original Android Development] bongo1:
noob flasher here not quite got this fully working with a secondary rom yet still trying, but one scenario I can't get my head around.

If your primary rom is stock no root. How can you install the usbfix? Is this scenario possible?
[Xperia Z5 Original Android Development] Myself5:
Nope. USB Fix needs root to work. I am still working on a different workaround for it (maybe inside MultiROM), but thats lower priority.
[Xperia Z5 Original Android Development] Ashray_Vk:
[MENTION=3816568]Myself5[/MENTION] , hey.

Could you extend support to the z5 premium too maybe ?

Thanks

Regards

AVK
[Xperia Z5 Original Android Development] Myself5:
I don't develop for devices I don't own, as I then can't guarantee that everything does work nor that it won't break someones device. If there is a developer working on satsuki who wants to port it and comes across problems, I'll gladly help, but I'm not going to blind-port it on my own, I hope you understand that ;)
[Xperia Z5 Original Android Development] zate27:
Hey I have the E6653 and I'm getting error 7 while flashing multirom. Recovery flashing was successful tho. Why am I getting the error the codename of my phone should be "sumire" or is there something I've missed?
[Xperia Z5 Original Android Development] Myself5:
hum, 6653 is what I have too. What did you flash it on? Which recovery did you use? The Stock or the other one?
[Xperia Z5 Original Android Development] zate27:
Damn man you answer fast :P

I flashed it via TWRP, TWRP 3.0.2-0 (wrong I guess), I tried to flash the stock recovery one

Here is my fastboot output:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users

\Pein\Downloads\TWRP-Multirom-Stock-20160507-00-sumire.img

target reported max download size of 536870912 bytes

sending 'recovery' (33988 KB)...

OKAY [ 1.118s]

writing 'recovery'...

OKAY [ 0.464s]

finished. total time: 1.584s

Seems like it wasn't successfull because TWRP seems like the same as before :/ Should I try the other recovery? (Without stock)
[Xperia Z5 Original Android Development] Myself5:
which kernel are you using?

BTW: MROM TWRP looks pretty similiar to the default TWRP, it just has 3 bars in the upper right corner which opens the Mrom Menu.
[Xperia Z5 Original Android Development] Myself5:
kexec and Stock!

All right. I finally managed to get kexec-hardboot working on stock. I ported it to [MENTION=5169444]AndroPlus[/MENTION] Kernel at a first, because it seems to be the kernel you people use. I also uploaded a flashable zip (I used AndroPlus' flashable zip as a base), you can find it here:

Boot.img: http://dl.myself5.de/sumire/MultiROM/boot_E6653_M5_AP.img

Flashable ZIP: http://dl.myself5.de/sumire/MultiROM/Z5_AndroPlusKernel_M5_ModZ_Edit_Permissive_v27.zip

Source for it would be here: https://github.com/Myself5/android_kernel_sony_msm8994_kitakami_r2

I also send a PR for it to [MENTION=5169444]AndroPlus[/MENTION] (https://github.com/AndroPlus-org/android_kernel_sony_msm8994_kitakami_r2/pull/3)

(Ramdisk is from AndroPlus Kernel v27, with the fix below)

Oh, and because I am badass, I also fixed up USB on Stock with that Kernel.

For every Stock Kernel Developer who's intrested how I did that (looking at you [MENTION=5169444]AndroPlus[/MENTION] and [MENTION=3037651]zacharias.maladroit[/MENTION]), I simply adjusted the USB files permissions in the ramdisk.

Just add

chmod 750 /init.usbmode.sh

to the on init step inside of init.sony.usb.rc. I know it's dirty.. but hey. It surely is less dirty than my hacky App (which therefore is no longer needed BTW).
[Xperia Z5 Original Android Development] killedbyghost58:
Will suzuran devices work:confused:
[Xperia Z5 Original Android Development] Myself5:
No.

Regarding porting requests its the same as for Z5 Premium. If I don't own the device, I'm not going to port Mrom to it.

HOWEVER: For suzuran specifically, [MENTION=4819888]oshmoun[/MENTION] is working on porting MultiROM to it, based on my device trees which means MultiROM for Z5C is coming in the nearish future.
[Xperia Z5 Original Android Development] :
as the one being mentioned....I confirm ._.

However, not sure when "nearish" is cuz my device is still at the shop getting repaired.

*if the guy repairing my device is reading this, GET BACK TO WORK AND HURRY IT UP!!*
[Xperia Z5 Original Android Development] zate27:
Hey, I am on modified stock (Removed DM-Verity, Sony RIC, TA-Fix)
[Xperia Z5 Original Android Development] Zaisesl:
Hi. i want to download it but i cant get in dl.myself5.de, is just my problem or anyone is having this issue?
[Xperia Z5 Original Android Development] Envious_Data:
Samegoes

If anyone has a copy could you kindly upload it and the recovery img elsewhere :)
[Xperia Z5 Original Android Development] Myself5:
Sorry for the inconvenience, my VPS' host servers HDD died, which means the VPS had to be moved, and now is not really working anymore, which yet has to be solved by OVH. I uploaded the Z5 files here, so you can access them. Note: the AP Kernel mod as well as StockUSBFix.apk are gone for now, need to find them locally first.

Heres the link:

https://www.androidfilehost.com/?w=files&flid=61527

Regards
[Xperia Z5 Original Android Development] Zaisesl:
I have the zip of the kernel you modified but not the apk. If you want i can upload it
[Xperia Z5 Original Android Development] Dockyy:
can you tell me if its good because i cant boot with cyanogemod:

I'm on Stock rom with androplus kernel v29

I flash multirom recovery with fastboot

i flash multirom zip on twrp modded

i install new rom cynogenmod zip as primary

now i have the choice: STOCK (internal) and cyanogen (primary), but when i choose cyanogen on startup, i have bootloop and finaly back to startup choice...

i did something wrong ?

[MENTION=3816568]Myself5[/MENTION]
[Xperia Z5 Original Android Development] langeveld024:
I think this is the reason you can't boot cm.
[Xperia Z5 Original Android Development] Myself5:
Server is back

Hey Folks!

I just finished setting up the New Server. Unfortunally, it seems like all data on the old server is gone. I uploaded everything I was able to find (as well as what was uploaded by you when the server was down).

Thanks a lot for the patience and help.

If someone still has files local, and sees that they are not on my server yet, please send me a PM with a link to the file and I'll upload it ASAP.

P.S. The Server is no longer sponsored, and now payed by myself, so feel free to help covering my server cost :P

Regards,
[Xperia Z5 Original Android Development] juanfragar:
So I guess the only thing missing is the UsbFIX apk?

Let's see if in some free time I can take a look at your repo and try to compile it.
[Xperia Z5 Original Android Development] Myself5:
I'll compile it later. I though it wouldn't be needed anymore, as I provided the ramdisk fix.
[Xperia Z5 Original Android Development] kodiak80:
[MENTION=3816568]Myself5[/MENTION] I've compiled the kernel successfully, and used the ramdisk.img from an AOSP M build, but I can't seem to get the device to boot. At best the device sits at the Sony splash screen, though in my trials I seem to get it to boot loop, or simply come up and flash the red LED three times before staying lit. I'm certain I'm doing something obvious to cause these problems, but any help would be appreciated.
[Xperia Z5 Original Android Development] Myself5:
You most likely didn't use the appended dtb kernel, did you (that would be Image-dtb.gz)?
[Xperia Z5 Original Android Development] nabeelahmad909:
download link for multirom not working?
[Xperia Z5 Original Android Development] kodiak80:
I did use the dtb kernel image. I'm using the source from your android_kernel_sony_msm8994_kitakami_r2 git repository, and I built my boot.img per the README_Xperia instructions from the same repository. Any reason to think that would be a problem?
[Xperia Z5 Original Android Development] fratzika:
I wonder if this works on my little z5c.

I really want to try AOSP builds but need my bluetooth and camera. Multirom is the only way i can do this.

So...should i give it a shot?

LE: i found the answer in page 3 ("coming soon"). Sorry for this useless reply:)