yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great question pickandrew.

I would say it is a higher level beta version. I try to only release things that could be used as a daily driver. The only thing that absolutely does not work is video recording with the camera, but picture taking does work.

There are a few small things that occasionally error, like Bluetooth share, mtp, etc, as listed in the OP. However, these things mostly work, just occasionally error.
[T-Mobile Samsung Galaxy S 4] smartt699:
Oms?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great question.

No, no Oms. AOKP is trying to stick with CMTE, and CMTE is having some sort of problem, but they don't want to change everything for Oms, then have to change it back for CMTE.
[T-Mobile Samsung Galaxy S 4] darazor:
Short update. I have found this rom to be very stable. :fingers-crossed:

The hiccup I had mentioned earlier appears to be related to trying to install BusyBox as a couple of apps requested. This appears to to be somewhat related to November security updates and the newer toybox use by Google.:crying:

Really super battery life. :good:

Did not test bluetooth yet. :o -D
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for the feedback darazor!

It appears that the November security updates are also causing an issue with substratum, layers, and CM theme engines. One of those few times that the security update can actually be a step backwards for custom ROMs. Hopefully it will get sorted out.

For the battery life, is it better than marshmallow? Nougat is supposed to really optimize battery saving, I do so much testing, modding, and flashing, I don't get the usual day to day use battery specs.
[T-Mobile Samsung Galaxy S 4] darazor:
ALU, I kind of thought that when I saw the oms post and your response.

Battery life is great but as to better that MM -hard to say. I am running with very few apps so as to minimize conflicts/unknowns. And, I usually have Xposed installed, that is an unknown in both directions.

I want to avoid the I wish therefore it is syndrome. So, at the least, I would say it is very, very good. As an aside, it is very responsive as well.:cool:

I hope to see other posts because this rom is very worthy of an install. And, the feedback is so useful to us all.

D
[T-Mobile Samsung Galaxy S 4] darazor:
ALU

Quick update.

Short test of Bluetooth call via GPS worked fine. Not a long test just for verification.

One other observation that I keep forgetting to mention.

Settings > Status Bar > Battery status style - icon landscape and circle tick options do not work; the icon remains an upright batter. Just for completeness sake.

D
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for the info D!

I am really glad the Bluetooth is working, especially with all of the mm Bluetooth troubles.

I'll check on the battery icon settings, thanks for helping by pointing it out.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Video recording update....

Hey everybody, just a quick note on the camera video recording situation.

There is a problem with the device trees or blobs that keeps the video recording function from working in Nougat. Hopefully, those that are far more skilled than myself will be able to get that fixed. I know there are several people working on it. I just do not have the skill set to fix that at this time.

That being said, while the pros work on a fix, I have come up with a workaround. (Read: hack.) I am not a very skilled programmer, but here are some screenshots to give you an idea. Essentially, I am opening the camera and displaying it on a surface view, then I am using some low level commands to record that screen. Because of this method, there are a few things to note:

- This app requires root permission.

- Before running the app for the first time, you must go to Settings->Apps, and give this app permission to use the camera, microphone, and write to storage.

- Leaving this app after starting a recording will cause the app to record your screen and save the output as /sdcard/Pictures/video.mp4

- You can choose between 1 minute or 3 minutes, however, you can't change a recording time or stop the recording once it is in progress.

- The camera takes normal looking pictures, but the video looks a little stretched.

- Version 0.8 has no audio recording yet.

