yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] revolt1:
shouldn't Nitro be doing the same thing
[Verizon Samsung Galaxy S 4] DaMadOne:
Not necessarily, apples and oranges. Much of his source comes from his own github, so the source code he is using is not the same as AOKP. Once I can verify with some people what it is that is causing it.. I can be pointed in the right direction hopefully. There is around 15GB worh of source for AOKP/Android once its all pulled to your computer. Im only real familiar with maybe %3 of it, and even then that percentage might be high lol. Im guessing its going to be somewhere in the hardware area, that houses a lot of the "drivers" and whatnot needed to operate the hardware. Knowing that nitros rom works with the camera I can do some comparing and see where he differs.

Just out of curiosity have you tried a recent CM build? under the hood AOKP shares A LOT of similarities and source with CM. I am wondering if they are having the same issue.

EDIT* nope.. cm does not have the video issue i just flashed it to try.. now to get it off my phone ASAP! haha =)

EDIT* CRAP! i made a whoopsie! and it had to error at the end of the compile too, why couldnt it have been at the beginning?! I fixed it and then just let it finish compiling just to make sure there was no moar fail in there.. but I dont like the idea of putting out a build that did not build completely clean. So I am starting the build completely over. If I happen to stay awake until its done then ill upload it and just post it here in this post and just update OP tomorrow. If not expect it when I get off work tomorrow.
[Verizon Samsung Galaxy S 4] DaMadOne:
Good news! I think i know whats causing it! Ill need to do some more testing to be sure, but I have a temp fix for ya!! grab the 9/29 build from HERE if you do not still have it. open the 9/29 build zip file... goto system/app and copy the Gallery2.apk in there to somewhere temporary like your desktop. Then open the latest build and replace the Gallery2.apk in it with the one you copied out of the 9/29 build. Flash your new "hybrid" zip. Video cam works!

Im pretty sure I know what new additions after 10/1 were made to it that broke it. So im on the right track! And in normal me fashion I was wayyy over thinking it :silly:

EDIT* Scratch that... flash THIS temp fix zip! Its just the Gallery2.apk from the 9/29 build.. so just flash it over your current install and reboot. It flashed for me no probs, but of course make a backup first just in case.

MD5 - 9a1640e68a599f5f1412c6bbb04f79bf
[Verizon Samsung Galaxy S 4] kvswim:
Will this workaround be included in the next build? Or will a real fix be included?
[Verizon Samsung Galaxy S 4] yakitori2:
video camera works fine in official 10-15 nightly. In official 10-12 nightly...the camcorder would work, but it would stop on its own randomly...and not save the video anywhere. They seemed to have fixed that issue as well in the 10-15 build.

Im pretty sure that a sync of the repo in the next smooth AOKP build will have all the things working as they are in the official one.

On another note. For some reason when I flash the Smooth version of AOKP...my 64 gb sdcard cant be read. Have no issues at all on the official one. Its been like that for the last 2 builds. Maybe something to look into.

:)
[Verizon Samsung Galaxy S 4] DaMadOne:
Yes the new build that I'm gonna post when I get home from work will have the 9/29 camera already in it as a workaround. I should be able to REALLY have it fixed by the next build.
[Verizon Samsung Galaxy S 4] apophis9283:
DaMadOne. They have commits up for active display to allow choosing of app notification. I was finally able to connect my desktop. Dont know how long its gonna last though.
[Verizon Samsung Galaxy S 4] DaMadOne:
So mixed reports on vidcam on the official 10/15.. revolt said it worked for him on 10/12 but was broken again on 10/15. Also since I dont have a 64gb sd card to do any tests with please get me a FULL logcat from phone on - homescreen. Also grab a last kmesg and dmesg as well. Please do this for both the official build that works, and with smoothaokp. thanks.

HERE is a great guide on how to do that. Its what im going to base my guide on when I get around to putting it in post #2
[Verizon Samsung Galaxy S 4] mcconvict:
OK..gonna flash the new nightly. See what's all going on there

---------- Post added at 09:27 PM ---------- Previous post was at 08:46 PM ----------

Camcorder still busted on dirty flash on 10/18 nightly.
[Verizon Samsung Galaxy S 4] DaMadOne:
Dirty flash, clean flash its not gonna matter, im 99% sure i know what the issues is. Im not 100% sure how to fix it and fix the reason it was committed.. but i can revert it just for my builds and pass on the info. Im uploading a new smoothaokp build now, it has the camera app from 9/29 in it so vid cam works for now.
[Verizon Samsung Galaxy S 4] mcconvict:
Camcorder I barely ever use so no big deal to me. That's the only issue I can find tho. Looking forward to the build
[Verizon Samsung Galaxy S 4] DaMadOne:
OP updated! 10/17. Has the video cam fix built in. Some updates to Active Display, most noteably the ability to exclude apps from being displayed with active display, which is something I have been especially waiting on. Also has the custom network stats color I have been working on. ENJOY!

