Hi guys,
So I've just flashed NSCollab 1.0.35 and have a few troubles.
My first issue is that it's not finding my Orange service, therefore I cannot make calls, recieve, text etc.
The other is that com.android.phone, which is obviously the phone keeps stopping, recieving error messages every 20seconds.
Any ideas why please?
Re-flash?
I'd suggest re-flash, but make sure you do a data/factory reset, wipe cache and dalvik cache. If that dosent work, which it probly should. If not, flash another rom.
Sent from my Nexus S 4G
Related
Please bear with me i'm a noob.
I got my G2x with stock rom 2.2 Froyo and then rooted and flashed it without updating it to Gingerbread... I,ve tried CM7, Weapon, and now on Eaglesblood. None of them would let me use voice search without crashing..it will recognize what i say but as soon as i pick a selection from the list it force closes.. and some of the phone settings i try to access will also crash on me.
Is this because i've never updated my phone to GB before root/flash? Was i supposed to? I actually tried updating it with LG updater after root/flash (weapon at the time) and bricked it.. so im not going thru that again.
Thanks in advance!
Sent from my LG-P999 using XDA App
Well for voice search... Have you tried uninstalling it and reinstalling it?
As for the rest of the phone, maybe a cache and dalvik cache wipe?
I'm not trying to patronize you, but you have stated that you are new to this, so I'm going to ask the following.
Between flashing new ROMs, did you:
Perform factory reset.
Wipe the dalvik cache.
Wipe cache.
Format /system.
This is not something you need to do everytime (Like when upgrading from one version of CM7 to the next), but is recommended (Especially going from the broad range of ROMs you went through).
If you haven't done the following, I recommend doing that first, then coming back should you still need to troubleshoot. MANY issues can be fixed simply by starting with a clean slate.
Yes, i have factory reset, wiped cache n dalvik, and formatted system between flashes. Im going to try reinstalling it now.
Sent from my LG-P999 using XDA App
Voice search works on my 2.3.4 roms. They are not anything special, but lean, fast and stable.
Regular: http://forum.xda-developers.com/showthread.php?t=1325403
Colorized: http://forum.xda-developers.com/showthread.php?t=1334819
So... I just tried reinstalling voice search to no avail. I uninstalled it first and then booted into recovery to wipe cache and dalvik. Now, what I noticed was that when I select wipe dalvik cache, it gives error log "E:unknown volum for path [/sd-ext]." but when I press Yes to confirm the wipe, it says "dalvik cache wiped." I'm not sure if it's really wiping dalvik or not... Well, I installed voice search again and it still force closed.
jboxer said:
Voice search works on my 2.3.4 roms. They are not anything special, but lean, fast and stable.
Regular: http://forum.xda-developers.com/showthread.php?t=1325403
Colorized: http://forum.xda-developers.com/showthread.php?t=1334819
Click to expand...
Click to collapse
I will try out your rom!
People actually use voice search? I used to try but i always found it was faster to just type because it never knows what im saying.
dokjon said:
So... I just tried reinstalling voice search to no avail. I uninstalled it first and then booted into recovery to wipe cache and dalvik. Now, what I noticed was that when I select wipe dalvik cache, it gives error log "E:unknown volum for path [/sd-ext]." but when I press Yes to confirm the wipe, it says "dalvik cache wiped." I'm not sure if it's really wiping dalvik or not... Well, I installed voice search again and it still force closed.
Click to expand...
Click to collapse
The dalvik cache wipe is working, it will always say that unless you've wiped your SD card with CWM. Since there shouldn't be a need to, it's not a problem and shouldn't be a factor in your situation.
Joe333x said:
People actually use voice search? I used to try but i always found it was faster to just type because it never knows what im saying.
Click to expand...
Click to collapse
I would like to use it when I'm driving around.. and it's annoying to knowingly keep a feature of phone that won't work
dokjon said:
I would like to use it when I'm driving around.. and it's annoying to knowingly keep a feature of phone that won't work
Click to expand...
Click to collapse
It actually works amazingly well now. It is almost eery how accurate it is.
My Milestone XT720 restarts many times. When i'm talking, when phone is in standby. It is restarting after i update it to FjFlacon's Cm7.2.
I love Cm7.2 and don't want to remove it. Please help to fix that reboots.
There is not enough information to figure out the issue.
You may need to at least provide some error/warning or logcat for some hints. Otherwise, we may not be able to address the issue, as not every people with that Rom face this issue.
Maybe is a bad flash... or try to do a factory reset... or just flash again your rom
Sent from my XT720 using XDA App
I have seen the problem before when I didn't do wipe data/factory reset after applying the update. Just yesterday I flashed S'pore sbf, and applied CM7.2 as update, and did wipe everything (data, cache, dalvik), and all is well. So try all wipes possible from openrecovery.
Thanks, guys. Will try to wipe everything before i flash again my phone
Someone help me please. I am running on Cyanogen 9 P6200 by Aorth and I can receive message but i can't sending message.
first time anybody complained about sms.
maybe you should re flash the rom and be sure to format cache and restore to factory settings
I have tried reflash and wipe cache factory reset but still the same. if I send message GSM signal disappear
Hey guys i updated my Nexus S (Crespo) to KitKat 4.4 now i cannot make or receive calls my modem is I9020XXXKJ1 do i need to update my modem or is there any other fix seems as if i reboot phone make a call quickly it works then after that when i make a call its silent at both ends, txts work and also the wifi works just the calling, Any help would be muchly appreciated,
Thanks,
Try to wipe cache, dalvik cache and factory reset your phone, it might be a dirty flash otherwise try installing another ROM
Sent from my Nexus S using xda premium
Randomly started working
superng888 said:
Try to wipe cache, dalvik cache and factory reset your phone, it might be a dirty flash otherwise try installing another ROM
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Thanks for the reply dude i had done this many times also tryed CM11 rom but last night i reset my phone then it randomly started working now its mint as and is still working even after more resets, anyway can close post now lol shes fixed and running better than ever!:laugh:
Hi everybody,
2 day ago, I got an error message on my Opo: "com.android.phone has stopped" and ever since it has been popping up every minute or so, or sometimes every 10 seconds when I'm on my phone. The most annoying thing is that sometimes when I get that error message I also loose my network, so I can't make any phonecalls/use my 3G.
I was looking at the Crash Report and I saw this message:
"[crash] com.android.mms.service threw java.lang.NullPointerException"
I remember the first time this error happened was when I was writing a message and suddenly the interface was stuttering and everything was going very slow. Rebooted and then I started getting those errors
I followed some instructions found here, on Opo forums and on android central:
1) go to apps and clear the cache/data from phone, sim-toolkit, messaging and messaging service and reboot
2) perform a soft reset (via the phone)
3) perform a hard reset (factory reset via the recovery menu)
4) install custom recovery, enable root and reflash the rom
None of these solved the problem. But I also don't have the feeling that a hard reset
Moreover, after a reset, I still see folders from apps I had before the reset. Including pictures in my picture folder that I had downloaded prior to the factory reset. This doesn't seem like a factory reset to me, is there any way to wipe everything clean?
*edit*
This is the log of the error report that I get:
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
*edit2*
When I had the error my settings were:
ROM: Cyanogen 12.0-YNG1TAS0YL
Kernel: 3.4.67-cyanogenmod-g1cbb9b0 build04cyanogenmod #1
No custom recovery
I've trying to fix the error, installing custom recovery, enabling root mode and reflashing the official cyanongen 12 rom. Still the problem persisted.
ROM: Cyanogen 12.0-YNG1TAS0YL
Kernel: 3.4.67-cyanogenmod-g1cbb9b0 build04cyanogenmod #1
Twrp recovery
ElGargamel said:
Hi everybody,
2 day ago, I got an error message on my Opo: "com.android.phone has stopped" and ever since it has been popping up every minute or so, or sometimes........
Click to expand...
Click to collapse
You forgot to provide details (ROM, Kernel, recovery, mods, etc.)
java.lang.NullPointerException usually means that the code calls for some value and it is not available.
davebugyi said:
You forgot to provide details (ROM, Kernel, recovery, mods, etc.)
java.lang.NullPointerException usually means that the code calls for some value and it is not available.
Click to expand...
Click to collapse
Sorry, I added details in the initial post under "edit2". In short, I started having the error with the Stock rom/recovery. Didn't fiddle with anything. Out of frustration I decided to install twrp, enable root and reflash the rom. Didn't work, problem happened again as soon as I booted up my phone. I feel it has to do something with the sim-toolkit? As soon as it access the network it starting to nuke the error, then loses network, then regains network, especially when I'm trying to write a message. In airplane mode it doesn't happen.
ElGargamel said:
Sorry, I added details in the initial post under "edit2". In short, I started having the error with the Stock rom/recovery. Didn't fiddle with anything. Out of frustration I decided to install twrp, enable root and reflash the rom. Didn't work, problem happened again as soon as I booted up my phone. I feel it has to do something with the sim-toolkit? As soon as it access the network it starting to nuke the error, then loses network, then regains network, especially when I'm trying to write a message. In airplane mode it doesn't happen.
Click to expand...
Click to collapse
It can be that or modem issue or something got corrupted on the /data partition.
davebugyi said:
It can be that or modem issue or something got corrupted on the /data partition.
Click to expand...
Click to collapse
Any way I can fix this from within twrp? How do I figure out what is exactly corrupted?
ElGargamel said:
Any way I can fix this from within twrp? How do I figure out what is exactly corrupted?
Click to expand...
Click to collapse
Trial and error. The easiest way is to wipe your device clean (system, cache, dalvik and data - storage not needed) and flash the ROM again. Also try to flash the latest available.
davebugyi said:
Trial and error. The easiest way is to wipe your device clean (system, cache, dalvik and data - storage not needed) and flash the ROM again. Also try to flash the latest available. [/URL]
Click to expand...
Click to collapse
Didn't work. Still get nuked by the error. I decided to flash OxygenOS (after system, cache, dalvik and data wipe). Now I don't have the error anymore, luckily.
But I still have problems with texting. I can receive texts from friends, but not from my girlfriend who has an iPhone. She can receive my texts and my MMS, but I don't receive anything from her. The problem is partly solved, but not completely. I feel it's still somewhat related to the original problem.
ElGargamel said:
Didn't work. Still get nuked by the error. I decided to flash OxygenOS (after system, cache, dalvik and data wipe). Now I don't have the error anymore, luckily.
But I still have problems with texting. I can receive texts from friends, but not from my girlfriend who has an iPhone. She can receive my texts and my MMS, but I don't receive anything from her. The problem is partly solved, but not completely. I feel it's still somewhat related to the original problem.
Click to expand...
Click to collapse
Well, then it must hardware related or problem with your carrier.
Flash a custom rom
Sent from my A0001 using Tapatalk