yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active General] ShimaMiku:
I'm new to this SS method. I have it installed, and my stock ROM is MF1. I have a 64gb micro SD card in my phone, but I haven't done anything as of yet because I'm not sure on the partition portion.

So if the internal memory is 16gb, and you turn in into two partitions...do they share "internal sd card" memory, or is it two partitions now? For instance, is it:

Partition 1: Total Partition Storage = (system memory 1) + (user memory 1)

Partition 2: Total Partition Storage = (system memory 2) + (user memory 2)

OR:

Partition 1: Total Partition Storage = (system memory 1) + (shared user memory)

Partition 2: Total Partition Storage = (system memory 2) + (shared user memory)

Reason I ask is because I'm trying to determine how much storage to partition. If it is shared, I only have to account for the system data, but if it is two entirely separate "user data" partitions, then I have to figure out how much I leave in stock versus AOSP (since stock is much more bloated).

Anyone else find a good balance?
[Galaxy S 4 Active General] baldwyn:
What's up with the cam patch being gone now? All I get is Error 410 - Gone
[Galaxy S 4 Active General] Fortune090:
Click on the link that comes before the zip link. It'll take you to the forum post where the link is. I was getting the same issue. ;)
[Galaxy S 4 Active General] pyro254750:
It appears to share data. I have the same photos present in gallery in both stock and slot 1.
[Galaxy S 4 Active General] baldwyn:
Found it. Thanks!

---------- Post added at 12:09 PM ---------- Previous post was at 12:05 PM ----------

My wifi doesn't work. I followed every step and everything else works just fine but when I hit the wifi toggle, it turns right back off.
[Galaxy S 4 Active General] dave5777:
Is your stock firmware MF1 or MF3

And did you flash the correct kernel for your firmware after the ROM?
[Galaxy S 4 Active General] br0adband:
It sounds like you didn't flash the kernel modules. Just for the record, at this point, to get the AOSP ROM working correctly meaning all the hardware functions as it should (but items like the camera will be lacking in features which are software-based, like HDR mode, etc), these are the steps. There are three relevant files you need to get everything working: the AOSP ROM zip itself, the kernel modules zip (depending on your build but there is a zip for MF1 and one for MF3 available as required), and the camera fix zip. Once you have all those:

1) Install Safestrap, as long as you have no issues then...

2) Copy the relevant ROM zip file, the kernel modules file (MF1 for that build, and MF3 for that build, respectively), and the camera fix to the microSD card - you can put them on internal storage but it's easier if it's just on the card seen as extSD

3) Reboot the device, when the funky kid shows up on screen, press the Menu button

4) When the TWRP "desktop" shows up, choose Boot Options, select an empty ROM slot, then (because it as empty) choose your partition size (2GB is typical, 1 for pure experimentation, 3 for going insane with app installs I guess), wait for that to finish, go back to main menu (press the onscreen Home button)

5) Choose Install, then find the ROM zip, add it, then add the kernel modules, then add the camera fix (so TWRP will flash them in that order) - if you have any signature failed issues you can disable that feature in the Advanced section of TWRP off the main menu, but as long as the file are solid and not corrupt you should be fine

6) When it's all done and all 3 zips have been flashed and it offers you the Reboot option on that screen, do it

7) The reboot should show "Safestrap Enabled" and it'll boot into the "new" ROM, etc

Since it's brand new you should get right into the Wi-Fi during the Google account setup mess, if not then something is a bit fishy - I've done that 5 times now for testing purposes: the very first time it did work but no Wi-Fi/Bluetooth/etc because of the kernel modules issue, the second through fourth times were done with the kernel modules and no camera fix, the fifth time earlier today was done with the camera fix and everything works.

Yes I miss the HDR option with the camera and other options as well but I can deal with it for testing purposes. Obviously all I have to do is reboot and I'm right back into the stock ROM in about a minute so it's a non-issue given we DO have this ability to run some ROMs now whereas two days ago we were all quite stuck. :)

