Database Users

no vibrate with JL1

So I flashed the new JL1 firmware last night to try it out and thus far its been a pretty solid firmware. The only problems I have found so far is that the vibration function does not work at all. and the market is missing apps like Paypal and a few others that I usually use. you can set it to always vibrate and leave haptic feedback on but when you go to adjust the vibration nothing happens as far as the phone vibrating. I just missed 2 calls and a text message because the phone didnt vibrate. Anyone have any ideas on how to fix this problem and while the ideas are flowing, how to root JL1. I miss having root so I can run my usual programs.

the vibration is confirmed as not working in JL1, no workaround it is a bug in a leaked firmware, not official. Go back to what you were running previously.

I know nothing about the vibration issue / how to fix it. Nothing in JL1 worth staying on it now, nandroid to what you were on before.
However, the Market issue is fairly common per these leaked official TMO roms. The fingerprint has changed so the market doesn't yet recognize it. Often downloading a few things, paid / purchased and then rebooting a few times makes them return. However, if it doesn't not you can optionally change the fingerprint back to one that worked and repeat the above.
I imagine your tried using RyanZA's root app and that failed. Have you also tried SuperOneClick yet?

tpreludesh said:
So I flashed the new JL1 firmware last night to try it out and thus far its been a pretty solid firmware. The only problems I have found so far is that the vibration function does not work at all. and the market is missing apps like Paypal and a few others that I usually use. you can set it to always vibrate and leave haptic feedback on but when you go to adjust the vibration nothing happens as far as the phone vibrating. I just missed 2 calls and a text message because the phone didnt vibrate. Anyone have any ideas on how to fix this problem and while the ideas are flowing, how to root JL1. I miss having root so I can run my usual programs.
Click to expand...
Click to collapse
dont know about receiving calls and sms. but when i adjust vibration, everything works fine.

I ended up going back to jk6 because i need the vibration function o work. as far as the market fix, i tried the whole download a few of my purchased and regular apps and rebooting a few times but that still did not fix anything. Call wise and reception wise, JL1 was far better for me in my apartment, but the other problems made it too much of a PITA. I guess I'l be rockin jk6 until someone can fix JL1 or until the nexus s comes out. either way, im ok with it.

kolyan said:
dont know about receiving calls and sms. but when i adjust vibration, everything works fine.
Click to expand...
Click to collapse
So you got vibration to work with jl1??
Sent from my SGH-T959 using XDA App

I doubt the vibration issue would be too difficult to fix, it's just that no one cares enough to do it I think lol. Really, JL1 seems so similar to JK6, I'd say just run the JL1 modem on JK6 (or just run JK6 if you think the modem is a placebo) and call it a day.

compuguy1088 said:
So you got vibration to work with jl1??
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
didnt have to fix anything. it was working from the beginning. just tested all vibrations and it works in sms, email, and in settings, probably in calls too then.

Slider unlock sometimes doesn't work with incoming call

Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?

Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.

I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?

question... are the phones plugged in to a wall charger when this happens?

Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).

DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place

ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).

cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there

My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers

I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.

Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.

problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel

Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App

swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago

I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?

[BUG] Other person can't her me mid-call, mic gets muted

Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.

Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300

Have you tried to DISable the noise canceling feature?

No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app

I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?

BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app

just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?

Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).

the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?

Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.

Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:

the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course

change modem

Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?

avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas

I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...

I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.

I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app

Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium

I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.

Help My Nexus 4 is a mute...literally

I got a nexus 4 but I noticed that its a mute...
No sound.. Even at the highest volume.
But the strange thing is when I unlocked it...and after a reset.. The sounds works for a few minutes and then the phone goes mute again.. I locked it again and the sounds returns again for a few minutes...
It not a speaker problem defiantly...
Any suggestions???
Sent from my Nexus 4 using xda premium

My Dad had a similar problem on his iPhone 2G once and it was to do with the headphone jack. Try plugging something into the headphone jack then playing some music before taking the headphones out then playing again. I know it seems weird but it worked for my Dad and it won't take long so it's worth a try. It's not very likely to work though because his iPhone was a solid 3 years old at the time and very beaten up, you probably haven't done similar damage to your phone in such a relatively short time period.

Nigeldg said:
My Dad had a similar problem on his iPhone 2G once and it was to do with the headphone jack. Try plugging something into the headphone jack then playing some music before taking the headphones out then playing again. I know it seems weird but it worked for my Dad and it won't take long so it's worth a try. It's not very likely to work though because his iPhone was a solid 3 years old at the time and very beaten up, you probably haven't done similar damage to your phone in such a relatively short time period.
Click to expand...
Click to collapse
thanks for your suggestion...
tired but to no avail... i noticed this is most likely a software issue... as after a reboot ..sounds works perfectly for a period of time (30 sec.... 10 mins) then after that ... sounds goes off (playing about... going to settings etc...)... and the only possibility to fix this is to reboot..
this happens on stock 4.2, 4.2.2, Cm10.1 RC1, Xylon, etc..
can't seems to pinpoint the fault...it seems to go to mute... but the volume rocker still shows volume is on... and move it up and down does not solves it..
when plug a headphone into the unit, is it supposed to show a head phone is plugged in ?? i don't seems to get that..

