yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] jhoutz:
The Droid Maxx shares a forum with the Droid Ultra. It is pretty much the same phone...maybe they can help you.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] 704Champ:
Well, the issue is fixed though I can't give an exact reason, other than the most recent OTA update seemed to fix it. So, if you experience this issue, I guess make sure your software is up to date.
[T-Mobile Samsung Galaxy S6 Edge] aaronc_98:
Could we install them on the Edge? I assume that we can but would lose edge functionality, but has anyone tried? I just got another phone and have not yet gotten TWRP setup but I will soon...
[T-Mobile Samsung Galaxy S6 Edge] ktetreault14:
Wouldn't try. Don't think the display will work.
[Verizon Galaxy Note 4 Themes and Apps] bdorr1105:
********This is for the Developer Edition ONLY and I can't stress this enough ********

********YOU MUST BE DEODEXED********

You can find more information

Here

on the 3Minit Battery Mod. This is not my work, I just followed the instructions to make it work. Credit goes to [MENTION=4619873]gharrington[/MENTION]

Instructions:

BEFORE YOU FLASH - ALWAYS MAKE A NANDROID BACKUP

1. Download

Zip file here

2. Place on your SD Card

3. Reboot to Recovery

4. Wipe Cache / Dalvick

5. Install Zip file

6. Reboot - It will take a while for reboot

Note this zip installs free version of 3Minit. If you want to support gharrington then you can pay for the paid version in the app store. Both Versions are in the App store

Screenshot

Thanks:

1. gharrington - Great instructions and App

2. balla48801 - For the Deodex Instructions, MODS and ZIP file
[Verizon Galaxy Note 4 Themes and Apps] bdorr1105:
Please delete this thread..... Thanks
[Verizon Galaxy Note 4 Themes and Apps] shpotik:
Thanks for this.

Why delete thread?
[Verizon Galaxy Note 4 Themes and Apps] bdorr1105:
Because it seems as if its already built in, there is only one dedoexed ROM...It was just to get everything started
[Nexus 5 Q&A, Help & Troubleshooting] silentcovenant:
Anyone know if there are any fast camera apps? I notice, whenever I take a picture, there's a slight delay, turning what would've been a perfect picture into a blurry mess. My old HTC One(m7) took really fast photos, pretty much instant to when I pressed the button. Similar to what the iPhones do, I think. Anyone know of any Camera apps, not the AOSP or Google camera app, that takes quick photos?
[Nexus 5 Q&A, Help & Troubleshooting] till22:
"Manual Camera" works great for me.
[Nexus 5 Q&A, Help & Troubleshooting] alen1901:
Yeah, manual camera is fast as hell. Close to galaxy s6 camera. At least on lollipop.

Sent from Pure Nexus 5
[XDA Assist] APizzaDerp:
Hello,

I'm kinda a noob to all this rooting thing. I somehow made my phone really hard bricked. It shows QHSUSB_Bulk in the Device Manager. Another issue is that my pc won't detect my phone in download mode, which kinda sucks for me because that means the LG Flash Tool 2014 won't work on my phone. Is there anyway to fix it? I've been going about it for a month or two using online help, which didn't help:(. So if anyone has a fix, can you please reply ASAP?

Thanks,

APizzaDerp

P.S. I can't attempt the Ubuntu method because I need my PC to stay in Windows for many reasons and can't afford to lose all my PC data just because of moving to another OS. Thanks Again:)
[XDA Assist] Heisenberg:
Hi :)

Thanks for writing to us at XDA Assist. Check out these threads:

[FIX] Unbrick LG G2 stuck in Qualcomm HS-USB QDLoader 9008 mode

Unbrick lg g2 qhsusb_bulk(qualcomm 9006) export very partition(hdd)
[Verizon Samsung Galaxy S6] S1L3nTShaDoWz:
Previously on the S4 I came to the conclusion I could use the international variant of it on Verizon as it had the proper CDMA bands for the job, is this the same case with the S6? Could I buy the international one that is unlocked and use it on VZW network without problems and if I have them what would they be? Going to do my own homework of course but I always want XDA's opinion on things like this.
[Verizon Samsung Galaxy S6] JGoldz75:
I was actually in the process of typing up this thread myself! I am also interested in the answer to this one. And can the international version be rooted? I need me some Greenify!

Edit: After speaking to a Verizon rep online, I was told "In theory, it should work; but we cannot guarantee device usability and stability from non-verizon devices".

