Related
I have a Samsung Galaxy S2 (which I believe is refurbished; I got it to replace my Vibrant which had a cracked screen).
This phone is rooted to de-bloat (and running 2.3.6) but does not have a custom ROM on it. It worked fine after I rooted it for several weeks.
Sometime maybe last week or the week before (I work deep nights, so I don't use the phone all that often), I noticed that the other party cannot hear me/one way audio.
This happens on
incoming calls
Outgoing calls
with a (wired) headset (I don't have a BlueTooth)
without a (wired) headset
on speakerphone
off speakerphone
WiFi calling
non-WiFi calling.
In all cases, I can hear the other party fine.
The kicker of it is, the Vibrant had a cracked screen, not because I dropped it, but because the lanyard which I put on it to prevent dropping it caught on the emergency brake of the car, and the screen of the phone slammed into the emergency brake. *faceplant*
I only rooted the phone in the first place after this little fiasco, but I didn't put (whatever the jig counter thingummy(1) is called so they can't "tell" you rooted your phone) when I did it.
Does anyone have experience with this issue? Would loading a custom ROM work? Do I just need the thing replaced again? I haven't actually damaged this phone at all, and EVERYTHING else(2) works. If I record a video, the audio is fine. I didn't see anything in my search, both on Google or in the forums. The Google/searchFu is not very strong with me sometimes... I mean, I'm all about my smartphone, but the PHONE part of that is reasonably critical, y'know?
(To be honest, I'm *capable* of rooting/loading a custom mod/unrooting, but it's kind of a PITA, and I'm really busy lately, so I don't want to bother if it's not going to work.)
Thanks in advance.
(1) - This being the extremely technical term
(2) - Well, not EVERY everything; I think I deleted some stuff I oughtn't have when debloating, so I can't navigate to files in my gallery, I have to actually use a file browser, but I can get there.
Phone is broken, warranty it, no custom rom will fix that
Could take it to a cell phone repair store. I use Android monsters
Sent from my HTC Vision using xda premium
Hello everybody,
I purchased my galaxy note 2 in late December, I kept the stock samsung ROM (android 4.1.1)and almost rooted it immediately after I had opened its box. Rapidly, I noticed it rebooted from time to time, it seems it happened randomly, i.e. not whilst performing a specific task on my phone. For instance, sometimes when I wanted to check my emails or texts, I picked it up from my pocket, and android was asking me to enter my SIM PIN. So basically my phone rebooted while sitting in my pocket. More rarely, it also suddenly rebooted while I was using it. (but to be honest, it spends more time in my pocket than it does in my hands, that's definitely why it did the latter far less frequently).
I saw that there was an update available, so I flashed the 4.1.2 stock ROM using kies, and rooted it again shortly after. But the reboots issue was still there, so in February I decided to give a try to a cyanogen mod 10.1 nightly build. For like a week or 10 days, it appeared to work properly, no more random reboots. However, after that delay, unfortunately it started to randomly reboot again.
I don't think that rooting the phone can cause such an abnormal behaviour, can it? I use several apps that require root privileges, that's why I did root it every time I flashed a new ROM.
Well the bottom line is that it's really pissing me off, so I'm considering to return it to samsung using a RMA procedure. But anyway, if you have any idea that could help me solve this problem, please feel to let me know, I'll gladly appreciate it. Also I'm wondering if anyone has an alike problem?
If need be, I'll return it for a repair or an exchange, if so, what do I need to do to reset it to factory defaults? I can re-flash the stock ROM, that should unroot it, but resetting the flash counter is also required, for that purpose I'll probably try the 'Triangle Away' app, hopefully it's gonna work. But AFAIK, when doing so on my former phone - a samsung galaxy S 2 - there was another counter, that counted how many times the first counter has been resetted, so one has to actually reset both of them in order for the mobile not to look having been tinkered with. Is anyone aware of a similar second counter on the galaxy note II? If you think of anything else I forgot to mention, please give me a shout.
Thanks for reading my post and helping me out.
Sadly it sounds like you might have a defective Note II. I have a stock (not rooted) Note II and, while I've only owned it for a month, it hasn't exhibited any problems with rebooting. Nor did I have anything like that with my S3 previously.
Probably not what you were hoping to read, sorry.
Thanks for your input muppetmania, well fortunately all galaxy note II don't have this problem
I just hope that if I return it, they'll be able to reproduce the annoying issue as they probably won't install as many apps as I did, or use it the same way, etc ...
My note 2 is the first android phone I've had that I have not rooted (yet). I've had it about a month now and it has randomly rebooted 3 times so far.
Every time it has happened it's been while I had 10+ tabs open in Chrome and was reloading several at once while also using other apps. For example one time I was composing an email and pulling excerpts from several sources on different web pages.. midway through composition and BAM, random reboot
In my opinion you did not cause this by rooting the phone
nebenezer said:
My note 2 is the first android phone I've had that I have not rooted (yet). I've had it about a month now and it has randomly rebooted 3 times so far.
Every time it has happened it's been while I had 10+ tabs open in Chrome and was reloading several at once while also using other apps. For example one time I was composing an email and pulling excerpts from several sources on different web pages.. midway through composition and BAM, random reboot
In my opinion you did not cause this by rooting the phone
Click to expand...
Click to collapse
If mine had only rebooted 3 times in a month then I'd be "happy" But for me it's more like 3 times a day. Well any random reboot is never a good thing, especially if you're are typing a text or writing an email. I'm scared it happens when I'm using my phone as a GPS on my motorbike, could be really pesky if I have to stop, wait for the mobile to reboot, get another GPS fix, and set my destination again ...
Just out of curiosity, you're also running the stock samsung ROM? Switching from it to cyanogen made virtually not difference for that matter.
I still have not rooted this device so yes... I'm running the stock Samsung rom
In case it may be relevant though, I do also use nova launcher and LOVE it. This new generation of TouchWiz is not bad at all not Nova is better, imo
I use the default launcher, both for the stock ROM and cyanogen Mod. I did not really like touchwizz, but I think the dual screen function and the stylus management were quite good though.
I gave a call to the after sales service, and they advised me to go to a Samsung store in order to get my phone repaired. Just to make sure it's going to be be alright (I mean that I don't want them to find out that I have rooted / installed a custom ROM on the mobile and use that as a pretext for refusing to fix it), can someone tell me exactly what do I need to do in order to revert the phone back precisely to its factory configuration?
So far, here is what I plan on doing:
- install the last official samsung ROM (which is currently the 4.1.2 version of android if i'm not wrong), that should unroot the phone altogether
- Use an app called "triangle away" to reset the flash counter
But I still wonder is there is anything else that would allow them to know that I flashed / rooted the phone. Is there anything like a second counter, that counts how many time the counter mentioned above has been resetted itself? Also I do remember that when I flashed my galaxy S II with an insecure kernel, a yellow triangle with an exclamation mark appeared during boot up (I know that "Triangle Away" should remove it), I don't currently have that on my GN 2, but I don't know whether Samsung still uses this method or if they have implemented something else?
Thank you.
Well before deciding to root, my phone was freezing when making a call. Sometimes the system would allow a conversation, then all of a sudden I would get a ringing sound followed by frozen software, I read, researched and tried not to bug any of you. I found possible issue with the proximity and light sensor. Also read on a reputable Android website, that Sprint had follied some of the PRLs OTA. So I decided to change the possible hardware flaws and Root. Low and behold it resolved the ringing that followed the freezing, but not the freezing. Was going good with Wicked Sensation 5.0, but could not stand the constant update request. That beloved Rom eventually did the same. So changed to 5 different roms and went from TWRP to Phils recovery since then. I am currently on Static 4.3, all roms worked great until I sent/recieved a call. As soon as I hit talk phone freezes and all audio ceases to function. Sometimes itll tease me after a dalvik wipe, but always after hitting "Talk," everything regarding S3 audio or sound, stops functioning.
Does anybody know about the issue I am describing? I switched the audio components so can this Handset Issue MB related? It is hard for me to rule out software due to the audio coming back after each newly installed rom. Before its demise, Audio sounds great. The audio disappears after a call. Just concerned about going to a Sprint repair center for the wait. If this is software related it highly likely my issues will come back. Not a pro, but well versed in the rooting process. As a ExSprint employee I went through all of Sam's rooted and never been stumped on a "Hardware vs Software" problem like this. If I find out its Knox Im taking a Google Nexus to record me throwin my S3 on the wall and sending it to Samsung....jk lol. (For reals though, the increasing challenges to root for every update pisses me off cause the Samsung always got better hardware then the others, but WTF Sammy?)
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:
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