I found a reproducible bug in LG ROM (sprint). How can I submit a bug report where it may actually get read?
Sent from my LM-V405 using Tapatalk
barth2 said:
I found a reproducible bug in LG ROM (sprint). How can I submit a bug report where it may actually get read?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
Okay I figured out every time I turn on inverse color to fake dark mode on an app that doesn't have it, the color gets reset to Auto. Don't know if it's a bug or intentional. I'd expect it to go back to my choice when I turn off over inverse color.
Sent from my LM-V405 using Tapatalk
Related
All my vibrations aren't as strong I guess you could say. And the haptic on the 4 bottom buttons don't vibrate at all when I press them, but what's weird is it makes a slight click noise like its trying to vibrate. Whhat should I do? I updated my cm6 nightly and it didn't change. I'm about to try a different rom. Is this something HTC would fix?
Sent from my Nexus One using XDA App
Really? Not a single reply wtf. Would they fix it? Its rooted
Sent from my Nexus One using XDA App
If it's hardware, they'll fix it assuming that it wasn't a software issue that caused the hardware. When I sent my unlocked/rooted device in for rebooting issues, they repaired it free of charge.
rickytenzer said:
If it's hardware, they'll fix it assuming that it wasn't a software issue that caused the hardware. When I sent my unlocked/rooted device in for rebooting issues, they repaired it free of charge.
Click to expand...
Click to collapse
funny same issue. and yes it was fixed under warranty. the phone was unlocked but i loaded up a stock rom before sending it back
That's a little more reassuring. Thanks. How long was the process?
Sent from my Nexus One using XDA App
I got a note here a few days ago and I noticed that the back and menu button freeze up sometimes. So I just restart the phone and it's good to go. Has anyone else had this issue? I sure hope it's a software issue and not a hardware issue.
Sent from my Nexus S using XDA App
Anyone? I don't think it's an app issue because when I got it, it was already reset.
Sent from my Nexus S using XDA App
phoneman09 said:
Anyone? I don't think it's an app issue because when I got it, it was already reset.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Same here, have happend 3 times in one week. Reboot is the only solution when it happends.
Do you think it's a software issue and ics will fix the issue?
Sent from my Nexus S using XDA App
I've had it happen to me once in the past couple of weeks with the stock GB rom. Hopefully it is on Samsung's bugfix list. BTW, does Samsung have a public url to report bugs?
I don't believe that there is, but I could be wrong.
phoneman09 said:
I got a note here a few days ago and I noticed that the back and menu button freeze up sometimes. So I just restart the phone and it's good to go. Has anyone else had this issue? I sure hope it's a software issue and not a hardware issue.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
It could be possible that its just a software glitch, have you taken it to the service center and asked them to update the software? I've read reports about those before with the Galaxy S2, some had it fixed with a software update while others got a replacement.
No I haven't because I would have to send it to them and then I would be without a phone. I hope when ics comes out it fixes the issue. If not I'll give them a call.
Sent from my Nexus S using XDA App
phoneman09 said:
Do you think it's a software issue and ics will fix the issue?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I absolutly think it is a software issue...
I sure hope so, that's all I gotta say!
Sent from my Nexus S using XDA App
That actually happened to me twice randomly...
Was checking out some clothing in browser and the back and menu buttons lit up but stopped working =/ got a bit confused to be honest! restart fixed it!
Second time i was playing Fruit Ninja and the same thing happend =/
How i fixed it ? Installed "CheckRom REVO" and "abyssnote" kernel.
Never happend again since then! Dont really know what was the actual problem but this is my only solution! Hope i was helpfull!
Sent from my GT-I9300 using XDA
Im also curious if there's any difference in firmware if let's say i live in singapore and upgraded using the malaysia version? Since the ics for singapore isnt out yet, and i cant wait anymore, are there huge performance changes between region specific roms?
Sent from my GT-N7000 using xda premium
iihito702 said:
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
You ask the right question! I can't understand this. Does Samsung officially response on this emmc bug problem?
skyhew said:
You ask the right question! I can't understand this. Does Samsung officially response on this emmc bug problem?
Click to expand...
Click to collapse
Say for example, you purchase an ERP software and start to modify/customize the software to your taste/requirement, and it run well w/out any issue. Later when the ERP vendor release an updated version of the software, you updated and your modified/customized component doesn't fit in and has causes corruption on your data, that is your own problem, there won't be any issue if you've used the software as it is, without modifying a single code.
The same applies to the so-called emmc bug, does it even trigger if you've use the firmware as it is? Only the dev/expert will know.
Actually it triggers during normal factory resets too.
Edit: As per the bricking threads, it has a certain percentage of happening. Making the whole thing uncertain with people having successes with some having bricks.
Sent from my GT-N7000 using Xparent Sky Blue Tapatalk 2
Cause they love quality control and want to test global recall on all ics running phones
Hihihi
Sent from my GT-N7000 using Tapatalk 2
Markuzy said:
Actually it triggers during normal factory resets too.
Edit: As per the bricking threads, it has a certain percentage of happening. Making the whole thing uncertain with people having successes with some having bricks.
Sent from my GT-N7000 using Xparent Sky Blue Tapatalk 2
Click to expand...
Click to collapse
The normal factory reset on a Jailbroken iPhone has different effect than on a non-jailbroken one.
Sent from my GT-N7000 using XDA Premium HD app
ycneosg said:
The normal factory reset on a Jailbroken iPhone has different effect than on a non-jailbroken one.
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
I am not too sure if it is different for Android Gingerbread and ICS .
Sent from my GT-N7000 using Xparent Sky Blue Tapatalk 2
Because they're taking a gamble on it happening only in a minority of cases or a minority of users being susceptible.
Presumably they have risk assessment or a conscious thought process internally that we're not privy to. To us it looks random in occurrance. Perhaps Samsung know more about it than we do and can take calculated risks.
I just recently updated to the cm 10.1.3 final build and I've noticed that there is a red light that always comes on between the earpiece and the front camera... Not sure what it is or why it seems to be on all the time. Rebooting the phone seems to fix it, but by the end of the day it is back on. Any thoughts?
Sent from my XT894 using Tapatalk 4
Goodeman said:
I just recently updated to the cm 10.1.3 final build and I've noticed that there is a red light that always comes on between the earpiece and the front camera... Not sure what it is or why it seems to be on all the time. Rebooting the phone seems to fix it, but by the end of the day it is back on. Any thoughts?
Sent from my XT894 using Tapatalk 4
Click to expand...
Click to collapse
That red light is the proximity sensor (well, half of it, the receptor is next to it). Not sure what's causing it to come on in your case - there was a version of Viber that switched it on constantly a few months ago, but that got fixed in a subsequent release.
Cheers,
Steve.
StevePritchard said:
That red light is the proximity sensor (well, half of it, the receptor is next to it). Not sure what's causing it to come on in your case - there was a version of Viber that switched it on constantly a few months ago, but that got fixed in a subsequent release.
Cheers,
Steve.
Click to expand...
Click to collapse
I figured it was the proximity sensor. Not sure what is activating it though. I don't have Viber FYI. Is there an app that could tell me which apps can control the proximity sensor?
Sent from my XT894 using Tapatalk 4
Goodeman said:
I figured it was the proximity sensor. Not sure what is activating it though. I don't have Viber FYI. Is there an app that could tell me which apps can control the proximity sensor?
Sent from my XT894 using Tapatalk 4
Click to expand...
Click to collapse
I've only ever noticed it being on while in call
Sent from my XT894 using xda app-developers app
rruleford said:
I've only ever noticed it being on while in call
Sent from my XT894 using xda app-developers app
Click to expand...
Click to collapse
Same here until now
Sent from my XT894
http://www.gottabemobile.com/2014/03/19/new-android-4-4-kitkat-update-android-4-4-3/
I'm just sharing some potential hope for those (myself included) waiting for some bug fixes from Google
In before its released the next day like 4.4.2
Sent from my HTC One using Tapatalk
Hopefully out before April
Sent from my Nexus 5 using Tapatalk
1 april: Android Lime Fish
I wish it was Laffy taffy
Sent from my Nexus 5 using Tapatalk
Yes.. is going to come out real soon and all the bugs will be fixed!!!!!
no honest really
I was told from a guy, whose uncle's friend works for Google in custodial and says positively an update will be coming the day it gets released which will have slight differences than previous versions.
Sent from my Nexus 5 using Tapatalk
chrisinsocalif said:
I was told from a guy, whose uncle's friend works for Google in custodial and says positively an update will be coming the day it gets released which will have slight differences than previous versions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Lmao that's more reliable than ibtimes sadly.
Sent from my Nexus 5 using Tapatalk
http://m.techradar.com/news/softwar...-fix-the-nexus-5-s-bluish-camera-tint-1236600
Sent from my Nexus 5 using XDA Premium 4 mobile app
atheistevofreak said:
http://m.techradar.com/news/softwar...-fix-the-nexus-5-s-bluish-camera-tint-1236600
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First time I heard about any tint on our camera.
Sent from my Nexus 5 using Tapatalk
FuMMoD said:
First time I heard about any tint on our camera.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, me too. I haven't noticed it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
FuMMoD said:
First time I heard about any tint on our camera.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Likewise. On every firmware/kernel I've tried, Ive never once experienced this nor heard of it either...
Maybe it addresses an issue the HTC One has. I thought he was more of an HTC leaks guy.
Sent from my Nexus 5 using xda app-developers app
FuMMoD said:
First time I heard about any tint on our camera.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I sub to our huge photo thread, and have NEVER heard of this. There is an occasional comlaint of a spot, but that appears an infrequent hardware issue. Techradar now on my bs lst along with the current king, IBT.
A new update...and more bugs created in it's wake...sigh Google
Sent from my Nexus 5 using Tapatalk
wideasleep1 said:
I sub to our huge photo thread, and have NEVER heard of this. There is an occasional comlaint of a spot, but that appears an infrequent hardware issue. Techradar now on my bs lst along with the current king, IBT.
Click to expand...
Click to collapse
Yeah same here. I'm subbed to the defects thread, picture thread and I followed the rma thread for a few weeks. I never saw any mention of a tint. People did mention a purple tint on the HTC one when comparing the HTC one to our phones.
Sent from my Nexus 5 using Tapatalk
FuMMoD said:
Yeah same here. I'm subbed to the defects thread, picture thread and I followed the rma thread for a few weeks. I never saw any mention of a tint. People did mention a purple tint on the HTC one when comparing the HTC one to our phones.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
With a couple of entirely non-educated, unprofessional clicks ( I swear the net has given any old attention-whore (clickbait,etc.) a podium) I was able to determine this is the battery drain bug fix mentioned a few weeks back:
https://twitter.com/LlabTooFeR/status/448025237272420352
https://www.google.hr/search?q=nexu...oogle&sourceid=chrome-mobile&espvd=1&ie=UTF-8
Seriously..relying on Twitter for breaking news is JUST LIKE relying on the town crazy flailing his arms when he stumbles down the street, but even less accurate, because at least he knows what's goin on in his own reality.
This article seems to be more accurate in the proposed direction of the coming update.
http://www.androidpit.com/android-4-4-3-tested-for-nexus-5#readsoruce_bottom
Sent from my Nexus 5 using XDA Premium 4 mobile app
I'm going to be mighty disappointed if the only bug fix is for the camera.
what about..
the 0 bytes/restart services bug?
the microphone bug in calls?
the microphone bug in videos?
the non received message and calls bug?
the intermittent slow WiFi bug when data is switched on?
.. come on Google!!!!!!