Related
Ok so I have been looking over the forums and I hope I didn't miss it if there is a post already about this so I am going to go ahead and ask away. If it has been posted and I did miss it then I apologize for beating a dead horse.
I have tried the Liquid Gingersense (v1.4, v1.5, and v1.6) and CyanogenMod (v7.1.0-RC1.5.2 and v 7.1.0-RC1.6.1) and have not had any luck. Along with some minor esthetic issues I had with the CyanogenMod, I had noticed that the Gingersense actually disabled my radio and I was unable to make any calls and the signal bars would just show up with an "x" next to it. I rebooted many times and kind of tinkered around and tried other ways of turning it on or playing with LTE on/off to see if that would help in any way and I never did get it enabled.
When I would look at the "Quick Setting" (if I recall the name correctly), the icon for me to enable it was greyed out so clicking on it did nothing at all. Has anyone had this issue? Did I perhaps miss doing something when setting this up? Any help on this would be greatly appreciated.
You mentioned that you had no signal with Gingersense but not with Cyanogenmod so I'm not sure if this is your case but did you flash the radio suggested for those roms? MR2, GB leak, etc. If not, you can find links in the pinned thread at the top of the Q/A.
Also, remember when switching between roms to wipe data/cache.
No actually I did not try that. So if I do get time to do that do I do the ROM then the radio thing? I do believe I came across a.radio deal and thought " I wonder if I need to install that?" But never tried. I figured it safer to ask and not break my phone than to break it and figure out how to fix it...lol
Sent from my ADR6400L using XDA App
Ya sounds like you need to flash an Mr2 or higher radio. Check the q&a stickys for links and instructions.
Sent from my HTC Thunderbolt
Well I decided to give it another shot. I have GingerSense v1.7 installed and did the MR2 install and it all works perfectly. I have a few apps I need to reinstall and a couple icons to redo but other then that everything looks great and seems to work smooth. Thank you guys for the help. I greatly appreciate it.
Actually the only issue I am having right now is that every...I dont know maybe 5 minutes or so there is an error that pops up that Im not sure how to get rid of. It says...
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly. Please try again"
Any ideas or thoughts about this?
Well I think I have discovered the root of this error. I have noticed that when I text and if o click on the Mic to do voice to txt that even though the screen pops up as if it OS going to record, it does absolutely nothing. How to fix it is where I am still stumped though.
Sent from my h4x0r3D ADR6400L using XDA App
Well it seems I have been noticing some weird things that are making me think maybe I should try Gingersense v1.5
At first my camera was working but Im not sure why it isnt now. I cant do pics or video and lastnight when I was trying to Skype with my cousin in CA the video cam didnt work for me. I also have been getting two different errors...
1) The process com.google.process.gapps has stopped unexpectedly. Please try again.
-AND-
2) The application Talk (process com.google.android.talk) has stopped unexpectedly. Please try again.
I also had noticed that it seems to take a bit longer for the phone to boot in comparison to what it used to and especially when it was brand new and not yet rooted. I have a custom static image that says "HTC quietly rooted" and a WWII themed Android boot animation". When I reboot I get a black screen for about 30 seconds then the custom HTC image comes up for about 20-25 seconds then the custom animation plays THEN once that's done I'm booted into my phone.
Is there any kind of way to cut those times down for faster booting? Well I think I will have to keep messing with this and see what I can do...
just started getting this when i got to my market, press menu, my apps. anyone have this problem or know how to fix. i have tried clear cache, clear data, reinstall rom, everything i can think of. thanks for the help guys.
It might be Juice Defender blocking it.
i will give that a try, been using juice defender for awhile and this just started.
That started happening to me a few weeks ago. I was on Unnamed for a long while before it happened. Now it's happening on each rom I flash after a day or two. Not sure why, haven't really looked into it yet because it doesn't really annoy me. Yet. Just confirming that you are not the only one.
I also have tried different rims. Tried unnamed, icscrewed, and currently running turkbey v32 hellraised with DD 010212. All was good then it just started. Atleast I know its not just me.
Searching (not just i777 forums and XDA) will show you that this may be an Android/Google problem. Several possibilities:
1. you restored from Titanium backup - this breaks my market links every time.
2. you've flashed enough ROMs that your Google account is overloaded - it apparently doesn't "unlink" phone from apps from install version and after a certain point, it won't associate your phone to your apps any more. I suspect this is part of why restoring from TiBu breaks the links. And TiBu's "restore market links" does not seem to help. This has been reported to Google (not by me - more than a year's worth of people at this point) and they apparently don't care.
3. Just the general "market links disappeared" bug. It happens to people on stock, too.
You can create a new Gmail account and relink all the apps to that, but I don't like that as a solution. If anyone else knows more, please chime in!
thanks alacrify, hoping it can get resolved. without app showing i dont know when there are any updates.
Jamlx1 said:
thanks alacrify, hoping it can get resolved. without app showing i dont know when there are any updates.
Click to expand...
Click to collapse
I use AppBrain to keep an eye on things - it runs about a day late, but if you didn't have it at all, how would you know?
i will have to give that a try. guess no fix until google does something by the sounds then.
tried a bunch of things found in other threads on the site and nothing seems to work. anyone else have any suggestions
Apologies if this is obvious to anyone else, I searched around a bit and couldn't find an answer to it, so I'm hoping someone can help me. I've just rooted my EVO 3D for the first time, and I installed ViperRom on it. I then also ran the .zip that ViperRom had in the thread that removed Sense entirely (because I was underwhelmed with Sense when I had it and it just seemed to get in the way of my custom launcher and other stuff). I also installed a .zip that gave me back my Recent Apps list.
However, I seem to have somewhere along the way lost the Incoming Call screen while locked. If the phone is locked, I get a call and all I see is the basic lock screen. Unlocking the phone then takes me to the incoming call screen. Before I did all of this, if the phone started ringing while it was locked, I could still answer it from the screen I was on. Now I have to unlock the phone before I can even see who is calling. I know this seems like a minor issue, but twice so far I've tried to unlock the phone and managed to also decline the call in the process, since the slider is directly over the answer and decline buttons.
Can anyone clear up what has happened? Is the incoming call screen that happens when the phone is locked part of Sense, and by DeSensing I removed it? Can I get something similar to it back? I tried a demo of a custom incoming call screen app in the market, and it didn't change this behavior, it just gave me a custom incoming call screen once I had unlocked it.
Thanks for any help
J
Make sure you are on the last update of viperRom redline. maybe when you remove sense it removed the incoming call lock answer option. I have viper rom and giving not that problem
Sent from my PG86100 using XDA Premium App
Why not post this in vipers thread ??? He's a cool dev any kinda problems your having with his Rom I'm sure he will provide you with feedback and provide you with a solution. If not him, the thread is very active I'm sure one of the fellow xda members will help you as well. You will get a lot more feedback this way. Good luck.
#Root-Hack\Mod*Always_
""Shooter on Deck""
I tried to post in Viper's thread, and it told me I didn't have permission and had to post all questions in this area.
I am on the latest update, I literally installed everything directly from his thread.
Any chance someone could actually give me some help with this?
hey, ive been running viper for a long time now. I used to have this issue, it had to do with the kernel that he was using a few releases ago. Id say, make sure ur up to date on the rom. if u still have issues, try a stock kernel, or one of the other modified ones, i dont remember exactly which kernel was doing that, but it has been fixed since.
I'm fairly certain that the phone call on lock screen is part of sense. So, removing sense is probably the cause.
Even when I'm running non sense launcher, I leave sense active, just for this feature.
H
Sent from my ever-changing, ROM-loving EVO 3D (via Tapatalk)!
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...
First off here is my info:
Phone: AT&T Samsung Galaxy Note i717
ROM: Cyanogenmod 10 quincyatt nightly build 12/23 (in attempt to remedy my problem)
Using this guide http://forum.xda-developers.com/showthread.php?t=1958944&highlight=install+cyanogenmod in installed the 11//14 stable build initially without too much trouble.
I did find right away that I was unable to locate any camera application or any way to access it other than the lockscreen shortcut.
When I attempted to use the shortcut from the lockscreen it simply does nothing. It doesn't crash my phone, but it also does not open my camera.
I also tried installing a couple of camera applications from the play store and they start up, but the camera never activates.
This problem persisted even when I upgraded to todays nightly build 12/23, also so far I have noticed no new problems with this build as opposed to the 11/14 stable build.
I have searched for a solution for this problem in the forums, and perhaps I missed something, if that is the case then please direct me to the proper thread.
I tried posting this in the development section only to find out that I am unable to (I've been using this site for a while but never needed to register to ask a question).
If anyone has had this problem and/or knows how to fix it I would greatly appreciate your input.
I apologize if I have left anything out, if I have then let me know and I will get back to you as soon as I can.
Edit: I updated to the 12/24 nightly build today and it appears to have resolved the camera issue right away. If anyone else is having this problem then I hope this helps.
ill give $5 to the person that fixes this.
tatzelworm said:
First off here is my info:
Phone: AT&T Samsung Galaxy Note i717
ROM: Cyanogenmod 10 quincyatt nightly build 12/23 (in attempt to remedy my problem)
Using this guide http://forum.xda-developers.com/showthread.php?t=1958944&highlight=install+cyanogenmod in installed the 11//14 stable build initially without too much trouble.
I did find right away that I was unable to locate any camera application or any way to access it other than the lockscreen shortcut.
When I attempted to use the shortcut from the lockscreen it simply does nothing. It doesn't crash my phone, but it also does not open my camera.
I also tried installing a couple of camera applications from the play store and they start up, but the camera never activates.
This problem persisted even when I upgraded to todays nightly build 12/23, also so far I have noticed no new problems with this build as opposed to the 11/14 stable build.
I have searched for a solution for this problem in the forums, and perhaps I missed something, if that is the case then please direct me to the proper thread.
I tried posting this in the development section only to find out that I am unable to (I've been using this site for a while but never needed to register to ask a question).
If anyone has had this problem and/or knows how to fix it I would greatly appreciate your input.
I apologize if I have left anything out, if I have then let me know and I will get back to you as soon as I can.
Edit: I updated to the 12/24 nightly build today and it appears to have resolved the camera issue right away. If anyone else is having this problem then I hope this helps.
Click to expand...
Click to collapse
I have the same problem.
Fixed?
James Musacchio said:
I have the same problem.
Click to expand...
Click to collapse
Well as I stated in my edit, the 12/24 nightly appears to have fixed this issue so far as i can tell. Also updated to the 12/25 nightly and the camera still works. One bad thing about this is that I have experienced more than a few reboots, but my phone starts up so fast afterwards that its a small price to pay for having my camera back.
As always, make a backup before you flash the newest nightly but I haven't seen too many problems other than the occasional crash of a couple apps and the unfortunate reoccurring crash of Apollo which is annoying.
Let me know if this fixes your issue, if it does then I'm glad I could help.
Tried CM10 nightly myself tonight, and was quite happy with it, until ....
Random reboots ....5 in 3 hours.
Camera is good, but the menu button was iffy ....
It's getting better, but I'm gonna stay with my backup for a bit longer I think ....g
12/25 is a bit sketchy
gregsarg said:
Tried CM10 nightly myself tonight, and was quite happy with it, until ....
Random reboots ....5 in 3 hours.
Camera is good, but the menu button was iffy ....
It's getting better, but I'm gonna stay with my backup for a bit longer I think ....g
Click to expand...
Click to collapse
Yeah I decided to try the 12/25 build and didn't notice any improvements from the 12/24. Ironically about an hour after my last post my phone then went into a reboot loop that I couldn't stop until I removed my battery. I had to boot into cwm recovery and then reflash the 12/24 build. So far this is the most stable nightly that allows for the camera to work without causing too many issues besides one incident I had the first day I flashed it.
I recommend people stay away from 12/25 as it was extremely unstable in my experience. I may try the 12/26 build simply because I can, but I'll definitely keep the 12/24 on hand if that fails as well.