yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
The continuing video recording saga....

All,

I am continuing to work on the video recording issue. Thank you all for your patience. As well as doing my own research and testing, I have posted in several developer threads to request assistance from more experienced developers.

Beanstalk and RR both use different vendor blobs than I am currently using. So I decided to try their vendor blobs. Compiling with their vendor blobs does not cause any compiler errors, however, when using them the camera works even less. In the case of Beanstalk it will not allow me to take pictures either. So it would appear that their vendor blobs require some changes to the device trees to work. I am pursuing that as well, but I apologize, it is slow and tedious work to unravel their work and compare it to mine. There are many differences, but not all of them are pertinent.

I also have been scouring the web during my work breaks. It appears CM13 did have several camera issues at first, which were later resolved. AOKP and PAC are partly based on CM, so there may be some correlations there as well.

If camera video recording is a must, there is Beanstalk 6.0, and RR, as well as my SlimLP, in which video recording works great.

So, still a work in progress, just wanted to keep you all updated! Thanks again for your patience!
[T-Mobile Samsung Galaxy S 4] carlos9545:
Thank you sir for the hard work that your doing, i just wanted to say that one day,(like a week ago)(previous version from lionheart) i recorded a friend of mine using the default camera app and it saved nice instantly to the gallery and later i tried to send a video trought whatsapp and didnt work either using the default. And one day i was anoyed(thinking that my camera was broken) so i started to push the record button several times untill i see a little video recorded a side in the gallery.

i know maybe this information may be hopeless but, maybe someone know why it worked.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
No fix yet, still WIP. Interesting bad work around.

Just an update, no fix yet for the video recording, but I am still working on it. I enabled the old camera api's just to see if we could use older camera apps that worked on "intent" instead of "mediarecorder" as a work around while I figure out what is wrong. The old camera api's still work, even on MM, if you build them in (they typically are not built anymore, in favor of the new camera2 api's). However, that did not solve the video recording problem.

I did find an interesting (however, lame) work around. This is not the fix, this is a bad work around just as an FYI:

The other day I needed to make a video recording of something at work, so I used the Screen Recorder app (not the power button screen recorder menu option, but the app) and checked the box for enabling the mic. So, of course, it started recording the screen, onto which I opened the camera app, which was displaying what the camera sees, and the screen recording captured what the camera saw, as well as the audio, since I had enabled the mic.

This is not my suggested fix, this is the lame duck work around for any still using the AOKP MM while I work on a real fix, or sensible workaround. Thank you again for your patience!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
To God be the glory! I've got working video recordings!

I am just doing some testing, ended up switching out a few device vendor blobs and a change to the device trees. Right now I am testing to make sure everything else still works as it did before.

I am heading to bed, and church tomorrow, but hopefully Monday I can have the new build posted on media fire and in the op!

Have a great weekend everybody, and thanks again for all your patience!

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] carlos9545:
your the best sir, have a good weekend hope to see the best rom for my phone running smooth and nicely. Thanks.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New build is up!

New build is up! Updated the OP.

The new build is up with the fix for video recording! Video recording now works! Essentially, I was using DU's material as a base (which is based off of CM), so I updated to using straight CM material for the device trees, and made the changes for AOKP, as well as adding in the Kernel Adiutor app again. I also updated the vendor blobs from "The Muppets" on Github. I have updated my Github sources as well, so anyone can use those if they want.

With this comes the Gello browser, as apposed to the Android default browser.

I recommend a full wipe for this one. I know it is a pain, but this is changing some vendor firmware and device tree stuff, you can flash dirty if you want first, but if there are issues, I would need you to do a full wipe and install to make sure it was not "leftovers" from the previous builds. I have been playing with this all weekend, it seems just as solid as before, but let me know if you run into any new problems.

Change Log:

20160718

-Fixed video recording, now works properly! (Praise God!)

-Dropped Android browser and added CM13's Gello browser.

-Edited updater script so that it may be flashed on any JFLTE phone.
[T-Mobile Samsung Galaxy S 4] Kuropis:
Going to install tonight. Can't wait!

Thank you for your hard work!
[T-Mobile Samsung Galaxy S 4] darazor:
Thanks for the update. One quick question. Is there a reason that SELinux is set to "Enforcing" on this build? This interferes with TWRP Manager APP which requires permissive. I'm not sure if some other apps are affected. All your other ROMs on the AOKP build have been set to permissive. Or am I missing something or failed to do something? Thanks.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
[emoji15]

Whoops! That's a rookie mistake! I can fix that in the download tomorrow. In the mean time, flash the aklu-fastcharge kernel and all will be fixed, as it will be set to permissive.

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] khaoticking:
You could also download the plugin for kernel aduitor that allows you to switch between enforcing and permissive if you don't want to flash a different kernel
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Fixed SELinux, set to Permissive.