EDIT* Approaching 30,000 views and 500 replies on this thread, I just want to thank the SmoothAOKP users for all their input and support! I owe all of you for keeping me on my toes and keeping me wanting to learn MOAR!
[Verizon Samsung Galaxy S 4] jova33:
Ok, I'm ready to jump back on AOKP now that I found this http://xdaforums.com/showthread.php?t=2447534

TW when I want a camera, AOKP when I want style.
[Verizon Samsung Galaxy S 4] DaMadOne:
hell yes jova! thanks for the heads up im gonna give this a go tomorrow after work. Im a device maintainer for CFX, since im a unicorn at heart this means I no longer have to backup/restore constantly when testing CFX stuff assuming it works!
[Verizon Samsung Galaxy S 4] mcconvict:
Well on dirty flash, camcorder freezes in 3-5 seconds and causes reboot
[Verizon Samsung Galaxy S 4] jacobk:
i still have no SD card mounted in the newest build :(
[Verizon Samsung Galaxy S 4] spotmark:
No wipe, no gripe. ;)
[Verizon Samsung Galaxy S 4] mcconvict:
Well if you reference back, he said clean or dirty it should work, which is why I specifically said dirty. It wasn't a gripe because I really am not concerned if the camcorder works. Was just letting him know it didn't work.
[Verizon Samsung Galaxy S 4] spotmark:
Don't get your panties in a bunch, I'm just giving you a hard time. Didn't you see the little winky thing?
[Verizon Samsung Galaxy S 4] scarmon25:
Just flashed this. Very nice. One little quirk. The vibration control doesn't work. Only thing I can find that has issues. Everything else works great. (Keep in mind I use snap camera so I can comment on videos)
[Verizon Samsung Galaxy S 4] mcconvict:
Even after a clean flash, video would record but wouldn't play
[Verizon Samsung Galaxy S 4] DaMadOne:
Video is recording fine for me, I did a little testing last night with the latest Gallery2 code and reverted the once commit i though was causing it and while it is working A LOT better its still not perfect, so i need to do some more testing.

As for the SD Card stuff I have asked that someone get me proper logs of both smoothaokp booting and the sd card not working as well as a log on official AOKP with the sd card working. I dont have a 64gb sd card here to test anything and I have no need for that kinda space on my phone so im not going to go out and buy one, so im relying on you guys for input. A few posts back I posted a link to a good tutorial on how to pull logs.

the vibration control in device options have been non functional. I posted a bug report on it a while back and BMc said he knew what the problem was, but it must have been put on his back burner because its still broke. Ill look into it a bit once I figure the cam out.
[Verizon Samsung Galaxy S 4] Nath5:
Has anyone been experiencing lots of force closes on the latest build. I clean flashed it and it is running really smoothly other than lots of force closes and reboots.
[Verizon Samsung Galaxy S 4] Jubakuba:
AFIK the kernel just doesn't support vibration control. I'm probably wrong though.

This is one of the reasons I wrote the minimum vibration in RC>Sound though...mako users wanted a more powerful vibrate on UI click.