Any other XDA thoughts?
[Verizon Samsung Galaxy S6] S1L3nTShaDoWz:
The International one is fully bootloader unlockable and rootable from the start, hence why I want it over this locked down one. Though someone suggested to me in a PM to post this in the international forum so I will try that and update here with whatever results I get.
[Verizon Samsung Galaxy S6] GuestK00143:
From what I could find it won't work because it's GSM and won't work with CDMA carriers. Here is a link to the info I found.
[Verizon Samsung Galaxy S6] edgemaster191:
I remember reading that the Verizon and Sprint variants have a separate Qualcom modem in them to connect to their CDMA and LTE bands.
[Verizon Samsung Galaxy S6] lilsalmon:
I have the US Verizon Galaxy S6 as well as my wife now. Currently in Cancun using a popped in TelCel SIM card seeing crazy 4G speeds on the hotel strip area.

So yea. The S6 from Verizon is killer with foreign SIMs.

Lil
[Verizon Samsung Galaxy S6] bkeaver:
Can i ask what this has to do with OPs question?
[Verizon Samsung Galaxy S6] lilsalmon:
Sorry I just reread the post and thought it was referencing using the vzw version abroad.

You can delete my post if it offends you that much. Was just trying to help because I just went through the process of using it in Mexico for the first time.
[Verizon Samsung Galaxy S6] bkeaver:
It's not that big of a deal, I just thought I was missing something :)
[Verizon Samsung Galaxy S6] lilsalmon:
No worries here ... :)
[Verizon Samsung Galaxy S6] Edu616:
Any answers yet? Thanks.
[Verizon Samsung Galaxy S6] rumdada:
Just want to let you all know the international version will not work on Verizon.

I have one was going to sell on craigslist and we met at verizon and it will not recognize the mobile network.

Im still trying to sale this thing lol
[General Omni Discussion] 01tarik007:
Hi friends,

I try to make my own ROM by adding my own intent actions, this actions will brodcasted by the system when i click on the camera button ,

where i can add this two lines :

Intent myintent =new Intent("ACTION_MY_OWN_INTENT");
context.sendBroadcast(myintent);

Thanks for any help.
[General Omni Discussion] 01tarik007:
Now my action is broadcasted by the system , only when i click on Volume up or down physique button by doing this:

open the AudioService.java path/to/android_root/frameworks/base/media/java/android/media/AudioService.java.

search for sendVolumeUpdate function

// UI update and Broadcast Intent
private void sendVolumeUpdate(int streamType, int oldIndex, int index, int flags) {
if (!isPlatformVoice() && (streamType == AudioSystem.STREAM_RING)) {
streamType = AudioSystem.STREAM_NOTIFICATION;
}

if (streamType == AudioSystem.STREAM_MUSIC) {
flags = updateFlagsForSystemAudio(flags);
}
mVolumeController.postVolumeChanged(streamType, flags);

if ((flags & AudioManager.FLAG_FIXED_VOLUME) == 0) {
oldIndex = (oldIndex + 5) / 10;
index = (index + 5) / 10;
Intent intent = new Intent(AudioManager.VOLUME_CHANGED_ACTION);
intent.putExtra(AudioManager.EXTRA_VOLUME_STREAM_TYPE, streamType);
intent.putExtra(AudioManager.EXTRA_VOLUME_STREAM_VALUE, index);
intent.putExtra(AudioManager.EXTRA_PREV_VOLUME_STREAM_VALUE, oldIndex);
sendBroadcastToAll(intent);

}
}

and add your own action in the end of this function

Intent myintent =new Intent("ACTION_MY_OWN_INTENT") }

use

sendBroadcastToAll

function to broadcast the intent, so you can be sure that the context had been well initiated.

now I try to make my own module for sending my own action intent, any helps are welcome.

:laugh::D
[General Omni Discussion] 01tarik007:
offfff

finally the secret is here

android_root/frameworks/base/policy/src/com/android/internal/policy/impl/ PhoneFallbackEventHandler.java

Thanks t me
[Shield Android Development] Steel01:
Reserved

Downloads

1. Main downloads

MultiROM: multirom-20150801-v32-UNOFFICIAL-roth.zip

Modified recovery (based on TWRP 3.0.0.0): twrp-multirom-20160526-UNOFFICIAL-roth.img

Kernel w/ kexec-hardboot patch (Stock 5.1 update 106) [flashable zip]: roth_kexec_boot_stock_106.zip

Kernel w/ kexec-hardboot patch (Stock 5.1 update 103) [flashable zip]: roth_kexec_boot_stock_103.zip

