The one thing I'd like to have on my P6Pro is native call recording, but I've always had a bad experience with custom roms - they have major drawbacks.
Last time I tried, I had LineageOS on the P2 XL, it stopped Google Pay from working, as well as Android Auto although no one else experienced that or knew why, and a year later, the phone went into a boot loop that only one guy repairing phones was able to fix just barely (flash-all stock rom didnt work for me).
I am very wary of custom roms due to stability, but if we can gain root level access and modify the kernel to add support for call recording without breaking the above mentioned things, then that'd be a big win.
Is it possible?
Coming from a OnePlus device, I terribly missed native call recording on my P6P. Best solution I found was to use SKVALEX Call Recording and shell out the $10 after the trial ended. The $10 fee is a one-time (I hope) lifetime fee. I recommend that as it gives me the same functionality I looked for with my OnePlus. You do need to root to gain access to all features, but that's it. No need to mess around with custom roms/kernels/magisk modules, etc.
No. There are no Dirty Pipe exploits that go further than proof of concept.
Just root and use Magisk modules for this kind of thing.
If your bootloader is locked (i.e. Verizon), just give up.
Carmageddon1984 said:
The one thing I'd like to have on my P6Pro is native call recording, but I've always had a bad experience with custom roms - they have major drawbacks.
Last time I tried, I had LineageOS on the P2 XL, it stopped Google Pay from working, as well as Android Auto although no one else experienced that or knew why, and a year later, the phone went into a boot loop that only one guy repairing phones was able to fix just barely (flash-all stock rom didnt work for me).
I am very wary of custom roms due to stability, but if we can gain root level access and modify the kernel to add support for call recording without breaking the above mentioned things, then that'd be a big win.
Is it possible?
Click to expand...
Click to collapse
If you keep the above mentioned (spyware/trackerware), then what are you gaining by going custom?
-- "google pay" is trackerware -- just add YET ANOTHER company that is monitoring all of your expenditures in order to generate targeted advertisements for you.
-- "android auto" is trackerware -- monitors your travels. Its also USELESS since your car radio should be able to do all that stuff without becoming a dumb screen for your phone.
There is a reason why gooble hasn't opened or documented the protocols used by these things, and its nothing to do with security and everything to do with making it impossible for you to prevent them from being data vampires.
Custom builds can be EXTREMELY stable, but generally not the mainstream CRAP where they just throw in a bunch of ill-conceived and poorly tested "features" and call it good. Like this "lineageos" you mention, which is a cesspool of brokenness.
Try out GrapheneOS. Its not a "feature" build. Its a "security" and "stability" build. Yeah, you lose pay and auto, but in exchange, you save your soul.
By the way, call recording can be done with Magisk (root) + "Axet's Call Recorder" magisk module.
elodin_89 said:
Coming from a OnePlus device, I terribly missed native call recording on my P6P. Best solution I found was to use SKVALEX Call Recording and shell out the $10 after the trial ended. The $10 fee is a one-time (I hope) lifetime fee. I recommend that as it gives me the same functionality I looked for with my OnePlus. You do need to root to gain access to all features, but that's it. No need to mess around with custom roms/kernels/magisk modules, etc.
Click to expand...
Click to collapse
And it has good audio quality in the recording, for both sides of the conversation?
I thought that was impossible since Google changed the APIs/kernel a few years ago, requiring custom kernel enabling that capability for call recording to work in new apps?
LLStarks said:
No. There are no Dirty Pipe exploits that go further than proof of concept.
Just root and use Magisk modules for this kind of thing.
If your bootloader is locked (i.e. Verizon), just give up.
Click to expand...
Click to collapse
Interesting, I didnt know thats achievable without going the custom rom/kernel path.
This rooting of the phone doesnt break Android Auto, Pay and OS updates?
96carboard said:
If you keep the above mentioned (spyware/trackerware), then what are you gaining by going custom?
-- "google pay" is trackerware -- just add YET ANOTHER company that is monitoring all of your expenditures in order to generate targeted advertisements for you.
-- "android auto" is trackerware -- monitors your travels. Its also USELESS since your car radio should be able to do all that stuff without becoming a dumb screen for your phone.
There is a reason why gooble hasn't opened or documented the protocols used by these things, and its nothing to do with security and everything to do with making it impossible for you to prevent them from being data vampires.
Custom builds can be EXTREMELY stable, but generally not the mainstream CRAP where they just throw in a bunch of ill-conceived and poorly tested "features" and call it good. Like this "lineageos" you mention, which is a cesspool of brokenness.
Try out GrapheneOS. Its not a "feature" build. Its a "security" and "stability" build. Yeah, you lose pay and auto, but in exchange, you save your soul.
By the way, call recording can be done with Magisk (root) + "Axet's Call Recorder" magisk module.
Click to expand...
Click to collapse
I hear you! Unfortunately I don't have an alternative for Auto until I get our car replaced with a Tesla - early Cybertruck reservation holder - still waiting..
And for Google Pay - well I find it indispensable when I forgot my wallet running to a store, or intentionally not carrying it.. its so liberating physically not to worry about it at all..
I will try Graphene once I switch to Tesla and wont need damn Auto anymore.
Carmageddon1984 said:
And it has good audio quality in the recording, for both sides of the conversation?
I thought that was impossible since Google changed the APIs/kernel a few years ago, requiring custom kernel enabling that capability for call recording to work in new apps?
Click to expand...
Click to collapse
Works well enough. Only two things wrong (and it one of them might just be in my head). 1. Volume for my voice on calls is only about 90% as loud as the voice of the caller on the other end. I can hear both plenty fine and I'm sure you will too, just a little noticeable the lower volume on my voice in the recording. 2. Not sure why but it doesn't record calls that use Direct My Call. I've tried them using bluetooth headsets, phone earpiece, speaker, nothing mattered. I think calls made with Direct My Call maybe don't register as normal phone calls internally on the phone and the recorder app doesn't work on them? Not sure, but I can live with those calls not getting recorded I guess.
elodin_89 said:
Works well enough. Only two things wrong (and it one of them might just be in my head). 1. Volume for my voice on calls is only about 90% as loud as the voice of the caller on the other end. I can hear both plenty fine and I'm sure you will too, just a little noticeable the lower volume on my voice in the recording. 2. Not sure why but it doesn't record calls that use Direct My Call. I've tried them using bluetooth headsets, phone earpiece, speaker, nothing mattered. I think calls made with Direct My Call maybe don't register as normal phone calls internally on the phone and the recorder app doesn't work on them? Not sure, but I can live with those calls not getting recorded I guess.
Click to expand...
Click to collapse
Thanks.
What is Direct My Call?
Do you mean to say it doesn't record calls which were accepted when Bluetooth device (eg: headphones) were used to start the call? I don't follow.
Carmageddon1984 said:
Interesting, I didnt know thats achievable without going the custom rom/kernel path.
This rooting of the phone doesnt break Android Auto, Pay and OS updates?
Click to expand...
Click to collapse
I'm rooted, I use Android Auto every single day, I use Google Pay occasionally (click the yellow How To Guide filter at the top of the list of threads in this section and you'll find the SafetyNet thread). OS updates, if you root you would have to apply the updates manually. There are several How To Guide threads in this section for how to do so - there are at least two main methods: factory image or OTA file (not actual over the air update, though).
If you do root, you should turn off the developer settings option to check for updates, as accidentally trying to take a regular OTA after rooting will at best just fail to work, but at worst might temporarily brick your device (always recoverable).
Also if you root you should look into a root backup method such as Swift Backup to the cloud, so if the worst happens, you can always flash from scratch and restore backups for apps you need to.
I use the full factory image method, which you can find the details of in whichever How To Guide you follow, if you decide to root, and depending on which method you choose to use for updating.
Carmageddon1984 said:
The one thing I'd like to have on my P6Pro is native call recording, but I've always had a bad experience with custom roms - they have major drawbacks.
Last time I tried, I had LineageOS on the P2 XL, it stopped Google Pay from working, as well as Android Auto although no one else experienced that or knew why, and a year later, the phone went into a boot loop that only one guy repairing phones was able to fix just barely (flash-all stock rom didnt work for me).
I am very wary of custom roms due to stability, but if we can gain root level access and modify the kernel to add support for call recording without breaking the above mentioned things, then that'd be a big win.
Is it possible?
Click to expand...
Click to collapse
I've call recoder on my P6P and it works perfectly.
You need to flash Addon features for Pixel magisk module
Carmageddon1984 said:
Thanks.
What is Direct My Call?
Do you mean to say it doesn't record calls which were accepted when Bluetooth device (eg: headphones) were used to start the call? I don't follow.
Click to expand...
Click to collapse
Direct My Call is the feature that will dictate automated menu options when dialing a business number. See this link for more details: https://support.google.com/pixelphone/answer/11237273?hl=en
Related
I finally decided to root/s-off/ROM last week, and after following the many excellent guides around I got to a place where I liked the features and speed of the ROM I settled on (Incredible 2 HD 4.something).
Here's a breakdown of what I passed through to downgrade/s-off/root/recovery/ROM:
Friday
Downgraded from 2.3.4/Hboot0.98. Successful.
Installed CWR, su, busybox. All well.
Boot once into stock VZW GB 2.3.3.
Grab full nandroid backup of "stock" 2.3.3 as a failsafe.
Back to CWR 5.0.2.0. Installed CM7 / gapps. All still well. I wanted Sense back, so hunted for a good candidate ROM.
Settled on Incredible 2 HD from themikmik.com
Initial flash acted like I wasn't rooted (CWR .zip install said (bad) when I selected the ZIP. md5sum is perfect, so it's not a bad copy. Battery pull later and a few full wipes, install is fine.
Saturday
Inc2HD ROM is really sluggish so I decide to nuke it from orbit and start over again.
I grab the Super Wipe script and run.
Reinstall DInc2HD ROM.
Rom is very responsive, acting much better.
Start reinstalling all my apps again.
Deal with the stupid problem of sms messages from VZW (http://www.droid-life.com/2011/06/2...age-from-vzwnmn-here-is-how-to-stop-them/]fix detailed here[/URL]).
Receive and place several calls as normal throughout the day.
Gradually reinstall apps only as I need them. Keeps down the clutter
Sunday
Receive and place several calls as normal throughout the day.
Gradually reinstall more apps only as I need them.
Getting to a good state with apps re-authed and reinstalled. Decide to grab another nandroid checkpoint backup.
Backup is fine, resume normal daily use.
Monday (today)
[*]Alarm goes off as intended (yay - I have 'Clock' back after being missing on my phone since 2.3.3!)
[*]Listen to some spotify paired to my car on the drive into work
[*]Colleague calls me .. and I can't hear him. I figure it's a bad connection so I call him back. Still can't hear him through the earpiece. As a quick test I switch to speakerphone, I can now hear him.
I figured this was a one-time thing, but start test calls to DInc2 from my desk.
Damn - earpiece isn't passing any audio. Speakerphone toggle gets me audio, as does plugging in my 3.5mm earphones.
I then test other apps I know I can toggle to playback through earpiece, and no dice (Google Voice, etc). All I can hear is a very very faint buzz while a call or playback should be coming from the earpiece. When I hang up, the faint buzz in the earpiece goes dead again.
Made sure bluetooth radio was off to rule out pairing to other devices (though I haven't re-paired since wiping anyway). No wifi radio on either. All alone with the mobile network radio.
Now I know I've done a lot to the phone over the weekend, but I can't find any common cause of what might have happened between the last good call I placed on Sunday evening and today (Monday). Phone sat all night charging on my nightstand. No physical damage or anything like that.
Thinking this may be a ROM or app issue, I bounce back to my known-good snapshot of the 2.3.3 stock ROM. Problem persists - crap.
To further rule out, I full wipe and install CM7.1.0.1 from scratch just to get another baseline. Still no earpiece audio - getting frustrated!
Whatever it is, it isn't exhibiting signs of being a ROM or app issue because it persists full wipes (wipe/cache clear/dalvik wipe, and another pass even with the super-wipe script).
Yes, I've checked basics like making sure In-Call Volume is not muted. I've also installed Audio Manager to make sure there's not some lurking audio volume problem. All sliders maxed before, during and after test calls.
Uninstalled any audio-related app to attempt to remove any hold on audio output. But recall here - it's following across ROMs and wipes, so this is just busy work.
Logic says then that either
I hit some rare bug?
The process of mucking around with recoveries, ROMs, and other lower-level items has flipped a bit somewhere that will persist full user-space wipes/partitions/formats.
it's faulty hardware (which I have a hard time believing, but stranger things have happened!) This would just have to be horrible timing.
Searches on here and other sites don't bring up too much for the Incredible 2 and this kind of earpiece issue. There's a passing mention of a "silent audio bug" here, but doesn't seem relevant (nor much detail given).
I've grabbed output 'c:\> adb logcat -v time -b radio > alogcat.radio.txt' while making a call and switching between earpiece (default) and speakerphone. No really good clues there. Changes in logging verbosity didn't show too much of interest. I'll pastebin it after I scrub my phone number out if anyone's interested.
So after the wall of text ... anyone have any ideas?
I'm in it to win it with this, so I'm not unrooting and warrantying this pig I'm due for a new phone but there's nothing I want other than to just have my DInc2 back working.
I'm off to keep searching. Wondering if there are other debug-level tools/switches via adb that'd let me poke at devices, but I'm guessing those interfaces may not be as readily exposed as I'd like.
Thanks in advance all.
tl;dr - Incredible 2 earpiece randomly stopped working, but speakerphone and headphones still output phone call audio fine. Follows across wipes/ROM installs. LOLWTFBBQ?
I hate to say it, but your earpiece is probably broken... U may have smashed it with your keys in your pocket (did that on og dinc)...
Sent from my Incredible 2 using xda premium
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Sent from my Incredible 2 using xda premium
faehsemc said:
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Click to expand...
Click to collapse
Fair enough. I hadn't ruled out full-on hardware failure I just found it to be the least-likely of the candidates.
I had to replace the speaker in my original Incredible, so I figure it can't be too much tougher to do in this one. I'm going to exhaust some other troubleshooting first (my wife has a functional stock DInc2 that I want to compare some logcat output from, see if anything stands out when making a standard voice call).
I'm always careful to change ONE thing at a time then test to make sure my variables are where I expect them to be, so this one threw me. I'll post back with results, and hopefully get my earpiece back .
OK, I ordered a replacement earpiece and replaced it. This did not fix the audio. I tested both the original earpiece and the new earpiece before installation by using a low speaker-level source and confirmed that BOTH actually work fine and produce sound as expected.
While the phone was disassembled, I made sure all contact points were good for the earpiece. This isn't a physical problem.
So, this takes me back into the software/firmware/radio arena.
And more specifically, in order to persist all wipes and reinstalls, this has to be something below.
I'm going to use adb to flash a radio (I think there's one newer than the one I have installed, something.622? Not down at bootloader to check right now).
If this doesn't do it, anyone want to buy a DInc2 for parts and dev?
The newest radio is .1111 before that .722
Sent from my Incredible 2 using xda premium
Good call on the 1.09.01.1111 firmware. I found and flashed that instead of .722.
No effect unfortunately.
So next I'm thinking that perhaps whatever kernel I brought with me from the first ROM flash could have jacked something up in terms of audio modules or packages. It's a long shot, but I'm going to grab something like nc2_2.6.35.14#21-2.3.4.zip (non-AOSP) and flash that.
Now that I have ruled out actual hardware failure, I'm just too stubborn to give up on this .. open to productive ideas on things to check, methods to troubleshoot or rule out, etc. TIA.
What about Tue hardware connection from the speaker to phone itself? I don't know much of the board on the phone so I can't give you ideas of where to test, but if you can see where the leads go I would say follow it
Sent from my Incredible 2 using xda premium
Right. I disassembled the phone again late last night and traced back to the extent I could follow. I didn't find anything glaringly obvious or bad.
Also of note, if I'm in a super-quiet room and keep the earpiece near me with no call in progress, I hear literally nothing. As soon as a call is initiated, I hear a very faint "sputtering" sound from the earpiece (original or new earpiece), which means the symptom here clearly impacts either speaker.
So something upstream from it ... whatever pathway sends audio to this device isn't getting instantiated properly? That'd make me look to the kernel or driver to understand what pathway does work when routing audio output to the rear speaker that doesn't properly route it to the earpiece for the same call.
Recapping for my own sanity:
- Physical causes == none seen, mostly ruled out via disassembly and inspection, earpiece replacement with known-good part and known-good reassembly.
- Radio == upgrade to .722, .1111 and back to .622, no change.
- ROM == not likely culprit (problem persists any ROM replacement)
Can't fight off the nagging feeling that the act of starting down the road to S-Off + su + rooting did something here.
Given that there are guides to un-rooting (don't think you can un-S-off per se though, right) I may give that a shot since this phone is essentially a guinea pig now. Going to see how far down this rabbit hole I can go.
While I'm stewing on that does anyone have links to android filesystem reference material? I'm thinking the high-level relation between things like bootloader, recovery partition, user-space filesystem and on which levels I can address these with tools like adb. I want to try to understand if some bit could have been flipped at a layer lower than what flashing a ROM or kernel can recover, but perhaps higher than a baseband radio flash. Knowing where all these live and how they interrelate sounds interesting to me. Then I can form a better working theory on what could cause the stupid problem I'm having and if it's plausible to be in software/firmware somewhere.
There is an unrooting guide on YouTube. I find it hard to believe its software, but I work on a radar weapon system that has proven me wrong many times... But if you have flashed multiple roms then the kernel would've been reflashed atleast once and if you are doing a full boot and system wipe, whatever drivers previously installed would have been overwritten... I'm leading to believe there is a shorted componant on your board and because the voltage is so low on these, there moght not be any visual evidence. Unless u have schematics of what voltage is applied where, there isn't a way to test most of them. Especially if the gates are set to be low when applied, vice highs. I would s-on factory reset and of that doesn't work, its hardware
Sent from my Incredible 2 using xda premium
Agreed. I work with enterprise hardware/storage/cluster systems, so I'm driven by nature to root cause this silly thing - but yeah, occam's razor seems to say here that it's just a really stupid coincidence that some random component failed just at the time I began making other changes. And I can't let it go
This is even more frustrating to me because I always make a point to introduce only one change at a time then test the outcome!
After poking through the SDK/reference guide about AudioManager, I was reminded that GV has access to the earpiece audio path. While I could just make test calls in/out, this saves me from burning minutes in the process.
As a quick-and-dirty workaround (for anyone who may stumble on this in the future), you can use Google Voice to act as an internal earpiece playback test tool.
Install and then go to settings and tell it to play back via the earpiece by default and not the speaker. Then (assuming you have voicemails to play), attempt playback. You can toggle between the two audio outs in a much quicker way than I've seen in any other app. Works close enough for me to serve as a test tool as I make discrete changes as I go through troubleshooting.
Maybe there are other media playback apps that'd offer a toggle to the earpiece for playback (but why?), though I didn't look. Seems like the AudioManager reference guide implied that the earpiece was a more "protected" audio path than the speaker (but that's likely just for actual carrier network voice calls).
Cheers,
I'm really getting a kick troubleshooting.. I've been recruiting for a year and a half now.. miss working on gear.. one and a half years left and back to my ship... Can't wait
Sent from my Incredible 2 using xda premium
I actually doubt it's your ROMs --- I'm running latest unmodified vz gingerbread and all of a sudden about 5 days ago I could no longer get earpiece to function - my only guess is something shorted out because of an off-market USB charger that I got 3 of for 7 dollars off Amazon...
Anyways, I had the same sorta flutter that you seem to hear when on a call and there should be sound... and otherwise silence when silence is expected... anyways I replaced it with a brand new earpiece and EXACT same issue is happening still.
Not sure whats up but this may be the world telling me to use my Bluetooth headset more anyways... I'll post if I find anything that fixes it, but I ain't gonna hold my breath given how few ppl seem to be experiencing this issue.
Good luck
Hi All
First time really contributing to this but I feel like some super-duper hacker (not that I know anything!). I'm smart and can play around with things. I actually trained as a lawyer, went into recruitment but am now considering moving into computing! This is fun and you can be involved in projects. However my eye has developed a nasty twitch... Recruitment is dead now anyway. (Any tips on how I can begin getting into programming/app development/ XDA work etc whatever it is would be appreciated, (I literally have no idea where to go but I'd like to!)).
Anyway, back on topic:-
So...I've been up for the past 24 hours with a new laptop and at first rescuing my Samsung Galaxy S6 which got caught in a bootloop with no recovery, (had to hard reset, lost all data), upgraded Android to Nougat. It all started when I went to do a recovery boot to get Magisk to work but it all went haywire. :crying:
Happy to give you a system specs - models - builds etc, if there's a good way of doing that let me know and I'll post so you techies can take a look and see what might be the reasons behind the issues. I'm running a 'bug report' through Developer Options at the moment and can post this if useful? I have a Bug Report that I've generated if this is useful to anyone in getting to the bottom of these issues, let me know and I can send...
Ok, so with no further waffling, the issues I've seen so far in the short time I've had this lineage-14.1-20170307-UNOFFICIAL-Nexus7420-zerofltexx-2 (this is the Zip file that I found for the Samsung Galaxy S6 which I understand is only developmental at the moment, it doesn't have its own one yet?)... (in descending order of importance):-
1. Fastcharging - this is very important to me. This seems to have stopped working. How can we get this back? Potentially a dealbreaker with the ROM if this can't be sorted quickly.
2. EE I should be receiving 4G++ super duper speeds on EE. This is really impressive and is very important again. However, since flashing the ROM etc, it's only connecting to T-Mobile (a connected network to EE but doesn't benefit from their 4G++ network, EE bought T-Mobile in the UK ages ago). I've contacted EE about this as I thought it may just be a settings issue. They sent me settings though it's still not working. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
3. Whatsapp VoiceNotes - I use WhatsApp voicenotes all the time; it's a crucial part of my day. Since upgrading there are two issues I can see with this:- a) there is an interference noise that ruins the clarity of each recording sent, it's there the whole time; and b) the recording itself sounds like it's slowed down and doesn't sound normal or right. At the moment this is unusabule and it's massively important, I'd imagine to most people too. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
4. Magisk - The reason for embarking on the entire debacle of the past 24 hours has been to be able to hide my root. That's why I wanted Magisk in the first place so I could use the apps like banking apps and SnapChat and Virgin TV that in draconian fashion refuse to let one use them when it sees it's a rooted device. Magisk to the rescue (in theory). So when I load up Magisk Manager now under SafetyNet Check Success, the basicIntegrity option is sometimes fine though now it's showing 'X'; and 'ctsProfile:false' is permanently showing. I've hidden Google Play Services and Google Play as I read this can cause issues. It does show #superuser in the dropdown and I'm not sure if this is a legacy from SuperSu I had before (don't think so as I did a complete reboot) or if this is part of the app?
5. Torch - torch option on settings panel doesn't seem to yield any torchlight at all. I wonder if other apps work or if there's anything the techies can do here?
Thanks so much for reading and I look forward to helping or assisting in solving in whatever way I can.
bestfootie said:
Hi All
1. Fastcharging - this is very important to me. This seems to have stopped working. How can we get this back? Potentially a dealbreaker with the ROM if this can't be sorted quickly.
2. EE I should be receiving 4G++ super duper speeds on EE. This is really impressive and is very important again. However, since flashing the ROM etc, it's only connecting to T-Mobile (a connected network to EE but doesn't benefit from their 4G++ network, EE bought T-Mobile in the UK ages ago). I've contacted EE about this as I thought it may just be a settings issue. They sent me settings though it's still not working. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
3. Whatsapp VoiceNotes - I use WhatsApp voicenotes all the time; it's a crucial part of my day. Since upgrading there are two issues I can see with this:- a) there is an interference noise that ruins the clarity of each recording sent, it's there the whole time; and b) the recording itself sounds like it's slowed down and doesn't sound normal or right. At the moment this is unusabule and it's massively important, I'd imagine to most people too. Potentially a dealbreaker with the ROM if this can't be sorted quickly.
4. Magisk - The reason for embarking on the entire debacle of the past 24 hours has been to be able to hide my root. That's why I wanted Magisk in the first place so I could use the apps like banking apps and SnapChat and Virgin TV that in draconian fashion refuse to let one use them when it sees it's a rooted device. Magisk to the rescue (in theory). So when I load up Magisk Manager now under SafetyNet Check Success, the basicIntegrity option is sometimes fine though now it's showing 'X'; and 'ctsProfile:false' is permanently showing. I've hidden Google Play Services and Google Play as I read this can cause issues. It does show #superuser in the dropdown and I'm not sure if this is a legacy from SuperSu I had before (don't think so as I did a complete reboot) or if this is part of the app?
5. Torch - torch option on settings panel doesn't seem to yield any torchlight at all. I wonder if other apps work or if there's anything the techies can do here?
Thanks so much for reading and I look forward to helping or assisting in solving in whatever way I can.
Click to expand...
Click to collapse
So in addition to these I've also discovered a further three issues:-
6. WhatsApp camera not working - you can take a photo within WhatsApp but it doesn't progress to the launch screen to the next screen to send the photo. Strangely, video clips do seem to work...
7. Bluetooth headset doesn't seem to be working anymore
8. Sky Sports App once you get past permissions and everything to watch the show it freezes on the loading step. I imagine this is something to do with the modified ROM/Kernel?
bestfootie said:
So in addition to these I've also discovered a further three issues:-
6. WhatsApp camera not working - you can take a photo within WhatsApp but it doesn't progress to the launch screen to the next screen to send the photo. Strangely, video clips do seem to work...
7. Bluetooth headset doesn't seem to be working anymore
8. Sky Sports App once you get past permissions and everything to watch the show it freezes on the loading step. I imagine this is something to do with the modified ROM/Kernel?
Click to expand...
Click to collapse
9. I'll also add in here that call volume and volume in general seem really low.
As a result of these nine bugs I'm going to have to revert back to an older version, quite possibly Stock Android, unfortunately... :crying:
So I have been 1 day with the phone, but I am thinking about reverting to Oreo for two reasons:
1) Maybe better stability/better in overall right now?
2) Xposed and more customization might worth it?
I wonder If Oreo is better for thiese reasons at the moment, just maybe because of Xposed and Gravitybox. But I have no idea actually. I also wonder If GB makes the phone laggier or less snappy (with Nexus 5X I noticed it)
These are some example of the things I would expect to work better in 8.0
- I feel ringtone/notification volume too low....
- I would like to customize led notification (more frequent blink....), customize button nav bar....as well as many other things GB might be able to do
- Facial recognition is not working at all, always need to use fingerprint which also does not work every time
- Also the voice recognition (assistant) is not working properly! For ok Google detection neither...
So I have the feeling 9.0 maybe does not worth it too much at this moment.
Thank you for your responses!
1. I've had a 2 XL since launch and I've noticed no difference in stability between 8.0 and 9.0. Both have been extremely smooth for me. As for "better overall," that's subjective.
2. That's also subjective.
-I'm not aware of a decrease in volume parameters in 9.0, so you would have to use xposed and/or modify system files to increase this. If you want to use xposed, you'll have to go back to 8. If you want to modify system files, you can do that on either version.
-I can't comment on facial recognition because I've never used it. As for fingerprint recognition, I've noticed no difference between 8.0 and 9.0. If it's really bad, it might be a hardware problem. I actually had to RMA a phone because fingerprints almost never worked. The replacement usually works unless the scanner or my fingers are dirty/sweaty/oily and in that case, wiping it off fixes the issue.
-Voice recognition works perfectly on my phone for both 8.0 and 9.0, so I doubt that downgrading will change that for you.
Ok, thank you very much, it helps.
So it seems is not about software. Maybe I will consider RMA.
I have another question, about voice recording (whatsapp), is it any commun issue that audio record does not cancell pretty well the noise in whatsapp? apparently calls are ok but whatsapp messages sound very noise and metallic
So, oneplus always had the ability to enable call recording, they just don't show it to you based on what country you are in / sim in use. However, there are ways via adb commands to enable it. They would have to be run fresh on every boot, but there are ways to automate it. However, now, it seems that oneplus is being much more active and during runtime disabling it randomly (at least popping up a message telling you that it is). I am pretty upset with this change that came in today's hotfix.
thetoady said:
So, oneplus always had the ability to enable call recording, they just don't show it to you based on what country you are in / sim in use. However, there are ways via adb commands to enable it. They would have to be run fresh on every boot, but there are ways to automate it. However, now, it seems that oneplus is being much more active and during runtime disabling it randomly (at least popping up a message telling you that it is). I am pretty upset with this change that came in today's hotfix.
Click to expand...
Click to collapse
There is a Magisk module (enable oos native recording) that enables recording and survives reboot. Just remember to uninstall it prior to any oos update, you can then reinstall it.
I try to stick with stock, as really had no issues. I was able to create an automate script that worked without rooting / modifying the stock firmware that reenabled recording on each reboot. The problem is, now the firmware is actively disabling it during runtime, not just as boot. my "solution" right now is that it seems to be tied to the notification, so if I never dismiss the notification tell me that its disabled, then it doesn't disable it in the future. Not a good solution to leave a notification up (As easy to dismiss by accident). but it really annoys me that they made such an antagonistic change.
I've created a workflow in automate that enables recording on boot and reenables it every time the notification of recording disabling comes up and dismisses the notification. Annoying, but seems to work without any rooting needed.
but i'm so annoyed that they changed this. I use t-mobile's wifi calling for my US SIM (I'm overseas), so everytime i drop out of wifi, it triggers as it seems to trigger everytime there's a "service" change of some sort on it.
Hello people,
I was wondering if there is someone out there daily driving the latest LineageOS build on their OP9Pro, who could tell me if it runs smoothly and whether there are any major bugs or inconveniences. I am thinking about flashing LineageOS on my device, but I am still uncertain if it is worth the hassle, as I rely on the phone working properly and with all/most of the features.
However I wasn't able to find much information about known issues or user reports.
I used to flash CyanogenMod on my own devices when it used to be relevant so I have a little bit of experience regarding flashing.
What I would like to know:
- Hardware working? (5G, Bluetooth, Wifi, NFC, Cameras, fingerprint, alert slider etc)
- Do all apps still work? (Banking, Netflix, GPay etc.)
- Does VoLTE/VoWifi work? (spec. German carrier T-Mobile)
- How is the update process? (OTA via system updater?)
- Major problems or known issues as stated above
I am really unsatisfied with the current state of OxygenOS (stock rom) as there are many bugs that probably won't be fixed, which is why I am looking into custom Roms again.
Also I own the EU version of the phone if relevant.
Thank you for your answers
Hi,
In case you're still wondering:
I just bought a used OnePlus 9 Pro with LIneageOS 19.1 installed.
- All of the hardware works (except I have not tested NFC - I don't use it.)
- I did not install microG or anything to use Goolge apps, I only use apps from F-Droid, so sorry I can't help you there. I don't know if any of your required apps will work.
- Phone calls work on WiFi Calling and the 4G/5G networks on USA T-Mobile service.
- OTA updates work fine.
- The only issue I have is that the Android 12 Desktop Mode doesn't work (the launcher button and two navigation buttons show up on the monitor, but they don't do anything. On my OnePlus 7 Pro with LineageOS 18.1, Android 11 Desktop Mode works pretty well.
Yes, thanks for the reply. I think i will wait for the upcoming Oxygen13, but I don't actually have high hopes for it being good. If I'll be disappointed with the update I'm likely going to flash LineageOS, as I am annoyed by the integration of Oppo's ColorOs into Oxygen, while there are still so many bugs and inconsistent UI.
akaYunus said:
Yes, thanks for the reply. I think i will wait for the upcoming Oxygen13, but I don't actually have high hopes for it being good. If I'll be disappointed with the update I'm likely going to flash LineageOS, as I am annoyed by the integration of Oppo's ColorOs into Oxygen, while there are still so many bugs and inconsistent UI.
Click to expand...
Click to collapse
My pleasure. Good luck!
Daily driving it for several months now and so far so good. The only issue I sometimes have, is that I press the power button and the screen turns black (still giving haptic feedback, but shows nothing on the screen.) I need to force reboot to fix this.
But it performs waaaaaaay better then ColorOS / "Oxygen OS" and read that the beta is again full of bloat.
I did install Gapps with this and works like a charm (thought I've picked Pico)
Hope this will help you with your choice
Dn_nS said:
Daily driving it for several months now and so far so good. The only issue I sometimes have, is that I press the power button and the screen turns black (still giving haptic feedback, but shows nothing on the screen.) I need to force reboot to fix this.
But it performs waaaaaaay better then ColorOS / "Oxygen OS" and read that the beta is again full of bloat.
I did install Gapps with this and works like a charm (thought I've picked Pico)
Hope this will help you with your choice
Click to expand...
Click to collapse
Yes, thank you aswell. I'm certainly going to install Gapps. Can you confirm that NFC/GPay is working? I rely on that as my main payment method.
Dn_nS said:
Daily driving it for several months now and so far so good. The only issue I sometimes have, is that I press the power button and the screen turns black (still giving haptic feedback, but shows nothing on the screen.) I need to force reboot to fix this.
But it performs waaaaaaay better then ColorOS / "Oxygen OS" and read that the beta is again full of bloat.
I did install Gapps with this and works like a charm (thought I've picked Pico)
Hope this will help you with your choice
Click to expand...
Click to collapse
Hmmm, I have never run into that power button issue. That is annoying!
akaYunus said:
Yes, thank you aswell. I'm certainly going to install Gapps. Can you confirm that NFC/GPay is working? I rely on that as my main payment method.
Click to expand...
Click to collapse
Sorry man, don't use Gpay and did not use NFC thus far.
So far, LOS 19.1 has been running like a dream on my 9 Pro. The only complaint I have is that calls using Bluetooth audio have a "stutter" effect, like the sound has little micro-dropouts; it's annoying enough that I try to avoid Bluetooth calls, but not so much that I can't put up with it if I have to. (Bluetooth music isn't affected, it's as smooth as lake ice.) I'm hoping we'll see a fix eventually.
MJPollard said:
So far, LOS 19.1 has been running like a dream on my 9 Pro. The only complaint I have is that calls using Bluetooth audio have a "stutter" effect, like the sound has little micro-dropouts; it's annoying enough that I try to avoid Bluetooth calls, but not so much that I can't put up with it if I have to. (Bluetooth music isn't affected, it's as smooth as lake ice.) I'm hoping we'll see a fix eventually.
Click to expand...
Click to collapse
That's fine as long as it doesn't affect wireless AndroidAuto. If anybody has experience with using it and maybe even with an AAWireless device I'd like to know as well. I have a 1st gen unit I use everyday while driving.
I'm running the version bundled with microg and am quite happy. It's a lot better than the last release of 18.1 that I was on in terms of battery life. I don't game, so I have no idea about it in that regard.
I've been running LOS 19.1 for about two weeks now, but must say I'm not all too happy with it:
- bluetooth calling (using wired android auto) audio quality is very poor, both ways (so for me and the person I'm calling with)
- fingerprint unlock works, but the 'scan area' seems to be more finicky. it often quickly switches to number based unlock. never had that with oos
- the battery life is considerably poorer for me
- the device gets much hotter while charging
- I've once had the top right part of my screen becoming unresponsive. only a reboot fixed that.
GoeniGoeGoe said:
I've been running LOS 19.1 for about two weeks now, but must say I'm not all too happy with it:
- bluetooth calling (using wired android auto) audio quality is very poor, both ways (so for me and the person I'm calling with)
- fingerprint unlock works, but the 'scan area' seems to be more finicky. it often quickly switches to number based unlock. never had that with oos
- the battery life is considerably poorer for me
- the device gets much hotter while charging
- I've once had the top right part of my screen becoming unresponsive. only a reboot fixed that.
Click to expand...
Click to collapse
That's sad to hear but maybe it will be fixed in future updates.
Still might give it a try in the near future. Does the version of the device matter? (EU, US or international)
Gpay works great on lineage
akaYunus said:
Yes, thank you aswell. I'm certainly going to install Gapps. Can you confirm that NFC/GPay is working? I rely on that as my main payment method.
Click to expand...
Click to collapse
Can confirm, though I did install a fork of magisk to get it to work
So, to summarize answers:
- "everything is fine, but I don't use nfc, gapps, banking apps. Bet everything else is fine"
- battery is worse than on Oxygen
- fingerprint sensor works, but it works worse
- "charging works, but, phone is hot. I don't use fast charging and fast wireless charging but yeah charging works, I am able to charge my phone"
- Google Pay works, but actually it does not work, you need "patched Magisk"
Can I ask additional questions?
- can I use all cameras and switch camera during movie recording?
- can I take heic photos?
- can I record 8k movie?