(This is different than the kernel dependant option which adjusts motor speed)
[Verizon Samsung Galaxy S 4] mcconvict:
Quiet!
[Verizon Samsung Galaxy S 4] DaMadOne:
Little bit. AOKP did a bunch of merging this past weekend. I ran a new build last night. Seems good so far, assuming no issues arise today I'll sling it up for you guys tonight. Before anyone asks... Vid cam is still broken, I have not had the time to really dig into it yet, reverting a specific commit helps a lot but still not entirely, but its def a bandaid because the commit from 10/1 makes it just stop recording on any error. Even when it was "working" it threw the error it now stops on. I have flashed back older builds and the video cam has been very flaky on 4.3. It never really worked 100%. So really the whole reason it errors in the first place needs to be figured out.
[Verizon Samsung Galaxy S 4] mcconvict:
Sounds good. I'll wait to start recording my memoirs til its fixed. Wanted to ask if anyone tried the dual boot thing? I would've loved to try it, but my PC bit the dust..
[Verizon Samsung Galaxy S 4] fuzzylax:
Great ROM!! two questions, is it possible to have the home key from waking up the screen? and is it possible to have soft keys disabled
[Verizon Samsung Galaxy S 4] rrrrrrredbelly:
For the first part, to disable home button from waking phone.... Settings - display - wakeon button
[Verizon Samsung Galaxy S 4] jova33:
For the second part http://xdaforums.com/showthread.php?t=2347425
[Verizon Samsung Galaxy S 4] kvswim:
For the life of me, I can't get Viper4android working on this ROM. Any tips? I've even flashed the faux kernel with no success. I've uninstalled and reinstalled the app and driver numerous times, switched the sound fx, etc etc. I'm trying to use it with Google Music and Pandora.
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
V4a doesn't work on 4.3.1 roms without the proper commits in the build trust me is frustrating
[Verizon Samsung Galaxy S 4] kvswim:
Sigh. Can I request this then OP? I particularly like this ROM for its cleanliness. Not a huge fan of going back to TouchJizz just to get some beautiful audio.
[Verizon Samsung Galaxy S 4] spotmark:
Is anyone else getting this from the last couple of builds? When you press the home button, it interprets it as a long press, and brings up recents. I remember this afflicting the S3 as well.
[Verizon Samsung Galaxy S 4] DaMadOne:
can you link me the commits? or maybe where it is talked about in the viper thread?

ill take it under consideration. I have never used the viper audio before. I have seen it and know what you are talking about though.
[Verizon Samsung Galaxy S 4] DaMadOne:
I have not ran into this I dont think. I am running a build right now though, Team Kang has been on a merge spree the last few days and A LOT of stuff has been merged. Custom hardware keys being one of them, maybe that will have inadvertently fixed that weirdness.

My apologies for not being around much the last week. Ive had too much stuff going on and it has completely distracted me from android. Im working on getting back in the swing of things.
[Verizon Samsung Galaxy S 4] DaMadOne:
woah. all kinds of weird happening with the build I just spit out. something is not right! I guess ill wait til tomorrow to resync and try again.

HEADS UP to the faux kernel users. his latest 013 kernel will not work with AOKP for the time being, so stick with 012.

OK so i figured out what was going on with the build i did earlier, it actually woks with the stock kernel. Faux's 012 kernel does not play nice with the changes made to phone recently and causes phone to FC over and over again. His new 013 kernel works with the phone, but display was all screwed up. Since his kernel is "CM based" it takes into account some stuff CM has added to display recently that AOKP has not yet added. So I have added it to display as well as support for the stock kernel. Building now to test.

Another thing that is happening is that the network mode is not set to LTE by default, instead it defaults to 3g network. Once manually changed to LTE all is fine. Once I have display support fixed up ill try and figure that one out.
[Verizon Samsung Galaxy S 4] mcconvict:
I was thinking it might be the display changes because I flashed the 10-22 KT kernel and had all kinds of problems til I reverted back to 10-16. Ready to try the new build :)
[Verizon Samsung Galaxy S 4] DaMadOne:
Yeah it seems CM has done quite a bit of QCom updating. I went to build last night with the display stuff added in and I repo synced before I did and between my first build i did yesterday and the 2nd one CM merged a bunch of crap into telephony and the compile failed because of it. When I get home from work im gonna do a fresh sync and try again.. I have a feeling its going to be a bit bumpy for the next few days at least. I know I dont want to stick with the stock kernel..
[Verizon Samsung Galaxy S 4] mcconvict:
Nah stock kernel isn't optimal. But if it will boot the ROM up so I can try custom kernels, that'll do for me
[Verizon Samsung Galaxy S 4] DaMadOne:
cool ill put up the build so you can test out kernels! I can only assume that any kernels made after 10/18 i think it was will not work.. as most are CM based I imagine and they are using a new display mode. its uploading now ill shoot you a link when it's done. Our stock kernel is a bit behind CM so I merged in theirs to ours to bring it up to date, from reading through the commits it looks like they also fixed where it likes to hang at the boot splash screen from time to time. So that will be awesome! I did not do a full display-caf merge I just picked in the new display mode commit. Im building now to see if more will need to be picked in.. hopefully telephony does not error again.
[Verizon Samsung Galaxy S 4] mcconvict:
Awesome! Thanks a lot! You, sir, are the man
[Verizon Samsung Galaxy S 4] DaMadOne:
Sweet! So updated AOKP kernel works, and faux's new kernel now works right with the added commit to display-caf! Still defaulting to 3g instead of LTE network.. Im not so sure how to fix that though, looking into it now.
[Verizon Samsung Galaxy S 4] DaMadOne:
New build, stock kernel merged up to current CM source to play nice with the new(to us) display mode. I have put the stock kernel though its paces and seems to be good. You will need to use newer version of custom kernels. Faux's 013 is working for me. I have not been able to get it to do anything funky, but I am going to consider this experimental until a few of you guys test it. This has some active display fixes and Jubakuba's lockscreen theme color which is pretty darn sweet. Various fixes not yet merged. Dig in check it out. Ill update op once I get some feedback. Mainly wanting to know how other kernels are doing with it. Im sure Mcconvict will chime in soon ;) And yes, the video cam is still broken. I have not for the life of me been able to figure it out. I have not given up though. This build also has frameworks_av merged up from current cm source in an attempt to fix it... nope =/

