yashsingh1/xdaforums huggingface dataset:
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] akshay shah:
Is it possible to install cynogenmode10 or 9 to galaxy y.

Actually lower end phone like samsung galaxy mini/pop has this cynogenmode 10 update.

So should i install this cynogenmode 10 to my galaxy y phone?:confused:
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] -CALIBAN666-:
Use searchbutton.:mad:

GREETZ WITH TAPATALKED BEATZ!!!
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Yash98:
^that

Bro, Android requires different drivers for different devices so CM is not universal.

A CM7 is in progress and after its completion we'll most probably see CM10.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] 74M3NUMB3RS:
No.... Mini already got its drivers...and so are others..

AMALAYER? SHES A LAYER!

NO..AMALADYGUARD...PWNED!
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] akshay shah:
I have searched buddy.....

But i cant get the perfect info about the cynogen mode 9/10 for samsung galaxy y.....

:confused:
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] humaid.locastic:
Lol we havnt got a 100% stable cm7 and u r asking for cm10
[Nexus 4 Q&A, Help & Troubleshooting] evaradar:
Hey folks,

After updating to 4.2.1 on my Nexus 4, I've been noticing lately the following issues:

1) If I am on a call and I want to do something else, I cannot do anything at all even when I press the power button so I can see the screen.

2) If someone calls me, sometimes the screen won't be on and I can't see who's calling and can't answer. Or it'll show up for a few seconds and boom, same thing. Same issue when ending a call.

3) If I am using my phone and after 15 seconds the screen turns off or sleeps, etc and I press the power button to unlock, I can't. All I see is a light colored black blank screen and then when I press the power button again I can finally see the lock screen widgets/lock screen.

So is this a software issue? Or am I the only one? Hardware issue? This is happening after the 4.2.1 update and not prior to it.

Cheers.
[Nexus 4 Q&A, Help & Troubleshooting] DazzaL:
I can confirm point 3. only happening since the 4.2.1 update. Screen is black for a few seconds before the lock screen shows up
[Nexus 4 Q&A, Help & Troubleshooting] evaradar:
Hmm. So it is not me then. Heh. Perhaps Google needs to fix this in their 4.2.2 update or whatever heh.
[Nexus 4 Q&A, Help & Troubleshooting] ronnyzilker:
I'm having this issue as well. I'm even thinking about rooting my phone just to see if a custom rom will fix this.
[Nexus 4 Q&A, Help & Troubleshooting] brooklynchildxbc:
i noticed the black screen too i'm going back to 4.2 since i didn't have the December problem
[Nexus 4 Q&A, Help & Troubleshooting] Roxy:
My phone was updated to 4.2.1 earlier this morning and I don't have any of those issues.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] DazzaL:
I had point 3 only but that's cleared itself now (I was rooted before updating and after hitting restore root in ota root keeper the problem went away). I've tried a few test calls but don't have issue 1 and 2
[Nexus 4 Q&A, Help & Troubleshooting] Armon2:
Updated 20 minutes ago and now I am repeatedly getting 3. Screen does not reliably come on when pressing the power button. Have not tried calls
[Nexus 4 Q&A, Help & Troubleshooting] n4user:
I'm curious to know how many of you with this issues are using those plastic screen protectors?

edited: After doing some tests i figured out that my screen protector is the cause. the screen protector is covering the sensor located on the top left side of the phone which causes android to deactivate the screen to save battery like it dose during calls when the phone is held against your ears.
[Nexus 4 Q&A, Help & Troubleshooting] evaradar:
I had root before. Then I got the update, but used Voodoo OTA rootkeeper to preserve root before. After I updated, I still had root. Should I hit restore root still even though I have root enabled?

You mean the one that came with the phone or aftermarket ones? If the one that came with the phone, I have not had the problem prior to 4.2.1. So I highly doubt that's the case here, or rather the issue heh.
[Nexus 4 Q&A, Help & Troubleshooting] Armon2:
I can confirm that that issues seem to have gone away after rerooting the device.
[Nexus 4 Q&A, Help & Troubleshooting] evaradar:
Hmm... So just uninstall SuperSU and reinstall SuperSU?

Edit: I tried using to restore root using Voodoo's OTA Rootkeeper and so far the problem as per #3 on my list (per main post) seems to have subsided.
[Nexus 4 Q&A, Help & Troubleshooting] VoiD_Dweller:
I got one for my Mom and right out of the box #1 and #2 were happening after initial setup. Doing a restore to factory seemed to fix it, we didn't do the update on either of our phones
[Nexus 4 Q&A, Help & Troubleshooting] LongDage:
I had the same problem, my nexus 4 was still on 4.2

