I am running the latest AKOP 4.2.1 From Ktoonez and Sask
THE ONLY ISSUE I AM HAVING IS SMS is very slow takes 5 seconds to 20 to send a single TEXT HELP WITH ZIP
BiggTeddy25 said:
I am running the latest AKOP 4.2.1 From Ktoonez and Sask
THE ONLY ISSUE I AM HAVING IS SMS is very slow takes 5 seconds to 20 to send a single TEXT HELP WITH ZIP
Click to expand...
Click to collapse
it is a known bug you will have to wait till it is fixed or flash something else
Related
A port of IAmTheDarkOne's 4.2 rom from the Nexus S. Can't really test what works and what doesn't as it keeps displaying an error that the process com.android.phone has stopped. If anyone knows how to fix it hopefully it can help us have a fully working 4.2 rom.
Link to rom
http://www.mediafire.com/?2d8d6yr4abzn5ov
ubnub82 said:
A port of IAmTheDarkOne's 4.2 rom from the Nexus S. Can't really test what works and what doesn't as it keeps displaying an error that the process com.android.phone has stopped. If anyone knows how to fix it hopefully it can help us have a fully working 4.2 rom.
Link to rom
http://www.mediafire.com/?2d8d6yr4abzn5ov
Click to expand...
Click to collapse
The FC ( process com.android.phone ) is kernel related. try to use the stock kernel that came with IAmTheDarkOne's 4.2 rom
khan_frd2002 said:
The FC ( process com.android.phone ) is kernel related. try to use the stock kernel that came with IAmTheDarkOne's 4.2 rom
Click to expand...
Click to collapse
Still happened.
Try using a stock cm10 kernel
Sent from my Nexus S 4G using Tapatalk 2
replace the phone and contact apk files with those from an aosp 4.1.2 rom
this trick help you but you cannot make calls and baseband should be unknown
the only thing is that deleted the phone.apk and contacts.apk and then install the rom. its boots up fine with no fc
build a new kernel aint that hard
Hi all,
For the last month, my Gnex (toro) has been having sms not send occasionally (about 1 in 4). The majority will go through but about 25% will reveal the error Unable to Send Message (despite being on LTE). I was using the MMuzzy 4.3 build (with franco kernel r395) when it started.
1) clean flash with franco kernel r193 and same thing persisted (tested with radios 4.2.2 and 4.1.1)
2) clean flash with MMuzzy 4.2.2 build and franco kernel r384 and same thing persisted (tested with radios 4.1.1 and 4.2.2)
3) clean flash with CM 11 snapshot with franco kernel r395 (tested with radios 4.1.1 and 4.2.2) and same thing persists
To isolate the problem at each step, I use the stock messaging application but troubleshoot with Hangouts and same thing occurs. I also will enter the SMSC code at each step too if the problem is noted.
The ROM has been switched and doesn't seem to be the causing agent. Same for the kernel version and radios. I can't for the life of me figure it out.
Please help. It's so annoying.
My e980 is running CM11 nightlies for 2 weeks now - clean flash from stock ROM. I experience random reboots once/twice a day. Any help? Any ideas how to record logcat or sth like that?
wjazdbitu said:
My e980 is running CM11 nightlies for 2 weeks now - clean flash from stock ROM. I experience random reboots once/twice a day. Any help? Any ideas how to record logcat or sth like that?
Click to expand...
Click to collapse
:bump:
been having the same problem!
Have you found a fix?
Hi,
I recently upgraded to Android 4.4.2 and I have the latest CM 11 Nightly installed.... cm-11-20140217-NIGHTLY-d2att.zip
I installed pa_gapps-modular-full-4.4.2-20140531-signed
and installed the latest modem firmware modem_CWM_I747MUMUEND3
My problem is that the phone keeps randomly rebooting.... no idea why.... anyone else experience this issue?
Also the phone tends to freeze for about 3-6 seconds.... strange....
Other then the random reboots the phone seems to be working quite well. no issues at all.
Any help is appreciated!!! thanks!!
Could be a sensitive power button
Well that's why there called nightlies it might just be a bug....its weird that there hasn't been a stable build yet.....but you can try the monthly snapshot and see if that works
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Try an AOSP-based ROM or return to stock to see if it still happens.
After CM 13 rom was flashed build from 17th was ok,then I did update to 18th December build and now this happens on every rom.
Any ideas what to do?
EDIT: ok so after about 5 minutes when phone got cooler it went away and is now okay... anyone has idea why this didn't happen before? could the phone be overheating?
patt2k said:
After CM 13 rom was flashed build from 17th was ok,then I did update to 18th December build and now this happens on every rom.
Any ideas what to do?
EDIT: ok so after about 5 minutes when phone got cooler it went away and is now okay... anyone has idea why this didn't happen before? could the phone be overheating?
Click to expand...
Click to collapse
This is an old well known problem with CM and other CM based Roms. Your problem of split in the screen goes away if u turn the screen off and on again. This will happen on every reboot. In order to get rid of the problem completely u need to flash kitkat boot stack from the link below (for TMO D851 only and not for other variants).
https://www.androidfilehost.com/?fid=23991606952594903
After this u can flash the latest modem of your choice.
Stick to stock rom. CM is garbage
Still_living714 said:
Stick to stock rom. CM is garbage
Click to expand...
Click to collapse
Phone is not mine. Here is what I think: Stock is garbage,laggy , CM: rocks
patt2k said:
Phone is not mine. Here is what I think: Stock is garbage,laggy , CM: rocks
Click to expand...
Click to collapse
I have been running stock since I bought the phone and mine still isn't laggy. Sure when I have tons of apps then I notice lag but cmon. Yeah cm is faster but at what expense?having bugs that make the phone useless?...