md5 - 32973e052dabe5af8afe64d84f9dd539

smoothaokp_jfltevzw_jb-mr2_2013-10-25.zip
[Verizon Samsung Galaxy S 4] mcconvict:
Blazing along like a champ. Everything is clicking like clockwork
[Verizon Samsung Galaxy S 4] kvswim:
I found this http://vipersaudio.com/blog/?page_id=127 but it doesn't say anything about commits. I listened to music on a charter bus for almost three hours today and I sorely missed Viper. It would be nice if we could get this working.

Edit: github is here, I don't know if this helps

https://github.com/vipersaudio/viper4android_fx and the whole thread is here http://xdaforums.com/showthread.php?t=2191223
[Verizon Samsung Galaxy S 4] themikeyan:
Dirty Flashed the 10/25 build... running great so far, haven't testing active display much yet.

Mike
[Verizon Samsung Galaxy S 4] kvswim:
10/25 doesn't play well with ChronicKernel even with a clean flash.
[Verizon Samsung Galaxy S 4] themikeyan:
yeah, Faux and Ktoonz work fine for me though.

Mike
[Verizon Samsung Galaxy S 4] HoodBoogie:
Ktoonz Dodd some crazy stuff after boot for me. Looked like the screen was busted and solid green with grey text.
[Verizon Samsung Galaxy S 4] DaMadOne:
CM has made some changes to the display mode. thats why the weird green screens. Make sure you are using the newest kernels, It looks like ktoonz merged in the new display stuff to his kernel on the 22nd. Looks like Chronic kernel added the display commits on the 20th. So any of those kernels after that should display ok. Kernels that worked on the build before my latest WILL NOT WORK.
[Verizon Samsung Galaxy S 4] mcconvict:
Damn..45% remaining after 8 solid hours of rhapsody playing, texting, internet. Impressed
[Verizon Samsung Galaxy S 4] DaMadOne:
Now if only I could figure out this vid cam issue.. I am completely at a loss. I have tried so many things. I can stop it from stopping recording, But the main error still happens and it keeps going. Except for when that error happens (you can only see it in log) it will not save and it just discards the video. AAAAAHHH!

I also want to add that since bringing up the stock kernel and a few other things I have not run into Samsung boot screen hangs either. I was testing some things last night and prob rebooted/flashed 20 times and all was well. Surprisingly enough I have updated TWRP to 2.6.3.0 since then too!
[Verizon Samsung Galaxy S 4] mcconvict:
Is it doing it on regular AOKP or just this one?
[Verizon Samsung Galaxy S 4] DaMadOne:
yea.. reg AOKP too. When I was testing stuff last night I was doing plain ole AOKP builds... It has been an issue for AOKP since the first week of October. It works just fine on CM nightlies.. It must only affect us JF users because I have not see any others complain. Ive tried my plain AOKP builds as well as official nightlies.. same thing. I see the error in the log, ALSA audio errors with error 5 and then recording stops. Crazy thing is that ALSA has not really been updated. AOKP tracks TinyALSA from google.. and it doesn't work. CM tracks their own TinyALSA which I have cloned in and built with and it doesn't work, it does the same thing. Yet video recording works with no problems on CM (no alsa errors). There was a commit to Gallery2 (our camera) around the first of October that forces recording to stop on ALL errors. I can revert that and then video will "record" for days.. but in the log that same Alsa error 5 happens, and it will keep right on "recording", but when you stop recording and that error has occurred it just stops, it doesn't actually save the recording. Im sure I am going to bang my head against a wall when either I figure it out or one of the actual AOKP device maintainers actually gets around to looking into it, and I see what it was.

