Database Develop

ICS bug or Vivid bug?

I am running ICS (stock, rooted) and have noticed that sometimes when I try to make a phone call, I cannot dial out (all calls fail). This happens until I toggle airplane mode on/off or reboot. Then it works again for some amount of time, but I eventually need to do the airplane mode toggle again.
Problem is that because I Just got the Vivid on Friday, I don't really know if the phone would do this on GB too (Vivid bug) or if this is something new (ICS bug)? It's not a big deal, but it is a little annoying.
Anyone else able to offer any input or feedback?
Thanks.

Been running Rum Float since it was released and have not had that problem. Currently using WCX ICS and again, having no problems other than what has already been noted in multiple locations (all no-sense related).

Thanks. I will needed to pay attention to when it is happening. I wonder if the phone gets stuck in LTE mode and therefore can't call out.
Sent from my latest device

mpicasso said:
Been running Rum Float since it was released and have not had that problem. Currently using WCX ICS and again, having no problems other than what has already been noted in multiple locations (all no-sense related).
Click to expand...
Click to collapse
Sorry to ask, but where do you find wcx ics for vivid. I can't seem to find it

anthromatt said:
Thanks. I will needed to pay attention to when it is happening. I wonder if the phone gets stuck in LTE mode and therefore can't call out.
Sent from my latest device
Click to expand...
Click to collapse
I am running stock rooted ICS as well. I haven't had any problems but I am not in an LTE area.
Sent from my HTC PH39100 using Tapatalk

marevalo said:
Sorry to ask, but where do you find wcx ics for vivid. I can't seem to find it
Click to expand...
Click to collapse
You would have to find where wild child is these days if you look a bit you will find it
Sent from my HTC PH39100 using xda premium

Look at wc's sig......it says my site look there for info
U have to sign up to see vivid tho

Non responsive touchscreen

Hello,
Since I've bought my Incredible S about 8 months ago, I've been experiencing this problem. Somethimes, when I'm writing a message, there is 1 letter that doesn't work, if I press on it, it chooses the letter besides it. If I exit the app and reopen it, everything is fine. So its only the keyboard that's acting weird.
I had this on the standard 2.3.3 and 2.3.5 and now on 4.0.3 with the Virtuous Quatrro ROM.
Now I'm using the default ICS keyboard, on Gingerbread I used Better Keyboard.
Does anyone know a sollution?
Just to notice, my phone was send to HTC for repair somewhere around Octobre last year, and they replaced the whole front, including the screen. 2 weeks before that, they replaced the motherboard. So I still had the problem after the repair. And I think it's not software related, bevause it's just when I'm typing something, and not when I'm scrolling trough menu's or something like that.

Had the same problem. And I have a solution: don't notice it
I know its irritating sometimes, but that's not a real problem, so take it easy
Sent from my Incredible S using Tapatalk

SandySemenov said:
Had the same problem. And I have a solution: don't notice it
I know its irritating sometimes, but that's not a real problem, so take it easy
Sent from my Incredible S using Tapatalk
Click to expand...
Click to collapse
Well, half the times I'm writing a message there is at least one key not working, and I have to reopen the app, it's quite frustrating...

MrSenne said:
Hello,
Since I've bought my Incredible S about 8 months ago, I've been experiencing this problem. Somethimes, when I'm writing a message, there is 1 letter that doesn't work, if I press on it, it chooses the letter besides it. If I exit the app and reopen it, everything is fine. So its only the keyboard that's acting weird.
I had this on the standard 2.3.3 and 2.3.5 and now on 4.0.3 with the Virtuous Quatrro ROM.
Now I'm using the default ICS keyboard, on Gingerbread I used Better Keyboard.
Does anyone know a sollution?
Just to notice, my phone was send to HTC for repair somewhere around Octobre last year, and they replaced the whole front, including the screen. 2 weeks before that, they replaced the motherboard. So I still had the problem after the repair. And I think it's not software related, bevause it's just when I'm typing something, and not when I'm scrolling trough menu's or something like that.
Click to expand...
Click to collapse
I have had that problem with my mum's Wildfire S as well.
But then i realized that the phone had not been rebooted in a while.
Restarting the phone did the trick so i assumed that there were too many programs running in the background.
However, now after i guess a couple of months, the problem still persists albeit at a very minor stage.

Either lock the screen then unlock it. Or reboot the phone.
Both methods work for me when I get this issue. I use the lockscreen when I need my phone but if I've got a 5mins spare ill reboot.
Sent from my Incredible S using xda premium

vizzy said:
Either lock the screen then unlock it. Or reboot the phone.
Both methods work for me when I get this issue. I use the lockscreen when I need my phone but if I've got a 5mins spare ill reboot.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
The funny part is when this issue occurs, sliding the lock screen also seems impossible

