yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] mcconvict:
Just a FYI...the 4.4 camera camcorder works like a champ. No issues at all
[Verizon Samsung Galaxy S 4] DaMadOne:
Lol
[Verizon Samsung Galaxy S 4] flyinj54:
Does the camcorder seem extremely blurry to you?
[Verizon Samsung Galaxy S 4] DaMadOne:
Awesome. Thanks. I will look into it!
[Verizon Samsung Galaxy S 4] mcconvict:
No. Mine seems absolutely fine. Was kinda surprised it worked this good
[Verizon Samsung Galaxy S 4] thehotboy:
yupp active display definitely gives me constant System UI fcs
[Verizon Samsung Galaxy S 4] jova33:
Isn't there an app on the play store that's active display, but better?

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] thehotboy:
i been using knock2+ but i can't get it to work all the time
[Verizon Samsung Galaxy S 4] mcconvict:
Active Notify?
[Verizon Samsung Galaxy S 4] jova33:
I forget what it's called. I follow droid life on Twitter and they were posting about it a lot a couple of weeks ago.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] DaMadOne:
OP updated with new build. This is mainly to bring up to date with what has been merged into AOKP and a few other things. May be the last build before 4.4. Not much happening on AOKP's gerrit since 4.4 release. I don't foresee many changes being made til the 4.4 merge up is done, which I am told is ongoing in the background. I am going to take this small break to get my Battlefield 4 on ;)

I did have a problem with AOKP backup on this one. The restore seemed to go fine, until i noticed that my lockscreen ribbon was not there even though it looked fine in ROMControl, ie, my icons were there, but nothing I did would get them to show. I had to re flash and just do RC settings manually, and all is fine.
[Verizon Samsung Galaxy S 4] mcconvict:
Typically smooth build. Runs like greased lightning. Gotta say I kinda dig the kit Kat launcher deal. Good stuff
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Did you change committs for the lpa?
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Guess not well I'll cross my fingers it will work on 4.4
[Verizon Samsung Galaxy S 4] jova33:
Slow GPS lock? I've only been back on AOKP for like a week, flashed the official nightly, then your build.

I have Hyperdrive in slot 1, and it locks on immediately. Both AOKP builds seem slow on getting a lock. The other day I had to flip to Hyperdrive so I could use navigation.

Also, what kernels go good with this? Ktoonz did not like AOKP, the official nightly.

Edit: Bluetooth issues, anyone else having this?

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] DaMadOne:
im sorry.. completely forgot.. Working on a test build for you right now.
[Verizon Samsung Galaxy S 4] DaMadOne:
I personally disable everything I can tracking wise on my phone... google knows enough lol. But just now I enabled it and tried to "check in" with my location on facebook.. it took maybe 30 seconds to lock, but I was also standing in my back yard.. so completely open. From wht I have read though it def takes longer to get a lock with our device on AOSP vs TW. On Apophis's thread I see where he suggests getting a lock on a TW rom then switching to AOSP, though I don't know if that applies to you since you were already on a TW based rom.

As far as BT goes, the pioneer navigation in my car is prob 4-5 years old and only has basic BT phone functions and it has been working fine for me. what kinda bt issues are you having?

For kernels, the only one I have tested is Faux's kernel. Works like a champ for me. I underclock to 1.655 and undervolt by -50mv on intellidemand. Smooth as silk.
[Verizon Samsung Galaxy S 4] jova33:
Bluetooth won't turn on at all. When I go into Bluetooth settings it's just stuck at turning Bluetooth on. I mess with a lot of stuff before I flash a ROM, flash some mods, dual boot, and dirty flashed, so there's so many things I could've done wrong to break it. It worked on the last build I flashed though.

Oh well, TW for the car, AOKP for everything else.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] mcconvict:
Absolutely no issues with GPS lock here. Instant and accurate in 1-2 seconds. Bluetooth can get crackly and about every 4 songs it freezes for 15 seconds, disconnects then reconnects. Will be fine for 4 songs then repeat the cycle. Not a huge deal. I figure its the price of being on the cutting edge. And is that a 4.4 test build you're working on?? I just tried it on my gnex and it was pretty slick. The Google experience launcher is a nice touch

---------- Post added at 07:23 PM ---------- Previous post was at 06:54 PM ----------

