I downloaded CM10 from here.
http://forum.xda-developers.com/showthread.php?t=1858295
But after a while, usually several hours of standby, when i wake TF101 up, there will be no sound, and I have to reboot it to make the sound back.
Does anyone have the same problem?
Thx
I reverted back to stock because of this (and other issues). It's really annoying to reboot just to get audio back.
See:
http://forum.xda-developers.com/showthread.php?t=1523358
http://forum.xda-developers.com/showthread.php?t=1884295
http://forum.xda-developers.com/showthread.php?t=1920025
etc.. lots of people having issues. I believe an update fixed it, though I'm not sure.
figure it out,
there is an issue with the Kernel or the CPU Governor. to fix the No Sound Issue (on calls or on any type of sound) just do the following:
1. under settings, go to performance
2. chose processor
3. set the "set on boot" which will restore processor settings on each reboot, thos will make the phone reset the processor settings.
4. reboot
alternative :
I know that changing the Kernel can also do the trick, but this way is less dirty
good luck
Let me start off by saying I am not completely sure where to post this.
I currently flashed my phone with Viper rom 3.1.0 for my HOX AT&T.
It works great but i have come to find one problem, my speaker doesnt work on anything but speaker calls not movies or music. Resaon being is that it states the beats audio was not found.
I installed this app https://play.google.com/store/apps/d...ng.beats&hl=en but i found my phone soundless not even a peep.
So then i tried this: http://forum.xda-developers.com/showthread.php?t=1692233 flashed it into my phone and still no sound.
So I reflashed my phone with the same rom and option doesn't seem to be available.
Has anybody faced this problem and if so has anybody gotten to a solution?
I tried using the Cyanogen 10.1 which works great but mobile data connection keeps dropping constantly forcing me to move to airplane mode and back to get data working again.
Any help appreciated.
Have you tried using cm10 or AOKP roms?
Sent from my One XL using XDA Premium
Did you do a full wipe (factor reset, wipe cache, wipe Dalvik, all in TWRP, not in bootlaoder) when you flashed? Also, don't restore any system data with Titanium (or similar backup apps). Might be a silly suggestions, although it doesn't hurt to state the (seemingly) obvious.
Wouldn't hurt to re-download ViperXL and re-flash.
You might also try to reboot into Safe Mode, just to make sure its not a 3rd party app that is causing the problem. Safe Mode is similar to button sequence for bootloader, except start pressing the vol down right after the white boot splash screen comes up. The phone will appear to boot normally, but you will see "Safe Mode" in the corners of the screen at all times. You will also not have any access to any installed apps.
I'm on ViperXL 3.1.0, and haven't experienced any such issues with the speaker or Beats on my AT&T One X. So I'm suspected its just a bad flash, or some 3rd party app causing the issue.
Hello,
my tablet is producing a very loud "pop" noise when speaker turns off (ie. after any sound). Galaxy Nexus seemed to have the same (hardware) issue, but I believe that mine is caused by software, as it started after I flashed CyanogenMod 10.1 (latest nightly). I'm running following setup right now:
DhollmenCM (but I flashed cyanogenmod over it, not sure if it's still here)
CyanogenMod 10.1 latest nightly
GApps for CM 10.1
Before installing CM everything worked well (but the original ROM is **** and I need profiles). How am I supposed to fix this?
I've had that before as well. Do you by chance have any audio enhancing software installed besides DSP Manager? Programs like Volume+ are notorious for this.
DSP Manager has everything disabled, nothing else is installed.
First I would try to remove DSP just to see if that's the problem.
Here is a simple app that I use to remove apps that the ROM's have in them that I don't want. I usually do it after I flash because I don't feel like opening the ROM on the computer and removing them ahead of time.
https://www.dropbox.com/sh/u4wijb1zwzdd3pn/4TyYtOpd1x
If removing DSP doesn't solve your issue and you didn't have this problem previously, I would reflash wiping "everything" before flash, including data. Since at that point there would be no way to be certain what is causing it. I don't believe the kernel could be the problem as I am running CM10.1 and the Dhollmen kernel as well and don't have any issues.
I have reflashed everything many times - with no effect. After removal of DSP there's no difference too.
pzduniak said:
I have reflashed everything many times - with no effect. After removal of DSP there's no difference too.
Click to expand...
Click to collapse
But did you wipe the system before flashing?
This is critical to make sure you have a clean installation, without it there are pieces that get left behind and cause all sorts of issues. If you have wiped, then it sounds like you have developed a hardware issue. Did it get dropped any time recently?
pzduniak,
I don't know if you're still having this problem, but I ran into this problem too. It was driving me nuts. It started happening when I was playing Pixel Dungeons.. then crept to my alarm and popped every time sounds played. I tried the DSPManager thing to no avail, but I tried this and so far have not heard any popping. I'm still testing, but I went into system>build.prop (I'm on a Sprint Galaxy S3, so just find build.prop on your device). In build.prop (make sure you're rooted so you can make changes), change the line that says lpa.decode=true to false. reboot and try that out. I researched very little about lpa.decode, but I remember having a problem in stock with battery drain and lpa.decode.. I dont know if it's true at all but give that a shot and let me know if the pops go away!
Good luck!
mtran2988 said:
pzduniak,
I don't know if you're still having this problem, but I ran into this problem too. It was driving me nuts. It started happening when I was playing Pixel Dungeons.. then crept to my alarm and popped every time sounds played. I tried the DSPManager thing to no avail, but I tried this and so far have not heard any popping. I'm still testing, but I went into system>build.prop (I'm on a Sprint Galaxy S3, so just find build.prop on your device). In build.prop (make sure you're rooted so you can make changes), change the line that says lpa.decode=true to false. reboot and try that out. I researched very little about lpa.decode, but I remember having a problem in stock with battery drain and lpa.decode.. I dont know if it's true at all but give that a shot and let me know if the pops go away!
Good luck!
Click to expand...
Click to collapse
I had been having this popping problem for a while now, and Google brought me here. I went ahead and changed the lpa.decode to false like you suggested and it worked like a charm! Thanks mtran2988!
Yeah, yeah I know! I'm either really brave or really dumb. If I was you I probably still wouldn't do this until we have a way to flash a stock ROM, but it does work.
*ROOTED T-MOBILE V20*
I have successfully flashed Viper4Arise - Deuteronomy (Viper4Android). The driver installed fine and I am currently listening to music with increased volume level, bass, viper clarity, etc. I have rebooted multiple times to make sure it didn't loop or anything.
What I did:
1) Went to this thread: http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
2) Clicked AndroidFileHost
3) Navigated to the latest Deuteronomy release, which happens to have been today.
4) I used Flashfire to flash the zip.
5) After the reboot I opened Viper4Arise and had to change FX Compatible Mode to "Compatible" to make it work.
6) Profit. :highfive::highfive::highfive:
Big thanks to the creator of Viper and this new version.
Note: There is currently a bug for Viper on Android N. Sometimes if music playback ends or you unplug headphones you will have to reboot to get Viper to process again.
Sweet ,love viper but it'll have to wait till I can get root on Verizon v20
Sent from my VS995 using Tapatalk
It works for me too. A little broken tho. I have faith tho they will work out the bug in N
The G.O.A.T. said:
It works for me too. A little broken tho. I have faith tho they will work out the bug in N
Click to expand...
Click to collapse
What is yours doing? Is it that bug where you have to reboot?
Does it affect the DAC performance? The fact that there was no system-level EQ and the only EQ I could find was the LG music player which is decent, it'd be nice to have a system wide EQ, especially by output.
Finally got this working because I'm apparently a moron and forgot to allow storage permissions to arise.
Now viper coupled with that ridiculously powerful DAC and my hd 380s bump and shake my head. Nice!!!
I've finally decided to flip the switch, so the 14.1 nightly builds are running (though they are built only once a week, due to the current infrastructure limitations).
The official builds are signed with private keys (for good security reasons), so there's no plan to provide any unofficial builds by me, to avoid the hassle of switching between different keys.
I'd like to thank @Loader009 for the donation of his retired xt897 devices to me, it greatly helped to make the transition from 13.0 to 14.1 much less painful.
Please let me know about the issues you encounter when running 14.1. In the case of the device crashes, I need to see the output of "cat /proc/last_kmsg" from adb shell, captured after the device rebooted after the crash. Thanks in advance.
I've got it flashed on my RAZR HD XT925 JBBL with the DPI changed to 320. I bought it secondhand and it came with KKBL so I downgraded to JBBL. Most things run fine but some apps that render off the GPU like Temple Run 2 and Subway Surfs show artifacts (random black squares and multicoloured artifacts). This occurs both in Lineage OS 13.0 and 14.1, what's the cause of this to occur?
I've noticed only two problems:
1 - NFC doesn't work properly. I can't read any tag. Android Pay also says, that device is not supported to use NFC.
2 - I use 2 custom layouts for physical keyboard and hot-keys like CTRL+Space don't work. I tried to modify the layout to make it work, but it doesn't work while typing (since space key in use, maybe)
I just installed it yesterday after a complete wipe (and format data/cache f2fs), and think I've got it all set up the way I like except launcher, and didn't run into any real problems yet.
I can't figure out how to get the expected shift/capslock behaviour from hardware keyboard. Still playing with settings.
It didn't come with an APN for freedompop but I found that info on another thread here, before applying that I didn't get LTE, only 3G or no data at all (at the places I've been in last day or so).
I dunno anything about NFC, but Android Pay installed for me with Aroma Gapps, haven't tried using it, doubt it'll work for tap-to-pay tho, as it didn't work for the last few versions of CM either, something to do with PN544 driver or something.
Did LineageOS come with trebuchet? I ended up with only the google now launcher, but maybe my gapps install erased trebuchet, I used aroma for the first time and may have selected things wrong... this one seems I can't customize much, can't get rid of google search bar, can't set background as solid color, can't set background color of app drawer at all which is back to a grid like kitkat.
Play store says firefox not compatible... dunno why. Maybe something I didn't select right with Aroma gapps, although every other app installed fine. Totally unrelated to LineageOS or our phone, but I wish I could find an idiots guide for aroma app selection, explaining what each app is for, particularly system apps I'm not familiar with.
edit: had one reboot, also had errors about MTP host stopping pop up...
enigma9o7 said:
I just installed it yesterday after a complete wipe (and format data/cache f2fs), and think I've got it all set up the way I like except launcher, and didn't run into any real problems yet.
...
Did LineageOS come with trebuchet? I ended up with only the google now launcher, but maybe my gapps install erased trebuchet, I used aroma for the first time and may have selected things wrong... this one seems I can't customize much, can't get rid of google search bar, can't set background as solid color, can't set background color of app drawer at all which is back to a grid like kitkat.
Click to expand...
Click to collapse
Trebuchet is the default launcher for LineageOS. Your Gapps deleted it. Also, if you use a smaller GApps, there is no google search bar ie its not installed. I personally use OpenGapps Pico.
Nightly build from 2017-07-28. Wi-Fi not working. Is it just me?
//EDIT: Tried older builds, too. Wi-Fi did not work with any of them. Flashed back to CM 11.0 and it worked again. Tried LineageOS 13.0 and Wi-Fi worked, too.
//EDIT2: Okay, I think I've figured it out. When I flashed the LineageOS 14.1 after I flashed the phone with previous versions, the Wi-Fi worked alright. It stopped working after changing File system to f2fs.
//EDIT3: Fine, I actually don't know, what happened, but I just changed the File system to f2fs again, flashed the phone with LineageOS 14.1 one more time and the Wi-Fi surprisingly works. I have absolutely no clue, why it did not work after the first flashing.
Shift key not working as expected
I already posted this in a seperate thread a few days ago, but I've got no response and it's driving me crazy, and I assume anyone who is still using this device is because of the physical keyboard, so probably relevant to all.
How do restore traditional "shift" behavior? I want to be able to press then release shift, and the next key I press is shifted. Right now I have to hold shift and another key simultaneously if I want capital letters or symbols from the numbers. I think there even used to be an LED that light up when shift was pressed/released until the next keypress, although I'm more concerned about how it actually works than the led...
I've played with most of the settings on the attached screenshot, other settings only seem to make things worse, sometimes making nothing happen at all for shift, sometimes putting out garbage, sometimes messing with capslock behavior (which is working normally with these settings, although no LED either)... but I certainly haven't tried everything.
If this is standard behavior for everyone using L14.1 and not a setting, is there a file I can modify or a 3rd party app, or anything, to get behavior I want?
rootdefyxt320 said:
I've got it flashed on my RAZR HD XT925 JBBL with the DPI changed to 320. I bought it secondhand and it came with KKBL so I downgraded to JBBL. Most things run fine but some apps that render off the GPU like Temple Run 2 and Subway Surfs show artifacts (random black squares and multicoloured artifacts). This occurs both in Lineage OS 13.0 and 14.1, what's the cause of this to occur?
Click to expand...
Click to collapse
hi
the version that you flashed in your xt925 was the oficial one released by LOS?
did u do any kind of port or mod?
enigma9o7: I've had the same problem sometimes back with the older builds of LineageOS 14.1. Try to clean flash it with the newest build from yesterday. I just tried to type something with the physical keyboard and the Shift button just worked "correctly".
EDIT: Okay, I think I've figured out your problem. You probably use the Asanti v2 keyboard setting. Switch it to Asanti v1 and the Shift key should work as expected.
Krlos Eduardo said:
hi
the version that you flashed in your xt925 was the oficial one released by LOS?
did u do any kind of port or mod?
Click to expand...
Click to collapse
It's the official 14.1 one for XT897.
rootdefyxt320 said:
It's the official 14.1 one for XT897.
Click to expand...
Click to collapse
without doing any port?
Should updates work thru the updater?
I just tried doing it, it downloaded succesfully, then rebooted into TWRP, but didn't do anything. So I tried installing myself (took me a while to find the file btw) and it failed zip signature verification. So I downloaded it on my PC, copied it over via USB, then tried again, and still fails.
kabaldan said:
I've finally decided to flip the switch, so the 14.1
Click to expand...
Click to collapse
@kabaldan, I noticed that a number of device trees in LineageOS now have a new branch of "lineage-15.0", but the xt897 does not. Is this an ominous sign that the xt897 will not be built for Oreo?:crying: or is just a timing thing at this early stage:fingers-crossed:
any hope for running it on mb886?
mb886 - atrix HD - ...you can test it if is your bl unlocked and twrp installed.
Mainboard have same base - msm8960. But i am now 100% sure if your phone is bl free unlockable. if not, then you can test to unlock it via sunshine.
I have installed this and for a while all was fine. But I was browsing in chrome when all of a sudden it froze and the phone restarted and went into a boot loop just showing the bootloader unlocked screen. I cleared the cache and dalvik cache from TWRP, which makes it boot, but any attempt to uninstall or launch chrome makes it happen again. Now it just seems to be happening at random without even opening chrome.
How can I wipe my device completely and start again? I know I can do a factory reset, but is there a lower level way to wipe it? I also saw something about changing the filesystem, is that worth doing (can it make it a bit faster)?
I have ordered a gemini PDA that I hope will arrive by late january or sometime in february, but I need this phone to get me through a couple more months!
Installed this a couple weeks ago, upgrading from a 4.4.4 CM after a number of apps I run on this finally dropped support. I did a complete wipe including the f2fs formats as suggested and it installed without incident.
I cannot believe how well it runs: keyboard works and lights up on pull out, turns off on close, hdmi port works, gps, camera+flash works. It really didn't lose any speed from my older install. Really well done, I was afraid there would be bigger problems but only a couple small ones so far.
The couple things I noticed: slow to get carrier signal and voice is garbled when using freedompop's dialer or google hangouts on the bottom mic. Slow signal seems normal, even 4.4.4 had this issue, though it can sometimes take a few minutes. Using a sound recorder shows the bottom mic working, but using fpop/hangouts dialer makes it garbled. Top mic, speaker phone, always works though. I don't have regular service to see is default dialer has same issue though, just freedompop free service which is just voip.
Still, this is a pretty awesome breath of life on this old thing. Ram holds it back somewhat but it's still pretty useful.
So I just wiped everything, repaired filesystems, and reinstalled. Data and cache were already f2fs so nothing to do there. But I noticed that during install it says:
twrp patching system unconditionally
unknown command [log]
unknown command [log]
Do I need a newer version of TWRP? I have 2.8.6. I noticed that at least 3.0 is available: https://forum.xda-developers.com/showthread.php?t=1887070
Here is 3.1.1-0 for you
https://drive.google.com/file/d/1vO4_nq3FNquuO3neHrOzuIb5gnmN11AZ/view?usp=sharing
CornholioGSM said:
Here is 3.1.1-0 for you
https://drive.google.com/file/d/1vO4_nq3FNquuO3neHrOzuIb5gnmN11AZ/view?usp=sharing
Click to expand...
Click to collapse
Thanks!
I've now installed the latest TWRP and reinstalled Lineage, gapps and su, and I didn't get any errors this time
But I have a really odd problem which I was hoping this would fix and it hasn't - I can't download certain applications from the play store, they say "Downloading" but they never actually start to download. Eventually either it mysteriously stops trying to download or I get an error message with code 492. It seems to be applications that are over a certain size. I've been googling but can't find any solutions that work. I have a lot of free space in all partitions. Did something with the directory structure get screwed up maybe? Seems like some problem with the dalvik cache I think, but wiping doesn't seem to help. I have no idea at this point