This is a standalone app that you can install just like any other app. No zip flashing, twrp, mods, etc. It saves your pictures and video recordings as (#ofmilisecondsofday) .jpg and .mp4 respectively in the /sdcard/Pictures folder. Clicking on the 1m/3m icon switches from 1 minute to 3 minute recordings. Clicking the camera icon takes a picture, and clicking on the recording icon starts a video recording based on your chosen 1m/3m setting.

Anyways, it isn't that great yet, but if you want to play with it, or see a theory to concept, here it is:

http://www.mediafire.com/file/4cl9o1t5no9cf3n/S4camera_0.8.apk
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New kernel is up in the Nougat Kernel thread!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
S4camera version 0.9 is up:

MediaFire link: S4camera_0.9.apk

https://www.mediafire.com/download/2xrel675ontbukg

Now you can stop a recording while it is recording!

The record button changes to a stop button during video recordings, allowing you to stop a recording while it is in progress.

There is still no audio recorded, and exiting the app during a recording causes your screen to be recorded.

Even though you can stop the recording, a video cannot be longer than three minutes.

Merry Christmas!
[T-Mobile Samsung Galaxy S 4] darazor:
Thanks ALU.

Something seems wrong with new 0.9 .APK It is only 68 Kb vs 1.24 Mb for 0.8 and installer says file is corrupt.

Unless I'm doing something incorrectly. Just thought I'd let you know.

Don't rush to fix, have a great Christmas. -D
[T-Mobile Samsung Galaxy S 4] nmb52:
urgh... I found the problem and have it fixed. With Android 6+, due to permission changes, Doggcatcher rearranged where storage is allowed. I moved the files where Doggcatcher wants them, and now it is happy. Between being too tired, unaware of the permission changes, and distracted by having to copy off the SD contents, then restore them, before I could even get the SD card to properly show up as external storage, I was not seeing the obvious right in front of me. My apologies for the distraction, and thanks for the gracious response.
[T-Mobile Samsung Galaxy S 4] arikdahn:
Thanks ALU. I did this and it appears the lowest global offset clock the kernel settings app will apply equates to 895 mV on the lowest frequency range. Any attempts to go lower will not save after a reboot despite many different approaches (overclock, reboot, underclock, reboot, etc.). Again I am doing global changes.

However, it DOES appear individual clock-range voltage settings can be offset lower effectively and it will save after a reboot. I was able to get 384 MHz down to 855mV. To me this does not indicate a functional limitation issue so much as a problem with the app's boot up script commands for global offset. As it seems time-prohibitive to experiment in this fashion changing individual clock ranges, I noted the phone spends the vast majority of its time in either the lowest (idle, sleep, etc.) or full-throttle frequencies. I dropped 50 in both and so far seems pretty solid. I will probably be taking the normal approach from my KToonsez kernel for the Sprint S4 wherein I drop voltage 5mV a day and testing for oddities. As soon as something bizarre happens, I back off and stick to those voltages.

I think this will likely occur around 835mV/1190mV min/max but we will see!

Maybe someone will have a chance to see if they can replicate my problems.

UPDATE: The thought occurred to me that this is traditionally used for what purpose? You all mentioned overvolting, but what benefit does this serve? I have never known anybody to overvolt, and the reason for these utilities in my experience have been less heat production/battery life increase/ and battery reliability benefits. In the past, it was the objective to get it down to the bleeding edge right on the functional side of instability for the most benefit.
[T-Mobile Samsung Galaxy S 4] darazor:
arikdahn,

Having missed what it was you were trying to accomplish at first, I now understand what and why you are doing these voltage changes. I would have been interested in seeing what actual battery improvement is the result from the initial settings. However, the process seems a bit long. Perhaps you can keep us all updated with the progress.

As for overvolting, the only reason I am aware of is to achieve a stable overclocking state of the processor. Given that the S4 is a 32 bit processor and 64 bit phones are plentiful that reason seems to have little validity now as most games would run poorly if at all other the basic arcade type.. I am sure that someone may wish to OC/OV just because they can and there is no harm in that.

I look forward to any results that you may wish to post. -D
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Again, great questions.

Typically, people use voltage control as you suggest: for decreasing voltage (under-volt) to get better battery life. You may wonder why anyone would over-volt, or increase the voltage.

Check out this file:

https://github.com/alaskalinuxuser/...bacc292b56/arch/arm/mach-msm/acpuclock-8064.c

In this file are a series of tables, labeled PVS0 through PVS6. Each table is for the same processor chip of different qualities. The one in my phone is a PVS3. Look at your stock voltages in KA, and compare with the table for your PVS quality number.

Some qualities require more voltage in order to deliver the same performance. But even within quality ranges, not all chips are created equal.

Increasing voltage (over-volt) will increase what is known as signal strength. Increasing signal strength increases stability.

Cars and trucks come from the factory with preset conditions for the fuel to air mixture. Since they engineered the vehicle, they must know the "best" mixture, right? Well, for the average driver, they do. That is their target, the average driver. But some drivers want to go mud bogging, and others want to have low riders. These are not average drivers. These non average drivers can argue all day long about pros and cons of every aspect of their vehicle, but ultimately will do their own thing, that which works for them.

Likewise, of you are reading this, you are on XDA. And just by virtue of being on XDA, I can assure you, you are not an "average" cell phone user.

My goal is to give you the tools to make those decisions yourself. Over? Under? "Stock"? (Not technically stock, more like AKLU stock.)

More stability, or more battery savings? It might depend entirely on the quality of your chip too. (By the way, PVS3 or 4 are supposedly the most common chips, as that was their " target " goal.)

Long answer that touched on, but perhaps did not answer your question fully. Hope that helps, and I love kernel discussions. :D

P.s. I'm not an expert. Many disagree with me. You can find something on Google that agrees with any theory you have, doesn't always mean it's true..... ;)

Best thing you can do is try it yourself, but be careful, voltage controlling can literally let the magic smoke out. And once the magic smoke comes out, you can't put it back in.....
[T-Mobile Samsung Galaxy S 4] jmolisco:
how to add google account?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Jmolisco,

Did you install the gapps package in TWRP? Usually, after installing gapps, the first boot will ask you for your google account information.

If it did not, or if you are adding multiple google accounts, then you can go to settings, accounts, add. Then choose a google account and fill in your information.

If you cannot choose google account, then you need to install the gapps listed in the op instructions. Let us know if you need more help.
[T-Mobile Samsung Galaxy S 4] arikdahn:
Thanks guys.

AKLU, funny you mention this. For a couple of years I was an aftermarket automotive e-tuner for mazda and GM vehicles so I can definitely agree that the way "they" want it isn't necessarily the best. Go figure, I mess with cars too.

So far I am down to 835 min and 1195 max without any negative repercussions. This would (theoretically) indicate close to 9% change at idle and a little bit less at full throttle. As it seems percent based there is probably still more wiggle room and a little more up top. So I'm still going in this fashion and am just kind of doing some loose interpolation to the ranges in the middle. Will keep you posted.
[T-Mobile Samsung Galaxy S 4] mkmanu:
My setup went ok except the phone keyboard doesn't work. I have "Android Keyboard (AOSP) has stopped" problem. Please help!
[T-Mobile Samsung Galaxy S 4] darazor:
mkmanu, 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.

-D
[T-Mobile Samsung Galaxy S 4] arikdahn:
So far this is where I am.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Sorry to hear you are having trouble. I do agree with darazor, I need some more info to be able to help you.

Are you using an m919? Clean flash, full wipe? Hopefully we can get down to the bottom of your issues.

Nice work! Perhaps others can reap the benefit of your labour! Thanks for sharing. Are you gaming, or just coasting with this setup? Avrg battery life improvement? (Plus screen on time).

For the group: the maker of greenify made an open source rootless app that has similar battery saving function. Any body try it yet? I'd test it out, but I am busy with S5 kernel improvements. (They asked for kcal.) It's called prevent:

https://xdaforums.com/showthread.php?t=3559151
[T-Mobile Samsung Galaxy S 4] darazor:
Hope your S5 work is progressing well.

After a look see, checking the posts but not a test it seems a bit awkward to use. Perhaps not quite ready for prime time?

My preference is to use App Ops(Qixingchen) and MyAndroidTools(wangqi) to restrict permissions, stop "start on boot", restrict services and activities. Together with AKLU kernel etc., I am very pleased with battery time. I would be interested in anyone else giving their opinion if they have time to give it a look see. Always a plus to have other choices. -D
[T-Mobile Samsung Galaxy S 4] mkmanu:
Thanks for the reply. My 1st time registered and using the forum so yeah I forgot to mention my phone details :D I have the T-mobile Samsung Galaxy S4 SGH-M919. This custom rom works very good for me now. The microphone on Voip apps (viber, skype) works which is nice since for other custom roms I've used the mic's not functional so the caller couldn't hear me, only I can hear them. Android auto works on my Accord that is the sole reason I want to flash a custom rom for my M919 since Tmobile takes forever to release Lollipop. Other functions work fine. I do have to change the date/time manually since it's a known bug. Phone performance is superb compared to the Tmobile Kitkat.

At first, I flash the rom and a lollipop Gapps which causes the "Setup Wizard keeps stopped working". I couldn't pass the initial setup to get to my home screen. I tried many methods like connect to wifi/4G, allow all permission for Setup Wizard, clear cache for the app and dictionary but it didn't work. I think incorrect version of Gapps is the problem since it's a nougat rom.

For the second time, I only flash the rom. I pass the initial screen. Everything is fine until I update the Gapps which is included in the rom. After the update the OS is buggy. "Google app has stopped working" message keeps popping up and phone restarts randomly every few minutes. Then I flash the stock nougat 7.1 Gapps but the file size is too big (~700mbs) so there is not enough space during install. Then I download the micro version (~200mbs) and phone is good now.

Thank you for the rom. I'm very amazed my galaxy S4 can run nougat :fingers-crossed:
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for the kind words!

I see. Well I'm glad it is working for you now. However, I think you should do a full wipe and reinstall the room and correct gaps.

You said that the built in gaps, which "came with the ROM" were not working. This ROM comes with no gaps at all. So if you reflashed the ROM, and gaps was still there, then it was a dirty flash, meaning you have left over bits (pun intended) that should not be there.

It is working now, and that may not be needed, but I recommend it. In twrp, do a wipe, then install this ROM, and the nougat gaps. It should clear out any "leftovers", but it is your phone, so if it is working, you can just go with it.

Either way, I'm glad you like the ROM! Welcome to our group!
[T-Mobile Samsung Galaxy S 4] darazor:
mkmanu

Just a quick clarification in case you don't fully understand which Gapps

On the Open gapps download site you want the top selection for Platform, ARM

Under Android you want, 7.1

and under Variant if you want to be able to use google assistant you will need at least nano

on todays downl;oad 15 Jul 2017 that will show a size of 179.41 MB

-D
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Good point about nano for Google assistant!
[T-Mobile Samsung Galaxy S 4] Nashat1990:
Hi Bro ,, I've flashed the room and the google apps and every thing just work fine but the kernel won't flash .. any suggestions ,, I love this Rom and want to flash the kernel for better battery life .. thanks for this awesome rom ...
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for the kind words Nashat1990, I'm glad that you like the rom!

As for the kernel not flashing, what exactly is happening. You will need to be very specific so that we can help you.

1. What kernel file are you flashing? It should be this one: https://www.mediafire.com/download/d8ex89k3wwcict3

(20170619 version).

2. Is there an error message in TWRP? What exactly (word for word) does it say?

3. What version of TWRP and Phone do you have, model, bootloader, etc.?

4. Have you tried re-downloading the kernel?

Thanks, we need more information to be able to assist you.
[T-Mobile Samsung Galaxy S 4] we87:
Galaxy S4 Tmobile

M919

No simcard, using only as a play phone- however the keyboard suddenly stopped popping up. I was using "GBoard" from the playstore but have uninstalled it, now even the default AOSP keyboard doesnt pop up whenever im in a text field. (web url, application text window, etc) I do not get a error message or notification of something stopping, the keyboard just does not show. Have to power off and power on, then it will show for a few minutes and stop again. No idea why or what to try next.

aokp_jfltetmo_nougat_unoffical_2017-06-30_1213

Baseband M919UVUFNH7

Kernel 3.4.112-cyanogenmod

Build date Jun 30
[T-Mobile Samsung Galaxy S 4] darazor:
Hi we87

Just a few questions to save ALU from asking and to help resolve your issue.

Did you install Gapps and if so which one?

Did you use the kernel that came with the rom or did you flash ALU's custom kernel? If custom which one?

Did you use TWRP and which version?

Was this a clean install or dirty? (coming from another rom you should clean install.)

Did you try re-flashing?

One observation. You're modem is an old version and probably should be updated but I don't believe that is the issue.

ALU will no doubt have a greater insight but these preliminaries will speed the process.

-D
[T-Mobile Samsung Galaxy S 4] we87:
thanks for the quick response. Sorry didnt know to add all this detail.

YES installed Pico gapps

YES Kernel that came with rom

YES I used TWRP (3.1.1-0)

I am not sure clean or dirty? Was on 4.4.4 and installed twrp then selected this zip

NO I have not tried reflashing yet
[T-Mobile Samsung Galaxy S 4] darazor:
we87

On the 1st post of this thread there is a box that gives these instructions:

-Download ROM and gapps, and put them on your phone or external storage.

-Reboot into recovery mode - TWRP (I personally installed this using 3.0.2-0).

-Backup what you had. (Just to be safe.)

-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)