I had installed an aftermarket screen protector. i removed it and the problem went away.
[Nexus 4 Q&A, Help & Troubleshooting] mastewman:
It does sound like that you have a screen protector that is covering your proximity sensor.
[Nexus 4 Q&A, Help & Troubleshooting] bton:
Yes. I can confirm the problem is with the screen protector. I had problem 1 and 2 before removing the screen protector.
[Nexus 4 Q&A, Help & Troubleshooting] silentsnow31802:
+1 on the screen protector. I had the #1 and #2 issue. My screen would immediately black out during a call and not come back on unless the person on the other end hung up first (was terrible for leaving voicemail lol). I had an extreme guard protector on and it was effecting the proximity sensor. Glad I searched for this issue because it was starting to tick me off! I guess its time to go back to CM10 since that was not my issue lol.
[Nexus 4 Q&A, Help & Troubleshooting] DJGibbon:
-1 for screen protector here, unless there's a super-secret one I can't peel off :(

My proximity sensor is presumably bust, as Elixir 2 and Android Sensor Box both show it reporting "near" and 0.0cm respectively. Anyone else have these issues?
[Nexus 4 Q&A, Help & Troubleshooting] daweeze02:
Same issue here even though I do have a skin on it. But I''ve had a skin on my last 5 android phones and its never triggered the sensor. I'm going to run that sensor box app after I'm off this call and see what it says.

---------- Post added at 08:26 PM ---------- Previous post was at 08:19 PM ----------

I'm emailing bestskinsever about this, mine is showing 0 as well and my other droid for work shows 100.

---------- Post added at 08:31 PM ---------- Previous post was at 08:26 PM ----------

Here is my email to bestskinsever

So I have orderd from you maybe a dozen or so times and love your products/pricing. But I have a concern with the skin for the nexus 4. Since I have put it on it is throwing mu prox sensor off and making it report a 0. My work phone with no skin is showing 100 in Android Sensor Box. So with the nexus every call I make the screen stays black. Maybe the nexus 4's sensor is more picky about skins? Here are some others have the same issue. Let me know what you come up with, because this may be an issue on all the nexus 4's.

PS There is not one spec of dust under my skin near the sensor. I applied the skin with the shower steaming up so no dust would fall on the screen.

http://xdaforums.com/showthread.php?p=35019284#post35019284

http://forums.androidcentral.com/google-nexus-4/227416-another-nexus-4-issue.html
[Nexus 4 Q&A, Help & Troubleshooting] roger_rocky:
Same here. I cut off the part of the screen protector near the two "dots" on the top-left, and problem 1 and 2 are gone.
[Nexus 4 Q&A, Help & Troubleshooting] zannyboy:
Experiencing the same issue here with best skins ever. As a temporary fix, in accessibility set so power button ends call.
[Nexus 4 Q&A, Help & Troubleshooting] daweeze02:
Here's the reply I got :)

We did not experience any interference from our Skin during our in-house testing of the Nexus 4 proximity sensor. * But we have redesigned our Skin so that there is now a cutout for the proximity sensor.

We will be happy to provide you with the Nexus 4 screen Skin with the proximity sensor cutout on order #.......
[Nexus 4 Q&A, Help & Troubleshooting] DefunctiO:
I have the same issue... So I have contacted them. I hope I will get the same answer you got. :) Thanks for an brilliant idea :)
[Nexus 4 Q&A, Help & Troubleshooting] nhatters:
Awesome! I'm experiencing the same issue and have also contacted them.
[Nexus 4 Q&A, Help & Troubleshooting] Ok_Kaleidoscope5109:
That's actually consistent with my testing. Screen protector does not affect proximity sensor despite covering it. There is one video on youtube showing it affecting it, but if you look at his screen protector, it's all warped and has gunk all over the proximity sensor area. You wonder why.... The proximity sensor readout on my phone shows normal.

The fact that the proximity sensor isn't behaving during phone calls is an issue with or without the screen protector.
[Nexus 4 Q&A, Help & Troubleshooting] daweeze02:
I got the new skins and ever since my issues have gone away.
[Nexus 4 Q&A, Help & Troubleshooting] sam1955:
sam1955

I have got exactly the same problem with my Nexus 4 & also has recently updated to 4.2.1 all else works fine but as soon as a call request is pressed it goes black & no amount of power button pushing will work,& also does not react to incoming call every time!

