yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] ecsnead69:
Ok, I have tried to clean install three times, each with a new download. Each time fails install. I get an error message saying that some symlinks failed and that an unexpected updater script in zip??
[Verizon Samsung Galaxy S 4] hlxanthus:
This is caused by either a faulty or obscured proximity sensor. Try using canned air to blow out the speaker grill area. I have this same issue occasionally.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] josephpalozzi:
This plagued me for quite a while until I figured out it was my version of TWRP. It only wanted to install under 2.5.0.2, not under any of the 2.6's. I'm not sure if it will install under 2.7.0.1. Good luck
[Verizon Samsung Galaxy S 4] cjkacz:
Newest twrp works also

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] s44:
Still have left-ear-only call sounds over headphones. No big, though... getting the boot freeze fixed (have other projects really done this?) would be much more important.
[Verizon Samsung Galaxy S 4] Aspesi4:
I have the same problem with the dialer. It takes a while for me to get the screen back on. I need to press the power button a few times until it finally is back. The issue is I can't hang up in time! So I'm now leaving realllyyy long messages by the time the screen comes back to end the call!
[Verizon Samsung Galaxy S 4] wesley404:
I've never been able to get Octo Kat on my GS4. I read above that it "possibly" wasn't compatible with TWRP 2.6.3.1, but that it was with 2.7.0.1...so I flashed the recovery first, made a backup and then tried to flash the ROM and Oct Gapps AOSP. I'm still getting the symlink failed binary updater error no matter which version of TWRP I'm using. Is there some way to resolve this, I really would like to use the ROM and see what it has to offer as an AOSP based ROM.

Thanks.
[Verizon Samsung Galaxy S 4] MassStash:
Really hope we get it figured out what isn't allowing twrp to flash this rom for some people. I also cannot flash this rom with my s3 or s4 with 2.6.3.1 or 2.7.0.x. Other roms seem to flashed fine with 2.7. So to flash this, I have to be on philz recovery. Some people have downgraded to twrp 2.5.x.x and say it works tho

~Jflteusc on OctOS

KToonsez Kernel

1.998 Max ¦ 189 Min ¦ 702 Screen Off

Ktoonsified v5 Setup
[Verizon Samsung Galaxy S 4] urrgevo:
I have a uscc s4 and have had the same problem. Do a battery pull and try again, it will flash after a few tries on 2.7.0.1. Wish I could downgrade but I don't have a pc
[Verizon Samsung Galaxy S 4] MassStash:
Ahhhh, that's interesting. Have to try that. If you wanna downgrade, just download a twrp you want and do this is terminal on phone

dd if=/storage/sdcard0/Download/recoveryfilename.img of=/dev/block/mmcblk0p21

Either retype the the recoveryfilename.img part, or rename the recovery you downloaded to that

~Jflteusc on OctOS

KToonsez Kernel

1.998 Max ¦ 189 Min ¦ 702 Screen Off

Ktoonsified v5 Setup
[Verizon Samsung Galaxy S 4] urrgevo:
I may try that when I have to flash again. Problem is finding the old recovery image lol
[Verizon Samsung Galaxy S 4] wesley404:
I'm not sure which version of twrp you have had success with, but 2.7.0.1 is still failing. Is the only sure way to get this working to downgrade to TWRP 2.5?

---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------

Past recovery images are on TeamWin's website under your device's name, should go all the way back to TWRP 2.5, I just looked it up this morning when downloading 2.7.0.1, they are all still there.
[Verizon Samsung Galaxy S 4] s44:
Not sure why y'all call 2.5.0.2 a "downgrade". It's been flawless since posted, and there's never been a reason to get off of it.
[Verizon Samsung Galaxy S 4] wesley404:
Downgrade shouldn't be taken as though it's "flawed", but as improvements, bug fixes and the like have been developed and newer versions rolled out, going back to a previous version and losing those value-added elements of newer versions can be viewed as a downgrade.
[Verizon Samsung Galaxy S 4] hlxanthus:
I occasionally get failed installs on twrp 2.7.0.1 but I just reboot boot loader via twrp menu and it always goes the second time. Not sure what the issue is there but hope this helps

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] red3razor:
www.teamoctos.com

Unified builds now available on our website for the S4. Current build now has new Tentacles built in. Settings/About Phone/tap on "OctOS build date." Now with Active Display, Lockskreen notifications/blur/shortcuts, battery + other statusbar mods. Many more tinker tweaks, check it out!

