Search results

Not looking good, none of the methods I've tried so far have even given me a boot animation :(

I'm taking a look at what's available. So far the most straightforward upgrade methods haven't worked despite the newer kernel. I'm now trying to rebuild the rom from scratch, so don't be surprised if the upgrade requires a factory reset. There's no telling that this'll even work at all with...

If it's final enough that the signature is there to allow it to be flashed to AT&T's locked bootloader without failing, then yes this would be the start. If anyone knows the answer to that let me know. Otherwise we have to keep waiting until release.

Yes, either that or adb shell with root access will work.

No worries :) However I'm not going to make custom ports because I wouldn't personally use/test them, and my S4 is no longer a daily driver. That being said I do enjoy hacking on this ROM in my free time, so once we have a working L kernel for this phone I'll do what I can to port L GPE over if...

Unfortunately that appears to be wishful thinking for now. I tested it and it looks like we can't boot lollipop with a KitKat kernel :(

I don't know when the samsung gpe lollipop release will ship. As soon as the official gpe s4 build shows up from Samsung, then I'll look into making it work with safestrap.

The code portions are typed in the terminal as root (su.) The rest is done in the GUI as described.

Last night I made some progress on wifi tethering. I now know the commands to make it work, but I haven't figured out an easy way to implement the fix for everyone yet. 1. Toggle Wifi off. 2. # rmmod dhd; insmod /system/lib/modules/dhd.ko "firmware_path=/system/etc/wifi/bcmdhd_apsta.bin...

GPS works for me on NB1.

TouchWiz ROMs have been known to cheat on benchmarks, so it's possible that's what you're seeing. For the vibrations I'd make sure that SELinux is set to permissive, but aside from that I'm not sure.

So I just gave this another test. On first connection it failed because it was having trouble finding files related to wpa_supplicant, which is interesting and may be related to internal wifi tethering not working. After setting skip wpa_supplicant, it successfully started broadcasting as an...

Hmm, I thought I tried that one to no avail. I'll give it another test.

Possibly. I'm not sure if a backup from safestrap will fully remove safestrap and clean everything up properly, as I've never tried it. I'd try the backup from safestrap and if you still have the custom logo or the safestrap startup splash after the flash and factory reset, then you need to go...

That'll mostly do the trick. If you want complete stock you should flash the stock AT&T (or VZW) image from ODIN, then do a factory reset after that. Then the Samsung custom boot logo should be removed.

Power Toggles may do what you're looking for. As far as I know there isn't any Xposed module to do this.

I haven't seen this issue, when I use enough data I see the appropriate warnings from Android, however I have unlimited data so I don't track it very closely, but it more or less mirrored what I saw on my Nexus 4. One thing to note is to make sure you have it start/end on the same day as your...

There have been other users in this thread that have had success getting cellular functionality on Verizon's S4. You may want to see here: http://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-install-aosp-s4-google-edition-t2817708/post54181536

You can get around the multi-boot process by turning off wifi or putting the phone into airplane mode before shutting down or rebooting. AOSP/GPE roms (like this one) and TW roms use a completely different device exposed by the kernel for usb transfer. This would be a quick fix if we could...

You may want to try the AOSP camera found in the fdroid repos to see if it works any better/differently.

Everything that I've tried involving usb debugging has worked for me so far (adb, etc.) The only usb method that's known to be broken is mtp.

That's strange. When you flash the 4.4.3 zip, the build.prop that gets installed includes ro.product.device as jgedlte, so unless the build.prop was modified in some way to change or remove this line, you shouldn't be failing there.

The next time I have to repackage this rom I'll make sure to include it, unless we're dealing with L at that point :P

You probably still have root but not the SuperSU app. Reinstall SuperSU from the play store.

Correct. That's why there are two separate zip files, one safestrap and one standard, for the Eclipse rom.

If you need to use a safestrap rom you cannot flash any kernel without bricking. So no you can't.

