[Q] i777 with Omni KK. Music stops playing suddenly. - AT&T Samsung Galaxy S II SGH-I777

I'm using the latest nightly, but I've been seeing this pretty much since I started using KitKat on my phone.
The problem goes like this. I'm listening to music, and after a random amount of time, the music stops playing and the player hangs. It doesn't matter if I kill it. I have to reboot the phone to make it work again. I've tried wiping the player's cache as well as using different players and it's the same.
I've been noticing a pattern with several apps unrelated to music. The Opendelta app which I use for upgrading nightlies sometimes also hangs when patching the zip, and provides an ETA that finishes about the same time as the Universe itself.
The phone also hangs when I'm copying files in USB storage mode from my computer.
I think I read over the i9100 forums that the KitKat driver for these phone's storage is really buggy or something, and thus behaves like that.
Has anyone have had the same problem?
Is there any hope for such a driver to be fixed in any ROM or Kernel for the i777?
Should I just revert to 4.3?
I'm not very Android/Linux savvy, but I could provide system logs if needed.

Mighty_Rearranger said:
I'm using the latest nightly, but I've been seeing this pretty much since I started using KitKat on my phone.
The problem goes like this. I'm listening to music, and after a random amount of time, the music stops playing and the player hangs. It doesn't matter if I kill it. I have to reboot the phone to make it work again. I've tried wiping the player's cache as well as using different players and it's the same.
I've been noticing a pattern with several apps unrelated to music. The Opendelta app which I use for upgrading nightlies sometimes also hangs when patching the zip, and provides an ETA that finishes about the same time as the Universe itself.
The phone also hangs when I'm copying files in USB storage mode from my computer.
I think I read over the i9100 forums that the KitKat driver for these phone's storage is really buggy or something, and thus behaves like that.
Has anyone have had the same problem?
Is there any hope for such a driver to be fixed in any ROM or Kernel for the i777?
Should I just revert to 4.3?
I'm not very Android/Linux savvy, but I could provide system logs if needed.
Click to expand...
Click to collapse
This is a known issue, and there's no fix for it at this time (that I'm aware of). It has to do with Exynos devices, so you're not alone.

http://forum.xda-developers.com/showpost.php?p=51013349&postcount=569

cyril279 said:
http://forum.xda-developers.com/showpost.php?p=51013349&postcount=569
Click to expand...
Click to collapse
Hadn't seen the exFAT bit, but it isn't linked exclusively to the external SD. It happens with the internal as well. And, as I said before, with other apps besides music.

SteveMurphy said:
This is a known issue, and there's no fix for it at this time (that I'm aware of). It has to do with Exynos devices, so you're not alone.
Click to expand...
Click to collapse
Oh, I see.
I think I'll just get this over with and flash a nice JB ROM.
Just out of curiosity, has Exynos support so far been depending on Samsung or are the drivers reverse engineered by someone?

Based on the thread, and what you've reported in the OP, these issues are one and the same.
The thread agrees with you, that the issue is NOT exclusively associated with the external SD. Folks are re-formatting both internal AND external SD, and reporting positive results.
further, the Open delta issue is suspected to be related, as a "fuse daemon" issue.
Try reading the thread, even if only starting from page 17.
Happy Flashing
-Cyril
Mighty_Rearranger said:
Hadn't seen the exFAT bit, but it isn't linked exclusively to the external SD. It happens with the internal as well. And, as I said before, with other apps besides music.
Click to expand...
Click to collapse

Thanks for all this information! Very helpful

Related

Galaxy SII reboots (crashes) randomly

