Related
Im running CM10.1 nightlies. I think this started with the 0308 release, but know it has been prevalent in the 0311 release, and 0312 release I just flashed. I have no sound notification at all on text or pic messages. I am running stock messaging and audios. I can go in and choose a different audio for the notification, they all play the sample when you choose them. So I choose one, and close it out. But when I get a text.... nothing. If I dont check the phone, I never know if Im getting messages.
Ive tried it with vibration both enabled and disabled, and with the visible notifications enabled and disabled. It just flat out will not play a sound when messages arrive
SilverFox66 said:
Im running CM10.1 nightlies. I think this started with the 0308 release, but know it has been prevalent in the 0311 release, and 0312 release I just flashed. I have no sound notification at all on text or pic messages. I am running stock messaging and audios. I can go in and choose a different audio for the notification, they all play the sample when you choose them. So I choose one, and close it out. But when I get a text.... nothing. If I dont check the phone, I never know if Im getting messages.
Ive tried it with vibration both enabled and disabled, and with the visible notifications enabled and disabled. It just flat out will not play a sound when messages arrive
Click to expand...
Click to collapse
What hboot are you on? Did you upgrade from 10.0 and if you did, did you wipe dalvik/cache and system? I'm running 10.1 0311 and am having no problems. I'm on 1.09 hboot though. I would recommend going back to a stable backup, then using your recovery(I'm using the latest twrp) to wipe the dalvik and cache and system, not factory reset, then flashing the update and the newest gapps. This worked for me but like I said i'm on the early hboot and I know that makes a difference.
Im on HBoot 1.14
I did a factory reset when I went from 10 to 10.1
The audio worked fine for the first couple nightlies on 10.1 I dont remember exactly which on started giving me issues
not going to have time for awhile to mess with it or try re-flashing. D/L Go Messenger, and it plays the notification sounds just fine
I just wanted to be sure that I am going to do this right.
Do I just go Settings > About phone > CyanogenMod updates > then download 10.1 and it will do all the work for me? Or do I have to make a nandroid backup (going to do that anyways), wipe cache and dalvik, flash boot.img then flash the rom?
Also, how stable is 10.1? Any known bugs?
kylepont said:
I just wanted to be sure that I am going to do this right.
Do I just go Settings > About phone > CyanogenMod updates > then download 10.1 and it will do all the work for me? Or do I have to make a nandroid backup (going to do that anyways), wipe cache and dalvik, flash boot.img then flash the rom?
Also, how stable is 10.1? Any known bugs?
Click to expand...
Click to collapse
The automatic updater will not work. At least if you're S-On. So flashing through recovery is the way to do it (wipes and boot.img flashing as usual also ofc). I believe flashing CM10.1 over CM10 might work without factory reset, but prepare for stuff not working and flashing it again with proper wiping.
Bugwise I'd say CM10.1 is absolutely ready as a daily driver. Wifi tether doesn't work when screen is off (same issue is with CM10). Performance is a bit lower than with CM10. You'll see some screen tearing when scrolling and switching home screens and in some games with intense graphics.
Give it a go! It's not too hard to go back to CM10 if it doesn't please you.
Sent from my One S. Please hit thanks if I helped.
zaak00 said:
The automatic updater will not work. At least if you're S-On. So flashing through recovery is the way to do it (wipes and boot.img flashing as usual also ofc). I believe flashing CM10.1 over CM10 might work without factory reset, but prepare for stuff not working and flashing it again with proper wiping.
Give it a go! It's not too hard to go back to CM10 if it doesn't please you.
Click to expand...
Click to collapse
This will be a tl;dr story so only read it if you can be bothered...
I did the automatic update, then as soon as it downloaded I had to run for the bus (one a bloomin' hour). I was then stuck on the htc splash screen for about ten minutes, did a soft reset, went into recovery, went back to CM10, restored the backup, not a problem. Then got home, pushed 10.1 onto the phone, flashed the new boot.img, then flashed CM10.1 and restored backup again. Worked fine. Then I had to try three different Gapps because two of them didn't actually work, and it was agonising that the website that I got them from only had an upload speed of around 0.4Mbs. But flashed that now, and everything works fine (although I had to delete and re-download NatWest and Play Music).
zaak00 said:
Bugwise I'd say CM10.1 is absolutely ready as a daily driver. Wifi tether doesn't work when screen is off (same issue is with CM10). Performance is a bit lower than with CM10. You'll see some screen tearing when scrolling and switching home screens and in some games with intense graphics.
Click to expand...
Click to collapse
Spotted a couple of bugs immediately. Syncing with facebook simply does not work (I only wanted contact pictures for caller IDs). Obviously the clock bug, but I know how that is fixed. Haven't had any screen tearing yet, and since Orange only give me 750MB there is nooooooooo way that I am going to use tethering, so that won't bug me. CM10.1 has fixed the music player bug, where the first song I play would take around 30 seconds to play, if I chose another song then it would restart the previous song, play that for five seconds, then play the selected song, and if I paused a song it would then start playing again for a couple of seconds after five seconds of being paused. That was irritating. Noticed it seems to be a fair bit more RAM heavy than CM10, but I miss the settings button on the top of the notification bar, that tiles thing just seems to take to long for my liking...
kylepont said:
Noticed it seems to be a fair bit more RAM heavy than CM10, but I miss the settings button on the top of the notification bar, that tiles thing just seems to take to long for my liking...
Click to expand...
Click to collapse
You can also swipe down with two fingers, or set a specific area that opens the Quick Settings immediately, in Settings
Sent from my One S using Tapatalk 2
usaff22 said:
You can also swipe down with two fingers, or set a specific area that opens the Quick Settings immediately, in Settings
Click to expand...
Click to collapse
Already knew about the sections thing, but because I'm right-handed every time I wanted to look at a notification I got settings, and setting it so that the settings open on the left side just seems a bit weird. I didn't know about the two fingers thing, and I like that, cheers.
Skyrocket i727 running CM-10.1-20130807 nightly. Apex launcher. On Rogers with UCMC1 radio.
It's running stable with the (big) exception that occasionally (once or twice a day) the four buttons at the bottom (settings/home/back/search) will not respond to any touch. The only way to fix it is to restart the phone. I searched the forums and cannot find an answer to why this might be happening, nor to anyone else having this problem. I have the backlight on these buttons disabled (to save power).
Also, this might be related or maybe not, but on Monday I had a very strange crash. The HOME button wouldn't work, but the BACK button and SETTINGS button did. The notification bar wasn't functioning and no push notifications were coming through. The quick-settings panel was reverted to default, and the buttons within the quick settings panel were completely unresponsive.
Even stranger, Chrome was unresponsive, Maps/Navigation were constantly force-closing, and in general the phone was throwing a massive fit over almost anything I did. I pulled the battery but that didn't help. I was forced to go into recovery mode and perform factory reset, wipe dalvik cache, and reinstall the ROM. This has worked (although a PITA) but the issue I mentioned first (bottom buttons not working) has manifested itself since then.
Any ideas what to do here?
Much appreciated!
Eric
Run the recent nightly. Could be an issue with your rom, although I haven't seen your problem.
I just flashed the most recent nightly a few minutes ago.
Should I go back into recovery and wipe cache and dalvik? (note: When I flashed the ROM through CM Updater / TWRP, it 'optimized' 119 apps... so I think it automatically wiped the cache...?)
curls00 said:
I just flashed the most recent nightly a few minutes ago.
Should I go back into recovery and wipe cache and dalvik? (note: When I flashed the ROM through CM Updater / TWRP, it 'optimized' 119 apps... so I think it automatically wiped the cache...?)
Click to expand...
Click to collapse
You should be ok. I never go back and wipe caches
The original issue is still occurring even on newest nightly. Completely random (using different apps each time - Facebook, Messenger, Youtube, etc...).
Any idea if a setting I can change is causing this?
mtdew said:
Hardware failure.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
LOL time to sell then!
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!
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