Ohhhhh test for the viper audio lol
[Verizon Samsung Galaxy S 4] DaMadOne:
lol its coming.. already built, uploading now. I played with 4.4 on my nexus 7.. the " Google experience launcher" is a joke... I still needed to grab nova launcher. From looking at the 4.4 source and n7 build the users will not notice much of a deference.. its all under the hood.
[Verizon Samsung Galaxy S 4] DaMadOne:
Viper Audio test build. I reverted the 3 commits you linked to. let us all know how it goes. Assuming it works please write up a how to on how to make it work with this rom step by step! I have not used it, but if you write up a how to I will def give it a shot! I have not flashed this personally, but really nothing has changed other than the few reverts for Viper from the last build I posted.

md5: 775aeca5c4c1d889ef4af40046202fda

DL: smoothaokp_jfltevzw_jb-mr2_viper_2013-11-05.zip - 198 MB
[Verizon Samsung Galaxy S 4] zeb carter:
A question

I'm still on the 9/23 build with MDK. I've been thinking of flashing something a bit later but before I do.

since I am still on MDK, what's compatible? I love this rom! But I don't won't to give up the ability to flash via recovery (using OUDhs CWM Touch Req0very v1.0.3.5).

What suggestions do you have for me with this great rom? And is there a later version of CWM I should use?
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
OK reverting those did work dude you are the man you don't know how happy this makes me.

1. Clean install

2. Install viper4audio http://vipersaudio.com/blog/?page_id=48

3. Open v4a install driver of choice super audio being best.

4. Reboot into recovery and flash https://docs.google.com/file/d/0B1THCFnqPTkqOWJjV2lnSWY5aWM/edit?usp=docslist_api (build prop edits)

5. Open v4a and enable adjust what you want and profit.

---------- Post added at 02:01 AM ---------- Previous post was at 01:51 AM ----------

More info on v4a here http://xdaforums.com/showthread.php?t=2191223

[APP] Official ViPER4Android Audio Effects (FX v2.3.1.3)
[Verizon Samsung Galaxy S 4] rkirmeier:
After a night of trial and error I got this running as a dual boot. Would have worked first or second try had I been using the latest version of the dualbootpatcher tool. Turns out the ramdisk patcher was not working correctly as AOKP would start booting then stay on the boot image screen. Non the less it's working and nice that I can switch back if needed.

I have 2 issues I'm hoping to get some help with.

1. In the active display the navbar area shows the screen background instead of just black. I do have my navbar set to translucent and probably the culprit but certainly also a bug. I like using the NavBar (main reason to run AOKP) and like the translucent look so really hoping this can be fixed.

2. The stock camera does not do widescreen. I tried the Focal Camera but it locks up. When I ran AOKP (4.2) there was a patched camera. Anyone know if there is a patched camera for AOKP 4.3? UPDATE: Problem solved by buying Camera JB+ in the Play Store. It's 1.99 so no big deal...

Nice work! If I can resolve these issues I'll probably AOKP will probably become my daily driver again. Nice to be back! :)
[Verizon Samsung Galaxy S 4] jova33:
For some reason I can't get Bluetooth working when I dual boot. I tried the official 10/31 nightly and this build. Bluetooth won't work for either.

Bluetooth works fine with the 10/13 official nightly though.

If you have Bluetooth working, can you send me your patched updater-script? And are you using the patched tool on the computer or phone app for the boot.img?

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] rkirmeier:
Just tested Bluetooth in my F150 with the Sync system and everything is working fine. Are you doing a dirty flash? Attached is my updater script for the dual boot. Using the ramdisk (boot.img) patch tool on a Windows computer. Had problems with version 1.18.1 but then downloaded the latest 2.5.3 and all is working fine.
[Verizon Samsung Galaxy S 4] leyvatron:
Thanks for the work.

I started using ktoonz kernel and the battery is much better.

What app are you using for IR? Watchon? Peel?
[Verizon Samsung Galaxy S 4] DaMadOne:
Yes, ktoonzes kernel is awesome. I haven't tried others.. doubt I will unless faux starts making AOSP kernels for our devices.

