I have asked a few times on the forum if this could be related to the baseband of my device. Basically what happens is in call, he proximity sensor seems to cause the touchscreen to go haywire. I receive what amounts to phantom button presses. Basically voiding the functionality of the proximity sensor to begin with, the calls get put on hold, muted, dropped or whatever. A new symptom has now appeared, the dreaded black screen bug. When a call gets dropped, screen goes black and nothing but a battery pull solves this. Contacts are suddenly missing and I need to resync to get them back
I have tried many different roms, every single kernel. The only solution I personally can think of, is disabling the proximity sensor altogether. Can anyone tell me which line in the build.prop would disable this?
Its my everyday phone, so this is rather urgent, any help would be appreciated
You need to add either of these 2 lines (not sure which, or if it matters):
gsm.proximity.enable=false
gsm.proximity.enable=0
Oh, and apparently MIUI ROMs have that option in the settings.
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Left4DeadMW said:
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Click to expand...
Click to collapse
I usually mount and format /system when i do flash a new rom. Thanks for your reply, but as I stated before, this happens on every rom I have flashed before
Related
I recently flashed alien 4 with the theme and all was good for a few hours but then i suddenly couldnt answer calls. when i get a call the phone vibrates nonstop without a ringtone but i cant answer or decline it and com.android.phone eventually force closes.
i reflashed the rom with no luck, fixed permissions flashed the old radio.
I have now flashed the cwm backup of my stock unlocked rom and the problem still persists.
pls help
ps I have an unlocked att atrix
anyone? ... Ive had to resort to switching to my old bb, feel like I jumped back a generation techwise
Do a full fastboot wipe. People often flash things without doing a proper wipe then are confused why things are broken. This means /system, /data, /boot, /cache, /preinstall, /webtop. All wiped. Then go into cwm and for good measure do a factory reset and wipe dalvik. Then flash alien, reboot, let it build system files, then reboot and flash the theme . Bam. Done.
Sent from my MB860 using Tapatalk
did another wipe according to the above instructions and seems to be working for now. Thanks
I have my phone rooted and installed the FTS V2.4 ROM onto my phone, followed the install instructions. On startup I get a force close error, The application Motorola services (process.com.motorola.service.) has stopped unexpectedly. Please try again. I then get the process com.motorola.home.other has stopped. Everything else works fine. I do get another error when trying to place an email and date & time widget. Is there a fix for this? It doesn't stop the phone from functioning just would like to fix it.
That is usually caused by a bad flash or incomplete wipe. Go back into the recovery wipe everything a couple of times reflash the rom and that should take care of it. I have had that happen on multiple phones with multiple roms.
arsmithsr said:
That is usually caused by a bad flash or incomplete wipe. Go back into the recovery wipe everything a couple of times reflash the rom and that should take care of it. I have had that happen on multiple phones with multiple roms.
Click to expand...
Click to collapse
So after booting into recovery I do wipe data/factory reset a couple times? Anything else I should wipe a couple times? And then do install zip from sdcard? Also, my friend said after it installs I should leave it for 10-20 minutes, is this true?
you can manually wipe the cache and dalvic cache 2 or 3 times each then factory reset a couple times then flash your rom again. What has happened is you have ssome files from the old rom and some files from the ne rom this causes the issues you are seeing. You could probably just factory reset a couple of times Cauculin? has made a special wipe becuase of these issues sometimes it doesn't format right that's why you need to do the multiple wipes to be sure it took.
Similar problem on virgin Razr
I get this each time I reboot " process com.motorola.home.other has stopped unexpectedly, Please try again. Force close. FC is my only option.
It has appeared a few other times but with no regularity. Like the OP I still have full function and use but I'm sure it is a sign of possibly other problems brewing.
From what I have read it looks as if a complete reset might be the only cure but I'm hoping to find another solution.
Q: Is "com.motorola.home.other" actually a file, or does it refer to a file that could possibly be copied back over from a backup if it is corrupt.
While writing this post this problem occurred again after closing an app, which has me even more concerned.
Many thanks
X/BillyD..
Im unable to make voice calls through the Phone app. It will connect, then make no noise (ie no ringing). Same if i receive a call, i hit accept and i hear nothing, nor can the person calling me hear anything. I can use the voice search/navigation, and i can use other voice apps (ie voxer) just fine. SMS works, as does 3g, and im not getting any error messages.
Phone is GT-I9100, Kernel is Siyah 3.1rc6, running D4rom (ICS). I've tried 3 seperate roms (Omega v11, D4, and Slim (all ICS)) all having the same issues. Im assuming this is an issues with ICS (or more likely something i didnt update prior to switching) but ive spent about 6 hours now trying to find out what is causing it.
I realize downgrading would solve this, but i'd rather find out what my issue is and fix it. any ideas?
Flash again, but this time full wipe, it happened to me once on d4 rom, this should do it
Edit: have you tried wanamlite with siyahkernel? If you follow the below, you shouldn't have a problem.
A. Ensure FULL wipe;
1. System
2. Cache
3. Data
4. Dalvik cache
B. Immediately Flash ROM
C. Let boot and initial setup
D. Check if phone dialer and choice calls are ok?
E. If ok, Restore only user apps and data. NO System crap. Recheck
F. Reboot and setup accounts. Recheck
Sent from my GT-I9100 using xda premium
Still no luck. Flashed 3 times, once with D4 again, twice with wanalite. did factory reset, manually wiped /data, /system, /cache, and Dalvik cache. after doing initial run (i didn't set up my gmail account, since i need wifi for that (data cap is annoying)) i tried to make a call, and it still wont ring. At first it would end the call after 15's or so. after restarting it it would go longer, usually until i end it. SMS still works, as does 3g data.
I got an error this time setting up the clock, but it was only visible for about 2s. It was something to do with setting the time, if i can get it again ill try to write it down.
Also, when wiping the Dalvik cache i get this :
E:unknown voluem for path [/sd-ext]
Dalvik cache wiped
any other advice?
I finally downgraded to GB rom (unnamed). Phone worked fine, as well as everything else. Ty for your help though, It was greatly appreciated.
Also, i noticed prior to updating it that the search and back buttons didnt do anything. IDK if this is normal or not, i dont use those buttons much.
Very strange after fresh full wipe and flash, and test without setup of the different ROMs
Edit: Have you tried flashing some of the alternative ICS modems found in the modem thread? Maybe yours doesn't like the modem packaged with the ROM.
If that doesn't work, what if you flash one of Intratech official or Frankenstein firmware. You'll need to re-root after and flash cwm again.
That error with the Dalvik is ok. Forget why, answer will be found with some searching though. If you look carefully, it would have said "Dalvik cache wiped"
Sent from my GT-I9100 using xda premium
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app
I would post this in the development thread but I have too little of a post count.
Let me preface by saying I love this FW and wholly enjoy it except for one fatal flaw. If my phone is shut off and I attempt to reboot the Samsung logo appears as usual then nothing more, just a black screen. However if I go in to recovery and wipe user data/factory reset it will boot just fine. I attempted to one by one try to bypass this problem by wiping; cache, dalvic cache, battery stats, and fixing permissions all of which did not work.
Any ideas on how I could use this fw without having to wipe my phone every time I want to switch batteries?
xypex982 said:
I would post this in the development thread but I have too little of a post count.
Let me preface by saying I love this FW and wholly enjoy it except for one fatal flaw. If my phone is shut off and I attempt to reboot the Samsung logo appears as usual then nothing more, just a black screen. However if I go in to recovery and wipe user data/factory reset it will boot just fine. I attempted to one by one try to bypass this problem by wiping; cache, dalvic cache, battery stats, and fixing permissions all of which did not work.
Any ideas on how I could use this fw without having to wipe my phone every time I want to switch batteries?
Click to expand...
Click to collapse
You must be installing an incompatible APP when it boots. . try and figure out which one it is.
xypex982 said:
I would post this in the development thread but I have too little of a post count.
Let me preface by saying I love this FW and wholly enjoy it except for one fatal flaw. If my phone is shut off and I attempt to reboot the Samsung logo appears as usual then nothing more, just a black screen. However if I go in to recovery and wipe user data/factory reset it will boot just fine. I attempted to one by one try to bypass this problem by wiping; cache, dalvic cache, battery stats, and fixing permissions all of which did not work.
Any ideas on how I could use this fw without having to wipe my phone every time I want to switch batteries?
Click to expand...
Click to collapse
I try the most simple solutions first................... redownload ROM and try that one. I just installed this last night. no issue so far.
do you remember which dl you used last time............BLOWNCO or DEVHOST ? try the other
whats FW ?
captemo said:
I try the most simple solutions first................... redownload ROM and try that one. I just installed this last night. no issue so far.
do you remember which dl you used last time............BLOWNCO or DEVHOST ? try the other
whats FW ?
Click to expand...
Click to collapse
FW=Firmware
I want to say I used devhost, however I will try to re-flash with the fw from both sources to try and fix it in that fashion.
An app that isn't compatible...sounds like finding a needle in a haystack, maybe I could just uninstall every app I have currently and try a reboot to see what happens? If that works I could install reinstall my apps two at a time until it will no longer boot?
Dunno if it makes a difference but I have plenty of storage space on my phones internal and external SD card memory. I just have heard that lack of space (sub 300mb) can cause all sorts of funky issues.
Thanks I appreciate it guys, I can't try reflashing for a day because I am at my girlfriend's and her macbook pro will NOT hook up to either of our Samsung phones no matter how much we play around with settings and drivers....ugh think different my butt.
xypex982 said:
FW=Firmware
I want to say I used devhost, however I will try to re-flash with the fw from both sources to try and fix it in that fashion.
An app that isn't compatible...sounds like finding a needle in a haystack, maybe I could just uninstall every app I have currently and try a reboot to see what happens? If that works I could install reinstall my apps two at a time until it will no longer boot?
Dunno if it makes a difference but I have plenty of storage space on my phones internal and external SD card memory. I just have heard that lack of space (sub 300mb) can cause all sorts of funky issues.
Thanks I appreciate it guys, I can't try reflashing for a day because I am at my girlfriend's and her macbook pro will NOT hook up to either of our Samsung phones no matter how much we play around with settings and drivers....ugh think different my butt.
Click to expand...
Click to collapse
FIRMWARE...................DUH
knew it was probably something simple.
just used to people saying ROM
even the developer states he flashes his ROM twice (at least) cause he can get 2 different reactions on his phone.