Good day to all.
I noticed that after DXKL3 rom, my phone reboots randomly. Sometimes it happens while I'm playing games; sometimes when I'm just about to click something; sometimes when I'm just tinkering with it.
Anyone experienced this?
daimler1727 said:
Good day to all.
I noticed that after DXKL3 rom, my phone reboots randomly. Sometimes it happens while I'm playing games; sometimes when I'm just about to click something; sometimes when I'm just tinkering with it.
Anyone experienced this?
Click to expand...
Click to collapse
Is your device overclocked?
Theonew said:
Is your device overclocked?
Click to expand...
Click to collapse
No, sir, it ain't. Here's what I did so far:
1) I cleared by browser cache from the application...
2) I formatted my SD card using the SD Formatter from this link...
3) I installed WatchDog just in case something goes wrong.
4) I move all my apps to my phone. No more apps on my SD.
I'll update my activities as I progress... By the way, I don't have Dolphin browser since day 1.
It was quite hard to narrow down which one was the culprit because I did all the abovementioned procedures at the same time without testing which of them works or not. But ever since I applied those procedures, I never got any random reboot up to this point yet.
daimler1727 said:
No, sir, it ain't. Here's what I did so far:
1) I cleared by browser cache from the application...
2) I formatted my SD card using the SD Formatter from this link...
3) I installed WatchDog just in case something goes wrong.
4) I move all my apps to my phone. No more apps on my SD.
I'll update my activities as I progress... By the way, I don't have Dolphin browser since day 1.
It was quite hard to narrow down which one was the culprit because I did all the abovementioned procedures at the same time without testing which of them works or not. But ever since I applied those procedures, I never got any random reboot up to this point yet.
Click to expand...
Click to collapse
It's possible to be #4. Maybe you moved an app to the SD which was supposed to stay on the phone. #'s 1-3 don't (usually) cause that issue.
Theonew said:
It's possible to be #4. Maybe you moved an app to the SD which was supposed to stay on the phone. #'s 1-3 don't (usually) cause that issue.
Click to expand...
Click to collapse
I have my bet on that too, sir. I just wonder why some apps were designed to be allowed to be moved on SD but might cause problems.
Anyway, up to this moment, I still got no random reboot. I'm about to conclude that it's totally cured.

[Q] SGS2 with CM9 Freezes suddenly. ROM problem?

I periodically find my phone in a frozen state/shut down (at least once a day or during the night)
I have the latest nightly CM9. I'm wondering if the freezes are caused by the ROM or i have some hardware problem or an rouge app or something.
Is there a way to see a log history of all processes so i could pin down what's happening just before a freeze? is there a better way to do this?
Thanks all
Could Be
jacksilver2 said:
I periodically find my phone in a frozen state/shut down (at least once a day or during the night)
I have the latest nightly CM9. I'm wondering if the freezes are caused by the ROM or i have some hardware problem or an rouge app or something.
Is there a way to see a log history of all processes so i could pin down what's happening just before a freeze? is there a better way to do this?
Thanks all
Click to expand...
Click to collapse
The biggest problem in cm9 is when you set your voltages/cpu too low, this can cause your device to lock up when turning it on again/opening lockscreen. Another problem which is usually the case is that you have a misbehaving app. The easiest way to counter these little niggles I have found is to do a complete wipe, format your sd card, format system etc, then attach sgs2 to pc via usb, mount your sd card and transfer cm9rom.zip to sd card. Only then flash your cm9 to your sd card in recovery after unmounting and disconnecting from pc of course. This lets you kind of narrow down the problem as you will know that you do not have any files/folders/apps from a previous rom install that are causing issues. I always do this when installing a rom, even if it is just a nightly update, since I used to get problems like yours, I do this now and have 98% less issues. But what I think you have most likely done is to underclock your device too greatly. Also, if you are using cpu profiles, make sure you are not setting screen off profile too low, otherwise it will most certainly freeze on open. Anyways, cover these bases and you should be golden. It is not a rom problem.
Slacker07, you deserve a medal
Sent from my GT-I9100 using xda premium
norpan111 said:
Slacker07, you deserve a medal
Click to expand...
Click to collapse
Like
Really thank you so much for the quick and detailed response! (I "Thanked" you off course)
Device freeze
slacker07 said:
The biggest problem in cm9 is when you set your voltages/cpu too low, this can cause your device to lock up when turning it on again/opening lockscreen. Another problem which is usually the case is that you have a misbehaving app. The easiest way to counter these little niggles I have found is to do a complete wipe, format your sd card, format system etc, then attach sgs2 to pc via usb, mount your sd card and transfer cm9rom.zip to sd card. Only then flash your cm9 to your sd card in recovery after unmounting and disconnecting from pc of course. This lets you kind of narrow down the problem as you will know that you do not have any files/folders/apps from a previous rom install that are causing issues. I always do this when installing a rom, even if it is just a nightly update, since I used to get problems like yours, I do this now and have 98% less issues. But what I think you have most likely done is to underclock your device too greatly. Also, if you are using cpu profiles, make sure you are not setting screen off profile too low, otherwise it will most certainly freeze on open. Anyways, cover these bases and you should be golden. It is not a rom problem.
Click to expand...
Click to collapse
Hello
I read your suggestion and i wonder is it the solution for device freeze during app usage? I am using CM9 and during few apps usage(Waze, temple run...) suddenly the device freeze and nothing i do can unfreeze it only long press on power button, i never touch the cpu or screen settings.
Thank you
haimram said:
Hello
I read your suggestion and i wonder is it the solution for device freeze during app usage? I am using CM9 and during few apps usage(Waze, temple run...) suddenly the device freeze and nothing i do can unfreeze it only long press on power button, i never touch the cpu or screen settings.
Thank you
Click to expand...
Click to collapse
Same problem, happened twice with Waze and several other times with ynet (news) app.
Running CM9 RC2, original kernel, no tweaks.
dannykul said:
Same problem, happened twice with Waze and several other times with ynet (news) app.
Running CM9 RC2, original kernel, no tweaks.
Click to expand...
Click to collapse
And full wiped?
ksilver89 said:
And full wiped?
Click to expand...
Click to collapse
Yes, full wiped before and after installation of ROM, installed few apps from Market, didn't use TB, have a few other friends in the office with same problem, also found this: http://code.google.com/p/cyanogenmod/issues/detail?id=5892
dannykul said:
Yes, full wiped before and after installation of ROM, installed few apps from Market, didn't use TB, have a few other friends in the office with same problem, also found this: http://code.google.com/p/cyanogenmod/issues/detail?id=5892
Click to expand...
Click to collapse
I have same problem. Is it fixed in CM9.1?

[Q] New Google Music Force Close Problems

Is anyone getting endless force closes after installing the new Google Play Music? I've tried using two different Touchwiz Roms and even CM 10.1 and all of them seem to have issues running the app. Thoughts?
+1 on that issue. I just uninstalled play music for the time being. It was ridiculous the number of times it fc'd on me
Sent from my SCH-I605 using Tapatalk 2
Yea it does it on every device I own x.x
Sent from my SCH-I605 using Tapatalk 2
so it sounds like its an error with the app? I guess it makes sense because it's such a new service but it's also weird that some people are having no issues at all.
also having force closes
On my note running jedi rom, nexus 4 and my tablet. The radio feature works fine on PC but it won't start on the 4 or my tab. The music app itself closes constantly on my note though. I uninstalled the app and reloaded a previous version so I can atleast still listen to my purchased tunes.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I had the same force close problem on my GS3 only fix I found was to unroot. Once I unrooted it worked fine.
Sent from my SGH-T999 using Tapatalk 2
It's a very strange problem that alot of folks are having, I did take the update and I've had zero problems although they did change alot in this update. Im running clean rom 4.5 with perseus kernel, no overclock or undervolt, idk if it matters what your running it should be stable either way I use it all the time but still getting used to the new look. .
M.A.D.NoTe.||
Looks like the update doesn't like too many songs. Deleted a few hundred and it works.
yeahmann said:
Looks like the update doesn't like too many songs. Deleted a few hundred and it works.
Click to expand...
Click to collapse
How many sings do u have stored
codemansGT said:
How many sings do u have stored
Click to expand...
Click to collapse
I have over 1000. It worked with 400-something.
I have just over 7000 songs. I am on an S3 on T-Mobile. I tried the new Google play music on several roms, included stock rooted and the app was unusable because of the force closes. I reverted back to the old version of Google play music, unrooted, let my music sync, then upgraded to the new version through the play store, and it has been working for 3-4 days without any problems. I rerooted the phone to test and sure enough the force closes came back. I repeated the process stated above and it works perfect again. I am convinced "root" was causing the force closes... At least in my case. Hope this helps.
Sent from my SGH-T999 using Tapatalk 2
Sloopdawgg said:
Is anyone getting endless force closes after installing the new Google Play Music? I've tried using two different Touchwiz Roms and even CM 10.1 and all of them seem to have issues running the app. Thoughts?
Click to expand...
Click to collapse
I was having the same problem and I just found a way to make it work for me.
1. Turn off phone.
2. Eject SD card
3. Reboot
4. Open Play Music and go through the setup making sure that it doesn't crash
5. Turn phone back off and insert SD card
6. Reboot
For me after those steps it is still working.
Edit: Until I put my music back on my sd card.
cmo220 said:
I was having the same problem and I just found a way to make it work for me.
1. Turn off phone.
2. Eject SD card
3. Reboot
4. Open Play Music and go through the setup making sure that it doesn't crash
5. Turn phone back off and insert SD card
6. Reboot
For me after those steps it is still working.
Click to expand...
Click to collapse
I thought the SD Card was the issue too. I've got a little over 3000 songs and I thought it was the loading process causing the FC's so I had done what you post above on 3 separate roms and all have FC'd. It has even FC'd before even launching the application. I have decided to just wait it out and hope that Google solves this issue soon. I have faith in them to get things fixed pretty soon like they usually do. Thanks for the tips though!
Sloopdawgg said:
I thought the SD Card was the issue too. I've got a little over 3000 songs and I thought it was the loading process causing the FC's so I had done what you post above on 3 separate roms and all have FC'd. It has even FC'd before even launching the application. I have decided to just wait it out and hope that Google solves this issue soon. I have faith in them to get things fixed pretty soon like they usually do. Thanks for the tips though!
Click to expand...
Click to collapse
I forgot that I had taken all my music off of my SD card before I did those steps. Once I added it back to my card it started happening again after I refreshed. But it didn't start until near the end of the refresh. It looks like there are certain tracks that it doesn't like, or after a certain amount of music on your sd card it stops working.
+1 on this issue, hope they fix it soon, having to use the touchwiz music player and it sucks.
non-rooted, galaxy s II with 4.1.2, about 3000 songs and 64 gb sd card.
Sloopdawgg said:
Is anyone getting endless force closes after installing the new Google Play Music? I've tried using two different Touchwiz Roms and even CM 10.1 and all of them seem to have issues running the app. Thoughts?
Click to expand...
Click to collapse
This time I'm pretty sure I have the fix. It is definitely working for me. There's a problem with the album art in the mp3's ID3 tags. I'm pretty sure it's only the art from a few of them but good luck finding which ones. If you delete all the album art from all mp3's you should be able to run the app without problems. You'll have to delete all the music from your phone and re copy it. You might have to delete everything you've uploaded to Google then re upload that too, but I'm not sure about the last part. Hope this helps.
cmo220 said:
This time I'm pretty sure I have the fix. It is definitely working for me. There's a problem with the album art in the mp3's ID3 tags. I'm pretty sure it's only the art from a few of them but good luck finding which ones. If you delete all the album art from all mp3's you should be able to run the app without problems. You'll have to delete all the music from your phone and re copy it. You might have to delete everything you've uploaded to Google then re upload that too, but I'm not sure about the last part. Hope this helps.
Click to expand...
Click to collapse
I was thinking the same problem being with album art but I can install Google Music without ANYTHING on my SD card and external SD card and it will still crash. It's very odd so I guess I'm just going to wait until Google pushes next update that will hopefully fix it. I've seen quite a good amount of people complaining so I'm sure Google will look into it.
Sloopdawgg said:
I was thinking the same problem being with album art but I can install Google Music without ANYTHING on my SD card and external SD card and it will still crash. It's very odd so I guess I'm just going to wait until Google pushes next update that will hopefully fix it. I've seen quite a good amount of people complaining so I'm sure Google will look into it.
Click to expand...
Click to collapse
I saw some people say yesterdays update fixed the problem but I'm not sure since I already wiped album art. If you have uploaded music to Google with album art it doesn't like that could still be causing the problem.
cmo220 said:
I saw some people say yesterdays update fixed the problem but I'm not sure since I already wiped album art. If you have uploaded music to Google with album art it doesn't like that could still be causing the problem.
Click to expand...
Click to collapse
Wow. I have not even tried updating for the past few days. I just updated, streamed a few songs, and smoothly went through my library without a single FC. Looks like they have updated and it is working just fine now for me! Thank you very much! haha