AOSP + goodies, mmmmmmmm.
[Verizon Samsung Galaxy S 4] wesley404:
I can't get the new unified build to flash on TWRP 2.7.0.1. I tried rebooting the recovery and battery pull as suggested, but I keep getting failed error message almost instantly once I swipe to install.
[Verizon Samsung Galaxy S 4] cjkacz:
I'm using that version of twrp with no problems. The only other thing I can recommend is to try using 2.5.0.2

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] wesley404:
Okay. So if it fails, just battery pull, reboot into recovery and try again? 2.5 has no known issues? I will give that a try now and see if I'm successful with either. Thanks
[Verizon Samsung Galaxy S 4] saul1991:
Unified build fails to flash on twrp I've tried 2.7.0.1 and 2.5.0.2
[Verizon Samsung Galaxy S 4] cjkacz:
When flashing try unchecking "check md5 sum". Mine us unchecked

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] saul1991:
Still fails to flash, this has also happened with other builds....
[Verizon Samsung Galaxy S 4] bthorne79:
After wipe reboot twrp recovery and flash
[Verizon Samsung Galaxy S 4] cjkacz:
Other users are reporting this works

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] Treken:
Happened w/ other OctOS builds? Also, it would be extremely important for you to write down what error message you're getting upon failed to flash. This would help us know what direction to take to fix your issue.
[Verizon Samsung Galaxy S 4] hlxanthus:
. . . and give a recovery log. Twrp has an option to copy it to sd

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] wesley404:
I just tried wiping, rebooting recovery and installing, still got failed error message. Should I post the log file here?
[Verizon Samsung Galaxy S 4] Treken:
Either that or if it's very large then pastebin and link it.

Edit: [MENTION=2903268]wesley404[/MENTION] You shouldn't create a private pastebin for logs. vvvv
[Verizon Samsung Galaxy S 4] wesley404:
http://pastebin.com/pxU1n4Ru

---------- Post added at 07:05 PM ---------- Previous post was at 07:04 PM ----------

[/COLOR]

Sorry, didn't realize it would be that big, let me figure out how to do pastebin and edit that post since it's so large.
[Verizon Samsung Galaxy S 4] hlxanthus:
Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] wesley404:
Sorry about that, I have updated it and made it public.

http://pastebin.com/pxU1n4Ru
[Verizon Samsung Galaxy S 4] s44:
Huh. Just had two hot boots in 10 minutes. Wonder what's going on.
[Verizon Samsung Galaxy S 4] Treken:
Can you be a little more specific? What build are you on... any custom apps installed.... any custom kernels.... any tweaks applied.... what were you doing when it happened.... did you get a log.... what gapps are you on? The more info we have the easier it is to diagnose the issue.
[Verizon Samsung Galaxy S 4] s44:
3/13, no tweaks, GPE GApps package from that era, no log because I wan't expecting either. First was just browsing reddit is fun, the other just looking at OctOS OTA to see if I'd missed any recent updates.
[Verizon Samsung Galaxy S 4] Treken:
Go to our site and flash the unified build. It has the new Tentacles anyway. Then let us know how it fairs for you. ;)
[Verizon Samsung Galaxy S 4] wesley404:
Is the unified ROM flashing on TWRP 2.7.0.1 now since I posted my recovery log? Is there a better way for me to get it to flash than wipe, reboot recovery and flash?
[Verizon Samsung Galaxy S 4] hlxanthus:
That is how I have been doing it lately. Do all my wipes, reboot recovery and flash ROM+gapps then boot system.
[Verizon Samsung Galaxy S 4] wesley404:
Is there a setting for capacitive button lights to be turned off?
[Verizon Samsung Galaxy S 4] Treken:
Not presently but it's in the works.
[Verizon Samsung Galaxy S 4] s44:
Clean flashed, TiBued back, everything flawless so far. We'll see -- I also had a random power-off last night before this latest flash. Very odd, since I hadn't had issues with 3/13 for the first few weeks... whatever.

Btw, are you going to push the unified build into the VZ OctOTA system? Don't think everyone follows these threads/G+/whatnot.
[Verizon Samsung Galaxy S 4] SamXp:
Been having several issues, and can't get a logcat since I don't know how to replicate them.

1) Bluetooth doesn't reconnect reliably. This is both with my car and Belkin BT adapter. A reboot fixes it every time.

2) After disconnecting from Bluetooth, audio stops working through the speakers. (Missed my wake up alarm because of it!). Once again, a reboot fixes it.

