I'm using the latest LP nightly (3/27/15) and have had problems RECEIVING texts only since about the 3/19 build. Sending them works out fine, and I do eventually get the texts either later in the day or when I reboot the phone. I do use Textra, but seems irrelevant, as the stock google messaging app isn't receiving them in a timely fashion either. I'm on a Google Nexus 5 (hammerhead). I do notice upon boot and intermittently the warning at "unfortunately com.phone.android has stopped". Wondering if this is related. I WAS using ElementalX kernel for a bit, and thought that might be the problem. So this morning I flashed the nightly without flashing the custom kernel. Still the same problem. I also use Xposed framework, however left that off as well just for a test. Same results. Is this a known bug? Any other information that I could provide to help?
In case a list of the xposed modules I use would be helpful, here they are.
enable ambient display xposed
force pandora rich notification
pandora patcher
greenify
lolistat
statusbar download progress
Been a long time Pacrom user and don't wanna give up on this rom as it's always been dependable, feature packed and the best in terms of battery life. Thanks for any help in advance.
EDIT: Also, for further clarification, I do have multirom with CM12 as my secondary rom. The texts are coming in fine there. Hence why I'm convinced it's a problem with the rom and not my carrier or hardware.
Related
Hello everyone. I've done a few searches on here but haven't found this exact problem. Relevant details without extra background info are in bold.
My wife and I each got an S4 with Sprint's recent BOGO promotion. My phone has had no issues. It came with MDL in the box, which I updated to MF9 via OTA, flashed TWRP via Heimdall in Linux, rooted, and installed the hotspot mod.
Her phone - completely stock MF9 and new from the store - has had problems, one of which I've so far been unable to fix. (How I wish it were mine. I develop for Android, but this is much more of a pain for her.) Hers already had MF9 at the store. It had the Google Services Framework/Core Apps runaway process issue with heat/battery drain from the start - which I fixed. However, it also has unresponsive sensors for ~3 seconds when receiving a call. It's almost as if there's some lag in activating the sensors. The phone is otherwise snappy with no other lag noted.
- Hard reset has been tried.
- The touchscreen is unresponsive during this time, though the display functions.
- The gesture for answering (when enabled) also does not work.
- We haven't tried enabling the home key to answer, but this will be next.
I've seen this before with Android a good while back. It was an inherent problem with Gingerbread on many phones. Haven't seen it pop up in Jellybean at all. In trying to diagnose, I've ensured that all bells and whistles are turned off. No air gestures are on.
We'd really like to get it working as it should. Has anyone else experienced this? Any advice?
Many thanks!
I believe this is more of a stock software issue. I have had the issue since day one.
When I turned off svoice and some of the other added features most of the lag disappeared. Svoice is pretty good at creating lag as far as ive seen.
Voice response seems to create th lag as it is awaiting a voice command from you.
This is what I have noticed anyway.
Sent from my SPH-L720 using xda app-developers app
I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app
Hi
I ask this question here, as I’m knew in the forum I can’t write it directly in the ROM post where would be more appropriate.
I have installed the in the phone the CM13.0 ROM built by mparus, I have used the cm-13.0-20161118-UNOFFICIAL-mparus-without_root-g760.zip build, the last one in this moment. The phone works correctly, I only had a pair of minor issues:
-phone app was not working, caused a reboot when trying to use it: it’s a vanilla cyanogenmod problem, it’s solved choosing the phone app as default for making calls
-camera app doesn’t detect the camera device: I have read that is a bug of the official camera app, can be solved installing another app as open camera
I have a serious problem for which I have not found information about. It’s with the notification lights, they are not working except for indicating the charging status of the device, not for mails, missed calls, etc. I tried all the possible combinations for this without luck. I have also tried third party app’s like light manager and they don’t work also, perhaps something is broken in the build but I’m not sure.
Any of you has experienced this problem with the mparus mod in the ascend g7? Can you give me any advice? I’m a bit frustrated about this
Thank you
Do a clean re-install of the ROM I'd say..
Amazon Alexa app crashes in all custom ROMs I have tried. I have tried clearing cache, uninstalling, etc, etc. but the same bad behavior remains. Runs fine if I revert to stock. Anyone else run into this?
Same here. I am on newest lineageOS.
Yep, that is my experience as well.
I use the alexa app on my stock tablet and have removed it from custom roms on my phone.
Haven't found a workaround yes but would appreciate one.
Works fine here on Dirty Unicorns on 3 devices and SAOSP on another.
Try turning off cellular data when trying to use the app. Any problems I have had with the Alexa app have been solved with this, doesn't seem to work well with it.
chibichuba said:
Try turning off cellular data when trying to use the app. Any problems I have had with the Alexa app have been solved with this, doesn't seem to work well with it.
Click to expand...
Click to collapse
Will try that tonight. Thanks for the idea.
I will post my results.
At least I am not alone in this.
The regular pre conversations app works for me on all devices, however it does not when I add a phone number. Basically I have a problem with the new conversations. It starts to load I get all icons then a faint conversations label and then it crashes. I have tried almost all ROMs available for my moto x pure, no exaggeration. I am using DU at the moment and it does not work. Amazon thought it may be that I did not have an activated SIM card and had no data. So, I purchased and activated SIM card after having phone for almost 2 years and data does not help. Turning data off changes nothing for me as well. My sons phone is a samsung stock and his SIM card has never been activated but it works fine.
I also have been having troubles with TP-Link Kasa the most recent update is causing it to act the similar. It simply ignores my sign in. I have come to conclude their is a security validation check being used by amazon and tplink.
This kind sucks...I don't know why certain apps does this. Android was built on open source however I notice slowly they are closing Windows/doors.
Alexa app crashing solved for me!
Whenever I would hit the listen button the app would crash, if this is one of your symptoms try turning off notifications, it worked for me, found the answer in a post for Miui phones.
Ime using MaxiCM(CyanogenMod-Mod) on 5.1.1 and for me it crashed as soon as i logged in and it got Internet, using the App offline works fine but yea, no use for it.
I've been looking around these forums for quite a while now, hoping to find a near-stock ROM based on the latest NPN25.137-83 North American firmware that has integrated notification LED support. Unfortunately, I haven't been able to find anything.
This ROM is the closest thing I can find to what I'm looking for. Very nearly stock - just zipaligned, debloated, deodexed, a simple camera mod, and the LED enabled for notifications. The only downside is that it's not based on 137-83. Considering the March security patch, it seems to be based on 137-67 at the latest. And the developer of the linked ROM apparently has no plans to integrate the August security patch or the rest of the 137-83 firmware (a big problem for me considering the Verizon VoLTE bugs on 137-67).
There are other solutions too, like the Moto LED enabler app, but it's not that reliable. The blinking follows some sporadic and unappealing pattern, and it sometimes likes to stop blinking entirely after a while. The list of apps that enable the LED also seems to periodically reset itself.
So, my question is as follows: would someone release a ROM similar to the one I linked with the latest firmware and patches? Or perhaps can we just get a TWRP flashable zip to enable the LED for notifications? I'll gladly pull some weight on this if someone can point me in the right direction. Thank you!
Would really like to see this implemented as well, Paranoid Android rom I tested a while back also had this implemented very well, even works with screen on.
I'd like this as well.
I tried with Tasker but, due to deep sleep, it stops to work after few seconds of screen off (it works fine only enabling the option "Keep Device Awake" but battery drains quickly)