The OP has been updated with a new build. The only change was setting SELinux to permissive.

Great point! For those that do not know how, it is very simple. In the Kernel Adiutor app, go to "plugins". Once there, click the download icon at the top, and it will ask you to download a small apk that is the plugin for SELinux.

The other option, is that you may install one of the kernels from the kernel thread, which are all set to permissive.

Just a side note while playing around a bit with permissive/enforcing: it is not as stable in enforcing. I highly recommend setting it to permissive.
[T-Mobile Samsung Galaxy S 4] darazor:
Flashed kernel all is well. Tried a dirty install and everything works fine xposed, bluetooth etc.

---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------

Thanks didn't know about that plugin.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New Kernel is up!

There is a new kernel in the Kernel thread!

http://xdaforums.com/galaxy-s4-tmobile/development/kernel-marshmallow-lollipop-kernels-t3411543
[T-Mobile Samsung Galaxy S 4] 500tab:
Hello, I'm having some problems in my attempt to flash the new build. I'm hoping someone can help me out here, getting alittle nervous. I've tried numerous times to wipe cache and dalvik cache and install the aokp-7-18-2016 ROM, however I kept either getting an error about setup wizard not working or if not, I'd get the ROM working but none of the GApps would work. So I tried wiping cache, dalvik cache and system a couple times and still left with one or the other problems there. The last time I was in TWRP trying to flash I got an 'error 20'. Since then I havent been able to get past the Samsung splash screen. I can get into ODIN mode but Im having trouble getting back to TWRP. Any help on this one REALLY appreciated.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
500tab,

Sorry to hear that you are having some issues. A couple of questions: What phone specific model, which TWRP version, which bootloader/baseband?

I am sure that you already tried this, but here were the install instructions:

I do know that it will work, as I use this method to test each build before putting it on the website. However, I do not test the downloads, so it is possible that there is a problem with the download. Also, there is the new 20160720 posted also. Keep in mind there was a big change in 20160716, so if you had a version before that, then you need to do a full wipe. Dirty flashing is risky. It can be done, but if there are errors, we always need to start with a clean slate.

As for the Gapps, which one are you using (please be very specific).

http://opengapps.org/

Has the gapps that I use. By default, when I go to the site, the gapps are set to 5.1, which is not what we want. Be sure that you are checking "ARM", "6.0", and then your size/choice. I have personally tested "Pico" and "Nano".

Let us know how it goes, and the information above, hopefully we can get you up and going!

EDIT:

Ah, I should have read your comments more carefully. If your TWRP is messed up, I would go to ODIN mode, flash a stock rom. Then use Odin to put on TWRP. This will clean your phone out like it was brand new.

--TWRP downloads--

https://dl.twrp.me/jfltetmo/

Hope that helps!
[T-Mobile Samsung Galaxy S 4] 500tab:
Alaska, thanks for the quick reply. I am using TWRP 3.0.2, ARM based GApps 6.0 Nano on my M919. I'm not sure what baseband I am using or how to look it up(especially while my phone is in its current state). It looks like my option is using ODIN, I will try flashing the stock rom and hope it smooths things out. Just to be clear, a clean wipe would be cache, dalvik cache, system and data? All four of those? I'll keep you posted.
[T-Mobile Samsung Galaxy S 4] dtriguero:
I'm gonna start running this rom as my daily since others I've found have issues and no real help nor regular updates and I'm not knocking those roms respected devs especially because I don't have the time to create builds of my own its just hard to track down and fix bugs in something I haven't built with little help sorry rambled on a bit but anyway got a question since I've seen in many others is there any chance of OTA updates for this rom be built in instead of having to check the forum or maybe at least a built in way to check to see if there has been any updates
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Yes, those are the "advanced wipe" options. That is what I mean by full wipe. Sometimes you can dirty flash, but it is a gamble. If too many things change, then you may have problems. Sounds like you are on the right track, and hopefully you are up and running soon! :D

I wish I could do ota updates! I am not very knowledge able about them, but I think I would need a host or server for that. Sorry. I would do it if I could, though. Great idea! And welcome to the AOKP! :D

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] bipnilaga:
Hello guys anyone ran into this issue? When i am on a voice call, I cannot send txt messages (sms), but can receive. As soon as I hang up the call, the text message gets sent.

I did notice that as soon as I am on a voice call, the LTE signal goes to 'no service' and it greyed out, but iam still able to talk. All other data still work such as the ability to browse internet. Note, that i can receive txt messages though. Its really weird. Otherwise this ROM is great! Love it.

I think this could be a problem with the ROM, as when i flashed back to the lollipop version of this rom is works just fine.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for joining the AOKP! :D

To be honest, I have never tried to send a text while on the phone. Then again, my phone calls are usually less than 5 minutes long, so I never needed to. So thanks for pointing this out!