Then lockscreen and unlock it again and all is fixed? ..... when I have issues with lock screen I just lock and re-unlock then it fixes it.
Does that work for you?
Sent from my Incredible S using xda premium

Locking and unlocking the lockscreen helpes, but there has to be a permanent sollution for this right?

Not that I know of. ....are you using just stock lockscreen etc or do you have 3rd party apps like widget locker?
Sent from my Incredible S using xda premium

vizzy said:
Not that I know of. ....are you using just stock lockscreen etc or do you have 3rd party apps like widget locker?
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
The stock ICS lockscreen.

Ahh. Could try a clean install of a different rom see if it happens? Tbh I'm just learning to live with it I get it once a week even less than that sometimes.
Sent from my Incredible S using xda premium

I get it like 20 times a day so it's pretty annoying..
Sent from my HTC Incredible S using XDA

Ahh then I honestly have no idea. I get it nown and again so it doesn't bother me too much.
All I can say it maybe try a different rom or kernel. Other than that I'm unsure maybe something internally it knackered as a worst case scenario.
Sent from my Incredible S using xda premium

I had this problem aswell. It started out in the same way as yours just being a tad un responsive, but slowly got worse. What it turned out to be was that digitizer was faulty as I replaced the digitizer myself and the problem was solved. As you say that the screen etc has been replaced before this could well be the case. I would recommend getting in done professionally as it isn't an easy job. Look on the market for a touch screen test app and see if you have any dead spots.

letmedanz said:
The funny part is when this issue occurs, sliding the lock screen also seems impossible
Click to expand...
Click to collapse
i've had the unresponsive lockscreen issue when using cm7 and cm7 based roms, then today i checked set cpu and i had a profile for screen off - a low clock speed with conservative governor. Changed to interactive and slightly high clock speeds and dont seem to be facing the issue any more....at least its been okay for the past 6 hours...hope this helps

I find if you lock the phone and wipe the screen until it's nice and clean it fixes this problem. It could be caused by a buildup of finger oils on the screen, or from your face after making a call. Not to sure though.

ZaySk said:
I find if you lock the phone and wipe the screen until it's nice and clean it fixes this problem. It could be caused by a buildup of finger oils on the screen, or from your face after making a call. Not to sure though.
Click to expand...
Click to collapse
I don't think its a reason, coz I've never heard about dirty screen lockscreen problems
Sent from my HTC Incredible S using Tapatalk 2 & its f*cking awesome

vizzy said:
Either lock the screen then unlock it. Or reboot the phone.
Both methods work for me when I get this issue. I use the lockscreen when I need my phone but if I've got a 5mins spare ill reboot.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
same with me.. huhu
http://www.youtube.com/watch?v=PCT5odDTaf8

To the people that are not rooted

Can you tell me why you are not rooted. I'm just curious. I've seen a lot of people that say they are not rooted and or rooted but not running a ROM. I've done it a lot on my gnex but have not found the need to do it on this phone.
Sent from my Nexus 4 using Tapatalk 2

Same here. Still not rooted.
Sent from my Nexus 4 using Tapatalk 2

I just rooted last night, Stock kernel, Stock ROM. The only reason I rooted was so that I could calibrate my display on my phone. There is no other reason for me.

rooted but still using stock ROM
After rooted you can install so many useful apps (e.g. CWM Recovery, Titanium Backup Pro, Market Enabler, Root Explorer........)

Everything is good here, so why put development software on it.?

There's no reason to not root, or at least unlock the bootloader, when you first get the phone. It'll save you a ton of hassle down the road should you ever decide that you want or need root

Solutions Etcetera said:
Everything is good here, so why put development software on it.?
Click to expand...
Click to collapse
Because you can? I don't have the bloody phone yet, but it's going to get rooted.
Ordered my Nexus 4 on Nov. 13th. Still waiting.

Yeah I'm unlocking the bootloader as soon as it arrives, I'll probably leave it stock for a bit but my last 3 devices I bought with the intention of leaving them stock, then decided to root later, and 3 devices I lost data on. So yeah just unlock it when you get it to leave the option open
Sent from my HTC PH39100 using Tapatalk 2

I'm not rooted because:
1) I have no need to be. Stock does everything I want it to do.
2) Having root doesn't allow some apps to work such as Google Movies & TV.
3) I got sick of flashing ROMs, making backups, and restoring everything after a wipe.
Sent from my Nexus 7 using xda premium

Root is useful for some application like ads filter, anti virus like Avast with remote controls. It is only a choice to do if you really need it
Inviato dal mio HTC Desire con Tapatalk 2

You guys probably are not aware of the amazing custom Roms like paranoidandroid that gives you so much control of your phone. Also great kernels like matrix that gives you more Battery life. Stock is great but android is all about modding.
Sent from my Mako Nexus quattro using Tapatalk 2!