-Install Rom.

-Install Gapps. - Optional

-Reboot to system and enjoy!​

-OPTIONAL - After first boot, then go back to recovery and install the AKLU kernel.

I think the TWRP version is now the newest 3.1.1 also (I use 3.1.1) but that part was not updated on the post. Everything else is valid.

Give this a try and let us know. Also, look at my post above #195 re google assistant. But not related to your issue.

-D
[T-Mobile Samsung Galaxy S 4] we87:
I did a wipe when I installed the rom, but I just redid it and selected everything under "advanced wipe" in TWRP and wiped everything. Now hopefully after the wipe and the reflash I should be okay. If I get a keyboard issue again I'll let you know. Thanks again for the quick response.
[T-Mobile Samsung Galaxy S 4] Nashat1990:
The kernel won't flash .. @nashat1990

You are welcome Bro.. You deserve more than that .. I'm trying to flash AKLU kernel and i have installed it from the link that came up with the rom as the instructions says ..

I'm using that newest TWRP version

To be honest i don't know if the kernel is flashed or not because the massage says :

ALKU Kernel

Complete

Script successed, result was complete

E: UNKNOWN command

Update partition details

Done.

That's the massage exactly

Something else.. When the mobile is starting there is a small massage above samsung logo says

Kernel is not seandroid enforcing.

So sorry for bothering you with my questions

Thank you again for your awesome job

Lots of respect
[T-Mobile Samsung Galaxy S 4] arikdahn:
I think this means the kernel installed. Go into your apps and look for the kernel config app. If it has a CPU Voltage section, you got it.

In other news I have run the values from my previous post for a while with no issues. One could keep going, but this already represents a sizeable decrease which should translate to battery and heat benefits. Hard to say if I notice them personally but I do feel like the heat output has decreased. I KNOW it has far better battery life by a few hours over my Sprint S4, but it is running a touchwiz based 4.4 ROM (wicked9). There are too many differences to consider, and it just may be android 7 optimizations. Anyway these values are probably usable by most folks and you would also have no issues.

Obviously your mileage may vary depending on usage. The longer the screen stays on, the more diminishing the returns of any optimizations of other hardware/software as the screen uses substantially more juice than anything else on a device.

As a question to anyone who may know. The "deep sleep" section of the overall CPU states. Is this something unique or does it follow the voltage rules of the minimum clock speed (384)? My phone spends the vast majority of its time here. If this is some arbitrary state we cannot configure?