Google support just saying return the handset
[Nexus 4 Q&A, Help & Troubleshooting] nhatters:
Likewise. My issues have too gone away after receiving a modified screen protector.
[Nexus 4 Q&A, Help & Troubleshooting] heynomi4u:
I faced all three issues that you mentioned here. My Nexus already had the 4.2.1 when I got it.

Having said that, Issue 1 and 2 just stopped happening after only 1 day (after I did a reboot). 3 still happens once in a week maybe.
[Nexus 4 Q&A, Help & Troubleshooting] ImWarped:
Just for reference. It's NOT a screen protector issue. I own 2 Nexus 4's, and 3 people at work have them.... All 4 of us have this issue. So 5 phones, only 1 of them has a screen protector on it. Initially I thought it was a root/rom issue, but it happens on the 3 factory spec'd phones too (never rooted, no customization) I haven't delved into it fully yet, but it happens on ASOP roms as well as stock... I would guess it's a bug in 4.2.1... I will flash back and give results shortly.
[Nexus 4 Q&A, Help & Troubleshooting] usmanCh:
Screen On/Off Issue

I had the same problem with the screen went black out and not responding but i wasn't either using protector. What could be the reason. I didn't found online but heard its problem with devices mostly having 8Gb . 16GB devices are fine. Is that so?
[Nexus 4 Q&A, Help & Troubleshooting] orbv:
Was having the same kind of issues. Got the scissors out and cut the screen protector back to expose the sensor and now is working well.

This is the 16g version.
[Nexus 4 Q&A, Help & Troubleshooting] page101:
Google Nexus 4 black screen

you were right
[Nexus 4 Q&A, Help & Troubleshooting] rpesta:
Fixed

I have an XtremeGuard skin. Newly applied perfectly. Turns out about 1mm of it was covering the left proximity sensor. I just used an xacto knife and cut off that little piece and the problem went away.
[Nexus 4 Q&A, Help & Troubleshooting] justforkix:
Taking off screen protector worked for me

I just got my new Nexus 4 and put a screen protector on it and updated to Android 4.2.2. The issue was there and it was a real one. I couldn't even hang up because I could not see where the button was.

Removing the plastic screen protector solved the problem.

I still consider it's an issue, because having a screen protector should not cause this.
[Nexus 4 Q&A, Help & Troubleshooting] Schwacker:
Wow, I'm glad I came across this for the past week this has been happening to me. I don't think it happened after upgrading to 4.2.2. but here is what is happening to me:

During a call (especially towards the end), I pull the phone away to hang up or use the keypad symbol to press a number. However, the screen doesn't come "alive" and I frantically press the power button to bring back the screen....however that turns into a game for the screen will quickly appear, and then back to darkness...the quickly appear then back to darkness.

I left a voicemail when this happened and i think I left a good 20 seconds of silence before I was able to hang up!

I don't use a screen protector but this is getting annoying!
[Nexus 4 Q&A, Help & Troubleshooting] ismethajametovic:
I was experiencing all three problems.

I have a screen protector and an ebay TUFF case. (Otterbox knockoff)

I fixed permissions and rebooted the phone and was still getting the problems.

I took off my case and made a call and found out the case was interfering with the proximity sensor.

So I guess when I have to make important calls, I have to take off my case. Otherwise, I'll get used to it or modify my case with a box cutter. :crying:
[Nexus 4 Q&A, Help & Troubleshooting] PeritoX:
Where can I find screen protectors that do not interfere with the proximity sensor?
[Nexus 4 Q&A, Help & Troubleshooting] ismethajametovic:
I don't think the screen protectors interfere with the P.S.

They are clear for godsake! However, I can see the anti glare S.P's giving us problems.
[Nexus 4 Q&A, Help & Troubleshooting] PeritoX:
They do. My phone wasn't turning on the screen during a phone call until i removed the screen protection.
[Nexus 4 Q&A, Help & Troubleshooting] ismethajametovic:
That's odd. I have a SP and mines fine. I resolved the issue when I took off my bulky case.
[Nexus 4 Q&A, Help & Troubleshooting] yuki71:
so glad i found this thread

got mine tuesday and have had all 3 issues

removes stock screen protector and have no issues
[Nexus 4 Q&A, Help & Troubleshooting] sunnywhite:
plastic screen protector makes screen turn off when call

You are correct, I cut the plastic protective film back down, and the screen turns on. use my finger to swip over the upper left corner, makes it on and off. that was the cause.

---------- Post added at 11:54 AM ---------- Previous post was at 11:37 AM ----------