As for the LTE 'no service' indicator, my understanding is (anyone can correct me if I am wrong) that you cannot make a phone call on LTE bands. Voice communications through the phone system only work on 2g or 3g connections. I am pretty sure that whichever rom used, this will always be the case. However, you don't need LTE to send or receive text messages. As you said, even without LTE, you can still receive text messages.

So, as to why we cannot send a text message while on phone calls? I am not sure. However, a couple of questions for you so I can look into it more accurately:

-Text app in use (have you tried others?)

-phone model (specific)

-Rom version you downloaded (e.g. 20160720 etc...)

-Kernel (if you flashed a different one then what came with the rom)

-Are you using bluetooth while doing this?

-Gapps verison you downloaded

-baseband (in settings menu --> about phone)

Most importantly, in your texting app, are you sending text messages as sms or as mms? This may make a difference. If you are using one or the other, try the other and see if that works.

Anybody else want to test this also? The more feedback the better!

Also, a logcat would be great. I will try that one, too.
[T-Mobile Samsung Galaxy S 4] cirrus97:
This is really weird. If I just flash fire & look for your zip files on my sd card they don't show, other zips I have show with no problems. When I go into TWRP and try to install the zip for the rom or the kernel zip I get a message that the zip file is corrupted. I'm using TWRP 3.0.2-0.

I'm wondering if it's the way it's zipped.

I'm using your 2016-06-03 build right now. I've wiped everything & tried just about everything I can think of, but still get the corrupted zip file
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Hey bipnilaga,

I just tried this while on a phone call with my wife. I sent her a text, while on speaker phone with her, and received a text, while still on speaker phone with her. Then I called another person and sent and received a text while not on speakerphone, but during the call with them. I think it must be some setting in your text message app?

I used ChompSMS app and the built in dialer app, on my OK3 baseband M919, using the AOKP 20160720 rom with the built in kernel from that rom. My gapps is the arm 6.0 pico from opengapps. Perhaps something in this lineup will help? Could you try it with ChompSMS to be sure?

cirrus97,

Sorry you are having trouble my friend! I tested the zip before putting it on the website, and due to your comment, I just now finished downloading from media fire, and flashed it to my phone. It worked without any issue. can you compare the file size of the download that you have against the reported download when you click on it and it takes you to media fire? It should be 361.42 mb.

Also, I know that chainfire is the best dev out there, and his work is incredible. However, using flashfire is extremely dangerous and can mess up your phone. I highly recommend using TWRP instead of flashfire. *No discredit meant to the great chainfire!* but even his own words say this:

So do be careful with flashfire. Also, can you install any other rom via TWRP. If not, since you have issues, I would almost recommend using odin to go back to stock, then odin to add twrp, and then doing a full wipe to install this rom. Perhaps that would help? If so (that is, if you can load other roms), then I would re-download the OP rom from your computer and check the file size. It works like a normal zip file, so if you cannot open it with a normal zip application (ES file explorer zip, Zarchiver) then the zip you downloaded was incomplete or broken.

Hope that helps, let us know how it goes! :D
[T-Mobile Samsung Galaxy S 4] cirrus97:
Hi apparently I'm brain dead today. You hit it right, the zips weren't the full size, for some reason the downloads weren't complete. Downloaded them again made sure of the size and is all good now. Thanks
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
I'm just glad you are up and going! :D

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] dtriguero:
no texting/call issues using gosms I would look into modem

---------- Post added at 07:54 PM ---------- Previous post was at 07:46 PM ----------

What your baseban and do both wifi and cell match. I usi a mix of two also which bootloader cause using a cell modem(baseban listed under about phone) lower than bootloader has been said to cause funny text and call issues it don't matter if wifi don't match actually older wifi modems work better for me
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New overclocked kernel in the kernel thread:

http://xdaforums.com/galaxy-s4-tmob...op-kernels-t3411543/post67902876#post67902876

Let me know if you have issues with the overclocking! :D
[T-Mobile Samsung Galaxy S 4] Kuropis:
Looking forward to the new build. Plans on adding the newer security patch?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Yeah, me too! :D

I am waiting to produce the next build for either the new security patches to be put in, or next month, whichever comes quicker. In the meantime I am working on kernels, which can be flashed without doing a whole new build. My internet is limited, and maintaining three roms and actively pursuing others for the S4 takes a lot of downloading of source, so I have to scale back a bit to keep from going over my limits. It is good, though, that is about all I have time for. Sometimes I can download source while at other places where unlimited internet is available. Tethering from my phone works (my phone has unlimited internet) but often I cannot get LTE signal, and it takes too long on 3g. Just some of the perks of living in Alaska, I guess! :D

A really easy way to see what the AOKP is up to is with your mGerrit app on your phone. If you update it in the Play Store, you can open it, it will be set to AICP (because it is alphabetical, and I comes before O), but you can click the three dots at the top for the menu and change it to AOKP. This shows you everything that is being worked on. You can also see it on your computer here:

http://gerrit.aokp.co/#/q/status:merged

or

http://gerrit.aokp.co/#/q/status:open

I have to put in a plug for these AOKP guys, they are busy folks doing some really, really hard work!
[T-Mobile Samsung Galaxy S 4] Inferno9999:
Hi guys, I've been really wanting to update my M919 since it is still on the dated kitkat and it feels a bit sluggish. Will this rom be a good replacement for day to day usage as if it were an official update? Is there any known issues that might prevent me from using it on a daily basis?

(I'm pretty rusty when it comes to flashing roms, I haven't installed a custom rom since 2-3 years ago so I might need a little help.)
[T-Mobile Samsung Galaxy S 4] germ27:
Just to be clear, all the steps are in the installation spoiler? I don't have to do anything else before those steps?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Inferno9999,

Thanks for looking at the AOKP!

Yes, this is a daily driver for many, including myself. All Marshmallow ROMs have a fickle Bluetooth issue, that you can read about in post #3. Other than that, it works great.

If Bluetooth is your #1 goal, I would recommend SlimLP here in the T-Mobile forums. It is Lollipop and the Bluetooth works perfectly there.

Feel free to ask any questions! :D

Germ27,

Thanks for looking at the AOKP!

Yes, those are all the steps. Unless you have not installed TWRP yet, in which case there are more steps. Be sure to ask us if you have more questions! :D

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] Inferno9999:
That is great news, I am glad that the rom is stable enough :D ! Now I will see how I do with flashing the rom. I don't even have a custom recovery installed yet. Do you recommend any specific recovery for the rom?
[T-Mobile Samsung Galaxy S 4] germ27:
I have not done anything yet, I just received a used S4 I bought off Ebay. This will be my first time customizing a phone, which is why I asked. I'm a tech savy person, build computers etc, but I'm just getting into the world of phones. I have a Alcatel one touch pop astro, but you can't really do jack to that phone. Which is why I bought the S4.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New Kernel is up!

New Kernel is up in the kernel thread!

http://xdaforums.com/galaxy-s4-tmobile/development/kernel-marshmallow-lollipop-kernels-t3411543
[T-Mobile Samsung Galaxy S 4] Inferno9999:
The rom installs perfectly fine on my phone, but when I try to do Gapps it says insufficient space on system partition. I used the stock gapps that was given in the link in first post. Size for the gapps is 600mb, am I doing something wrong?

---------- Post added at 04:49 PM ---------- Previous post was at 04:26 PM ----------

Nevermind, disregard my previous post. I just read your first post more carefully and you only tried out the minimal versions of it. Sorry for the confusion here. I will try the full version and if that doesn't work then I will do mini etc. I will post back once I successfully install a package.

(I know pico and nano work, but I want a version that includes more stuff so I will be trying the higher sized ones until I find one that works.)

---------- Post added at 05:45 PM ---------- Previous post was at 04:49 PM ----------

I have successfully installed the mini version of Gapps (full version resulted in space error). Now my next problem I face is that when I try making a test call (voicemail) the screen stays black and even when I try to press the power button nothing happens. I have to hold the power button until the phone reboots itself. I really love the smoothness of the 6.0 rom compared to the old kitkat that originally came with the phone, but I fear I may have to be forced to go back to 4.4. Am I the only one with this issue (I think it might be the proximity sensor)?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Yeah, some of the gapps are pretty big!

Also, another user had a proximity sensor problem. Read posts 81-85 for more info, but under ROM settings, you can set the screen to wake on volume buttons, that worked for him.

Hope that helps! :D

And great job flashing your phone! Welcome to the AOKP!

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] germ27:
Should I wipe the phone before Odin or only before installing the new rom. Do I need to have usb debuging enabled?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Germ27,

Great questions.

No, you do not need USB adb debugging, because you will be entering download mode, which is just for this purpose.

You also should not wipe your phone before using Odin. You will only wipe it after you made a backup in TWRP, but before you install the new ROM.

Clear as mud? ;)

We were all new at this once, so don't be afraid to ask questions. To keep this thread on topic, however, perhaps you should PM me if you have more trouble.

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] Kuropis:
Hi everybody.

I actually had to turn the proximity sensor off on my phone to get it to work. There is a crack over the sensor so the phone thought it was always by my ear hence a black screen. Turned the sensor off and no problems what so ever.

It's great to see more people using this ROM! It's been my daily driver since I installed it. Big thank you to AlaskaLinuxUser for all his time and hard work.

I'm considering trying the new kernel but still don't know much about how to install and how they work. I need to read more of the kernel thread before I do.

Side note I really need to update TWRP. Not to go off topic but can someone point me in the right direction so I can learn and get it updated?