Related
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?
Hi buddies
As Grarak chose to close the thread of his rom and that maybe some of you want to have some more return and exchanges about the way the rom works, discuss about bugs etc, i open this thread, so that we will be able to do what a forum is done for : talk and exchange together.
New version is 12082014, any return?
Testing soon..
Is calling with sim 2 in 2g working Now?
If not how to use it Any tetsters!
Edit :still No sound from sim2
and there is No way to chose network type
and No 3g from sim 2 too
Im on 9-12-14 build....2g sim not working same as official cm11....3g sim is working......
i 've had terrible battery life, and searching on google lead me to a battery misc processus eating battery, problem solved with 5.0.1 by google
do you guys have the same experience, and have heard about a fix incorporation in the new builds? :good:
I had to go all the way back to the 11-20-14 build. I tried updating to the new builds 12-8, 12-9 and 12-10. No data at all on any of these builds.
Flashed the newest build! We're on Lollipop 5.0.1 now This update is supposed to help battery life. We'll see.
The new music app automaticaly force closes, and the DSPmanager was replaced with AudioFX.
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
fabulous69 said:
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
Click to expand...
Click to collapse
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
FoxyDrew said:
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
Click to expand...
Click to collapse
mhm then i think a change that has broke the app. I m sure Grarak will correct it in the next release
Ok, the ROM was going great for me, then yesterday at work my phone turned off when it was in my pocket. I tried turning it on, it booted, started doing the boot animation and then did that for five minutes before it shut off again. This time it wouldn't turn back on no matter how many times i tried power cycling or booting into bootloader. When I got home I tried charging it and the light wouldn't even come on. So I plugged it into my PC and the phone showed up as qhsusb_bulk. After researching that i found it means the bootloader got wiped somehow. My question is, how could my bootloader be gone, because as far as I know, no one has gotten their device S-OFF.
your device is bricked
seems there is a solution on the web but not working for everybody and for specific devices
i dont know what to advice you...
i dont know if it is rom related, but if it is, i wont flash this !
Yes that's what i figured. Luckily Amazon was nice enough to give me a new phone once I send that one in. I was just trying to figure out how it would even be possible that my bootloader got fried, considering my device was still S-ON.
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
DRAGONMM2010 said:
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
Click to expand...
Click to collapse
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
Completely agreed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
fabulous69 said:
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
Click to expand...
Click to collapse
Didn't test it. Haven't spent enough time on Lollipop because of the no data issue.
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
thirteen_percent said:
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
Click to expand...
Click to collapse
Yah data works...just not good. It has to do with not being able to access APN's.
No one want's to sit "for a WHILE" to open a webpage or read an email.
On the latest build, System UI crashes.
Currently running the latest Chroma rom with the stock kernel. The little circle that's supposed to show up around the lock icon at the bottom doesn't show up 90% of the time (http://prntscr.com/abhku3). I'm trying to unlock it with a bluetooth (not NFC) fitness band.
This isn't a problem with the band, because I tried putting Face Unlock as well, but the detection doesn't show up most of the time.
Is there any way to fix this?
sixaxis94 said:
Currently running the latest Chroma rom with the stock kernel. The little circle that's supposed to show up around the lock icon at the bottom doesn't show up 90% of the time (http://prntscr.com/abhku3). I'm trying to unlock it with a bluetooth (not NFC) fitness band.
This isn't a problem with the band, because I tried putting Face Unlock as well, but the detection doesn't show up most of the time.
Is there any way to fix this?
Click to expand...
Click to collapse
I haven't had an issue with smart unlock before, I pair it with my Moto 360. I don't know if it's the kernel because I personally use the Taurus kernel and not the stock one, that might be a reason but again I don't know for sure at all. Maybe on Multirom I'll install a second Chroma and leave it on stock and see if I can get it to reproduce what you're having, I'll get back to you in about 20-30 minutes on how it goes.
-Edit- Might be a bit longer since I need to redownload the latest build. My internet can be slow at times
-Edit 2- I haven't had the issue, at least with my watch. Not too sure how much further I could help you :/
fireball0093 said:
I haven't had an issue with smart unlock before, I pair it with my Moto 360. I don't know if it's the kernel because I personally use the Taurus kernel and not the stock one, that might be a reason but again I don't know for sure at all. Maybe on Multirom I'll install a second Chroma and leave it on stock and see if I can get it to reproduce what you're having, I'll get back to you in about 20-30 minutes on how it goes.
-Edit- Might be a bit longer since I need to redownload the latest build. My internet can be slow at times
-Edit 2- I haven't had the issue, at least with my watch. Not too sure how much further I could help you :/
Click to expand...
Click to collapse
Thanks for helping out! I tried with the Quanta v10 kernel but had the same problem. Reinstalled the rom. No dice :/
This is strange
sixaxis94 said:
Thanks for helping out! I tried with the Quanta v10 kernel but had the same problem. Reinstalled the rom. No dice :/
This is strange
Click to expand...
Click to collapse
It is a bit strange. I do have one final thing to test out actually. I just remembered my girlfriend got a generic bluetooth fitness band thing for her senior year, I'll charge that up and see if that gives the same issue since I still have the multirom boot with it. It'll take probably an hour to charge it since it's just a generic one.
fireball0093 said:
It is a bit strange. I do have one final thing to test out actually. I just remembered my girlfriend got a generic bluetooth fitness band thing for her senior year, I'll charge that up and see if that gives the same issue since I still have the multirom boot with it. It'll take probably an hour to charge it since it's just a generic one.
Click to expand...
Click to collapse
I'm certain it's not the band's fault cause gave unlock isn't detected either. I'll try the pure nexus and cm roms to see if it makes a difference.
sixaxis94 said:
I'm certain it's not the band's fault cause gave unlock isn't detected either. I'll try the pure nexus and cm roms to see if it makes a difference.
Click to expand...
Click to collapse
Especially if the band was working fine on other roms or devices. CM 13 is my main daily driver rom and I haven't had a single issue with several bluetooth devices I own, I always will recommend it xD The fitness band is almost charged and I'll test that out here real soon
fireball0093 said:
Especially if the band was working fine on other roms or devices. CM 13 is my main daily driver rom and I haven't had a single issue with several bluetooth devices I own, I always will recommend it xD The fitness band is almost charged and I'll test that out here real soon
Click to expand...
Click to collapse
I only got the band 2 days ago and have just tested it on Chroma.
Quick question, does CM13 support Volume Key to unlock AND double tap status/nav bar to lock? My power button is screwed up and it barely registers. Also, are the latest nightlies stable or should I go with an older build, if I don't plan to update my rom in the next month?
sixaxis94 said:
I only got the band 2 days ago and have just tested it on Chroma.
Quick question, does CM13 support Volume Key to unlock AND double tap status/nav bar to lock? My power button is screwed up and it barely registers. Also, are the latest nightlies stable or should I go with an older build, if I don't plan to update my rom in the next month?
Click to expand...
Click to collapse
Double tap to sleep, yes. Let me quick boot into it to make sure for the volume key. If you get Kernel Auditor and the right kernel you can have double tap to wake which is wonderful. Ok it does have the option for volume key unlock. I haven't had any issues with the nightlies, a while back I had one that would randomly freeze my touchscreen but that was early last month.
fireball0093 said:
Double tap to sleep, yes. Let me quick boot into it to make sure for the volume key. If you get Kernel Auditor and the right kernel you can have double tap to wake which is wonderful. Ok it does have the option for volume key unlock. I haven't had any issues with the nightlies, a while back I had one that would randomly freeze my touchscreen but that was early last month.
Click to expand...
Click to collapse
Sweet, I'll give CM a shot! I hope the smart unlock was a rom problem and not a hardware one. My phone's nearing the end of it's life, so it's more than possible.
sixaxis94 said:
Sweet, I'll give CM a shot! I hope the smart unlock was a rom problem and not a hardware one. My phone's nearing the end of it's life, so it's more than possible.
Click to expand...
Click to collapse
How's CM holding up for you? Is Smartunlock working on it at all?
fireball0093 said:
How's CM holding up for you? Is Smartunlock working on it at all?
Click to expand...
Click to collapse
I haven't gotten around to it yet. I'll try it later this week and report back
fireball0093 said:
How's CM holding up for you? Is Smartunlock working on it at all?
Click to expand...
Click to collapse
It was a problem with Chroma. I'm running CM now and the Smart Lock works flawlessly!
sixaxis94 said:
It was a problem with Chroma. I'm running CM now and the Smart Lock works flawlessly!
Click to expand...
Click to collapse
Glad to hear it's working! I've been having some issues on Marshmallow in general lately, contacts aren't syncing from Google. But, I'm gonna open up my own help thread for that xD
https://www.xda-developers.com/omni...-added-improved-camera-for-xperia-xx-compact/
download from here
http://dl.omnirom.org/kagura/
anyone tried it?
tonight, as soon as possible
mkhalid said:
download from here
http://dl.omnirom.org/kagura/
anyone tried it?
Click to expand...
Click to collapse
sony xperia XZ？？？
I just installed it, so far it works well and seems better optimized than the AOSP version of Sony.
oh ****, too much not developping aosp and omnirom gets in
Not support sony xz dual. Sim delected
I hope rom support sony xz dual.
Had it for a few hours. Feels nice, the finger recognition doesnt really work though. Cameras good, sound is ok, once the finger recognition works thatl be ace. Just remember to install supersu and gapps too guys.
Few things...
- Bluetooth is messed up (range seems to be extremely limited and the audio quality when using a Bluetooth device is unusable)
- Severe echo during phone calls when not using Bluetooth
- Screen is frequently unresponsive after waking the phone. Pressing the power button to turn off the screen and turn it on again helps. Seems to be fixed by turning off Double Tap Screen to Wake
- No way to get it to pass SafetyNet
I'd recommend against using this. Certainly not a Daily Driver, but glad to see they're making progress.
thatguy222 said:
Few things...
- Bluetooth is messed up (range seems to be extremely limited and the audio quality when using a Bluetooth device is unusable)
- Severe echo during phone calls when not using Bluetooth
- Screen is frequently unresponsive after waking the phone. Pressing the power button to turn off the screen and turn it on again helps. Seems to be fixed by turning off Double Tap Screen to Wake
- No way to get it to pass SafetyNet
I'd recommend against using this. Certainly not a Daily Driver, but glad to see they're making progress.
Click to expand...
Click to collapse
Install next lock screen to find, the unresponsive after unlocking. There's no lock screen that's why.
Camera is poor too. I am using it and find it usable after finding a few apps to get around solutions. Battery life is crazy good atm.
Here's a good link to give ppl a rough idea of port status.
https://docs.omnirom.org/Nougat_Device_Status
Guadostar1 said:
Had it for a few hours. Feels nice, the finger recognition doesnt really work though. Cameras good, sound is ok, once the finger recognition works thatl be ace. Just remember to install supersu and gapps too guys.
Click to expand...
Click to collapse
thatguy222 said:
Few things...
- Bluetooth is messed up (range seems to be extremely limited and the audio quality when using a Bluetooth device is unusable)
- Severe echo during phone calls when not using Bluetooth
- Screen is frequently unresponsive after waking the phone. Pressing the power button to turn off the screen and turn it on again helps. Seems to be fixed by turning off Double Tap Screen to Wake
- No way to get it to pass SafetyNet
I'd recommend against using this. Certainly not a Daily Driver, but glad to see they're making progress.
Click to expand...
Click to collapse
Guadostar1 said:
Install next lock screen to find, the unresponsive after unlocking. There's no lock screen that's why.
Camera is poor too. I am using it and find it usable after finding a few apps to get around solutions. Battery life is crazy good atm.
Here's a good link to give ppl a rough idea of port status.
https://docs.omnirom.org/Nougat_Device_Status
Click to expand...
Click to collapse
I see, they used my work on aosp, it contains some exact bugs i got before, i fixed some of them in the lastest build thanks to XZ dev discord
Camera has many issues. Fingerprint sensor. Few other small bits. But I love it. Shame battery dies so quickly due to "miscellaneous" app in battery usage.
New weekly build came out but I think no changes
fastbooking said:
oh ****, too much not developping aosp and omnirom gets in
Click to expand...
Click to collapse
Nevermind, and keep up your good work :good:
New nightly released was good, fixed a few smaller issues, but still the odd unresponsive lock screen once in 5, but only takes 1 second to hit the power button again.
Nightly build change logs can be found here
https://omni.cmxlog.com/7.1/kagura/
F8332安装omni rom无法识别sim卡
Guadostar1 said:
New nightly released was good, fixed a few smaller issues, but still the odd unresponsive lock screen once in 5, but only takes 1 second to hit the power button again.
Nightly build change logs can be found here
https://omni.cmxlog.com/7.1/kagura/
Click to expand...
Click to collapse
How do you find the call quality?
It's garbled over bluetooth here, and in non-bluetooth calls the other person always complains they can hear an echo of their own voice.
Music quality over in-car bluetooth is fine though.
Apart from the above issue & the occasional random compilation error when applying a Substratum theme, it seems to run well so far.
I would be happiest if someone made a nice kernel, like the EX for our OmniRom featured XZ Kagura.
I would like to be able to play with that, but unfortunately I do not have time, and there are smarter people with much more experience @flar2 @_LLJY @AndroPlus
uglavnom_bezopasni said:
I would be happiest if someone made a nice kernel, like the EX for our OmniRom featured XZ Kagura.
I would like to be able to play with that, but unfortunately I do not have time, and there are smarter people with much more experience @flar2 @_LLJY @AndroPlus
Click to expand...
Click to collapse
Amen to that. ROM is pretty stable with only few quirks so let the fun begin
Sent from my F8331 using XDA-Developers Legacy app
AOSP kernel I made a long time ago..
I use this rom and it does not detect my Sim
F8332 anyone has the same problem
Hi all,
My screen would blackout from time to time. When I unlock the phone the screen wouldn't turn on but everything else works like multi touch. I feel the vibrate when navigating around.
A solution that works sometimes is hitting power button twice to launch camera.
I'm running Havoc Pie ROM. I know it's not an issue with the ROM because it happen with all of the. I've tired about 4 ROMs and is the same problem.
Please help me find a solution because it's very frustrating and is troublesome in a emergency situation.
Thanks in advance.
Did you drop the phone at any point?
Or anything to cause this?
Have you installed an app that was on all ROMs that you've installed?
EG: Camera app.
Turn of automatic brightness,or stop using gsi with vendor...its a bugfest
Predatorhaze said:
Turn of automatic brightness,or stop using gsi with vendor...its a bugfest
Click to expand...
Click to collapse
If I think back... This started after I converted to treble
vic_singh said:
If I think back... This started after I converted to treble
Click to expand...
Click to collapse
dont go lower than 10%! brightness or the screen come black! and you cant continue becus you cant see nothing.(also disable auto brightness)
yes it can be a vendor problem,yes it can also be a image problem.
i just give my opinion its not really needed to have a gsi pie image on your phone,for now its full with bugs,and i think there is really not much improvements on the pie OS compared to oreo