First I cut down the plastic protecitve film, it seems solve the problem. Also download "Speaker phone" app has eliviated the problem. That makes the screen stays on whole time when I make calls. Even with my finger covers up the upper left corner "where senser located".

On 4.22 JDQ39, rooted, unlocked.
[Nexus 4 Q&A, Help & Troubleshooting] Marco12121:
I have the same problem in a call my screen turn off. But when i squeez the upper right corner near the front camera my screen turn on during a call. Let me know if its the same in your case
[Nexus 4 Q&A, Help & Troubleshooting] pk1025:
On/Off issue

The only issue I have and this happens sporadically, is when I'm done using my phone and I hit the power button to turn off the screen it turns off and then comes back on almost instantaneously, so it does the opposite of what it's supposed to do. I've noticed this sporadic issue after 4.2.2. Anybody else?
[Nexus 4 Q&A, Help & Troubleshooting] CoolApps:
1) If the device is close to you (I mean real close) then the proximity sensor will switch off the screen to save battery while calling.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] pk1025:
I think you misunderstood me. When I'm done with it and I want to turn the screen off it flickers back. So essentially I have to press the power button twice to turn it off.
[Nexus 4 Q&A, Help & Troubleshooting] sandy-achar:
And to avoid accidentally press unintended buttons on call.
[Nexus 4 Q&A, Help & Troubleshooting] CoolApps:
Oh ok.

Sent from my Nexus 4

---------- Post added at 07:29 PM ---------- Previous post was at 07:29 PM ----------

Yep.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] CoolApps:
The following properties will fix the black screen issues after calls and they must be added to the build.prop file:

ro.lge.proximity.delay=25

mot.proximity.delay=25

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] criticalfiction:
My workaround

I've been having this problem for a while. I've got a screen protector on, but it's got a cutout for the proximity sensor. Proximity is reported correctly on AndroSensor. My workaround has been to set the "Sleep" option under Settings -> Display to 30 minutes. It used to be set to 30 seconds, so I had this problem on almost every call. This appears to have fixed it. I assume I'll still have the problem if the call is longer than 30 minutes. Presumably there's some conflict with this setting when the screen is switched off during a call.
[Nexus 4 Q&A, Help & Troubleshooting] longford:
I have had point 1, 2 and 3 only after I upgraded to 4.3. Moreover, my wifi and bluetooth won't come on either.

Not sure if 4.3 165Mb update broke it or the 2 Mb update 3 days ago broke the wifi/bluetooth. Don't use wifi/bluetooth since most of my stuff is from broadband/3G..

I still have the screen protect which came with the device and do notice that there is a proper cutout for the 2 sensors on the top left. Not certain if this is a screen protect issue. Besides the happening of the above three issues is erratic and not consistent. For me, it happened like in less than 1% of the time.

But I suspect 4.3 had something to do with this.
[Nexus 4 Q&A, Help & Troubleshooting] bfettd:
Entirely possible. I have an N4 with no screen cover on it, this issue never presented itself before the update (and was slightly sporadic) - but now it's completely the case. AndroSensor has proximity readings of 0 constantly.

I really don't want to RMA the phone as that means wasting hours on a fresh set of installs / restores, but what else to do?

--Dan
[Nexus 4 Q&A, Help & Troubleshooting] munawwar:
I had this problem for a while (no screen protector). I did the following things (on Android version 4.3).

1. Checked whether my proximity sensor is working or not. The sensor is physically located at the top,left side of the phone. I used an app named AndroSensor to get the readings from the sensor. When nothing is close to the sensor, the reading shows '2.0 in'. And when I place my hand over it, then reading shows '0.0 in'. So I assume the thing is working fine. In any case I cleaned the glass above the sensor with a cloth.

