[Q] Synergy RLS1 Audio (Vibrate/Silent) Profile Issue - Droid Incredible Q&A, Help & Troubleshooting

Hey everyone,
I had been running RC2 of Synergy before I upgraded yesterday to RLS1. I didn't notice the issue running RC2 for about a month, so it must be something new in RLS1...or something I did to it.
I can't get my Dinc to stay on a profile. When I turn the ringer up so I can hear it, then set it to Vibrate or Silent...the ringer somehow stays all the way up where it was. Does the same with notifications and such too. It's like I have lost all control over the audio on my phone.
I had Audio Guru installed and thought it might be doing something odd, so I played around with it (which it was acting funny too) and actually un-installed it to see if things changed. They didn't, issue still there. Just wondering if it's something I did...or if anyone else is seeing this in the RLS1 of Synergy.
I would have posted in the Synergy thread, but I don't have my 10 posts yet...

NOT FIXED (prev FIXED?)
Well, I wanted to edit my original post (below) because it's misleading. It was fixed UNTIL I did a reboot. I've tried 3 times to re-flash with full triple wipes and it always happens. The last time I even left Titanium Backup alone and just the let the phone restore what was linked to my Google account, but sure enough, after 1 reboot, the issue came back.
I have a bug thread open on the Synergy project, go comment if you're having the issue too - an Evo guy already said he is having some similar issues too. I tried to post the direct link, but apparently I haven't met my minimum to do that either. So, go to the Synergy thread and click on the link in the NOTES section that says "Please report any bugs Here".
-----------Original post------------
Well, I don't know what I did to get the issue to present itself, but after biting the bullet and doing a re-wipe and re-flash, everything is working as expected now. Maybe I was a goof and I forgot to wipe the Dalvik last time...who knows...
Anyhow, I'll re-post if it presents itself again, but it appears to be FIXED now.

Related

[Q] Weird Screen Issue After ROM Update

So I've started getting a very weird "ghost touch" on my evo. Rather than try to explain what it is, here's a video (no links for newbs apparently) ###youtube.com/watch?v=0zW934J0UQ8
So you'd think it's a hardware issue but I have this hypothesis that it's some kind of software issue because it happened right after I switched from Fresh 3.1 to Fresh 3.2. It also goes away if you standby and it's somewhat intermittent.
The only problem with the software hypothesis is after it happened, Fresh 3.3 came out so I loaded that up trying to get rid of the problem and then I loaded Ava, and now I'm on Virus and the problem hasn't gone away. I've also switched up kernals a few times with no result. Radio\PRI\Wifi maybe but I don't know how that would affect it. So it may be that's just me not wanting to have to return my phone, but any thoughts would be appreciated before I go back to stock and get a new one.
KB

[Q] What's new in CM6 V6.1.0 RC2?

Please excuse this question if this has been hammered to death. I spent the previous 9 days on vacation and feel slightly out of the loop. I'd also rather not read the past 100 or so pages in the CM6 thread to get filled in.
I flashed RC2 and everything seems to run great. I notice the ADW Launcher "apps" icon has changed. Any other tweaks? What works, what doesn't? Any bugs etc.
Thanks
it's only my opinion.
cm6.1rc2 is a bug fix for rc1.
...cm's team showed a tweet about possibly having wimax authentication working a few days ago(not released...wip!). but it seriously isn't their focus how sad.
talk about missing the mark on this phone...
I only noticed a few issues thus far. I had a problem keeping a GPS fix the other night, however I'm not sure if that is attributed to RC2 or my lack of doing a full wipe. I also noticed this morning my messaging app keeps experiencing an FC.

[Q] CM7 eventually just starts showing black screens instead of most things. Why?

This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.
dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.
I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.
I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol
Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App
I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.

EVERY app, stock or not, continiously resets(closes and reopens).

Ive sort of tried to search this one (How do I search JUST the Epic 4g section of XDA??) and found no one describing this problem the way I do...
This is my second time having this issue, and the fix for it last time was a pain in the ass, so id like a new fix-
Every app, every aspect of my phone, continuously resets/reloads. This is most noticeable with Hancent SMS, as it saves a message as a draft when you close out of the app... Well, right now, ill be typing and "message saved as draft" will constantly pop up at the bottom of the screen (about once every 2 seconds), and the phone will lag and it will erase 1 or two characters(making me look like I cant type :silly: ).
If this was the only problem, maybe I could live with it, but it affects everything. Launcher Pro randomly/continuously resets. The notification bar often resets while trying to pull it down. The phone app will close or freeze as soon as I start receiving a call. Sometimes it'll play my ringtone without a way for me to answer, other times I never knew I missed a call unless they leave a voice mail... And sometimes its worse than others, sometimes its fine for an hour, then something goes stupid and even a reboot doesn't help. For instance, right now, it was happy. I launched aLogcat to check it out and now the screen orientation REFUSES to stay one way. Even setting the phone down, it switches directions every few seconds, which makes aLogcat reload and therefor its unusable.
I haven't mentioned what im running because Ive had this exact same issue on a totally different rom, almost a year ago, but im running-
build - SleeperROM_3.0.0_FC09
kernal - 2.6.35.7-Shadow-FC09_v1.0
baseband - S700.0.5s.FC09
firmware - 2.3.6
Ive had this happen on EB13 on the EpicExperience ROM too.
SOO, if anyone has advice on how to fix this, id be extremely interested.
On the other hand, last time I had this issue I was convinced it was a corrupt piece of memory somewhere early in the OS, something I corrupt during install, and I went ahead and reflashed and wiped and reflashed and wiped and returned to stock and etc. etc. etc... and that seemed to work... actually, I dont know exactly what part of the process fixed it, thats why I do not want to repeat it unless I have to... BUT, if someone would like to explain/point me in the right direction. I'd like to know how to DELETE AS MUCH AS POSSIBLE and FLASH as CLEAN as possible. (that is, if no one else knows of a fix for my problem)
thanks all!
Err, well only thing I can think of is a truly clean install using Odin. This means do not restore any data from backups. Then slowly begin installing applications 1-by-1 through the play store website (for speed sake) to see if your issue creeps up again.
It also couldn't hurt to format your SD card too. Corrupt data on the SD card can cause some wonky things at times.
get another device...i hope u have the equipment protection plan
Thanks for the advice guys OFF TO THE ODIN MACHINE! haha.

Build 13.0-20160207 "Unfortunately, Bluetooth Share has stopped."

Is this a known issue with the D851 and CM13? I keep getting a force close over and over and it won't stop unless I reboot the phone witch in turn disables Bluetooth. I can't seem to find anything about it other than one post with no answers. Here is a pic of the build causing the problem. Any way to fix this?
Same issue here. Seems to be caused by a commit to lg g3 update init in the cm changelog.
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
SovereignKnight said:
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
Click to expand...
Click to collapse
Looking at the changelog for the next potential nightly, it seems like it will be fixed. They added back part of that file.
See http://review.cyanogenmod.org/#/c/132118/
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
UPDATE: re-flashed, GPS is working fine.
I dirty flashed 20160212 and now my GPS doesn't work, but the Bluetooth messages have stopped on my D851.
mdphoenix said:
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
Click to expand...
Click to collapse
CM maintainers Forget our Device is BCMD unlike their devices.. so they think if it works for them, it must work for all.......
Only the D851/D856/F400/LS990 use BCMD while the others use that wcn crap.
as for data. Leave that to CM to mess that up to............. I had to go and fix my Device tree for PAC that CM totally screwed up.
your data issue is more a apn-cong.xml issue.. if you want a fix to that.. go read the last few pages on my Pac thread. and I listed a fix for data issues..............
Nice. Thanks!
..
Had this issues on an earlier build fixed it by reflashing
MuF123 said:
What was the fix?
Click to expand...
Click to collapse
A long hard road followed all of this. Lessons were learned, and in the end, nothing really gained. Except a working phone.
The entire issue started when I tried to flash SuperSU. Not knowing that CM didn't use SU. That began the decline. I ended up using the LG flash tool to put it back to an older stock version. It worked for a while, then I rebooted and it went to hell. Deader than dead. I shipped it off to a guy in Texas I found on Ebay to JTAG it. Came back just fine. Except I think whatever I did to it before then jacked up the charging. The phone wouldn't charge at all. Sitting on a charger for two days gave it about 5%. Come to find out, it was still under warranty. I shipped it to LG. They fixed it, returned it, and now it's on stock Lollipop, and I have to say - I quite like LG's interface. I've turned off a few things, installed Nova, etc. But at this point I have no reason to root or go custom. I did with my VZ phones because they were such nazis about everything. But I've got free tethering with Tmo. The phone works well. So, I'm sticking with what I have for now.

Categories

Resources