yashsingh1/xdaforums huggingface dataset:
[AT&T LG Optimus G] r0b0m1nd:
N7 works over Bluetooth for me. Same with Google Play and numerous streamers like Pandora and Songza to name a few.
[AT&T LG Optimus G] DeathmonkeyGTX:
I have never had this problem ever, on several devices and cd players. But, my habitual usage includes Google play music app. It works well enough for me, and is fast on hsdpa or better.
[AT&T LG Optimus G] Globalrebel:
Any player should work over BT. Once your connection is up, just navigate to the player and you should be good to go. Since BT is just providing the A2DP connection, the player doesn't care where the music is being sent to. It just plays it to the audio out source. I think your problem is your headunit, but can't be 100% sure. My players (all of them, both streaming and non-streaming) work on any BT car I've connected too. Some cars won't display the album cover art and so forth, but the music comes across just fine.
[AT&T LG Optimus G] whatever125:
Well any music app will play music, but I can't seem to change the song from my headunit, it has to be changed from the phone. Changing songs from the car will pause it everytime.

I would like this feature to work with my car on an app like poweramp
[AT&T LG Optimus G] streetsmart999:
For me, All the controls work from steering wheel for every music player I used (from stock to ASOP) May be it depends on car stereo too.
[General Questions and Answers] flor1n90:
Hello. i wanna ask you, how can i unlock Alcatel OT Idol 6030X ? is coded in orange :(
[General Questions and Answers] xghost11:
i think sigmakey will unlock your phone .
[General Questions and Answers] Allfaq:
Sorry but don't works with sigmakey :((
[One (M7) Q&A, Help & Troubleshooting] teeniv:
My phone details: (bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.17.3250.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.24.707.3

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) meid: 00000000000000

(bootloader) product: m7_u

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0711000

(bootloader) cidnum: HTC__038

(bootloader) battery-status: good

(bootloader) battery-voltage: 3741mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d16dc66985

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

I am currently S-OFF and rooted. If i make it S-ON then the phone is stuck in bootloader. Any ideas on what I can do to un-root it (for warranty purposes)?
[One (M7) Q&A, Help & Troubleshooting] prunzzz:
Hey, wait.

you said you are sOFF

But your fastboot getvar all shows, you are sON

What exactly is your status?
[Nexus 5 Q&A, Help & Troubleshooting] angus242:
I just made a bunch of mods and now I'm having trouble getting the screen to turn on. Here's what I did:

1) Unlock boot loader (Used Android Toolkit)

2) Root (Same kit as above)

3) TWRP (Same as above)

4) Installed center clock mod (This one)

5) Installed smaller DPI nav bar (This one)

6) Installed 4-in-1 reboot (This one)

After all were finished, once my screen turns off, I see it kind of light up again (though still blank) and if you press the power button, the lock screen flashes on for a moment and then automatically shut off again. All the way off. A brief moment later, I seen the screen come back on but blank.

I read there was a possible compatibility issue between the center clock and small DPI mods so I removed them. Still have the issue. I can't see how the 4-in-1 could affect the screen.

Any ideas? I search but couldn't find anything close to the issue.

Thanks
[Nexus 5 Q&A, Help & Troubleshooting] angus242:
Here's a video. Hopefully the screen off but really on glow comes thru the vid.

[YOUTUBE]vK1BXGaSMlI[/YOUTUBE]
[Nexus 5 Q&A, Help & Troubleshooting] angus242:
I had too many issues so wiped back to stock.

The toolkit has a few bugs.

The center clock and small DPI nav bar apps had compatibility issues.

I was not able to revert back to stock with the 4-in-1 app.

Apparently there are still some issues with the toolkit ver 1.1. From my little investigating, I think there's a simple typo in the programming and it's looking for an older version of SuperSU (1.65 vs 1.69).

I'm back to stock, unlocked and rooted. Screen/display works.

I have no idea what broke or how it broke but it's back to normal now.
[Nexus 5 Q&A, Help & Troubleshooting] angus242:
Turns out my issue was with Light Flow. Not sure on the exact steps to get this to happen. But after 2 wipes and one rebuild without any restoring, I can get the issue to duplicate.

I personally believe it has something to to with being rooted and having the app use rooted options.
[Galaxy S 4 Active Android Development] my-blue-snog-box:
ATTENTION: THIS INFORMATION IS DEPRECATED!

I am leaving the thread up for reference, but as I no longer have the device and haven't been keeping up on the development of the I537, many of these methods may not (and probably won't) apply any longer. Please search the subforums for recent information.