Hope this helps...
[Galaxy S 4 Active General] baldwyn:
As it turns out, I flashed MF3 kernel and I'm actually on MF2. What do I do now? How do I upgrade to MF3?
[Galaxy S 4 Active General] br0adband:
If you honestly have MF2 on the device - stock ROM is MF2 - then it's suggested (by me, maybe some other people but I am the one making this post so I'm on my own) that you do the actual OTA update to get MF3 on the device. It's up to you to do that, but at this point in time there's basically MF1 (the pre-release firmware that prevents people from doing updates to anything at this point so you really are stuck if you end up installing it - there's a one-click ODIN for that build, iirc) and MF3 (which is the latest official AT&T update).

Obviously the kernel modules have to match the build or ROM you're intending to use, so... if you want to "play with the big boys" so to speak you're going to have to upgrade to MF3 to get compatibility with MF3 ROMs, or pull the kernel modules from MF2 and package them into a flashable zip and just flash THOSE after installing the AOSP ROM (the only one we have right now).

tl;dr If you have MF2 as your stock ROM, you'll need to pull the kernel modules from it, package them into a flashable zip, and then use that in place of the MF3 kernel modules.

My suggestion stands, however: do the OTA update to MF3 and then reset the device at least once (factory reset), after that do what's required (geohot's active root - you'll need to install that again because it won't survive the OTA update from MF2 to MF3 but once MF3 is in place it'll stick, install Safestrap, etc).

I could be wrong on the active root thing from MF2 to MF3 so if I am it just means another minute or two to reinstall active root I suppose.

Good luck...
[Galaxy S 4 Active General] Devo7v:
I think it would be more beneficial for the community to pull the kernel modules from MF2 so that we always have it just in case. Unfortunately I'm not technically savvy enough to explain how to do it, but hopefully someone can step in and help out.
[Galaxy S 4 Active General] my-blue-snog-box:
[MENTION=3047491]Devo7v[/MENTION] are you on MF2?

---------- Post added at 06:19 PM ---------- Previous post was at 05:49 PM ----------

[MENTION=2479894]baldwyn[/MENTION] send me a Hangouts request (my-blue-snog-box) and I'll walk you through the process of getting me the modules. Then I'll create and upload a flashable zip for MF2 for everyone.
[Galaxy S 4 Active General] Devo7v:
Unfortunately I'm on MF3. I just assumed everybody was on either MF1 or MF3 so when I saw somebody was on MF2 I thought it would be beneficial to the rest of us to get as much off an MF2 device in the hopes that it could help development in some way. I doubt that it would have any real benefit over MF3, but at least if you have a zip file of the kernel modules for MF1, MF2, and MF3 we cover all users.
[Galaxy S 4 Active General] my-blue-snog-box:
It's my understanding that there are some users on MF2 who modded some stuff in /system and for whatever reason cannot revert the changes, and so the OTA update won't go through.
[Galaxy S 4 Active General] br0adband:
Pulling the files is easy, I did that the other day for MF3 with a single adb command shown to me by Hashcode. I installed Android Studio then dug into where the adb files are located, opened a command prompt from there and plugged in my GS4A with USB debugging enabled, ran:

adb devices

to make sure the device was visible then:

adb pull /system/lib/modules <target destination>

so for me the command was:

adb pull /system/lib/modules c:\modules

and that pulled them into the c:\modules directory.

Now as for packaging them into a flashable zip, I can't help there, still not my particular cup of tea doing that kind of stuff but I'm sure if you pull the MF2 files and post them here in an archive, someone - perhaps Hashcode himself if he has time - can repackage them into an flashable/installable zip, sure.
[Galaxy S 4 Active General] my-blue-snog-box:
I hate to quote myself...but if there is anyone else on MF2 who wants me to walk you through it, you can hit me up as well. I have some free time ATM where I could get it done, but I will be busy the next few days. I just don't wanna leave anyone hanging.
[Galaxy S 4 Active General] joshuadjohnson22:
Will mods for the Google edition work? I would like some tweaks on this thing
[Galaxy S 4 Active General] br0adband:
One would think so since when you're running the GE aka AOSP ROM (the only one we can get functional as of this moment that I know of) it's "the ROM" so, if it's a tweak or mod for the regular device (the Google Edition S4) it should - given some constraints - work for the GS4A running the port of that ROM, at least that's how I would say I understand it. I believe the AOSP port is taken from the Google Edition S4 sold from Google Play, I could be wrong there but I think that's where it came from.

Since when running Safestrap and some ROM from one of the ROM slots is completely separate from the stock ROM and won't touch it in any respects, can't hurt to do some experimentation I suppose. Tweak away... :p

I keep switching back to the stock MF3 build because I take pics at various times during the day and it's more convenient to just stay on the stock ROM at this point. I don't suspect we'll get full camera functionality anytime soon using the AOSP build, and I've yet to do some testing with Play marketplace apps for camera stuff as well, like some other potential HDR app but I think the HDR functionality simply doesn't work at all with the AOSP ROM as of yet.

But it's nice to be able to tinker, certainly. :D
[Galaxy S 4 Active General] joshuadjohnson22:
This is what I am thinking. If I brick the Google edition rom who cares I'll just reflash lol.
[Galaxy S 4 Active General] br0adband:
Well yeah, you'd need to reinstall the ROM using Safestrap into one of the slots, sure - I find it faster and easier to delete a slot then start over than doing the wipe process, but that's just me.

And definitely Safestrap is awesome for experimentation since it's a) not using the microSD card for anything (like older methods would to have an SD card version of a ROM running from it) and b) since we're shaving off partition space in the native internal storage it's going to be just as fast - or it should be - as the native stock ROM itself since they're on the same storage hardware.

Safestrap is seriously cool stuff, I'm damned glad I discovered it the other day and delved into it both feet first. SO... again, Hashcode, thanks. ;)
[Galaxy S 4 Active General] my-blue-snog-box:
What, specifically, were you thinking off trying? I don't mind being a guinea pig.
[Galaxy S 4 Active General] joshuadjohnson22:
Well I want % battery and transparent background and maybe the full sms app with customizations. I tried a few mods but I only could find the ones for 4.3 which of course made my status bar disappear. I now have a fresh install so I too can try anything that you other guys who don't want to mess up your rom want. Just post the link, it has to be for the Google edition and I'll flash away
[Galaxy S 4 Active General] my-blue-snog-box:
Here is the module fix for MF2: https://db.tt/m87mU1iM

I'll also post it in the dev thread.
[Galaxy S 4 Active General] br0adband:
Ok, that is a no-go on all fronts. Got the zip, checked it for errors (WinRAR test archive), copied it over, installed it and gapps (8-13-2013) and... nothing on the reboot. Immediately after the funky kid graphic for Safestrap it's just a black screen, no activity, no backlight, absolutely nada.

Tried pushing the MF3 kernel modules to it then rebooting, still nothing but black so, that ROM ain't gonna work for us presently, seems like we'll be somewhat "stuck" with the AOSP for now which does work and is somewhat snappy for sure.

Thanks for your efforts, LeJay, it is much appreciated. We'll get this sucker running 4.3 sooner or later. :D
[Galaxy S 4 Active General] joshuadjohnson22:
Quick reply and this battery mod will do for now. I tried a lot of mods lol as long as it is for the Google edition ROM and 4.2.2 it works so look in the unlocked, Verizon, att, and T-Mobile s4 development threads
[Galaxy S 4 Active General] my-blue-snog-box:
Can you link the battery mod?

Find me on Hangouts: my-blue-snog-box

If I helped you, please hit the "Thanks" button.
[Galaxy S 4 Active General] joshuadjohnson22:
I had a hard time finding you. Get it here

In theory these should work (although I have not tested them):

http://xdaforums.com/showthread.php?t=2342628

I am looking for a % battery and transparent status bar. I found a flash for each but each one takes over the other one.

I started a thread:

http://xdaforums.com/showthread.php?p=45785158#post45785158
[Galaxy S 4 Active General] wyvphone:
This works great and is shockingly easy to use for something that--I'm pretty sure--is fairly complicated. Thanks a bunch for your work. :D

I also tried out LeJay's CM10.2 ROM and it just dumps me to a black screen. adb logcat isn't even seeing a device (but that might be my computer) so my debugging is limited at the moment. AOSP with the camera fix works mostly well so far. (I am seeing a problem where, when connected to wifi, some apps using data just stop. It doesn't do that on cellular, just wifi. Might be a keep-alive state being wrong.)

(Oh, and don't be stupid like me and proceed to violate the first rule of SafeStrap: thou shalt not flash on top of the stock ROM. I did it accidentally but the computers don't care about accidents. Off to MF1 ODIN for me...)
[Galaxy S 4 Active General] pyro254750:
Flash the kernel module for your device (mf1, mf2, or mf3) and the WiFi problems will go away.
[Galaxy S 4 Active General] yankeesfan714:
How do you think we go about getting new Roms for the s4a? Just ask? I asked ptmr3 and he said he would consider a jedi rom for us but won't do a blind build and would need a s4a to test on.

GT-i9295(i537) running SafeStrap
[Galaxy S 4 Active General] my-blue-snog-box:
[MENTION=3571182]Tsaukpaetra[/MENTION], can you please add the module-fix zips to the OP?

MF1

MF2

Find me on Hangouts: my.blue.snog.box@gmail.com

If I helped you, please hit the "Thanks" button.
[Galaxy S 4 Active General] wyvphone:
I did that straight away, on first flash. Bluetooth works (NFC is flaky) so I'm assuming the (MF1, /sigh) kernel module pack took. A person in the AOSP discussion thread said to try turning off the wifi sleep policy, rebooting, and turning it back on as that worked on his or her Galaxy Nexus.
[Galaxy S 4 Active General] paleh0rse:
Simply brilliant app!!

/muchlove
[Galaxy S 4 Active General] Hashcode:
Downloads section has a new Safestrap version:

Safestrap-JFLTEATT-ACTIVE-3.6x-B09.apk

CHANGELOG:

No more wipe error on /cache

Reworded the /boot not found message as INFO

Boot partition should be protected in stock now. (In past versions, a boot.img file in a .zip being flashed to stock would overwrite the actual boot partition and force the use of ODIN to restore the stock boot partition).

3rd and 4th CPUs are reattached correctly after 2nd-init (this was reflected in lower benchmarks)

Installation scripts were debugged a bit. But still seeing some users not getting a clean uninstall. :/ I'll work on this more.

TWRP update to 2.6.3.0 (See change log here: http://www.teamw.in/project/twrp2). And if you like TWRP don't forget to let them know.

From a local build stand point, this update was HUGE for me. I redesigned how the recovery files are built in order to support / maintain more devices in a better manner. This portion was not reflected in the change log but hopefully helps keep the builds consistent across several devices in the same family (VZW, ATT, ATT-ACTIVE).

INSTRUCTIONS FOR UPGRADING

Boot to your stock ROM

Install the new APK via file manager

Make sure to agree to the warning about replacing the existing APK

Once you're in the new APK (you'll note 3.60 in the lower left corner), use the "Install Recovery" button.

That's it. Now you can reboot into recovery and go right back into your ROM slot.
[Galaxy S 4 Active General] greeneyez15o:
Quick question. If I hit the uninstall recovery I will go bak to stock recovery ? And no harm done from previous aosp I will have all my space bak ?
[Galaxy S 4 Active General] Hashcode:
Stock recovery is still there.

You should probably delete the rom-slots before uninstalling.
[Galaxy S 4 Active General] trikar21b:
I just want to double check before I go and use this. I have the S4 (non-active) SGH-I337. This method will work on that as well, correct? Are the steps I follow the same? What about the MF3 modules from the active, can I use those as well on the I337 since it's virtually the same device minus the camera MP size?

[edit] Recognized this is in the wrong thread. Sorry!
[Galaxy S 4 Active General] br0adband:
If you have the actual regular Galaxy S4, there's a whole bunch of ROMs you can use for it. I'm pretty confident the Safestrap version posted here, in this thread, in this subforum for the S4 Active, is going to be somewhat different and could potentially brick your I337.

But I'm sure Hashcode will respond when he's got a chance - seems like we get an awful lot of people posting here in the GS4A subforum about the GS4. :D
[Galaxy S 4 Active General] Devo7v:
You're in the wrong forum. Please post in the AT&T forum to get answers specific to your device. Here's the tread you should post in http://xdaforums.com/showthread.php?t=2448925
[Galaxy S 4 Active General] trikar21b:
Thanks, I found the link in the OP right after I posted. The OP confused me for a second since it mentioned it I misread it as a combined thread.
[Galaxy S 4 Active General] joshuadjohnson22:
My battery life on the GE rom is so much better
[Galaxy S 4 Active General] pyro254750:
That's about what I'm getting as well which is an hour more screen on than I got on average on stock ROM.
[Galaxy S 4 Active General] baldwyn:
I've got 2 questions. First, how big should I make the ROM slot? Big enough for just the ROM itself or big enough to include all the apps I install while on that ROM?

And Secondly, I really liked the GE ROM, but missed holding the home key to pull up all my running apps. It just went to GNow. How can I do this, or will the 4.3 ROM have that function? I'm really stoked about trying that one out once we're able, anyway.

Thanks and all you guys are awesome!
[Galaxy S 4 Active General] Diablo2424:
You need to make the rom slot big enough for the ROM and any data store in /data so your installed apks as well. I had made mine 1gb originally and ran out of room.. Had to delete and recreate it as 2gb then reinstall the ROM

As for the recent apps, you can access them by double clicking the home button... Holding it goes to gnow for me as well on the GE ROM.
[Galaxy S 4 Active General] androidbitten:
Found what might be a bug with the speakerphone: If you place a call, then choose speakerphone, the other caller does not hear the audio. Once you toggle off speakerphone - all is back to normal. I might be missing something as well...
[Galaxy S 4 Active General] Diablo2424:
I too just noticed this yesterday, once on Speakerphone the microphone no longer works. If you switch back to handset or bluetooth it works.
[Galaxy S 4 Active General] joshuadjohnson22:
haha i also meant to post this bug a few days ago but never got around to doing it. I cracked out my BT headset because of it. I am shocked that this is the only bug I have seen so far
[Galaxy S 4 Active General] Diablo2424:
That's the only bug in the ROM I've noticed so far... but since I updated my SafeStrap, I noticed that I can no longer perform a backup of my rom-slot1 :(. I just get an error stating that TWRP cannot create a backup folder.

EDIT: I found another bug in this ROM... when connected to a PC and chosen as MTP - the device never shows on the PC, I tried this on a Windows 7 x32 and Win 7 x64, as well as Ubuntu PC. The phone never showed on any of them.
[Galaxy S 4 Active General] my-blue-snog-box:
A temporary workaround for the backup thing: download OBackup. I have backups automated through Tasker with OBackup. You don't even have to boot into recovery :)

_____________________

Find me on Hangouts

If I helped you, please hit the "Thanks" button.
[Galaxy S 4 Active General] Diablo2424:
Awesome, thanks for the tip on that app, I love it.

It still doesn't work though, I'm still getting permission errors... now that I recall, when I had an issue with some mods I tried installing (inverted GApps - see the thread in the Apps & Themes section), I attempted doing a "Fix Permissions" in TWRP. Maybe that is causing all of these permission issues. :(, if so, I wonder how to fix it.
[Galaxy S 4 Active General] my-blue-snog-box:
That just reminded me; a few days ago I tried "Fix Permissions" and my phone would freeze up whenever I made a call.

_____________________

Find me on Hangouts

If I helped you, please hit the "Thanks" button.
[Galaxy S 4 Active General] Hashcode:
After trying to back up your rom slot (and getting the error) you can pull the recovery.log by going to Advanced -> Copy log to SD

The file is called "recovery.log" It should a better description of the error near the end.

Sent from VZW S4
[Galaxy S 4 Active General] Diablo2424:
Cool, thanks.

I have quoted my recovery.log file below - still doesn't look like it gives me any more info than I got in the recovery.

:confused:
[Galaxy S 4 Active General] androidbitten:
Another oddity. Exported SMS/MMS messages to XML via Titanium and imported into asop Rom - worked fine. Exported Call log to XML then into asop rom - phone app would fail, can't remember exact error - 'unfortunately contact application failed' - something along those lines. I found a way around it by going through contacts first? I moved passed it by reflashing rom slot to continue testing.
[Galaxy S 4 Active General] killkillkill:
That isn't at all surprising. How about just syncing back up with your google account? That's what its there for.
[Galaxy S 4 Active General] popfan:
It is using a different dialer than the Samsung rom, so it will always fail.
[Galaxy S 4 Active General] androidbitten:
[MENTION=3564768]popfan[/MENTION] - makes sense, thanks [MENTION=5224889]killkillkill[/MENTION] - call and sms log are not syncing back (might be a setup issue on my end)
[Galaxy S 4 Active General] androidbitten:
Battery app quits after 20+/- second - closes
[Galaxy S 4 Active General] ShimaMiku:
[MENTION=4243514]Hashcode[/MENTION] Please forgive my ignorance on this, but is there a reason we cannot install the experimental CM 10.2 build on our i537 versions with SS?

I'm a little confused because the AOSP build was also created i9295 as is the CM build, but I haven't seen anyone successfully install it on SS.

Is that because it writes it's own recovery? If so, is there a way to prevent it from doing so? I wish I was a developer to help in this matter, but I never learned how to actually program/code.