Hi I am having a few issues with the 10.1 galaxy and wondered if anyone can help. When I click and hold on txt to highlight it so I can copy and paste to another section most of the time it doesn't work and will still have the last copied txt whatever that was saved. After a few times of trying eventually it will say copied to clipboard but is well annoying how do I get it to work properly.
Problem 2, emails I receive often have URL addresses of stuff to check out, in the email I am unable to highlight the txt at all so can't copy and paste it see what I'm looking at, any one had similar problems, any solution?
Yup. I had copy-paste-select issues all the time.
In the custom roms though I dont remember having any issues (though I switch roms for 2 days now I might not have enough experience).
I think its some lame stock roms programming by samsung. What rom are you on?
thanks for the response, not sure am using version 3.1
Kernel 2.6.36.3
Do these things come preloaded with a lot of Samsung software they most people wipe. I find mine crashes a bit and whilst watching video via the add on cable through my 42tv its regular as clockwork will stutter, is that poss related to some ****ty software on here?
Thanks again
Hi All,
I seem to have funny problem with certain items under Settings>>Call. I can't access some of the items there (Call rejection, Set reject messages, Call alert, Call answering/ending and Video call image). Each of those causes com.android.phone crash.
Anything else relating Phone.apk doesn't crashes at all. I am using rooted stock I4.
Anyone had such problems or maybe have some idea on fixing this. I didn't spent much time messing around with system itself, and although Phone.apk replacment seems like cure I am not sure how hard or dangerous is to extract it from some firmware and just replace it.
Thanks in advance,
Vladimir.
vandric said:
Hi All,
I seem to have funny problem with certain items under Settings>>Call. I can't access some of the items there (Call rejection, Set reject messages, Call alert, Call answering/ending and Video call image). Each of those causes com.android.phone crash.
Anything else relating Phone.apk doesn't crashes at all. I am using rooted stock I4.
Anyone had such problems or maybe have some idea on fixing this. I didn't spent much time messing around with system itself, and although Phone.apk replacment seems like cure I am not sure how hard or dangerous is to extract it from some firmware and just replace it.
Thanks in advance,
Vladimir.
Click to expand...
Click to collapse
Try this..
go into settings->applications-->manage applications-->all-->call setting-->clear data..
I can't find such item in manage applications. Anyway I did few "resets" which cleared all data but didn't help.
Thanks.
No wonder no one else experienced this, since doubt anyone is dumb enough to rename CallSettings.odex.
Anyway, if someone succeeds and have same problem that is probably it!
FYI!
Samsung Galaxy SIII Stock ROM has leaked! S Voice and all other goodies are up for grabs!
Go to: http://forum.xda-developers.com/showthread.php?t=1646610
Link for S Voice: [Dropbox Link]http://goo.gl/AgNJk
This works ONLY on ICS. But, just because we have ICS, doesn't mean that it will automatically magically work, it is just that ICS is a prerequisite to make it work.. I don't have a DX2 anymore, so you guys need to test this out and see if it works!
Install it as a system app: Push it to /system/app and change permissions to rx-r--r--. Then, choose "Samsung powered by Vlingo" for Voice input in settings.
Anyway, I am trying to use it on my Droid Incredible 2 on a fairly stable ICS ROM and it is still waaaay too buggy, crashing almost at every search query. So we still need some devs fixing this up!
Thanks, hopefully someone can get this working 100% for us. Did a voice search for Facebook and sure enough it worked. Then I used it to send myself a text message and I'm not in my contacts so I spoke each digit individually and it picked it up and sent my text. Got it and everything lol. Only issue I noticed so far is that when you try to change the wake up phrase from Hi, Galaxy it instantly force closes. But I'll keep playing with it. Thanks again
Edit: Also works for making phone calls. Every once and a while she'll tell me "An unexpected server error has occurred, please try again."
DX2 running ICS on CM9
I am not responsible for what you do to your phone
First off, I'm sorry if it seems like this has been answered before, but I did a good deal of searching and couldn't find anyone who had quite the same problem I do.
I've been using Agrabren's CM10 - Disarmed Toaster for CDMA since Friday. But I ran into a "storage running low" problem this morning (after I let my phone go dead last night and then put it on the charger overnight) which caused me to do a full wipe and re-flash with his latest version (0.2.2). Since then, I haven't been able to receive texts at all. I have Google Voice, and I was getting the texts there, but not in the actual messaging app. I have since tried disabling and re-enabling Google Voice to no avail, and it is currently disabled to remove extra variables. I haven't been very scientific about my troubleshooting process, which has mostly involved a lot of flailing around, wiping, and re-flashing. But I've re-installed the ROM countless times and twice now have flashed a Sense ROM (MeanROM 2.6) to update my PRL and Profile and then flashed back to CM10. I suddenly got a flood of all my texts when I flashed to Sense, but still don't get any texts after flashing back to CM10.
I tried Paranoid Android and AOKP variants and have the same problem. I even tried Team DIRT's CM10 Codename Android and texts still didn't come in. I should also mention that I had the same problem a while back with Disarmed Toaster 0.1.6, and it probably started the same way with running out of battery and then having the storage low issue and re-flashing. I never figured out exactly what the issue was, but I think at the time I was able to fix it by flashing a Sense ROM and updating profile and PRL.
Sorry for the long explanation. Let me know if there is any other info I can provide to help. I really didn't want to go back to MIUI, but that might be only option at this point.
Also, for reference:
HBOOT - 1.40, S-Off
Recovery - 4ext 1.0.0.5 RC5
THANKS
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
efan3719 said:
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
Click to expand...
Click to collapse
Thanks. I already asked there and I've been following the thread. I don't think anyone else has mentioned this problem.
Sent from my PG86100 using xda app-developers app
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
coal686 said:
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
Click to expand...
Click to collapse
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Jsparta26 said:
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Click to expand...
Click to collapse
That's an interesting thought, but it doesn't seem to explain why no one else is having the same problem, or why it worked at one time, and then didn't work after I re-flashed.I guess there could be something wrong with the flash process that was corrupting that file on my phone. But I was able to *send* sms without a problem, so I'm not sure.
As I mentioned before, I've been following the threads for the ROM and no one else has mentioned the same problem. I asked the question in the thread, but I didn't get an answer.
Anyway, as I mentioned above it's working now, so I wouldn't be able to provide a logcat unfortunately. For anyone else with the problem, I guess the only suggestion I can give it to make sure you keep a backup of a working ROM handy if you're going to re-flash a lot.
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
mastadave99999 said:
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
Click to expand...
Click to collapse
Haha...
Just so you know, once you've cleared out the 4G logs, you can make that directory "immutable" so that the logs don't get created anymore. Just run this command in terminal emulator:
chattr +i /data/wimax/log
I'm obviously not an android developer, and I have no idea why the logs are still created. I also have no idea what caused the text message issue, but if you are currently not getting texts, I would suggest you restore a working backup and then re-flash Agrabren's ROM like I did.
SMS Help!!
soldierforchrist2 said:
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
Click to expand...
Click to collapse
Has anyone figured out why SMS stopped working? I am running AOKP JB ROM and I can send text messages but I am not receiving them. Thanks for your help.
Still not working
I've been having the same problem with the sms, it works if you re-flash something else a couple times then flash CM10 back on but sms will only work for so long. I would like to pick apart the problem and see if we cant find the source of the problem, it could be a temp file that CM10 has been saving that interferes with the sms, but that's just a guess. any help on this is greatly appreciated
Just wanted to say I too have encountered this. I have tried flashing unofficial aokp 3.5 and unofficial slimbean 1.1. Getting ready to flash an MIUI rom like mentioned above.
Some Experimenting....
I did a small experiment just now (to try and get incoming SMS working) because I had essentially experienced the EXACT same problem, except that it was with P.A.C.MAN v.23 instead. What I did was installed a stock-based rom (I used unSENSABLE), which obviously allowed all my SMS to come flooding in, and stayed on that rom for about a day. After that I made a nandroid backup (of unSENSABLE) in 4ext, wiped everything except sd (not using the superwipe, and including caches) and then restored the backup. After that I booted up, let it sit for a while, then restarted into recovery. Again I wiped everything without using the superwipe, and flashed P.A.C.MAN v.23.0.0 and then GAPPS and booted. After all that, SMS was working again. We'll see how long it lasts...
Here goes. I have the 4.1.1 Omega v32-XXDLJ5 ROM with Siyahkernel v1.7rc2 on my I9300.
Now the problem is, the ROM was working perfectly without any hitches, but today when I tried using Google Voice app, the voice failed to take my input and kept asking me to tap the microphone icon onscreen. I can see that it is registering the voice (with the visual representation surrounding the microphone icon), but there is no feedback. Upon checking further I found that the same issue is with Samsung's Assistant as well. It is not providing any feedback.
Unfortunately that's not the end. I also found that the dictation in messaging etc. of Google voice isn't working either. So, basically, they all are listening to my voice but not providing any reply/feedback.
Same issue had happened to me before 10 days. At that time I had felt that I might have tweaked with some setting somewhere which resulted in this issue (did a nandroid restore to resolve it). But this time around, i haven't done anything which would have caused this issue.
Can anyone help me to find the cause of this issue, and if anyone knows what/where the fault is, your help in resolving this issue will be appreciated.
I know I can reflash the rom/restore the nandroid backup, but it also means having to re-install everything/some from scratch, which is a pain. And also, those don't identify the source of the problem. And this being the 2nd time, it might very well be repeated a 3rd or more number of times.
Did you try fix permissions in CWM.
I have the CWM 3.60, but i get a notice that this ver of CWM should be used with CF-CWM v1.1 or newer, so, various options have been diabled. Maybe that's why I don't have the fix permissions option. Any idea about this?
NB: Found the option in CMR and it fixed the issue right up. Thnx a lot buddy