So apparently the choppy bluetooth audio issue is on the Note 4. Has anyone found or know of a solution to the problem? It pretty much only happens when playing games.
Are you using Wanam Exposed?
Yes indeed.
This problem is covered in other threads. Start by disabling exposed then go read up on the rooting thread.
I consider myself to be a thorough user of google search and also did a thorough search through xda, and found no indication this is linked to wanam. If you really wanted to help you could posted a link to where I could read up on this, instead of giving a general statement. You disposition is the reason why there are many posts on forums asking questions about things. If you cant given a confident answer, I would suggest not getting involved. But thanks at least on helping pin pointing this to wanam at least, assuming that is the case. So excuse me while I go do some searching for bluetooth issues and wanam.
So sorry I couldn't spoon feed you the answer. Good luck.
---------- Post added at 06:13 PM ---------- Previous post was at 06:02 PM ----------
Sitting waiting for a food order, found the post. This worked for me: http://forum.xda-developers.com/showthread.php?p=56122331
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
Oops, copy and paste fail there, disregard.
I hate wasting space and time on pointless things and also jumping to conclusions, but its obvious you have nothing to offer except smart butt comments lacking the smart part. I hate being short, but your link lead to the auto root thread saying dont install xposed because of shealth issues which were resolved with another xsposed module already. Even did a search through the whole thread for bluetooth, which yeilded no results. Even did a google search for choppy bluetooth and wanam and it brought me to this post I created. So do the forum a favor and stop wasting space with useless statements about things you dont know. Thanks.
The choppy Bluetooth has nothing to do with exposed. Having the same issues with non-rooted device. No solution though, sorry.
Sent from my SM-N910F
I'm not having any issues from either a Bluetooth headset or Bluetooth speakers. I'm rooted and user Xposed. Exynos version.
Sent from my SM-N910U
Yeah i guess it could be either related to being rooted or having xposed intalled. I contacted the developer of the rom I am using, which is dynamic kat. He is working with me now to find a resolution. Sad thing is I had the same problem with my note 3 running stock rom with xposed and root too.
BTW, the issues only kick in when playing any of the games I have installed.
It's a chronic issue with Samsung Phones (I had it on S3 even). Most common cause is phone going to sleep when the screen is off. That's obvious not the case with you, since you are playing games when it happens. One suggestion I saw that might work is turning WiFi off.
Same problem for me. Non rooted. I noticed it more using Deezer.
I found a fix. Does this happen when screen is off? When I changed kernel CPU Governor to ondemand, all Bluetooth choppiness has disappeared.
Brava27 said:
I found a fix. Does this happen when screen is off? When I changed kernel CPU Governor to ondemand, all Bluetooth choppiness has disappeared.
Click to expand...
Click to collapse
Will try with screen off. From memory my screen was on.
Where do u change this setting? Is this a root only change?
No issue for me stock on T-Mobile. I have noticed a very small chop - not even a chop, more like a slight immediate skip in the audio - randomly and very infrequently. I've been using a bluetooth speaker and my car's Uconnect system for several hours with this phone.
Just to keep things clear, I dont want to get this thread cluttered with random things that may not apply. But I have owned over 10 samsung devices and never had this problem until I rooted and installed xposed on my note 3 and 4. So I am sure it is because of either xposed or root. I doubt it is root. I will try going through different xposed modules to see if I can find the root cause. Also as I stated originally this only happens when playing games and only games. Not when the screen is off or playing any thing by audio other than games. If you have connection issues I would suggest making sure your bluetooth device is fully charged and there is no obstructions in the signal. Most bluetooth devices work best within 25 feet line of sight and keep in mind not all bluetooth devices are built the same. Some get less than 10 feet till they start having connection issues.
Same issue here...
On a completely stock 910U, no root - I get very intermittent Bluetooth connections to my car stereo. (My old S4 was / is perfect).
I also get intermittent function with my Fitbit. Most of the time the phone call notifications don't come through to the fitbit with the Note 4.
Very frustrating - both are key functionality for me.
If it looks like this is a phone issue then I'll probably return it and go back to my S4 until it's properly fixed - I am not interested in workaround with root or custom ROMs.
Cheers - N
sniickers said:
Just to keep things clear, I dont want to get this thread cluttered with random things that may not apply. But I have owned over 10 samsung devices and never had this problem until I rooted and installed xposed on my note 3 and 4. So I am sure it is because of either xposed or root. I doubt it is root. I will try going through different xposed modules to see if I can find the root cause. Also as I stated originally this only happens when playing games and only games. Not when the screen is off or playing any thing by audio other than games. If you have connection issues I would suggest making sure your bluetooth device is fully charged and there is no obstructions in the signal. Most bluetooth devices work best within 25 feet line of sight and keep in mind not all bluetooth devices are built the same. Some get less than 10 feet till they start having connection issues.
Click to expand...
Click to collapse
Did you find a solution?
Unfortunetly no. Only way to prevent it is running stock at this point. Not sure whats causing the issue, whethet it is root, custom rom, xposed, or any xposed modules. Maybe someone will eventually post a sound fix. I have heard of developers fixing it in their custom roms. But no posting of how the fix is created.
JagDave said:
The choppy Bluetooth has nothing to do with exposed. Having the same issues with non-rooted device. No solution though, sorry.
Sent from my SM-N910F
Click to expand...
Click to collapse
+1 same here haven't rooted yet its randomly choppy heard it was a Bluetooth 4 issue
Related
Ever since I flashed 5.0 to my 900V, my battery life has gone significantly down. Now this can be expected to some extent as I can no longer use Amplify to control NlpCollectorWakeLock (which is one of a few wakelocks going to town on my battery). One of the others is bluedroid_timer, which is part of bluetooth. I did some searching and I saw some other people with the same issue, but no answers. I use a Moto 360 on a daily basis, use bluetooth streaming in my car, and use bluetooth headphones at the gym, so turning off bluetooth isn't really an option. Bluesleep is another one that is spending a lot of time running. Anyone have any ideas? I've read a few threads where people mention this problem, but no one has posted any answers yet. Here is an album of my wakelocks.
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
MattE303 said:
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
Click to expand...
Click to collapse
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
MattE303 said:
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
Click to expand...
Click to collapse
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
https://code.google.com/p/android/issues/detail?id=87778
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
dirkdigles said:
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
Click to expand...
Click to collapse
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
MattE303 said:
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
Click to expand...
Click to collapse
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I did see that and I am a GasBuddy user. There was also mention of NFC, that was the first thing I looked at. Experimenting now with GasBuddy removed.
I'm not rooted so I can't check for individual wakelocks, I have to just run it for a while, then look at the "Awake" bar graph in the stock Battery app, so it takes while to see if anything changed. I really wish Google would give us the choice whether to let 3rd party apps see the detailed battery stats, locking that down made it so much harder to diagnose this kind of thing without root.
Glad you got yours sorted out!
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
ldeveraux said:
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No idea, but it's mentioned on their Playstore page in a recent app update:
4.6.6
Get deals while you are filling up by turning on Bluetooth.
Click to expand...
Click to collapse
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
MattE303 said:
No idea, but it's mentioned on their Playstore page in a recent app update:
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
Click to expand...
Click to collapse
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
MattE303 said:
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
Click to expand...
Click to collapse
I started experiencing the issue with excessive wakelocks from Bluedroid_timer on my stock Nexus 6 about a month ago. Noticed my battery life dropped significantly as a result. Used Permission Friendly Apps to see which apps were using BT and if I happened to install any around the time this problem began. Only new apps indicating BT connectivity were GasBuddy and Netflix. No idea why GasBuddy needs BT but I'm pretty sure I installed it about the same time the wakelock issue began. Good to know someone else saw the same thing. Just uninstalled it and waiting to see if the wakelocks stop.
Has anyone experienced any cut offs in audio when watching video of streaming music while all notifications sounds work? Tried to reboot phone, clean headphone jack and clear system cache but still doesn't seem to work. If anyone has a solution to this problem, leave a message.
Also: I have looked around and it doesn't seem this problem is that well known yet.
I am having the same issue! It's driving me crazy.
I'm experiencing the same issue . For me, it most likely to happen when i play game. I tried to watch youtube for an hour and a half to see if this happen, but it didn't do I'm not sure if its because of the game or the software/ hardware issue
Today I noticed that audio from videos (received via Whatsapp, or on YouTube) would fade out after a second or so. Reboot solved the problem.
I play YouTube streaming all the time in the car, and upto now it never did that.
What app are you using for music/video?
Stock?
I'm using Spotify or Amazon music and Youtube mainly. And this issue 100% will happen when i play Fire Emblem Heroes, i tried other games for ~15 min but this issue didn't happen
I've been having this problem the last few days. It started with Allo messages playing for two seconds then stopping. Now it's happening to YouTube videos I watch. So frustrating.
Found this thread over on Samsung community forums: https://us.community.samsung.com/t5...rd-id/GeneralDiscussion/thread-id/2913/page/1
Sounds like lots of people are taking their phones back for exchanges. Might be a bad soldering connection on the phone.
Jimmmycrackcorn said:
I've been having this problem the last few days. It started with Allo messages playing for two seconds then stopping. Now it's happening to YouTube videos I watch. So frustrating.
Found this thread over on Samsung community forums: https://us.community.samsung.com/t5...rd-id/GeneralDiscussion/thread-id/2913/page/1
Sounds like lots of people are taking their phones back for exchanges. Might be a bad soldering connection on the phone.
Click to expand...
Click to collapse
Have you restarted your phone? Fixed the issue for me, so I think it's just a software-related bug. Plus, it only happens when I open games or other media when I have music playing (for example.)
joeyvanhummel said:
Have you restarted your phone? Fixed the issue for me, so I think it's just a software-related bug. Plus, it only happens when I open games or other media when I have music playing (for example.)
Click to expand...
Click to collapse
multiple times....and I did the USB audio routing option. still doesn't fix anything.
only thing that gets the speaker to work is pressing HARD on the back cover of the phone about two inches above the speaker....and if that's the only thing that makes it work, it's gotta be an internal wiring/soldering issue
---------- Post added at 09:52 AM ---------- Previous post was at 09:44 AM ----------
jmallow said:
I am having the same issue! It's driving me crazy.
Click to expand...
Click to collapse
next time it happens, try pushing on the back cover of your phone....about an inch or two above the speaker
see if it comes back on
Jimmmycrackcorn said:
multiple times....and I did the USB audio routing option. still doesn't fix anything.
only thing that gets the speaker to work is pressing HARD on the back cover of the phone about two inches above the speaker....and if that's the only thing that makes it work, it's gotta be an internal wiring/soldering issue
---------- Post added at 09:52 AM ---------- Previous post was at 09:44 AM ----------
next time it happens, try pushing on the back cover of your phone....about an inch or two above the speaker
see if it comes back on
Click to expand...
Click to collapse
Man, do you think it's both a software bug AND a hardware issue, both causing similar problems?
The S8 really is a great phone when it works, but it seems to have a lot of infancy problems.
Think I found the solution.
Okay. First of all, thank you everyone for reply to this thread. I think I found the solution to the audio cut off problem. Every time when the audio goes off I just gave the phone a few Taps against my palm. So far, this method worked out pretty well for me.
The method I used was to held the phone by the top ear piece area and aimed the speaker area and just slapped it against my palm for a few times.
firedjj1 said:
Okay. First of all, thank you everyone for reply to this thread. I think I found the solution to the audio cut off problem. Every time when the audio goes off I just gave the phone a few Taps against my palm. So far, this method worked out pretty well for me.
The method I used was to held the phone by the top ear piece area and aimed the speaker area and just slapped it against my palm for a few times.
Click to expand...
Click to collapse
what a horrific "solution"
I have done similar.....press my finger hard against the rear panel...right above the speaker grille on the bottom of the phone.
so clearly, it's a hardware issue with wiring/soldering in the internals.
Here is a thread on the official Samsung foruns with LOTS of people complaining about the same: https://us.community.samsung.com/t5...rd-id/GeneralDiscussion/thread-id/2913/page/1
I tweeted that thread to Samsung and Samsung USA....no answer from either
I'm slightly shocked more people aren't complaining about this problem
Because your phones are defective and defective phones (out of the total number sold) represents a tiny percentage.
Just get a replacement.
Some of the comments on Samsung forums make it look like a software issue. If you restart your phone and it works again it is a software issue and the "tapping" thing is just a placebo.
If it was hardware (bad connection), rebooting would do nothing.
But that is what makes it so crazy, the behavior is mostly pointing to software but the tapping on the back has worked twice for me. I'm really curious about an official word (if we're that lucky)
same problem
I have the same problem with my S8. Couldn't find any solution until now.
I have written several times to Samsung support, no answer until now...
kick069 said:
But that is what makes it so crazy, the behavior is mostly pointing to software but the tapping on the back has worked twice for me. I'm really curious about an official word (if we're that lucky)
Click to expand...
Click to collapse
theohood said:
I have the same problem with my S8. Couldn't find any solution until now.
I have written several times to Samsung support, no answer until now...
Click to expand...
Click to collapse
I wrote Samsung support and Samsung Mobile on Twitter multiple times about his issue...and copied the link from the official Samsung forums that I linked on page 1...and they keep refusing to answer my question about it
I had the same issue with the sound I have a sim free s8 rang Samsung UK support yesterday they arranged a brand new phone which I received today via ups just swapped them over so I am very impressed with the there service
So far no issues
Sent from my SM-G950F using Tapatalk
same issue here in the netherlands.. samsung told me to send it in for repairs
guys sorry to inform that it is most probably a hardware issue since only few customers including me are facing this. If it was a software issue then more customers will come up with similar complaints. Bad luck we may all got the same batch of faulty phones.
The reason why i am saying is that i started the device in safe mode and the issue is still there. By tapping right above the speaker clears the issue and same vice versa while playing if tap above the speaker the sound again cuts off meaning to say IT'S AN HARDWARE RELATED THING
I'm not a developer or support any ROMs I just like spreading the good word and helping people when I can. I'm not responsible if your device breaks or you lose data. So make a TWRP backup if you are worried.
This is not a perfect method and it needs improvement so if we can work together and try to fix the issues maybe we can get full support from the OPs' of the note 7 ports.
You must be on MM bootloader, unlocked, rooted, with most recent version of TWRP to ensure everything goes smoothly.
Download most recent Ram Kernel for Verizon:
https://forum.xda-developers.com/note-4/orig-development/kernel-ramkernel-t3472138
Download aurora Verizon data fix:
https://forum.xda-developers.com/showpost.php?p=69066109&postcount=2681
Find a Note 7/S8 ROM that you want to try on the snapdragon note 4 thread:
https://forum.xda-developers.com/note-4/snapdragon-dev
1. Clean install desired ROM (wipe everything 3 times except SD card)
2. Flash datafix
3. Flash kernel
4. Wipe caches and boot into ROM
5. Play around with your new phone lol
If you do not have root for whatever reason download the su zip from nseven thread and flash it in recovery.
https://forum.xda-developers.com/note-4-verizon/development/note-4-grace-7-t3434155
These ROMs do not support Verizon apps including visual VM and MyVerizon. They also don't support Wi-Fi calling. Check the bugs of the ROM so you know what to expect.
If you are having issues check the original ROM thread for answers or post a question on here and maybe somebody can help.
The bugs that I know so far that are Verizon specific across all ROMs:
- MMS does not work on the stock messenger (*See below for fix)
- Phone FC when the person on the other end hangs up first (really want to figure this one out)
- Texts are sometimes delayed for some reason
Some ROMs might require you flash gapps for some reason so follow the op instructions for the ROM you choose, just ignore any modem or bootloader flashing instructions.
I've tried Norma ROM and Racerom. I've had the best experience with Racerom but that is just my personal preference. Any questions please ask.
Cheers!
Thanks to @chevyrhoads for all his time and effort on nseven. I cannot thank you enough sir! And thanks to all the other developers sharing these great roms, data fix, and kernel for everyone to enjoy.
MMS Fix:
1. Extract others.xml from nseven ROM found in system/csc folder and save it to your SD.
2. Edit the others.xml file and delete everything within the <FeatureSet> tags.
3. Paste this feature within the <featureset> tags:
<CscFeature_Message_ConfigMmsMdnTagName>X-VzW-MDN</CscFeature_Message_ConfigMmsMdnTagName>
and save the changes.
4. Paste the others.xml file in your current ROMs system/csc folder (In my case there was no others.xml file to swap or replace) and change the permissions of the file to 644 and reboot.
5. You should now be able to send MMS on the stock messenger app !
hey i flashed unchanced rom and the data fix + kernel but my phone still reboot if i use data
How did you fix the fc after phone call. Also, my phone shows 3g all the time and my text.mwssafes seem delayed. Im using Verizon note 4 n910v
I tried Race Rom and get a repeated Phone has crashed. I had better luck with the Norma ROM but had severe battery drain and after being off for a while, the phone wont turn back on, requiring a battery pull.
Any suggestions on the best ROM to try?
Sorry for not responded sooner
derSA7 said:
hey i flashed unchanced rom and the data fix + kernel but my phone still reboot if i use data
Click to expand...
Click to collapse
I guess that ROM does not work with this setup I'm sorry.
jBMWguy said:
How did you fix the fc after phone call. Also, my phone shows 3g all the time and my text.mwssafes seem delayed. Im using Verizon note 4 n910v
Click to expand...
Click to collapse
I cannot figure out what causes the phone fc. Maybe try flashing the 4G fix found on chevyroads nseven thread. I did notice that texts are delayed. After using racerom for a couple of weeks I've been getting reboots, freezes, and some texts not going through for a very long time. I recently flashed RR 7.1.2 but having issues with recording Snapchat videos so I'm probably going to go back to nseven tonight or tomorrow. I will add delayed texts to the bugs list.
bishop0114 said:
I tried Race Rom and get a repeated Phone has crashed. I had better luck with the Norma ROM but had severe battery drain and after being off for a while, the phone wont turn back on, requiring a battery pull.
Any suggestions on the best ROM to try?
Click to expand...
Click to collapse
From what I see Norma has the most potential on the snapdragon thread but idk after using racerom for weeks it started falling apart on me. I would now honestly recommend using Nseven for a note 7 port. I'm gonna keep this thread open so tinkerers/crack flashers can mess around and report their findings on here and maybe we can get a more stable method.
Sent from my SM-N910V using Tapatalk
jcip17 said:
Sorry for not responded sooner
I guess that ROM does not work with this setup I'm sorry.
I cannot figure out what causes the phone fc. Maybe try flashing the 4G fix found on chevyroads nseven thread. I did notice that texts are delayed. After using racerom for a couple of weeks I've been getting reboots, freezes, and some texts not going through for a very long time. I recently flashed RR 7.1.2 but having issues with recording Snapchat videos so I'm probably going to go back to nseven tonight or tomorrow. I will add delayed texts to the bugs list.
From what I see Norma has the most potential on the snapdragon thread but idk after using racerom for weeks it started falling apart on me. I would now honestly recommend using Nseven for a note 7 port. I'm gonna keep this thread open so tinkerers/crack flashers can mess around and report their findings on here and maybe we can get a more stable method.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
All of the phone FC's people are experiencing from the Note 4 S7/S8 ports, are due to the method / files along with the porting process to enable the S7/S8 ports to work with the Note 4's.
If you notice, you only receive a FC if the other party hangs up or disconnects first. If you "beat them to the punch" and end the call before the other party does, you won't receive the FC.
Another thing to note; when using a third party app for text messaging such as "Textra" for example. Let's say you are using Textra to text back and forth with someone and suddenly you decide to call them. If you use Textra's built in function to initiate the call, it doesn't matter if you are first or last to end the call, you won't get a FC. I've actually tested that theory out for another developer per their request, and was able to make calls with no FC's regardless of who ends the call first, just by opening Textra, and choosing to call someone from it's built in feature.
Just an FYI...
I'll possibly be taking over all future development for chevyrhoads, in reference to the Nseven ROM per his and my discussion just as soon as I'm back in the states, caught up with all the kids in college and school activities, kiss the wife, and feed the dogs, lol. I'm no android developer, nor am I pretending to be. "I'm only an android enthusiasts, and happy to be one." Retired Senior Software & Security Expert / Software Developer / SEAL, will do my best to keep the Nseven ROM up to date for everyone to enjoy...
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
p.s. @jcip17,
Those are some of the best & well written instructions I've come across. Excellently done!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Android.Ninja said:
All of the phone FC's people are experiencing from the Note 4 S7/S8 ports, are due to the method / files along with the porting process to enable the S7/S8 ports to work with the Note 4's.
If you notice, you only receive a FC if the other party hangs up or disconnects first. If you "beat them to the punch" and end the call before the other party does, you won't receive the FC.
Another thing to note; when using a third party app for text messaging such as "Textra" for example. Let's say you are using Textra to text back and forth with someone and suddenly you decide to call them. If you use Textra's built in function to initiate the call, it doesn't matter if you are first or last to end the call, you won't get a FC. I've actually tested that theory out for another developer per their request, and was able to make calls with no FC's regardless of who ends the call first, just by opening Textra, and choosing to call someone from it's built in feature.
Just an FYI...
I'll possibly be taking over all future development for chevyrhoads, in reference to the Nseven ROM per his and my discussion just as soon as I'm back in the states, caught up with all the kids in college and school activities, kiss the wife, and feed the dogs, lol. I'm no android developer, nor am I pretending to be. "I'm only an android enthusiasts, and happy to be one." Retired Senior Software & Security Expert / Software Developer / SEAL, will do my best to keep the Nseven ROM up to date for everyone to enjoy...
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
p.s. @jcip17,
Those are some of the best & well written instructions I've come across. Excellently done!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Thank you @Android.Ninja ! You made my day with this post. If you need a tester or any assistance please just ask. I'm a decent problem solver lol. Also that is a great find using textra call feature doesn't FC the phone. We must keep these great phone alive!! If it's possible I ultimately would like to create a perfect datafix for all these ROMs so we are free to choose any port. I'm positive it is not as easy as it sounds but it's wishful thinking. I figured out which CSC feature enables mms on the stock messenger. I'll post it in the OP.
Sent from my SM-N920V using Tapatalk
Replied to the OP instead of editing it. Disregard this post lol.
jcip17 said:
Thank you @Android.Ninja ! You made my day with this post. If you need a tester or any assistance please just ask. I'm a decent problem solver lol. Also that is a great find using textra call feature doesn't FC the phone. We must keep these great phone alive!! If it's possible I ultimately would like to create a perfect datafix for all these ROMs so we are free to choose any port. I'm positive it is not as easy as it sounds but it's wishful thinking. I figured out which CSC feature enables mms on the stock messenger. I'll post it in the OP.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
That sounds great, referring to the CSC! I'll put you on the Alpha/Beta Testers list as soon as I can. We may be able to get together and create a universal one in all datafix using aroma installer to allow the user to "Select" the ROM they would be using. The only issue would be of there was a major platform upgrade by the developer of the ROM of their choosing, but even so, we could just have it "Null Out" as to not harm or change anything etc. Yup I've got many of these note 4"s best phone for the money IMO.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Anybody experiencing lockups every once and awhile on any of the ports where you need to pull the battery? And when the phone boots up texting does not work until a proper reboot is performed? I was almost late to work today because my phone locked up overnight and that is my alarm lol. I'm back on nseven to see if its the ports or my phone :/
From what I remember this started when I was using resurrection remix 7.1.2 and ever since I've been having lockups on the other n7 ports.
Sent from my SM-N930V using Tapatalk
jcip17 said:
Anybody experiencing lockups every once and awhile on any of the ports where you need to pull the battery? And when the phone boots up texting does not work until a proper reboot is performed? I was almost late to work today because my phone locked up overnight and that is my alarm lol. I'm back on nseven to see if its the ports or my phone :/
From what I remember this started when I was using resurrection remix 7.1.2 and ever since I've been having lockups on the other n7 ports.
Click to expand...
Click to collapse
I'm interested in nseven Rom and heard good things about it. Could you suggest it as a daily? I'm on kyubi note 5 port.
jafferkhan said:
I'm interested in nseven Rom and heard good things about it. Could you suggest it as a daily? I'm on kyubi note 5 port.
Click to expand...
Click to collapse
That's nice to hear you're on Kyubi, thats my baby. There are some minor-ish issues with nseven, t9 dialing does not work, the auto brightness does the opposite of what it's supposed to do (sunlight dims the screen, darkness makes the screen brighter), fingerprint doesnt work, and always on display causes a brightness issue where you cant control the brightness (just untoggle AOD and brightness can be controlled). And for me I've been having intermittent issues with data where my 4g icon blinks white then dims to grey then back to white nonstop. When this happens I cannot use data until I reboot. Other than that the note 7/s7 software is awesome and everything else works from what I can tell. How's Kyubi running for you? I kinda miss it lol
Sent from my SM-N930V using Tapatalk
jcip17 said:
That's nice to hear you're on Kyubi, thats my baby. There are some minor-ish issues with nseven, t9 dialing does not work, the auto brightness does the opposite of what it's supposed to do (sunlight dims the screen, darkness makes the screen brighter), fingerprint doesnt work, and always on display causes a brightness issue where you cant control the brightness (just untoggle AOD and brightness can be controlled). And for me I've been having intermittent issues with data where my 4g icon blinks white then dims to grey then back to white nonstop. When this happens I cannot use data until I reboot. Other than that the note 7/s7 software is awesome and everything else works from what I can tell. How's Kyubi running for you? I kinda miss it lol
Click to expand...
Click to collapse
That's a great analysis bro. Thanks for the feedback I really appreciate it. Kyubi is the best Rom for this phone period. I've tried all of them except nseven but kept coming back to kyubi because of its stability. It's fast, smooth and very good on battery. I missed the note 5 themes which I get here plus the theme store and more. I think kyubi is more of what a stock Rom should have been. I know it's developer is very good, everything works flawlessly, I've had zero issues on it since its almost 9 months that I've been using it. Close your eyes and flash it, it's that good!
Testing....
Sent from my SM-N930V using Tapatalk
I'm on Verizon now and if I get another VZW N4 I'll build a proper N7 or S8 rom with everything working as it should. other than Iris scanner and fingerprint scanner.
But just know that these international port Roms are not setup for the CDMA networks so they will not work right. Even these "fixes" are only partial things that are missing and there's more smali framework edits needed to make them work right. The best option is to build a Rom using the actual VZW software and this will solve most all of these issues. Been there done that with my UN5 and UN7 Roms. I have the S7 edge now but to be honest I'd much rather go back to the N4 running my ported N7 rom so I can have my IR blaster and removable battery. The N4 is the best phone in my opinion.
note 4 is died and is a new way to do this fast and easy
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.
Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.
piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.
Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )
Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.
supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!
I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.
dirtydodge said:
I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.
Click to expand...
Click to collapse
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:
jcrompton said:
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:
Click to expand...
Click to collapse
Yea i never video or WiFi call (ok maybe have yo WiFi call about 2 or 3 times a year) so losing those two things don't bother me. I've always turned off enhanced lte services since they introduced it simply because it drains more battery plus from what I've googled about it, it don't really pertain to anything i need. I am hopeful though that once people start to use this root method, we'll start to figuring out how to fix everything like normal.
I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method? I mean there are a few fun things to do but not worth a unstable system and 80% battery.
timmy10shoes said:
I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method?
Click to expand...
Click to collapse
Why do you say "it's not really root to begin with"? By doing this method you gain access to root files and to the heart of your phone. SuperSU installs and works, you are able to deodex, theme, modify all as you want if you know what your doing. Sure there are a few issues with it (battery limited to 80%, WiFi calling, and camera) but none of this will get fixed we work on finding out the issue, but root has always brought about some type of issue one way or another in locked bootloader devices. My plan with rooting my phone is to build my rom with the tweaks and mods that i like, run the ad blockers that i like, possibly install xposed (haven't used it in a while). One of the main purposes of root in my opinion is to make your phone the way you like it. I mean you can sit around and wait for someone to make the phone how they like it and then possibly share it with others or you can take the initiative to learn yourself. Not really root to begin with? It's root, just not how it used to be. I hope someone does figure out a different root method that don't render the battery to 80%, i wish i knew how to look for exploits (I'm currently trying to learn) but until then, this is what we have. What are your reasons for believing this is not a real root method?
timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
Click to expand...
Click to collapse
Well that's why I'm still hoping for a different root method they don't have to use leaked files. But i can say that this root method runs a lot smoother than the method we had to use in the S7. This method hasn't been out very long, but is say within the next few months we'll start seeing more development happening . Or at least i hope. I've just recently started making my own roms (i don't release them to anyone being as I'm still learning and can't give a lot of trouble shooting assistance) but it's fun for me to pass the time at work. (I have a real laid back job with nothing to do a lot of times lol)
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.
timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.
Click to expand...
Click to collapse
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.
I have developed a few roms myself for the Bionic and Razr. Its highly entertaining and I want it myself but there hasn't been true root since the note 3 I believe.
---------- Post added at 04:54 PM ---------- Previous post was at 04:53 PM ----------
dirtydodge said:
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.
Click to expand...
Click to collapse
I use unactivated devices. There is a ton on trial and error so I don't use my daily driver for that.
Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?
Don_Pachuco said:
Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?
Click to expand...
Click to collapse
No roms yet (on AT&T at least that i know of). Not trying to be rude but do you even search, see attached picture. Literally 4 post down from this thread.
I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.
Don_Pachuco said:
I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-note-8/how-to/n950u-odin-5-files-stock-firmware-t3715770
Help!!! Please help!!!!
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear
jforest3026 said:
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear
Click to expand...
Click to collapse
This is a thread for mods done after rooting, post questions about getting rooted in your root thread please.
https://forum.xda-developers.com/ga...nt/root-samfail-galaxy-note8-t3685340/page323
the %80 max battery issue
I've enjoyed a rooted Note 8(sm-n950u) Nougat7.1.1 for over a week via samFAIL method and am quite thankful to the samfail/pwned team for providing it.
The max battery issue is the only drawback as far as I've noticed so far. I have a nice and speedy phone that is devoid of bloating apps, and vendor/carrier garbage.
As far as the max battery issue, I've done some digging and haven't found a cure yet.
I've noticed a couple things.
in /efs/Battery and in /sys/class/power_supply/battery there is a file named batt_capacity_max that has something to do with the max battery limit which is obvious by name of course.
Notes:
1. You can not change the value in /sys/class/power_supply/battery/. You can edit and write the file without any error or sign of failure; But checking the file immediately afterwards, you'll find that the contents did not change.
2. You can change the file in /efs/Battery/, but the contents are reset upon reboot.
3. The file contains only a number.
In my case, batt_capacity_max contains the number 1000 regardless of the charged state. i.e. It is 1000 when the phone if charged to max, and it is 1000 when the phone is nearly drained.
I change the value to see if it has any effect, and it does.
I interpreted the 1000 as binary 8, and changed to number to 1010 (binary 10). Then I charged the phone only to find that I could not charge the phone past 17% eep! This wasn't a problem though as rebooting the phone or returning the file to its original value restored the function to normal(rooted normal, that is..max 80%).
I've also deleted the file, then charged the phone to find that there was no effect.
I then came across a slightly older xda thread charge to 100 snapdragon root(s8 sampwn)
The thread had a great number of contributors and provided a great deal of background info, but the method described therein has become obsolete or does not apply to the Note 8 i believe.
If anyone has discovered anything effective regarding the battery max limit, I hope they will contribute that info here, or at least link to an existing thread that I may have missed.
One thing I would like to understand is what processe(s) are being employed in this battery limit system. Is it merely a sub-function of the SafetyNet, or something else? I've filtered what I believe are the pertinent logs(dmesg and logcat) trying to find reference to batt_capacity_max but have come up empty.
I have't tinkered with this in a couple days, but I plan to get back to it tomorrow. Anyone has ideas or suggestions, please contribute. personally I don't really care wether I "fix" this issue as much as I am using this pursuit to glean a better understanding of the android/samsung subsystems relative to it. .. to fix it, of course, is ideal.
delete