So I flashed this rom this week and I'm wondering if anyone else is having a problem with incoming calls? When I tried calling myself from another phone, it takes like 5 or 6 rings to get my SGSII to ring. Also the screen doesn't come on to show me who is calling. It will just vibrate... Is this a known bug?
Check the thread for fixes. You can also try flashing a different modem.
http://forum.xda-developers.com/showthread.php?t=1335745
Black screen fix
Go to settings
Programs
Call settings
Answer settings
Turn off enforce proximity sensors
(New build 2.11.26 seems that turning on works intead off)
The proximity sensors will still work after changing the setting
Reboot
I just installed the new modem on mine and the call volume seems much improved, but I had installed the fix from the dev forum a couple of hours ago and really didnt test it much...Big issue I have noticed is the screen doesnt wake on incoming txt messages - you experienced this?
Please use the Galnet forums for Support. Thread closed
Related
Can anyone show me how to enable in-call softkey function??? During call, my display is off and cannot use softkey, if there is an extension number, I have to wait until operator pick up or even cannot see which number is calling via call waiting function.
My ROM is original HTC ROM, don't ask me to load cooked ROM
Thank you
Did it ever work before?
This is the standard:
The display turns off once you put your device close to your ear.
Moving away again should turn back on the screen.
Now there are 2 possible issues:
1) The sensor is malfunctioning
2) The driver/system is malfunctioning
Since you don´t mention if the problem arose after you did something, one cannot offer you better help. Maybe you already tried a hard or a soft reset?
Thanks tictac,
I did upgrade firmware and problem temporary solved
Hey Mongoose,
First of all, great job with the ROM. Installed both Alpha 2 and 3 and you are making fantastic progress!
Thanks also to all of the Eris DEVs (and all DEVs for that matter) out there, my first little Android has held its own for a few years now
A quick comment:
The keyboard consistently opens ALMOST all the way up. For me, it's been stopping in the middle of the last row - still able to use - but not fully visible.
I was in the Messaging app and I did something that made it jump up to fully visible, but now (of course) I can't replicate what I did.
Thanks again, looking forward to future iterations!!
Wanted to comment on what I've tested and is WORKING for me:
touchscreen (not having any of the reported issues)
physical & soft buttons
data
calls (sending and receiving, no mic)
earpiece audio
sms (sending and receiving)
vibration / haptic feedback
proximity sensor
google sync
root access
NOT WORKING:
microphone
speaker audio
wifi (scans fine, can enter text to connect, says it's connecting, then authenticates, then loops on connecting/authenticating)
gps
camera
bluetooth
trackball
light sensor
orientation sensor
accelerometer (downloaded an app that has opengl 3D using the accelerometer and it rebooted the phone when I tried to view the 3D model)
magnetic field sensor
sdcard
mms (when I choose attach a picture it says "No external storage available.")
Also, installation was a piece of cake!
Wiped data and dalvik and then let it boot. Obviously no boot animation, but first the screen illuminated, then the soft buttons lit, then the haptic feedback shook, and then I was at the Start screen.
Again, fantastic job!!
Hello all,
Just to clarify (since some people in the Dev forums are still having issues that I have not had with Alpha 3) my Eris model number is PB00100.
I believe this is the 2nd model number of Eris from Verizon (not 100% sure about this)? I did have my original Eris replaced after I was losing calls like crazy.
Hope this helps!
Thanks for the detailed feedback! With another post you'll be allowed to post in the section. Look forward to seeing you over there
No problem! Last night I was following the dev thread in the Hero forum talking about the audio issues. Looks like jaybob413, Shelnutt2, shed, you, and a couple others are very close to working that issue out.
Once this build has a working mic, I will be using it more extensively.
Hey guys,
I know this thread already exists in this forum but has come to an end with no solution and since its kinda very important to sort this issue to be able to use my phone I thought ill start fresh for some input from the experts.
I have a Galaxy S2 I9100 rooted with a custom ROM(slim ICS 4.1 when the issue started) and it started randomly freezing when unlocking the screen and normal use .but since last week it wouldnt let me make or receive calls as the phone freezes and reboots 10-20 secs into the call..i updated to 4.2 with the hope of resolving this but tht didnt work..I have changed kernels and ROMS(resurrection, cm9 release build)..though the dialer did work for calls on resurrection ROM the proxomity sensor wouldnt work..
so i tried going back to stock sammy ICS (XXLPH) and then the dialer would work but again without the proximity sensor and the samsung tests also confirmed that the sensor wasnt registering...
am rooted now and back to slim 4.2(dont like the look of sammy) with siyah kernel 3.2.2...the dialer and proximity sensor don work..the rest of it is all fine..
Ive done all the wipes each time ive installed a new ROM...also done kernel wipes before installing Kernels..
I think its not a ROM/hardware problem but well it could be but hope to get it sorted through the normal techniques..I cant return my phone for repairs as it was in mint condition bot second hand in UK without warranty papers..
Any help would be highly appreciated..thanks
EDIT: It seems the proximity sensor is to blame for this problem as i found out through other posts..and also i can make and receive calls with the headset/headphones plugged (in which case i assume the phone doesnt try to activate the proximity sensor)..
For now i would like to know how to disable the proximity sensor on the phone..I have tried inserting the gsm.proximity.enable=false in the build.prop editor using the ROM Toolbox lite app n rebooted...but that din seem to work...is there any other way to do this??pls help
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
proximity sensor and screen brightness sensor
3dawg said:
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
Click to expand...
Click to collapse
I havent managed to find a solution as yet..it seems the proximity sensor and the screen brightness sensor(which are on the same PCB i think as per the unassembling video) have a hardware fault and might need repairing..
Some kernels i think maybe bypass using the proximity sensor if its not working..for now I am back to the SLIM 3.2 ICS rom..It doesnt switch off my screen on call and also no auto brightness adjustment but rest all works ok so am using it for now before i get the hardware repaired..
also the resurrection rom v 2.5.1 works fine in the same manner(havent tested many others..CM7 release build doesnt work)..or you can try that script in build.prop to disable the proximity sensor..
check how it goes..
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
proximity sensor and screen brightness sensor
3dawg said:
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
Click to expand...
Click to collapse
I tried checking with the testers for the Slim ROMS..regarding differences in kernel or anything for slim 3.2 and 4.2(3.2 works while 4.2 doesnt) but they couldn't tell me what was the exact problem or the differences that should affect in this case..I haven't tried a CM9 ROM yet but it could work..The kernel for the resurrection ROM is siyah kernel but when i tried that kernel with the slim 4.2 ROM that still didn't work for calls as the phone rebooted.
Have you managed to find a replacement cost for the proximity sensor? also does your screen brightness sensor work?
hello everyone
after much debugging of this problem, I think it has to do with battery saving option in the ROM/Kernel.
while having a voip call using sipdroid or magicjack, the proximity sensor turns off the screen and causes the sound to cut off completely. i think the mic still works because i was able to record a voice message while the screen is turned off by the sensor. this also means the wifi signal was still on.
sipdroid has the option to keep screen on during a call. this options works very well. the screen dims but does not turn off completely. on the other hand, magicjack does not have such an option.
why i think it is a battery saving issue is because while the phone is plugged in to wall or laptop, proximity sensor does turn off the screen but the audio is not cut off and everything works just fine.
anybody knows a fix or a workaround for this issue?
the problem is the same on cyanogenmod, MIUI, and Team DIRT. i think i had the same problem when i was using ICS before i switched to jellybean.
thanks
Have you tried the "keep proximity sensor on" setting in the call menu? make sure it's unchecked. Was just asking because you didn't mention it in your post.
Roxxas049 said:
Have you tried the "keep proximity sensor on" setting in the call menu? make sure it's unchecked. Was just asking because you didn't mention it in your post.
Click to expand...
Click to collapse
yes. it is unchecked. however, magicjack uses its own dialing app. sipdroid is fine because it has the option to disable proximity sensor.
but more importantly, is this a normal behavior? shouldn't i be able to turn off the screen via proximity sensor and still be able to chat? maybe graphics and audio processes are in conflict when the proximity sensor is activated.
hmnxyz said:
yes. it is unchecked. however, magicjack uses its own dialing app. sipdroid is fine because it has the option to disable proximity sensor.
but more importantly, is this a normal behavior? shouldn't i be able to turn off the screen via proximity sensor and still be able to chat? maybe graphics and audio processes are in conflict when the proximity sensor is activated.
Click to expand...
Click to collapse
i should say, this only happens when the phone is unplugged. i.e. running on battery. i dont know what it is trying to do. maybe save battery. how can i access such settings?
also, i use sipdroid with another voip number. magicjack has its own number and its own dialing app.
I am back to ICS and everything works fine. maybe this problem will go away when htc releases an official jeally bean rom.
hmnxyz said:
I am back to ICS and everything works fine. maybe this problem will go away when htc releases an official jeally bean rom.
Click to expand...
Click to collapse
actually, the only ICS rom that worked flawlessly is the stock rom. i ended up flashing a rooted stock rom. the problem is gone. finally.
Hi.
I was using my Atrix with CM7 MROM for long time.
Yesterday I switched to CM9 Olympus with new kernel by krystianp. It's great rom but...
I got two little problems:
1. when I plug my headset I don't have icon informing about this.
2. when headset is plugged it auto pick up calls. I found something like this "phone>menu key>call settings>Accessory settings for call" but I don't have this options in my dialer or anywhere else.
Can anyone help me with this? Icon is just a feature I liked but auto answering calls is a little disturbing for me. Especially when I don't know who is/was calling.
It is pretty clear you don't know what you're doing, or else you wouldn't flash an experimental ROM and then complain about a bunch of already very well known issues.
I suggest in the future you stick to GB ROMs and stay away from things you don't understand.
ravilov said:
It is pretty clear you don't know what you're doing, or else you wouldn't flash an experimental ROM and then complain about a bunch of already very well known issues.
I suggest in the future you stick to GB ROMs and stay away from things you don't understand.
Click to expand...
Click to collapse
I thought auto answer was normal function which is working and I didn't find anything about problems with it. So if it can be turn on should also be able too turn off...
I know that new kernel and roms are in development and that they have some bugs (proximity sensor, screen tearing, problem with some games) but one app which I needed runs only on 4+ Android.
So could answer me it is possible to turn off auto answering calls or it is bug which I miss reading threads about kernel/cm9/cm10?