yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] darazor:
If the question was good, the answer was a Rio Olympian achievement. (Yea, i really wrote that!). I always look forward ;) to your answers because they are so complete. Even my OCD gave a sigh of relief. I will relax now and enjoy Perseids or just take one the usual way.

Except one thing, I usually try to avoid any sod references. Thanks, D

Sent from my AOKPMMALU semi-smart but getting smarter every day phone.
[T-Mobile Samsung Galaxy S 4] timz1313:
New York new York. [emoji12] [emoji12] [emoji12] [emoji12]

---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------

Ty..buddy..
[T-Mobile Samsung Galaxy S 4] darazor:
Since you didn't reference a prior post, there seems to be some level of ambiguity relative to the exact meaning of YOUR post.

Some of us were wondering if you might attempt to clarify your point?

Thanks for bearing with us.

Sent from my AOKPMMALU now with more voltage options than a MK48 mod7 ADCAP, semi-smart phone.
[T-Mobile Samsung Galaxy S 4] timz1313:
No problem. Ninja
[T-Mobile Samsung Galaxy S 4] Inferno9999:
I had to stop using the S4 because the phone's screen would get very hot to the touch (its mainly the upper portion of the screen). This phone was bought on eBay and I felt like I was ripped off since I got it at 140. There was many otheres but this one seemed to be kept in excellent condition and it is except for the hot screen. Is anyone else out there experiencing the same problem? I checked with CPU temp and the phone reaches 60-65c, is my device defective? :'(
[T-Mobile Samsung Galaxy S 4] redx64:
i am getting a lot of restarts on the new rom. Is there a way to diagnose why this is happening so i can see if its the temperature or something specific?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Well, that could be a GPU/CPU problem. Here is my recommendation, try these in order to see if either help:

1st - Set your GPU to ondemand governor and set the max for 128 MHz. This is not ideal for use, but then you can try this for a day or two and see if the phone gets hot or not. If the phone still gets hot, this rules out the GPU. If the phone does not get hot anymore, then your GPU may be burning up. You could keep using the phone with the GPU frequency set lower, like 320 MHz or so.

2nd - Set your CPU to ondemand governor and set the max frequency for 1026 MHz. This is not ideal for use, but then you can try this for a day or two and see if the phone gets hot or not. If the phone still gets hot, this rules out the CPU. If the phone does not get hot anymore, then your CPU may be burning up. You could keep using the phone with the CPU frequency set lower, like 1350 MHz or so.

3rd - In the kernel adiutor app, set the thermal temperature limit to 58 C. This will throttle back the performance to keep the phone cool. I say use this option last, because other things may be affecting the phone heat, like the radios. This will only cut back the CPU frequency to compensate for a hot phone.

Let us know if any of these work, and good luck!

Yes. In the kernel adiutor app, you can click on settings. Under settings is debugging. There are 3 options there. Just after rebooting from a crash, click to save all three files and attach the files to a post here or send them to me in a PM, and we will take a look. Also, please answer these questions:

Question: Have you adjusted any voltages for the CPU/GPU?

Question: Are you using Xposed?

Question: You mention temperature, does the phone get hot?

Question: Have you tried using the previous post # 203 to find your PVS#, and what is the PVS#?

Question: Which governor are you using?

Also, there is a newer version of the kernel in the kernel thread, perhaps you should download that and see if it works any better?

We are here to help, so let us know what the results are! :D
[T-Mobile Samsung Galaxy S 4] darazor:
Few quick thoughts.

1. All versions of the rom or just the current

2. Any app(s) that runs a lot in the background

3. Screen brightness all the way up or low

4. Have you tried to go to a lower clock speed on CPU and/or GPU

5. What kind of case is the phone in

6 Is it hot only when screen on or screen off too

7. Have you changed any voltages

Those and other things which don't immediately come to mind you may have considered but I ask because you have the phone and there isn't much info for us to draw an inference from except the heat issue.

I would suggest that you try a number of scenarios (if you haven't) and let us know the results.

This is not in any way a criticism just an attempt to get enough info to offer some helpful suggestions.

I'm sure ALU will have much more incite. D

I see he did!
[T-Mobile Samsung Galaxy S 4] christoophat:
In my experience w/ my S4 over the course of trying many different ROMs, it seems that I've always had the most issues using "tweaked/optimized" kernels, with little or no real world benefit. Obviously, we users all use our phones differently, some as "just a phone" others to see how much performance can be squeezed out of our aging devices. For me a stock kernel, & a bloat free ROM is perfect.
[T-Mobile Samsung Galaxy S 4] Inferno9999:
Could my heat problems be a result of living in hot area. It reaches 90+ here, I have noticed that my phone doesn't get as hot if I disable cell data and use wifi only.
[T-Mobile Samsung Galaxy S 4] darazor:
Well, if you are outside in the bright sunlight in 90-degs there is no doubt that would have some effect. But, having said that, it would be very helpful to us if you try some of the things previously mentioned and relay the results.:fingers-crossed:

It was 96-degs in my local area yesterday(not in my house); I was in and out - no discernible heat problem. Thanks. D
[T-Mobile Samsung Galaxy S 4] Inferno9999:
I will try the suggestions, but before I do that what is a normal cpu temp range for our variant of the s4?
[T-Mobile Samsung Galaxy S 4] darazor:
Well my temps usually run between 40 and 60 deg C unless I'm doing a full backup. That's my "normal" it may not be the same for everyone. It most definitely will depend on the type of phone activity. High Cpu/Gpu use will up that of course. You get the idea though.

Perhaps some other people can give their ranges; I think by and large they are the same.

D
[T-Mobile Samsung Galaxy S 4] timz1313:
I can help you out you need your time MSN Class C codes...... and from there it's almost any less of what you can do with it... this is a new release with the hell I'm ordering it.. . It has a 45 day trial. For free check it out if you guys want it rocks...........................bbbbbbb . ....................ssssdssss......

---------- Post added at 01:47 AM ---------- Previous post was at 01:46 AM ----------

The master of the disaster

---------- Post added at 01:52 AM ---------- Previous post was at 01:47 AM ----------

The keypad on the dialer still isn't working correctly you can't delete messages on your voicemail there's a glitch there................. now I need some expert developer you know to tie the ends up and figure out what's going on.......
[T-Mobile Samsung Galaxy S 4] timz1313:
Experiment

---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------

..........ooooooo.........

You

---------- Post added at 08:07 AM ---------- Previous post was at 08:06 AM ----------

[emoji15] .......[emoji201] [emoji201] [emoji201] ....

---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------

Exposed ambient display module connect............ssssssssss....... Loll.........
[T-Mobile Samsung Galaxy S 4] gizm0luvsu:
I am not sure if this counts as a bug because with these roms bluetooth is known to cause issues . One thing i have noticed is that my bluetooth works great i can turn on and off and use headphones to listen to music fine. Sound comes in great as i have viper4android installed and it works great. The issue comes in during a phone call. if i have bluetooth on and a headset connected bluetooth controls as well as being able to hear anything does not work. Everything plays out of the handset as if i did not have anything connected. Also you can not hang up the call until you turn off bluetooth. Then the cell service does a reset cycle and comes back. I know bluetooth has always been an issue and i rarely use a bluetooth headset for that function so it is definitely not a deal breaker. Just thought i would say.

Good work on the rom. It is the most stable i have tried out.
[T-Mobile Samsung Galaxy S 4] darazor:
See ALU posts 101 & 103
[T-Mobile Samsung Galaxy S 4] gizm0luvsu:
Thank you very much.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
They have updated the source to include the security patches for 20160805! I am syncing the source this weekend, and should be pushing out new builds early next week!

Have a great weekend everybody!

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] Arimetix:
Microphone

Can anyone tell me if you found any issue with the microphone while recording a video or voice? I tried CM13 and Resurrection Remix roms but I always had the same problem, the microphone recording is way too low and in the playback I almost can hear anything, just little whispers :eek:

I'm back to the stock firmware Android 4.4.4 and the problem was resolved, but I really loved Marshmallow!

So please, can anyone confirm me if in this rom all the common features work properly? (specially voice recording) :fingers-crossed:

Thanks!
[T-Mobile Samsung Galaxy S 4] darazor:
Animetrix

You are correct the volume is low. But, I did find it better with earphones than speaker. I installed Volume Booster app by GOODEV and it worked quite well. A slider on the app allowed a 58% increase but it was somewhat distorted. I settled at 26% and that was better. I didn't play around with any other setting. So, you may want to kick the tires and give it a drive around the block - see if it fits your needs. ALU may have better suggestions. D
[T-Mobile Samsung Galaxy S 4] Kuropis:
Looking forward to the update! Anything new besides the security?

Side note: Any plans on working on the new Android 7 when it's more available?

Thanks for the ROM and all that you do for our antique phones! :)
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Arimetix,