Nothing in particular, aside from running the latest version of android with its security and bug fixes.

Interesting. I tried this a while back (4.4.2) and all it did was change the error code that mtpserver would give, and still wouldn't mount the storage via mtp. If you actually got the storage to mount and copy a file that's a decent improvement. It could also be that I'm on the NB1 kernel.

Usually this means that the file has been modified or removed by something since the original flash of the 4.4.3 rom. You can pull the original debuggerd from the 4.4.3 zip, or reflash the 4.4.3 rom and try again.

I wouldn't worry about Google Earth. It wasn't patched in the 4.4.4 OTA and I'll remove it going forward to avoid this crash.

It's crashing on launch for me, but I've never tried using it on this phone before. Is this a new problem with 4.4.4, or has it always had this problem?

Unfortunately no new updates on wifi tethering or mtp. MTP will probably require a clever hack that I'm not even sure would actually work, so the likelihood of that getting fixed is low. I'd really like wifi tethering working as much as anyone else, but I'm not sure what's up with it...

Ah that would explain it. This update requires the original apps installed from the 4.4.3 rom to be present. If it tries to update one and it is changed or missing, then it will fail with the "unexpected contents" error on that file.

Strange, mine didn't error on that one. Are you using the stock drive.apk from the 4.4.3 rom?

What error are you seeing? Is it failing due to a file having unexpected contents?

Yes, you'll want to be on 4.4.3 to start. Then you'll download the gpe_444_update.zip and flash it in safestrap, followed by flashing the latest SuperSU. I don't think you need to flash the kernel modules again, but it doesn't hurt and only takes two seconds.

Sorry about the delay, I had to do quite a bit of hacking on the OTA to make it work with this rom. Note that you will have to reflash supersu after the update and possibly kernel modules to be safe. If the system update downloaded notification is still showing, a second reboot should fix that...

So I've taken a look at the OTA, and it includes a boot.img kernel image and an updated recovery image. If the recovery were even able to install this properly, it would probably hose the kernel and trip Knox, in the worse case scenario.

Google's updates generally don't install automatically, but it will keep bugging you. I'd avoid it as it may have components that'll break things. I'll work on getting it integrated.

Yes, 4.4.3 should work everywhere the 4.4.2 version of this ROM does. I left both up just in case people wanted the older one for whatever reason.

I have no plans to do that. My goal was to get the stock Samsung GPE image working as much as possible. You're welcome to add them yourself though.

USB debugging works, you just have to enable it by going to developer options (which is shown after tapping the build number 7 times.)

Good catch, apparently setting SELinux to permissive is good enough and the encryption disabler isn't necessary. I've updated the main post to reflect.

Wow. Setting SELinux to permissive fixed Chrome too! :D Yes soft keys work, as does disabling the capacitive buttons. See this thread for instructions: http://forum.xda-developers.com/showthread.php?t=2032117. You can disable the capacitive button lights with GravityBox.

SELinux did the trick. Paid apps now work :D

I tried this a couple weeks ago but it didn't work. However, I didn't realize the SELinux bit, so I'll give it another shot. Thanks.

I just verified that USB internet tethering does work. You need the Samsung USB drivers installed if you're running Windows, but I just successfully tested it on Windows 8.1.

I haven't seen error 492, so you may be running into a different issue entirely. What happens for me is when a paid app tries to install it gets stuck at installing indefinitely, and will hold other apps in the queue. You must then hit stop in the My Apps installing section and only select free...

Yeah, I didn't think that'd work. I'm pretty sure the reason paid apps aren't installing is Google's security mechanism for paid app data. For each paid app, Google remounts its directory from some unknown location to /mnt/asec/com.app.name via dm block devices. This usually happens...

You'll want to flash the NB1KernelModules and SuperSU after flashing the ROM and before reboot. Other than that it looks good. I tried testing a USB mass storage enabler but it didn't work for me; YMMV.