Standard Disclaimer: Flash this at your own risk. I am not responsible for any problems that this file may cause, up to and including bricking your device.

Current Version: MasterPatch v.0.92​

Choice of Kernel Modules for MF1, MF2, or MF3

Optional Add-Ons:

-Camera Fix - still no stock camera support

-Hardware Keys support for S4 ROMs

-Speaker-Phone Fix

-Edited "gps.conf" file for faster GPS fix in the United States

-I537 build.prop

-apns-conf.xml file - This may make it so that you do not need to manually input your APN on a ROM for another carrier

FOR NOW, ONLY FLASH AFTER A FRESH ROM INSTALL AND BEFORE FIRST BOOT

Introduction:

After making several MasterPatch zips combining patches and features (mostly to make regular S4 ROMs compatible with the S4 Active I537), things started getting tedious. I decided to make an Aroma Installer Zip which will allow for anyone to to pick and choose what he/she wants.

Note:

Immediately after installing a ROM in a new slot, flash the MasterPatch. Do not reboot in between.

PLEASE SUGGEST ANY OPTIONS THAT YOU WOULD LIKE TO SEE IN UPCOMING VERSIONS

Thanks:

Hashcode for SafeStrap

TreyLWalker & jrkruse for the S4_Active_Call_Record_Fix.zip which fixes Speaker Phone

Lejay for the Camera Fix

Darkman for the Hard Keys Fix

Ayush Singh for the incredible guide on Aroma

Devo7v for recommending I try my hand at Aroma

Instructions on editing the code:

If you want to add your own personal options to the installer, you will need to:

-Extract the zip

-Add code to /MasterPatch_v.XX/META-INF/com/google/android/aroma-config to give the option in the installer's UI

-Add code to /Masterpatch_v.XX/META-INF/com/google/android/updater-script to install the files if the option is chosen in the UI

-Place corresponding files in /MasterPatch_v.XX/AROMA/CHECKBOXx/ or /MasterPatch_v.XX/AROMA/WINDOWx/ depending on where the option is chosen in the UI

DOWNLOAD ON ANDROID FILE HOST:

MasterPatch_v.0.93

MasterPatch_v.0.92

CHANGELOG

Version 0.93 20Nov2013

- UI Improvements

- Removed APN option...still working on it

- Added Camera apk from KitKat

Version 0.92 19Nov2013

- Initial Release
[Galaxy S 4 Active Android Development] my-blue-snog-box:
reserved
[Galaxy S 4 Active Android Development] dave5777:
Random reboots after flashing on the GPE ROM :(
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Was it a fresh ROM install? What firmware version are you on? What options did you choose?
[Galaxy S 4 Active Android Development] dave5777:
No dirty with Dalvik and Cache wipe mf1 speaker phone, GPS, cam
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Are you able to re-flash the same ROM in a new slot, flash the MasterPatch, boot, and let me know if you have the same problem? I tried dirty flashes on a few different ROMs earlier and didn't run into the problem.
[Galaxy S 4 Active Android Development] dave5777:
OK made a new ROM slot installed GE ROM used Aroma Master Patch selected mf1, cam, and speaker phone. Then wiped cache before rebooting. No problems yet :)
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Wonderful! I'll make a note in the OP to only flash after a fresh install for now. I will make kernel modules optional in the next build to try and rectify the problems you had.
[Galaxy S 4 Active Android Development] my-blue-snog-box:
[MENTION=3047491]Devo7v[/MENTION]:

All great suggestions and I really appreciate the feedback. I hope to get to it this afternoon--I just have a few things to take care of IRL and then I will see what I can do.
[Galaxy S 4 Active Android Development] Devo7v:
There is absolutely no rush, when you have time you have time. Everybody can get ROMs up and running, this is just more of a convenience thing. Enjoy your real life.
[Galaxy S 4 Active Android Development] my-blue-snog-box:
OP updated with new version
[Galaxy S 4 Active Android Development] my-blue-snog-box:
-The gps.conf still has all the needed code to work anywhere. It just allows for a quicker fix in the US.

-I don't think I'm going to add the Hyperdrive compatibility patch or LTE fix because they are specific to one ROM and I want to keep the size down.

-I plan on working on Google Wallet in the future.

Thanks again for the suggestions.
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Btw, the newest beta build is posted in the OP.
[Galaxy S 4 Active Android Development] dks21:
Hi, This a really good work. But as a user of the international version of the i9295 i cannot use this patch (but i tried ;) )... Is it possible to make it work on a normal i9295 to use regular or custom S4 roms?