for IR I am using ZappIR. I had a hard time talking myself into spending $8 on it.. but the reviews were great so I did. Its awesome and I'm not at all upset that I spent $8 on it... though I do feel that price is a bit high when you look at the price of some much more complex apps out there. I personally think $4 would be fair...
[Verizon Samsung Galaxy S 4] DaMadOne:
finally.. just gonna leave this here... I'm going to bed.
[Verizon Samsung Galaxy S 4] DaMadOne:
New linaro builds are coming...bear with me. I have been running a basic no addons build today and it's showed no signs of issues. I am working on getting the script tweaked the way I like it, and updated to the newest 4.7 toolchain which has posed a couple issues from the outdated 4.7 toolchain that I compiled with last night. It takes forever to compile.. get an error.. yell things you would never want your mother to hear at the screen then track down a fix and or try and fix it myself.. then rinse and repeat on the next error. Learning A LOT as I go.. that's half the fun.
[Verizon Samsung Galaxy S 4] gfro9191:
Thanks so much for picking up where apophis9283 left off. Works perfectly!
[Verizon Samsung Galaxy S 4] apophis9283:
I want everyone to know why he was having build issues when I didnt. Apparently it has to do with the IR stuff. Im glad he picked it up as well. I think you guys are going to really enjoy his builds. Hes a really nice guy. You guys couldnt ask for more.
[Verizon Samsung Galaxy S 4] DaMadOne:
thanks for the +1 rep =P Long story short it wasn't even the IR. Same errors with vanilla AOKP. How it was compiling for you without some modifications to the kernel I have no clue. Have you looked at neo's github recently? I like what he is doing with the GCCfreedom commits. Those combined with the script I am sure will follow should be awesome.
[Verizon Samsung Galaxy S 4] apophis9283:
I have no idea why you were having build issues. It compiled fine for me. When we were talking I compiled twice with 0 errors. Did make clobber and not using Ccache. Im glad you got it working, these guys deserve some good builds.
[Verizon Samsung Galaxy S 4] GTvert90:
Price dropped to $4.95
[Verizon Samsung Galaxy S 4] DaMadOne:
That's just my luck lol. oh well.. I'm happy with it.
[Verizon Samsung Galaxy S 4] DaMadOne:
Holy crap! so I thought why build with linaro 4.7 when I could build with 4.8? So AOKP linaro 4.8 w/ -O3 optimizations anyone? Might just have to dub the rom SmoothAOKP?

It built. Unfortunately though the stock kernel will not boot. I flashed ktoonzes over it and it booted right up. Wanna talk about some SMOOTH! There is next to NO boot up lag. Pretty much once I can see the main home screen I can start swiping home screens pretty quickly with pretty much no lag, and it overall feels ridiculously snappy too. Ill see if I can get a kernel log of it crashing and try to get in touch with one of the kernel devs tomorrow and see if they have any insight as to why it would compile but not boot. A quick google search shows I am not the only one to have problems with kernels and GCC 4.8. If it's not something that can be fixed, I can always cross compile with linaro 4.7 just for the kernel if I have to. Or just do away with the AOKP inline kernel building and build it with Ktoonzes baked right in. (of course I will need to ask him first)

anyone have any thoughts? if I can't fix it. AOKP kernel compiled with linaro 4.7? or bake in Ktoonzes?
[Verizon Samsung Galaxy S 4] GTvert90:
Sweetness. As far as the kernel goes, which ever is smoothest I don't know enough to know if cross complying is bad or not
[Verizon Samsung Galaxy S 4] mp3sum:
I love seeing real Devs bridge the communication gap between enthusiasts and their own more technical endeavors. Sounds like the start of a beautiful kang thang.
[Verizon Samsung Galaxy S 4] mcconvict:
I say ask KT. I pretty much always use his kernel anyway. Any chance you could upload that build and I'll flash KT? I'd love to check it out!
[Verizon Samsung Galaxy S 4] MiPaDo:
I use this on my SGS4 and love it.
[Verizon Samsung Galaxy S 4] jova33:
Yeah, whatever kernel AOKP was using was giving issues with charging.
[Verizon Samsung Galaxy S 4] DaMadOne:
Cross compiling would "basically" mean the rom would compile with 4.8 and the kernel with 4.7. It would be fine, it would just be cooler to me if it was all 4.8.

haha I'm far from a "real dev" but I'm trying =P I know I like to be informed on things I'm into.. so I try to keep you guys informed.

I think a lot of us do.. I'm not ready to give up on the stock kernel yet. Only compiled once after all.

here is what I am running on my phone today. Just a heads up It is vanilla aokp. I will likely build another with the IR and at least the features implemented in my last released build when I get home from work. I haven't had it freak out on me... yet.. :D

AGAIN FOR ANYBODY WHO TRIES THIS THE STOCK KERNEL IS SCREWED, IT WILL NOT BOOT. IMMEDIATELY FLASH ANOTHER KERNEL (ktoonzes, etc.).. IF THIS SOUNDS WEIRD TO YOU, DO NOT TRY IT! If you do try this make sure you do a 100% fresh install, backup your apps and settings with something like TiBu and AOKPBackup then wipe system/data/dalvik and cache. Otherwise I am gonna ignore your "bug reports". It only takes a few extra minutes to do a clean install vs a dirty one. =)

MD5: 7198b28221b9235122146c2c83242d2d

SmoothAOKP_Linaro4_8_Test_2013-08-12.zip - 180.58 MB
[Verizon Samsung Galaxy S 4] apophis9283:
Im pretty sure Neo went down that road and the toolchain borked the browser. Make sure you walk lightly when you go down that path and test everything.
[Verizon Samsung Galaxy S 4] DaMadOne:
Browser works. Camera works.. I have had no FC's or RR's.. I laid in bed for like an hour last night going through apps I use often and not so often.. It's working well as far as I can tell. *fingers crossed*
[Verizon Samsung Galaxy S 4] jova33:
Yeah, I dirty flashed, clean flashed. I don't know what I'm doing wrong. I modify my gapps by putting the team blackout ones in there, but I don't think that would mess up Bluetooth.

I'm wondering if I messed up something in the updater script. Or.... what modem do you have? I'm on the MJ7 modems.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] rkirmeier:
My modem (Baseband version) is MDK.
[Verizon Samsung Galaxy S 4] jova33:
I'll try your updater-script later, I'm at school now. Thanks man.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] rkirmeier:
I don't see how the dual boot updater script could have any impact as either your system will run or not. Maybe the new modem is causing problem with AOKP.
[Verizon Samsung Galaxy S 4] jova33:
That wouldn't explain why Bluetooth works with the MJ7 modem on the the 10/13 nightly though.

Edit: I'll try all things. I've still got all the old modems, so I'll try them first.

Edit again: absolutely correct. It was the modems. interesting though that MJ7 works with the 10/13 official nightly, no one else has mentioned MJ7 modems messing up on AOKP, or if they did, I must've missed it.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] DaMadOne:
From a quick glance @ cm who has updated their vendor blobs for the latest VZW update.. there are some changes that need to be done to other things in order for everything to work right it looks like.

I am just holding out for AOKP kitkat before I start messing with stuff again as it just seems futile to spend more time with 4.3.1. I am REALLY hoping that the video cam is back to working out of the box on kitkat. I was getting a bit burnt out and needed a break anyways, plus this break give me time to shoot fools in BF4 for a bit! If any of you guys play BF4 on PC my name is EKRboi on there. Im not as serious about it as some people are, I just play for the fun of it.
[Verizon Samsung Galaxy S 4] mcconvict:
Have you seen how far along BMc is on 4.4? Got data, SMS, MMS, BT all working. YouTube and camera are on his fix list. But he's flying along.
[Verizon Samsung Galaxy S 4] jova33:
So is there a problem with AOKP and the MJ7 modem, or am I the only one who's experienced it?

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] mcconvict:
I've never bothered changing my modem. Never saw a reason to change it.
[Verizon Samsung Galaxy S 4] jova33:
Well MJ7 has AWS, so if you live in an area where it's been activated, you'll get like 5x faster than regular LTE.

Although it's not activated here where I live, maybe some of the cities I travel to will.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] DaMadOne:
YES! he is moving right along! correct me if I am wrong, but I believe he is working on the S3 atm. Hopefully S4 falls right into place after that! :laugh:
[Verizon Samsung Galaxy S 4] mcconvict:
I saw him say that the s4 is at the same place as the s3. He's doing both I think
[Verizon Samsung Galaxy S 4] rkirmeier:
Who needs 5x faster then regular LTE. It's smoking fast already...
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Nice write up [MENTION=3853348]kvswim[/MENTION]

Only issue ive found is my teamspeak app not working
[Verizon Samsung Galaxy S 4] jova33:
I guess they've merged the fix for MJ7 modems. Should be in future builds

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] jova33:
Hulu not working?

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] jpmcnown:
I'm unclear, with the Viper4Android. Do we need to do all that stuff to install it if we flash the 11/5 rom?
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Yes
[Verizon Samsung Galaxy S 4] kvswim:
It's really not that hard, it just looks like a complicated process. It's pretty much just hitting a few buttons and rebooting twice. It's totally worth it. Honestly the hardest part is finding that lpa.decode line in build.prop.
[Verizon Samsung Galaxy S 4] jpmcnown:
Thanks, yeah, I agree, It's not very complicated, particularly considering the very detailed instructions. I just wasn't sure if the 11/5 build contained the addition, because I was going to try and dirty flash it over 11/3 if so. Thanks again.
[Verizon Samsung Galaxy S 4] jova33:
I'm a genius. Adblocker was blocking the ads on Hulu, so Hulu couldn't work lol.
[Verizon Samsung Galaxy S 4] kvswim:
On the 11/5 the camera randomly fails to start, and Snapchat will not record a video. Pulled the logcat and got a bunch of these:

not sure if this is a new issue or not, I remember reading people were having problems in earlier builds but I thought there was an update that fixed it. I also grabbed a dmesg if it logs that sort of thing.
[Verizon Samsung Galaxy S 4] jova33:
I haven't gotten video recording to work either.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] mcconvict:
Have you tried the 4.4 camera app? It worked for me
[Verizon Samsung Galaxy S 4] jova33:
Ok, it didn't work. switched to lower resolution. it worked. Switched back to 1080, hit record, waited 5 seconds, hit stop, and video didn't record. Hit record again, hit stop, and it recorded.

Very strange. This is the 4.4 camera.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] kvswim:
Also, there is a SIGNIFICANT battery drain after the error appears and persists until a reboot, which fixes the camera for a while until it fails again and the cycle repeats. Battery graph shows Android System at 17%, phone idle at 13%, and Mediaserver at 12%; while BetterBatteryStats says msm_camera taking up 92.3% of kernel wakelocks.
[Verizon Samsung Galaxy S 4] sbcrumb:
I also can't get the video camera to work. If someone can link me to the 4.4 camera I will give that a try.
[Verizon Samsung Galaxy S 4] DaMadOne:
Just popping by to say hello. BMc has been working through the bugs that I have posted on bugs.aokp.co. The vibrator settings have been fixed. He has acknowledged the problem with the video camera and is looking into it. Also how on the last couple of builds it defaults to the 3g network instead of LTE he is looking into, I posted a log he requested today. Team kang is working through all the device bugs so that they can post a final 4.3 milestone before really digging into kitkat.

I have not stopped working on android in the background, though not as much as I was. I have committed stuff to aokp's gerrit that has been merged helping bring things for our device up to date. There has just really been no big reason to make another SmoothAOKP build as there has not been any major new stuff added and other than the vibrator settings the same bugs everyone has been dealing with are still there. With BMc on the case I can only assume it will be another few days and things like the video camera will be fixed. I spent a bunch of time trying to figure the video cam out and I can't wait to see how he fixes it. It will likely be one of those "DUH!" moments =) As soon as these bugs are squashed I will do another build. I am still running the same build you guy are!

I have been enjoying BF4 in between painting my house (not fun btw) and work. Other than the final 4.3 bugs getting squashed, I can't wait for AOKP kitkat to start rolling out and new fun to begin. It is my understanding that AOKP is going to start fresh with kitkat so the first builds will be pretty much AOSP, and then once that is running smoothly the AOKP features everyone has grown to love will begin to trickle back in. I think kitkat is going to be a fun ride and I will get to watch and hopefully help bring the features back and learn a crap load in the process. You guys ready?!
[Verizon Samsung Galaxy S 4] mcconvict:
Good hearing from you. Happy all is going well. Kit Kat is a pretty good experience for me so far. I miss all the options tho. Can't wait for all the unicorn magic to get thrown back in the mix
[Verizon Samsung Galaxy S 4] DaMadOne:
Y'all might wanna go looking through my dev folder [MENTION=1901967]androi[/MENTION]d filehost... Who knows what you may find... Just sayin =)
[Verizon Samsung Galaxy S 4] mcconvict:
Downloading right now! You are the freakin man!
[Verizon Samsung Galaxy S 4] DaMadOne:
Lol. Thanks. I take 0 responsibility for it. Its not without its issues.. But I figured y'all might wanna try it
[Verizon Samsung Galaxy S 4] DaMadOne:
Its dhackers gapps.. I pulled the Google home out of it because the AOKP build has the launcher in it.. But with the launcher3 I have not got the OK Google home screen voice recognition to work with it. If you go find dhackers gaps package it has a pre made Google home in it.. It may work with it
[Verizon Samsung Galaxy S 4] DaMadOne:
The "OK Google" voice command does work with the 4.4 kitkat launcher apk floating round the Internet's so it prob works with the launcher in dhackers gapps package
[Verizon Samsung Galaxy S 4] jova33:
So is there anything spectacular about kit Kat? I updated my wife's stock Nexus 7 to 4.4, and wasn't impressed.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] wessiide:
Anyone experienced the same issues on this rom as other 4.4 roms have had? Such as proximity sensor, gps issues, dropping Wi-Fi and Bluetooth?

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] mcconvict:
Actually my 4.4 experience has been nearly flawless. The euroskank cm builds have been excellent
[Verizon Samsung Galaxy S 4] wessiide:
Blah nvm!

Sent from my SCH-I545