khnglh said:
thanks for your suggestion...
tired but to no avail... i noticed this is most likely a software issue... as after a reboot ..sounds works perfectly for a period of time (30 sec.... 10 mins) then after that ... sounds goes off (playing about... going to settings etc...)... and the only possibility to fix this is to reboot..
this happens on stock 4.2, 4.2.2, Cm10.1 RC1, Xylon, etc..
can't seems to pinpoint the fault...it seems to go to mute... but the volume rocker still shows volume is on... and move it up and down does not solves it..
when plug a headphone into the unit, is it supposed to show a head phone is plugged in ?? i don't seems to get that..
Click to expand...
Click to collapse
I would reflash a factory image in fastboot, if that doesn`t solve the issue it may be a hardware issue that requires repair (relock the bootloader in that case).
BTW do you have sound with music, youtube etc?

I had a similar problem when i flashed the Sony sound pack ported from xperia z. Every single sound vanished from the device, even speaker and mic when making a call! Restored a backup and it has since worked fine!
Sent from my Nexus 4 running latest jellybam with motley kernel! using xda app-developers app

gee2012 said:
I would reflash a factory image in fastboot, if that doesn`t solve the issue it may be a hardware issue that requires repair (relock the bootloader in that case).
BTW do you have sound with music, youtube etc?
Click to expand...
Click to collapse
it definitely seems like a hardware issue.. main be the main board..
no sound what so ever from any application.. however after a reboot.. the sounds works for a while then it goes silents.... (factory rom 4.2.2)
never had any problem with any nexus phones seems Nexus One... but think my luck ran out on me...

davecousins said:
I had a similar problem when i flashed the Sony sound pack ported from xperia z. Every single sound vanished from the device, even speaker and mic when making a call! Restored a backup and it has since worked fine!
Sent from my Nexus 4 running latest jellybam with motley kernel! using xda app-developers app
Click to expand...
Click to collapse
thanks for your suggestions.. no sound pack installed.. (full factory rom 4.2.2)
i did tired installing Beats audio zip... thinking it may overwrite some sound files and hopefully fix the problem... but no luck

If you can, flash back to stock and RMA it. This isn't a common or normal issue and you probably won't be able to fix it yourself that easily.

khnglh said:
thanks for your suggestions.. no sound pack installed.. (full factory rom 4.2.2)
i did tired installing Beats audio zip... thinking it may overwrite some sound files and hopefully fix the problem... but no luck
Click to expand...
Click to collapse
When you fully press volume down when the issue has occurred, does the phone then goes into vibration mode?
Sent from my Nexus 4 using xda premium

Yes it does... It goes down to vibrate then silent mode.. And when I press up... Still no sound...
Sigh... I will give it another day or two before I change the phone
Sent from my LG-P880 using xda premium

NO VIBRATION for incoming calls. need help plz :(

So I'm on a ported s6 rom (aurora) for note 3 (n900w8).
I've been noticing this problem, where a phone call would come, but no vibration with it even though the mode was set as vibration mode.
I have missed many phone calls because of this.
At first I thought I simply failed to notice the vibration, but yesterday I witnessed it not vibrating during the incoming phone call. Screen comes on, incoming call screen pops, but no vibration.
This problem persisted ever since lollipop (I think). Had the same problem in the previous roms (other note 3 lollipop roms).
Oh and it happens when the phone is in idle. If a phone call comes while i'm using the phone, it vibrates just fine.
So I was suspecting it might be blocked wakelock or alarm issue. But then again, the only app i'm using for that purpose is Servicely (by chainfire), and I only have a couple apps checked (ie. facebook, google play services, keep, mega, supersu...etc).
TW 5.0.2.
No xposed framework installed.
Rooted/deodexed.
Anyone experiencing the same problem? Any fixes? Help plz. This is starting to bother me a lot...

anybody at all ?

Well as long as the vibrating motor is okay I don't think there is much to think. You are on a ported ROM, so some bugs are to be expected. If you were experiencing the same on an official 5.0 ROM that would be bothering, but as its not you should ask about this in that ROM's thread.

Do you have enabled the power saving option? If yes, try to deactivate it and see if it still not working.

Flash an official rom.
'Ported' Roms are usually very poorly done, as they are meant for other devices.
Sent from my SM-N9005 using Tapatalk

ithehappy said:
Well as long as the vibrating motor is okay I don't think there is much to think. You are on a ported ROM, so some bugs are to be expected. If you were experiencing the same on an official 5.0 ROM that would be bothering, but as its not you should ask about this in that ROM's thread.
Click to expand...
Click to collapse
celderic said:
Flash an official rom.
'Ported' Roms are usually very poorly done, as they are meant for other devices.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
hm... The last rom I was on was Note 3 LP 5.0 rom built on official note 3 firmware (Vision X from Tmobile Note 3 xda forum), and I still saw that happening.
so yea it wasnt a problem of being ported rom or not...
and I dont want to go back to stock odex rom..
Thx for the replies anyways guys
IEAL said:
Do you have enabled the power saving option? If yes, try to deactivate it and see if it still not working.
Click to expand...
Click to collapse
and no I dont have them on