BMc is our official device maintainer, but he has been tied up with Moto X and Active display stuff here recently. I have helped out and committed stuff to AOKP's gerrit involving our device when I can... but in the end im still just a n00b in the learning process..
[Verizon Samsung Galaxy S 4] mcconvict:
I remember it doing this a while back. Same thing. It would record but when stopped it wouldn't save. Wondering if the fix would be similar here?
[Verizon Samsung Galaxy S 4] DaMadOne:
some updates to frameworks_av as well as camera today involving qcom devices. God I hope the camera is fixed.. im doing a build now to test it out. Also the network stats stuff I had been working on got officially merged in today! Stoked on that! Contributing FTW =P
[Verizon Samsung Galaxy S 4] mcconvict:
Nice work on the contribution! As always, looking forward to another build
[Verizon Samsung Galaxy S 4] thehotboy:
hey anyone, how do i get the active display to work? i enabled the option n everything but get nothing .. just system ui force closes
[Verizon Samsung Galaxy S 4] jova33:
I got that dual boot thing working. Hyperdrive on ROM 1, AOKP on ROM two. I might do a how to tomorrow if anyone is interested.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] rkirmeier:
Interested!
[Verizon Samsung Galaxy S 4] mcconvict:
Can my mom please have her smartphone back?

---------- Post added at 12:48 PM ---------- Previous post was at 12:27 PM ----------

Camcorder still broke on last nights official nightly. Don't use it but still bugs me because its the last remaining bug of significance for me
[Verizon Samsung Galaxy S 4] DaMadOne:
Which build are you running? I had a few FC's on early build with AC in it. But I have not had a single issue on this latest build. I just realised I never updated OP with the last build I posted in the thread, So if you missed it look back a bit and grab that one. Ill update OP when i get off work.

def do up a how to. Id like to check it out. I just have not messed with it yet.
[Verizon Samsung Galaxy S 4] DaMadOne:
Happy Halloween!
[Verizon Samsung Galaxy S 4] mcconvict:
Google gave us all KitKat for Halloween. New toy to look forward to
[Verizon Samsung Galaxy S 4] DaMadOne:
yea! why is this crap ROM not on kitkat yet!?! oh wait... =)
[Verizon Samsung Galaxy S 4] mcconvict:
Lmao..well played sir
[Verizon Samsung Galaxy S 4] HoodBoogie:
I did a clean install. My radio and WiFi signals are weaker than when I was using TW ROMs. Also having boot loops every other reboot. Wiped everything before install
[Verizon Samsung Galaxy S 4] mcconvict:
Radio and WiFi will always read weaker on aosp Roms. Try a custom kernel to cut the boot loops
[Verizon Samsung Galaxy S 4] DaMadOne:
yea, there have been some commits to Androids gerrit to help calculate and display the signal strength better. My guess is they don't get merged because its for devices that are not Nexus devices, so its not googles "problem". The stock kernel has always been a bit wonky. Grab a 3rd party kernel. I personally suggest Faux's kernel, its what I use and my phone runs fine. I do find the boot loops odd though. When I brought AOKP's stock kernel up to date with CM a couple weeks ago I ran it for 2 days and did many tests with it. Rebooted a ton and never had an issue.
[Verizon Samsung Galaxy S 4] apophis9283:
That commit (i use it in my builds) is to put android phones in line with signal strength with non android phones......
[Verizon Samsung Galaxy S 4] DaMadOne:
right.. its just superficial though.. it doesnt actually boost the signal, it just make the bars display closer to what they really should be. The only place locally i see FULL bars is while im at work.. but there is a tower 100 yards from there too. Did a speed test the other day when I was bored. Got 28down and 22up.
[Verizon Samsung Galaxy S 4] apophis9283:
Nope, doesnt boost it. Just more accurate
[Verizon Samsung Galaxy S 4] jova33:
http://xdaforums.com/showthread.php?p=46965295

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Does this rom support ViPER4Android?
[Verizon Samsung Galaxy S 4] DaMadOne:
no.. another person said it does not work. Apparently there are some commits that need to be done on the source in order for it to work on 4.3.1? I looked a little bit but did not find info on what was needed. Since I have no personal interest in it I did not spend a lot of time on it. If you can track me down the info on what I need to do on my end I have no problem doing a build that supports it. If it doesn't cause problems with non viper users I can keep adding in the support on future builds. Though I sorta expect seeing another build or two and then moving on to the now released 4.4 kitkat. I expect that will open a whole new can of worms for viper until he updates it.
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Here is the post about the commits to revert the lpa changes made in cm so viper will work

http://xdaforums.com/showthread.php?p=46328675