[Q] A working rom?

I really hate to make this post, but I've had such bad luck in the recent days, that I'm at wits end and need a little help figuring out whats going wrong here. As of now, I am runing LiquidSmooth 2.9... But as with all my recent flashes, there are tons of problems. Currently my issues are: external SD card doesn't show, GPS doesn't lock on (which from what I read I need to install a working GPS rom, get a lock, then reflash.. ok cool) and lastly facebook and instagram are aggravatingly slow. I can have full service, even be on Wifi... text from posts will load fast... anything else... You're better off playing the lottery than hoping a quick picture will pull up.
I don't know what I'm doing wrong here, I throw the zip file on my phone, go into TWRP, wipe cache and dalvik, install, wipe again, factory reset, reboot, and then start using my phone...
With every rom I've tried there are issues from no gps, no camera, no keyboard, bluetooth cuts out... etc...
Is there a rom that works? Or are there steps I'm missing or a fix to my said issues? Any help would be great
higherbeing said:
I really hate to make this post, but I've had such bad luck in the recent days, that I'm at wits end and need a little help figuring out whats going wrong here. As of now, I am runing LiquidSmooth 2.9... But as with all my recent flashes, there are tons of problems. Currently my issues are: external SD card doesn't show, GPS doesn't lock on (which from what I read I need to install a working GPS rom, get a lock, then reflash.. ok cool) and lastly facebook and instagram are aggravatingly slow. I can have full service, even be on Wifi... text from posts will load fast... anything else... You're better off playing the lottery than hoping a quick picture will pull up.
I don't know what I'm doing wrong here, I throw the zip file on my phone, go into TWRP, wipe cache and dalvik, install, wipe again, factory reset, reboot, and then start using my phone...
With every rom I've tried there are issues from no gps, no camera, no keyboard, bluetooth cuts out... etc...
Is there a rom that works? Or are there steps I'm missing or a fix to my said issues? Any help would be great
Click to expand...
Click to collapse
Try flashing devil kernel from the Original Development section for your SD card woes. AOSP doesn't support exFAT by default (I'm guessing that's what your card is flashed as and is why you can't see it). This kernel adds support for exFAT to any AOSP ROM.
Try enabling Force GPU Rendering in the Development Options and see if that doesn't fix your slowness with Facebook and Instagram. I personally don't use Instagram but have had no issues with Facebook on CM10.2.
Finally, you already have the fix for your GPS issues, just need to bite the bullet and get it done. The good news is that as long as you stay on AOSP ROM's you shouldn't have to do it again.
Let me know if that does/doesn't work and we can try some different options, good luck!
Thank you the GPU thing seems to have worked, doesn't seem to lag as much anymore. However, the devil kernel didn't seem to do much other than replace TWRP
I'll take that back =S pics aren't loading again.
higherbeing said:
Thank you the GPU thing seems to have worked, doesn't seem to lag as much anymore. However, the devil kernel didn't seem to do much other than replace TWRP
Click to expand...
Click to collapse
Devil kernel not recovery.
It is a kernel that will work on AOSP and TouchWiz ROMs, and in combination with the recovery allow you to dual boot one of each.
You do not want this, you want just the kernel.
ok so I've tired the devil kernel, no luck. I tried a couple different roms, no luck. Finally flashed with CleanRom3.5 and my SD card is back. But now the issue I'm experiencing is when I try and play music through spotify it randomly shuts down the audio channel. The music still plays according to the app, but I can't change songs. I can pause and hit play, but no audio. I have to force close the app, and I can then again listen to a song, maybe two before it happens again. Sometimes it happens within 2 minutes, either way I have not made through 2 consecutive songs. Any ideas on that?
try beans Jellybeans build 21.. no issues works great.
I have to be honest, I have had nothing but compatibility issues with the use of TWRP. I switched to CWM and I stopped having little glitches and hang ups in the Roms. I would give it a shot, not saying it is even the cure all but it worked for me as crazy as it sounds.
sent from my Viking slab.
higherbeing said:
I really hate to make this post, but I've had such bad luck in the recent days, that I'm at wits end and need a little help figuring out whats going wrong here. As of now, I am runing LiquidSmooth 2.9... But as with all my recent flashes, there are tons of problems. Currently my issues are: external SD card doesn't show, GPS doesn't lock on (which from what I read I need to install a working GPS rom, get a lock, then reflash.. ok cool) and lastly facebook and instagram are aggravatingly slow. I can have full service, even be on Wifi... text from posts will load fast... anything else... You're better off playing the lottery than hoping a quick picture will pull up.
I don't know what I'm doing wrong here, I throw the zip file on my phone, go into TWRP, wipe cache and dalvik, install, wipe again, factory reset, reboot, and then start using my phone...
With every rom I've tried there are issues from no gps, no camera, no keyboard, bluetooth cuts out... etc...
Is there a rom that works? Or are there steps I'm missing or a fix to my said issues? Any help would be great
Click to expand...
Click to collapse
Maybe you should try goodness Noteworthy, might also get an update this weekend
My links should still be good, if not pm me and I'll point you in the right direction.

[Q] Q&A CM11

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

Categories

Resources