Thanks for looking at the AOKP!

This kernel supports Fauxsound, as such, if you purchase the Fauxsound app (unfortunately, it is not free, I don't make it or it would be), then you can adjust the microphone gain. Here is a screenshot:

But I would try the suggestion by [MENTION=2571065]darazor[/MENTION] first, because it is cheaper. I have already purchased Fauxsound, and you can adjust the microphone gain up to get better sound quantity and/or quality, depending how you adjust it. Adjusted, the volume seems normal to me.

Hope that helps!

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
A few small things, like how/where to display the date, and many behind the scenes items. They cleaned up some sepolicy permissions and the like, but nothing will change much for you guys.

As for Android N. They released the full source Tuesday (my time) last week. By God's grace, I have successfully built a boot image, a user/data image, and the recovery image for AOSP 7. However, this phone uses legacy ALSA sound drivers (which were old in Lollipop) that are giving me fits in Nougat. If I can get passed those errors, the system image will be complete and we can have a pure AOSP alpha.

Unfortunately, I am not as skilled, so it may be a while yet, but I am having fun learning "ninja" the new build system that completely changed the way I built ROMs before. They have made changes like outlawing cflags, so I have to make changes to all of my usual files and syntax.

Long story short, I am having fun learning a few new tricks, and it is a WIP.

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New build is up!

Praise God, another successful build!

The OP has been updated with the latest build, which includes the latest security patches, up to August 5th, 2016! Other than that, a few touch ups here and there, but most of the changes are behind the scenes this time. Many thanks to the AOKP team for the hard work that they do to implement new features and update the security patches!

The AOKP team also has implemented a new "old school" boot animation, so be sure to check that out on boot up! I have included both the "lighning" version that we have been using all along, and the "old school" version that they are using now, if you have a preference for one or the other. You can always copy this to /system/media/bootanimation.zip to replace it if you have a preference.
[T-Mobile Samsung Galaxy S 4] darazor:
Thanks for update! Again, very smooth. And yet again, I hope we are not monopolizing your time. While we all love the builds, we also know you surely must have yotta other things to do -much appreciated though.

Like the "Old style" animation as a change. Is it my imagination, wishful thinking, both or is the app prep faster (liking the new dark format and position at the bottom too)?

New AudioFX is a plus.

One thing I noticed. The kernel info in System Settings> About phone info has a date of Mon Aug 29 and the Kernel thread still shows the date 20160817 for the MM kernel. Are they in fact the same kernel or has that thread date and/or kernel not been updated yet?

Just an observation. -D
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
As always, great questions! You have a keen eye, my friend!

Yes, the app optimization and overall load time should be *slightly* faster. This is the first time I have compiled it with java 8. Previously, I was using Java 7. Java 8 compiled code can be 2% to 20% faster depending on the code, the task, and the benchmark. You can read about it here if you like:

http://www.optaplanner.org/blog/2014/03/20/HowMuchFasterIsJava8.html

As for the kernel, it is the same kernel, however, every time I perform a build for the community, I always do a clean build, so there are no "dirty leftovers". This means that the kernel is cleanly rebuilt at the same time as the ROM. It is built from the same source, though, so it is in theory identical except the date. Great observation, though!

Giving credit where due, though, the AOKP team came up with the dark theme bar at the bottom, and I also think they did a great job! :D

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] darazor:
Read the java benchmark article. Is the GC that is referred to Garbage Collector? I see it was written for build 45 while the current build I believe is 102. I don't know what version you are using or if that would make any difference. If so, presumably for the better. Nice article.

