Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Wow no wonder Ive been late to work all week. Phones doing the same thing.
Sent from my SCH-I605 using Tapatalk
As an update from my fiddling about this morning, it seems to only happen when the lock screen is set to the Swipe method. If set to a pattern, pin, anything else, this error doesn't occur. A temporary workaround at best, as this no longer allows me to access multiple lock screen widgets.
Wow man.. since my last post I wiped and am running a new rom, kernel, everything.. still doing it ?
Sent from my SCH-I605 using Tapatalk
I believe I've narrowed it down to a few possibilities, between it being the new ripple/ink effects on the lock screen or something to do with the multiple widgets. I can't believe we're the only ones dealing with this. Does anyone have any insight if even a complete reset, rom flash and kernel swap hasn't fixed it?
As another update, I appear to have been mistaken. While delayed slightly, the end result is no matter what, the alarm eventually silences itself after a few seconds, unknown why.
I had the same thing happen using n3bula (4.3) rom. Alarm would turn itself off. Didn't really have time to mess with it so I went back to beans 22 (4.1.2). If you figure anything out, let us know
Sent From My Sticky Note, Too?
As another update from yet more fiddling. I tested it this morning as it would normally be, hooked up to my computer charging, with my bluetooth headset on but also sitting on its charger. The alarm cut out even with pin set as the lock screen. When removed from the cable connecting it my computer and my headset on my ear, it didn't. Going to test further.
So, as yet another update, I believe I found the problem, a reply from prior posters experiencing the same thing would be helpful to see if it was the same issue. I have one of the original sony android smartwatches that connects through Bluetooth. On a hunch, I disabled Bluetooth on my phone before going to bed a few nights and wouldn't you know it, no problems. Did it again with the watch off and just the headset connected, again, no issues. Seems the watch is a bit too dated or butts heads with the MJ9 firmware driving the Bluetooth module.
So as to follow up. In my situation specifically, my music player is Poweramp and I noticed whenever my headset is connected and my alarm is going, it immediately tries to take over and start playing music, I think that's what caused my alarm to go silent. My headset is the Plantronics Voyager Legend, my smartwatch is the original Sony Smartwatch, I don't know if the combination of the three are relevant to the others in this thread having the problem.
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
ForcePhenomenon said:
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
Click to expand...
Click to collapse
when you wipe do you also format internal sd?
MunkinDrunky said:
when you wipe do you also format internal sd?
Click to expand...
Click to collapse
Correct, thought I'd noted that when I said clean wipe. I wiped internal storage, cache, everything you should when flashing a new rom, going to the point of doing it multiple times and even dirty flashing a few times to see if that would fix the problem (as it did fix some issues going on with n3bula and they actually recommend doing it.) But, nothing of the sort happened.
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
MunkinDrunky said:
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
Click to expand...
Click to collapse
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
ForcePhenomenon said:
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
Click to expand...
Click to collapse
have no idea but since it was a variable in this situation I thought to try to rule it out for certain.
Related
So this has been happening randomly on calls for about two weeks now. I'm still on Stock everything and would like to know if this is a known problem, if something is wrong with my phone, or if there is a fix? I'm past the point of returning and getting a new one and plus, I have grown atattched to this phone LOL.
I've tried hitting speaker and then turning it off but that doesn't work. Tried ticking mute and then unticking it, not working either. Reboot doesn't work. Resetting back to stock doesn't change it either.
Thanks to all.
AJ
Sounds like a typical ATT phone call. Would you and the person on the other end both happen to be on speaker phone? I cannot have a call via speaker to my wife if she is on speaker (which see insists on using) - there is too much voxing going on, I only hear every couple of syllables.
T
Sent from my SAMSUNG-SGH-I777 using XDA App
Not a speaker phone call. Seems like it happens mostly when I make calls from speed dial from my homepage screen. I can't conf
irm that last bit though lol.
Another question is this....I just turned my phone completely off and it had 42 % battery. When I turned it back on it now has 22% left.....what in the world is going on lol???
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
asjdwf said:
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
Click to expand...
Click to collapse
I need more details to say this for sure, but I THINK you may be having the same issue I had. Not many people seem to have this issue (only seen a handful across a variety of forums). So if you happen to be a fellow sufferer, then welcome to the club!
My problem was:
After the 2.3.6 update (UCKK6), the person on the other line had trouble hearing me because my voice cut in and out frequently, yet randomly. On my end though, they came in nice and clear. I often had to deal with people hanging up on me because they thought my call dropped or that I hung up, or had to deal with a lot of people repeating "hello? hello!? You there!?" as I helplessly tried responding and not being heard.
My Solution(s):
1) keep the 2.3.6 update, but flash just the 2.3.4 (UCKH7) modem. Everything on your phone will work fine, but you will get the following FALSE warnings (FALSE as in the phone says it can't do something, yet everything works fine anyways. These are only based on first-hand experience and may not happen to you.)
a) upon boot (not wake/unlock) there will be an error notification about you not being able to access your external memory card due to security reasons... don't worry, its bull.
b) when using your phone as a mass media storage device, you will get a notification about the mass storage function not being able to work... this message is also bull.
2) Or you can just completely return to 2.3.4 (UCKH7) and either ignore the update prompts or freeze the process until a newer update that hopefully fixes our problem (or ICS) is released.
I did (1) for about 2 weeks then did (2) after reading all the battery complaints blamed on UCKK6. It reverted just to play it safe with battery life (plus they say that "if it ain't broken, don't fix it" and for me, UCKH7 wasn't broken and the update definitely broke it).
Wow, that sounds identical to me except its they can hear me but I can't hear them LOL. I reverted last night with odin one click downloader and the stock kernel for battery life so we will see what's going to happen today. Is this a phone problem physically or is it software?
Thanks
AJ
For me, its a software issue (modem to be specific) because it only happens on UCKK6 (and the leaked UCKJ1, UCKJ2, and UCKJ4) and when on UCKH7, my calls are as clear as a LAN line.
I say that if the problem still exists now, then its hardware. In that case, try contacting Samsung for a replacement if your ATT warranty is up. You could try ATT too because its a defective phone and they may still do something.
So, this is my short story:
I've had this phone for 6 months. I've had it rooted for about 5 months. I've used tons of Roms, and have had no problems whatsoever. I have several Nandroid backups as well, each dating around 2 months a part (each).
/End Story
Problem:
All of the sudden, I called a friend to find that the in-call volume was EXTREMELY low. I turn it up all the way and could only faintly hear him. He sounded a mile away. I had to turn it on speakerphone to finally make out what he was trying to say.
Things I've Tried:
I've tried going back to each of my Nandroid's, when the sound was working, and nothing was fixed. I've tried Factory Reset with no results. I've wiped cache/dalvik cache - nothing. I've tried messing with Hearing Aid settings - nothing. I've tried turning the volume all the way down in the call, and then turn it all the way up to see if it fixes it - no results.
Currently I'm running the Infected Rom 3.5. But I tried calling people on MIUI, Sense 3.0, etc, with no results thus far.
Question:
WHAT could possibly be causing this? It's not like I blew a speaker, I've never done any volume adjustments on my phone with an app or anything. The receiver still works, as I can hear them, but they sound near non-existent until I switch to speakerphone.
Any guesses/suggestions?
Diabetic said:
So, this is my short story:
I've had this phone for 6 months. I've had it rooted for about 5 months. I've used tons of Roms, and have had no problems whatsoever. I have several Nandroid backups as well, each dating around 2 months a part (each).
/End Story
Problem:
All of the sudden, I called a friend to find that the in-call volume was EXTREMELY low. I turn it up all the way and could only faintly hear him. He sounded a mile away. I had to turn it on speakerphone to finally make out what he was trying to say.
Things I've Tried:
I've tried going back to each of my Nandroid's, when the sound was working, and nothing was fixed. I've tried Factory Reset with no results. I've wiped cache/dalvik cache - nothing. I've tried messing with Hearing Aid settings - nothing. I've tried turning the volume all the way down in the call, and then turn it all the way up to see if it fixes it - no results.
Currently I'm running the Infected Rom 3.5. But I tried calling people on MIUI, Sense 3.0, etc, with no results thus far.
Question:
WHAT could possibly be causing this? It's not like I blew a speaker, I've never done any volume adjustments on my phone with an app or anything. The receiver still works, as I can hear them, but they sound near non-existent until I switch to speakerphone.
Any guesses/suggestions?
Click to expand...
Click to collapse
As with more abnormal issues such as this, the best recommendation, in my opinion, is to revert to a stock ROM, kernel and clear the /data partition.
This will ensure the device is running 100% stock software. If the issue still persists with stock ROM, kernel and a cleared /data partition (test before loading 3rd party apps) the final conclusion would be a hardware related issue. At this point, should be able to take the device in for service.
If the issue disappears on a stock setup, then you can start eliminating possibilities such as a specific ROM, kernel or 3rd party apps which could be impacting the volume.
Hope that helps!
^
I pretty much did as suggestion, but I decided to put on an almost-stock ROM (with some visual differences) to sprint first. When I told the technician the problem, he noticed the rooted phone and said that it was because of my software. I knew it wasn't, because of all the resetting I had done, different nandroids, etc, and that it was the in-call receiver. He stated he was 100% sure it wasn't.
I went home, went back to full stock. Same problem. Took it to a different sprint store and they said that there was a connector issue, and since they didn't have the part - they will order me a new phone for 38 dollars (I didn't have a warranty).
Not too bad. Too bad the d*ck at the sprint store couldn't have looked at it first, as he would have seen that. But oh well. Whatchya gonna do?
Decided to post this in case someone has similar issues.
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
I googled vibration not working galaxy s2.
Found this but I didn't watch it as I am not on wifi.
http://www.youtube.com/watch?v=3JA3PXNYjJM
gerbs said:
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
Click to expand...
Click to collapse
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
jcordova23 said:
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Yeah, already called att for a replacement and its on the way. Finally decided to give up after getting it back to 100% stock (kernel rom bl etc).
I literally tried everything. But in the end it makes sense that it is a hw problem since so many others have run into it too. Poop.
i watched the video you showed. i started to mess around with my settings while i inserted my headphones on. Somehow, everything is fixed but the vibration is not as strong as before.
Furthermore, my aux does not work with this phone sometimes. It would need to be connected a certain in order for it to work.
I probably dropped my phone while I was working out while i have my headphones on. The connector probably got messed up in the process.
I might need to send my phone in for a replacement. Since i'm not under warrenty, i might send my phone to a lab. I'm pretty sure they can do something about it.
iichrisphamii said:
I might need to send my phone in for a replacement.
Click to expand...
Click to collapse
The vibrator turned out to be a hardware issue for me as expected, fyi.
Hey guys!
The other day, I picked up an Atrix, mainly to use as an mp3 player so my S3's battery wouldn't drain as much during the day.
So, I took the steps any good android-user would go through. I unlocked the bootloader, rooted, and had Clockworkmod all set up.
This is within 30 minutes of having the phone. During the first while of tinkering with it, I noticed some strange things. There's really too many to list, but I'll try.
The phone at times is completely unresponsive. At seemingly random intervals, the Atrix would freeze, and randomly start selecting things.
For example, whilst using the keyboard, it would stream out random lines of text, like yyyyzzyyzyyzyyzyyyxyyxyyzy. Thinking that it was just a fluke with the rom , I carried on.
Often, the only time I can accurately and reliably select something is immediately after turning the screen off and back on again. And sometimes, that doesn't work either.
Also, there seems to be a 4-5 second latency from pressing the screen, to the device registering it.
Again, at random intervals, the image displayed on the screen begins to shake, and becomes unresponsive. I really wish I could record it happening.
There's also a host of other problems. The wifi hasn't ever worked, and the phone flat out refuses to flash some gapps packages.
So, my Atrix is basically a non-functioning, shivering, nightmare of a phone to work with. None of these issues have been caused by flashing different roms, and I have never touched any of the sbf files.
No matter what I try, it is just unusable. Every thing I have tried has failed, and this phone is out of warranty, so replacement is out of the question. So, is there anything I can do to fix this issue? I really, really need help.
Thanks in advance guys!!
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Newbleeto said:
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hey! Well, I started on the stock ota 2.3.6
Yes, the bootloader is unlocked, cwm is the recovery, and I can get into it. Before flashing, I did wipe dalvik, cache, and factory reset.
The roms I've installed are in this order:
Stock ota 2.3.6, Cyanogenmod 7 2013/1/1 nightly, TopSmart's final release 1.3 rom, and AOKP 4.1.2 from October 17.
The roms flash just fine,and I always use the correct gapps. The problems have persisted through everything I have tried.
Bluetooth does not work, and neither does anything that requires a radio. (Data, calls, wifi, etc)
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
affiatic said:
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
Click to expand...
Click to collapse
I got it used, but it was still in the box, and even had the plastic screen that says "Don't text and drive" on it. The phone had literally never been booted up.
I think I figured out the problem, and will try to post a video of it.
The touchscreen just freaks out when being used. I found this out through the pointer location in the dev tools in Cyanogenmod 7
I'm on cm10 and random touches happen to me. I just lock and unlock the screen to fix. Only happens to me on cyanogen roms.
Sent using tapatalk
Could it be a foreign phone? that would explain the radio not working. The screen breaking and ghost touches sound like the leaked rom/kernel, was it happening with all the roms you installed?
first I've tried about 4-5 roms from stock tw to aosp style.
I get a gps lock but it's waaaaay off, floats around and doesn't give me my true location, maps, ingress etc none of them work properly.
my auto rotate doesn't work on any rom, beans/alliance dn3 gummy etc, it doesn't matter. if an app is landscape it tends to work and i can force an app to rotate aside from my camera app however nothing that should rotate when I turn my phone on its side seems to work. I. basically deal with it however is starting to get frustrating, I've tried everything I can think of and can't get it to work.
any ideas on what might fix this or is a warranty replacement the best course of action.
and lastly my presence sensor won't work, in calls the screen doesn't turn off I have to manually turn it off, I don't understand. it used to work great I could just place my hand in front of it on calls and it worked, not anymore.
I'm thinking I should just get a warranty replacement my quandary is that I've got my bootloader unlocked and I'd like to get another note 2 with an unlocked bootloader, however I know that's more always possible.
liftedplane said:
first I've tried about 4-5 roms from stock tw to aosp style.
I get a gps lock but it's waaaaay off, floats around and doesn't give me my true location, maps, ingress etc none of them work properly.
my auto rotate doesn't work on any rom, beans/alliance dn3 gummy etc, it doesn't matter. if an app is landscape it tends to work and i can force an app to rotate aside from my camera app however nothing that should rotate when I turn my phone on its side seems to work. I. basically deal with it however is starting to get frustrating, I've tried everything I can think of and can't get it to work.
any ideas on what might fix this or is a warranty replacement the best course of action.
and lastly my presence sensor won't work, in calls the screen doesn't turn off I have to manually turn it off, I don't understand. it used to work great I could just place my hand in front of it on calls and it worked, not anymore.
I'm thinking I should just get a warranty replacement my quandary is that I've got my bootloader unlocked and I'd like to get another note 2 with an unlocked bootloader, however I know that's more always possible.
Click to expand...
Click to collapse
Chances for getting another Note 2 with it still on 4.1.2 is slim, but there is a chance.
Thats is weird that all of sudden this problem started occurring.. You did not drop your phone or do something that may have effected these things?
Have you tried to Odin a Stock Recovery and perform a Factory Reset? You might want to give that a go and see if it solves these issues.. Also when testing GPS, I have always resorted to an app called GPS Toolbox. It works great!
lacoursiere18 said:
Chances for getting another Note 2 with it still on 4.1.2 is slim, but there is a chance.
Thats is weird that all of sudden this problem started occurring.. You did not drop your phone or do something that may have effected these things?
Have you tried to Odin a Stock Recovery and perform a Factory Reset? You might want to give that a go and see if it solves these issues.. Also when testing GPS, I have always resorted to an app called GPS Toolbox. It works great!
Click to expand...
Click to collapse
I have dropped it a few times however it lives in a TPU case, I've never dropped it from higher than about waist high. though it is possible
I'll try to Odin this weekend, can you point me to the most up to date rootable odin, I've done some searching I'm just not sure which is best.
liftedplane said:
I have dropped it a few times however it lives in a TPU case, I've never dropped it from higher than about waist high. though it is possible
I'll try to Odin this weekend, can you point me to the most up to date rootable odin, I've done some searching I'm just not sure which is best.
Click to expand...
Click to collapse
Use the Stock Recovery image in the stickied Data Corruption thread in the General Section..
well I've tried a couple of different methods, guess something really is broken... I'm going to go back to bone stock and call VZW to get a replacement, damn this sucks... I'm not going to be able to flash the stuff I want.
whatever as long as everything else works.
flashed back to VRAMC3 called VZW went through 90 minutes of troubleshooting and updated all the way to Kit-Kat... still doesn't work.
and to top it all off, my vibrate just started going really strange.
I'll have a new phone tomorrow, hopefully ghetto root works.
May Not Be THE Solution, But Finally Worked For Me!
So, I've been experiencing GPS issues on R3Ds Port S5, SlimKat, Paranoid, DN3, and Dirty Unicorns... been trying all the solutions being posted in the threads before factory resetting and starting all over.
BTW I use GPS Toolbox to test my GPS connections and get 0/0 satelllites.
In a last ditch effort, I loaded AllianceRom and GPS connected (20/20 Satellites with GPS Toolbox)!! I was starting to suspect that it was hardware until AllianceRom. As great of a Rom as it is, I will likely not stay on it unless I cannot get any of the other Roms to connect GPS.
I'll let this Rom run for about 4-5 hours and then with a GPS fix, try and re-install Dirty Unicorns or R3Ds and report back.
I'm hoping this can be a solution for a least a few, if not all (wouldn't that be nice) of you experiencing the same issues as I was.
got a CLNR last week and everything works great.
sadly, no roms fixed the issue and now I'm on locked bootloader ND7.
on the bright side ghetto root worked and wanam xposed is at least a decent way to get what I want, manually editing my the files to increase volume etc is a pain, however it's better than nothing.
glad to hear alliance fixed your gps, hopefully it stays fixed.
Sent from my SCH-I605 using Tapatalk