Related
I flashed my first ROM last night, and tried to play music using Google Music Beta, which I downloaded from the market. When I try to play the music, the app keeps on force closing. I tried reinstalling the app, tried reflashing the rom, but nothing seems to work. Any help would be appreciated.
Did you perform a full wipe before flashing the rom? I'm running 2.1 (remix) as well using mr2.5 and the kernel that came packed with BAMF 2.1. Having no issues using google music beta. Don't have much in the way of advice, just chiming in to help you narrow down where your issue is coming from (namely that the rom itself shouldn't be the issue). Might want to verify the md5, never know when you might snag a bunk download.
Suboof said:
Did you perform a full wipe before flashing the rom? I'm running 2.1 (remix) as well using mr2.5 and the kernel that came packed with BAMF 2.1. Having no issues using google music beta. Don't have much in the way of advice, just chiming in to help you narrow down where your issue is coming from (namely that the rom itself shouldn't be the issue). Might want to verify the md5, never know when you might snag a bunk download.
Click to expand...
Click to collapse
Yes, I performed a full wipe before flashing the ROM, assuming that means data/factory reset, cache, dalvik cache, battery stats...did that three times. Not sure if I am supposed to do it more. Also checked the md5, downloaded and flashed it twice more after the first time, and still can't get it to work.
Hrm, afraid I don't have much else to suggest outside of verifying settings within the music app itself. As I said, was primarily just letting you know the rom itself shouldn't be the issue. Sorry I cant be of more assistance . Might try a different rom and see if the issue persists, but if you're liking the 2.1 thats far from an actual solution even if it does solve the problem.
Suboof said:
Hrm, afraid I don't have much else to suggest outside of verifying settings within the music app itself. As I said, was primarily just letting you know the rom itself shouldn't be the issue. Sorry I cant be of more assistance . Might try a different rom and see if the issue persists, but if you're liking the 2.1 thats far from an actual solution even if it does solve the problem.
Click to expand...
Click to collapse
Never mind, I thought I got it working, but after playing a song, it crashed. I might just go back to stock rom, not a really big issue.
hksg said:
I flashed my first ROM last night, and tried to play music using Google Music Beta, which I downloaded from the market. When I try to play the music, the app keeps on force closing. I tried reinstalling the app, tried reflashing the rom, but nothing seems to work. Any help would be appreciated.
Click to expand...
Click to collapse
I was having the same problem (just 20 minutes ago). The app would load, the albums and tracks would appear, and then when I went to play one of them it would force close. What I did to correct the problem was to to reflash 2.1 in recovery without wiping. I let in reboot and now its working fine.
I am running bamf 2.0 - 5 and it works for me.
Although it Sometimes makes my phones signal drop to 1x so maybe flash a new radio?
THUNDERBOLT
poisonj5 said:
I was having the same problem (just 20 minutes ago). The app would load, the albums and tracks would appear, and then when I went to play one of them it would force close. What I did to correct the problem was to to reflash 2.1 in recovery without wiping. I let in reboot and now its working fine.
Click to expand...
Click to collapse
Tried this, then even flashed the new ROM RC1 and RC2, and still am unable to get it working. Any help is appreciated. I just keep on getting the same issue, Error playing requested track. And then when I go to check the app data, I see the numbers going in and out, flickering, and have to force stop and then uninstall.
hksg said:
Tried this, then even flashed the new ROM RC1 and RC2, and still am unable to get it working. Any help is appreciated. I just keep on getting the same issue, Error playing requested track. And then when I go to check the app data, I see the numbers going in and out, flickering, and have to force stop and then uninstall.
Click to expand...
Click to collapse
same for me. I'll be going back to stock or another ROM until this gets solved
theredspecial said:
same for me. I'll be going back to stock or another ROM until this gets solved
Click to expand...
Click to collapse
ATM, I am using Lighting Rom 3.3.1, which is a Froyo ROM, but I might try one of the other Gingerbread ROM's available. But I really did love that DasBamf ROM, and the issue seems to be amongst just a few of us.
Bump.
Still having Google Music force close on Das BAMF RC3. Can anyone confirm that it works?
I can confirm I'm having the same issue with BAMF 2.1 stripped. I tried reloading the rom without wiping and fixing permissions and still getting a force close when I attempt to play anything from the cloud.
Sent from my ADR6400L using XDA Premium App
hksg said:
Bump.
Still having Google Music force close on Das BAMF RC3. Can anyone confirm that it works?
Click to expand...
Click to collapse
It is listed as a known issue in the RC3 thread, but they are having trouble reproducing it. I had the same problem with RC1, but after I wiped and loaded RC3, it appears to be working fine now. I only loaded it last night and tested a little this morning though, so problems could still develop. When I was having trouble with RC1, I tried the procedure of uninstalling Google Music, unmounting SD card, reinstalling Music, and then remounting SD card. It didn't work with RC1, but I did the same thing prior to testing Music on RC3. I have no idea if that made any difference either way, but it won't hurt to try.
Edit: The known issue could be referring to the HTC Music app, not the Google one, now that I look at it again.(Still reading through the entire RC3 thread)
FreemanB said:
It is listed as a known issue in the RC3 thread, but they are having trouble reproducing it. I had the same problem with RC1, but after I wiped and loaded RC3, it appears to be working fine now. I only loaded it last night and tested a little this morning though, so problems could still develop. When I was having trouble with RC1, I tried the procedure of uninstalling Google Music, unmounting SD card, reinstalling Music, and then remounting SD card. It didn't work with RC1, but I did the same thing prior to testing Music on RC3. I have no idea if that made any difference either way, but it won't hurt to try.
Edit: The known issue could be referring to the HTC Music app, not the Google one, now that I look at it again.(Still reading through the entire RC3 thread)
Click to expand...
Click to collapse
It was indeed the HTC Music app that is the known issue. I posted in the thread, and I provided a logcat, so hopefully someone with more experience than me can understand it.
I'm having the same issue on DAS BAMF 2.1 on latest lean kernel.
I can get it working 99% of the time with wifi only. If i use 3g or 4g the app force closes. I've tried different kernels as well.
Anyone else able to confirm if this issue is wifi/3g/4g related? Im able to use the player only if I use wifi.
Maybe this can help the devs push out a patch in 2.2
I am using it right now on RC3
Sent from my ADR6400L using XDA Premium App
I'm also able to get it to work if i wirelessly tether to another thunderbolt. Only time I have an issue is if I'm using the 3g/4g radio.
I just go to Google music and play from the cloud
Sent from my ADR6400L using XDA Premium App
BlackHoleSlam said:
I just go to Google music and play from the cloud
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I mean I can access music.google.com from the browser but that kind of defeats the purpose of the app/widget.
My friend who has the same rom isn't getting the issue.
A lot of times when I'm listening to music and the screen is off, the music stops playing. Pressing the headset button does not resume the music, I have to turn on the screen and press the play button.
I had this problem on KE7 as well as I have it on KF2, my phone is rooted, currently I use PowerAMP, but if I can remember correctly, I've encountered the issue using Doubletwist as well. I even tried hard resetting, but the issue persists (I didn't really start from scratch but rather restored my user apps from a Titanium Backup).
Before I go through the tiresome task of uninstalling all the apps and installing them back one by one, I decided to ask for your help. Maybe somebody already managed to resolve a similar issue...
Settings> Motion> disable it... It may be because of the motion sensors... If you tilt the phone in a certain angle, the music stops playing...Just try, if it didn't work, then there is a problem...
This seemed to be happening to me when using PlayerPro. However, I had the trial and paid for versions installed, and it seemed to be the trial version doing this. Switching to the paid for version stopped the issue.
Could PowerAmp be behaving the same?
waynej4 said:
This seemed to be happening to me when using PlayerPro. However, I had the trial and paid for versions installed, and it seemed to be the trial version doing this. Switching to the paid for version stopped the issue.
Could PowerAmp be behaving the same?
Click to expand...
Click to collapse
I have bought the full version, so it can't be this. The motion theory is interesting, but the phone was sitting on my desk when it happened today. Will try disabling it anyway.
Setting motion control to off did not help either. ;(
Sent from my GT-I9100 using Tapatalk
Hey man, im experiencing the same problem.
Glad to hear im not the only one. Ill be following this thread for answers. Im using PowerAmp as well.
Well, nice to hear I'm not alone.
I will try using doubletwist for a day or two, to see if it's a PowerAmp thing. But if memory serves me well, I already expirienced the same issue before buying PowerAMP.
Sent from my GT-I9100 using Tapatalk
Just came across this thread:
http://powerampapp.com/forum/viewtopic.php?f=4&t=1274
Interestingly somebody mentions Google Listen as the culprit. I do use it a lot. Will try removing it and report back. BTW: Pocket Casts is free today on Amazon Appstore!
Freezing Google Listen defenitely helps.
I'm having the same problem, both with the stock player, and BBC iPlayer.
I'm also using Google Listen... so it'll be a shame if it's that which causes the problem.
I've just checked my Listen settings: it's set to check for new updates once a day, but I've had the players stop more than once in one day. I also had 'send anon feedback' switched on. I've turned that off.
I'd really like to hear if it's the confirmed culprit (and how to remove or freeze it) - cheers
I've also heard the problem could be when the phone is switching between 2G and 3G mode: as I'm in a basement office, I have poor signal quality, so there's a chance that's to blame...?
Well I use Google listen on my nexus one for a year now, and it never shows up in my apps list using battery, nor does it ever appear in system panel lust using no CPU. Its been just fine.
I've found the music is stopping when I get Gmail messages (though not every time)... so it's one of my Gamil widgets, the Status bar (though I have notifications turned off) or the Social Hub.
Once I've backed up all my data I'm going to do a Factory Reset
Update:
I've done a factory reset, that didn't stop it.
I've removed the Gmail widget, that didn't stop it.
I've gotten a brand new replacement phone, that didn't stop it.
I've tried a different music player (UberMusic), that didn't stop it.
Anyone got any more ideas?
sorry to bump old thread, but Im also facing this issue and couldnt find it anywhere except this thread.....
Currently on resurrection remix rom 2.3, not too sure what gives
kedirakevo said:
sorry to bump old thread, but Im also facing this issue and couldnt find it anywhere except this thread.....
Currently on resurrection remix rom 2.3, not too sure what gives
Click to expand...
Click to collapse
Maybe post in rr thread instead?
Sent from my GT-P7510 using xda premium
kilometers4 said:
Maybe post in rr thread instead?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
i had this issue with other roms also before... but since RR is my current rom so i just... u know...
But yea maybe i try posting in RR thread too, see if anyone can help
kedirakevo said:
i had this issue with other roms also before... but since RR is my current rom so i just... u know...
But yea maybe i try posting in RR thread too, see if anyone can help
Click to expand...
Click to collapse
I think i managed to solve the issue, I uninstsalled DSP manager through TB
So I have a Droid X2, now un-rooted and back on stock 2.3.4 and this is an issue I have had since I had the phone and have never found a fix. I have asked this multiple times on the Verizon forum for the DX and never get an answer...
SO every day I seem to have issues with my notifications going mute, sometimes, but not always, my ringer even goes mute. Usually once a day I have to reboot my phone because it is the only way I can fix it. I thought at first it had to do with my blutooth, but since SBFing and going back to stock I have not re-added my blutooth and it still happens. I took it into the store and he suggested that it is an app causing a conflict and I should uninstall 10 or so apps at a time to try and narrow it down... but I just went ahead and did a factory restore to see if it would help... but it happened again today...
Now, the notifications I use are ones I put on the phone. I have tried putting them on the SD and the internal and it seems to happen with both. I have also put them directly on and also tried ringdroid but it still does the same thing. The sound and notification levels will be all the way up, and when you go into the settings and try to pick a notification sound or ringtone, even the stock ones, you wont hear anything (and you would usually hear a preview of the sound)... The only way I can get the sounds to work is to reboot the phone and when it comes back, it will be fine... for a while. Sometimes have to reboot multiple times a day, but almost always at least once a day to get them back up...
Since you all seem smarter than the Verizon folks and have been a huge help to me thus far, I thought I would ask here and see if anyone else has ran into this and has a fix or if there are any known apps that would cause this. I have done searches but found nothing...
Is your music player ok?
Sent from my MB870 using XDA App
king..kranium said:
Is your music player ok?
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
You know, I have never thought to check. I will next time it happens. I rebooted the last one earlier and its been fine, but I am positive it'll happen again here later...
king..kranium said:
Is your music player ok?
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Okay... happening again. Nope. Music won't play. Says something about not being able to play that type of file. Just regular music that plays any other time. If I reboot the phone I'm sure it'll work. Any ideas?
I have the same issue of notification sounds going mute randomly. I'm using galaxy tab P1000, android 2.3.3
sometimes music player stops playing songs randomly too!
DroidTalk said:
I have the same issue of notification sounds going mute randomly. I'm using galaxy tab P1000, android 2.3.3
sometimes music player stops playing songs randomly too!
Click to expand...
Click to collapse
I hate to say it, but finally good to hear someone else is having the same issue. Ive not found anything on it and cant seem to get helpfrom anywhere to fix it! Hopefully one of the smart people here will be able to help!
Happened to me again. This time right after i updated google plus app.i had to restart to get it back.
kalojado said:
Okay... happening again. Nope. Music won't play. Says something about not being able to play that type of file. Just regular music that plays any other time. If I reboot the phone I'm sure it'll work. Any ideas?
Click to expand...
Click to collapse
What rom are you on?
Sent from my MB870 using XDA App
DroidTalk said:
Happened to me again. This time right after i updated google plus app.i had to restart to get it back.
Click to expand...
Click to collapse
Hrmmm, I don't have g+ installed, so I know that isn't it for me... but same thing, I reboot and it comes back...
king..kranium said:
What rom are you on?
Click to expand...
Click to collapse
No rom. I was rooted but un-rooted and went back to stock gingerbread...
I upgraded to android 2.3.6 overcome 4.1.0 (its a custum rom for galaxy tab). Lets see if it resolves the issue. I'll report back if the problem happened again.
DroidTalk said:
I upgraded to android 2.3.6 overcome 4.1.0 (its a custum rom for galaxy tab). Lets see if it resolves the issue. I'll report back if the problem happened again.
Click to expand...
Click to collapse
Awesome... thank you!
I've had a similar issue but not exactly the same. I normally keep my phone on silent mode but sometimes during the day it will automatically go off silent mode. Seems to happen most often when the battery level is below half. I just learned to live with it. My alarm would deactivate by itself in Froyo, so at least this isn't going to cause me to be late for work like that.
Problem is solved here after last week's upgrade. I'd suggest flashing a new build if possible. I guess for some unknow reason, parts of the OS gets corrupted or maybe its a bug in device drivers for our android phones thats been addressed in later builds.
kalojado said:
So I have a Droid X2, now un-rooted and back on stock 2.3.4 and this is an issue I have had since I had the phone and have never found a fix. I have asked this multiple times on the Verizon forum for the DX and never get an answer...
SO every day I seem to have issues with my notifications going mute, sometimes, but not always, my ringer even goes mute. Usually once a day I have to reboot my phone because it is the only way I can fix it. I thought at first it had to do with my blutooth, but since SBFing and going back to stock I have not re-added my blutooth and it still happens. I took it into the store and he suggested that it is an app causing a conflict and I should uninstall 10 or so apps at a time to try and narrow it down... but I just went ahead and did a factory restore to see if it would help... but it happened again today...
Now, the notifications I use are ones I put on the phone. I have tried putting them on the SD and the internal and it seems to happen with both. I have also put them directly on and also tried ringdroid but it still does the same thing. The sound and notification levels will be all the way up, and when you go into the settings and try to pick a notification sound or ringtone, even the stock ones, you wont hear anything (and you would usually hear a preview of the sound)... The only way I can get the sounds to work is to reboot the phone and when it comes back, it will be fine... for a while. Sometimes have to reboot multiple times a day, but almost always at least once a day to get them back up...
Since you all seem smarter than the Verizon folks and have been a huge help to me thus far, I thought I would ask here and see if anyone else has ran into this and has a fix or if there are any known apps that would cause this. I have done searches but found nothing...
Click to expand...
Click to collapse
I'm certainly no dev, just an avid user who likes learning and tweaking to get the most from his phone. I recall having similar problems with FROYO stock or rooted which as I remember went away when GINGERBREAD came out. I've been running DZK's CM7 beta as my daily driver since it was released with virtually no problems and unlike most other ROM's does not need multiple tweaks and scripts to scream with the exception of a wifi and/or dialer glitch that looks like Moonshadow has recently fixed. Sooooo unless HDMI is a deal breaker I'd suggest you flash CM7 and see if that takes care of your problems just remember to abide by the cautions regarding use of TBU to restore apps. And lastly as a rule of thumb I reboot my phone every morning once I get to 100% charge...force of habit I guess.
Good luck
Sent from my MB870 using Tapatalk
Thanks everyone... I havent been on because it strangely hasn't been happening. Not sure what changed. Did not uninstall any apps, and have not had any updates (as far as I know... well besides app updates) and for some reason it hasnt been happening lately. Again, no idea what changed. Still unrooted on stock 2.3.4 gingerbread and phone seems fine now. Been happening for months and when I finally come here to get help, the problem seemed to have went away. I will keep you all updated if this changes. Hopefully if it is happening to anyone else, it has also been fixed... Thanks again for all your help. Really appreciate you guys helping out this noob
what i did
i have an mb870 too with no service running google voice and groove ip . my issue with notifications
was with my kids hitting all the button selections she could. in the process my message notifications
got defaulted to the wrong messaging app. i was still getting messages but no tones or vibrations.
so i just went to all the messaging apps i have and made sure to select the right one for the default
hope this helps
Just curious how many people are having issues with stock Google apps and the stock browser after the ota update. The Gmail and maps will get stuck on a white screen as does the stock browser and the play store will just lock up on whatever screen it was currently on. Google wallet will freeze during the unlocking your device notice. These are the only ones I have found so far but I had none of these issues before the ota update. A phone restart will fix it for a period of time but I'm currently having to restart my phone 2 times a day to get the apps to work properly again.
Sent from my EVO using Tapatalk 2
I also forgot to add that during the restart after the screen turns off you can will change the ring volume up and down and hear it change for 2-3 seconds before the phone actually does restart. I noticed this when I had my Bluetooth headset still connected and it was not telling me it was disconnected for at least 4-5 seconds after the screen turned off unlike before the update when it was no more than a second.
Sent from my EVO using Tapatalk 2
juanm269 said:
Just curious how many people are having issues with stock Google apps and the stock browser after the ota update. The Gmail and maps will get stuck on a white screen as does the stock browser and the play store will just lock up on whatever screen it was currently on. Google wallet will freeze during the unlocking your device notice. These are the only ones I have found so far but I had none of these issues before the ota update. A phone restart will fix it for a period of time but I'm currently having to restart my phone 2 times a day to get the apps to work properly again.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Mine does this as well, the only "fix" I have found for it is rebooting the phone. Then it works for a few days until it randomly decides to freeze again.
I was having the same problems where the browser will be a white screen and not work. I went twrp and wipe cache/dalvik cache and haven't had a problem since
Sent from my EVO using Tapatalk 2
Same problem here
Sent from my EVO using xda premium
I have been having the same problem also been having random reboots at times
I'm rooted and flashed the latest firmware, is there any way it can be undone
Sent from my EVO using xda premium
After the update! The stock browser doesn't highlight the the URL address when tapped like before...Instead we have to manually delete the URL to search something else or press the little X after tapping on the URL.
Wtf!? Yeah count me in too. I just did a restart and it didn't fix problem. Gwallet still in notification bar saying initializing.
Sent from my EVO LTE
Also been having the same problem since updating, most noticable with the browser just being a white screen. Tried wiping cache & dalvik cache again, doesn't seem to help. Stock ROM with S-OFF. Surprised I haven't seen more mentions of this problem, but perhaps it's not widespread?
Well as I've learned over my time at xda updates are always catch 22's. That's why I choose to wait and read users feedback on how the latest ota is functioning. However none if this is revelant to your issues just figured I'd post it for future reference. Also have you guys tried a full wipe of your current rom? After you make a backup of your data of course to see if that will help ??
#Root-Hack_Mod*Always\=LTE
Yeah...I was having the same problem after the ota, but after a couple of reboots things started to work right.
Im having this too, is getting very annoying. Sometimes i just want to use the phone quickly for something and have to re-start the phone... I feel like breaking it against the floor.
Sent from my EVO using xda app-developers app
I too am having the same issue. Play and browser all fail to respond. Wiped cache etc. Still repeats each time.
Sent from my EVO using xda app-developers app
I wound up here after searching for this error, which just started with me yesterday with the browser (stock). It just displays a white screen when I try to use it.
I've had the latest update (flashed with 1.22.651.3 odexed ROM from xHausx and firmware from Captain Throwback) about a week now and this just started happening yesterday.
Yesterday I somehow got it to work again by clearing the Internet cache and then I performed a search from the Google search bar and all was well. I was thinking at the time that it was stuck on a particular page and that this got around it. But that fix isn't working for me today, so I'm going to try to clear dalvik/cache from twrp as recommended here and see where that gets me.
It's good to know I'm not the only one though... I wonder if there's anything else more specific we all have in common since we seem to be a fairly small subset. Maybe we all flashed the Odexed update for example?
EDITED TO ADD: Appears to affect Gmail too. And possibly several other Google apps as mentioned here and in other threads. Since there was a Gmail update I did yesterday, I'm going to try to uninstall that as mentioned in this other thread I found http://forum.xda-developers.com/showthread.php?t=1810829
CheriePie said:
I wound up here after searching for this error, which just started with me yesterday with the browser (stock). It just displays a white screen when I try to use it.
I've had the latest update (flashed with 1.22.651.3 odexed ROM from xHausx and firmware from Captain Throwback) about a week now and this just started happening yesterday.
Yesterday I somehow got it to work again by clearing the Internet cache and then I performed a search from the Google search bar and all was well. I was thinking at the time that it was stuck on a particular page and that this got around it. But that fix isn't working for me today, so I'm going to try to clear dalvik/cache from twrp as recommended here and see where that gets me.
It's good to know I'm not the only one though... I wonder if there's anything else more specific we all have in common since we seem to be a fairly small subset. Maybe we all flashed the Odexed update for example?
Click to expand...
Click to collapse
Install chrome. Problem solved.
njfoses said:
Install chrome. Problem solved.
Click to expand...
Click to collapse
NOT helpful at all since it affects not only the stock browser but other Google apps as well.
Refer back to my original post which I updated with additional information.
I've found if I reboot and never use the stock browser I don't have the white screen problem. I set maxthon as the default and act like the stock browser doesn't exist.
Sent from my EVO using Tapatalk 2
I reverted back to the previous version of Gmail yesterday hoping that would fix the problem but it still happened. This morning when I clicked an email notification from my status bar, Gmail did the white screen thing and needed to be shut down manually. Just to verify that this and the browser incident were related, I tried to launch the stock browser and it too was white screen.
So those of you suggesting to install an alternate browser to get around this issue need to understand that this is a lot more widespread than the browser alone. For me, both my Gmail and Google Offers were white screens this morning upon trying to launch them so it definitely appears to affect all Google apps.
Yeah this happens to me as well. Its really bad now. Nothing fixes. It does it on all the roms with newer OTA for me. Only two roms will work for me without this problem. I have tried everything. Wiped everything, Reflashed, Checked my sd card, factory reset, you name it. It even does it on restored roms that didn't have the problem before. I don't know what to do....
A developer told me to try and manual flash boot.img through fastboot but I'm not even sure how to do that. Need to read up on it.
I have had the issue to wear when I am trying to open the browser app, it will actually freeze the entire phone until I hit the home button repeatedly in play store will not load anything until I fully restart the phone I've tried fixing for missions do a nandroid restore nothing seems to work
Sent from my EVO using xda app-developers app
Sorry if this thread already exists.
You have no idea how happy I am this ROM exists!! But I cannot get SMS working. I get FC's on every SMS app I try including Hangouts. Anybody else getting this and/or have a remedy? Thanks
I was about to post the same error here, I have an Amaze with Videotron, S-Off, Super CID, HBOOT-1.93.2222 (JuopunutBear), TWRP as a recovery.
I tried everything, I tried different Gapps, I also tried without installing Gapps, I tried sms apps from the Play Store and Hangouts too. The only thing I haven't tried is formatting my internal SD card. (it was a clean install, all formatted and cache cleared). I also tried switching to ART but I had the same problems.
Everytime I try to just open the sms apps, the app crashes. I managed to see the error once and it was something about SQL but it might be a misinterpretation from my part.
Calls, 4G and WiFi were all working perfectly too.
After some research on Google, I tried installing busybox, xposed framework and uninstalling Voice+, but nothing works. The basic messaging app just closes without any kind of message and other apps show that it stopped working.
(I tried the Evervolv rom 4.4 and SMS were working on that one, maybe it's a setting with my network type as I am on Videotron in Canada and it is using AWS, maybe a setting under *#*#4636*#*# ??)
I want to contribute and sen some log of that error, how can I do that? I am familiar with roms, kernels, etc but not that much with logs... I tried many roms before and never got that specific problem...
Thanks to anyone who can help with this issue!
It's not just you SMS simply doesn't work on this rom and I was surprised to see that no one else pointed this out in the original thread. The default Messaging app closes immediately when you try and open it. Other SMS apps also crash either immediately upon opening them, or when you try to send a message (hangouts & SMS Pro for example). This is the only thing keeping me from using this amazing rom as my DD.
I have the same exact problem with SMS- will try the evervolv 4.4 though was really looking forward to CM11
Edit: also didnt have any other problems with the rom except for the black boxes and the camera
Let's hope there is a way to fix it!
I would post the question in the official thread but I do not have enough posts to do so unfortunately
Heck I couldn't even try SMS due to the black box issue, that's why I didn't mention it in the original thread.
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
anybody get the SMS working on this ROM so far?
pbergonzi said:
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
Click to expand...
Click to collapse
The black box issue has nothing to do with GPU or CPU speeds. There are discussions on the dev threads. The issue affects other legacy devices on various KK based source builds, not just Amaze and CM. The consensus is this seems to be related to the default browser which has changed in KK. This would also explain why it effects other gapps too.
MS92 said:
anybody get the SMS working on this ROM so far?
Click to expand...
Click to collapse
Not that I'm aware of.
Media Issues
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
ranwal said:
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
Click to expand...
Click to collapse
Maybe app settings for the app and Erase App Data?
can i get a link for the updated adreno drivers? thanks!
865DETH said:
can i get a link for the updated adreno drivers? thanks!
Click to expand...
Click to collapse
Yes you can its on last three pages of orignal thread you also have to sign up for that
Sent from my HTC_Amaze_4G using Tapatalk
as the OP says and i quote that only non working things are
1. camera exposure
2. tethering
but as the thread goes ahead we read more prolems/bugs
May i ask what is the current status for bugs/not working and other issues and what has been fixed and any other stuff we should flash over the ROM like driver, may it be upoaded to the OP for ease as its reall hard to search for those things on mobile app. thank you and good luck.
Anyone else have issue disabling their microphone while in a call? I tried with both the speaker phone and regular handset mode, the "no mic" icon enables but my caller can still hear me. The Hold button seems to work fine though.
FYI, it took a while for the battery to figure itself out. I wiped the battery stats before flashing everything and the first few days I got a lot of jumping battery levels. I let it charge all the way down as much as I could then rebooted and did a full charge and rebooted again and then full charge again. That seemed to reset the battery level to the correct state.
I also , enabled Device/GPS only for the location detection other wise the google services at 50% or more battery.
I'm running the 2014-02-16 build, with the updated video drivers.
Camera is not working
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Any updates for the camera isssue??
Shahxz said:
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Click to expand...
Click to collapse
Since PAC uses the CM device tree for its source any issues with CM will also be evident in PAC. Until the CM devs are able to resolve the camera exposure issue it will exist in both ROMs.
Librastar said:
Any updates for the camera isssue??
Click to expand...
Click to collapse
Think about your question for a minute. Have you seen any recent posts in the CM dev thread indicating an update which solves this issue? If you had just taken a moment to look at the dev thread instead of posting this you would have answered your own question. It's not like the CM-11 thread is incredibly long, it's only 28 pages total. This post is just laziness on your part and an unnecessary waste of bandwidth.
is there any alternate app in the market, i tried couple of apps but nothing useful
@Odysseus1962
If I were to compile AOSP, which variant would you suggest for me to build?
Sent from my SAMSUNG-SGH-I747 using Tapatalk