You are certainly correct, the Team deserves a great deal of credit. But, so too does Michael Tilson Thomas when he conducts the SAN FRANCISCO SYMPHONY in Rossini, Mozart or Gershwin.:highfive:

Re kernel, i find your attention to detail truly awe inspiring. Thanks, -D
[T-Mobile Samsung Galaxy S 4] nitroidd:
Hello! I love the work you've done so far with the ROM, in fact it had prompted me to try it out as a daily driver.

Everything appears to work well so far, however I noticed one thing interesting: when using any other app that requires voice (for example, Sound Recorder or Discord), it will be very silent when I speak into the microphone near the charging port... however, when I speak into the earset speaker, it is loud (not quite as clear of course since a speaker diaphragm isn't meant for recording voice, but rather playing back voice)

It seems as if the earset speaker and microphone inputs are switched when not using it in the phone app (it works as intended in a phone call). Could this be a kernel thing?

Also, if you're willing to do so, is there any avenue you can provide that allows me to donate for the amazing work you've put forth? You're so benevolent; you may not want it, but I insist!
[T-Mobile Samsung Galaxy S 4] darazor:
ALU does really quality work. And, if I read you right,

If you look back to posts 227 - 230 and also see post 27. I think you will find your answers. -D
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks, I'm glad you like it, and welcome to the AOKP! :D

Actually, anything is possible, however, darazor is correct, there are some good work arounds for the low microphone volume issue. You are correct in that the kernel does control amplification of the microphone in the form of analog gain. I have often considered turning it "up" in the kernel, however, then the end user could not turn it "down" if it is too loud.

The actual app control of which microphone to use takes place with a system call, or "intent" to use a device. Those are set in the device trees and within Android itself. You bring up a good point, though, and I will take a look, just to make sure.

To be honest, I sincerely believe that you guys give me too much credit. Most of the heavy lifting is done by the AOKP team. I simply tailor their work for our device, which God has been gracious in allowing that to be successful. Darazor is correct in pointing to that post. Thanks for the thought, but I can't take anybody's money. I do this for fun and do not accept donations. :)
[T-Mobile Samsung Galaxy S 4] nitroidd:
Woot!