2. As recommended at other places (can't post link cuz I have < 10 posts), I went to Settings > Apps > All > Phone and clicked Clear data, rebooted phone and behold..the screen now turns on properly when I move the phone away from my ear during call.

EDIT: btw, doing this will not delete your call logs (just a clarification, in case you are worried about that).

I love this phone!..this was the only problem I had with it and it is solved now :cool:
[Nexus 4 Q&A, Help & Troubleshooting] jatink007:
I never faced this problem with 4.3. but lately the problem no 3 is occurring a lot. Any clues to wat the problem would be? its definitely not the proximity sensor or the case.

Please help
[Nexus 4 Q&A, Help & Troubleshooting] jatink007:
Updated to kitkat....now its working fine. I guess its a flaw in the OS itself :)
[Nexus 4 Q&A, Help & Troubleshooting] LumiqFI:
Removing the screen protector worked for me too
[Verizon Samsung Galaxy S III] SubaruCop:
So while browsing between my samsung Internet app and chrome, every time I click on the factory browser, I get a blue tint to my screen. If I hit the back button it clears up but immediately closes. Does anyone have a clue on how to fix it. I am stock not rooted.
[Verizon Samsung Galaxy S III] President Jesus:
Do you happen to have power saving mode turned on? I know (at least on JB, not quite sure about ICS) there is an option in there which sets the browser to be like that when it is enabled.
[Verizon Samsung Galaxy S III] Dmwitz:
It sounds like the Power Save function. The blue tint saves power.
[Nexus 7 Q&A, Help & Troubleshooting] Dark_shadow70:
I Did something really stupid, I have a Nexus 7, rooted, unlocked, went to twrp and did a back up of the stock rom, it said successful, then rebooted used the rom, everything perfect but I had tablet mod on it, decided to go back to full stock, booted to recovery, wiped everything, tried to restore and my backup is not there, and I deleted the rom as well, so now I have no rom to flash and I'm stock in recovery, anyway to push a rom into the nexus in recovery or bootloader? I tried flashing it with root toolkit 1.5.5 but it doesn't find the tablet,(all the drivers are installed), any and all help is appreciated...:confused:
[Nexus 7 Q&A, Help & Troubleshooting] exglynco:
Your PC won't see your N7 in Android because you haven't turned on USB debugging, and probably can't now.

You should be able to push an updated TWRP in fastboot that will see your 4.2 backup. The older version can't find its backups in 4.2,as you've discovered.

I'm not the lowest of the low, but I am the slowest of the slow.
[Nexus 7 Q&A, Help & Troubleshooting] Dark_shadow70:
I did have it on, I can see the tablet from control panel, but when I run the kit it says adb device not found..
[Nexus 7 Q&A, Help & Troubleshooting] exglynco:
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.

I'm not the lowest of the low, but I am the slowest of the slow.
[Nexus 7 Q&A, Help & Troubleshooting] joshnichols189:
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.

Try the toolkit in fastboot.
[Nexus 7 Q&A, Help & Troubleshooting] Dark_shadow70:
when I'm in the bootloader it says it's in fastboot mode, but the toolkit wont find it!

I running recovery 2.3.2.1

tried adb sideload as well and it says "cannot read sideload" any ideas? getting a little crazy here..:eek:
[Nexus 7 Q&A, Help & Troubleshooting] Dark_shadow70:
Can anybody give me specific commands in ADB or fast boot I'm an idiot when it comes to that, on how to try to push a ROM into the device so I can flash it from recovery, or maybe a link to where I can read about it, I would really appreciate it..
[Nexus 7 Q&A, Help & Troubleshooting] RMarkwald:
While in recovery, type in the following:

adb push <name of ROM zip> /sdcard

You need to open a command prompt window, change directories (cd) to your Android SDK - platform tools directory, and to make things easy, move the ROM zip file into that directory as well (platform-tools that is). Then type the adb push command above.

EDIT: This puts the ROM zip on the root of your sd card (/sdcard). I have a ROM folder on my sd card, so I would type:

adb push <name of ROM zip> /sdcard/ROM

This just shows that you can push a file into a folder on your sd card.
[HTC Droid DNA] another581:
I was just testing a different SIM card, and as I put the original Verizon SIM card back in, for some odd reason it got locked automatically.

The Verizon store is only 5 minutes away by walking from my location, so I went there and asked for the PUK code.

But as the clerk tried retrieving the PUK, she said it is yet to be available for confirmation and that it will take approximately one to two weeks...and I have to leave the device with them since they don't know why the SIM card has no PUK provided.

I just told them to email me once the PUK is ready and brought my phone back. I had accidentally locked my phone with a South Korean carrier before but as for that incident, a simple reset to the whole system got the job done. But this is the first time I have ever had a SIM card from Verizon, so I don't know if there are other ways to unlock the SIM card lock or reset it

Does anyone have a solution? Thanks
[HTC Droid DNA] bwhite757:
Mine did this without removing the SIM, completely locked up on me, this was after I was getting "No SIM card" errors. Verizon tried replacing the SIM card first, but it locked up again before I got out of the store. So they just DOA'd the phone and gave me a new one with new SIM card. Haven't had another issue.
[HTC Droid DNA] nixta_72:
Same thing was happening to me...brought it to Verizon and they gave me the "bad batch of Sims from old supplier line"...they replaced the sim and I haven't had the issue since.