El Daddy said:
I'm not rooted because:
2) Having root doesn't allow some apps to work such as Google Movies & TV.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
http://www.ubergizmo.com/2012/07/google-play-movies-streams-rooted-android-devices-now/
They fixed that actually...
Sent from my HTC PH39100 using Tapatalk 2

Cor-master said:
http://www.ubergizmo.com/2012/07/google-play-movies-streams-rooted-android-devices-now/
They fixed that actually...
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Oh nice. I'm glad they fixed that.

This is going to be my first android phone as I'm coming from blackberry and I was doing some research as to rooting my device. That's probably the direction I am going to go but I just had one question. What are the potential drawbacks of rooting your device? I read that some apps don't work such as banking apps and things along those lines. Just wanted to get all the possible information. I'm located in Canada, if that relates to any location specific apps.
Thanks
EDIT: Found some tutorials and threads, thanks

I did unlock the bootloader and I'm rooted, no ROM. I to got tired of flashing and making back ups and redoing my home screen multiple time a week if not every day. That's fun for awhile. But for me all the Roms are all the same for the exception of a few things. My phone runs great and I do get very good battery life. I can understand why some do it but I think android is at that point to where it does and have everything I want. I'm even thinking about unrooting my phone. Haven't needed any thing that requires root yet. I did have the display app for awhile for my screen but I've not used it that much and have not noticed that my screen is slightly yellow. My flickster app won't work when I'm rooted so I think I might unroot it.
Sent from my Nexus 4 using Tapatalk 2

I stayed unrooted for 8 days which is actually a record with any Android device. I liked stock and had no problems with it, but there were just a few features in Cyanogen that I love that aren't available in stock. And they're actually small things such as the volume toggles and the percentage number for battery. But they were worth it. So far my Cyanogen experience has been just as smooth as stock, so there really haven't been any drawbacks. I'm also using the Faux kernel which seems to have improved the wakelock problem the device was having on the stock kernel. I was able to get somewhere around 20 hours of battery life yesterday when I was getting around 12 on the stock kernel. I still haven't calibrated the display to my likings yet, but I'll get to that. Needless to say, I'm really enjoying having a Nexus 4.

I liked rooting my vivid because sense sucked, but I went with a aosp ROM and was very happy. Though, what I like more is messing with new software updates (official) and not being rooted just makes that easier to download. There's nothing I miss from rooting. Everything I did was to make the phone as smooth running as possible and that's what I got now.
Sent from my Nexus 4 using xda premium

Not rooted. The entire reason I rooted my old GS2 was to get AOSP on it. This has it in its purest, best form stock.

I root because I want to block ads, use titanium backup, Franco Kernel, AOKP (I have my menu and search button back plus the nav bar ring has more options than just google now). I use TWRP for backups in case I mash my phone and Google doesn't have images up yet... I can at least restore mine LOL. I use lots of tasker tasks with root. Use Datasync to auto backup and restore games and other app data on each device (not just when flashing ROMs. I mean I play a game and put down phone pickup tablet and data is already synced on there.). There's just so many things to do with it!

I will eventually, and most likely roll to CM, but until that time I just have no need for it.
Sent from my Nexus 4 using xda app-developers app

Lag when unlocking on 4.4

Randomly when I will unlock my phone from the active display screen ( when you just have to pull the lock icon down) there will be a solid 3-4 second Lag before the screen unlocks. Am I the only one experiencing this. I'm completely stock with the 4.4 ota on vzw.
Sent from my Moto X

Dogbone737 said:
Randomly when I will unlock my phone from the active display screen ( when you just have to pull the lock icon down) there will be a solid 3-4 second Lag before the screen unlocks. Am I the only one experiencing this. I'm completely stock with the 4.4 ota on vzw.
Sent from my Moto X
Click to expand...
Click to collapse
Wow. All these problems with 4.4. It's running great on my N7, so I think I'll hold off. Tmobile didn't even push it out yet, but I like 4.2.2

I have the same issue on stock 4.2.2. Happens maybe a couple of times a day. Not sure the cause.
Sent from my XT1053 using Tapatalk

Dogbone737 said:
Randomly when I will unlock my phone from the active display screen ( when you just have to pull the lock icon down) there will be a solid 3-4 second Lag before the screen unlocks. Am I the only one experiencing this. I'm completely stock with the 4.4 ota on vzw.
Sent from my Moto X
Click to expand...
Click to collapse
this is being discussed in another thread. it is a minor annoyance but doesn't seem to hinder phone operation.

I turned off slide unlock and haven't had a problem since. I think there's a bug between active display unlock and slide unlock...
Sent from my XT1060 using Tapatalk

Credits to the user that posted this. You can fix this by switching to no lock, unlock the phone using active notifications, and select swipe to unlock again. That fixed my issue and lag for me.
Sent from my XT1060 using Tapatalk