Thank you both AlaskaLinuxUser and darazor.

I'm a complete idiot. I didn't realize that the S4 has two microphones, one on the top near the headphone jack (for speaker-mode/commands), and one at the bottom near the charging port (for regular handset use).

Of course, I was using those applications in speaker mode, which is why it was faint when I was talking to the bottom mic. I talked into the top microphone and it picks up perfectly!

All is working as intended; in fact, I don't think I'll need to download the volume gain app as I feel it sounds good to me.

Thank you both very much, I'll be hanging around! I can keep prolonging the life of my S4 before I really have to upgrade!
[T-Mobile Samsung Galaxy S 4] darazor:
Welcome aboard nitroidd. You're not an idiot you just made a small mistake. We all make them.

You sound enthusiastic and that's an important quality in this game. I (we) look forward to your posts. Good questions are good learning tools -everyone gains from them.

If you have time to read the previous posts, I believe you would benefit from them; I have. ALU's posts and answers are as informative and complete as any I have read on an xda thread. -D
[T-Mobile Samsung Galaxy S 4] masumbhuiyaa:
automatically turn off my phone.

this rom and kernel does not monitor battery level properly. also it turn off phone many time in a day. i installed this rom to enjoy mm and first charge facility.
[T-Mobile Samsung Galaxy S 4] darazor:
Thanks for your post. But?

You don't say anything about your phone, model, firmware, carrier etc. I don't have these issues nor has anyone else reported them. When reporting issues it is customary to give some specifics. Your profile does not say what your device is? Perhaps you could provide some details otherwise ALU or anyone else can't begin to help you.

I see that on your other posts "Resurrection Remix" and "Phone always crashing, even on stock firmware?" that your phone hasn't been "working right" all along!

Thanks, -D
[T-Mobile Samsung Galaxy S 4] masumbhuiyaa:
i am usiing galaxy s4 (sgh-m919) t-moblile

my current firmware is M919UVUFOK3, carrier -airtel

do you think turning off mobile even battery level up then 45 % , is a firmware problem.

yes firstly installed you rom now i have moved to "resurrection Remix"

always crashing phone app not my phone when i brows by "gesture anywhere.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Hi masumbhuiyaa,

Sorry to hear that you are having trouble! Thanks for giving AOKP a try!

It sounds like you have 3 problems, and perhaps if we talk about them, we can find a solution. Please let me know if I understand these correctly:

1. The battery does not properly charge, hold a charge, or is incorrectly reported, causing you to lose mobile data?

2. Your phone randomly reboots or turns off.

3. Using Gesture Anywhere feature causes the phone to get fault crashes.

It sounds like you have moved on to RR, which is a great rom as well. I hope that works out for you! The great thing about Android is that it is like ice cream, there is no wrong flavor, it is just a matter of preference. :D

As for the issues, if they continue when you change roms, which, from your other posts, it would seem they do, then the common denominator is the phone, the user preferences, or the apps installed. A few thoughts for you that may help you on your journey:

1. The battery.

- Our phones are a bit old. It may be possible that your battery needs to be replaced. Does it get hot or swell?

-Some apps prevent deep sleep and keep the phone constantly active, such as AnTox, the encrypted messaging/calling/chatting app. Other apps may be preventing the phone from going into a deeper sleep, and forcing the phone to stay awake, causing the battery to drain. If you look under your battery settings, you should see a breakdown of which apps are hogging the most battery.

-The modem turning off may be a battery issue, or it could be another settings issue. Perhaps you could check to make sure that you have not enabled battery saving mode for a high percentage. Does the screen change color when this happens, does the phone get hot when this happens?

2. The random reboots.

-A really good test for this would be to do a clean wipe of your phone and return it to stock configuration, and use the phone with the built in apps only for a few days. If it randomly reboots with the stock phone firmware, then it is not a software issue, it means that your phone has problems and may be dying. This could be related to the battery, but also may be a heat issue.

-If the stock firmware, with stock apps does not cause a random reboot, I would root it and install your usual apps and try that for a few days. If it reboots then, then it is an issue with some of the apps you use. Perhaps one of them has a problem or settings issue.

-If it still does not randomly reboot after testing those apps, then I would do the same with custom roms and see if the issue persists.

3. The gesture anywhere feature.

-I will have to check to see if there is a problem with that. I don't use that feature myself, so I will give it a try to see.

-An option for you may be to stop using the GA feature and see if your phone quality of use improves.

Again, no hard feelings for switching to RR. I hope that goes very well for you. It is my hope that if you still have issues, you can try some of the above and see if that helps. In any event, good luck!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
I tested out the gesture anywhere feature, and it is working great. No fc or reboots from general use. I will keep testing.

-AlaskaLinuxUser https://thealaskalinuxuser.wordpress.com
[T-Mobile Samsung Galaxy S 4] masumbhuiyaa:
3. The gesture anywhere feature. i did not check it for your rom. it happing with rr rom.

i just faced random turn off and incorrect battery level status when i used your rom. phone turned off when battery level 57% , i tried turn on my phone pressing power button. but did not turn on so plugged usb then turn on with battery level 42%!!!! i did not installed to much app after flashing you rom just installed v4A.

i always use fhilz touch 5.18.2jfltetmo recover and " clean wip to install new rom" feature when flash a rom.

but with rr mm 6.0.1 rom it's ok now. with rr rom i have installed L speed, busy box, nexus launcher, ES file explorer, ridmix keyboard, V4A, zenUI launcher, dictionary, google, google now launcher, and tested with minimum level 05%.

gesture anywhere is better for quick and fast access any app.