Thanks in advance.
[Galaxy S 4 Active Android Development] Devo7v:
So this is something that has been bugging me for awhile. I'm not the most knowledgeable person on the subject, but it seems like you should be able to flash an S4 ROM and then flash an S4 Active kernel on top of it. It would have to be a 4.2.2 kernel for 4.2.2 ROMs and a 4.3 kernel for 4.3 ROMs, but it seems that it should work. It was possible to do this when flashing Samsung i9000 ROMs onto the Samsung Captivate. The devices had very similar internals, but the Captivate didn't have a front facing camera. This is a very similar situation to what is going on with the S4 and the S4 Active.

If anybody is adventurous, extract the kernel from the S4A Google Play Edition ROM, flash a 4.2.2 S4 ROM, then flash the S4A kernel on top of it. Make sure to flash the keys fix as well and see what happens. I feel like it should work, but please don't hold it against me if something goes wrong. You can always Odin back to stock.

If this can't be done I would like to know why.

---------- Post added at 09:25 AM ---------- Previous post was at 08:54 AM ----------

I just went and flashed 0.93 (well, I didn't flash it I just ran through the installer and then quit at the end). I only have a couple comments:

The "Welcome" screen needs some minor formatting:

"You are about to Installing" should say "You are about to install:"

"VERSION" is bold, which is fine but it should have the same formatting (bold/not bold) as "UPDATED" on the next line. I think it would also look better if "VERSION" was on its own line.​

Changelog looks much better, maybe include the day along with the month and year of each version.

On the System Information page, I would make the output text for Device Name, Board Name, and Manufacturer bold just like the output text below it.

Kernel Modules page looks good

On the Other Options page I would:

Make "Required before first boot!" all caps and bold to make it stand out. It is very important that users understand this.

For the descriptions of the mods, most of them are all caps except for the Camera patch description. Pick a format and stick with it.​

I'm not sure if you can change this, but on the About screen it says "ROM Name: MasterPatch" maybe change it to "ZIP Name: MasterPatch"

Like I said above I didn't actually complete the installation, and I can't imagine you changed the functionality so I assume that functionally it works the same as the last version. Again, thanks for doing this.

I was thinking more about the Hyperdrive AT&T Compatibility Pack and I think you're right, it would make the MasterPatch needlessly big. That said I definitely think there is something in there that corrects the APN. If and when you do get the APN setting working I would have an option for the T-Mobile APN as well.
[Galaxy S 4 Active Android Development] my-blue-snog-box:
[MENTION=543140]dks21[/MENTION], are you willing to try what [MENTION=3047491]Devo7v[/MENTION] recommended? If so, I am willing to work with you on a project for your device.
[Galaxy S 4 Active Android Development] dks21:
I have already tried something like this. In a total freestyle manner, i tried to flash the cyanogen 11 kitkat for i9505 ( this one: http://xdaforums.com/showthread.php?t=2521384 ) and

the kernel provided here (probably not suitable) http://xdaforums.com/showthread.php?t=2395242... But It didn't boot at all :D
[Galaxy S 4 Active Android Development] Devo7v:
So I think I know what you're problem is, you are flashing the S4 ROM which is 4.4, but then on top of that you are flashing the S4A kernel which is 4.2.2. The ROM and kernel versions need to match, so you need to either get a 4.4 version of the kernel or you need to flash the 4.2.2 of the S4 ROM.

Do me a favor, flash this ROM and then flash LeJay's kernel on top of it. Since they are both based off CM10.1 hopefully it will work. If it does than that means you need a CM10.2 kernel from LeJay to flash CM10.2 based-ROMs and a CM11 kernel from LeJay to flash CM11-based ROMs. I searched through LeJay's threads to find newer kernels but I couldn't find anything other than CM10.1. I noticed he released a CM10.2 ROM so you may be able to extract the kernel from that, but this is pretty much where my knowledge stops.

EDIT: The important thing to remember is that the ROM version and the kernel version must match to even have a chance at this working.
[Galaxy S 4 Active Android Development] dks21:
;;;

I am OK to test things. But as far as my knowledge about how to " compile, program, extract kernel and so on", is limited, I am affraid that my role would only be beta-tester...
[Galaxy S 4 Active Android Development] dave5777:
I flashed Gravitron and the master patch with the Hardware key fix. My only issue is the home button won't wake the screen. I checked the gpio-keys.kl and it has the right config. Any ideas?

I figured it out. You have to go into Gravitron custom settings and enable then disable it.
[Galaxy S 4 Active Android Development] Devo7v:
EDIT: It looks like you figured it out. Disregard this post.
[Galaxy S 4 Active Android Development] Reel E. Weird:
this post reminded me that I have flashed they Hyperdrive rom with the latest master patch and the ATT compatibility patch and I cant get my wifi to work.

I've tried flashing it in a different order and I'm still having issues with it.

Couple of things:

1) Does the new master patch cancel out the ATT compatibilty patch?

2) Is there a certain order you should use when flashing the Hyperdrive rom with the master patch?
[Galaxy S 4 Active Android Development] Devo7v:
You should flash them in this order:

Hyperdrive ROM, make sure you select the i337 kernel during the install process and DO NOT REBOOT.

Flash the MasterPatch with whatever you options you want.

Flash the AT&T compatibility pack last

That how I've done it in the past, before the Aroma MasterPatch was released. It could be that the MasterPatch is doing something different but I can't imagine it is. After you've wiped your slot and reflashed, if it still doesn't work try installing the individual fixes 1 by 1 like we used to have to do. Just make sure you flash the AT&T Compatibility Pack last. Let us know how it goes.
[Galaxy S 4 Active Android Development] Reel E. Weird:
ok. Thanks [MENTION=3047491]Devo7v[/MENTION]. Will try that and report my findings
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Who wants to test my newest attempt to get APN working? Hopefully it will do away with the need for the ATT Compatibility Patch. I need it tested on clean installs of two different ROMs: first being Hyperdrive, second being any other ODEXED ROM made for the S4. PM me if you can help.
[Galaxy S 4 Active Android Development] pyro254750:
I believe the issue is that we do not yet have access to an s4a kernel for any version above 4.3. Also apparently the kernel that we do have has some sort of touchwiz dependence since with exception to the gpe only touchwiz Roms based on 4.2 are confirmed working.

My guess is that the next progression we will see is a 4.3 update followed by the kernel from said update being used to produce 4.3 ota based Roms.
[Galaxy S 4 Active Android Development] Devo7v:
That is indeed correct. I was just trying to help somebody who didn't understand why they couldn't flash CM11. It looks like Hashcode is going to be updating SafeStrap in the next couple weeks, so hopefully he'll get 4.3 working.
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Oh? Where did you find this?
[Galaxy S 4 Active Android Development] Devo7v:
It was a quick comment he made a few days ago.

EDIT: Here it is. I had to look through all the SafeStrap threads to find it again.
[Galaxy S 4 Active Android Development] davenger1:
To get WiFi on hyperdrive flash ROM and patches let it boot and settle, reflash MF1 2 or 3 module witch ever u are on and wipe cache and dalvik cache reboot and WiFi will work!
[Galaxy S 4 Active Android Development] Globel:
I am using the aosp with safestrap and just the MasterPatch_v.0.93 everything seems to work fine... I Am i missing something without the AT&T patch.... ? Can i be missing any cell bands? I seems to get good service.
[Galaxy S 4 Active Android Development] casadelbeard:
The AT&T patch that is being mentioned is for the Hyperdrive ROM. That particular ROM was developed for the Verizon S4, so there are patches to put non-VZW phones on the proper cellular network.

If your ROM was developed for an AT&T S4, then you need not worry.
[Galaxy S 4 Active Android Development] whtboymic:
Is there a step by step?

Hey all, I'm trying to help a buddy put a custom ROM on his i537. I have a couple questions:

do i follow all instructions for flashing a standard S4 rom prior to flashing this?

If yes, does a stock rom with touch wiz work better than a GPE rom?

Any help is much appreciated. Thanks.
[Galaxy S 4 Active Android Development] Reel E. Weird:
Forgot to comment, but this worked for me. Thanks a lot!
[Galaxy S 4 Active Android Development] Globel:
do you add this at the same time when you flash the aosp? Like add it so you flash both at the same time? After reloading my phone any time I apply this patch my phone randomly reboots... takes a while maybe every 7-20 minutes...

My procedure:

1. Odin MF1 oneclick

2. on first start I skip everything straight to file manager.

3. Run ar.apk

4.run safestrap

5. install recovery select reboot into recovery

6.flash i9295 google edition v1 over stock... click home when done... no reboot...

7. flash masterpatch 93.1

8. select mf1 , and select all other options.

9. Reboot phone ..

10. Phone should be done I setup as usual...

