Related
CyanogenMod 5.0.8 for HTC Droid Incredible
Koush just updated this to Test Version 3 today.
Get it here - http://inc.sodpit.com/roms/koush/
*FYI* I did not make, nor am I trying to take credit for this ROM. Just making a thread where it can be discussed.
Post up any bugs you notice here and I can add them to the 1st post in a list.
quite a few bugs in test 3 right now
1. High pitched whining sound when making phone calls
2. No speakerphone
3. No bluetooth
4. Camera is 3mp
5. No multi-touch in stock browser or maps
6. Trackball wake and unlock has dissappeared
7. Facebook sync not working
8. Internal storage not recognized
Calendar is force closing on me
Sent from my Incredible using Tapatalk
i can't get MMS to download
EDIT: disregard, seems to be working after a reboot
Oh wow. I guess I will hold off on installing this one then.
What has been fixed so far ? Graphic flickering issue still there ?
Maps is fc for me
Sent from my Incredible using XDA App
Graphical issues are fixed. You guys might wanna hold off on this one if you actually make phone calls. It's a pretty big issue, but I'm sure koush is working it out.
This release is also scoring much lower in linpack as well.... I'm getting 3.5s as opposed to 7s compared to the last test rom.
jonnybueno said:
quite a few bugs in test 3 right now
1. High pitched whining sound when making phone calls
2. No speakerphone
3. No bluetooth
4. Camera is 3mp
5. No multi-touch in stock browser or maps
6. Trackball wake and unlock has dissappeared
7. Facebook sync not working
8. Internal storage not recognized
Click to expand...
Click to collapse
These plus couple others.
Calendar is force closing
Can't get my contacts to sync right. 11 get pushed through but nothing else.
Also it seems a bit less responsive. Linpack was running 3.5 - 3.8 instead of my normal 8.1 - 8.3.
Can anyone get GPS to work? cell location works fine, but no GPS.
I will come back to this or any other roms when GPS is working.
You had me thinking this was a final version with the "[ROM] Cyanogen 5.0.8" thread
I too noticed no GPS.
I believe that this rom is a definate step in the right direction. Once the devs can get all of the hardware working in their roms, the sky is the limit. Thanks to Koush for all of his work!
I don't have Twitter, but does anyone else here?
Someone should tweet him to look at this thread because all the bugs are listed here (I'm sure he knows most of them but maybe not all). So this would help him a lot with progress I'm sure.
Droid Incredible Rooted!
Twitter is working for me and so is maps. Button unlock works too just have to hold it down for a few seconds.
Sent from my Incredible using Tapatalk
It says "upgraded to test version 3" in the first post.
Sent from my ADR6300 using XDA App
I didn't have any high pitched noise making calls and speakerphone worked fine for me. no FC's in Maps either.
andrew53517 said:
I don't have Twitter, but does anyone else here?
Someone should tweet him to look at this thread because all the bugs are listed here (I'm sure he knows most of them but maybe not all). So this would help him a lot with progress I'm sure.
Droid Incredible Rooted!
Click to expand...
Click to collapse
I'm sure he knows. That is why it is still called a test version. He is working on it still.
Sent from my ADR6300 using XDA App
I have maps working on mine. On the first boot I installed the maps update which broke it. Then I redownloaded the app pack from rom manager and installed it. It removed maps from my phone for some reason. I then installed maps from market again and it worked.
Sent from my Incredible using XDA App
-Calendar also FC for me. Couldn't fix it.
-Maps FC at first but after I reinstalled it from the market it worked.
-Reboot seems to turn off the phone rather than rebooting.
Been using this ROM since it popped up as update 3.
Noticed most of the above bugs, and got maps to install just like the others, however Google Earth is -refusing- to install properly. Also, I have the high pitched whining issue, but the ROM also isn't seeming to recognize my microphone so no one can hear me when I call.
All the progress is excellent so far, I'm very impressed with Koush's work. Can't wait till this thing is ready
Cameron_S said:
Twitter is working for me and so is maps. Button unlock works too just have to hold it down for a few seconds.
Click to expand...
Click to collapse
Do you see the option to enable anywhere in the settings? I can't get this working. you're on test 3 right?
seanhassars said:
I didn't have any high pitched noise making calls and speakerphone worked fine for me. no FC's in Maps either.
Click to expand...
Click to collapse
I reinstalled and the high pitch squeal went away. I think wireless n or hydra kernel may be the source of that issue.
On another note, Twitter works fine for me
Once I launch poweramp, it start to initialize, then crush.
I Uninstall and reinstall, Wipe cache and dalvik
This is the first time that I have this problem with Poweramp
You've installed this through blackmart? There can be a problem when the app was cracked. Try to download it from some other source and then install. Hopefully the problem will be solved
Why you are so sure that i downloaded a cracked version?
I bought the unlocked version already....
Sent from my GT-N7000 using xda app-developers app
I have asked it as a question. And if the app crashes, you have to look out for an update as there can be a bug in the app.
+1
I'm having this problem too. To note, the crash does not display the "app crashed" pop-up. It started with cm-10.1-20130529-NIGHTLY-n7000 and persists with cm-10.1-20130530-NIGHTLY-n7000.
I did not try rolling back to cm-10.1-20130528-NIGHTLY-n7000 (which did not exhibit this problem). The newer nightlies have significantly increased performance and stability overall, so I'm interested in fixing Poweramp instead of going back to cm-10.1-20130528-NIGHTLY-n7000 (which I don't know 100% will fix it).
Interestingly, Poweramp played music when I connected Bluetooth in the car. While playing, the app still crashed if I tried to open it up (and the music stopped). I was able to start the music back up with BT controls though.
Wiping cache and data did nothing. I re-enabled Apollo, which crashed (with the app crash message) until I turned off Bluetooth and turned it back on. Apollo works but Poweramp is unchanged.
I'm having the exact same problem.
It happens on my galaxy s3 with latest cm rom.
so am I
Ortanon said:
I'm having this problem too. To note, the crash does not display the "app crashed" pop-up. It started with cm-10.1-20130529-NIGHTLY-n7000 and persists with cm-10.1-20130530-NIGHTLY-n7000.
I did not try rolling back to cm-10.1-20130528-NIGHTLY-n7000 (which did not exhibit this problem). The newer nightlies have significantly increased performance and stability overall, so I'm interested in fixing Poweramp instead of going back to cm-10.1-20130528-NIGHTLY-n7000 (which I don't know 100% will fix it).
Interestingly, Poweramp played music when I connected Bluetooth in the car. While playing, the app still crashed if I tried to open it up (and the music stopped). I was able to start the music back up with BT controls though.
Wiping cache and data did nothing. I re-enabled Apollo, which crashed (with the app crash message) until I turned off Bluetooth and turned it back on. Apollo works but Poweramp is unchanged.
Click to expand...
Click to collapse
So am I
My samsung s3 use the latest cm nightly rom 30130530
also crashed hope this bug can be fixed as fast as possible
Apparently it is a wider issue, since I have the same problems with my SGS2, running the 30/05 nightly.
Problem solved
bmaes said:
Apparently it is a wider issue, since I have the same problems with my SGS2, running the 30/05 nightly.
Click to expand...
Click to collapse
Hi,
In the 31/05 version - Poweramp is working OK for me.
talgreen said:
Hi,
In the 31/05 version - Poweramp is working OK for me.
Click to expand...
Click to collapse
I can confirm, in the 1/06 version for SGS2 Poweramp is working again. Must have been a bug in the ROM.
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
This is the only and the known problem with droid4 on cm10.1 cm10.2 but I have a very good experience with the latest nightlies using buildprop editor to change only the telephony.lteOnCdmaDevice=0. Don't use the patch and se if it helps for you.
Sent from my XT894 using xda app-developers app
I have that property "zeroed" already, do you mean I should try reverting Tobby's mod?
Try the latest nightlies, there are some changes regarding to apns, it's updatable from cm10.1 and make only that change don't apply any patch.
Sent from my XT894 using xda app-developers app
Joril said:
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
Click to expand...
Click to collapse
I've seen this on stock, and I think it's related to bluetooth - perhaps it's not releasing the audio properly after a device disconnects?
There's an app in the Play Store called "Earpiece", and I can use that to bring the audio back when that happens by switching it on, and then switching it off again.
HTH.
Steve.
I don't use bluetooth at all, but I'll try Earpiece, thanks
the problem is that it will crash before you realize and you will loose the next call, so I don't think it is of some use.
I tried latest nightly and safestrap 3.65 (from 3.63) and I had lots of black screens, several on one day and then I realize that before, I had it working stable on cm10.1 when I found out that noop was the problem, cfq and deadline was ok (after speaking with hashcode it made the default to cfq) but it was on safestrap 3.11, but then newer versions of safestrap appeared and I updated it and from time to time it started to go bad again.
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
I would ask hascode if safestrap can be a problem, but now he has retired in supporting the d4, of course this can be applied to razr
Regards
lucize said:
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
Click to expand...
Click to collapse
How is it going?
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Regards.
Sent from my XT894 using xda app-developers app
lucize said:
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Click to expand...
Click to collapse
Ok, now I'm on a 10.2 nightly, with just the lteoncdma fix... Let's see how it goes
It took a while to connect to the GSM network, did this happen to you too? (The signal strength icon even changed to a question mark at one point)
I first have no sim, then no signal then I get full bars
Sent from my XT894 using xda app-developers app
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Joril said:
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Click to expand...
Click to collapse
I'm on kitkat, I think that I had it too with 28, try 27 or other, maybe stable, anyway is better than 1 or 2 days
Regards
Definitely better, yes So you're using CM11? Any problems?
Joril said:
Definitely better, yes So you're using CM11? Any problems?
Click to expand...
Click to collapse
the 05 fromm stargo is not so ok, the previous was stable, or at least I didn't had problems.
I'll try the 07, I have problems with deep sleep and I don't know why, because for now wakelocks can't be accessed on 4.4, then again is not a new install, is an upgrade from 10.2
the strange thing is that now I have another error in catlog when it goes out of sound compared to the error when it is on the gsm patch, maybe I'll try a test without changing build.prop at all, in the end it doesn't matter if the signal icon is wrong as long as it's stable.
Regards
Hey! Joril! I posted in your other thread, on another forum, about this same topic, but I figure that I'd get comfy here, since the Droid 4 "scene" has seemingly migrated from DroidForums to this website.
Anyway, I haven't been able to fix the problem. In fact, at one point, when the audio died, I went through the typical steps - I turned off Bluetooth, and reset the phone. However, when the phone was "coming back", so to speak, an "Android is upgrading" box popped up. Odd, I thought, since I didn't do anything different. Anyway, it gets through this, and... I get an UID error. Something about the UID being inconsistent with the system, and that the data partition was terribly unstable.
So, my phone was freaking out. Great. I was missing several apps, and the whole device is incredibly unstable - apps are crashing, left and right, as well as background services. It is at this point that I decide to bite the bullet and restore my phone to stock settings.
I do so. I use the Droid 4 Utility, restore the stock ROM, getting rid of Safestrap 3.11 in the process. Everything's back to normal. Stabilized. I commence to rooting the phone, installing the latest version of Safestrap, and installing CyanogenMod 10.1.3. I get it running, and... the problems remain. I still have the same audio issues. MMS is still iffy. GPS is a hit-or-miss process; every once in a while, if the planets align, a system reboot will "fix" GPS.
Anyway, that's my story. I've been doing some research - or, rather, a lot of research - and it seems to me that the audio problem was, perhaps, fixed in the latest CyanogenMod 11 build. Something about the previous code not playing well with the "Audio HAL", whatever that is, and the Audio HAL issue being consistent with other phones with the same processor, I believe - or something to do with an "MSM8660". I believe that "MSM8660" is a Snapdragon processor, but I could be wrong!
To make a long story short: CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds? I don't know how to code, but it should be relatively simple to patch the few crippling bugs remaining on 10.1.3, using code from future builds and versions.
Jishkah said:
CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds?
Click to expand...
Click to collapse
Right now I'm on a CM10.2 nightly and the audio issue appears a bit less than when on 10.1, I'd say once every 5/6 days instead of once every other day... Anyway I'd like to wait a bit more before trying CM11 too
CM11 has this issue also, but the error will not be the same if the build.prop has only lteoncdma modified, for me, if I apply the full gsm patch the error will appear more often and catlog will show the cpu pegged error.
the problem with CM11 (for me) is no deep sleep, the sound issue is not so important anymore
It appears that some of us have been dealing with a very annoying issue with the mic not working in calls, Google Now, video recording, or any other voice based service (utter!, etc.). Oddly enough, it works fine, and then suddenly stops working completely until a reboot.
No errors appear, or popups, it just doesn't work, as if the microphone hardware is not even attached. It is certainly a software issue, but not too sure what is causing it. There is another older thread that covers microphone problems, but is not related to this new issue caused by something wrong in Sense 6.
Temp fix 1: Boot the phone into safe mode.
Temp fix 2: Reboot, but not guaranteed to work for very long.
If we all share our settings, we might be able to pinpoint what is causing this issue.
- ViperOne 6.1
- ElementalX 14.1
- TWRP 2.6.3.3
- Radio 4A.25.3263.21_10.38x.1157.04L
- ProjectERA v15.2
- Viperdark 6.1.1
- Launcher: Google Experience
- Xposed with a few modules *Ruled Out*
EDIT: I think I figured it out. It is the caused by the IntenseBlast addon in ProjectEra. Flashing this should fix your issue: IntenseBLAST_UNINSTALL.zip.
I will test this out for a few days and see if the problem persists after uninstalling IntenseBlast.
EDIT 2: I reflashed IntenseBlast to test my luck, and... my mic seems to be working fine. I'm guessing now that countless reboots fixed the issue, and it was simply a coincidence that the time I uninstalled IntenseBlast... the microphone decided to work. As of now, there is no known solution, but you can try rebooting your device a few times.
EDIT 3: A full factory reset and reflash solved my problem completely.
EDIT 4: The problem was discovered to be Project ERA. However, v18 is said to fix the issue, so try that build than any older release.
Okay, I've only had the issue on ViperOne 6.x.x, and always had ERA, and Kangaroo kernel. Twrp 2.7.0.0. No xposed.
I know they changed the mics in later m7 builds. Would this be related?
Sent from my HTC One using XDA Premium 4 mobile app
myrigon said:
Okay, I've only had the issue on ViperOne 6.x.x, and always had ERA, and Kangaroo kernel. Twrp 2.7.0.0. No xposed.
I know they changed the mics in later m7 builds. Would this be related?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agreed. I updated my OP. I believe ERA is conflicting with Sense 6, more specifically, the IntenseBlast addon.
BuffMcBigHuge said:
Agreed. I updated my OP. I believe ERA is conflicting with Sense 6, more specifically, the IntenseBlast addon.
Click to expand...
Click to collapse
Not entirely sure that's it, as I had the issue both with and without intense blast, and on different versions of ERA, which didn't cause issues on other ROMs, or earlier ViperOne releases.
Sent from my HTC One using XDA Premium 4 mobile app
Has this issue been spoken about in the Viper M8 thread? I ask because since with our M7 devices and the Sense 6 is a port, could this be causing the spotty mic problems?
I have not been subject to this issue... Yet.
As far as some people not being affected at all and others may be a combination of the port and assembly plants. HTC had assembly plants in different countries and the parts come from different manufacturers.
I'm glad you started this thread cuz I'd like to find the answer & help other users too.
(I'm not a dev, just a user passing forward what I've learned)
ghostryder12 said:
Has this issue been spoken about in the Viper M8 thread? I ask because since with our M7 devices and the Sense 6 is a port, could this be causing the spotty mic problems?
I have not been subject to this issue... Yet.
As far as some people not being affected at all and others may be a combination of the port and assembly plants. HTC had assembly plants in different countries and the parts come from different manufacturers.
(I'm not a dev, just a user passing forward what I've learned)
Click to expand...
Click to collapse
I wonder if it might be related to the microphones, as htc only used the super good hdr microphones on the earlier builds, and switched to an inferior type after.
Sent from my HTC One using XDA Premium 4 mobile app
myrigon said:
Not entirely sure that's it, as I had the issue both with and without intense blast, and on different versions of ERA, which didn't cause issues on other ROMs, or earlier ViperOne releases.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm assuming that the requirements for the spotty microphone are a Sense 6-based ROM (i.e. ViperOne 6.x) and IntenseBlast installed. Could also be related to the microphone hardware.
There are also a few levels of IntenseBlast, I believe the Maximium and Ultimate Edition are the culprits, since the original edition has been shown to work. I'm guessing (I'm no dev, just a tester), that the addon disables the microphone due to power requirements to the speakers. Undervolting wouldn't help, but could be certainly related a short or cut off of power to the microphone hardware. That is why a reboot temporarily fixes the issue until it starts again. The mic seems to work fine by booting into SafeMode, further demonstrating how a mod on boot is causing the issue. However, I'm not entirely sure how IntenseBlast works, but I'm sure it contains a boot level script that doesn't run in SafeMode.
All I know is that uninstalling it fixed my problem so far. If I get it back, I would be sure to update this thread. Thanks for the insight everyone.
Edit: I tried out my luck and reflashed IntenseBlast Maximum edition... and my mic seems to be working fine. Seems that uninstalling it the first time coincidentally caused my microphone to work fine after reboot. I guess we can rule out IntenseBlast... and say that this problem is completely random... and is fully restored by rebooting the device countless times... until it cuts out again.
Have you found a solution?
I'm having the same issue and it's really driving me crazy.
Is it possible that the problem is caused by HTC Speak mod from Venom team?
rockwentz said:
Have you found a solution?
I'm having the same issue and it's really driving me crazy.
Is it possible that the problem is caused by HTC Speak mod from Venom team?
Click to expand...
Click to collapse
Not currently.
It won't be the speak mod, as I don't use it, and had the issue.
Sent from my HTC One using XDA Premium 4 mobile app
myrigon said:
Not currently.
It won't be the speak mod, as I don't use it, and had the issue.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I went ahead, backed up my user apps with titanium backup, wiped my data, and reflashed ViperOne 6.1. Haven't seen the problem since.
Sent from my HTC One using Tapatalk
BuffMcBigHuge said:
I went ahead, backed up my user apps with titanium backup, wiped my data, and reflashed ViperOne 6.1. Haven't seen the problem since.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i have the same settings as your's in the 1st post , im suffering now from this issue but what i noticed in my phone is that when i reboot the mic works as i open voice recorder and record and it works but when i use any app which access the mic like phone , viber the mic stops working
Nightf0x_007 said:
i have the same settings as your's in the 1st post , im suffering now from this issue but what i noticed in my phone is that when i reboot the mic works as i open voice recorder and record and it works but when i use any app which access the mic like phone , viber the mic stops working
Click to expand...
Click to collapse
Yes, that seemed to be the issue. When using the mic for the first time in any app that requires it, it works, but then any subsequent apps will not be able to access the mic thereafter.
A full factory reset and reflash is suitable to fix the issue. Did you dirty flash from 5.8.0?
BuffMcBigHuge said:
Yes, that seemed to be the issue. When using the mic for the first time in any app that requires it, it works, but then any subsequent apps will not be able to access the mic thereafter.
A full factory reset and reflash is suitable to fix the issue. Did you dirty flash from 5.8.0?
Click to expand...
Click to collapse
no i wiped system and data partitions , then clean installed 6.1
BuffMcBigHuge said:
Yes, that seemed to be the issue. When using the mic for the first time in any app that requires it, it works, but then any subsequent apps will not be able to access the mic thereafter.
A full factory reset and reflash is suitable to fix the issue. Did you dirty flash from 5.8.0?
Click to expand...
Click to collapse
reflashed rom , restored my apps and mods again this issue appeared i have feeling it is concerned with either xposed modules or the kernel
now wiping and reinstalling again for the 2nd time
Nightf0x_007 said:
reflashed rom , restored my apps and mods again this issue appeared i have feeling it is concerned with either xposed modules or the kernel
now wiping and reinstalling again for the 2nd time
Click to expand...
Click to collapse
Weird. What xposed modules are you using?
BuffMcBigHuge said:
Weird. What xposed modules are you using?
Click to expand...
Click to collapse
gravitybox , subsense of elementalx kernel , ice cube of ice cave xperia apps mod , halo floating window , fix for halo floating window , mutliwindow sidebar , sense 6 toolbox , expanded notifications + few other modules but not enabled
Reflashed rom and the mic is working properly for a week so far.
Perhaps the problem is from Project era; because I only flashed it along with IntenseBlast and HTC speak when I had the problem.
Xposed is not the culprit. I was using none of those mods when I had the problem.
Sent from my HTC One using Tapatalk
yes , i confirm it now zeroinfinity project era soundmod is causing this problem at least on my phone
wiped my device , reinstalled rom, kernel, mods, app, xposed mods., all have no issues but last thing i flashed is the soundmod which caused my mic to stop working , hopefully just before i flashed the soundmod i backed up my device just restored and everything now works
i will inform zeroinfinity cause i really need his soundmod:fingers-crossed:
Nightf0x_007 said:
gravitybox , subsense of elementalx kernel , ice cube of ice cave xperia apps mod , halo floating window , fix for halo floating window , mutliwindow sidebar , sense 6 toolbox , expanded notifications + few other modules but not enabled
Click to expand...
Click to collapse
Nightf0x_007 said:
yes , i confirm it now zeroinfinity project era soundmod is causing this problem at least on my phone
wiped my device , reinstalled rom, kernel, mods, app, xposed mods., all have no issues but last thing i flashed is the soundmod which caused my mic to stop working , hopefully just before i flashed the soundmod i backed up my device just restored and everything now works
i will inform zeroinfinity cause i really need his soundmod:fingers-crossed:
Click to expand...
Click to collapse
Holy S*** ... you have a Frankenstein phone ...how do you ever figure it out when things aren't working
Hi,
My N6 speakers stopped working. Headset jack still works. I'm running a rooted Purenexus with Franco Kernel. Android 7.1.1. Kernel Franco 3.10.40, Pure Nexus version 7.1.1.20170215 OFFICIAL.
I've tried :
rebooting
updating Franco to latest version
rebooting in Safe mode
Nothing helps. No sound out of either speaker using music app or youtube.
Phone is in good shape, used to work fine, has no sim currently but is used as wifi surfer.
Any ideas of how to fix? Seems like it might be a software issue, since it worked fine until recently. But safe mode didn't help, so I'm wondering if it might be hardware?