DroidOnRoids said:
Credits to the user that posted this. You can fix this by switching to no lock, unlock the phone using active notifications, and select swipe to unlock again. That fixed my issue and lag for me.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
This helped me for about a day, and then the lag came back... note that (for me at least) the delay has only ever happened maybe 10% of the time, so it takes a while to test if it's actually fixed.
also it seems to be worst when swiping up into an application vs. down to the home screen.

I am experiencing this too since upgrading to 4.4. Gonna try disabling /reenabling Slidelock , see if it helps
Sent from my XT1060 using xda app-developers app

blynkofaneye said:
I am experiencing this too since upgrading to 4.4. Gonna try disabling /reenabling Slidelock , see if it helps
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Did it help?
Sent from my XT1056 using Tapatalk

Fix a no go for me
Tried the method posted above on my AT&T Moto X (newly updated to 4.4). Literally no more than ten minutes later, the lag was back. This is unfortunate.

on the soak test forums this has been reported by a lot of users, so Motorola is aware

DertyDOH said:
on the soak test forums this has been reported by a lot of users, so Motorola is aware
Click to expand...
Click to collapse
They must have been well aware of it before they released any of the official 4.4 versions. While it doesn't happen all the time it happens enough any Motorola employee using it would have noticed. And they have been testing it for at least two weeks so really no excuse.
I believe they knew perfectly well about it but decided to push out the update anyway to be first to get 4.4 out the door.
I've been very impressed with Motorola so far, but this is a bit of a black mark, hopefully they are already working on a fix.

Does anybody else get a force close when going to Settings ==> Security? The lag described in this thread and my issue happened when I upgraded to 4.4, so I figure it's something related.

Guys I was getting the same issue after its update. I had some other issues with apps not installing force closing etc so I bit the bullet and did a factory data reset through recovery. Lag is gone and all other issues with KitKat fixed. YMMV
Sent from my XT1060 using xda app-developers app

strictlyphat said:
Guys I was getting the same issue after its update. I had some other issues with apps not installing force closing etc so I bit the bullet and did a factory data reset through recovery. Lag is gone and all other issues with KitKat fixed. YMMV
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
^^^ This
Did this for unrelated reason and now all my 4.4 quirks seem to be gone.
Sent from my XT1060 using Tapatalk

strictlyphat said:
Guys I was getting the same issue after its update. I had some other issues with apps not installing force closing etc so I bit the bullet and did a factory data reset through recovery. Lag is gone and all other issues with KitKat fixed. YMMV
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Dev edition?

strictlyphat said:
Guys I was getting the same issue after its update. I had some other issues with apps not installing force closing etc so I bit the bullet and did a factory data reset through recovery. Lag is gone and all other issues with KitKat fixed. YMMV
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
I just got done re-installing everything after doing a factory reset, and I'm still having the black screen for a second or two after unlocking an active notification. So I would definitely not recommend other people try this, unless you want to waste a few hours re-installing stuff.

ice20978 said:
I just got done re-installing everything after doing a factory reset, and I'm still having the black screen for a second or two after unlocking an active notification. So I would definitely not recommend other people try this, unless you want to waste a few hours re-installing stuff.
Click to expand...
Click to collapse
I was just about to do a reset. Glad I came back here first.

I am also experiencing the lag. It seems to do it more when an app (such as chrome) is open when locking. I also noticed I have a really hard time with the two finger swipe down on the notification bar as well.

ice20978 said:
I just got done re-installing everything after doing a factory reset, and I'm still having the black screen for a second or two after unlocking an active notification. So I would definitely not recommend other people try this, unless you want to waste a few hours re-installing stuff.
Click to expand...
Click to collapse
I even fastbooted the official firmware to complete stock again and I'm still getting it. It's obviously firmware related.

When i flash custom roms it breaks root :(

You guys have any idea why it would do that and what i could do to fix that.

kyhassen said:
You guys have any idea why it would do that and what i could do to fix that.
Click to expand...
Click to collapse
Care to provide more information? Not really enough here to go on. What ROMs you're trying and what you've run in the past might be good places to start.

Ok sorry for late reply I didn't see this. I been having issues after issues with this phone the minute I rooted it lol. Constant crashes, keyboard broke so I had to get my swift key back, voice to text doesn't work at all on any Rom which is annoying me. Data keeps turning on and off. Battery will say full but keep getting low battery notification. Bucket full of fun most of it I will tolerate. I found out SuperSU or whatever doesn't work on 4.3 and I need to manually root it again which idk if I'm using the right file
Sent from my HTCONE using XDA Premium 4 mobile app

Superuser works fine on 4.3,broken kb sounds like rom issue. You flash a rom for sprint version right(or one with sprint support and no kernels (none for sprint phones yet)
Sent from my HTCONE using Tapatalk