Phone reboots first during app updates in the playstore...
[Galaxy S 4 Active Android Development] Globel:
I found after another odinone click and manually installing all patches my phone no longer reboots
[Galaxy S 4 Active Android Development] N0ctrnl:
I actually get random reboots on Darkman's Nexus AOSP port. It isn't a full device reboot though. Just drops back out to the boot animation and quickly back into the ROM.

I flashed it using the following steps:

1. Create new ROM slot.

2. Flashed AOSP ROM

2a. Flashed camera fix for AOSP ROM

3. Ran MasterPatch 0.93

Anybody else had something similar? It seems to run really well and everything works, but the reboot issue is no good, of course. :)
[Galaxy S 4 Active Android Development] Globel:
Why flash the camera patch if its included in the master patch?
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Hey everyone, I haven't disappeared. I'm working on a few other projects. Right now, the best way to reach me is Hangouts (url in my sig) if you have any bug reports or feature requests. Life is crazy: work, planning a wedding, family stuff, etc. I hope to get back soon. I will check the thread as I can. Thanks for the patience.
[Galaxy S 4 Active Android Development] ohwarumbloss:
i9295 user here...

I did some testings but always ended in camera fail.

But, you can use a 4.3 CM build (SlimRom/AOKP/CM) with the 4.3 Kernel provided in the S4a unofficial CM build and they will run. Using the Masterpatch, or simply copy'n'paste the gpio-key.kl will make the Hardware keys work.

But both, the Camera patch and the Masterpatch, won't get the Cam to work.

That's were I am stuck :(

If we fix this problem, the world of i9505 Roms is open for us ;)

Real life always comes first. Period.
[Galaxy S 4 Active Android Development] dks21:
Have you tried this fix: http://xdaforums.com/showpost.php?p=45330988&postcount=50 ?
[Galaxy S 4 Active Android Development] ohwarumbloss:
Yes, I did. It does not work and I give it up for now. We need a Developer for this job, not a Copy´n´Paste Dude like me ;)
[Galaxy S 4 Active Android Development] yankeesfan714:
[MENTION=5381171]my-blue-snog-box[/MENTION]

Are you still using a Active? I know we had to pull mf1 2 and 3 modules to flash Roms. Well on 4.3 we are in the same boat. How would one go about getting their hands on ML2 modules?
[Galaxy S 4 Active Android Development] my-blue-snog-box:
I'm rocking the Nexus 5 now: I sold my I537. Having a device that is totally open has really improved my knowledge of Android. That being said, I will gladly make a zip package if you get me the stuff I need. Do you guys have root and SafeStrap for 4.3 now? I hope so--that would be great! Hit me up on Hangouts (see the link in my sig) and we can figure out what to do to get y'all rolling :)
[Galaxy S 4 Active Android Development] yankeesfan714:
The field where your hangouts name is does not expand so I can't see it.. Mine is briandutch714@gmail.com I hope I can get you the stuff that will help us out. Thanks for your help
[Galaxy S 4 Active Android Development] Malous:
Hello, may I ask something. The reason that you stop updating this, is that it doesn't need it or you bought another phone? Thank you.
[Galaxy S 4 Active Android Development] Devo7v:
He has another phone. He will occasionally stop by and update things, but he's really just doing us a favor. I appreciate it.
[Galaxy S 4 Active Android Development] my-blue-snog-box:
Sorry that things have stopped, everyone. Life has gotten crazy. Here are the two options that I see: we can either have this thread closed, or someone else can take over the project. I just don't have the time to keep up.

If someone else is willing to take over, I will gladly assist in whatever way I can (as I can make the time). I can also recommend plenty of good resources.

If someone is willing to step up, please contact me.
[Galaxy S 4 Active Android Development] sharpeyedman:
The link is down. Can anyone share this file? I am willing to upload it and share the link. Help is greatly needed.
[Galaxy S 4 Active Android Development] stinky180:
Can someone re-upload MasterPatch_v.0.93? The links are down in the original post.
[Galaxy S 4 Active Android Development] Jaydizzle414:
anybody? this would be very helpful as im trying to flash gpe 4.4.4
[Galaxy S 4 Active Android Development] stinky180:
i found the armoa patch on a different thread and it did not work. find masterpatch v.2 as it worked for me. should be in the general forum.
[Galaxy S 4 Active Android Development] Jaydizzle414:
Did this and my WiFi is still broken on 4.4.3
[Galaxy S 4 Active Android Development] stinky180:
can't the same as, i flashed hyperdrive and the masterpatch v.2 and wifi is working. before flashing the masterpatch, wifi was not working.
[Galaxy S 4 Active Android Development] Jaydizzle414:
I got it working now :thumbup: