Related
As I put in the topic, I'm running the newest liquid smooth build on my N10. Everything is running really great on it, but I can't connect to WiFi at all? Sorry for posting this here but I'm a noob and can't post in the dev forums yet. Any help would be greatly appreciated considering my tablet is useless without WiFi!
Sent from my HTC One XL using xda app-developers app
Some wifi problems are inherent to 4.2. But if wifi doesn't turn on immediately after flashing any rom, usually a reboot cures it. Before rebooting tho, try cycling Airplane mode on/off.
Sent from my Nexus 10 using Tapatalk 2
djd338 said:
Some wifi problems are inherent to 4.2. But if wifi doesn't turn on immediately after flashing any rom, usually a reboot cures it. Before rebooting tho, try cycling Airplane mode on/off.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
I've already tried rebooting several times. I even booted into recovery and wiped everything again and reflashed the Rom. Still no WiFi? I've never had a problem with it on stock or cm10.1
Sent from my HTC One XL using xda app-developers app
I never had wifi issues with my N10 until I decided to give Liquid's newest build a try. I tried all the tricks - reboots, toggling airplane mode, even started from scratch and reflashed the entire ROM but had no luck. Sometimes it would connect for a moment, but then would immediately disconnect. As soon as I returned to my latest backup (Steve Spear's AOKP pub builds), and even since trying other ROMs I've had no wifi issues. I'm saying with 100% certainty there's a problem with Liquid's ROM, but it sure seems that way to me.
Maybe redownload the ROM and start over (perhaps something got messed up while downloading). That's the one thing I never tried as I got tired of monkeying around with it.
Rodeojones said:
I never had wifi issues with my N10 until I decided to give Liquid's newest build a try. I tried all the tricks - reboots, toggling airplane mode, even started from scratch and reflashed the entire ROM but had no luck. Sometimes it would connect for a moment, but then would immediately disconnect. As soon as I returned to my latest backup (Steve Spear's AOKP pub builds), and even since trying other ROMs I've had no wifi issues. I'm saying with 100% certainty there's a problem with Liquid's ROM, but it sure seems that way to me.
Maybe redownload the ROM and start over (perhaps something got messed up while downloading). That's the one thing I never tried as I got tired of monkeying around with it.
Click to expand...
Click to collapse
Would you mind posting the link to that ROM? I don't have time to mess around with issues and need a solid and fast daily driver. I use autocad on my N10 for work so I'm needing this resolved badly!
Sent from my HTC One XL using xda app-developers app
Nevermind, stupid question lol I'm downloading another Rom now. Ill just have to wait on liquid smooth to come out of its beta stages before using it.
Hmm... I'm on the latest LiquidSmooth and wifi works just fine for me.
dust. said:
Hmm... I'm on the latest LiquidSmooth and wifi works just fine for me.
Click to expand...
Click to collapse
See that's what doesn't make sense to me, nobody else seems to have this issue? I might just try wiping everything and reflashing again tonight.
Sent from my HTC One XL using xda app-developers app
liquidismooth v.2.10 galaxy s 4 t Mobile issues
cman_17 said:
As I put in the topic, I'm running the newest liquid smooth build on my N10. Everything is running really great on it, but I can't connect to WiFi at all? Sorry for posting this here but I'm a noob and can't post in the dev forums yet. Any help would be greatly appreciated considering my tablet is useless without WiFi!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I got such smooth ROM with no WiFi whatsoever and can't make landline calls only to cellular why don't know? But so far is the most fast and smooth ROM available
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
jspitzer221 said:
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
flash stock, you wont have to deal with it.
jspitzer221 said:
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
SoD seems to show up randomly... I've heard that JWR ROMs have less SoDs than JSS so you could try one, or if your not into switching ROMs here is an app (free) that could help you. It's called Safe Charge, and the comments say that it works great.
If you read my OP, I already have Safe Charge installed and am still getting sod. I really like the ROM I'm using, but I may just have to switch to avoid this unfortunate issue.
Sent from my Nexus 4 using xda app-developers app
jspitzer221 said:
If you read my OP, I already have Safe Charge installed and am still getting sod. I really like the ROM I'm using, but I may just have to switch to avoid this unfortunate issue.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Oops I guess I missed that part... I'm pretty sure that you can find a near similar ROM/kernel setup for JWR... If all else fails, try stock...
(Oh and if you can still RMA it, do it. People have speculated that its a hardware issue...)
No worries. I'm trying out SlimBean because I hear that doesn't have the issues, but not being able to use Franco with it is a bit of a bummer. In fact I haven't yet found a third party kernel that does work with it.
Sent from my Nexus 4 using xda app-developers app
I had this happen to me with a particular rom. Everything was great until id lock the phone, then try to unlock and see nothing but a black screen. I switched roms and it never happened again.
Sent from my SGH-I317M using xda premium
I have a sprint LG g2.
Just recently the process Sensors.qcom started using cpu all the time and is murdering my battery life.
I am unrooted using stock everything.
What is Sensors.qcom and how can I stop it from eating my battery?
Sent from my LG-LS980 using Tapatalk
xNotta said:
I have a sprint LG g2.
Just recently the process Sensors.qcom started using cpu all the time and is murdering my battery life.
I am unrooted using stock everything.
What is Sensors.qcom and how can I stop it from eating my battery?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I'm having this problem also.
What is sensors.qcom?
same here but on the nexus 5 since the latest update
I toggled all of my sensors and rebooted a few times and the next day the process was gone.
Haven't seen it since. Doesn't even show in battery usage anymore.
I read something about apps that don't shut down the sensor after it finished using it and the still in use sensor was why that process was running.
But I'm not sure if that is even close to what is happening.
Try seeing if it's running around time of startup, if it is, find out which downloaded apps auto start and disable or uninstall them and reboot again.
Sent from my Sprint LG G2 (LS980) using Tapatalk.
just had this issue myself, anyone else had it and managed to fix it??
My phone is 3 days old and noticed my batterylife wasn't as good today, it came down to Sensors.qcom.
Can anyone else tell me there experience?
I also have a nexus 7, I was seeing the same issue with it.
So I found sensors. Qcom in system/bin, then changed its name to sensors.qcom.bak.
I lost my accelerometer, but things seem to be fine.
This is the problem with our G2s. Certain apps are keeping the accelerometer in use after the app has closed, a definite Google issue.
Sent from my Nexus 7 using XDA Premium 4 mobile app
markdexter said:
I also have a nexus 7, I was seeing the same issue with it.
So I found sensors. Qcom in system/bin, then changed its name to sensors.qcom.bak.
I lost my accelerometer, but things seem to be fine.
This is the problem with our G2s. Certain apps are keeping the accelerometer in use after the app has closed, a definite Google issue.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well need to find those bloody apps then. I have GiONEE Elife E7 with same battery drain issue with sensor.qcom
I had such a problem for a long time. But then I used the application "Ccleaner for Android 2.0" (or later) and delete this process. It was in the section "Delete at your discretion". I have LG G2 sprint unlocked by a European operator with root. All my sensors (accelerometer) work very well. sensors.qcom stay in system/bin
I bought a LG G2 on launch day and loved it except the screeching during voice calls. I had it swapped several times until it was realized that it was a software issue. My friends exchanged their G2s for the same issue. My question is, has this been fixed already or is the update rolling out today meant to fix this issue? Thanks.
That's definitely not a software issue. I've not had a single issue with my g2. To me that sounds like hardware. Easiest way to find out: download stock unrooted Rom in verizon development section, flash it and then test. If you're rooted just download the rooted stock Rom and flash as usual in custom recovery. If it's software a clean flash should do the trick. I'd be surprised if it wasn't hardware related though.
Sent from my VS980 4G using XDA Premium 4 mobile app
BreakingVZW said:
That's definitely not a software issue. I've not had a single issue with my g2. To me that sounds like hardware. Easiest way to find out: download stock unrooted Rom in verizon development section, flash it and then test. If you're rooted just download the rooted stock Rom and flash as usual in custom recovery. If it's software a clean flash should do the trick. I'd be surprised if it wasn't hardware related though.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nah, it was software. I did flash quite a few ROMs and it didn't help. I had the same issue on my Note 3 and a software update from Verizon fixed it. I'm just curious if they've fixed it for the G2 yet.
slide83 said:
Nah, it was software. I did flash quite a few ROMs and it didn't help. I had the same issue on my Note 3 and a software update from Verizon fixed it. I'm just curious if they've fixed it for the G2 yet.
Click to expand...
Click to collapse
Yes, if you are stock, unrooted, take the update. If you are rooted, flash one of the new radios / modems for Verizon here:
http://forum.xda-developers.com/showthread.php?t=2451426
I flashed the 12B version and everything has been perfect since.
rfarrah said:
Yes, if you are stock, unrooted, take the update. If you are rooted, flash one of the new radios / modems for Verizon here:
http://forum.xda-developers.com/showthread.php?t=2451426
I flashed the 12B version and everything has been perfect since.
Click to expand...
Click to collapse
I was leaning towards software bc I haven't experienced any of those screeching issues. If it was software one would think it would effect more ppl. Glad the update got you squared away.
I'm waiting for a rooted zip of the ota.
Sent from my VS980 4G using XDA Premium 4 mobile app
Got it on 12B, but only during a 4G to 3G switch, then dropped call. Coverage inn my house is spotty. Otherwise, sounds great.
Had it on my gnex and sounds the same on my g2. Definitely a Verizon thing.
Sent from my VS980 4G using Tapatalk
I didn't notice anything of the sort on my Gnex or G2 on Verizon. Towers maybe?
Sent from my VS980 4G using XDA Premium 4 mobile app
Happens only on very low signal /4G to 3G switch to me. ^
Normal really.
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
Hello, I have been experiencing moments of "freezing" or unresponsiveness as well.
For me, it seemed to be due to chrome or using power saving mode. (People in another forum were blaming their droid maxxs freezing problem on chrome) I disabled chrome and disabled power saving mode.
Then I started using opera. I experienced another moment of unresponsiveness using opera without the power saving mode.
I was thinking back to the first times that it happened and it seemed to be paired to the wifi download and upload symbol being active in upload and download activity.
I know that correlation does not mean causation, but I think it is worth exploring if the network activity is causing it to somehow hang.
This bizzar occurance made me perform a factory wipe leading to another round of issues involving processing err_0000, but that is another story; sadly, it didn't even fix the issue.
OP, are you still experiencing the moments of unresponsiveness? If you are, have you noticed the events that are correlated with the event?
Has anybody else experienced this or found a remedy?
It could be one of the apps from the play store that is not playing nice with kitkat, but due to the multitude of other issues, I'd say it is a kitkat or touchwiz flaw.
Thanks for any help.
Lago
nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
I had an issue with screen not responding sometimes .....I figured out it was due to the flip case (original by Samsung). Although lately I haven't experienced that either.
Try using the original non flip case and see if you still have the issue.
Sent from my SM-N9005 using XDA Premium 4 mobile app
pac-mannan said:
Try using the original non flip case and see if you still have the issue.
Click to expand...
Click to collapse
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app
lagoboss said:
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If your phone isnt hanging up and freezing, that gives me hope. I'll gsm reset, clear the cache and then flash.
Thanks
Sent from my SM-N900 using xda app-developers app
pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just cleared the cache, factory wiped, and installed the Russian update N900XXUDNC4 and so far, the phone is a lot smoother. No hangups in the browser yet, but time will tell lol.
It is annoying setting up the phone like new lol. I'll update the post as to if I have moments of freezing or the screen becoming unresponsive.
Sent from my SM-N900 using xda app-developers app
Cheers mate..do tell me how the battery is..if its good I might flash Russian as well ,currently have but flashed
Sent from my SM-N9005 using XDA Premium 4 mobile app
Had this problem too, as well as lots of lag. Reflashed and did a factory reset. Took care of both.
Sent from my SM-N900W8 using xda app-developers app
Battery life is looking good. Power Saving off, bluetooth on and connected to my smart watch.
I made one short call. I don't talk on the phone that much. I mostly use it for Internet browsing, music, and instant messaging/texting. I'll update on Tuesday when I have a full day at school.
Keep in mind though that the n9005 is the lte version. I have a n900, the non lte international variant; our battery life may be different.
Edit: 4/20/2014 same charge 70% 1 day 6 hours bluetooth, wifi, gps, and 1 Gmail account in sync.
Sent from my SM-N900 using xda app-developers app
Even I experienced the same. My phone came with Kitkat installed. Freezing happens when a webpage is loading or the time i turn on Sync etc. strange thing is phone seems smooter when power save mode turned on.
I think it may be a problem that was not fixed until the March 31st 2014 KitKat build. I have been using Chrome heavily since I installed the most recent official rom; I have not experienced any lag or hanging system wide or in the browser. It reminds me of 4.3.
When I wiped and reinstalled the previous rom, I noticed the lag and unresponsiveness right away.
I'm going to use the browser heavily next week. If I have no issues, I think it may be safe to say that the bug was fixed in the latest kitkat with March 31st 2014 build date.
People with lag, do you have the lte variant or the regular SM-N900? I'm starting to think only the SM-N900 are being impacted by sour Sammy updates.
And if you guys wipe your phones, make sure to turn reactivation lock off because it could cause an error that will not recognize your real Sammy account and password. This phone has become stressful; I'm not updating it again lol
Sent from my SM-N900 using xda app-developers app
I just experienced another moment of unresponsiveness using the google search box within the chrome app running DNC4 :/ Going to try the latest Russian KitKat
Sent from my SM-N900 using XDA Free mobile app