3) Random reboots (can't detect a trend - could be browsing on Chrome, Facebook, Youtube).

4) When I do reboot, it will often hang at the Samsung Galaxy S4 screen. I'll have to do a battery pull to reboot again.

5) Google Voice to text crashing when using Swiftkey.

No custom kernel or processor tweaks. Such a great ROM otherwise!
[Verizon Samsung Galaxy S 4] Treken:
What's the build date and was it unified or a vzw build? Also, pay attention when it happens to see what app may be linked to the issue, it will help us know where to start.
[Verizon Samsung Galaxy S 4] s44:
I'm having issues with Bluetooth as well on the unified build: it won't reconnect to my K810 keyboard. Worked fine on 3/13.
[Verizon Samsung Galaxy S 4] s44:
Any reason why the tether settings don't seem to include band specification any more? Pretty sure 3/13 did.
[Verizon Samsung Galaxy S 4] s44:
Another hot boot. Just listening to music and reading on Pulse. Will try reflashing with stock Dalvik tomorrow... Does that require reflashing anything else from the Aroma installer?
[Verizon Samsung Galaxy S 4] Treken:
We need specific information to address your issue. We have no clue where to start unless you provide a build date and version(unified/jfltevzw), also what gapps you're using and any apps you installed. What were you doing for each issue(that is...were you browsing, playing a game, checking email, etc). This sort of information is what we use to know where to start otherwise the issue cannot, and will not be addressed. For this reason we ask that you provide thorough and detailed information. A log is also something we need. Use syslog or some other logcat app. See OP for instructions on how to get a log.
[Verizon Samsung Galaxy S 4] s44:
I know this is the generic "not enough info" response you're giving, but c'mon man... I'm on the exact unified build you told me to flash, and which I've given updates on. I mentioned switching to the std dalvik so obviously I'm on the enhanced one. And you didn't even answer the questions that require no additional information at all: what happened to tether band selection, does switching from Qualcomm dalvik to the original require anything beyond clearing the dalvik cache, and... how come no one has acknowledged the headphone-call-on-left-side-only bug I mentioned months ago that still persists through the unified build?

Eh, whatever. I'll log if I can get the hot booting to reproduce itself...
[Verizon Samsung Galaxy S 4] Treken:
I wasn't aware of a "generic response". Not sure about tether band selection because I don't use it and never noticed it before, if it's something that was taken out then I'm unaware of it. A suggestion is to

not

use the dalvik gapps if you're already experiencing problems as this may lead to creating more problems. Nothing extra is required to run unified builds aside from gapps. The left headphone audio bug you talk about hasn't been mentioned by anyone else, maybe someone else can try to reproduce this issue. A log is a must. If that doesn't answer any of your questions then perhaps one of the other team members can help you out. I stay bogged down in code most of the time and the fact that I'm even responding to your reply is a rarity.
[Verizon Samsung Galaxy S 4] theHoleK:
Same issues here. My build is jfltespr 4/8 running stock kernel and Gapps modular mini 3/21(a).

I've also been unable to record videos in the stock camera app or Snapchat for several weeks/builds.

Also, the last time I reported these issues I was told it's Google's fault/known AOSP issue, but the links provided described other issues with BT pairing that I am not experiencing.

Log is being sent now!

---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------

Team OctOS,

Please spend a little more time on resolving these issues that are annoying us so much. While I appreciate the fact that you all are volunteering your time in creating these builds, I see more time being spent making the OctOS custom settings menu and a unified installer instead of fixing bugs. The first time I sent a logcat about the BT pairing issue was 12/28; the video recording issue was reported with a log on 3/18. I am respectfully requesting a shift of your focus on the problems being reported instead of cosmetics or an easier installer.
[Verizon Samsung Galaxy S 4] Dubbsy:
The big picture is completely being missed here.

It's not that issues are being ignored its that working on the old setup is completely fruitless. Our hidden menu was rebuilt from the ground up. It's taken this long to get back to a state at which we can release files again.

We haven't shifted nor will shift focus on each build. We still build out each jf separately and jf unified. We have two entirely separate branches.

We do our best to fix things that we can. We look for fixes for similar issues. We implement fixes. Some work. Some don't. We do look at the logs, and many times we've been able to implement fixes in the next updates or are a part of a much bigger update later.

My goal for a while was not maintaining or fixing anything. It was prepping to add many more devices to our supported section. Kevin, our main coder, was busy building from the ground up. And stopping that progress is stupid. Bthorne, Gromm, and cjkacz have been building the jf and d2 while we work on the other things.

Once the new layout is taken care of, the entire focus of the team will be device additions and bug fixes.

We won't deviate from this goal.
[Verizon Samsung Galaxy S 4] theHoleK:
What happened to Advanced Settings? It used to be under Settings/Device, then it was in the OctOS settings menu under Device tunables, and now I can't find it anywhere. I like to calibrate my gyroscope and enable extra gain in voice calls.
[Verizon Samsung Galaxy S 4] Treken:
It's been added back and should be in the latest unified build. If it's not then a new build will be out tomorrow that should also have some minor fixes
[Verizon Samsung Galaxy S 4] Stryke_the_Orc:
Thread cleaned.

Unnecessary comments are just that, unnecessary.

Thank you.
[Verizon Samsung Galaxy S 4] Stryke_the_Orc:
Thread cleaned, again...
[Verizon Samsung Galaxy S 4] cjkacz:
For those of you who prefer the individual builds (whatever your reason may be) I have pushed builds to our website. They now contain all the features of the unified.

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] theHoleK:
Where?
[Verizon Samsung Galaxy S 4] cjkacz:
Www.teamoctos.com at top of screen and under "Devices Supported"

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] theHoleK:
The post I quoted was posted by you on the 10th. The latest jfltespr is the 4/8 build. That's why I'm confused.
[Verizon Samsung Galaxy S 4] cjkacz:
I had to wipe my build directory clean so all builds took a few hours each. It took me 2 days to build all the S4 devices out

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] s44:
Welp, since flashing back to stock Dalvik I've had no hot boots and (amazingly -- knock on wood) no power-on freezes. Excellent.
[Verizon Samsung Galaxy S 4] Treken:
Good to hear! :)

Dubbsy has been out for a bit due to some personal things he's taking care of. He'll be around before too long.
[Verizon Samsung Galaxy S 4] cjkacz:
JFLTE build is up on site. Not alot of noticeable changes from prior build. AOSP updates and under the hood stuff...﻿

http://www.teamoctos.com/supported-devices/samsung-galaxy-s4/octos-unified-jflte/﻿

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] Treken:
Our unified builds have passed their evaluation period and deemed stable. We have merged our unified branch in to our mainstream branch. We will no longer work on jf individual carier builds.
[Verizon Samsung Galaxy S 4] Bait-Fish:
The install instructions listed in the OP say to flash GApps. There are no GApps files at the linked copy.com page. Did the location change? I didn't see anything regarding this on the team's website either.
[Verizon Samsung Galaxy S 4] cjkacz:
Our apps have not been updated . I would recommend flashing another set. I use PA myself.

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] Treken:
Just a heads up but some folks are reporting issues with newest PA Gapps. You can use ours since they will auto update once you're booted up. ;)
[Verizon Samsung Galaxy S 4] s44:
Only ROM issue I've been having is the status bar clock disappearing and not coming back. Not running any Xposed or anything, and turned off the clock mod in Nova.
[Verizon Samsung Galaxy S 4] Treken:
So you're using nova launcher?
[Verizon Samsung Galaxy S 4] s44:
Yep. It isn't trying to mess with the status bar any more though (no SU request/toast). I believe when I toggle the clock off and on in Tentacles it works until I enter the app switcher. Need to confirm that though.

edit - never mind, may be Active Notifications
[Verizon Samsung Galaxy S 4] scarmon25:
So if I understand this right. I can choose to have a pure vanilla version of android through the Aroma installer? When I say vanilla I mean like your other ROM you did. No mods or anything other then android.
[Verizon Samsung Galaxy S 4] hlxanthus:
That is correct. You can have as much or as little as you want. Your choice. Everything is preset to mimic a GE rom, so change what you want.
[Verizon Samsung Galaxy S 4] scarmon25:
Awesome. Once the update that fixes shadow gun is released I definitely have to try this out.
[Verizon Samsung Galaxy S 4] Highway 55:
This is running great on Sprint S4. Data seems to be functioning fine, and even MMS is working as well :o Good job guys!
[Verizon Samsung Galaxy S 4] Dubbsy:
** besides the live wallpapers, the boot animation, the lock screen handle, and the puss-beans.