Kernel w/ kexec-hardboot patch (CM 12.1) [flashable zip]: roth_kexec_boot_cm_12_1.zip

MultiROM Manager: MultiROMMgr-debug.apk​

2. third-party kernels with kexec-hardboot patch

None yet

Nicely ask your kernel developer to merge kexec-hardboot patch (patch for roth).​
[Shield Android Development] Steel01:
Reserved

Notes

I finally made this work. However, it is still not well tested. Three things to note:

1. The touchscreen does not work in the boot selection. Neither will the d-pad. So, I've had to set Y as up, B as down, and A and power as confirm.

2. The recovery is sideways. This is because that's the native orientation of the display. TWRP 3 no longer has rotation code, so I can't rotate the display to landscape.

Also, I have yet to make a Linux rom boot using this. That's mostly because I haven't got the guest atags patch working on Fedora's kernel (haven't tried and personally don't really care about others). If and when I make it work, I'll try to make an mrom installer for it. Sound and graphics acceleration don't work, but everything else seems really solid. Kudos to [MENTION=2826079]Gnurou[/MENTION] for coding as much as he has and getting most of it merged into the upstream kernel.
​

Changelog

20160526

Updated recovery to TWRP 3

20150905

Updated the Stock 106 zip to include the volume fix.

20150905

Added kexec patch for Stock 106.

20150801

Found problems in the kexec patch. Synced those to match Tassadars hammerhead patch and voila, stuff started working better... CM 12.1 and Stock 103 boot great as secondaries now.

20150723

With the release of official update 103, this seems to work pretty well. Some basic testing with stock as primary didn't show any problems. However, I haven't tested much. I've removed older kexec images since they would just cause problems anyway. I've also added multirom manger, which on a rooted system should set up everything in only a few taps.

20150604

Disabled adb in multirom completely. For some reason this breaks adb/mtp/etc in all roms, primary and secondary. Also, by doing a primary backup and restore to secondary, the stock rom boots as a secondary. Unfortunately, it seems to have all the same problems that it has as primary when multirom is enabled. On the bright side, CM seems to work perfectly fine as primary and secondary now.

20150528

Updated TWRP to latest upstream. Removed exfat-fuse support as well to allow it to fit. This means ROMs cannot be installed to external SDs or usb harddrives formatted as NTFS or exfat. ext2/3/4 and fat32 should work. However, inserting multirom into the stock image still breaks many things, so using multirom is still not recommended. I am hopeful that the eventual android 5.1 update will work better with multirom.

20150423

Updated multirom to fix force close of the play store on stock internal. Didn't work.
​
[Shield Android Development] AltCtrl701:
Thanks for this! I now have grid gaming AND cm! Again thanks for your work on the shield.
[Shield Android Development] Steel01:
Updated TWRP and Multirom. Still wouldn't call it truly usable, but at least it's workable now. Stock console mode and the play store break when multirom is in use. That's the obvious symptoms. Also noticeable is the internal sd not mounting... I still don't know how to fix it, but it seems part of the init scripts are either failing or plain not running. If you play with this, you'll want to keep a backup of a pristine boot.img around. That's what I'm doing when I want stock for a set top box. But now that adb is working in ROMs, I don't know of any problems using this with CM 12.1. That has me hopeful that if Nvidia ever gets it in gear and releases the update, this will all fall into place.
[Shield Android Development] Steel01:
Tassadar updated the multirom TWRP to 2.8.7.0, so I ran builds. Still waiting on Nvidia before continuing with multirom research and implementation... Build in the second post.
[Shield Android Development] Steel01:
Build updates and a success story. I can boot through the multirom boot menu to stock 103 without problems. I need to do more testing, but it looks like this is safe to use now. However, backup and restore in twrp seems broken with update 103. To the point a restored system will not boot.

Edit: Fixed the backup / restore problem. Link updated. Manager will be updated shortly.

Edit 2: Botched the kexec build apparently. Running a new one now and will update once actually tested this time.

Edit 3: Fixed the kexec kernel. But my previous CM 12.1 build won't boot as a secondary, whereas it did on the old kernel. Will have to debug this.
[Shield Android Development] paed808:
Does multirom work if the Shield's primary rom is KitKat? (Update 101) I haven't updated to Lollipop.

I noticed you don't have any kexec kernels for KitKat..
[Shield Android Development] YamazakiRobert:
can you check the following tread http://xdaforums.com/showthread.php?p=47964256#post47964256

they have a nice theme and its landscape mode and same resolution of the shield device

thanks
[Shield Android Development] Steel01:
Small update.

Stock 103 boots fine as a secondary (using the copy primary to secondary function). That makes it a lot easier to experiment on the primary without having to flash back to stock anytime I want to do something not dev related.

Stock 101 does *not* currently boot as a secondary. If I set it up as primary, turn on adb, copy to secondary, then try to boot it, the logs show init blowing up all over itself. I have no idea why right now. Also, stock 101 won't work as a primary either, since things like the play store, console mode, and who know what else broke anytime I flashed a kexec kernel.

For some reason, multirom doesn't copy the boot image command line parameters into the secondaries kernel command line. This makes it difficult to disable selinux for porting purposes. I had to recompile the CM kernel with selinux disabled to get it to boot with the new blobs initially.

I expect I'll be able to fix the last point with a bit of research. At that point, dual booting CM and stock 103 should be completely feasible. I'm kinda stumped on the problem with 101, though. And since I don't plan to use it, I probably won't spend much time debugging the problem. If someone wants to look into that, I wouldn't mind helping them get started, though.

Edit:
[MENTION=4549135]paed808[/MENTION]: No, I've removed the old kitkat kexec kernel for reasons stated above. I could boot into CM as a secondary with stock kitkat without problem; however, that broke stock so bad, I considered it unusable.
[Shield Android Development] paed808:
[MENTION=1416222]Steel01[/MENTION] I just wanted to know just in case I accidentally enable Multirom while flashing a zip in TWRP. I don't want to use Multirom on my Shield Portable. I have a Nexus 7 for that. I just want TWRP, but this is the only TWRP for the NSP. If I accidentally enable Multirom what happens? Does it inject itself in the bootloader? If that fails, will it result in a brick?
[Shield Android Development] Steel01:
Nah, it's really hard to brick one of these. Trust me, I overwrote the partition table and still was able to recover... (don't try that at home). As long as you don't flash the multirom zip, you won't even be able to access the multirom section inside TWRP and it won't inject itself during any other flashing.

The reason that this is the only truly working (and maintained) recovery on the Portable is because it has the screen rotation code. I couldn't get that to work properly for CWM (and agabren never released his code and won't respond to any contact about it) and upstream TWRP doesn't have it either. So, multirom TWRP is it. But as mentioned above, as long as you don't flash the multirom zip, it should act exactly like the upstream TWRP.

As a fun side note: There are two things that I currently know of that can brick a Shield device (Portable, Tablet, and TV)

1. Overwrite or delete the bootloader. That's the blob partition to fastboot. So yeah, be very careful when fastboot flashing that one.

2. Put something android doesn't recognize in the dtb partition. I actually didn't know this one until recently. The bootloader interacts with this partition during early boot, like before it hands off to boot.img. And apparently, that's the only way the bootloader will read a dtb and hand it off to the kernel. Yeah... so, I've been pretty lucky in my testing that I didn't brick my device by flashing something else there (like an upstream linux version, don't do that).

Interestingly, you can completely obliterate the partition table and the bootloader will still run. However, it won't be able to find the LNX partition to continue booting. But you can fastboot boot whatever you want (like Linux on an sdcard). Moral of the story: Don't let Linux 'fix' your internal GPT for you... You might have to pull favors with other Shield owners to undo that one. Well, I now keep a dd'ed copy of that GPT, just in case.
[Shield Android Development] paed808:
[MENTION=1416222]Steel01[/MENTION]. Thanks for the detailed explanation. Now I know what "blob" and "dtb" are. I thought just the boot.img was the bootloader, as it is on most Android devices.
[Shield Android Development] Steel01:
Alright, I think this is finally ready for prime time. CM 12.1 and Stock 103 should work as primary or secondary without problem. If you see a problem, please report it. If you've got an older version installed, you'll want to reinstall almost everything: multirom, secondaries, kexec, etc. TWRP and the primary rom should be fine as is, though.

I was able to get Stock 101 to boot as a secondary. However, it's still not all there. The internal sd stuff doesn't all mount, causing all kinds of ugly problems, not the least of which is the Play Store crashing. I can manually run 'start sdcard' as root to get /mnt/shell/emulated mounted, but the links under /storage don't come up. At least at that point, the store works and it seems streaming and all that is fine. However, the main internal sd path (/storage/emulated/0) remains empty. So, not really a fully usable setup.

Edit:

Okay, so that was weird. I left my Portable booted into 101 for a bit. When I came back, all the internal sd mounts were correct. Eh? Maybe stuff refreshed after a bit and picked up the sdcard bind mount? Slightly confused, but it seems there is a way to make this work. Will probably look into this more eventually.
[Shield Android Development] AltCtrl701:
Does this break miracast, or is it a problem with lollipop? I edited system/build.prop and added persist.debug.wfd.enable=1 which allowed me to see my miracast adapters but it just disconnects and fails to pair. Running 103 stock rooted with your multimod recovery set up, but only internal stock rom with modified kernel. I can however cast the scrren through netflix app, thats it, hulu doesnt see them and i cant mirror screen. Thanks for any info!

Sent from my SAMSUNG-SM-G900A
[Shield Android Development] YamazakiRobert:
the miracast its a problen with lolipop, but for you use the multi rom with last cm you need the shield using the update 103 with is lolipop
[Shield Android Development] blessedyeti:
Working on my Shield portable using 103 and your CM Rom. Straightforward install but didn't know where to find CM Rom at first. One issue, downloads in CM were not accessible ( message cant open file) but were found in 103 downloads? Did I use wrong patch? Thks
[Shield Android Development] Steel01:
Why an I not getting email updates to this thread... Sorry for the slow response.

Yeah, Google removed miracast support in Lollipop. I've never used screen casting, so I can't comment further than that.

Downloads in CM are not available? Do you mean that CM cannot access the internal SD download folder? If so, is the rest of the internal SD accessible? I'll check tonight when I can get my hands on my Portable.

You want the patch for whatever your internal ROM is. Though technically, you don't even need a primary ROM, that's what I'm have for testing right now. Everything is secondaries. In which case, you can use whatever boot image you want. Wouldn't recommend this for normal usage, though. The Portable is already short on space...
[Shield Android Development] blessedyeti:
secondary Rom will only read offf of ext sdcard, not internal storage?

Edit: Storage now working. Don't know what changed. Rooted CM with Kingroot. 103 seems snappier than CM.
[Shield Android Development] Steel01:
I was wondering if there was a permissions issue because it worked fine for me. But I'm using the newer cm build from later in the thread and not the stable one in the OP. And... Don't use root methods on CM... It's built in and in the developer options menu.
[Shield Android Development] Steel01:
Kexec patch added for Stock 106. Download in the manager app and in the second post.
[Shield Android Development] YamazakiRobert:
[MENTION=1416222]Steel01[/MENTION] please check this recovery http://xdaforums.com/showthread.php?t=2676180 is a twrp with the new theme with landscape support
[Shield Android Development] JazzMartian:
Yeah this fork of TWRP is nice. I was just hoping it would be developed more. I downloaded the source, but have no clue of how to compile it.

https://github.com/Tasssadar/Team-Win-Recovery-Project

A tut on here wasn't too encouraging, when it listed the required base knowledge/familiarity, and I didn't meet those credentials. The OP stated that it probably wouldn't happen with his tut for a noob. Never compiled source code before. I have the Android SDK and Android Studio...but don't know how to use them really.

Maybe somebody here could/would compile it? I'm interested in what shape it's in now.

The TWRP team will hook up an official build for our NSP (or and Droid lacking one), as long as they are provided with the source of the kernel and the build.prop.
[Shield Android Development] Steel01:
I've talked to Dees_Troy and Tassadar a bit about the device. The problem is that the display is mounted sideways. When you boot TWRP, you'll notice the initial symbol is sideways. That's the way the screen is designed to work. So, for anything to be usable, the software has to rotate the display. This works on Tassadar's multirom TWRP due to some hackish code that isn't being actively maintained anymore. I tried compiling the new 3.0 based multirom TWRP, but not enough of the rotation code is left to make it work. And Dees_Troy and _that don't think proper rotation support would work very well (and wouldn't be easy to write). So, the Portable might not get any upgraded TWRP. I might be able to patch something together eventually, but it's not very high on my priority list at the moment since the current release works fine with cm-13.0.
[Shield Android Development] JazzMartian:
Ah. Well glad I did strain myself trying to compile it lol. And agreed the current version runs good. It's just in us to always want more hah. Thanks. It's good to get the little development we do get out of it.

Oh and the insanely minimal amount of system space kills me. Especially when my my phone (with considerably lower specs) has almost 2GB of system space. SMH
[Shield Android Development] YamazakiRobert:
why not let the display sideway on recovery? is not like we stay on recovery much time, and the buttons on the screen are going to be larger and more easy to use
[Shield Android Development] Steel01:
Having a sideways recovery would probably drive me nuts. But I tried building that way a couple days ago and the display was still corrupted. No idea why, but haven't had time to get back to it since.