The regular live wallpapers are included also in case octo papers aren't desired. And there is a revert for the handle. As far as I'm concerned end users can deal with it on the boot animation and puss-beans...

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] mlin:
Thanks guys for the responses. Again, I wasn't trying to offend I just wanted to understand and now that you've explained it I think it's a beautiful idea. I'm going to dive in now.
[Verizon Samsung Galaxy S 4] daniel4653:
Yeah but data does seem a bit slower (usually happens with aosp). Hitting about 200-300 kbps download. Normally have 650-800kbps in the exact same area with touchwiz.
[Verizon Samsung Galaxy S 4] SimonTuffGuy:
Very nice... backed up and flashed the newest version and did a semi-standard install. I like the pure-Google feel similar to my old Nexus... but it feels weird from getting accustomed to TW. Will have to play around with it for a few days and see what I like.

Any word on Google Wallet and Tap to Pay? I know there is a patched version that seems to enable it, as it doesn't look to be enabled in the version that comes installed.

Even though I had checked the option to restore my applications during setup, nothing came back. Maybe a quirk thinking it's a different device from TW to AOSP... but a bit of a pain to reinstall everything again. Did I miss something?
[Verizon Samsung Galaxy S 4] Dubbsy:
That option is provided by Google and often causes issues specifically wakelocks. I never suggest backing up apps like that when there are plenty legit good ways to do it... that never mess up.

And the Google backup will only transfer things that it knows are compatible with your file system. You also have to have had your Google backup sync enabled on your prior ROM in order for it to work at all.

I'll work on wallet when other stuff is done. It's the latest wallet app from play store. And it's a carrier specific thing. There are a few ways around it though.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] :
I have been waiting for this. Im just upset that I just now saw that it has been posted... grrr I am always late to the game haha...

Thanks guys!

Now only if my download speed wasn't super slow:silly:
[Verizon Samsung Galaxy S 4] saul1991:
Nice!! Are these nightlys??
[Verizon Samsung Galaxy S 4] Dubbsy:
Sometimes. But normally it's whenever we get something done and commit it to the aroma. I could set the buildbot up but we haven't gotten to the stage where we can automate building all carriers and options and arrange them in aroma yet.

We are adding USC next along with opengl fixes. I believe tomorrow I'm running builds of every carrier. treken does active development only on Verizon with an occasional sprint build so grommish can test because he's working off a smaller SSD in his local box. I build on the server and I keep all the devices setup so my builds take 15 minutes instead of an hour.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] royredman:
Ok. Just to make sure, this will work for the Verizon Galaxy S4, correct?

Also, does this mean that I would be able to install Samsung system apps (like the ir blaster and Samsung voice recording app) on a also based ROM?
[Verizon Samsung Galaxy S 4] nolimit88:
hi anyone have same problem with me ?

my camera not working
[Verizon Samsung Galaxy S 4] trillonometry:
I'm getting an error trying to bluetooth sync my fitbit with bluetooth 4.0... Guess that's not any big priority to fix?
[Verizon Samsung Galaxy S 4] nolimit88:
problem solved just restart 2 times and camera working :good:
[Verizon Samsung Galaxy S 4] hlxanthus:
As of right no there are no tw dependant apps that will work on this ROM. WatchOn is included in the aroma package, and there might be other Samsung apps that aren't dependant on the tw framework that might work. But we have not specifically added any others.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Cruiserdude:
Is there anything in the GPe source that could possibly allow the TW camera to be ported here? Obviously GE was TW and this is AOSP, but I know there's still some TW in 4.3 GPe, and I don't know what all the camera relies on.

Also, any idea what's going on with Photosphere? I notice it's not available in either of the cameras, and I no longer see Photospheres I've already taken in the gallery.

Other than that, great rom on my end, the best really! Definitely worth the wait!
[Verizon Samsung Galaxy S 4] collindv:
I don't use a lock screen on my phone (I have an s-view cover). On previous Roms I have used, pressing the home button with the screen off would simply wake the phone, now it seems to wake the phone and return to the home screen. Anyone else notice this or have a solution? Thanks!

Great ROM BTW! Just have to get used to the aosp base vs tw I think.
[Verizon Samsung Galaxy S 4] KennyG123:
Thread closed. Please join it in its new home in the Unified Development section here: http://xdaforums.com/showthread.php?t=2565948
[Verizon Samsung Galaxy S 4] gwallers:
I'm not having much luck with this rom and viper4android. Everytime I open viper it wants to install the drivers. I click the cortex a8 w/neon and it says reboot. I reboot and when I go back into viper says the same thing as it did the last time. Anyone know how I can fix this??